Repository navigation
Flag destructive commands in Run metrics - #1163
Merged
Merged
Conversation
This was referenced Oct 23, 2026
Merged
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
Flags cover force pushes, explicit shared-branch rewrites and recursive deletes outside the Worktree. Old evidence remains missing when the check cannot establish a result. The guide and site pages describe the advisory behavior.
Closes #1038
Evidence
After: the retained regressions pass in
cargo test --test metrics(24 passed, one fixture entry ignored). Fixtures cover matching commands and near misses across all six Harness command shapes; fixture commands are trace data.cargo test --test run_metrics: 10 passed, one fixture entry ignored, including successful and failed Runs with flags, late amendments and trace removal.cargo test --test console peek_shows_retained_run_metrics_and_marks_missing_signals: passed.cargo check,cargo clippy --all-targets -- -D warnings, formatting and generated-doc checks passed.scripts/affected-tests 7b8de1fc8cb5bdb27aaf037aecaa53b9c17c66e7: passed on2786258; 44 site tests and 2,405 Rust tests passed (58 fixture/helper entries skipped). Timed selection: 1,945.16 s wall, including the 112 s Rust compilation; nextest execution: 1,756.743 s.Test seams
thirdshift metrics: flags, near misses, historical evidence and weekly counts.show --json: retained commands and missing signals.Review
Reviewed against issue-981 pinned at
7b8de1fc8cb5bdb27aaf037aecaa53b9c17c66e7. Addressed both Standards judgment calls and all seven Spec findings, running each behavioral reproduction before fixing it and retaining its tests. Both axes read all 14 changed files, including the generated HTML hunk. Generated-output exclusions: none. Unread changed files: none.Unaddressed findings
Standards
None.
Spec
None.
Security
None. Security review of the issue-1038 diff against merge base 7b8de1f found no introduced findings: the check only lexes session commands (never executes them), retained commands render escaped in peek via linkify, trends keep counts only, and flags are advisory (never block or fail a Run).
Security review outcome
No unaddressed introduced findings.
Merge Danger
Door: two-way
Blast Radius: metrics
Adds advisory metrics and trace-directory metadata. Saved flags do not change Delivery or Run outcomes.
Built with codex · gpt-6.1-sol · xhigh