Skip to content

chore(cli): adopt Roost 0.2.0 with v4 storage diagnostics - #1735

Merged
Lampese merged 4 commits into
mainfrom
codex/roost-namespace-budget
Oct 20, 2026
Merged

Lampese merged 4 commits into
mainfrom
codex/roost-namespace-budget

Conversation

@Lampese

@Lampese Lampese commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

Related issue

Coordinated adoption of Roost #15, #16 and #17. Merge this before the dependent message-state change #1737.

Problem / pressure

Lody still uses TypeScript SDK 0.1.3 and Native 0.1.2. The released 0.2.0 packages contain interned SQLite namespaces and compact batch recovery, but the sustained-streaming budget test queries the removed text namespace column directly.

Summary

Pin SDK 0.2.0 through the shared catalog and Native 0.2.0 exactly in the CLI manifest and publication guard, preserving the published-runtime version policy. Update the lockfile and exact release-age exceptions for the SDK, Native main and all six platform packages, preserving unrelated resolutions. Normalize diagnostic SQL to the same space/key/value columns for containers 3 and 4, retaining all three existing storage budgets.

Native 0.2.0 uses SQLite container v4 and refuses earlier containers. This PR performs no migration, automatic reset, history cleanup or deployment. The dependent #1737 reuses this catalog update for its owner-local recovery API.

Visual explanation

Simple change: the CLI consumes the coordinated 0.2.0 SDK and Native versions; only test SQL adapts to the v4 namespace relation. Runtime ownership and application write paths do not change.

Before / after

Before After
SDK 0.1.3 and Native 0.1.2 are separately pinned. The SDK catalog and exact Native runtime pin are both 0.2.0, with six exact platform dependencies.
Storage diagnostics read roost_kv.space directly. v4 joins roost_spaces; v3 keeps its original relation, with unchanged budgets.
#1737 cannot compile against the released SDK API. The released SDK exposes its required local recovery option.

Test plan

  • Frozen pnpm installation passes with both installed packages at 0.2.0 and no local native override.
  • Full CLI suite: 4,429 passed, four existing skips.
  • Electron native staging: four tests pass; all six target selections use synthetic foreign bindings, while the installed host binding executes signed SQLite write/reopen probes.
  • Complete pnpm check, pnpm format, documentation checks and diff checks pass.
  • The public CLI builds with a 2 GiB heap and passes its published-bundle runtime probes; six dependency-version policy tests pass.

Context handoff

Same-repository maintainer branch, rebased on main 5da1dab. The owning bilingual storage and Native-runtime notes record the published dependency versions, container boundary and validation. Merge #1735 before #1737; no package publication or application database change is included.

@Lampese
Lampese marked this pull request as ready for review October 19, 2026 21:02
@Lampese
Lampese force-pushed the codex/roost-namespace-budget branch from 69585c0 to 439970e Compare October 20, 2026 10:25
@Lampese Lampese changed the title test: support interned Roost namespaces in storage budgets chore(cli): adopt Roost 0.2.0 with v4 storage diagnostics Oct 20, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Desktop PR smoke regression failed on commit 439970e6bf5a87b4853079f9232d47f471073dc5.

Recordings not attached

  • Run evidence: failure-index.json is missing

The Actions artifact retains the complete trace, screenshots, logs, and runtime evidence.

@Lampese
Lampese merged commit 0882a4a into main Oct 20, 2026
15 of 16 checks passed
@Lampese
Lampese deleted the codex/roost-namespace-budget branch October 20, 2026 11:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant