Manifest: no deprecated or sunset signaling per mode or endpoint

[winsznx]

Priority: P2 · Area: Manifest protocol

Providers can silently remove modes or endpoints with no advance notice. An agent with a cached manifest discovers removal only when a live request fails, potentially mid-workflow with funds at risk.

Proposed fix: Add optional { deprecated, sunset_at? } to each pricing/endpoints entry, and a root expires_at (ISO 8601) to bound client-side caching.

---

RouteDock Drip Wave 6 backlog.

[Codex723]

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

I would like to work on this issue and have experience designing API versioning and manifest systems with backward compatibility and safe deprecation strategies. I can extend the manifest schema to include deprecated and sunset fields per endpoint, add a root expires_at for cache control, and ensure agents can safely detect and handle upcoming or active removals without runtime failures.

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

[itzabdoull]

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

Hi maintainer! Can I work on this issues?

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

[drips-wave]

Congratulations, @Codex723! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Codex723: 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 🌊

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @Codex723 as part of the Stellar Wave Program's 6th Wave 🥳

Moderator's reason: [Auto-assessed] The contributor implemented the requested deprecation signaling (deprecated, sunset_at) and manifest expiry logic (expires_at) across the schema, types, and client implementation. The PR includes comprehensive smoke tests covering all new logic and follows the proposed fix outlined in the issue.

😎 @Codex723: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.