Context
All PRs #1-#9 verified against `e-beta.sunat.gob.pe` with the public Greenter test cert (RUC 20000000001). Production endpoint `e-factura.sunat.gob.pe` has NEVER been tested.
Same for SIRE: shapes match Manual v22 byte-for-byte but no live test. Same for GRE.
Scope
First production emission on a real RUC + cert:
- Setup `CPE_PROFILE=prod-real` with real cert + clave SOL
- `cpe doctor --driver sunat-direct` against prod
- `cpe factura emit --params '{...}' --dry-run --mode prod` first
- Tiny test factura (S/1 to a known RUC) with --yes
- If accepted: validate CDR, void it via NC the same day to keep the test clean
- Document results in a new `PROD-VERIFIED.md` (or just append to LIMITATIONS)
Same for
Success criteria
- LIMITATIONS.md "Producción ... never tested" line removed
- All ⚠️ entries in driver matrix → 🔬 production-verified
- Audit log shows successful prod CDR for each CPE type
Risks
- Cert leak if env vars get logged
- Plazo violation if the tiny test factura is forgotten and not voided same-day
- SUNAT throttle / rate limit not yet observed in prod
Why P1
Until this happens, the CLI is "demoware" — verified against beta only. P1 because nobody should run prod on unverified code.
Context
All PRs #1-#9 verified against `e-beta.sunat.gob.pe` with the public Greenter test cert (RUC 20000000001). Production endpoint `e-factura.sunat.gob.pe` has NEVER been tested.
Same for SIRE: shapes match Manual v22 byte-for-byte but no live test. Same for GRE.
Scope
First production emission on a real RUC + cert:
Same for
Success criteria
Risks
Why P1
Until this happens, the CLI is "demoware" — verified against beta only. P1 because nobody should run prod on unverified code.