Document missing modules in README's Modules table

[N-thnI]

Problem

The "Modules" table in README.md only documents 10 of the modules that exist under src/. Missing: src/contracts/* (logic.rs, proxy_entry.rs, rbac.rs, storage_layout.rs), src/utils/* (address.rs), gas.rs, migrate.rs, timelock.rs, consensus.rs.

Why it matters

A new contributor reading the README has no way to know what rbac.rs, proxy_entry.rs, storage_layout.rs, timelock.rs, consensus.rs, or migrate.rs are responsible for without opening and reading the source directly.

Acceptance criteria

• Add a one-line "Responsibility" description for each currently-undocumented module listed above
• Keep the existing table format/style
• Descriptions are accurate to current behavior (read the module before summarizing it, don't guess from the filename)

Scope

README table only. This depends on issue #1 (duplicate table removal) being resolved first — edit whichever copy remains, or coordinate if both are open simultaneously.

Definition of done

Every .rs file under src/ (including src/contracts/ and src/utils/) has a corresponding row in the README "Modules" table with an accurate one-line description.

[OluRemiFour]

I've reviewed the issue and understand the requirements. I'd love to work on this and submit a clean PR that meets the acceptance criteria.

Payout wallet (Stellar): GALHFNUOYOY4S5CNRK7OI7NKS7UNWYGSJII2POQ6XQKWMUVLKZ2SAWMP

GrantFox OSS campaign — smart escrow payout on merge.

[ABEEGOLD]

Hello Maintainer,

I've reviewed the issue and understand the requirements. I can audit the undocumented modules under src/, verify their current responsibilities directly from the source code, and update the README Modules table with accurate one-line descriptions while preserving the existing format and style. I have experience contributing to open-source projects and maintaining technical documentation that stays aligned with implementation details.

[grantfox-oss]

🦊 GrantFox — @ABEEGOLD has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

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

Good luck! Track your progress on GrantFox.