docs: consolidate LIMITATIONS.md across PRs #1-#4#5
Merged
Conversation
Single source of truth at packages/cli/LIMITATIONS.md. Linked from README and SKILL.md so new contributors / agents find it before assuming a feature works end-to-end. Documents per area: CPE / Emission (PRs #1, #2): - Driver matrix (mock / sunat-direct / facturador / nubefact / apisperu) × CPE type (factura / boleta / NC-ND / guia / resumen / baja) with status per cell: 🔬 verified,⚠️ shape-only, 🚧 stubbed - NC, ND, Guía → driver methods throw, UBL builders shaped - cpe void T3 → flow shaped, command stubbed - Resumen Diario sendSummary → XML verified, blocked by SUNAT beta nginx 401 on test RUC (rate limit specific to /sendSummary path) - Drivers facturador/nubefact/apisperu → return clear "not implemented" - Catálogos SUNAT → minimal hardcoded set (NIU, ZZ) - Producción endpoint → never tested, only beta SUNAT REST OAuth APIs (PR #3): - Padrón puntual via portal → blocked (numRnd token + reCAPTCHA) - Tipo de cambio (SUNAT + SBS) → both blocked by WAF - Consulta CPE Integrada → shape verified vs Greenter openapi, untested live SIRE — RVIE/RCE (PR #4): - All endpoints follow Manual v22 March 2024 byte-for-byte, never tested live (test RUC has no SIRE history) - Reemplazar propuesta + Importar comprobantes → use TUS.IO resumable upload protocol; SUNAT manual says "JAVA required". Future PR. - Reportes complementarios → same async pattern, easy adds Cross-cutting: - Production submissions never tested - Stress / rate-limit tests never run - Multi-RUC profiles never exercised - Audit log unbounded (never rotated) - Bun-only, macOS/Linux only (Windows untested) Out of scope (no plans): - Mexico CFDI, Colombia DIAN - PDF render - GUI / dashboard - Becoming an OSE acreditado Convention: every PR must update LIMITATIONS.md (move items between shaped → verified → out of scope, or add new ones). Review blocker if not.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Single source of truth at
packages/cli/LIMITATIONS.mdfor everything that's stubbed, blocked by SUNAT WAF, shape-verified-but-untested-live, or pending production verification. Linked from README + SKILL.md.Why
After 4 PRs, the limitations were scattered across:
RESEARCH.mdfiles in different submodulesA new contributor (or me in 6 months) shouldn't have to read 4 PR descriptions to know whether
sunat cpe nc emitworks orsunat tipo-cambiois even implemented.Convention going forward
What's documented
Per-area sections covering all 4 merged PRs:
Quick markers used throughout:
Test plan