Saltar a contenido

HANDOFF — GatewayQR-MunicVAllende

Read before coding

CONTEXT.md, CONSTITUTION.md, DOMAIN-MODEL.md, SPEC.md, docs/adr/ADR-001 to ADR-004, ACCEPTANCE.md, RISKS.md. Reference code: C:/Work/AI/GatewayPrismaQR (template), C:/Work/PCPOS/20260728F_CYRE/srcs/pos_ctoq.cpp (POS PAGOQR client), C:/Work/PCPOS/20260914_CARACOL (QR encoder and renderer to port).

Before touching code: 1) summarize the expected behavior, 2) flag ambiguities or contradictions, 3) propose a file plan and tests. Implement only the SPEC's scope.

Order of work

  1. Gateway (gateway module) plus muni-emulator module and bench UI.
  2. POS changes (SPEC §2, three changes) after the gateway passes AC-01 to AC-15 on the bench.

(origin: agent, confirmed: 2026-11-16)

Do not

  • Do not change the PAGOQR contract beyond the qrdata field.
  • Do not edit SPEC, ACCEPTANCE or CONSTITUTION to make an implementation look correct.
  • Do not add dependencies without the operator's approval (ADR-002).
  • Do not use T-SQL newer than SQL Server 2016 SP1 in migrations (ADR-002).
  • Do not invent municipal response payloads beyond the doc examples; mark them as assumptions until the sandbox corpus exists (RISKS R-01).
  • Do not log the API key or pagadoPorLegajo anywhere (CONSTITUTION C2, C3).
  • Do not ship emulator classes inside the gateway artifact (ADR-004).

(origin: agent, confirmed: 2026-11-16)

Required evidence

  • Green mvn -DskipITs=false verify with JaCoCo bars (domain 90 %, overall 80 %).
  • Every AC-NN covered by a test carrying its ID in the name, except the criteria ACCEPTANCE.md marks as verified on the POS (AC-29, AC-33): those close on a recorded POS end-to-end run with its evidence under docs/evidence/ (human decision, 2026-11-18).
  • Integration tests against SQL Server 2022, never H2.