feat(runtime): establish the managed mutation acceptance kernel

[zhiiw]

Summary

Establish the managed mutation kernel that owns the durable boundary from T1 reservation through terminal settlement and atomic SQLite successor acceptance.

This PR intentionally stops before Gitoxide candidate reopening and accepted-ref repair. Those recovery and projection responsibilities now live in a second stacked delivery so this PR has one primary invariant:

Once a managed Write/Edit T1 is durable, only the owner-scoped managed settlement path may commit its terminal outcome; provider outcome, accepted successor, canonical workspace head, and reservation release are either committed together or not committed at all.

Ownership

• Runtime owns the original Write/Edit arguments, the bounded pure transform, the immutable provider-result snapshot, and the exact durable response envelope.
• Execution Stores / SQLite owns the cross-process reservation, terminal transaction, accepted workspace history, and disposable projections.
• The managed mutation authority owns candidate/no-effect verification through issuer-scoped capabilities; generic RuntimeEvent/T2 writers cannot settle a managed operation.

Atomic boundary

For a successful mutation, SQLite commits the tool outcome, workspace successor fact, canonical head CAS, and reservation release in one transaction. For no-change or a proven no-effect business failure, SQLite commits the terminal outcome and reservation release without advancing the head.

Failure and retry states

• Pre-T1 admission failure: no reservation and no tool execution.
• Managed no-change/no-effect: one durable terminal, no head movement.
• Valid successor: one atomic accepted successor.
• Missing or conflicting proof: unsettled/fail closed; no generic fallback.
• Exact historical retry: returns the immutable accepted result even after a later legal head advance.

The no-effect bearer is now bound to its issuing owner, concrete execution store, and durable storage-root identity. Runtime also constructs the terminal outcome once and uses that same immutable event for live publication and durable settlement.

Follow-up boundary

The stacked Gitoxide recovery PR owns durable candidate receipt reopening, accepted-ref projection, active-reservation recovery state, and production-shaped helper crash evidence. It does not widen this PR's SQLite or Runtime authority.

Verification

• Rebuilt from current upstream/main.
• git range-diff preserved all six extracted commits exactly.
• Core, Storage, Runtime, and Runtime Host builds pass in the full stack.
• Focused mutation/settlement/persistence tests pass.
• Cross-store no-effect capability forgery is rejected.
• git diff --check passes.

中文说明

摘要

本 PR 只建立 managed mutation kernel，负责从 T1 reservation 到 terminal settlement 与 SQLite 原子 successor acceptance 的 durable 边界。

Gitoxide candidate 重开与 accepted-ref 修复已经移到第二个 stacked PR。本 PR 只证明一个主要不变量：

managed Write/Edit 的 T1 一旦持久化，只有 owner-scoped managed settlement 才能提交终态；provider outcome、accepted successor、canonical workspace head 与 reservation release 必须同时提交或全部不提交。

Owner

• Runtime：拥有原始 Write/Edit 参数、有界纯 transform、不可变 provider result snapshot 与精确 durable response envelope。
• Execution Stores / SQLite：拥有跨进程 reservation、terminal transaction、accepted workspace history 与可重建 projection。
• Managed mutation authority：通过 issuer-scoped capability 验证 candidate/no-effect；generic RuntimeEvent/T2 writer 无权结算 managed operation。

原子性与失败状态

成功 mutation 在一个 SQLite transaction 中提交 tool outcome、workspace successor fact、canonical head CAS 与 reservation release。no-change 或已证明无副作用的业务失败只提交 terminal outcome 并释放 reservation，不推进 head。

缺少证明或证明冲突时 fail closed，禁止 generic fallback。no-effect capability 已绑定签发 owner、具体 execution store 与 durable storage-root identity；Runtime 只构造一次 terminal outcome，live publication 与 durable settlement 使用同一 immutable event。

后续边界

第二个 stacked Gitoxide recovery PR 负责 durable candidate receipt 重开、accepted-ref projection、active reservation recovery state 与真实 helper crash evidence，不会扩大本 PR 的 SQLite/Runtime 权限。

验证

本分支已从最新 upstream/main 重建；六个 extraction commits 经 range-diff 全部精确保留；Core、Storage、Runtime、Runtime Host 构建通过；mutation/settlement/persistence 定向测试通过；跨 store 伪造 no-effect capability 会被拒绝；git diff --check 通过。