Remove generated comment noise from source files

[Lakes41]

Difficulty: Hard

Type: Refactor

Summary

Remove repetitive generated comments from source files so contributors can read and maintain the code more easily.

Current Behaviour

Many files contain comments such as GuildPass Mobile: Import package module dependencies, Return evaluated JSX layout, and Exit functional execution container scope block. These comments do not explain domain behaviour and make diffs noisy.

Expected Behaviour

Source comments should explain non-obvious domain logic, edge cases, or implementation choices. Boilerplate generated comments should be removed.

Suggested Implementation

Delete repetitive generated comments across app/ and src/. Keep meaningful TODOs and domain-specific notes. Add a lint rule or review guideline to avoid reintroducing generated boilerplate comments.

Files or Areas Likely Affected

• app/**/*.tsx
• src/**/*.ts
• src/**/*.tsx
• .eslintrc*
• CONTRIBUTING.md

Acceptance Criteria

• Repetitive generated comments are removed from app screens
• Repetitive generated comments are removed from feature hooks and stores
• Meaningful domain comments and TODOs are preserved
• Typecheck and lint still pass
• Contributor guidance discourages non-informative generated comments
• No runtime behaviour changes are introduced

Additional Notes

This is a broad cleanup, but it is mechanical. Keep it separate from functional refactors to make review easier.

[xx7412421-cloud]

/claim #19

I can take this if it is still available.

Plan:

• identify generated or low-value comment noise in source files
• remove only comments that do not explain behavior, keeping meaningful docs intact
• run formatting and a focused project check before opening the PR

I will wait for assignment before submitting a PR.

[YfengJ]

I would like to apply for this issue.

If assigned, my plan is to remove repetitive generated comments across app/ and src/ while preserving meaningful TODOs and domain-specific explanations, then add a lightweight guideline or lint/check note so the boilerplate comment style does not come back. I would keep the change mechanical and reviewable, with no runtime logic changes, and validate with the project formatter/linter/tests available in the repo.

[Marvy247]

Hi Maintainer, I've reviewed the issue description, and I'm confident I can implement all the requested details smoothly.​ Please assign this issue to me! I can have a PR ready for review in a few hours. Thank You.

[David-patrick-chuks]

Hi, I'd like to work on this issue. I've gone through the description and acceptance criteria and I'm confident I can deliver it. I'll make sure every acceptance criterion is met and submit a clean, tested PR. Please assign it to me.

[mc-stephen]

Hello team,

I'd like to claim this issue. Cleaning up auto-generated or boilerplate comments is a great way to make the codebase more readable for everyone.

I work regularly with multi-service architectures and manage deployments using Coolify, so I appreciate a codebase that prioritizes meaningful documentation over filler comments.

My plan for this cleanup is to:

1. Targeted Cleanup: Safely remove the repetitive comments (like "Return evaluated JSX layout") across app/ and src/ files.
2. Preservation: Double-check that all actual domain logic, architectural context, and active TODOs remain untouched.
3. Guardrails: Add clear guidance to CONTRIBUTING.md and check if we can enforce a linting pattern or review rule to prevent reintroducing them.
4. Safety: Keep this strictly mechanical with absolutely zero changes to runtime behavior.

Could you please assign this to me? I can get started on the cleanup right away!

[grantfox-oss]

🦊 GrantFox — @mc-stephen has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

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

Good luck! Track your progress on GrantFox.

[YfengJ]

Thanks for the update. I see this has been assigned to @mc-stephen via GrantFox, so I will step back and will not open a competing PR. Good luck with the implementation.