align default dispute timeout docs and on-chain configuration

[grantfox-oss]

DEFAULT_DISPUTE_TIMEOUT_SECSinstorage.rsis declared with one value, while dispute expiry actions and admin-set timeouts may diverge. Sync the implementation, tests, and docs. - Impacted files:app/contract/contracts/Folder/src/storage.rs, app/contract/contracts/Folder/src/dispute.rs, app/contract/contracts/Folder/src/types.rs, app/contract/contracts/Folder/src/test.rs, app/contract/docs/UPGRADE_SAFETY_GATE_TEST_GUIDE.md, app/contract/README.md

[OluRemiFour]

I've reviewed the task and have a clear implementation plan. Looking forward to contributing with a quality PR.

[micmusjnr20]

I am applying to resolve the issue: Align default dispute timeout docs and on-chain configuration.

Discrepancies between official technical documentation and actual on-chain parameters create severe operational risks and user confusion. If developers, integrators, or users rely on documented dispute windows that don't match the hardcoded smart contract constraints, it can lead to missed dispute deadlines, failed transactions, or unexpected state lockups. Ensuring that human-readable specifications and on-chain state machine settings are perfectly synchronized is critical for protocol safety and developer trust.

I will audit the contract configurations, update the corresponding documentation across all relevant repositories, and add tests to ensure these values remain aligned going forward.

[grantfox-oss]

🦊 GrantFox — @micmusjnr20 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 #334)
2. Your PR will be reviewed by the BlockDash-Studios maintainers

Good luck! Track your progress on GrantFox.