Add rustdoc comments to src/contracts/logic.rs and proxy_entry.rs

[N-thnI]

Problem

src/contracts/logic.rs (700 lines) and src/contracts/proxy_entry.rs (917 lines) — the two largest files in the crate, and the core of the contract's public surface and upgrade-proxy logic — have zero /// rustdoc comments between them.

Why it matters

plan.md's "Documentation" section explicitly asks for "Inline rustdoc — add /// doc comments to every public function explaining parameters, errors, and side-effects." These two files are the highest-value, highest-complexity target for that and currently have none, making them the hardest files in the repo for a new contributor to safely modify.

Acceptance criteria

• Add /// doc comments to every pub fn in src/contracts/logic.rs, covering parameters, return value, error conditions, and any side effects (storage writes, events emitted, auth requirements)
• Do the same for every pub fn in src/contracts/proxy_entry.rs
• cargo doc builds cleanly with no warnings about missing docs (if #[warn(missing_docs)] is enabled; otherwise just verify visually)
• No behavioral changes — comments only

Scope

Doc comments only in the two named files. Do not modify function bodies or signatures.

Definition of done

Every public function in logic.rs and proxy_entry.rs has a rustdoc comment describing its parameters, errors, and side effects; cargo doc --no-deps builds without missing-docs warnings for these two files.

[GazzyLee]

hello, I’m interested in taking this on. I’ll add comprehensive rustdoc to every public function in logic.rs and proxy_entry.rs, covering parameters, return values, errors, authorization, storage effects, and emitted events. I’ll keep the change strictly documentation-only and verify it with cargo doc --no-deps. please assign

[EmmanuelAdah]

I'd love to take this on! My background in technical instruction, technical writing, and engineering smart contract entry-points makes me a perfect fit for documenting this core logic. I will add comprehensive /// rustdoc comments to every public function in logic.rs and proxy_entry.rs, detailing parameters, errors, and side effects to ensure cargo doc builds cleanly without altering any behavior. Please assign it to me if available!

[grantfox-oss]

🦊 GrantFox — @EmmanuelAdah 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 #246)
2. Your PR will be reviewed by the Vero-protocol maintainers

Good luck! Track your progress on GrantFox.