Skip to content

docs: document add-bond-invoice action for bond payout flow#44

Open
grunch wants to merge 1 commit into
mainfrom
docs/add-bond-invoice-action
Open

docs: document add-bond-invoice action for bond payout flow#44
grunch wants to merge 1 commit into
mainfrom
docs/add-bond-invoice-action

Conversation

@grunch
Copy link
Copy Markdown
Member

@grunch grunch commented May 14, 2026

Summary

  • New page src/add_bond_invoice.md documenting Action::AddBondInvoice (introduced in mostro-core 0.11.2) — the bi-directional bond-payout invoice flow that fires after a solver-directed slash via bond_resolution on admin-settle / admin-cancel.
  • Routing-layer note that add-bond-invoice (bond payout) and add-invoice (trade payout) must be dispatched on the action discriminator alone, not collapsed via status / memo heuristics.
  • Cross-links from pay_bond_invoice.md, admin_settle_order.md, and admin_cancel_order.md into the new page; TOC entry in SUMMARY.md; user-facing message suggestion in message_suggestions_for_actions.md.

Test plan

  • just build succeeds (mdBook compiles cleanly).
  • book/add_bond_invoice.html renders with all internal links resolving.
  • Reviewer eyeball-checks JSON payload shapes against mostro-core 0.11.2 (Payload::PaymentRequest for the reply, Payload::Order(SmallOrder) for the request).
  • Confirm slash_node_share_pct = 1.0 vs < 1.0 behaviour and forfeit-deadline anchor (slashed_at + payout_claim_window_days * 86_400) match mostrod PR #738.

🤖 Generated with Claude Code

Document Action::AddBondInvoice introduced in mostro-core 0.11.2 — the
counterparty-direction dual of pay-bond-invoice that requests a payout
invoice from the non-slashed side after a solver-directed bond slash.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 14, 2026

Warning

Rate limit exceeded

@grunch has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 15 minutes and 14 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 799b6da1-bb3e-4ac7-92f6-b5f4a8866928

📥 Commits

Reviewing files that changed from the base of the PR and between 6ae34c4 and a2dcfe4.

📒 Files selected for processing (6)
  • src/SUMMARY.md
  • src/add_bond_invoice.md
  • src/admin_cancel_order.md
  • src/admin_settle_order.md
  • src/message_suggestions_for_actions.md
  • src/pay_bond_invoice.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/add-bond-invoice-action

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

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.

1 participant