fix(vibe): Set IN_PROGRESS after cl-execute gate

[shafty023]

Purpose

cl-execute gave contradictory status instructions to a run that blocks at the readiness gate. Intake step 7 said to mark the ticket IN_PROGRESS when evaluation starts, but references/result-formats.md says a gate that blocks returns BLOCKED_BEFORE_START with Feature status: <unchanged status>. This came up on a real run against ISS-12552.

Now the status moves only once the gate lets work proceed:

• Step 7: do not mark any included feature IN_PROGRESS during intake or the readiness gate. A gate that ends in BLOCKED_BEFORE_START, including HUMAN_REVIEW_REQUIRED, leaves every feature status unchanged.
• Step 10: only after the gate returns GO, or GO_WITH_UI_PLAN_APPROVAL and planning proceeds, mark each included non-terminal, non-currently-blocked feature IN_PROGRESS, then confirm it before returning a planning wait or starting execution.
• cl-sweep said the same thing as the old step 7 ("a ticket worker that begins evaluation, requirements discovery, or plan creation must mark the feature IN_PROGRESS"). It now states the gate-first rule too.

result-formats.md already matched the intended behavior and is unchanged.

Files changed

• plugins/vibe/skills/cl-execute/SKILL.md (intake steps 7 and 10)
• plugins/vibe/skills/cl-sweep/SKILL.md (ticket worker status rule)
• plugins/vibe/.claude-plugin/plugin.json, plugins/vibe/.codex-plugin/plugin.json (1.0.41 to 1.0.42)
• CHANGELOG.md (### vibe v1.0.42)

Commands run

node --test plugins/vibe/skills/cl-sweep/scripts/*.test.mjs plugins/vibe/skills/cl-execute/scripts/*.test.mjs   # 182 pass, 0 fail
uv run pytest plugins/vibe -q                                                                                    # 211 passed
cd tools/plugin-manifests && npm ci && npm test                                                                  # 6 passed

No test pinned the old wording, so no test changed. No Python was touched.