[zy95-12]

Written-by: Codex

Fixes the confirmed source defects tracked by #2393 on delivery/ai-centric-development-service. Chief execution/protocol failures now remain Run diagnostics instead of overwriting Task business blocks, accepted tests or Review evidence. Scoped responses apply valid Task decisions once and return exact field/scope/receipt feedback through the existing bounded correction and fresh-snapshot path.

Chief retains the decision about retry, downstream role, consultation and completion. No fixed recovery workflow, automatic escalation, alternative state store, JSON boolean repair or broad unmanaged-process release was introduced. Existing interrupted verification recovery remains available; explicit reconcile-exit reuses #2375 with protected current-invocation authority. Its own current coordination lease is excluded from the retirement barrier, while old invocations and other workers remain barriers.

Updated PROJECT/ROADMAP long-term memory, dated architectural decision, owned subsystem/operations documents, OpenAPI contracts and canonical generated patches.

Validation at 40a2df43ebcb94e5a6ad4f87d01a2ceeac1b1b03:

• Original Task-block pollution and cross-Task batch coupling regressions failed before the fix.
• 85 affected Chief/input/service tests, 10 API/docs tests and all 6 policy-budget tests passed before the final narrow lease integration fix; its new regression failed before and 3 selected delivery regressions passed afterward.
• Exact-head full npm run verify passed: 4,968 tests, 0 failures, including all 8 real disposable DSH runtime scenarios. Exact-head GitHub Actions job logs confirm Node 24 completed with no failed tests/steps and tests-ok recorded test: success, plugins: skipped, package: skipped. The API rollup still reports queued, inconsistent with the completed logs; that projection is not represented as a green status. Evidence: Node 24 job, tests-ok job. Both checked out the merge of exact head40a2df43 into basece65e1a6.
• Pairing review of the final delta found no blocking findings. No comments, reviews or unresolved threads at the latest refresh.

Limits: deterministic fixtures and disposable SDK/DSH execution are distinct from the reported OpenToday live timeline. No live tasks, credentials, resource profiles, deployment or original frontend changed. No real private installed-App acceptance is claimed. The standing Owner delivery-branch basic-CI policy applies; missing independent Verifier/enqueue PASS is not represented as passed.