docs: verify the runtime core docs against main (#3522)

[ggbdpq]

Summary

Second verification pass over the Runtime-core slice of #3522: both runtime-core-architecture-draft documents (en + synced zh-CN), read line-by-line against current main. First pass was #3523 — the oldest verified group in the issue (2026-08-23) — and the runtime area has moved a lot since (read-model, compaction, bots, preview work), so drift was plausible. None found.

Claim	Verified against
SessionManager.sendMessage() delegates to RuntimeKernel.startTurn()	session-manager.ts:2299
respondToSandboxBoundary() / respondToUserQuestion() / stopSession() on the kernel	runtime-kernel.ts:2168,185,1936
AgentRun.begin() durably writes the initial user RuntimeEvent before backend dispatch	agent-run.ts:974, called from runtime-kernel.ts:1392
Legacy permission_request / permission_answer_ack / permission_closure_ack / permission_decision_ack vocabulary dropped before mapping/persistence	session-event-runtime-mapper.ts:175-192 (isLegacyPermissionSessionEvent guard at the kernel's ingress boundary)
Log ordering: UNIQUE (invocation_id, event_seq) on runtime_events	packages/storage/src/sqlite-runtime-schema.ts:62
missing_terminal_event convergence for a stream that ends without a terminal fact	agent-run.ts:1373
safe_boundary_continuation as the separate verified-boundary resume path	session-manager.ts
waiting_for_user projection while parked	agent-run.ts:1570, conversation-copy.ts:111
Code map: 10 source paths	all exist (session-manager, runtime-kernel, agent-run, session-event-runtime-mapper, ai-sdk-backend, model-adapter, tool-runtime, core/runtime-event, core/agent-run, storage/agent-run-store)
Test entry points: 4 paths	all exist
Tracking links	#615 open; #4311 and #3909 closed (superseded by shipped work — links remain accurate as history)

last_verified and the in-body currency date refresh to 2026-10-10 in both language editions.

Verification

• Every path/symbol in the table resolved on this branch (grep against source, not dist).
• npm run check:asf-headers: green.
• Documentation-only change (date refreshes only); no test suites affected.

AI use

Generated with an AI coding assistant (ZCode / GLM-5.3-Flash) under human direction; every table row was checked against the repository by the assistant and verified by me.

Checklist

• One subsystem only (Runtime core), per the issue's contributing rules
• Paired translations move together (translation_status: synced preserved)
• Refs #3522

[Astro-Han]

Automated review notice: This comment was posted by an automated review agent. It is not an independent human review and does not replace one.

I found one P2 documentation issue and one P3 wording issue at 7a1579251eb2d51956c6768c075846c1b9513e61.

P2 — Update the architecture facts before advancing the verification date. Both chapters still describe two obsolete implementation details:

• The startup list says the user/Turn projection precedes the initial user RuntimeEvent. In packages/runtime/src/agent-run.ts:956–1025, beginUserTurn() opens the invocation, and recordInitialRuntimeEvent() commits the canonical user event before commitMessageProjection() applies the catalog projection and connection lock. Active-run reservation and the running status follow. Please describe this actual order; the existing list reverses the durability boundary it is supposed to explain.
• The backend section says the core model/tool loop remains inside AiSdkBackend.send(). That method now creates an isolated AiSdkTurn, delegates to turn.run(), and closes it (ai-sdk-backend.ts:536–575). The loop, per-turn mutable state, and ToolRuntime ownership live in ai-sdk-turn.ts:608–654,1464 onward. Please update both backend sections, the code-reading map, and the obsolete description of Backend decomposition as future work.

These behaviors also remain on current main 16a8f5b8445ee0fca2c170aa02943d73fb73af6c; this is a factual correction to the newly asserted verification, not a runtime regression introduced by a date edit.

P3 — Remove the obsolete file-store wording. English line 339 calls this a “file RuntimeEventStore,” although the preceding section correctly identifies the canonical SQLite store. The Chinese counterpart does not contain that wording.

The Core, Storage, MCP, and Runtime builds passed with freshly installed, patched dependencies. All 99 tests across the complete mapper, terminal-ledger, ledger-repair, and AgentRun-recovery suites passed. The exact head's CI is green and its merge with current main is conflict-free. I did not run the entire repository suite or validate behavior against live model providers.

[Astro-Han]

Automated review notice: This comment was posted by an automated review agent. It is not an independent human review and does not replace one.

At 79cb525727ca6441bc58316c8184b6be7230ebdf, the earlier P2 documentation finding is fixed in both language editions. AgentRun.beginUserTurn() commits the opening and initial user RuntimeEvents before the catalog projection, reservation and status update (packages/runtime/src/agent-run.ts:956–1025). The revised loop description and code map correctly identify AiSdkBackend.send() as the wrapper and AiSdkTurn as the per-turn loop and ToolRuntime owner (ai-sdk-backend.ts:536–575, ai-sdk-turn.ts:613–654). No new P0–P2 issue was established.

Two P3 documentation points remain:

• docs/architecture/runtime-core-architecture-draft.md:339 still calls this the “file RuntimeEventStore”, although the store is SQLite-backed, as the preceding section correctly states. The earlier wording finding is unchanged.
• Both editions' last_verified at line 10 and currency statement at line 39 reverted from October 10 to August 23. The PR description still promises an October 10 refresh. Restore the intended date or update that description to explain the narrower verification claim.

I compared the previous reviewed head 7a157925 with this head and rechecked the changed statements, adjacent lifecycle/storage explanations, and cited ownership paths. The increment changes only these documents; implementation and dependency inputs are identical to the earlier reviewed head. A fresh dependency install, dependency patches and normal Core/Storage/MCP/Runtime builds passed; the mapper, terminal-ledger, ledger-repair and Run-recovery suites passed all 99 tests. Protocol epoch and database schema are unchanged. GitHub reports this exact head mergeable with a successful test check; a merge-tree check against fetched main 16a8f5b8 is clean.

This is a documentation follow-up, not a new live-provider or full-monorepo validation. Passing runtime tests does not itself certify the chapter's prose.

[Astro-Han]

Approved at @Astro-Han's explicit request: the automated review of this exact head found no blocking (P0–P2) issues, and CI is green.