Skip to content

01a051eb - Cap forum invoices and 503 debug listings - #74

Merged
TaprootFreak merged 1 commit into
developfrom
01a051eb-invoice-cap-debug-503
Aug 30, 2026
Merged

01a051eb - Cap forum invoices and 503 debug listings#74
TaprootFreak merged 1 commit into
developfrom
01a051eb-invoice-cap-debug-503

Conversation

@TaprootFreakAI

Copy link
Copy Markdown
Collaborator

EN:
Follow-up to #68. Forum invoice amounts above 10 million sats are rejected and stored as bad_body. Debug invoice and zap-ingest listings return 503 when the store throws, same as the other debug routes.

DE:
Nachzug zu #68. Forum-Beträge über 10 Millionen Sats werden abgelehnt und als bad_body gespeichert. Debug-Listen für Invoices und Zap-Ingests liefern 503, wenn der Store wirft, wie die anderen Debug-Routen.

Details

Codex on #68 after merge:

  • Test and keep the 10_000_000 sat cap (remove the v8 ignore that hid it).
  • Document 1..10_000_000 in SPEC and the endpoint handbook.
  • Catch store throws on GET /debug/invoices and GET /debug/zap-ingests.

Over-cap POST /messages/:id/invoice now persists bad_body instead of
hiding behind a coverage ignore. Debug invoice and zap-ingest lists
return 503 when the store throws, matching the other debug routes.
@TaprootFreakAI

Copy link
Copy Markdown
Collaborator Author

EN:
Ready after 1 review pass.
Follow-up to #68: over-cap forum invoices persist as bad_body, and debug listings return 503 when the store throws.

DE:
Bereit nach 1 Review-Durchlauf.
Nachzug zu #68: Überhöhte Forum-Beträge werden als bad_body gespeichert, Debug-Listen liefern 503 wenn der Store wirft.

Details

Grok quality and logic: 0 findings. CI green on 8f043ba. Mergeable CLEAN. Codex items from #68.

@TaprootFreakAI
TaprootFreakAI marked this pull request as ready for review August 30, 2026 13:53
@TaprootFreak
TaprootFreak merged commit 06b3adb into develop Aug 30, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants