Align backend docs and naming with Access Layer

[Chucks1093]

Summary

Replace template-era naming in backend docs and domain comments with Access Layer terminology.

Context

Some server files intentionally preserve template scaffolding for faster development. We should keep the reusable structure while making the project-facing naming clearer for contributors.

Scope

• Audit obvious project-facing names in README, package metadata, and backend docs
• Keep reusable scaffolding that still helps development
• Update contributor-facing wording so it reflects Access Layer instead of the previous product context

Acceptance Criteria

• Project-facing docs use Access Layer terminology
• Reusable scaffolding is preserved where still useful
• Contributors can understand what is template carryover versus current product direction

Maintainer Contact

If you are assigned to this issue or need more context, reach out in our Telegram channel for updates and coordination: https://t.me/accesslayerorg

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 150 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[edehvictor]

@edehvictor has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Can I work on this? I'd start working on it real quick

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

[drips-wave]

Congratulations, @edehvictor! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @edehvictor: 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 🌊

[drips-wave]

This issue has been completed by @edehvictor as part of the Stellar Wave Program's 3rd Wave 🥳

😎 @edehvictor: You earned 150 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.