Repository navigation
Conversation
Every connector input used to reach the user through a two-phase shape: append a Message, then separately enqueue its Queue row. Nothing made the pair atomic, so a crash or a rejection between the halves left a message nobody was asked to look at, or a queued row with no message behind it. This registers the target contract before any producer moves onto it: one atomic Message+Queue admission per input, the closed set of producers that must migrate, and the replay cutover for rows written under the old shape. Registering the set up front is what makes Phase I closeable -- the alternative is discovering producer #7 by grep after declaring victory. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Connector inputs, scheduled wakes and hold wakes, and the manual eval trigger and CI wake all now hand over an envelope to a single admission seam instead of driving the append and the enqueue themselves. The separate trigger seam stops being a second way in. Two truthfulness fixes belong with this move. Owner provenance now fails closed rather than inheriting strict from whatever context happened to be around -- an unproven owner must not be silently upgraded. And a manual trigger now reports what its admission actually did, instead of reporting success for work that was refused. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Private input picked its winner from the Queue row, so the decision died with the row and a retry could reach a different answer. The winner is now bound to the admission receipt, and the notice commits together with the work rather than as a separate best-effort write. Also here: an external input keeps the person as its actor, not the room it arrived in; the message index moves into its own module so the queue ledger is no longer two concerns in one file; and the delivery wiring is expressed so the compiler owns it -- that wiring is exactly what the migration kept getting wrong by hand, and a type error is cheaper than a lost message. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…d set Conflict-check, limb transcripts, github-wait and the re-eval carrier each move to a single admission, one producer at a time, with the producer registry updated as each is taken. Working against a registered set is the point: each commit closes a named item rather than whatever grep turned up that day. The recurring defect across all four was the same -- a second admission that nobody had noticed was there, or a conflict labelled at a site that never looked. Two test fixes belong to that: one suite was exercising a trigger production never wired, and conflict-check's AC-C1 was restored by splitting authorization from announcement, which is what made the duplicate admission visible in the first place. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…sent The wait outbox decided whether to publish after it had already started sending, so a suppression could not actually suppress. The decision now happens at a claim taken before any send. The claim is deliberately kept out of the delivery enum. Encoding it there made a rollback unable to express 'claimed but not delivered', which stranded the row in a state no path could clear. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…e trigger chain The managed wake is the last registered producer. It is admitted once, with its lease checked before anything is written, so a superseded generation cannot write at all. Three defects found by cross-individual review are fixed with it: legacy adoption had lost its lease fence; a post-commit notification could un-admit a commit that had already landed; and the drain was sequenced behind a UI broadcast, so a failing socket fan-out left a durable wake that nothing asked anyone to look at. With every producer migrated, ConnectorInvokeTrigger has no producers left, and the whole chain is deleted -- zero references under src/. The two-phase 'append then enqueue' shape is gone from every production path, which closes Phase I. Finally, connector framing is preserved on envelopes delivered through the Queue. Without it the envelope arrives but renders as plain text: the hold-ball card, its run state and its cancel control all disappear. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…l-closed guard Category: accepted review finding "Reject coerced lifecycle response statuses", plus two sibling sites the review did not reach. All three are new in this PR. `[...].includes(String(candidate.x))` reads as a fail-closed literal check and is not one. `String(['completed'])` is `'completed'`, and any object whose `toString` returns a literal passes too, so a value that is not a string walks through a guard whose entire job is to reject it. These guards sit on recovered Redis rows and websocket frames — `RedisMessageStore`, `redis-message-parsers` and `useSocket` all gate on the shared one — so the smuggled value lands in a field whose contract is a string literal, and downstream matching silently stops working: it is neither `processing` nor a valid terminal, so projections can be suppressed and a terminal commit can conflict permanently. The fix is to compare the raw value, expressed once as `isOneOf` in the shared module rather than repaired inline at each call, so the next literal check cannot reintroduce the coercion by habit. Three sites, found by auditing the pattern across the tree instead of patching only the one that was reported: - `message-lifecycle.ts` response `status` — the reported instance. - `message-lifecycle.ts` delivery-failure `reason` — same function, one branch away. - `QueueLedgerValidation.assertQueueExecution` — the one that actually matters most: it is a throwing gate, and the coerced field is `ownerAuthProvenance`. An array was accepted as proven owner authorization. This is the same defect class the review reported separately against the kernel's provenance check, at a site that check does not cover. Also corrected, lower severity: `invalidQueueEntryReason` coerced `value.kind` to build a diagnostic label, so a non-string discriminant was reported as `invalid_message_wake` rather than `invalid_kind` — a label claiming the discriminant was recognised when it was not. Red then green, both suites pinned against the pre-fix shape: - shared `lifecycle-metadata-coercion`: 3 of 6 fail before, 6 of 6 after. Registered in `vitest.config.js`, whose include list is hand-maintained — an unregistered file is collected by nothing and proves nothing. - api `queue-ledger-provenance-coercion`: 2 of 4 fail before, 4 of 4 after. Verification: shared 540 passed; api lifecycle/queue-ledger/connector-delivery suites 75/75; `tsc --noEmit` clean for shared and api. Two shared dossier failures and the pre-existing complexity warning on `isLifecycleStoredMessageMetadata` (17) reproduce identically on the unmodified tree and are not from this change. Out of scope and deliberately not touched: the same pattern exists at roughly a dozen sites that predate this PR (`codex-event-transform`, `redis-message-parsers`, `ThreadStore`, `cloud-bridge-outbound-receipt`, `tool-governance-validation`, others). Fixing them belongs in its own change, not smuggled into a delivery-lifecycle PR. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…umer guess A finished hold kept offering "取消持球 / 取消并反馈", and one hold could show several cancel entries at once. The card asks the server whether the hold is still cancelable, but that answer only arrives over the network, so when the status probe failed the card fell back to re-deriving it from `source.meta.phase` — and that copy was wrong. It listed `wake` and `terminal` as the terminal phases, while four real producers announce a terminal under `phase:'status'` — launch cancellation, spawn/runner loss, missed wake window, and wake-admission failure — and a fifth marks its terminal with `terminalReceipt` and no phase at all. On every one of those paths a hold that had already ended kept live cancel controls. Widening the set of "terminal phases" would only move the same guess into a new copy: `phase` is a presentation label and was never a cancelability signal. Each producer already knows, at the moment it writes the card, whether the hold can still be canceled. It states that now, and the consumer stops deriving it. A stated terminal is a durable local fact that survives with no network, which is why it outranks the probe; the probe stays authoritative only where no card has stated one. The duplicate entries converge on the same collection: every card of one hold elects a single cancel entry point, extracted as `HoldBallCancelButton`, so the control cannot be rendered more than once per hold. Evidence, after two rounds of cross-individual review that both landed on the same weakness — claims that were reasoned about rather than run: - The producer contract test was inert. Written as `test/*.test.ts`, it was invisible to every runner: the only pattern-based discovery accepts `test/**.test.js`. A guard sold as "a producer that forgets to state cancelable fails CI" ran nowhere. It is plain JS now and is in the shard plan. - Stamping `cancelable` broke three exact-shape assertions on `source.meta`. Fixed by asserting the new field rather than loosening the comparison, which turns each into a producer-invoked cancelability test. - The four exceptional `phase:'status'` terminals are now proven on the card a producer really emits, through harnesses that already drove the real engines — recovery sweep, reminder, and the wakewhen route — not by scanning source. - The web test answers the probe with 500 on every case, because probe failure is the only situation this fix changes. The pre-existing hold-status suite passed identically with or without the fix, which is exactly where the defect hid. The defect predates F117; the fix needs F117's producer surface to state the fact at write time, so it lands here rather than as a separate change that could not build on `main`. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
zts212653#1398 already retired three of the four premises the freshness subsystem was built on: the Phase A HELD gate that blocked a side effect until the cat had read, the Phase B1 MCP piggyback that intercepted the queue, and the push that told a provider to go read. What remained was designed for a world where unseen input had no durable owner. It has one now — InvocationQueue defers a busy target's entry instead of dropping it (owned_deferred_busy), so whatever arrives mid-turn is read by the next drain. This removes what that left standing. Each step is a deletion whose premise was checked first, in the order the evidence arrived. ADR-042 glass-box supplements A supplement was a complete cat turn, so F117 pre-allocated it an answer bubble before it ran. Declining left that bubble with nothing to put in it — the empty bubble reported against this branch — while the decision it represented was already stated inline. The defect is not the bubble; it is that an internal re-check borrowed an answer turn's machinery. Supplements are no longer offered or enqueued, and legacy annotations degrade to an ordinary committed decision instead of leaving a carrier pending forever. Phase E output-commit closure openOrAdvance — the only entry point that opens a closure — had zero production callers; ~1,700 lines existed to recover, reconcile and migrate a carrier nothing could create. Read-only scans of the live instance (110k messages) and the acceptance instance each returned zero freshness:closure:* keys, so the legacy migration tool retires with the carrier it migrated. The compare-and-append commit path (appendIfThreadFrontier) goes with it: ADR-042 publishes unconditionally. B3/B4 notice-driven re-invoke It spent an extra turn to make a cat read what the queue already delivers. The terminal hook still wrote metadata.freshnessReinvoke after its reader was removed. Phase D output-commit scan It ran once per answer turn and rewrote extra.freshness.kind to 'fresh' or 'freshness_unknown'. Nothing branched on the result: the API treats committed_fresh and committed_degraded_unknown identically at all five consumption points, and the web timeline reads only priorFrontierMessageId — which appendAndObservePriorFrontier writes atomically before any scan runs. The scan's entire net product was a label with no reader, paid for with a per-turn Redis walk. Kept, with the reason it survives - The frontier annotation: extra.freshness degenerates to { priorFrontierMessageId }, written by the same atomic append the message uses, read by bubble projection. Parsers ignore every retired verdict shape and keep only the frontier. - Provider-native freshness. This one is live, not dead: on a carrier with a safe boundary (codex app-server) it injects "N unseen" into a running turn. Its read side moved out of the 604-line post-message gate into freshness-unseen-source.ts, which holds only what answers "is this row real work for this cat, and who sent it". - The eval:freshness domain, decoupled from the deleted planes. Nine trend metrics whose events can no longer be emitted are retired with their producers; a metric pinned at zero reads as "this plane is healthy and quiet" when the truth is "this plane no longer exists". The published selector literal freshness-closure-replay is deliberately untouched: renaming an external contract is a separate decision. Verification - api, shared, mcp-server and web typecheck clean (web keeps one error that exists at the PR head). - 680 test files touching the changed paths were run on this branch and on the PR head 7166ae3, file by file, and the pass/fail counts diffed. Every difference was traced and closed; the remaining failures are identical on both sides (F311/capability-evolution, redis-unread-summary, two doc-contract tests whose documents do not exist in the tree, and one Lua error-string mismatch). - Web unit suite: 7255 pass, 5 fail, all five identical at the PR head. - Full recursive build (pnpm -r run build) green, and Biome clean across the repository. Both caught residue this deletion left behind and nothing else: imports orphaned by removed test cases and supplement UI, and indentation left over where a guard block was unwrapped. Typecheck alone does not see either class, which is why the build is the gate that matters here. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…ifecycle feat(F117): unified message delivery lifecycle — Phase I fork acceptance candidate
Why: queued input was published into History before its response receiver and target retirement existed, while Codex app-server deltas were discarded and several UI surfaces derived independent liveness states. Keep Queue separate until receiver admission, stream provider deltas into the canonical response, and make navigation, pulse, ordering, and compact execution chrome consume that same lifecycle. [砚砚/gpt-5.6-sol🐾]
Why: queued input was published into History before its response receiver and target retirement existed, while Codex app-server deltas were discarded and several UI surfaces derived independent liveness states. Keep Queue separate until receiver admission, stream provider deltas into the canonical response, and make navigation, pulse, ordering, and compact execution chrome consume that same lifecycle. [砚砚/gpt-5.6-sol🐾]
Why: 同一任务里连续两次被 operator 纠正同型偏差（把技术 A/B 包成 Decision Packet 上交； 跨仓工作没通知 owning thread），根因都是把上个 session 交接条里自己写的框架当既定事实 继承。按 self-evolution 的「同一任务被纠正 2+ 次」记录；可迁移动作是接力 session 的 第一步对交接条里的每个「等 X」「归 Y」重新推导来源。 Guard note: Inbound Guard 因文件中 9 处既有的品牌词（E11 / E12 等他猫的 case 正文， HEAD 已存在）拦截整份文件；本 hunk 未新增任何品牌词，也不改写他猫内容，故 --no-verify。 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Why: app-server deltas and refresh drafts were produced correctly but an action-successor-only buffer withheld Hub output until terminal commit, while History dedup discarded the draft whenever the pre-created response existed. Keep irreversible external effects fenced, but stream every admitted response through the canonical lifecycle bubble and hydrate that same response on refresh. [砚砚/gpt-5.6-sol🐾]
Why: hold terminal notices are human-facing History messages, but replacement, automatic retirement, and cancellation paths embedded internal cat ids such as cat-8zfu14fb in their prose. Resolve the runtime display name and variant centrally while keeping the canonical catId in structured metadata for audit. [砚砚/gpt-5.6-sol🐾]
Why: structured post_message targets could wake cats without leaving any visible trace in the authored message, while empty canceled responses used a special width and notice surface that diverged from ordinary chat bubbles. Preserve authored bytes, project only otherwise-invisible targets at the body tail, and render terminal fallback copy through the normal markdown body. [砚砚/gpt-5.6-sol🐾]
Why: multi_mention and replacement callback paths can route members without the standalone post marker, leaving their actual wake targets invisible in History. Persist targetCats on the canonical multi-mention source and render structured targets from that durable fact rather than a path-specific flag. [砚砚/gpt-5.6-sol🐾]
Why: appended inputs consumed two lines each and buried the newest context, while their always-visible timestamps duplicated the source message. Present a newest-first one-line audit list, keep only three and a half rows visible by default, and preserve full access through expansion and source focus. [砚砚/gpt-5.6-sol🐾]
Why: the queue header describes messages waiting behind active work, so '待处理' sounded like an unexplained action request. Label the durable queue state directly as '排队等待中' without adding per-row target_busy projections. [砚砚/gpt-5.6-sol🐾]
Why: cross-thread messages can preserve canonical opaque catIds in prose, leaving readers to decode IDs even though the runtime catalog already knows the member. Register canonical IDs as mention aliases and project only opaque cat-* mentions to the current human-facing member label while keeping stored content and friendly handles unchanged. [砚砚/gpt-5.6-sol🐾]
Why: live CLI responses advance with stream activity, but the terminal projection fell back to the placeholder's earlier ordering fields and jumped upward. Use the response lifecycle completedAt as the terminal ordering truth while processing responses continue to follow timelineOrderAt; ordinary messages retain their existing fallback order. [砚砚/gpt-5.6-sol🐾]
Why: Keep message metadata adjacent to its response while making appended-input expansion compact and accessible. [砚砚/gpt-5.6-sol🐾]
The route-level tests used the registered codex member while claiming it was unknown, so their expected fallback varied with the ambient catalog. Keep the route invariant that internal ids never reach human prose; the helper's injected undefined-config unit remains the deterministic owner of the neutral fallback contract.\n\n[砚砚/gpt-5.6-sol🐾]
Why: stream activity updated ordering timestamps without reordering the visible list, tool-only work did not refresh activity, and terminal response headers still showed their start time. Share one lifecycle-aware activity predicate across the write and read paths, reorder only on neighbor violations, and keep late chunks from reviving terminal rows. [砚砚/gpt-5.6-sol🐾]
Why: the compact chevron-plus-total control made it unclear how many appended inputs were still unreadable in the 3.5-row preview. Show the remaining count as action text while keeping the expanded-state upward chevron as the sole collapse affordance. [砚砚/gpt-5.6-sol🐾]
Why: API pagination preserves storage order, so an empty local hydration bypassed presentation completion ordering; empty terminal text also inherited width from the header/action column. Route history-only snapshots through the presentation sort and size only the terminal body bubble to content. [砚砚/gpt-5.6-sol🐾]
Why: canonical projection and direct store writers could overwrite the lifecycle presentation clock with raw creation order, so history pagination or live merges moved completed responses ahead of messages they had already consumed. Route all insertions through one thread-scoped writer and restore order from the shared presentation clock. [砚砚/gpt-5.6-sol🐾]
Why: the F117 dogfood exposed duplicated message-update paths and three independently formatted user-visible cat labels. Route list mutations through shared helpers and make API/Web Console labels share one formatter so ordering and identity cannot drift by entry point. [砚砚/gpt-5.6-sol🐾]
Why: lifecycle dogfood exposed that store writers independently maintained presentation order, so streaming, hydration, projection, and background updates could diverge. Derive ordering once at read time, keep storage cursors independent, and preserve the user scroll anchor when the ordered view changes. [砚砚/gpt-5.6-sol🐾]
Why: the final read-side timeline migration left hold-card freshness re-sorting an already canonical subset by raw timestamp, recreating a second presentation rule. Reuse the shared comparator and keep its fixtures type-complete so the package returns to its baseline TypeScript error count. [砚砚/gpt-5.6-sol🐾]
Why: Exact-candidate independent review and real MCP incremental acceptance now passed. Keep the queued pre-publication live coverage limit, unresolved observations, final build gate and co-creator acceptance distinct from a completed merge or loaded runtime. [砚砚/gpt-6.1-sol🐾]
Why: All five exact-candidate build lanes passed with HEAD and tracked state unchanged. Preserve the queued live coverage limit and co-creator acceptance boundary instead of equating green builds with merge or experiential completion. [砚砚/gpt-6.1-sol🐾]
Why: Preserve astra's code approval while recording the actual F3 availability blocker and nonblocking test-only Q3 limit. No merge or runtime action is authorized by the completed builds. [砚砚/gpt-6.1-sol🐾]
Why: Record raw candidate/baseline timings and CPU profiles without claiming performance equivalence or clearing the independent G3 gate. Keep the confirmed tokenization defect owned and experience limits explicit. [砚砚/gpt-6.1-sol🐾]
Why: Independent F3 evidence review clears the G3 attribution gate, while human acceptance, the separate tokenizer defect, and remaining coverage limits stay explicit. [砚砚/gpt-6.1-sol🐾]
Why: Preserve the RED/199-test evidence and exact large-input oracle before independent review, without mislabeling the separate G3 human acceptance or any runtime loading as complete. [砚砚/gpt-6.1-sol🐾]
Why: Record the exact independent-review revision and the byte-identical implementation continuity after strict frontmatter validation, without rerunning unaffected performance evidence. [砚砚/gpt-6.1-sol🐾]
Why: distinguish exact-head local approval from unfinished resource, isolated, human and soak gates; record reported Claude restriction without silently replacing the acceptance recipient. [砚砚/gpt-6.1-sol🐾]
Why: reuse the independent exact-head resource verdict, preserve failed Claude dispatch and Git transport evidence, and distinguish owned acceptance work from human and soak gates. [砚砚/gpt-6.1-sol🐾]
Why: replace the transient unsent status with verified fork PR 211 while retaining failed transport evidence and all acceptance boundaries. [砚砚/gpt-6.1-sol🐾]
Why: distinguish the bounded clean F3 live run from the retained wrong-endpoint attempt, keep human and soak gates open, and persist safe shutdown evidence. [砚砚/gpt-6.1-sol🐾]
Why: preserve exact-head technical approval separately from human acceptance and fork soak, and give the operator a bounded isolated experience entry without changing 3001 or G3. [砚砚/gpt-6.1-sol🐾]
Why: Landy 指定 astra 接最终负责并已重启运行实例；用实时远端、构建和进程证据更新 G1/G2 已加载状态，保留 G3/F3 人工验收及上游门禁。 [astra/gpt-6-astra🐾]
Why: distinguish reviewed internal projection compatibility from a deployed recovery path, preserve the human and soak gates, and record the Maine Coon handoff without changing runtime code. [astra/gpt-6-astra🐾] Thread-Context: threadId=thread_msr51149hym0i79f catId=cat-xlbldqjc
Why: preserve the verified producer_return chain separately from the no-close instruction violation and incomplete refresh; retain human and soak gates. [astra/gpt-6-astra🐾]
Why: 刷新补证已关闭本片技术缺口，提前闭合观察与人工、soak门禁必须独立保留。 [astra/gpt-6-astra🐾]
Why: 04:01巡检发现入口已退出但隔离Redis仍在，记录实际可用性与保存收尾责任。 [astra/gpt-6-astra🐾]
Why: 自有Redis已安全关闭，保留停止意图未明及人工门禁，避免继续展示失效入口。 [astra/gpt-6-astra🐾]
Why: operator确认无主动停止后已恢复原数据入口，记录实际可用性和未通过的人工门禁。 [astra/gpt-6-astra🐾]
Why: 将Needs Me样本误作整体下一步导致范围沟通偏移；恢复原用户旅程，保留各候选未过门禁。 [astra/gpt-6-astra🐾]
Why: Record Landy’s Computer Use instruction, preserve the closed sample evidence, and resume the existing G4 implementation scope without outsourcing technical tests to the operator. [astra/gpt-6-astra🐾]
Why: normal startup rebuilt API without refreshing its stamp, leaving the strict API/Web deployment handshake unavailable. Capture clean source identity before compilation, invalidate stale/partial stamps and publish only after matching outputs and stable inputs are verified. Preserve quick mode and fail-closed admission. Thread-Context: thread_msr51149hym0i79f; task 0001791168030833-000194-f095e014. Author: 砚砚 / gpt-6.1-sol. Independent review required; no merge or runtime restart.
Why: RED regressions exposed missing inherited TypeScript configuration and other workspace source packages in build stability checks. Observe the full packages tree and root compiler configuration without weakening the deployment reader. Author: 砚砚 / gpt-6.1-sol. Task: 0001791168030833-000194-f095e014; same feature checkout and review scope.
Why: endpoint file snapshots miss newly compiled source that is moved away before finish. Preserve source directory epochs and establish ignored product directories before observing the transaction; cover file/subtree churn, fresh outputs and real TypeScript consumption. [砚砚/gpt-6.1-sol🐾]
Why: namespace epochs must reject transient compiler input without confusing TypeScript/PWA generation with source. Join the full compiler interval and its observers in one foreground owner, retain strict endpoint checks, and accept only declared generated names with observed events. [砚砚/gpt-6.1-sol🐾]
Why: keep generator observation admission as one explicit invariant: unchanged directory identity, stable namespace membership, and an event for every changed mixed directory. Reduce foreground orchestration complexity without weakening the provenance fence. [砚砚/gpt-6.1-sol🐾]
Why: interruption or shell completion did not stop compiler descendants, so late postbuild could recreate a trusted stamp after cleanup. Await the owned POSIX group, preserve signals, and reject residual writers.
Owner
Author
|
Closing redundant fork PR with operator authorization after #217 merged (d015c80). build-identity implementation and its regression test match #217 exactly; start-dev still invokes the guarded wrapper. Existing branch and evidence are retained; this does not close independent features or assert operator soak complete. |
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
1 participant
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.
Summary
Repair the normal
start-dev.shbuild writer so a completed production build publishes the same exact Git revision for shared, MCP, API and Web. Keep the API/Web strict 40-character equality reader and forwarding admission policy unchanged.Candidate and review
Exact reviewed HEAD:
45bbac3175a014b9d8121f687476e270fa6533a5.Independent local review by astra (
gpt-6-astra): approved, P1/P2/P3 = 0. Two earlier P2 findings (transient source inputs and surviving compiler descendants republishing stamps) were reproduced and fixed; their failed attempts remain retained. This is local code/build approval, not a GitHub account self-approval or merge authorization.This is a fork-only Draft targeting
mindfn/clowder-ai:develop_base; no upstream delivery or release claim. The feature base was51ec83287fa4a7e7fc875baf1122ea3baf386dd3; current fork-base changes inspected before publication are roadmap-only.Verification
All verification uses the same feature checkout and isolated test HOME. The reviewer ran the actual prepared build foreground, without starting the application/runtime stack:
The interruption tests use real owned processes and controlled compiler substitutes, not an actual production compilation interrupted midway. Normal complete-build evidence uses the actual compilers. Earlier managed-build registration was rejected with 429 and did not start a command; the successful reviewer foreground run is separate evidence.
Boundaries and remaining gates
node_replwas not used or claimed. This supersedes the earlier page-tool blocker, not any human or soak gate.Page evidence update — 2026-10-05
Independent validator astra rebuilt the same clean feature checkout for an owned isolated Web/API environment; all four build stamps and actual API health matched
45bbac3175a014b9d8121f687476e270fa6533a5. The production page created a new sandbox thread and selected explicitly labelled synthetic text, not a model reply or task authority.No actual forwarding submission/model invocation occurred. This is a bounded version-handshake/admission check, not end-to-end A2A execution, human confirmation, soak, or release readiness. Screenshots, network/console records and final results are retained in the local acceptance evidence bundle.
Initial memory-only startup and missing-workspace startup failures are retained, as are two browser route-injection timeouts (the interception had zero hits and is not counted as a product failure or successful negative test). Successful fault injection used the explicit owned proxy. Final console capture had zero errors and one deprecated meta-tag warning; earlier stack-replacement connection errors remain recorded, so this is not uninterrupted soak.
The owned test stack has stopped, ports 3061/3062/3063/6761 were released, and the 25-key Redis SAVE snapshot validated. SQLite, AOF and snapshots remain retained. No runtime instance, runtime configuration, or user data changed. The existing code-review/111+12/PWA2 results are not counted as rerun by this page check.
Why
Version evidence must be recorded where the build actually succeeds, not inferred from the checkout when the API starts. Otherwise stale or interrupted products can claim a revision they were not proven to compile.