Agents: no way to update a spending policy after registration

[ritik4ever]

Context

register_agent writes a default SpendingPolicy with very large limits, and no public function updates it.

Problem

Every agent is permanently stuck with the defaults — 1,000,000 USDC per transaction and 10,000,000 per day. The SpendingPolicy UI component and the agent runtime's AGENT_MAX_PER_TX / AGENT_MAX_PER_DAY environment variables both imply this is configurable. It is not.

Proposed approach

Add set_policy(agent_address, max_per_tx_stroops, max_per_day_stroops, allowed_categories, min_score_to_earn, caller) gated on the agent's owner, preserving daily_spent_stroops and last_reset_ledger across the update.

Acceptance criteria

• Owner can update their agent's policy
• Non-owners are rejected
• Accrued daily spend is preserved across updates
• Frontend and agent runtime wire through to the new function

Where to look

• contract/agents/src/lib.rs:217

---

Comment to claim this before you start so we avoid duplicate work. If the approach above looks wrong, say so in the thread — the proposal is a starting point, not a specification.

[Sankai2003]

@Sankai2003 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Based on the requirements, I will implement a clean and effective solution that aligns with the design specifications and fully satisfies the acceptance criteria.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Sankai2003 to this issue.

[drips-wave]

Congratulations, @Sankai2003! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Sankai2003: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊