DEV test case FB444EP needs exact AGRALE MT 15.0 V 5500 catalog row

Sub-tickets

Activity

• coder04-mba-l-ca created · 1w ago
  parent=#3512
• coder04-mba-l-ca statusChanged · 1w ago
  Await exact-model research/catalog row for FB444EP; then coder04 runs its Alta+Modificación pair.
• db04-mba-l-ca note · 1w ago
  2026-10-05 SELECT-only PROD then DEV recheck. public.chasis id36 (historical exact MT 15.0 V 5500) is ABSENT in both live tables, not a row currently soft-deleted and available for reactivation. PROD live AGRALE ids: 130 MT 15.0 LE, 134 MT 15; DEV: 130 MT 15.0 LE, 140 MT 15. Exact resolver terna (AGRALE, MT 15.0 V 5500, GO/up124) currently approved to PROD id134 / DEV id140. Neither base has vehiculos or normalized-history refs to id36; DEV has no existing FB444EP vehicle. Therefore do not substitute id130/134/140 or merely clear borrado_en. Need proxy's authoritative Agrale/homologation evidence establishing whether MT 15.0 V 5500 is a distinct exact model; if yes, create one PROD catalog id below 1e9, copy same literal id to DEV per MOVILBA-625 policy, and repoint only the exact resolver terna after audit. No write made.
• db04-mba-l-ca note · 1w ago
  2026-10-05 research route corrected: proxy-mba-w-cc declined the Agrale/homologation lookup as outside app-browser automation role; sent exact VIN/model question to researcher-mba-l-cc. Catalog creation and resolver change remain held until authoritative model identity/distinction is documented. No DB write.
• researcher-mba-l-cc note · 1w ago
  MOVILBA-710 research result: "AGRALE / MT 15.0 V 5500" is NOT a distinct model. It is AGRALE MT 15.0 LE V 5500 with "LE" dropped -- same truncation class already fixed elsewhere in this ticket family (OH1618/55, MT17.0 LE V6000 variants). Evidence: 1. Agrale's own manufacturer page (agraleargentina.com.ar/chasis-buses/mt-150-le) and its datasheet (megacar.com.ar/wp-content/uploads/2021/02/mt_150_le_.pdf) document exactly ONE chassis under this PBT/wheelbase combination: "MT 15.0 LE V 5500" -- "V 5500" is the wheelbase code (5500mm), not a separate trim. No manufacturer or dealer source anywhere publishes a bare non-LE "MT 15.0 V 5500." The only bare "MT15" hit found is an unrelated older Euro-3-era chassis (different generation, no "V 5500" suffix) -- not this vehicle's family. 2. CNRT catalog (chasis-modelo.tsv) normalizes "MT 15.0 LE V 5500" (and two trailing-space variants) to MT 15.0 LE, Asignado. No bare "MT 15.0 V 5500" row exists there either, consistent with it never having been a separate catalog entry anywhere outside this one book row. 3. VIN family match: FB444EP's VIN 8BBC59B1ARM006598 shares the WMI+VDS prefix 8BBC59B1A with AC029ZU's VIN 8BBC59B1AJM002560, which chasis-equivalencias.md already documents (line 63, researched/confirmed 2026-09-24) as AGRALE MT 15.0 LE V 5500 -- same chassis line, year-code digit differs (J vs R). Same methodology as the OH1718 VIN match just applied in MOVILBA-365. CONCLUSION: historical id=36 was most likely a redundant duplicate label for the same live MT 15.0 LE row, not a genuinely distinct model -- no manufacturer evidence supports recreating it as distinct. The exact resolver terna should repoint to the live MT 15.0 LE row (PROD id130 / DEV id130), NOT to the current generic bare "MT 15" (PROD id134 / DEV id140), which is a different, less-specific family per the same CNRT/manufacturer evidence. No DB write made; db04/coder04 to apply after audit per standing protocol.
• db04-mba-l-ca note · 1w ago
  Researcher 2026-10-05 finding accepts AGRALE MT 15.0 V 5500 as omitted-LE spelling of existing MT 15.0 LE V 5500, based on Agrale page/datasheet, CNRT chasis-modelo.tsv, and VIN family; no distinct catalog row should be created. Exact resolver correction drafted at /data-lezama/movilba/migration-evidence/2026-10-05-movilba-710-agrale-mt15-v5500-resolver-PROD-Y-DEV.sql SHA256 d41989395adebb1cbf8059de273cbfc784e65520c4162bd396df348b8ca396ea. Only AGRALE/MT 15.0 V 5500/GO row changes: PROD id134 -> 130, DEV id140 -> 130, with evidence updated; raw book and catalog rows unchanged. Same file ROLLBACK rehearsal PASS PROD then DEV, both printed exact old -> new notice. No committed DB write yet; audit requested.
• coder04-mba-l-ca note · 1w ago
  2026-10-05 17:38 ART: proxy-mba-w-cc declined the manufacturer/homologation research as outside its proxy role (tag proxy-mba-w-cc-muvpoazham8g). Research request redirected to researcher-mba-l-cc for an authoritative source on exact AGRALE MT 15.0 V 5500 (FB444EP, VIN 8BBC59B1ARM006598), explicitly distinguishing it from live MT 15 and MT 15.0 LE. db04 retains the DEV catalog resolution work; do not make a near-model substitution.
• audit-mba-l-cc audited · 1w ago
  audit pass: resolver SQL read in full; cross-checked against researcher's bwi evidence note
  payload

  {"scope":"resolver SQL read in full; cross-checked against researcher's bwi evidence note","outcome":"pass","evidence":"sha256 matches cited; gate checks target db, live chasis130=MT15.0 LE, positive control LE V5500 terna unchanged, old evidence text match before UPDATE; single-row UPDATE id134/140->130 with GET DIAGNOSTICS=1 check; default ROLLBACK. Researcher sources: Agrale mfr page+datasheet, CNRT chasis-modelo.tsv, VIN WMI/VDS family match to AC029ZU (same methodology as MOVILBA-365)","reportRef":null}

• coder04-mba-l-ca note · 1w ago
  Correction, 2026-10-05 17:38 ART: db04's fresh PROD-then-DEV catalog census supersedes my earlier note and the child description's historical-id claim: chasis id36 is ABSENT from both catalog tables now. Exact key AGRALE / MT 15.0 V 5500 / GO resolves instead to generic MT 15 (PROD id134, DEV id140), which must not be exposed as the exact model. No FB444EP vehicle exists yet in DEV. Do not restore/infer id36 or use MT 15/MT 15.0 LE as substitutes. Proxy declined the manufacturer research; researcher-mba-l-cc has the authoritative-source request. No DB write. Next: obtain sourced model identity, then db lane determines PROD literal catalog ID and copied DEV row plus exact resolver correction, audit before write.
• db04-mba-l-ca note · 1w ago
  2026-10-05 APPLIED audit-PASSed SHA256 d41989395adebb1cbf8059de273cbfc784e65520c4162bd396df348b8ca396ea. PROD movilba first: exact AGRALE/MT 15.0 V 5500/GO resolver 134 -> 130, COMMIT; post-read exact key and existing LE V 5500 positive-control key both id130. Then DEV movilba_dev: exact key 140 -> 130, COMMIT; identical post-read. public.chasis rows, raw book text and other resolver keys untouched. SQL placed at docs/migrations/2026-10-05-movilba-710-agrale-mt15-v5500-resolver-PROD-Y-DEV.sql byte-identical to audited/applied artifact. FB444EP Alta+Modificación test pair can now be run by coder04; no new catalog row/id was needed after manufacturer research.
• coder04-mba-l-ca note · 1w ago
  Research and resolver work complete; DB lane applied the audit-PASSed exact-key correction PROD then DEV (resolver id130 in both). Coder04 ran the DEV01 FB444EP Alta + paired Modificacion through the live UI. Alta readback: dominio FB444EP, NUDO/Línea 107, chassis id130 AGRALE MT 15.0 LE (the sourced canonical equivalent of book MT 15.0 V 5500), M3, VIN 8BBC59B1ARM006598, expediente EX-2026-39357754-GCABA-DGGSM, fecha 2026-06-09, interno 7777, ID MDVR 1074115. Modificacion readback: interno 7777->3333, ID MDVR 1074115->777774, same expediente, fecha 2026-07-09; ficha shows Desde 09/07/2026 and both change lines. Evidence: /data-lezama/movilba/evidencia/MOVILBA-359/FB444EP-alta-readback-2026-10-05.json and FB444EP-mod-readback-2026-10-05.json. No credentials recorded.
• coder04-mba-l-ca completed · 1w ago
  Exact model source researched; audited resolver correction applied PROD+DEV; FB444EP Alta+Modificacion completed and read back on DEV01. Evidence paths in latest note.