*Title:** `feat(contracts): implement stuck funds recovery and emergency admin operations

[Divineifed1]

Description:
Safety mechanism to recover incorrectly sent tokens or handle edge cases where users lose funds due to platform bugs. Admin operations must be time-locked and transparent.

Key functions:

• emergency_withdraw(env, asset, to, amount) — timelocked admin
• recover_token(env, asset, to, amount) — for accidentally sent tokens
• set_admin(env, new_admin) — admin transfer with delay

Acceptance criteria:

• emergency_withdraw has 24-hour timelock (stored as pending_until)
• recover_token only works for tokens not owned by the contract's intended logic
• All emergency ops emit EmergencyAction event with reason hash
• Admin transfer requires 48-hour confirmation period
• Tests simulate timelock expiry and cancellation

[Davichi-1]

Hello Maintainer, I'd like to work on this issue. I have experience with backend development and state management, and I can implement this. Please consider assigning it to me.

[dubemoyibe-star]

I'd like to work on this issue.

From my understanding, the goal is to provide safe recovery mechanisms for exceptional situations without compromising trust. Sensitive admin actions should be transparent, time-locked, and only executable after the required delay, giving users visibility before they take effect.

My approach would be to implement timelocked emergency operations with explicit pending states, enforce the 24-hour and 48-hour delays for withdrawals and admin transfers, and ensure "recover_token" only applies to assets outside the contract's intended flow. I'll also emit structured "EmergencyAction" events for every operation and add tests covering timelock scheduling, execution, cancellation, authorization, and edge cases.

I'd be glad to start implementation once assigned.

[grantfox-oss]

🦊 GrantFox — @dubemoyibe-star has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #24)
2. Your PR will be reviewed by the Exquisitech maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@dubemoyibe-star's PR #32 was approved and merged by @Divineifed1.

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

👏 Great work, @dubemoyibe-star! Keep contributing to Exquisitech.