Se acepta una fecha de expediente en el futuro: se cargo 01/01/3050

Sub-tickets

Activity

• wi-cli-venus created · 3w ago
• coder03-mba-l-cc assigned · 3w ago
  coder03assistant-mba-l-ca / coder
• coder03assistant-mba-l-ca statusChanged · 3w ago
  coder03assistant-mba-l-ca | 2026-09-24 05:09 ART. DEV code: createColectivo forwards fechaExpediente to createColectivo history.fechaAlta; updateColectivo forwards it to applyColectivoEditWithHistory, which writes event fechaAlta and for BAJA also fechaBaja. Neither service path bounds the supplied date. Building a red service-boundary control before the fix; LP680FF remains untouched.
• audit-mba-l-ca audited · 3w ago
  audit fail: Uncommitted createColectivo/updateColectivo fechaExpediente service guard and focused action test; no DB or HTTP write exercised.
  payload

  {"scope":"Uncommitted createColectivo/updateColectivo fechaExpediente service guard and focused action test; no DB or HTTP write exercised.","outcome":"fail","evidence":"audit-mba-l-ca | 2026-09-24 05:13 ART. node --test tools/tests/colectivo-expediente.test.cjs: 7/7 pass; same under TZ=Pacific/Kiritimati: 7/7; pnpm run typecheck: exit 0; git diff --check on two changed files: exit 0. Code reaches both repository calls and for edit BAJA repository sets fechaAlta=fechaBaja=fechaEventoPersistida, but repository is mocked in these tests. Blocking: MOVILBA-547 explicitly requires choosing today versus near-future ceiling before implementation; no decision appears in bwi events, yet code hardcodes today. Also node -e date check shows 0000-01-01 round-trips through new Date/toISOString, so validator admits year zero despite claimed real calendar date. Add the ceiling decision and a rejecting control for 0000-01-01; re-audit. LP680FF untouched.","reportRef":null}

• coder03assistant-mba-l-ca progress · 3w ago
  coder03assistant-mba-l-ca | 2026-09-24 05:18 ART. Business decision for this delegated fix: fecha_expediente ceiling is the current calendar day in America/Argentina/Buenos_Aires, inclusive; no near-future grace period. An expediente date represents an already issued filing, and DEV LP680FF includes the near-future 2026-09-30 case as a reported error, not a scheduled filing. Apply at create and edit service boundaries. No independent ceiling on fecha_baja: a future effective Baja may be legitimate; this app edit path derives Baja event date from fecha_expediente, so a future expediente supplied for a Baja edit is rejected under the same input rule. Existing LP680FF rows remain untouched. Audit FAIL 05:13 also found year 0000 accepted by calendar parser; add a red control and reject it before re-audit.
• coder03assistant-mba-l-ca decision · 3w ago
  coder03assistant-mba-l-ca | 2026-09-24 05:22 ART. Elazar explicitly confirmed to audit-mba-l-ca at 05:21 ART: block expediente dates after the current day in America/Argentina/Buenos_Aires; no future grace. This confirms the ceiling recorded in the 05:18 progress event and implemented in create/edit service validation. No separate future-date prohibition on fecha_baja was decided; app BAJA edits that use a future fecha_expediente are blocked through that same input validation. Stakeholder confirmation in tracker is being handled by audit; do not treat that pending confirmation as permission to admit future dates.
• coder03-mba-l-cc decision · 3w ago
  coder03-mba-l-cc 2026-09-24 - Decision recorded, relayed by audit-mba-l-ca at 05:21 ART as Elazar's explicit word. Expediente dates AFTER TODAY IN ART are REJECTED, with no forward grace window. That closes the question audit held this item's FAIL on. audit is putting a confirmation question to Eugenia in the tracker; that is a confirmation, not a gate, and it does not hold the code. Second bound, no decision needed from anyone: 0000-01-01 is accepted by the validator today and must be rejected. The floor is to be taken from the book rather than invented - measure the real minimum Fecha_Alta/Fecha_Baja in the current book and set the floor below it, so a legitimately old expediente is never refused. Assigned to coder03assistant-mba-l-ca. Both bounds need a control seen to FAIL against the prior code: today+1 accepted pre-fix and rejected post-fix, same for 0000-01-01. A green-only test is not a control here. Named risk: 'after today' evaluated in UTC rejects a valid same-day ART expediente for three hours every night, so the comparison is anchored to ART explicitly and that anchoring is pinned by its own test.
• audit-mba-l-ca audited · 3w ago
  audit pass: audit-mba-l-ca | 2026-09-24 05:27 ART. Uncommitted shared-tree MOVILBA-547 service date guard and focused action tests only; create/edit path through mocked repository, no real DB/HTTP write. Excludes concurrent MOVILBA-555 changes.
  payload

  {"scope":"audit-mba-l-ca | 2026-09-24 05:27 ART. Uncommitted shared-tree MOVILBA-547 service date guard and focused action tests only; create/edit path through mocked repository, no real DB/HTTP write. Excludes concurrent MOVILBA-555 changes.","outcome":"pass","evidence":"Reviewed src/services/vehiculos.ts validarFechaExpediente and both createColectivo/updateColectivo call sites before writes: YYYY-MM-DD calendar validation, year >=0001, date <= ART today inclusive. Reviewed tools/tests/colectivo-expediente.test.cjs: tomorrow and year-zero rejected on both paths without writes; today accepted; fixed UTC-to-ART midnight boundary. Independently ran node --test tools/tests/colectivo-expediente.test.cjs: exit 0, 13/13. git diff --check on the two files: exit 0. Pre-fix negative controls (tomorrow and year zero accepted) reported by implementing lane, not rerun in this audit. No real row or browser path exercised.","reportRef":null}

• coder03assistant-mba-l-ca progress · 3w ago
  coder03assistant-mba-l-ca | 2026-09-24 05:26 ART. DEV shared tree: src/services/vehiculos.ts validates fechaExpediente on createColectivo and updateColectivo before repository writes: real YYYY-MM-DD, floor 0001-01-01, ceiling current day in America/Argentina/Buenos_Aires inclusive. Elazar decided no future grace at 05:21 ART (decision event). Source book /data-lezama/movilba/libro/2026-09-24-0434-parque-rutap.xlsx Base!AH Fecha_Alta: 5,538 datetime cells, minimum 2025-06-19; Base!AI Fecha_Baja: 3,939 datetime cells, minimum 2025-07-08; no non-date populated cells. The 0001-01-01 floor is below both minima and accepts the earliest four-digit Gregorian date. Red against prior code: tomorrow create/edit accepted (2 failed controls); 0000-01-01 create/edit accepted (2 failed controls). Green now: focused action suite 13/13, source suite 36/36, targeted ESLint and git diff --check exit 0; fixed ART midnight test maps 2026-09-25T02:59:59Z to Sep 24 and 03:00:00Z to Sep 25. No independent fecha_baja bound; BAJA edit with a future expediente is rejected via same validation. LP680FF reproduction rows unchanged. audit-mba-l-ca PASS event 08:26:35Z: mocked create/edit path only; no DB, HTTP, or browser write exercised. Ready for coder03 commit/deploy; item remains inProgress until deployed verification.
• coder03-mba-l-cc commit · 3w ago
  coder03-mba-l-cc 2026-09-24 - Shipped to DEV as 03155317, v5.6.47, health gate OK serving patch 47. Paths: src/services/vehiculos.ts, src/app/vehiculos/agregar/colectivo/page.tsx, tools/tests/colectivo-edit-load.test.cjs. test:source 37/37 and test:tools 101/101, both exit 0. Implemented by coder03assistant-mba-l-ca, audit-mba-l-ca PASS on both with its own rerun. Item stays inProgress: what is proven is that the service REJECTS, not that a real colectivo was created or that DEV holds no bad rows - deployed verification is still owed. Unrelated fix carried in the same commit and stated so it is not mistaken for part of either item: colectivo-edit-load.test.cjs:242 was already red on dev before these patches, because MOVILBA-362 made the expediente mandatory and the client guard began firing before the server rejection the case exists to check; it survived because no ship path runs test:tools.
• coder03assistant-mba-l-ca progress · 3w ago
  coder03assistant-mba-l-ca | 2026-09-24 05:33 ART. Live tracker /data-lezama/movilba/import-reports/todo-rutap-importacion-prestaciones.xlsx, Para Eugenia!A11:F11: added question #87 asking Eugenia to confirm Elazar 24/09 rule: reject expediente dates after ART today on colectivo create/edit, no future grace. E11 PENDIENTE; D11 blank; F11 attributes criterion to Elazar and asks no source-book repair. Exact wording and target supplied by audit-mba-l-ca after checking live/downloaded Resueltos #34/#63/#76 and withdrawn #84. Before write, bwi show MOVILBA-547 was inProgress; this row is a question, not a claimed answer. Wrote under hub lock, verified workbook opens and A11:F11 exact, SHA-256 c4a2a4080997cc0b502b5add288453a109cd18ea540c5eda172f55c5af0cf232. SQLite import snapshot 11 (3672 cells); diff snapshot 10 to 11 shows only new Para Eugenia row #87, all other sheets unchanged.
• coder03-mba-l-cc note · 2w ago
  Eugenia confirmo el criterio, 2026-10-01, pregunta 87: 'Correcto.' - no se admiten fechas de expediente futuras, ni en alta ni en edicion. La pregunta queda cerrada del lado del negocio.
• coder03assistant-mba-l-ca progress · 2w ago
  coder03assistant-mba-l-ca | 2026-10-01 23:16 ART. Rechecked BWI decision: Eugenia confirmed #87 Correcto on 2026-10-01; future expediente dates are rejected. Existing audited service guard covers createColectivo and updateColectivo, with ART-today inclusive and YYYY-MM-DD/year>=0001 validation; shipped to DEV as 03155317/v5.6.47 per commit event. Audit PASS was focused mocked-path verification (13/13) and did not exercise DB/HTTP/browser. No new code diff; leave open pending any required live create/edit verification.
• coder03assistant-mba-l-ca blocked · 2w ago
  coder03assistant-mba-l-ca | 2026-10-01 23:42 ART. Code is deployed and focused audit verified mocked create/edit date validation, but no real DEV01 create or edit was exercised. Blocked on an authorized DEV01 account with write permission to create and edit a QA colectivo, then read back the saved date/history. The available account failed authentication and has VIEWER role per coder03 2026-09-28 measurement; no password reset requested.
• coder03-mba-l-cc note · 1w ago
  Stakeholder feedback, tracker online 2026-10-05 13:24 (Eugenia/Fabri), relayed by coder03: Verificado: 'genera el popup avisando: La fecha del expediente no puede ser anterior al evento de negocio vigente'.
• coder03-mba-l-cc unblocked · 1w ago
  cleared: coder03assistant-mba-l-ca | 2026-10-01 23:42 ART. Code is deployed and focused audit verified mocked create/edit date validation, but no real DEV01 create or edit was exercised. Blocked on an authorized DEV01 account with write permission to create and edit a QA colectivo, then read back the saved date/history. The available account failed authentication and has VIEWER role per coder03 2026-09-28 measurement; no password reset requested.
• coder03-mba-l-cc completed · 1w ago
  completed