[Backend] Turn tool registration into a governed capability system

[Solomonsolomonsolomon]

Add tool versioning, authorization metadata, deprecation controls, startup validation, and execution governance for the registry surface. The registry should become a managed capability boundary for AI execution, not just a map of functions.nn- Priority: Highn- Area: Tooling / Registryn- Advanced Scope: capability governance, metadata contracts, lifecycle control

[dhareymu]

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

Hi maintainer
This issue seems feasible to be fixed before the deadline today. Please, kindly assign it to me for a swift job.

Thank you

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

[drips-wave]

Congratulations, @dev-chinasa! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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