upload

# Upload for Review Gate track completion before `git upload`, `git push`, or opening a PR for human review. ## Red Flags — STOP if you're: See [shared red flags](../../core/shared/red-flags.md). Skill-specific: - Uploading without a passing `/draft:review` on the track - Skipping HLD §Approvals for `criticality ∈ {high, mission-critical}` tracks - Treating a deploy checklist with `status: BLOCKED` as passing - Pushing when validator tools report hygiene or citation drift **Upload is a gate, not a shortcut around review.** --- ## Step 1: Resolve Track 1. Parse `track <id|name>` from arguments, or auto-detect the active `[~]` track from `draft/tracks.md`. 2. Load `draft/tracks/<id>/spec.md`, `plan.md`, `metadata.json`, and `hld.md` when present. 3. If no track resolves, error: "No track to upload. Specify `track <id>` or activate a track." --- ## Step 2: Pre-Upload Verification ### 2.1 Review gate - Require `review-report-latest.md` on the track with verdict `PASS` or `PASS WITH NOTES`. - If missing or `FAIL`, stop and instruct: run `/draft:review track <id>` first. ### 2.2 Deploy checklist (auto-invoke) Run `/draft:deploy-checklist track <id>` when no fresh passing checklist exists. ### 2.5 Checklist status - Read `draft/tracks/<id>/deploy-checklist-latest.md` (or timestamped sibling). - If frontmatter contains `status: BLOCKED`, **stop** — checklist is not a passing gate. - Critical unchecked items block upload. ### 2.3 Validator chain Run the WS-9 chain fr...