Honor terminal routes and preflight privacy persistence#99
Merged
Conversation
coreytshaffer
marked this pull request as ready for review
July 17, 2026 07:43
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.
Summary
human_handoffand the currently unimplementeddeterministicresilience routes terminal before backend executiontc runpackets before ledger creation and persist fixed content-withheld metadata instead of raw prompt/data textReconciliation
This branch originally claimed CR-123/124 while parallel work merged different canonical CR-123/124 changes into
main. Reconciliation commitf7bef76mergesorigin/mainnormally, preserves main's CR-123 Evaluation Handoff Contract and CR-124 Eval Handoff Hygiene, removes the superseded internal-scoring scope, and renumbers the distinct runtime fixes to CR-125/126. No rebase or force-push was used.Scoring and score interpretation remain external to TriageCore. The next eval-lane candidate remains a separately approved deterministic bundle/manifest builder.
Impact
Privacy-blocked runs now exit before creating ledger residue. Successful
tc runrecords contain content-withheld metadata and input lengths rather than prompt/data content. Governed terminal routes returnhandoff_required, recordworker_result_status=not_attempted, and do not invoke a backend.Validation
python -m pytest -q— 945 passed, 2 skippedpython -m triage_core.tc_cli audit --privacy-invariants— 698 records passedgit diff origin/main --check— clean