Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/ANTI_ABUSE_BOND.md`:
- Around line 148-151: Update the stale file path in the documentation: replace
the reference to src/db/bonds.rs with the actual module path src/app/bond/db.rs
in the ANTI_ABUSE_BOND.md bullet describing the Bond model and helpers; ensure
the bullet still lists the helper functions create_bond,
find_bond_by_order_and_role, find_bonds_by_state, and update_bond_state so
readers can locate those functions under src/app/bond/db.rs.
- Around line 445-448: The fenced code block containing "share_fraction  =
child_sats / parent_max_sats" and "slash_amount    = round(parent_bond_amount *
share_fraction)" is missing a language specifier; update that fenced block in
ANTI_ABUSE_BOND.md by adding a language tag (e.g., ```text) immediately after
the opening backticks so the block complies with markdownlint MD040 and the repo
guideline.
- Around line 122-145: The SQL snippet in ANTI_ABUSE_BOND.md is out of sync with
the migration: replace or update the inline CREATE TABLE so it exactly matches
the migration (use parent_bond_id instead of range_parent_id, add
child_order_id, slashed_share_sats, payout_routing_fee_sats, and the
idx_bonds_parent index, plus any column types/defaults present in
migrations/20260423120000_anti_abuse_bond.sql), or remove the inline SQL
entirely and replace it with a clear pointer to the canonical migration (and
then update the Phase-6 "extend Bond" section to use the same column
names/fields as the Phase-0 schema in the migration).

In `@src/app/bond/db.rs`:
- Around line 27-39: The query in find_bond_by_order_and_role returns an
arbitrary row when multiple child bonds exist; make it deterministic by
restricting to parent-level bonds: change the SQL in sqlx::query_as::<_,
Bond>("SELECT * FROM bonds WHERE order_id = ? AND role = ? LIMIT 1") to include
AND parent_bond_id IS NULL (i.e. "WHERE order_id = ? AND role = ? AND
parent_bond_id IS NULL LIMIT 1"), keep the same bind order (order_id, role_str)
and error handling; alternatively, if you intend to return the earliest bond
instead, add an ORDER BY created_at ASC before LIMIT 1 — pick one approach and
update find_bond_by_order_and_role accordingly.

In `@src/app/bond/math.rs`:
- Around line 109-111: The comment on the test using cfg_with(0.007, 0) is
incorrect about rounding mode: update the comment to state that Rust's
f64::round() rounds half away from zero (so 3.5 → 4) rather than "round half to
even"; locate the test that calls compute_bond_amount(500, &cfg) and replace the
misleading phrase "round half to even" with "rounds half away from zero" (or
similar wording mentioning f64::round()) to accurately reflect the behavior.

---

Nitpick comments:
In `@migrations/20260423120000_anti_abuse_bond.sql`:
- Around line 16-67: Add a composite index to support efficient ordered scans by
state and creation time: create an index on (state, created_at) named e.g.
idx_bonds_state_created_at so the scheduler query used by find_bonds_by_state /
PendingPayout can filter by state and order by created_at without a filesort;
add this index now or add a migration to introduce idx_bonds_state_created_at
before Phase 3 when PendingPayout sweeps are enabled.

In `@src/config/types.rs`:
- Around line 44-47: Rename the confusing percentage field amount_sats to a
percentage-named identifier (e.g., amount_pct or pct_of_order) and update its
serde default helper accordingly (rename default_bond_amount_pct →
default_amount_pct); update the doc comment to show the new unit (0.01 = 1%) and
change any usages of amount_sats and default_bond_amount_pct in code to the new
names so the bond formula reads max(amount_pct * order_amount,
base_amount_sats). Ensure struct field, default function, and all references
(parsing/serialization, tests, and docs) are updated together to avoid breakage.