Add Maximum Submissions Per Quest Enforcement

[RUKAYAT-CODER]

Overview

The contract tracks submission counts but does not enforce a maximum per quest. A quest offering a single reward could receive unlimited submissions, creating unbounded storage growth.

Specifications

Features:

• max_submissions: Option field in quest registration
• Reject submit_proof when count >= max

Tasks:

• Add max_submissions to Quest type
• Add check in submission.rs submit_proof`n- Add tests for limit enforcement

Impacted Files:

• contracts/earn-quest/src/types.rsn- contracts/earn-quest/src/submission.rsn

Acceptance Criteria:

• Submission rejected when max reached
• Quests without max_submissions accept unlimited submissions

[Meet-hybrid]

CAN I WORK ON THIS PLEASE?

[collinsezedike]

I've dealt with grief-vector admin actions before and know the cooldown needs to gate the re-pause path specifically, not just be a passive timestamp that nothing checks.

Here's my plan:

• Add last_unpause_ts storage in security.rs, set whenever unpause succeeds
• Add pause_cooldown_seconds storage, defaulting to 1 hour, adjustable only by SuperAdmin
• In the pause function, check current_ts - last_unpause_ts >= pause_cooldown_seconds before allowing the pause; if too soon, emit PauseCooldownViolation and return Error::PauseCooldown
• Tests: re-pause immediately after unpause fails with the correct error and event; re-pause after the cooldown elapses succeeds; SuperAdmin can adjust the cooldown duration and the new value takes effect

Happy to start as soon as I'm assigned.

[sublime247]

I would love to resolve this issues