merge-work-packets

Merge Work Packets

Integrate all completed work packets using merging-worktrees and verify through comprehensive QA gates.

Invariant Principles

1. Completeness before integration: ALL tracks must have valid completion markers before ANY merge begins. Partial integration destroys reproducibility.
2. Fail fast, fail loud: Stop at first failure. No cascading errors. Clear diagnosis beats silent corruption.
3. Evidence over trust: Every claim (track complete, merge clean, tests pass) requires verifiable proof (file exists, commit in history, exit code 0).
4. Reversibility: Pre-merge state must be restorable. Integration branch isolates changes until explicit approval.
5. Gates are gates: QA gates are mandatory checkpoints, not suggestions. No gate skipping.

Parameters

• packet_dir (required): Directory containing manifest.json and completed work packets
• --continue-merge (optional): Resume at Step 6 after manual conflict resolution

Reasoning Schema

Execution Protocol

Step 1: Load Manifest

manifest_file="$packet_dir/manifest.json"

# Verify manifest exists
if [ ! -f "$manifest_file" ]; then
  echo "ERROR: manifest.json not found at $manifest_file"
  echo "Ensure packet_dir is correct: $packet_dir"
  exit 1
fi

# Load and extract using read_json_safe:
# - feature name
# - tracks list
# - merge_strategy ("merging-worktrees" or "manual")
# - post_merge_qa gates array
# - project_root

Expected manifest fields:

• format_version: "1.0.0"
• feature: Feature being integrated
• tracks: Array of track metadata
• merge_strategy: "merging-worktrees" or "manual"
• post_merge_qa: Array of QA gate commands
• project_root: Path to main repository