[Quality-2][Medium] Sandbox plugin execution with timeout and resource budgets

[greatest0fallt1me]

Summary

Implement Sandbox plugin execution with timeout and resource budgets as a production-ready improvement in this repository.

Why this matters

This boundary protects funds, credentials, authorization, or sensitive operational data and must fail safely under adversarial input.

Scope

Trace the affected public entry point through persistence, external dependencies, and user/operator-visible output. Implement Sandbox plugin execution with timeout and resource budgets without weakening existing authorization, correctness, compatibility, or CI safeguards.

Priority

Medium

Acceptance criteria

• Authorization, validation, and least-privilege checks run before sensitive mutation.
• Invalid, stale, replayed, cross-tenant, and malformed inputs fail closed without protected-detail leakage.
• Secrets are excluded from logs, errors, telemetry, exports, and client-visible state.
• Negative and adversarial tests prove the security boundary.

Validation

The PR must include focused regression coverage for this issue, including:

• Authorization, validation, and least-privilege checks run before sensitive mutation.
• Invalid, stale, replayed, cross-tenant, and malformed inputs fail closed without protected-detail leakage.
• Secrets are excluded from logs, errors, telemetry, exports, and client-visible state.

Run the repository’s standard formatting, lint, build, and test commands where applicable, and report unrelated pre-existing failures separately.

Non-goals

• Typo-only, formatting-only, or documentation-only changes.
• Unrelated refactors, dependency upgrades, or broad redesigns.
• Weakening security, authorization, CI, validation, or production safeguards.
• Changing public behavior outside this issue’s scope.

Contributor application

Before implementation, comment with relevant experience, a concise implementation approach, expected files or modules, and an estimate for opening the first PR. Wait for maintainer assignment before coding.

PR requirements

Use a feature branch and include Closes #<issue-number>. The PR must address every acceptance criterion, link each criterion to code and tests, explain security and failure-mode handling, include meaningful regression coverage, preserve compatibility, and report validation results.

Quality review

This is a substantive engineering issue. Review will consider correctness, security, failure handling, test quality, scope discipline, and maintainability.

[payfoxX]

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

I love to fix this issue, kindly assign it to me. Thanks

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

[drips-wave]

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

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