3 Commits

Include renames

Author	SHA1	Message	Date
weichen	adcd8fefd2	Fence U3 account writes and stabilize directory cursors ... Why: Account disable could be followed by late Backend business writes, API key creation could implicitly create users, account bootstrap locks could invert, and directory cursors were process-local or leaked out-of-scope changes. Evidence: Local go test ./... and isolated PostgreSQL package suites passed on the staged candidate; exact committed-head SELF replay and stage 6 human review remain pending. Impact: Adds final account transactions and external-effect checks across HTTP, Host, Bus and run manager; tightens API key issuance and persists versioned cursor signing. Delegated RDM rename still needs the separately proposed real-operator contract, so A1 and stage 6 are not complete. Refs: Documents U3 r1, approved A1-A4 amendment fb3a821, pending delegated-projection amendment 5783940, Dev feature/iam-u3-account-directory-recovery.	2026-10-14 07:33:54 +00:00
weichen	bd4b3bca94	Remove the empty -ws shell directory after each apply ... Why: relaxAndRemove cleared the per-exec id directory but left the -ws parent behind, so every conversation accumulated an empty husk - the live probe caught it in the workspace listing. Evidence: go test ./... green; TestOverlayCleansShellDir pins the behavior with a real bwrap roundtrip. Impact: One extra os.Remove of the (now empty) parent; failures are best-effort as before. Refs: Dev task feature/agent-s0-workspace-overlay (fix-up of #135).	2026-10-11 02:18:01 +00:00
weichen	01fd3b6fd4	Add the S0 task workspace overlay: frozen base, private upper, CAS apply ... Why: The sandbox tier wrote the session directory directly, so a buggy or runaway script could leave the workspace half-mutated and nothing bounded what a timeout had already written. The plan's first landing shape (section 4.4) swaps the session bind for a frozen-base overlay: each exec freezes the session dir (hardlink clone + sha256 baseline), runs on a private upper, and only a clean exit promotes the change set back via CAS (baseline hash match -> atomic replace/remove; externally changed targets double-store as *.conflict-* instead of clobbering). Timeouts and kills discard the upper entirely - half-written state never lands. Evidence: go test ./... green including bwrap integration roundtrips (TestSandboxWorkspaceOverlayRoundtrip: add/modify/delete through a real overlayfs upper with whiteout handling and ws cleanup; TestSandboxWorkspaceOverlayTimeoutDiscards: partial writes discarded on timeout) and unit anchors for freeze manifest (.agentx excluded), CAS add/modify, conflict double-store, and the change summary. Impact: Opt-in via --exec-workspace overlay / AGENT_SYSTEM_EXEC_WORKSPACE (only with --exec-backend sandbox; fail-closed on unknown modes). The model sees a one-line change summary appended to the tool output, so discards and conflict files are visible. Default behavior is unchanged. Refs: proposal 2026-10-10-agent-delegation-routing-sandbox.md section 4.4; Dev task feature/agent-s0-workspace-overlay.	2026-10-11 02:04:05 +00:00