Track remaining #98 state-kernel scope: warm-runtime process state, generated-runtime state mounting, budgets, lifetime visibility

[ScriptedAlchemy]

Readback audit of origin/main @ 72c3b38f9eeafa0a8e762c413960f5d34cf18946 found that #98 was closed after the durable node:sqlite slice (#142/#149/#154) while the rest of its scope is neither delivered nor tracked. #107's Wave-3.5 comment records "#98 delivered", and #98 itself carries no deferral comment, so these holes are currently invisible:

Untracked remainder

1. Warm-runtime process state never mounted. meta-framework: execution plan and sequencing #107 revision 2's dependency graph specifies "Provide an optional durable Agent state kernel #98-v1 (lifetime taxonomy + node:sqlite driver; process state rides the warm runtime)" and "Provide an optional durable Agent state kernel #98's process state consume it (wave 4+)". On main, createWarmFlightHost owns no state (packages/rsc-runtime/src/warm-runtime.ts:73-92) and createMemoryStateDriver is exported (packages/rsc-runtime/src/state/index.ts:59) but has no production caller — only tests construct it. Restart/multi-instance process-state proofs do not exist.

2. Generated bundles cannot mount state at all. Every generated invocation path calls runAgentRequest without a state handle:

   • tool path: renderGeneratedRoute, packages/agent-bundle/src/mcp-server-runtime.ts:146-149
   • event path: packages/agent-bundle/src/mcp-server-runtime.ts:438-459
   • generated worker scope: packages/agent-bundle/src/build/entry-shell.ts:456-462

   So (await agent()).state is unavailable in every compiled bundle; the kernel is reachable only by embedders who wire a driver into runAgentRequest themselves (as examples/rsc-agent-runtime does).

3. Kernel-contract budgets absent. The body requires cancellation, size, time, and retention budgets; the public definition contract exposes no such policy (packages/rsc-runtime/src/state/contract.ts:117-131) and nothing under packages/rsc-runtime/src/state/ implements retention.

4. Lifetime visibility absent. The body requires inspect/Workbench to expose effective lifetime and runtime-instance identity; no state-lifetime projection exists under packages/agent-bundle/src/ or packages/workbench/src/.

Suggested disposition

Either reopen #98 for the remainder, or treat this issue as the tracker. Item 2 pairs with the same mounting hole for notices noted on #99 (generated request scopes pass neither state nor noticeLedger), so one "generated-runtime request-scope mounting" lane could cover both.

Refs: #98, #99, #107 (cluster: #93–#108).

[ScriptedAlchemy]

#251 landed the generated-runtime mounting slice in merge e131071: generated MCP, routed CLI, and script request scopes now own a state driver plus notice ledger; request/process lifetimes use memory, workspace-durable uses node:sqlite, invocation identity is forwarded into the render scope, and createWarmFlightHost can own the shared runtime state.

This completes #233 items 1–2. Items 3–4 (kernel-contract budgets and inspect/Workbench lifetime/runtime-instance visibility) remain deferred, so this tracker stays open.

[ScriptedAlchemy]

Lane open for the remaining scope (items 3–4) on branch fix/233-remainder: kernel-contract budgets land in packages/rsc-runtime/src/state/** (contract/journal/drivers/conformance — kernel layer only), and lifetime visibility lands in the read-only inspect/doctor surfaces under packages/agent-bundle/src/. No edits planned to packages/rsc-runtime/src/notices/** or the MCP notice surface, so the #99 inbox lane should be unaffected; the ledger's state definition only picks up default budgets through defineState. Will rebase over whatever lands first.

[ScriptedAlchemy]

Recorded from the #104 journey suite (#260): generated event request scopes mount host/session/workspace principals (workspace = native cwd) but no actor principal, so actor-directed notice recipients can never match admission in generated runtimes — recipientMatchesPrincipal requires an available actor. The worktree-proximity example targets the supported workspace axis instead. Actor-principal mounting (deriving an actor identity where a host contract exposes one, honest unavailable otherwise) is follow-up lineage for this issue alongside the already-deferred items.

[ScriptedAlchemy]

Coordination note from the #99 stage-3 landing (#264, bb9e82c19): the notice ledger's state definition gained an exposed event — each served MCP inbox read of a non-empty inbox appends one bounded journal event (idempotent per invocation) and updates a bounded per-notice exposure summary. No state-kernel internals were touched, but the budgets slice (item 3) should count this event family when sizing journal growth for the notice ledger store.