Repository navigation
Release 0.3.0: reliable channel routing, catalog persistence, and CLI validation - #40
Merged
Merged
Conversation
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
1 participant
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.
Scout 0.3.0 fixes the issues found while reviewing the published package. Explicit channel routing now treats scoped npm names and agent mentions in the body as message text. Claude session catalogs serialize atomic writes and drain pending persistence and error reporting during shutdown.
The CLI suite builds isolated temporary source fixtures, verifies both compact and detailed help, and runs in the root unit command and as an explicit Node 24 CI step. The npm README accurately lists the bundled CLI, broker/runtime, and basic web surface; the Rust TUI remains optional and the retired monitor is no longer advertised.
The local publisher gains an explicit existing npm-login mode for two-factor challenges. Token mode remains the default. Both registry scopes are pinned to npmjs, credential conflicts fail closed, and source, signing, retained bytes, receipt, and promotion gates remain unchanged.
Validation: exact-head local standalone checks, full unit suite (including dedicated CLI and 52 publisher tests), and signed tarball audit; hosted Linux and macOS CI must pass before merge. Two independent reviewers approved the exact candidate. The shared source is narrowly synchronized from the separately reviewed and merged source fix.
Closes #34
Closes #38
Closes #39