[Unit PRs] Complete intents from the full unit delivery set without a rollup PR #563

Part of #553. Suggested step 9 of 13; one focused PR into main.

Outcome: An intent using the new strategy can finish from its complete, verified unit delivery set without opening an intent-to-base rollup PR.

Depends on: #558, #559, #561, #562

Scope

• Extend the existing completion/delivery owner to account for every required current-plan unit, foundation/follow-up delivery, shared stage, gate and repository outcome.
• Skip final intent-PR publication only for the new policy. Preserve finalization for existing strategies and distinguish workflow, publication and delivery outcomes.
• Produce a complete versioned delivery set for downstream tracker/UI consumers. Do not treat the first observed PR or a transient empty list as the complete set.
• Represent accepted scope omissions explicitly according to the agreed policy; they are not merged units. Define an explicit all-no-change outcome without fabricating a PR.

Acceptance criteria

• Successful complete delivery creates no aggregate intent PR and reports every unit PR/result.
• Blocked units, unowned shared output, failed final checks or unresolved repository outcomes prevent full completion.
• A later workflow section or plan revision cannot be omitted from an earlier delivery set.
• Accepted omissions and zero-change runs have explicit outcomes; neither is confused with missing delivery evidence.
• Focused completion/replay tests cover current-plan identity, repeated finalization and both legacy strategies.

PR boundary and rollout

Execution completion and delivery accounting only. No parent tracker writes, UI redesign, model reruns during publication reconciliation or second completion state machine.

Related work to reconcile

Reconcile with #534, #537 and #539 before implementation. Reuse their final completion/publication contracts when available on main; do not independently recreate those safeguards in this child.

Starting points

lambda/v2-orchestrator/index.js, lambda/v2-orchestrator/section.js, lambda/shared/v2-process-keys.js, lambda/shared/v2-process-store.js, lambda/intents/index.js.

Planning baseline: main at b5d68d5d2f12292d56a21aab917e4d8f9538aa0b (2026-10-15). Recheck current main and applicable guidance before implementation. Existing strategies remain supported; the new capability stays disabled until qualification.