Coverage gates for uncovered contracts (batch-sender, vault, asset-policy, governance)

[truthixify]

Tier: M (2-4 days) | Type: test

Context. .github/workflows/coverage.yml runs cargo tarpaulin with --fail-under gates only for stealth-announcer / stealth-registry / stealth-sender at 90% and wraith-names / stealth-splitter at 80%. stealth-batch-sender, stealth-vault, wraith-asset-policy, and the governance PoC have no coverage gate, so tests can regress silently. Batch-sender only has 6 inline snapshot tests and vault has 8, so today's real coverage is likely well below any published bar.

Scope.

• Extend coverage.yml with per-crate tarpaulin runs for the four missing contracts.
• Set gates at 80% for vault / batch-sender / governance and 90% for asset-policy (small surface).
• Backfill tests until each crate meets its gate: for batch-sender that means adding a tests/ dir with adversarial cases beyond the current inline snapshots; for vault that pairs with issue Security audit of stealth-registry Soroban contract #2's hardening tests; for asset-policy add rotation + timelock adversarial cases; for governance add negative-path tests (quorum-not-met, cancelled proposal, executed twice).
• Upload the merged HTML report as a workflow artifact and link it from stellar/README.md.

Acceptance.

• coverage.yml runs tarpaulin for all nine Stellar crates
• Every gate passes on develop
• Coverage HTML artifact linked from stellar/README.md operations section
• Per-crate coverage numbers recorded in contracts/audit-prep/TEST_COVERAGE.md

Files. .github/workflows/coverage.yml, stellar/stealth-batch-sender/tests/ (new), stellar/stealth-vault/tests/ (new), stellar/wraith-asset-policy/tests/ (new), stellar/contracts/governance/tests/ (new), stellar/README.md, contracts/audit-prep/TEST_COVERAGE.md.

[BuddiBisong]

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

I would like to work on this issue because I am a professional developer and i have the skills and technical knowhow to solve this issue

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

[fwseyi]

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

Hi i'd like to work on this issue

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

[stpatrickghost]

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

Can i work on this?

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

[drips-wave]

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

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