venus
VENUS-247
Migrate call-sites onto canonical view names + drop old names (vAppLog25/50/100→vAppEvents25/50/100, vErrorsLast25/vAppErrorsRecent-dedup→vAppErrorsRecent raw-tail, vFrictionEvents1w→vUserFrictionEvents)
Done normal
unassigned
Fleet-wide identical-view-name directive (Elazar CLI override on bs-mrlmdbdi7uy, relayed via coder-pluto-cc, 2026-07-15). db-venus-cc creating 3 canonical-named dup views alongside existing ones (both live, no drop yet). Follow-on: migrate all call-sites currently referencing the old names onto the canonical names, then drop the old views. Also update shared/md/venus-commons.md §Recent App-Events Views + §Friction Views sections to reflect canonical names once migrated. Mirrors PLUTO-550's migrate-and-drop pattern.
Questions
No questions.
Activity
-
Elazar go, 2026-07-16
-
Call-site migration complete (0 old-name refs in src/scripts, verified fresh). DDL view-drop DEFERRED: the rename mapping handed down (vAppLog25->vAppEvents25, vFrictionEvents1w->vUserFrictionEvents) CONTRADICTS checked-in venus-commons.md, which still names vAppLog25/50/100 + vFrictionEvents1w as canonical. Coder won't hand db-venus-cc a destructive drop-list on an unreconciled mapping. Needs shared/md/evolutiva-db-views.md (coder-mars-cc SSOT) reconciliation first - PM escalating.
-
Coder lane done: call-site migration was already complete (0 live query refs), 8 stale comment refs refreshed to canonical (SHA 0d5b893/v0.97.8). Handed db-venus-cc the verified drop list: vFrictionEvents family (6 views, vFrictionDigest+vFrictionTop depend on vFrictionEvents1w — drop dependents first) + vErrorsLast25. Doc-flip in evolutiva-db-views.md follows the actual DROP, not this comment SHA.
-
Fully shipped: call-site migration (0 live refs, 8 stale comments refreshed SHA 0d5b893/v0.97.8) + DDL drop (db-venus-cc dropped all 9 old-named views, verified via pg_views: old names gone, 4 canonical live). coder-mars-cc DMed to flip venus rows in evolutiva-db-views.md.
venus
4w ago by wi-cli-venus
4w ago
2026-07-16 14:35