Skip to content

Commit a2e1915

Browse files
authored
fix(review): correct predicted_gate_calls migration ref to 0137 (#8695)
Both predicted-gate-calls.ts and predicted-gate-agreement.ts carried a comment pointing the predicted_gate_calls table at migrations/0132, which actually creates the unrelated impact_map_query_cache table. The table is created by migrations/0137_predicted_gate_calls.sql, so a reader tracing the table's migration history was misdirected to the wrong file. Closes #8675 Co-authored-by: bitfathers94 <237535319+bitfathers94@users.noreply.github.com>
1 parent c81e7e8 commit a2e1915

2 files changed

Lines changed: 1 addition & 1 deletion

File tree

0 Bytes
Binary file not shown.

src/review/predicted-gate-calls.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
// src/review/predicted-gate-agreement.ts for the read/join side). Structurally a sibling of
55
// src/review/contributor-calibration.ts: `review_audit` (migrations/0049) is DELIBERATELY actor-login-free
66
// (feeds the anonymized orb-collector export), so this is its own separate, LOCAL-ONLY table
7-
// (migrations/0132) -- never wired into exportOrbBatch or any other cross-instance/public export path.
7+
// (migrations/0137) -- never wired into exportOrbBatch or any other cross-instance/public export path.
88
//
99
// UNLIKE contributor-calibration.ts's per-commit dedup (a re-run at the same head_sha replaces its prior row),
1010
// every predict_gate call gets its OWN row here: there is no commit to dedup against pre-submission, and a

0 commit comments

Comments
 (0)