…TION_REQUIRED, eval)

After gstack-build monitor exits 0 (ALL_RUNS_COMPLETE) or 13
(FINALIZATION_REQUIRED), agents were stopping without running Step 3:
Final Ship & Completion, leaving branches unmerged and plans unarchived.

Three-layer defense:
1. Compaction-resistant bash printf in M3.5 block — survives context compaction
   as a tool result visible in active context
2. MANDATORY prose block after M3.5 fence — explicit direction to Step 3
3. ALWAYS RUN callout at Step 3 header — second reminder at the destination

Also adds exit code 13 (FINALIZATION_REQUIRED) to the exit code table and
a periodic LLM-judge eval (skill-e2e-build-step-transition) that verifies
agents correctly proceed to Step 3 after monitor exit.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…addition

The review resolver now includes content-review in the dashboard skill list.
Update the gen-skill-docs test assertions to match the new ordering:
  plan-eng-review, review, content-review, plan-design-review

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

New capability (non-code phase kinds, step-transition guardrails) and
concurrent-build fix warrant a MINOR bump per fork versioning convention.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

The skill-md.test.ts assertions hardcoded the version string to verify
TDD changes are present. After the v1.22.0 bump these checks failed.
Update to match the current version so the same guard continues to work.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

When --skip-ship leaves all features at origin_verified, gstack-build
exits with code 13 (FINALIZATION_REQUIRED). Two integration tests were
asserting exit 0 — a pre-existing failure on main. Update both assertions
to expect 13, with comments explaining the code meaning.

Also treat exit 13 as "success" in the activity log so skip-ship sessions
don't show up as failures in dashboards/retros.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

When all features reach origin_verified but --skip-ship prevents the
ship step, exit with code 13 (FINALIZATION_REQUIRED) instead of 0.
Exit 0 would signal "done" to the orchestrating skill, but Step 3
(ship + archive) is still required — the user must explicitly ship.

This pairs with the integration test update (expect 13 not 0).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

- Regenerate build/SKILL.md from template after step-transition and
  content-review gate changes
- Add --no-plan-review to integration test invocations that use
  --skip-ship and --skip-clean-check to prevent LLM calls in CI

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

… regex

- Add buildKindInstructions(phase: Phase): string[] to cli.ts — exported
  function for kind-specific implementation prompts (writing/experiment/
  research/manual/code). Tested by cli.test.ts:3714-3760.
- Fix extractCoverageTarget regex to support decimal targets like ≥90.5%.
  Previous pattern (\d+) truncated at the decimal point.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>