fix(store): project-scope metrics/evolution writers + composite-PK migration#92
Merged
epicsagas merged 2 commits intoJun 19, 2026
Merged
Conversation
This was referenced Jun 19, 2026
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
Close the project-scoping gap so the evolution dashboard reflects the selected project across the metrics/evolution panels. Closes #84 (root cause); partially addresses #83 (file-based reader arms tracked in #91).
Changes
metrics_statewriters (save_metrics_pool/save_metrics_direct) bindproject;INSERT OR REPLACE→ON CONFLICT (key, project).metrics_statePK(key)→(key, project)via idempotent table-rebuild migration (_harness_meta.metrics_pk_v2, transaction-wrapped,pragma_table_infoPK detection, DDL synced).score_history: scopedDELETE ... WHERE project = ?+projectcolumn bind (no cross-project wipe).evolution_recordswriter (insert_record_pool) bindsproject;reflect.rscallers passproject_slug().serve.rsget_adaptation_landscape→ scoped reader.load_metrics_scoped_poolskill_attribution query: dropWHERE project(column absent; tracked in dashboard: thread project param through file-based evolution readers (seesaw/variants/snapshot/manifests) #91).Spec / Pipeline
SPEC-20260619004500.md · PIPELINE-20260618165444 (orbit, council mode)
Acceptance Criteria
AC1 ✅ AC2 ✅ (composite PK via isolation test) AC3 ✅ AC4 ⚠ (landscape scoped; file-based arms → #91) AC5 ✅
Test Plan
Follow-ups
#91 — file-based reader arms (seesaw/variants/snapshot/manifests) + skill_attribution project column.