Confirm Mercedes chassis designation for AB139OT

Sub-tickets

Activity

• db04-mba-l-ca created · 3d ago
  parent=#4621
• db04-mba-l-ca progress · 3d ago
  Added the lettered Eugenia question as row 10 of the local live tracker Pendientes, linked to MOVILBA-795 and import parent MOVILBA-794. The local workbook was updated and verified; no claim that it has been pasted into the online tracker. Pre-edit archive: archived/2026-10-13-115541-todo-rutap-importacion-prestaciones.xlsx. Post-edit stamped copy: 2026-10-13-115849-todo-rutap-importacion-prestaciones.xlsx.
• coder03-mba-l-ca statusChanged · 3d ago
  New tracker response received 2026-10-13: Eduardo Parodi's criterion says take the designation declared by the company rather than infer equivalence from technical paperwork. For AB139OT retain book value MERCEDES BENZ / OH 1621/62 / GO; determine the narrow exact catalog mapping needed for MOVILBA-794, without substituting 1621/55 or 1721/62. No DB write yet.
• coder03-mba-l-ca assigned · 3d ago
  db04-mba-l-ca / db
• db04-mba-l-ca progress · 3d ago
  Stakeholder criterion received: retain AB139OT declared MERCEDES BENZ / OH 1621/62 / GO, no inferred equivalence. Workbook SHA256 81874621 (Base!5571 only matching triple, 1 row); tracker CSV SHA256 8fc5dd47. Current PROD/DEV have live manufacturer id3, GO option id124, no exact chasis/resolver key. Draft default-ROLLBACK SQL docs/migrations/2026-10-13-movilba-795-ab139ot-declared-chassis-PROD-Y-DEV.sql SHA256 b452bc09eaf1e0653e528e2e7715d6232059e28c5f8d59be863875a154a5c7b2 creates distinct declared catalog label and exact approved resolver key, deriving per-base new ID. PROD then DEV rehearsals rc0, post-rollback catalog/resolver count 0 each. DEV nextval advanced into its documented >=1e9 test band despite ROLLBACK (sequence nontransactional); no catalog row survived. Audit verdict pending; no apply.
• audit-mba-l-ca audited · 3d ago
  audit pass: Focused static review of frozen SQL hash b452bc09eaf1e0653e528e2e7715d6232059e28c5f8d59be863875a154a5c7b2; independently verified pinned workbook row and tracker criterion. No database rehearsal or apply performed by audit.
  payload

  {"scope":"Focused static review of frozen SQL hash b452bc09eaf1e0653e528e2e7715d6232059e28c5f8d59be863875a154a5c7b2; independently verified pinned workbook row and tracker criterion. No database rehearsal or apply performed by audit.","outcome":"pass","evidence":"audit-mba-l-ca | 2026-10-13 ART: SQL SHA matches. Independently verified workbook SHA256 8187462151f626657c81f53691d0cd82153f92aeb3c565a016c2fff3e2edbd20 and Base row 5571: AB139OT / MERCEDES BENZ / OH 1621/62 / GO, VIN matches candidate, Fecha_Baja blank. CSV SHA256 8fc5dd4738d24e1d8e99571f8626e9345d01041633791deec928c966fe441952 includes MOVILBA-795 answer: follow company-declared designation, not inferred homologation. SQL creates a distinct exact catalog label and only the MERCEDES BENZ/OH 1621/62/GO resolver triple; no alias/repoint or other row mutation. Preconditions fail closed for wrong DB, nonunique maker/GO, normalizer drift, existing exact catalog/resolver key; postchecks exact approved row. db04 reports PROD→DEV default-ROLLBACK controls and postreads; not independently executed. Rollback removes table rows, but serial chasis.id nextval is nontransactional and leaves sequence gaps in both DBs; db04 reports DEV test-band impact. No catalog/resolver rows persist. Apply still requires source-hash verification before each run and the documented PROD-then-DEV order.","reportRef":null}

• coder03-mba-l-ca progress · 3d ago
  Parodi criterion implemented as distinct OH 1621/62 catalog label, not an alias. Exact audited SQL SHA b452bc09 applied PROD id146 and DEV id1000000001; AB139OT mapped in imported history. Both DB imports green. SQL recorded in repo c29a096c; fleet pod live confirmation pending.
• audit-mba-l-ca audited · 3d ago
  audit pass: Single post-push GitLab develop path/credential-pattern check at exact commit 98ca5f4f762f0926818cdacb335ba3930cf9106a; no application/database or deployment-health verification.
  payload

  {"scope":"Single post-push GitLab develop path/credential-pattern check at exact commit 98ca5f4f762f0926818cdacb335ba3930cf9106a; no application/database or deployment-health verification.","outcome":"pass","evidence":"audit-mba-l-ca | 2026-10-13 ART: Fetched origin/develop and checked FETCH_HEAD=98ca5f4f762f0926818cdacb335ba3930cf9106a. Sensitive/internal path scan and heuristic literal credential-pattern scan returned no matches. database/movilba_dev.dmp is present (40,204,909 bytes, blob 7863306d…); dump contents were not inspected, so this does not assert dump contents are credential/PII-free. No SQL/app code re-audit performed.","reportRef":null}

• coder03-mba-l-ca progress · 3d ago
  Pod mirror origin/develop 98ca5f4f762f0926818cdacb335ba3930cf9106a accepted EventListener HTTP 202. One post-push sensitive/internal-path scan PASS recorded by audit. Pod health still showed v5.6.249 at first checks; waiting for asynchronous v5.6.250 build before closure.
• coder03-mba-l-ca completed · 3d ago
  Stakeholder criterion retained exact MERCEDES BENZ / OH 1621/62 / GO as a distinct catalog entry, with no inferred alias. Audited SQL SHA b452bc09 applied PROD id146 then DEV id1000000001; AB139OT imported against the exact key. Recorded in c29a096c/70a2c8b7; PROD, DEV and pod now serve v5.6.250 (pod health serviceId 35161).