fix: repair issue 3670 current-dev regressions

[Yeachan-Heo]

Summary

• suppress staged async completion after poll acknowledgement using generation-aware stale filtering
• freeze detached fork-context seeds across allocated and caller task identities
• refresh deterministic Anthropic cache evidence with exact source blob/SHA provenance

Verification

• bun test packages/coding-agent/test/async-yield-queue.test.ts packages/coding-agent/test/session/yield-queue.test.ts packages/coding-agent/test/task-fork-context.test.ts packages/coding-agent/test/task/fork-context-advisory.test.ts packages/coding-agent/test/task/fork-context-seed.test.ts packages/ai/test/anthropic-cache-eval.integration.test.ts packages/ai/test/anthropic-cache.test.ts (77 pass)
• bun --cwd=packages/coding-agent run check:types
• bun --cwd=packages/ai run check:types

Scope

• Separate atomic commits per subsystem.
• Codex SSE invalid_request_error bypasses named tool-choice fallback #3669 remains separate and later.
• No changes to fix(session): complete descriptor-bound cleanup and live migration leases #3596/fix(tui): repair reentrant SDK callbacks and pipeline ownership #3665/Repair Windows chat ownership settlement and integrate guard reconciliation #3676 or contributor branches.

Follow-up

• RALPLAN detached planner session-resolution failure recorded as a GJC product-gap ledger entry.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[Yeachan-Heo]

Hostile intake: REQUEST_CHANGES / merge blocked

Exact head fd5624b0ffcf2472b57b3516954df8accdb2fcb1; base 8846d0925b598ead06d56979f0d2696ed5bcc8de is an ancestor of current dev, and the product diff is narrowly scoped to the #3670 coding-agent/AI repair surface. Focused exact-head verification passes 28 tests / 133 assertions across async yield queue, fork context, and Anthropic cache evidence; git diff --check passes.

However, this is an owner-controlled internal repair PR, not a contributor PR, and exact required CI is not terminal: Telegram generation guard and affected native-build remain pending. The PR must not merge until exact-head CI is terminal green, the owner’s review artifact is authoritative, and the separate #3669 Codex SSE repair remains separate. Central review does not mutate or merge the owner branch.

—
[repo owner's gaebal-gajae (clawdbot) 🦞]

[Yeachan-Heo]

Review correction: integration hold, not product REQUEST_CHANGES

Exact head 9711458b0b797e1a2545a4b4b88e2bffee298949 has 20 green product checks. The remaining evidence/aggregate failure is inherited from the Telegram generation-guard integration gate and is downstream of that root; it is not a product-code failure in this PR. Therefore no product REQUEST_CHANGES disposition is assigned.

The PR remains on integration hold pending the assigned #3679 Telegram successor/guard repair. Once #3679 provides the exact current integration state, this PR requires a fresh exact-head check census; no rerun or contributor mutation was performed here.

—
[repo owner's gaebal-gajae (clawdbot) 🦞]

[Yeachan-Heo]

Terminal hostile disposition: MERGE_READY — integration hold remains

Exact head 3da7b40 is current against dev@cebd783a and the product checks are terminal green: 22/22 green, 0 red, 0 pending. Hostile review finds no P0/P1 in the #3670 coding-agent/AI product diff. The async staged-completion generation metadata, fork-context seed preservation, and immutable Anthropic fixture provenance are scoped to the owner lane and retain separate #3669 evidence requirements.

The earlier evidence failure is inherited Telegram guard integration and downstream, not a product failure in this PR. Merge authorization is therefore conditional on the assigned #3679 Telegram/guard owner resolving the integration root; this PR must not be merged ahead of that dependency. No contributor branch was mutated and no workflow was rerun.

—
[repo owner's gaebal-gajae (clawdbot) 🦞]

[Yeachan-Heo]

Hostile terminal review for #3670: MERGE_READY. Scope is contained to async delivery acknowledgement suppression, detached fork-context seed freezing, and Anthropic cache provenance. The unrelated architecture-2383 artifact was removed and replaced by issue-scoped evidence. Current PR base is cebd783; prior inherited-dev red was attributed to #3679 Telegram guard authority, not REQUEST_CHANGES on product logic. Focused tests and package typechecks passed; PR CI run 30654139692 was green. No guard-manifest mutation is present.

[Yeachan-Heo]

Post-merge correction: MERGE_READY was satisfied

Correction to the earlier integration-hold wording: PR #3681’s exact head 3da7b40 was technically MERGE_READY with 22/22 green product checks and no P0/P1 findings. The Telegram integration dependency had already been resolved by #3679 before the merge. PR #3681 subsequently merged into dev as commit 699a634.

The prior comment’s integration-hold language is superseded for historical accuracy; the technical hostile-review findings and MERGE_READY disposition remain valid. No source or workflow changes are implied by this correction.

—
[repo owner's gaebal-gajae (clawdbot) 🦞]