fix(development-system): align component workflow routing

Route every verified green increment through its selected delivery checkpoint before ticket-terminal review, then reserve the final delivery handoff for unchanged exact-identity readiness.

Closes: 20260901-xige

Author: jwilger

plugins/development-system/components/development-discipline/skills/development-workflow/SKILL.md

@@ -58,10 +58,10 @@ still routes to `final-review`, even when that review itself is read-only.
 | Answer or review only                          | The relevant domain, documentation, security, OpenAI, or browser capability                | The requested answer or review is complete; do not enter implementation without a change request                    |
 | Diagnose unexpected behavior                   | `systematic-debugging`                                                                     | Evidence identifies the cause; implementation is separately requested or already in scope                           |
 | Prepare a substantive change                   | `change-preflight`, then `delivery-workflow` to select delivery mode and increment cadence | Every required surface has an evidence-backed decision and the delivery policy is known before preservation actions |
-| Implement a feature, fix, removal, or refactor | `test-driven-development`                                                                  | RED is used when applicable; the current increment is verified and its lightweight review is clean                  |
-| Verify a completion claim                      | `verification-before-completion`                                                           | Fresh evidence covers the exact claim                                                                               |
-| Review the completed change                    | `final-review`                                                                             | The review coordinator reports completion for the current diff                                                      |
-| Choose commit and publication mode             | `delivery-workflow`, plus `rationale-commit-messages` when a commit is authorized          | Repository-selected delivery evidence is current                                                                    |
+| Implement a feature, fix, removal, or refactor | `test-driven-development`, then the selected `delivery-workflow` checkpoint                | RED is used when applicable; the increment is tested, lightly reviewed, gated, and delivered                        |
+| Verify a completion claim                      | `verification-before-completion`                                                           | Fresh evidence covers the exact increment or terminal claim                                                         |
+| Review the delivered completed change          | `final-review`                                                                             | All increments are delivered and the coordinator reports completion for that exact identity                         |
+| Choose commit and publication mode             | `delivery-workflow`, plus `rationale-commit-messages` when a commit is authorized          | The increment checkpoint or post-review exact-identity readiness evidence is current                                |
 | Create or update a PR or MR                    | `delivery-workflow` for authorization and mode, then the available forge capability        | The PR/MR exists at the intended exact head and its URL and state are recorded                                      |
 | Respond to a pushed CI failure                 | `ci-failure-follow-up`                                                                     | A causal repair or unchanged-revision rerun reaches terminal success                                                |
 | Respond to review feedback                     | `receiving-code-review`, then the applicable implementation and verification specialists   | Valid feedback is resolved or technically defended                                                                  |
@@ -70,7 +70,11 @@ still routes to `final-review`, even when that review itself is read-only.
 For ordinary implementation, the usual sequence is repository inspection,
 `change-preflight`, early `delivery-workflow` selection, one
 `test-driven-development` applicability decision and one increment at a time,
-`verification-before-completion`, `final-review`, and `delivery-workflow`.
+`verification-before-completion`, and the selected `delivery-workflow`
+checkpoint for every increment. Only after every planned increment is delivered
+does `final-review` inspect that exact identity; its clean result then returns to
+`delivery-workflow` solely for exact-identity readiness, not to manufacture a
+new commit or checkpoint.
 `rationale-commit-messages` governs each authorized commit. The selected
 delivery workflow governs whether work is committed, pushed directly, or sent
 through a PR/MR, and whether exact-revision CI must reach a terminal result.
@@ -94,16 +98,19 @@ Keep these boundaries explicit in both action and advisory responses:
 
 - Start with current user direction, repository instructions, and mutable state
   before describing any commit or push. For a substantive change, select
-  `delivery-workflow` before the first preservation action. After
-  `final-review`, recheck `delivery-workflow` for final delivery.
+  `delivery-workflow` before the first preservation action. Deliver every green
+  increment through that selected mode before terminal `final-review`. After a
+  clean terminal review, recheck `delivery-workflow` only for readiness of the
+  unchanged reviewed identity.
 - For answer or domain-review work that is not a completed-diff final review,
   skip `change-preflight`,
   `test-driven-development`, `verification-before-completion`, `final-review`,
   `delivery-workflow`, `babysit-pr`, commits, pushes, PR/MR creation, and ticket
   creation unless a separate change request activates them.
 - After diagnosis identifies the cause, inspect state again, then route through
   `change-preflight`, early `delivery-workflow`, `test-driven-development`,
-  `verification-before-completion`, and `final-review` for an authorized fix.
+  `verification-before-completion`, checkpoint delivery, and—only when all
+  planned work is delivered—`final-review` for an authorized fix.
 - Before creating or updating a PR/MR, inspect current repository state again,
   confirm PR/MR mode and authorization, select an available forge capability,
   and bind creation plus the recorded URL and state to the exact reviewed head.