chore(meta): pql changelog — T-1204 to review

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-26 12:55:43 +02:00
parent 1f199b9717
commit d20ae38b74
2 changed files with 2 additions and 0 deletions
@@ -3131,3 +3131,4 @@ Batch-7 Si pre-answer (2026-07-25): the ticket''s question (1) is RESOLVED — t

 SWEEP COMPLETE (2026-07-25/26). Root cause pinned to ONE commit: f4c72e148 (2026-03-13, ''update all 18 briefings for v0.2 pivot'') — adjacent-id transcription slips from the Where''s the Fun? workshop batch (eea3f3cf2), copied forward by every later briefing-maintenance pass, never a renumbering. Eleven mis-citations fixed on main across five briefings: gore.md (D-131->D-130 emergent-moral-arc — lead-verified against D-130''s near-verbatim body; D-131->D-136 first-moment), mellanie.md (D-131->D-136, D-134->D-126 x2), ozzie.md (D-126->D-134, D-131->D-136, D-134->D-126), stig.md (D-126->D-134 x2, D-131->D-136), nigel.md (D-136->D-137 x3, plus a knock-on the sweep''s grep could not see: D-137->D-120 x2 ''no skill ceiling'' — found when the D-136->D-137 fix would have created contradictory D-137 citations in one file; D-120 verified as the real record, scope.md, itself SUPERSEDED). The slip family: D-126<->D-134 swapped; D-136 as D-131; D-137 as D-136; D-130 as D-131; D-120 as D-137. Sprint/discussion archives verified already-correct (all postdate the workshop and cite current meanings) — no annotations needed. Governance records themselves correct, untouched. Remaining 13 briefings from the same commit: T-1205.', NULL, '2026-07-26 10:50:32', '2026-07-26 10:50:32.969', '2026-07-26 10:50:32.969', NULL, '735a5bcd8dbce0897f4a77a76ff3ff3b', 2) ON CONFLICT(hash) DO NOTHING;
 INSERT INTO ticket_history (ticket_record_id, field, old_value, new_value, changed_by, changed_at, created_at, updated_at, deleted_at, hash, canonical_version) VALUES ('06FSP4MX7C66N76V31EB88YC78', 'status', 'in_progress', 'done', NULL, '2026-07-26 10:50:38', '2026-07-26 10:50:38.896', '2026-07-26 10:50:38.896', NULL, 'a73745109833b6478ce0d7ff2ed673b5', 2) ON CONFLICT(hash) DO NOTHING;
+INSERT INTO ticket_history (ticket_record_id, field, old_value, new_value, changed_by, changed_at, created_at, updated_at, deleted_at, hash, canonical_version) VALUES ('06FSP7HT5ES8D83VZA6ETACRAW', 'status', 'in_progress', 'review', NULL, '2026-07-26 10:55:32', '2026-07-26 10:55:32.378', '2026-07-26 10:55:32.378', NULL, '77078d2928d2421bb00ca4e4dcc49faa', 2) ON CONFLICT(hash) DO NOTHING;
@@ -5308,3 +5308,4 @@ INSERT INTO tickets (record_id, type, parent_record_id, title, description, stat
 Batch-7 Si pre-answer (2026-07-25): the ticket''s question (1) is RESOLVED — the pql migration did NOT renumber decision ids. tooling/pql-migrate/restructure_decisions.py''s own docstring states the migration is token-preserving (''the [D-NNN] bracket text and #d-nnn-... anchor stay byte-identical'' — only file locations and link paths changed), and seed_tickets.py preserves decision_ref verbatim. Therefore the D-126/D-131 drift is write-time mis-citation in the era documents (or later reuse/repurposing through ordinary record editing), and the sweep scope is exactly D-126/D-131 (plus any other ids the sweep itself surfaces as suspicious), not a migration-derived affected set. Start at step (2).

 SWEEP COMPLETE (2026-07-25/26). Root cause pinned to ONE commit: f4c72e148 (2026-03-13, ''update all 18 briefings for v0.2 pivot'') — adjacent-id transcription slips from the Where''s the Fun? workshop batch (eea3f3cf2), copied forward by every later briefing-maintenance pass, never a renumbering. Eleven mis-citations fixed on main across five briefings: gore.md (D-131->D-130 emergent-moral-arc — lead-verified against D-130''s near-verbatim body; D-131->D-136 first-moment), mellanie.md (D-131->D-136, D-134->D-126 x2), ozzie.md (D-126->D-134, D-131->D-136, D-134->D-126), stig.md (D-126->D-134 x2, D-131->D-136), nigel.md (D-136->D-137 x3, plus a knock-on the sweep''s grep could not see: D-137->D-120 x2 ''no skill ceiling'' — found when the D-136->D-137 fix would have created contradictory D-137 citations in one file; D-120 verified as the real record, scope.md, itself SUPERSEDED). The slip family: D-126<->D-134 swapped; D-136 as D-131; D-137 as D-136; D-130 as D-131; D-120 as D-137. Sprint/discussion archives verified already-correct (all postdate the workshop and cite current meanings) — no annotations needed. Governance records themselves correct, untouched. Remaining 13 briefings from the same commit: T-1205.', 'done', 'medium', 'clerk', 'server', NULL, '2026-07-25 20:58:36.219', '2026-07-26 10:50:38.896', NULL, 'eb63bfa9711770fedfcecd1773145fad', 2) ON CONFLICT(record_id) DO UPDATE SET type=excluded.type, parent_record_id=excluded.parent_record_id, title=excluded.title, description=excluded.description, status=excluded.status, priority=excluded.priority, assigned_to=excluded.assigned_to, team=excluded.team, decision_ref=excluded.decision_ref, updated_at=excluded.updated_at, deleted_at=excluded.deleted_at, hash=excluded.hash, canonical_version=excluded.canonical_version WHERE excluded.updated_at > tickets.updated_at OR (excluded.updated_at = tickets.updated_at AND excluded.hash > tickets.hash);
+INSERT INTO tickets (record_id, type, parent_record_id, title, description, status, priority, assigned_to, team, decision_ref, created_at, updated_at, deleted_at, hash, canonical_version) VALUES ('06FSP7HT5ES8D83VZA6ETACRAW', 'story', '06FB0TNSRXDCJS4P9Z5JQ1DAAM', 'Furniture/props asset production', 'Per-class production story (T-1049 breakdown, batch 6). Brief: docs/assets/briefs/furniture-props.md — interior furniture + small props (manifest categories furniture|props), D-257 toon treatment, conventions.md naming/mask/footprint_tiles rules. FIRST acceptance: promote + rename the 4 promotable spike GLBs (baroque_table, modernist_chair, scifi_desk + props/lion_statue) into client/assets/models/ + manifest.json per D-241 — no new generation needed; vw_beetle stays excluded (Q-067 car deferral, see briefs/deferred.md). Note: spike GLB binaries are gitignored — regenerate or restore locally at promotion time per the spike README.', 'review', 'medium', 'justine', 'visual', NULL, '2026-07-25 21:11:17.291', '2026-07-26 10:55:32.377', NULL, '474e9e9adcb6e92a49c2e579afc16c0f', 2) ON CONFLICT(record_id) DO UPDATE SET type=excluded.type, parent_record_id=excluded.parent_record_id, title=excluded.title, description=excluded.description, status=excluded.status, priority=excluded.priority, assigned_to=excluded.assigned_to, team=excluded.team, decision_ref=excluded.decision_ref, updated_at=excluded.updated_at, deleted_at=excluded.deleted_at, hash=excluded.hash, canonical_version=excluded.canonical_version WHERE excluded.updated_at > tickets.updated_at OR (excluded.updated_at = tickets.updated_at AND excluded.hash > tickets.hash);