Repository navigation
Conversation
This was referenced Nov 2, 2026
github-actions
Bot
added
the
risk:T3
Keep Chief proposals separate from Maintainer and Owner approval. Preserve retired role context and room history without reassigning existing Tasks or inferring worker exit.
Keep exact latest Task-role native bindings and context parts, refuse unknown exit and missing handles, and use committed role catalogs when pinning execution rights. Preserve original Workflow lifecycle and legacy DAG workspace behavior.
Keep logical identity separate from artifact responsibility and SDK read-only policy. Preserve retired active claims while blocking new work until Chief selects an active target.
Preserve structured handoff identity through native delivery and restore archived context only after committed activation. Guard the actual DSH single-resource return path and keep historical implementation evidence outside the bounded active policy.
Collaborator
Author
|
Written-by: Codex Merged current #2184 execution/governance into the original branch. Current composition: 123 targeted tests + core lint passed; current full verify NOT rerun. Added red/green regression for role retirement during source-exit inspection, revalidating the committed target before claiming. Original consultation/handoff semantics, pinned role context and shared exit proof are preserved. Current head: 36210b9. Remaining composed-stack validation stays tracked under the original issue/PR. No main merge/deployment/control-plane/frontend changes. |
This was referenced Nov 3, 2026
Base automatically changed from
feat/2184-execution-lifecycle
to
delivery/ai-centric-development-service
November 3, 2026 09:11
Collaborator
Author
zy95-12
marked this pull request as ready for review
November 3, 2026 09:13
Collaborator
Author
|
修复验证更新：仅归档 M7 checkpoint 后预算仍超限，因此也提前带入 #2225 中已有的 S1–S6 历史原文归档。当前 SHA |
zy95-12
merged commit Nov 3, 2026
5b63d50
into
delivery/ai-centric-development-service
3 of 5 checks passed
zy95-12
added a commit
that referenced
this pull request
Nov 3, 2026
…mmaries (#2225) Written-by: Codex Latest composition at c16a25e: Merged current #2175/#2184 into the original branch. Current composition: 130 initial targeted tests; after integration fixes,33 policy-budget/harness checks, core lint and actual DSH native return probe pass. Current full verify NOT rerun. Actual runtime reproduced logical Bot vs physical worker conflation in input budget fencing; regression/fix retained. Complete mandatory rules remain under the unchanged384k cap after completed service narratives are archived verbatim behind active memory links. No instruction source removal or silent truncation. Prior full-check counts below belong to their explicitly named older heads, not this updated tip. Still Draft; composed Task/state/API acceptance remains in progress. No deployment, merge or independent Review. Refs #2177; stacked on #2210. Current head: 4101275. Bound Project/Chief/Task-role context through model/Harness budgets, full-input checks and scoped source pages with hashes/cursors. Reuse existing memory, archives, participation and Task-role Session records for relevant retrieval, versioned working summaries, bounded history views and unverified execution experience. Failed consolidation preserves the last valid summary; model experience cannot overwrite human-controlled facts or role policy. Structured native handoff input is JSON and passes current claim/resource/input-authority checks. Codex has a host-selected tool history output cap while SDK compaction defaults remain runtime-managed. Sequential native Chief intake testing in dependent #2179 exposed a real stale-context problem: changing Bot system-prompt metadata did not guarantee an already resident Session received current job facts. This PR now delivers the current protocol and scoped facts in the actual turn input, checks its complete budget, revalidates actor/delegation before dispatch, and restores only its own prompt metadata. The same resident Session remains in use. A baseline-red/two-job regression protects this behavior; no fresh Session hides the failure. Validation at current head: full `TZ=UTC npm run verify` passed **4560 tests, 0 failures, 0 skips**, including four actual DSH runtime checks with deterministic inference. Agent suite43/43. Before the native follow-up, selected context/delivery/pool/Harness suites176/176 and the four unchanged context modules measured100% line coverage, branch73.47–91.54%; not complete branch coverage. Updated architecture/subsystem docs, PROJECT/ROADMAP/LESSONS, changelog and generated patches. Separately, actual Codex gpt-6.1-sol validation used the existing operator profile and runtime source a9ff63b: two fresh workers fixed fixture code, passed independent host tests, resumed the identical backend Session after a changed caller prompt, read their own work summary and recovered a conversation-only marker absent from repository files. Both confirmed stop/exit before release;9 checks passed. That proof names its source revision; it is not a new current-head full Chief/pool workflow, observed SDK compaction event, actual provider-window measurement or native Task-role physical restoration. Remaining acceptance: native physical restoration #2184, storage normalization #2182, public protocol integration #2185 and full task-flow acceptance in #2179. Unknown capacity remains explicit. No production deploy/restart, control-plane/UI edits or frontend task interruption. Draft; author self-review is not an independent Reviewer PASS. README rewrite remains last in #2189.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Written-by: Codex
Latest composition at 36210b9: Merged current #2184 execution/governance into the original branch. Current composition: 123 targeted tests + core lint passed; current full verify NOT rerun. Added red/green regression for role retirement during source-exit inspection, revalidating the committed target before claiming. Original consultation/handoff semantics, pinned role context and shared exit proof are preserved. Prior full-check counts below belong to their explicitly named older heads, not this updated tip. Still Draft; composed Task/state/API acceptance remains in progress. No deployment, merge or independent Review.
Expose scoped handoff get/list views over the original Task collaboration history, with acceptance receipts, source/target context references, actual worker binding, initiative fences and predecessor/successor links. Trusted offer/accept ports reuse existing pools; replay cannot reactivate completed execution. A Chief reroute cannot bypass an earlier writer whose exit remains unknown.
Ordinary consultation is a separate private protocol with native/v1 ask/get/list/reply APIs. Keep legacy conversation-handoff records and Chief-question alias readable. Chief first contacts the initiating user's active personal agent; safe answers remain private until user publication, while watch replies use current original delegation and Task inbox/Effects. Notifications run after commit, cancel ended questions and defer busy native watches. External agents have isolated mailboxes without a native personal Bot or invented provider transport.
Refs #2175; stacked on #2208. Architecture/subsystem docs, long-term project memory, changelog and canonical source mirrors included. This Draft keeps native Task-role restoration and real long-task/provider acceptance on #2184/#2177; transactional storage #2182, public events/provenance #2185 and role governance #2171 remain integration dependencies. Do not close these issues from the scoped foundation.
Validation at439a41c0ede34f4be08b96bac0500c7c71d6d298:
-168 selected tests passed under coverage. Includes actual channel HTTP safe/watch/private-scope checks, lost accept-response replay, source-exit fence, legacy queries, no Task creation for ordinary questions, postcommit notification and busy/cancel cases. Initial pool/consultation tests failed on missing APIs at the parent.
Not run: new real Codex/Claude task, official grok/dots provider integration, browser/deployment or frontend changes. Safe/external mailboxes require their clients; send/dispatch is not a read/handling receipt. Generic public input provenance is completed with #2185. README/API rewrite remains last in #2189.