Separate scoped Attempt acceptance from Task completion and let Chief select the next delivery

PROJECT.md

@@ -18,33 +18,17 @@ architecture lives in [docs/architecture.md](docs/architecture.md) and
 Current stage and priorities: [ROADMAP.md](ROADMAP.md). How decisions are made:
 [docs/governance.md](docs/governance.md). Dated decisions: [decisions/](decisions/README.md).
 
-## Runtime and recovery contracts
-
-Earlier implementation checkpoints are [preserved verbatim](docs/history/2026-11-05-controller-exit-memory-checkpoints.md).
-Current resource profile identity, Task-role context, CLI/configuration validation and
-owned pre-spawn reservations remain binding. Unknown worker/preparation exit keeps
-occupancy; dependency readiness and exact-candidate test evidence remain separate.
-Apps require explicit installations and scoped credentials with no Owner fallback;
-SDK candidate/PR adoption, App Review, host merge and Chief acceptance remain distinct.
-Recovery/correction reuses original queues and schedules, preserves drafts and current
-rights, and never chooses automatic business escalation. All canonical subsystem
-contracts remain active. No live task/config/credential change or deployment is implied.
-
-## Established backend foundations
-
-Dated agent-connection, personal-agent and backend-convergence implementation
-checkpoints are [preserved verbatim](docs/history/2026-11-04-agent-foundation-checkpoints.md).
-Current authority, same-principal inbox/receipt, public OpenAPI and native/external
-agent contracts remain in their subsystem pages; source/fixture results do not
-complete live App/provider/release/multi-repository/UI acceptance or authorize deployment.
-
-## Fork Project State — 2026-10-31
-
-Earlier source snapshot/deployment checkpoints are [preserved verbatim](docs/history/2026-11-04-recovery-source-checkpoints.md). Current interfaces follow the README and subsystem contracts. Keep original frontend Task40/PR48 and healthy schedules; this backend work is direct-session source delivery without deployment.
-
-## Historical upstream Project State
-
-Historical upstream mission, named roles and resource inventory are [preserved verbatim](docs/history/2026-11-03-upstream-project-inventory.md). Current fork ownership and capabilities follow the active state and dated decisions above. The governing and automation boundaries below remain active.
+## Current runtime and foundation boundaries
+
+Earlier runtime, foundation and fork references are [preserved verbatim](docs/history/2026-11-05-attempt-settlement-memory-checkpoints.md#earlier-runtime-and-foundation-references).
+Current profile/CLI identity, owned reservations, actual exit/occupancy, dependency
+readiness and exact candidate evidence remain binding. Apps use explicit installations
+and scoped credentials without Owner fallback. Native/external agents share current
+principal/inbox contracts. Recovery preserves drafts, context, rights and original
+queues/schedules; it never selects business escalation. Source/fixture success grants
+no live App/provider/release/multi-repository/UI acceptance or deployment. Preserve
+frontend Task40/PR48 and healthy schedules; current fork decisions govern inherited
+roles and historical inventory. Canonical subsystem contracts remain active.
 
 ## Governing boundaries
 
@@ -89,13 +73,7 @@ Changes to this page, to `ROADMAP.md`, to `docs/governance.md` or to `AGENTS.md`
 decisions, concluded as [docs/governance.md](docs/governance.md) requires and recorded in
 [`decisions/`](decisions/README.md).
 
-M5/M6 and M7 implementation references are [preserved verbatim](docs/history/2026-11-05-review-evidence-memory-checkpoints.md#earlier-project-implementation-references).
-Historical acceptance is not current acceptance. Preserve private credentials,
-current authority/revocation, actual exit proof, independent same-SHA verification
-and unchanged Control Plane reuse; live provider, mixed-resource and deployment
-acceptance remain separate.
-
-Earlier Codex acceptance is [preserved verbatim](docs/history/2026-11-05-warning-memory-checkpoints.md); it grants no new deployment, App or credential authority.
+Earlier implementation evidence links are [preserved verbatim](docs/history/2026-11-05-attempt-settlement-memory-checkpoints.md#earlier-implementation-evidence-links); current rights and live acceptance still need fresh proof.
 
 ### Collaboration contract and earlier validation
 
@@ -115,10 +93,6 @@ or silently retarget recorded execution. Complete role rules and knowledge remai
 available under explicit budgets; release only truly unbound failed preparations.
 Safe-mode proposals require explicit requester approval; watch uses current grants.
 
-Dated candidates, environment probes, schedule observations and historical check
-counts are retained in [the implementation archive](docs/history/2026-11-02-collaboration-implementation.md).
-Their results are not evidence for the current source or Owner visual acceptance.
-
 ### Current UI compatibility requirements
 
 Frontend Task40/PR48 remains its original continuation; backend work does not take
@@ -139,36 +113,17 @@ verified bindings; it is not overall Task acceptance. Resource views retain curr
 and unknown leases while digesting only proven released history. Dated UI drafts,
 asset measurements and test reports remain in [the archive](docs/history/2026-11-02-collaboration-implementation.md).
 
-### Task-scoped SDK context and resident Chief memory — 2026-11-01
-The original implementation checkpoint is [preserved verbatim](docs/history/2026-11-04-context-implementation-checkpoint.md). Current contracts and acceptance follow.
-
-Keep Chief durable memory and one logical Session per Task/role. SDKs retain their
-supported persistence/compaction; FlyBot keeps bounded facts and exact binding/exit
-proof, without a second model-history compactor. Rework resumes original context;
-incompatible binding requires explicit recovery. Native continuation now has actual
-DSH deterministic single-resource return/context coverage. Historical deployment and
-probe details, including their original limitations, remain in
-[execution history](docs/history/2026-11-03-execution-evidence.md#task-scoped-sdk-context-and-resident-chief-memory--2026-11-01).
-
-### Service delivery history
-
-Earlier Task40/service publication evidence is [preserved verbatim](docs/history/2026-11-05-warning-memory-checkpoints.md).
-Preserve frontend Task40/PR48, original UI and healthy execution. Backend work targets
-only the authorized delivery branch, not main, credentials or deployment.
+### Current context and service boundaries
 
-### Role, collaboration and context convergence
-
-Dated #2184/#2175/#2177 implementation checkpoints are [preserved verbatim](docs/history/2026-11-04-role-convergence-checkpoints.md).
-Current contracts remain active: one logical Session per Task/role; pinned persona,
-resource/profile and current delegation; actual exit before restoring context;
-consultation distinct from durable initiative handoff; private user context is not
-published automatically. Memory is bounded guidance, not authority or delivery
-proof. Preserve immutable source/history pages, verified evidence and independent
-acceptance; historical fixtures do not establish live-provider or UI completion.
-See [agents](docs/subsystems/project-agents.md), [Harness](docs/subsystems/project-harness.md)
-and the Project memory/context contracts for the current implementation.
-
-Earlier backend convergence checkpoints are [preserved verbatim](docs/history/2026-11-05-warning-memory-checkpoints.md). Versioned Task/dependency outcomes, transactional facts/Effects, original ACLs and private publication approval remain required; historical deployment is not current acceptance.
+Earlier context/convergence implementation references are [preserved verbatim](docs/history/2026-11-05-attempt-settlement-memory-checkpoints.md).
+Retain one logical Task-role Session, bounded resident Chief memory and Harness-owned
+persistence/compaction; no second history engine. Resource/profile/model/persona,
+current delegation and exact exit/binding proofs constrain continuation. Consultations
+and initiative handoffs stay distinct; private context is not published automatically.
+Task/dependency versions, original ACLs and committed Effects/publication approval
+remain binding. History and memory are not current authorization or delivery proof.
+Preserve frontend Task40/PR48 and original UI; backend source delivery grants no live
+provider/App/release/multi-repository/UI acceptance, credentials or deployment.
 
 ### Current delivery guarantees
 
@@ -187,3 +142,7 @@ Detailed dated implementation checkpoints are [preserved verbatim](docs/history/
 #2518: SDK/inspection/merge elapsed time produces evidence-bearing warnings through one progressive disclosure service. Chief chooses recovery; operational warnings reach existing personal/human inboxes. Unknown exit and current authority remain gates.
 
 #2519: SDK Reviewer receives the complete hash-verified host log inline, without scratch access. Preserve exact candidate/current authority, artifact and execution-context budgets; persist only provenance metadata. Host output is data, never Review or CI approval.
+
+#2526: Chief may accept a merged Attempt scope without closing its Task, then explicitly choose a fresh next delivery. Scoped prechecks are observations; Chief recommends and decides. Personal Agent assistance is the last resort, never a framework-selected escalation.
+
+#2526: same-scope repeated Chief action refusals reuse task-attention warnings and the configured no-progress threshold. Current exact failures reach Chief; changed delivery facts retire the old warning. Warnings never choose roles or escalate to Personal Agent automatically.

ROADMAP.md

@@ -102,3 +102,5 @@ privilege or mission scope and complete no outstanding operational acceptance.
 #2518 unifies warning summaries/topics/evidence and hourly SDK/two-hour merge notices; verify independent Chief operational delivery and explicit stop without Task cancellation. Legacy DAG unchanged.
 
 #2519 removes the host-log scratch dependency through sealed inline evidence. Verify full input, configured context refusal and read-only SDK behavior separately from live OpenToday acceptance.
+
+#2526 separates Attempt settlement, fresh target-based delivery and overall Task closure. Verify commit failure/replay, stale facts, unknown exit, quota admission and Task-role continuity; no automatic Developer or human route.

changelog.d/2526.fixed.md

@@ -0,0 +1 @@
+Chief can accept a merged Attempt without closing its Task, inspect scoped delivery choices and explicitly start a new delivery from verified target history while preserving Task-role context and the old PR record.