Repository navigation
fix(cli): explain guarded recovery for formal Volume Baseline drift - #124
Closed
ikenainanodesu wants to merge 1 commit into
Closed
ikenainanodesu wants to merge 1 commit into
ikenainanodesu wants to merge 1 commit into
Conversation
alkor2000
pushed a commit
that referenced
this pull request
Oct 14, 2026
An out-of-band edit to a formal Volume under Managed Scope fails closed with managed_scope_formal_volume_baseline_drift, but neither the scope activate refusal nor the Legacy baseline scope refusal said how to recover, and the latter pointed at Maintain and activation as if the edit were source or policy drift. The refusal now appends a localized recovery hint, the Legacy hint names the troubleshooting route, and docs/troubleshooting.md gains the "Formal Volume Baseline drift" section: preserve the state, check pending Recovery through the Guide, restore a verified matching snapshot when there is none, and never edit Baseline hashes. Exit status and error codes are unchanged; a synthetic regression covers both locales and both output modes. Landed from PR #124 by ikenainanodesu; the maintainer regenerates the cognition Entries in the closing commit of this batch. Closes #123 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Contributor
|
Landed on main as 509e686 with you as the author. The PR stays unmerged only because this repository regenerates its governance files (Baseline and Code Volume) in a closing commit instead of merging branches; the code, catalog keys, doc section and regression went in unchanged. It ships in rc21. The minimal repro made the review a five-minute job, thank you for that. Release: https://github.com/aoci-spec/aoci-code/releases/tag/v0.1.0-rc21 |
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
2 participants
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.
Closes #123.
After an out-of-band edit to a formal cognition asset, Scope Change correctly refuses
managed_scope_formal_volume_baseline_drift, but previously provided no recovery guidance. The Legacy Baseline refusal only suggested ordinary maintenance/activation, leaving the distinction unclear.Add localized recovery guidance to the formal-asset refusal and a troubleshooting link to the Managed Scope Baseline refusal. Document preserving evidence, checking existing Recovery, restoring a verified matching snapshot when necessary, and replaying supported operations. No automatic rebaseline, guard relaxation, new command, MCP/schema change, persisted-format change, or installed-binary replacement is introduced. The twin-line deletion defect is already fixed upstream in 6b4f0cc (#117); this PR does not duplicate that change.
Validation
make fast: passed in an isolated Go 1.26.9 Linux container.make verify: not fully green. Package tests, race detector, staticcheck, license/text/dependency checks, reachable-vulnerability check and clean-room smoke completed; scenario suite 75/75 and self-upgrade suite 80/80 passed.dockerexecutable. Database-backed integration is not claimed.All fixtures and reproduction material are synthetic. No private repository files, logs, raw indexes, snapshots, or identifiers are included.