Repository navigation
chore(cli): adopt Roost 0.2.0 with v4 storage diagnostics - #1735
Merged
Merged
Conversation
Model: gpt-6.1-sol
Model: gpt-6.1-sol
Lampese
force-pushed
the
codex/roost-namespace-budget
branch
from
October 20, 2026 10:25
69585c0 to
439970e
Compare
Contributor
|
Desktop PR smoke regression failed on commit
Recordings not attached
The Actions artifact retains the complete trace, screenshots, logs, and runtime evidence. |
Model: gpt-6
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
Test plan
pnpm check,pnpm format, documentation checks and diff checks 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.