Document mainnet oracle policy in README (V2 + adapter)

[Mimah97]

Context / Why

Document mainnet oracle policy in README (V2 + adapter). README still lists planned items that are implemented or blocked. This is required for Vatix Soroban audit/mainnet readiness.

Current state

Relevant paths: README Planned Functionality vs adapter status. Workspace crates: market, treasury, resolution, outcome-token under contracts/. Docs: README, AUTH_TABLE.md, docs/adr-001-oracle-adapter.md, scripts/upgrade/UPGRADE_PLAYBOOK.md.

Proposed work

1. Start from README Planned Functionality vs adapter status and add a failing test that captures the gap.
2. Implement fail-closed behavior (no silent Ed25519 fallback when adapters are enabled).
3. Update AUTH_TABLE / events-reference / upgrade playbook if entrypoints or storage change.
4. Keep CEI/reentrancy notes in docs/reentrancy-cei-audit.md in sync.
5. Run crate tests and workspace integration tests that touch the path.

Acceptance criteria

• Automated tests fail if the gap is reintroduced.
• Docs (AUTH_TABLE, events, playbook) match production ABI.
• No new instant admin mutators without timelock where peers already use 172_800s.
• CI-relevant cargo test paths stay green.
• No panic!/todo!() on shipped library paths.

Out of scope

Off-chain indexer work belongs in vatix-backend.

[titilope12]

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

Hello Maintainer, i can fix this issue

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

[Enemuo-debug]

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

Can I please be given the opportunity to work on this 🙏

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

[pharuq411]

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

i will like to work on this issue as a contributor

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

[bellofuad34-ctrl]

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

Hello Maintainer, I'm a full-stack developer and I've gone through the requirements. I can fix the issue and submit PR today.

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

[olaide2001]

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

Hi Maintainer, I can handle this task well. Please consider assigning it to me.

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

[Samylee1]

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

Hello Maintainer,

I'd like to work on this issue. I have experience contributing to similar codebases and can quickly get up to speed with the existing architecture. My plan is to identify the root cause, implement a clean fix that follows project conventions, and thoroughly test the solution before submitting a PR.

Looking forward to contributing.

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

[drips-wave]

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

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@pharuq411's PR #828 was approved and merged by @Mimah97.

🏆 @pharuq411: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (802 total points). Track your full progress on GrantFox.

👏 Great work, @pharuq411! Keep contributing to Vatix-Protocol.