Batch intent view, dust-tolerant fills, slash-cycle cap, reputation badge

[knytcomics-ui]

Summary

Four assigned issues bundled into one PR:

• [High] Add a batch view function get_intents_batch #250 — get_intents_batch(intent_ids) view on intent_settlement, bounded by MAX_BATCH_SIZE, mirroring get_intent's Option<IntentRecord> semantics per entry. examples/risk_aware_solver_bot.py gains get_intents_batch/screen_candidates helpers demonstrating the batched call.
• [High] Add a minimum partial-fill increment and dust-tolerance guard #247 — ProtocolConfig.min_partial_fill and dust_tolerance_bps (admin-configurable via set_config). fill_intent now rejects non-completing fills below the floor, and treats a fill landing within the dust tolerance of min_dst_amount as Filled instead of leaving an unfillable PartiallyFilled remainder. README's fee/fill discussion and error table updated (new FillTooSmall error).
• [High] Add a cap on repeated Open → Accepted → Slashed cycles per intent #241 — ProtocolConfig.max_slash_cycles and IntentRecord.slash_cycles. slash_solver now retires an intent to a new terminal Abandoned state (instead of re-opening indefinitely) once it hits the cap, preserving partial-fill progress. New intent_abandoned event. SECURITY.md, README's lifecycle diagram, and docs/event-schema.md's transition table updated.
• [High] Design and prototype an on-chain solver reputation-tier badge #242 — docs/242-reputation-tier-badge-design.md resolves docs/solver-registry-design.md §10 Q3 (soulbound, bespoke contract, auto mint/burn on tier change). Minimal reputation_badge prototype crate (mint_badge/burn_badge/get_badge, admin-gated as a placeholder until solver_registry from issue fix: block solver deregistration while holding an accepted intent #1 exists) with tests covering mint-on-promotion, burn-on-demotion, and per-solver query isolation.

Closes #250
Closes #247
Closes #241
Closes #242

Validation performed

• No Rust toolchain was available in this environment, so cargo fmt/clippy/test could not be run locally.
• Pre-existing, unrelated to this change: intent_settlement/src/lib.rs on main already fails to compile — set_config/load_config reference DEFAULT_MIN_BOND, DEFAULT_FILL_WINDOW, DEFAULT_INTENT_EXPIRY, DEFAULT_PROTOCOL_FEE_BPS, MAX_PROTOCOL_FEE_BPS, MIN_FILL_WINDOW_SECS, MIN_INTENT_EXPIRY_SECS, MIN_BOND_FLOOR, MAX_BATCH_SIZE, and MAX_EXTENSION_DURATION, none of which are defined anywhere in the crate (introduced by the merged feat/protocol-fee-cap PR feat: add max protocol fee cap and admin audit trail #184). CI on main's latest commits shows this as a standing failure, predating this branch. This PR does not touch or fix those names — it follows the same (currently-broken) references for consistency, per new-field additions to ProtocolConfig/IntentRecord/Error/IntentState and the new reputation_badge crate (not part of CI's intent_settlement-scoped workflow, so unaffected by the above).
• Reviewed the diff by hand against existing patterns in the file (CEI ordering, checked arithmetic, event-emission style, storage TTL bumps) since automated verification wasn't possible.
• examples/risk_aware_solver_bot.py changes verified with python3 -m py_compile.

⚠️ Given the pre-existing broken build on main, please run cargo build/cargo test in CI or locally before merging to confirm this PR's additions are syntactically correct — I was unable to do so myself.

[drips-wave]

@knytcomics-ui Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits