Repository navigation
Keep Scoring updates attached to retained sample files - #1306
Merged
Merged
Conversation
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
Keep each Scoring sample attached to the exact file loaded, including arbitrary filenames and samples sharing a seed/window. Resumed model grading, human Scores and Bug-origin settlement all commit through that retained handle.
Preserve the JSON format, ordering, machine-wide writer lock and CLI/Console behavior. Update the domain-to-code index; the inspected hand-written site descriptions remain accurate.
Closes #1305
Evidence
cargo test --test bug_origins historical_review_and_reclosed_origin_regressionsfailed in the newsave-failurescenario:failed settlement withdrew the retained decision's Eval proposal.After: the same scenario passes with withdrawal after successful checkpoint replacement.
cargo test --test scoring: 35 passed;cargo test --test bug_origins: 16 passed (each has one ignored subprocess entry point).cargo test --test console scoring: 3 passed, including CLI/Console parity with a noncanonical sample filename.cargo check --tests,cargo fmt --check, andcargo clippy --all-targets -- -D warnings: passed./usr/bin/time -p scripts/affected-tests mainpassed, using the fullcargo testsuite because nextest is unavailable. Wall time: 1366.91s (22m 47s), including 40.83s compilation of the remaining test targets; focused builds had already populated dependencies. Timing includes the selector and reflects this host's load, not CI queue time.Test seams
Review coverage
Independent Standards and Spec reviews used
git diff main...HEAD, fixed at maina2dfcfbd849ea803eb0e345a2348c6e6a9a81f4f. Both axes read all 11 changed files. Unread changed files: none. Generated-output exclusions: none.Final reports, including each axis's supporting files-read list, are retained in this Session at
.thirdshift-review-PnlyQx/standards.mdand.thirdshift-review-PnlyQx/spec.md.Unaddressed findings
Standards
tests/scoring.rs:275andtests/bug_origins/settlement.rs:190both discover and rename a fixture sample. The Scoring helper serves its two regressions; Bug-origin setup belongs to a separate fixture. Spec decision 12 keeps regressions at the existing CLI seams. Keeping these short setups local avoids adding Scoring-directory knowledge to generic shared test support; the reviewer explicitly calls this tradeoff defensible. No incorrect behavior was alleged. This is a local maintenance decision, with no deferred Spec or Day-shift call.Spec
None.
Security
None.
Security review outcome
No unaddressed introduced findings.
Merge Danger
Door: two-way
Private storage ownership refactor with no JSON migration or CLI changes.
Blast Radius: Scoring
Sample publication and all three writers share this protocol; the existing writer lock and permission-preserving replacement remain in use.
Built with codex · gpt-6.1-sol · xhigh