oracle: clear_prices, get_stable_price, and get_price_with_stable_fallback have zero test coverage

[abayomicornelius]

Problem

Three oracle view/mutating functions have zero test coverage:

• clear_prices (contracts/oracle/src/lib.rs:402) — batch-clears temporary price entries for multiple tokens. Only the single-token clear_price appears to be exercised; the batch version is never called by any test.
• get_stable_price (line 321) and get_price_with_stable_fallback (line 341) — both contain the overflow guard added for issue oracle: get_stable_price / get_price_with_stable_fallback trust an unchecked u128->i128 cast as a valid price #383 (if price_u128 == 0 || price_u128 > i128::MAX as u128 { None } / the equivalent inline check), but no test calls either function at all, so the guard itself is unverified by the test suite.

grep -rn "clear_prices\|get_stable_price\|get_price_with_stable_fallback" --include="*.rs" . | grep -v oracle/src/lib.rs
# no output

Why it matters

#383's fix (rejecting a stable_price value that doesn't fit in i128) is exactly the kind of boundary condition that regresses silently without a dedicated test — a future refactor of either function could reintroduce the unchecked cast and nothing in CI would catch it. clear_prices's loop-based batch clearing is also untested, so an off-by-one or early-return bug in the loop would not be caught.

Suggested fix

Add tests: clear_prices with a multi-token vector, asserting each token's price is actually cleared from temporary storage; get_stable_price/get_price_with_stable_fallback with a stable_price value at/above i128::MAX asserting None/fallback-to-primary behavior, and with a normal in-range value asserting the stable price is returned.

[northvictor]

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

Hello maintainer, can I be assigned to this issue?

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

[IFEANYIBRIGHT]

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

Hi! I’m a full-stack developer with a strong blockchain background. I’d love to handle this issue and can deliver a clean, reliable solution. Kindly assign it to me.

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

[Dr-Ag-web3]

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

GM maintainer, please assign this to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Dr-Ag-web3 to this issue.

[privexlabs]

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

Hi, I would like to work on this

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

[drips-wave]

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

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