basquetWi + New ticket
movilba MOVILBA-724

Historial del vehículo: alinear el orden de secciones con las categorías

Done normal cmcoder04-mba-l-ca

Tracker 2026-10-07-1115, Pendientes row 65 (Para Elazar; respondents Lean y Paula): asks whether sections in Historial del Vehiculo can use the same order as ficha categories: Informacion general, Empresa, Equipamiento Tecnologico, Numeros de Serie y Componentes, Informacion Operativa, Estado Actual. This is absent from the canonical tracker. The downloaded row incorrectly carries MOVILBA-716, already used by the completed SQLite tracker-script item; do not reuse that ref. No implementation or UX acceptance has been assessed.

Sub-tickets

No sub-tickets.
+ Add sub-ticket

Activity

  • coder04-mba-l-ca created · 1w ago
  • coder03-mba-l-cc assigned · 1w ago
    coder04-mba-l-ca / coder
  • coder04-mba-l-ca statusChanged · 1w ago
    History field display order follows ficha categories; scoped change ready for audit.
  • audit-mba-l-cc audited · 1w ago
    audit fail: Reviewed exact diff: rutap-history-fields.ts FICHA_HISTORY_ORDER + sort, rutap-history-values.test.ts new assertion
    payload
    {"scope":"Reviewed exact diff: rutap-history-fields.ts FICHA_HISTORY_ORDER + sort, rutap-history-values.test.ts new assertion","outcome":"fail","evidence":"consumption (field in RUTAP_HISTORY_FIELDS, has definitions entry) is absent from FICHA_HISTORY_ORDER; displayRank.get returns undefined -> MAX_SAFE_INTEGER, so it sorts after openpassMountingKit, outside any ficha category. Test only samples 6 fields, does not catch this. Verified via node: missing=['consumption'].","reportRef":null}
  • audit-mba-l-cc audited · 1w ago
    audit fail: Re-reviewed diff after correction; ran test myself
    payload
    {"scope":"Re-reviewed diff after correction; ran test myself","outcome":"fail","evidence":"pnpm exec tsx --test src/lib/rutap-history-values.test.ts fails: asserted [0,3,6,17,31,41] vs actual [0,3,6,17,32,42]. Consumption field was correctly added to the order, but hardcoded test indices for lineNumber/state were not bumped for the shift. Field-coverage is now correct (47/47, no missing); only the stale index assertion is wrong.","reportRef":null}
  • audit-mba-l-cc audited · 1w ago
    audit pass: Final diff re-reviewed, ran test myself
    payload
    {"scope":"Final diff re-reviewed, ran test myself","outcome":"pass","evidence":"pnpm exec tsx --test src/lib/rutap-history-values.test.ts: 54/54 pass. consumption correctly placed, completeness guard (every HISTORY_FIELDS field has a display rank) is real coverage. Non-blocking: the 6-field position assertion derives expected via HISTORY_FIELD_DISPLAY_ORDER.indexOf on the same array it sorts by, so it can never fail regardless of category content - verifies sort mechanics, not category-order intent. No lint/typecheck run (not in my scope).","reportRef":null}
  • audit-mba-l-cc audited · 1w ago
    audit pass: Re-reviewed typecheck-fix revision (categoryBoundaryFields as const tuple), same logic as prior PASS
    payload
    {"scope":"Re-reviewed typecheck-fix revision (categoryBoundaryFields as const tuple), same logic as prior PASS","outcome":"pass","evidence":"pnpm typecheck clean (tsc --noEmit, next typegen ok). pnpm exec tsx --test rutap-history-values.test.ts: 1/1 pass. No functional change from prior PASS; only typing. Prior note re: tautological position-assertion still applies, non-blocking.","reportRef":null}
  • coder03-mba-l-cc completed · 1w ago
    v5.6.180 shipped PROD+DEV+pod, fleet parity confirmed (serviceId 25434->25571, (25571-911)/137=180), oc rollout status successfully rolled out
  • coder03-mba-l-cc note · 1w ago
    Tracker: moved Pendientes->Resueltos (Solucionado, desplegado v5.6.180) in canon 2026-10-08-1046.
feature
1w ago by coder04-mba-l-ca
1w ago
2026-10-07 14:48