[stringsofthemind-oss]

Planner-generated operation IDs and replaceable local history can authorize a second external effect after an ambiguous first attempt. This draft adds an opt-in trusted host admission profile beneath the existing Once kernel: immutable intent bindings, a shared execution store, and an independently durable witness of revision plus operation/intent state content. UNKNOWN remains blocking, including a crash before the first provider effect.

The original T06/T07 counterexamples remain intact. Their maximum-one-effect protection check fails RED with two provider effects; H01/H02 require one effect and deny substituted IDs, partial history replacement, locally rehashed replacement state and coherent rollback. A separately admitted identical action still executes. Review also found and reproduced a revision-only partial-restore defect; the stronger v2 profile is required by MCP rather than silently accepting that earlier candidate.

Validation on Windows / Node 24.19.0 / two disposable PostgreSQL 18.6 clusters:

• 12 hostile-recovery scenarios passed (13 Node tests), with built-in-only independent provider-journal checks.
• 105 affected SDK regressions passed, zero skips; 26 installed candidate MCP tests passed.
• Packed MCP with unchanged published SDK 0.1.25: 25 compatibility tests passed; new intent mode denied before callbacks.
• Actual Summa42 efc6794ea79a4be5b2f60e376833a1d03cba053c services: kill after provider commit/lost acknowledgement, three fresh workers blocked before replacement Attempt, then authoritative CONFIRMED_EFFECT / SETTLED and replay; one POST and one provider effect. Independent checker reads the saved Summa42 SQLite state.

Reproduce with npm --prefix mcp run package:hardening -- /absolute/new-evidence-directory, then follow the generated README. See docs/SILENT_CHICKEN.md and examples/summa42-host-integration/ACCEPTANCE.md for protocol, SQL privileges, migration, negative cases and acceptance mapping. CI repeats the hostile cases and actual pinned Go-service proof.

Review/merge/release gates: this ports the unmerged PR #303 store seam, so coordinated security/design review remains necessary. Full Box/LLM/global-scheduler integration, production TLS/credentials, physical failure-domain separation, production recovery and scale qualification are incomplete. v2 scans the full namespace on each short transaction and sacrifices availability after ambiguous cross-store commit. No automatic migration of existing uncertain history is supplied. The revision-only v1 API remains a documented draft/control surface and is not accepted for host-intent v2.

SDK 0.1.27 / MCP 0.2.3 are source-built unpublished candidates. MCP's default SDK pin, public-current metadata and plugin pins remain unchanged. Do not merge, release or treat this as universal exactly-once execution on the strength of fixture CI alone. No real payments, customer orders or production credentials were used.

Final head aeed7d7: 37 CI checks succeeded, 2 publication/submission jobs intentionally skipped. The full SDK release chain passed locally; corrected Evolution campaign and isolated trial passed. Linux hostile-recovery CI (39440167766) passed Go race tests, all hostile scenarios and actual Summa42 proof; downloaded artifacts were rechecked using the built-in-only checkers. Exact installed evidence dependency audit found zero vulnerabilities. No merge or publication was performed. The authorized factual Summa42 #35 update is SofiaFlux/summa42#35 (comment) .

[cloudflare-workers-and-pages]

Deploying onceexec with    Cloudflare Pages

Latest commit:	aeed7d7
Status:	✅  Deploy successful!
Preview URL:	https://c0969bd2.onceexec.pages.dev
Branch Preview URL:	https://feat-silent-chicken-host-aut.onceexec.pages.dev

View logs