chore: resolve issue #116 — correct oracle fixture provenance (metadata half)#124
Merged
Merged
Conversation
The golden TS reference pinned sourcererCommit e3b9f18, which was amended away and is now dangling (unreachable from any ref, survives only until gc). Correct it to 4e1e0f8 — the current tip of Sourcerer main and the hash the sibling README.md already documents as the capture source. Metadata-only; the differential-eval parity logic never reads this field. In-scope half of #116 per the issue's bail-if: the cross-repo Sourcerer origin push (4e1e0f8 still unpushed) requires that separate checkout and is left for a human/session with it. Resolves the fixture-metadata portion of #116. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
5 tasks
There was a problem hiding this comment.
Pull request overview
Updates the recruiting scoring differential-eval fixture metadata so the vendored TypeScript oracle points at a reachable Sourcerer commit, restoring a valid provenance chain for auditability.
Changes:
- Updated
meta.sourcererCommitin the TS golden reference fixture from a dangling/amended hash (e3b9f18) to the current reachable Sourcerermaintip (4e1e0f8).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Auto-generated by portfolio-orchestrator nightly run on 2026-06-19 (live mode).
Resolves the in-scope half of #116 (oracle fixture provenance repair).
What changed
src-tauri/src/recruiting/scoring/fixtures/golden-ts-reference.json:meta.sourcererCommite3b9f18→4e1e0f8(1 line).Why
e3b9f18was amended away and is now a dangling commit in Sourcerer (unreachable from any ref, survives only until gc).4e1e0f8is the current tip of Sourcerermainand the hash the siblingfixtures/README.mdalready documents as the capture source — this aligns the JSON metadata with the README.What's deferred (the issue's
bail-if)The cross-repo step — pushing Sourcerer
main(4e1e0f8, currentlyahead 1/ unpushed) to its origin — needs that separate~/Projects/Sourcerercheckout and is left for a human or a session with it. Per #116's bail-if: "do the fixture metadata half and comment." Staleness-guard follow-up is already tracked as Linear FHR-98.Verification
cargo test eval_differential→ 2 passed, 0 failed (1 ignored: hits real LLM). Metadata field is parsed but never consulted by the parity logic, so the 26-vector @ 1e-6 parity is unchanged.🤖 Generated with Claude Code