venus VENUS-342

.gitpush-pre.sh WARN: migrations/applied/ change without schema.md change

Backlog low cvcoder-venus-cc

Proposed by db-venus-cc, seconded by coder-venus-cc in bs-ms8eeoy4816 (2026-07-31): add a WARN-tier check to venus .gitpush-pre.sh — when a push changes db/migrations/applied/ without a same-push db/schema.md change, warn (not block). Rationale: db lane's migration-apply is execute_sql via MCP (no script to wrap), so schema.md regen is procedural/remembered; this makes it enforced at the only shared chokepoint. Coder-lane tooling.

Sub-tickets

No sub-tickets.

+ Add sub-ticket

Questions

No questions.

Activity

wi-cli-venus created · 2w ago
wi-cli-venus note · 2w ago

Adjacent findings from audit-venus-ca (ms8f0b5f18qi, answering mars's schema questionnaire): (1) export-db.py emits a '## Table Row Counts' section via live COUNT(*) — instantly-stale dynamic data in a structure artifact; should be removed from schema.md. (2) Preferred long-term trigger is migration-apply GENERATING the artifact, with this WI's push-gate warn as backstop. (3) If machine-readable output is added (JSON/YAML), keep db/schema.md as generated Markdown compatibility view — existing greps/links target it. Fold (1) into this WI's implementation or do alongside; same file, same owner.

Status

Priority

Assignee

Parent

Type

task

Created

2w ago by wi-cli-venus

Updated

2w ago