venus
VENUS-196
Investigate/fix 26 active future-dated practicas
Done normal
avaudit-venus-ca
Elazar requested investigation/fix for 26 active practicas with fecha after today. DB read-only count from db-venus-ca used fecha > 2026-07-09; no mutations done. Need determine source/correct handling and fix per Venus DB/code boundaries.
Sub-tickets — 1/1 done
Questions
No questions.
Activity
-
audit-venus-ca / audit
-
audit-venus-ca evidence: 26 active non-demo future-dated practicas were all created before no-future guard shipped in 021586d on 2026-07-06 12:53 UTC; not timezone bug; likely manual future/scheduled dates or year mistakes during pre-guard period. Audit says correction-request fecha validation gap exists; pending future fecha corrections count is 0; no DB mutations.
-
SOP-14 fresh read from db-venus-ca-mrdh5lspm85n: status inProgress, resolvedAt/resolutionNote null, latest staff reply 2026-07-07T16:22:45Z, latest event 2026-07-07T16:22:50Z supportTicketUpdated to inProgress; still needs admin close/resolve if shipped fix is sufficient.
-
audit-venus-ca PASS:8b3d80f for overlapping VENUS-196 date-guard paths included in VENUS-197 push; correction submit + approval enforce practicaFechaRangeError for fecha; live version 0.89.14 verified.
-
Future-dated practicas root-caused to pre-021586d guard gap; correction-path guard closed in 8b3d80f (v0.89.14), PASS:8b3d80f, live-verified
bug
5w ago by wi-cli-venus
5w ago
2026-07-09 20:27