Repository navigation
findings.py: ledger path from FINDINGS_LEDGER - #429
Merged
Merged
Conversation
…a commit is checked in the ledger's own repository (@developer) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s checked in the repository that holds it (@developer) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Fast lane, harness item findings-ledger-path. Prevents 2026-11-03: the agreed ledger could not be recorded, because the ledger must live in a separate repository.
FINDINGS_LEDGERgives the ledger path (default docs/findings.jsonl);addchecks the commit in the ledger's own repository. Search record and gates unchanged. 3 net counted lines; harness suite 3860 passed; mypy, ruff clean.🤖 Generated with Claude Code