wraplisted

# Wrapping up an approved task **Project facts come from `.claude/WSS.WORKFLOW.json`**: `WSS.branch.integration` is what this skill pushes — and, from a lane worktree, what it fast-forwards that lane onto — `WSS.record.roadmap` and `WSS.record.releases` are what step 6 reads, and `WSS.commitTrailer` names the session trailer. Without a manifest, fall back to the current branch and say in one line that you did. Where `.claude/WSS.LANE` names a lane, `WSS.lanes.named.<lane>.records.X` overrides `WSS.record.X` for the splittable keys — [`WSS.LANE-CONTRACT.md`](../../wss/workflow/WSS.LANE-CONTRACT.md)'s resolution rule. `WSS.record.releases` is never among them, which is why step 6 asks the milestone question only from the main checkout. **This skill writes no record file.** The handoff — the part that makes this the handoff — belongs to `handoff-writer`, which step 3 invokes. Who owns what is [`wss/workflow/WSS.OWNERSHIP.md`](../../wss/workflow/WSS.OWNERSHIP.md). ## The `--wss-wrap` shorthand `--wss-wrap` invokes this immediately, with no confirmation and regardless of whether the work looks finished. It overrides every judgment call below: don't ask "is this really done?", don't wait for approval of the last deliverable, just run the closing ritual. Where a flag counts is [`README.md`](../../README.md); what it authorizes is the block `wss-shorthand-flags.sh` injects and [`wss/workflow/WSS.OWNERSHIP.md`](../../wss/workflow/WSS.OWNERSHIP.md)'s matrix — the two copies `wss-d