fix(orchestration): stabilize accepted authority and controller review flow

[Ldsystem]

Summary

Publish the accumulated WOR-109/WOR-112 source work, including the controller-first flow repair. This branch contains 48 commits not yet in main; it is not limited to the latest two repair commits.

• Persist and consume compact accepted-task authority without replaying historical executor handoffs.
• Stabilize semantic plan identity, planner decomposition/reslicing, and lightweight scope control.
• Reuse claim-bound validation observations; keep execution evidence separate from reusable project CI.
• Build product-only review candidates and controller-owned publication envelopes; check stage evidence before reviewer dispatch.
• Admit current task/binding/scope/validation/ownership authority and preserve scoped product repair findings.
• Reconcile runtime behavior with existing rules, skills, contracts, and reusable regressions.

Verified source

• Commit: 962da878550a924407c58f00a4143ccfea3ecf51
• Tree: a85c2dad15a458e26f8e4e858ae57e4ea2d72eea
• bin/work-bundle-ci: exit 0; 48/48 modules passed; skills passed.
• Independent scoped collaborator source review: accepted, no findings on this exact commit.
• Source checkout clean after validation; no source changes for PR preparation.

Why draft / remaining WOR-112 closure

This PR does not declare final integrated WOR-112 acceptance. Native review publication still accepts only sandbox-process provenance, while the actual independent Codex collaborator review used a different transport. No receipt was fabricated and no review was replayed for bookkeeping. Task 005 also has claim-relevant task/scope/validation-allocation drift, and Task 006's accepted result still references earlier source. Current final integrated acceptance and migration-impact closure remain outstanding.

The larger accumulated diff removes source-local historical execution artifacts as part of the earlier execution/source-boundary work and promotes reusable regressions. This PR preparation did not rewrite historical evidence or workspace control artifacts. No execution-flow or work-bundle-mcp changes are included.

Related: WOR-109, WOR-112. WOR-113 and WOR-75 have been reconciled to reuse the applicable WOR-112 repair after its final acceptance. No downstream issue is started or closed by this PR.