Repository navigation
Conversation
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: Queue sources are published after a processing response is reserved, so taking a fresh publication clock can display the source after its receiver. Freeze each source's durable dequeue clock, retain its enqueue lower bound, and carry the latest admitted input time into the response presentation floor. This preserves causal display order without changing storage cursors or legacy replay.
Why: Keep the fork runtime dependency aligned with the self-authored A2A PR so the next operator restart runs the reviewed SDK version rather than stale 0.3.267. Install with development dependencies enabled for a valid production build.
Why: make the documentation-only zts212653#1398 successor an explicit ancestor without replacing the fork active-feature roadmap. All code and dependency blobs remain identical to the independently reviewed 0c2a0e8 candidate. [砚砚/gpt-6.1-sol🐾]
Why: Queue, message bodies, references and member reads must project MessageFrom rather than infer operator identity from an absent catId. Preserve sender envelopes in socket events and reply previews, share display resolution, and keep navigation from declaring custody changes from prose.
Why: a timer callback can arrive while the sampled silence is still below the configured deadline. Re-arm the remaining interval so exact Stop never fires early, while preserving the existing CPU extension cap and once-only result.
Why: grouping still inferred a human sender from absent catId while body visibility consumed MessageFrom. Use the same identity entry point and retain source metadata in the queue preview regression.
Why: late approval reads and secondary chat-cache gaps could erase published cards or hide admitted executions. Fence request order, reconcile on reconnect and terminal events, and preserve canonical sender identity in live cards.
Why: client acceptance completes delivery and retires Queue work. Optional SDK input UUID evidence updates only the original source and target, persists through reload and remains independent of Stop, results and callbacks. Unsupported clients show a static delivered indicator without claiming model reading. Validation: Web 16/16, compiled Queue and SDK 59/59, owned Unix Redis replay and styled browser interactions pass. Full CI and operator acceptance remain separate gates. [砚砚/gpt-6.1-sol🐾]
…vidence Why: notification producers now admit through the durable Queue, and action carrier recovery joins exact source, response, child and parent evidence. Tests must exercise those contracts rather than bare MessageStore delivery or retired custody projections. Install Redis executables for owned isolated Linux tests without relaxing the existing network boundary. Validation: wait lifecycle and outbox 18/18, action lease races 7/7, schedule and task consumers 74/74. Prior CI failures retained; the full public gate remains to run on this candidate. [砚砚/gpt-6.1-sol🐾]
Why: SDK failure correlation UUIDs and synthetic API errors do not prove model consumption. Preserve consumed failed-turn lists and real main-query reply evidence while leaving Queue, Stop and completion independent. Keep absent optional delivery fields absent and construct the browser fixture immutably so current type and production gates can pass.
Why: public recovery wrappers omitted Queue and could pass lookup failures before reaching their intended dependency. Use real Queue and exact History child/parent evidence, retain scope, cancellation, expiry and parallel cases, and assert every injected fault is reached.
Why: Live admission preserves its immediate single-attempt handle. The ordinary active-writer wait loop bypassed the Live retry budget and could acquire another client after refusal. Keep ordinary member recovery while returning the existing typed Live failure without replay.
Why: cloud handoff must bind the current persisted source owner, thread and canonical sender before issuing a return grant or sending to Host. Completed responses enqueue cloud work through the real Queue; missing, deleted or mismatched sources must never reuse a prior human body or acquire return authority.
Why: keep atomic task and private wait receipt hydration together without growing the Redis store or changing its single-read authority. Fresh API build and owned Redis registration/CAS/rejection checks pass; storage and module budgets remain unchanged.
Why: the live replay already derives Queue/History and provider signals. Keeping Supplement and MCP notice certificates misrepresents the measured mechanism. Preserve retained event evidence and readiness checks; verify the generated verdict excludes retired metric identities.
Why: retired inline routing, catId guesses, Queue custody and notice writers prevented old fixtures reaching their intended branches. Keep owner, visibility, cancellation, cross-generation, fault and replay assertions on actual Queue/History/child identities; connector refusals must reach delivery, atomic failure publishes no replacement and lost acknowledgments replay once. Deny inherited runtime Redis and require explicit isolation for optional tests. Original 37-file failures are retained; current 438 checks pass with unchanged input hashes, plus focused recovery and owned Redis controls.
Why: the complete public gate reproduced cancellation before the fake gh installed its signal handler. Drive the real scheduler timeout only after readiness and hold the real child until an explicit release, preserving gate ownership and process-close assertions without depending on startup speed. Validation: original full public gate 27406 pass, one startup race, 112 skipped; retained original red and diagnostic timing probes. Corrected cleanup tests 2/2 and preflighted cleanup/request/batch/admission consumers 14/14. Full public rerun remains required. Author: 砚砚/gpt-6.1-sol
…eptance Why: deliver latest public main and the complete A2A lifecycle through the existing fork acceptance branch while retaining fork coordination records. Public candidate has independent review and a complete canonical public API pass; runtime, human acceptance and soak remain separate.
Why: owner Queue updates and cancellation share the HTTP session identity, but sockets were hardcoded to default-user. Resolve the existing session cookie on connection without trusting client auth metadata or promoting anonymous and remote unpaired clients.
Why: HTTP and Socket must share the existing validated owner principal so user-scoped Queue updates reach the complete page. Include the exact independently approved public successor without changing runtime or merging develop_base.
Why: approval events and reconnects can arrive while a pre-change GET is active. Request version fencing alone still shares that stale physical read. Use the API client's bounded trailing generation for pending and settled refreshes, and verify the real coordinator preserves fresh results after overlap and failures.
Why: the decision sessions consumer must ask for a fresh approval owner read after a write. Preserve its unified-read assertion while verifying the coordinator option that prevents an older active GET from satisfying that refresh.
Why: approval events and reconnects can arrive while a pre-change GET is active. Request version fencing alone still shares that stale physical read. Use the API client's bounded trailing generation for pending and settled refreshes, and verify the real coordinator preserves fresh results after overlap and failures.
Why: the decision sessions consumer must ask for a fresh approval owner read after a write. Preserve its unified-read assertion while verifying the coordinator option that prevents an older active GET from satisfying that refresh.
…ation/a2a-1398-fork-acceptance
Why: API restart invalidates its session map, while Socket authority is fixed at handshake. Automatic transport reconnection could enter default-user before HTTP recovery and leave owner approval and Stop projections disconnected. Gate every physical connection on a shared fresh cookie read, preserving bounded retry and retired-surface fences.
Why: AppShell must mock the added session refresh contract, and the real Socket integration must observe disconnect before waking the existing visibility recovery path instead of assuming manager retries.
This was referenced Oct 9, 2026
mindfn
changed the title
Owner
Author
|
Closing with operator authorization after #217 merged at d015c80. #217 uses the original feat/F117-1354-message-delivery-lifecycle source branch and replaces this integration draft. Runtime checkout has been updated, and the operator reports restart complete. Branch and historical review/acceptance evidence are retained; no merge of this superseded PR is needed. |
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.
Superseded by #217. Use #217 for fork acceptance and merge preparation.
The operator requested the original
mindfn:feat/F117-1354-message-delivery-lifecyclesource branch instead ofintegration/a2a-1398-fork-acceptance. GitHub cannot change an existing PR's head branch, so #217 carries that correction without creating another code branch.#217 head is
028a63af71bc3ae6f9ebf9fcf8bd542c0e02d40b, exactly the head of upstream zts212653#1398. Both fork PRs targetdevelop_baseat3e70e1d6805be24672e8f841861f180d20b184c2. This PR's integration head00a513906e2a30248e603b9fe079c9643e2cfcd1differs only in 11 documentation/evidence paths; code, dependencies, tests and workflows are identical.Existing independent review, full test and isolated page evidence remain applicable within their recorded scope and are summarized in #217. Per operator direction, duplicate fork CI is not required and supplementary real-Claude Stop verification after quota failure is not a delivery prerequisite. Operator experience and fork soak remain open.
This PR remains an archival draft, not the active delivery candidate. Do not merge it. No runtime checkout, configuration, data or process was changed by this source-branch correction. Guard maintenance #215 is separate and is not an acceptance prerequisite.