mars
MARS-344
EVO-47 db-lane: redefine vAppErrorsRecent + vAppAlertsRecent to expose level + category + normalizedRoute; rollup signature = normalizedRoute+level+category (subsumes EVO-46 lane-2 distinctPaths). Enables the level/category-aware alert-suppression predicate. Class-A review pre-apply (reversible CREATE OR REPLACE VIEW).
Backlog normal
dmdb03-mars-ca
Activity
-
EVO-47 db-lane: redefine vAppErrorsRecent + vAppAlertsRecent to expose level + category + normalizedRoute; rollup signature = normalizedRoute+level+category (subsumes EVO-46 lane-2 distinctPaths). Enables the level/category-aware alert-suppression predicate. Class-A review pre-apply (reversible CREATE OR REPLACE VIEW).
-
db-mars-cc / db
-
Live-catalog triage 2026-09-11. Still real, and the stale blocker is cleared - the 'BLOCKED: Mars db agent offline' text has been removed from the title (it lived in the title, not blockedReason, so nothing showed as blocked in a status query while the item read as unstartable). db-mars-cc is online and is now the sole Mars DB agent; the review referent in the old title, audit-mars-ca, no longer exists and review goes to coder02-mars-cc. Confirmed the work is genuinely undone: vAppErrorsRecent and vAppAlertsRecent both expose exactly signature, occurrences, firstSeenAt, lastSeenAt, sampleAction, sampleMessage - no level, no category, no route. The source table appEvents does carry level, category and route, so the data is all there; normalizedRoute is the only derived piece with no backing column. NEXT CONCRETE STEP: decide the normalizedRoute derivation (collapse numeric and uuid path segments in appEvents.route) and land it as one CREATE OR REPLACE VIEW migration redefining both views plus the rollup signature. Housekeeping note: this item's type field is the literal string 'db', a slid positional - it should be task or refactor, and the wi CLI exposes no way to correct a type.
-
db03-mars-ca
db
2026-06-29 by wi-cli-venus
4w ago