fix: add strict read-only diagnostics - #1
Merged
Conversation
icerain-cmd
marked this pull request as ready for review
August 1, 2026 11:29
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.
What
run-once --diagnostic, a fail-closed read-only state/config inspection path--dry-runbehavior but document that it may update retries, cursors, buffers, dead letters, and run logsWhy
The earlier operational verification called
--dry-runside-effect-free, but that mode intentionally constructs the pipeline and can write local HEGI state. The new mode avoids pipeline construction and all Telegram, LLM, Memory Forest, archive, and run-log paths while validating a private stable SQLite snapshot.Safety properties
Verification
.venv/bin/python -m pytest -q: 179 passedscripts/smoke-test.sh --python .venv/bin/python: 128 passed.venv/bin/ruff check .: passedbash -n scripts/migrate-existing-install.sh: passedgit diff --check: passedLive profile verification was read-only: operating config, state DB/sidecars, queues, archives, and approval artifacts retained identical fingerprints. No Telegram, LLM, archive, approval, or Memory Forest commit call was made.