[Bug] Instance storage TTL never renewed after initialize

[collinsezedike]

Summary

initialize extends instance-storage TTL exactly once (contracts/tholos/src/lib.rs:289-291). Every other function that reads or writes instance storage, update_resolvers, propose_rotation/vote_rotation/cancel_rotation, set_paused, assert_outcome, dispute, finalize, resolve, never calls extend_ttl again. Contrast this with set_assertion, which explicitly re-extends the persistent Assertion entry's TTL on every write for exactly this reason. If INSTANCE_BUMP_AMOUNT elapses without an external ExtendFootprintTTLOp, instance storage (admin, token, resolvers, paused flag) becomes eligible for archival, and every function depending on it starts failing until a RestoreFootprintOp is submitted.

Scope

• Add a shared helper that bumps instance TTL, called from every state-changing entrypoint (assert_outcome, dispute, finalize, resolve, update_resolvers, set_paused, and the rotation functions).
• No storage layout changes, this is purely about calling extend_ttl more often.

Proposed approach

fn touch_instance_ttl(env: &Env) {
    env.storage()
        .instance()
        .extend_ttl(INSTANCE_LIFETIME_THRESHOLD, INSTANCE_BUMP_AMOUNT);
}

Call this from the top of each state-changing entrypoint, mirroring how set_assertion already renews the persistent side. Add a test confirming instance TTL is extended after a call to one of these functions, not just at initialize.

[Rayhab2000]

Please assign this issue to me

[collinsezedike]

Hey @Rayhab2000, checking in, no rush. Just want to make sure you have what you need on this one. Let me know if you're stuck or have questions.

[collinsezedike]

Hey @Rayhab2000, second check-in, still no rush. Just want to make sure nothing's blocking you. Let me know if you're stuck or have questions.

[collinsezedike]

Hey @Rayhab2000, still no update on this one. If there's no progress or word back within the next 24 hours, I'll have to unassign it and open it up to someone else.