Skip to content

Add saved conversation intents and scoped restoration - #185

Merged
sidmohan0 merged 79 commits into
mainfrom
conversation-scoped-restore
Oct 29, 2026
Merged

sidmohan0 merged 79 commits into
mainfrom
conversation-scoped-restore

Conversation

@sidmohan0

@sidmohan0 sidmohan0 commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Add saved send intents and explicit conversation-scoped restoration across Rust, WASM, Python and Node. A preparation saves mappings and funded pending intents before external handoff. Only a trusted observation of a successful send to the exact chat stages issuance; definite non-delivery has a separate resolution. Any unresolved intent pauses all scoped restoration in that chat, including old or plain responses. Other chats remain usable.

Core owns context identity, one-time site binding, marker membership, operation history, counts and strict decoding. Pending sends reserve their later confirmation row, encoded bytes and revision increments before handoff; other writes, including recovery, cannot spend those credits. The 100,000-row ceiling and 256 recovery-only slots remain finite. Bindings expose owned views and scoped strict/buffered/progressive streams through shared Core. No read, restore or failure silently saves state.

The coordinated v3 map11 includes conversation state at key 9. Legacy v1/v2 reads, exports, no-ops and discarded changes preserve bytes until a warned, approved and saved upgrade; published beta.1/beta.2 cannot open v3 state.

Independent source, artifact and installed-consumer reviews passed. Clean evidence covers full Rust formatting/Clippy/all-feature tests; all-SDK build/check/smoke and installed typing; actual four-SDK parity (45 scenarios/600 steps); separate encrypted native conversation hosts (16/66), CAS (9/28), pressure and original host suites; and Chromium encrypted lifecycle/recovery with four histories, eight credential paths and 15 authenticated malformed imports. Contract inventory, parity receipt and capacity measurements retain the exact scope. Final integrated-head CI is required.

Trusted hosts still must substantiate send observations, chat identity, durable saves and deployment capacity. The reference proofs do not establish real provider acceptance, shipping-host security, final G3 freeze or beta.3 publication.

Implements the Core/SDK conversation behavior for #148, with #167/#168/#169/#170/#171 and current-field recovery for #152.

@sidmohan0 sidmohan0 added no-changelog No user-facing change; requires Changelog exemption reason in PR body area:workspace Persistent pseudonym workspaces and workspace SDK integration labels Oct 29, 2026
@sidmohan0 sidmohan0 added this to the 0.5.0-beta.3 milestone Oct 29, 2026
@sidmohan0 sidmohan0 removed the no-changelog No user-facing change; requires Changelog exemption reason in PR body label Oct 29, 2026
@sidmohan0 sidmohan0 changed the title Specify pending sends and conversation-scoped restoration Add saved conversation intents and scoped restoration Oct 29, 2026
@sidmohan0
sidmohan0 changed the base branch from codex/workspace-operation-records to main October 29, 2026 12:08
@sidmohan0
sidmohan0 marked this pull request as ready for review October 29, 2026 14:53
@sidmohan0
sidmohan0 merged commit 4bc6966 into main Oct 29, 2026
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:workspace Persistent pseudonym workspaces and workspace SDK integration

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant