README's Repository Structure section is stale — mobile/, bridgelet-product-audit/, and .kilo/ are undocumented

[phertyameen]

Location

• README.md — Repository Structure section
• mobile/ (top-level folder, purpose undocumented)
• bridgelet-product-audit/ (top-level folder, purpose undocumented)
• .kilo/ (top-level folder, purpose undocumented)

Problem

The README's "Repository Structure" section describes this repo as
containing only frontend/ and docs/. The actual top-level file listing
also includes mobile/, bridgelet-product-audit/, and .kilo/, none of
which are mentioned anywhere in the README's architecture, quick start, or
repository structure sections.

Impact

This is more than a cosmetic doc gap: a contributor or auditor reading the
README to understand what this repo contains has no way to know these
folders exist or what they're for, which is a problem for a project
explicitly built as financial infrastructure where unexplained content in
a public repo invites reasonable questions about scope and intent. It also
suggests the README isn't being kept in sync with actual repo changes.

Fix

• Document each folder's purpose in the Repository Structure section:
  what mobile/ is for (a planned native app? Currently unused
  scaffolding?), what bridgelet-product-audit/ contains and why it's
  public, and what .kilo/ configures.
• If any of these folders contain material that shouldn't be public (see
  the related audit issues for .kilo/ and bridgelet-product-audit/),
  resolve that before simply documenting them.
• Add a lightweight CI or pre-commit check that flags new top-level
  directories not mentioned in the README, to prevent this drifting again.

Acceptance criteria

• Repository Structure section in README accurately lists every top-level folder with a one-line description
• mobile/, bridgelet-product-audit/, and .kilo/ each have a documented purpose
• A check (CI or documented review step) exists to catch future structure drift

[devgbmuyiwa]

@devgbmuyiwa has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I can work on this issue
Kindly assign this to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @devgbmuyiwa to this issue.

[DrSa7ag3]

@DrSa7ag3 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello, I’ve read through the issue description and understand the expected outcome. I’d be glad to work on it in the next few hours.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @DrSa7ag3 to this issue.

[ykargeee-bit]

@ykargeee-bit has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer
I want to implement this task
Kindly assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ykargeee-bit to this issue.

[drips-wave]

Congratulations, @ykargeee-bit! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @ykargeee-bit: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@ykargeee-bit's PR #545 was approved and merged by @phertyameen.

🏆 @ykargeee-bit: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,385 total points). Track your full progress on GrantFox.

👏 Great work, @ykargeee-bit! Keep contributing to bridgelet-org.

[drips-wave]

This issue has been completed by @ykargeee-bit as part of the Stellar Wave Program's 8th Wave 🥳

😎 @ykargeee-bit: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.