📚docs: write docs/contributing/setup.md

[sotoJ24]

Title: docs: write docs/contributing/setup.md — contributor workflow from fork to PR including test account creation with DEV ONLY role selector

Issue Summary

The contributor onboarding guide. Documents the full workflow from forking to submitting a PR: branch naming conventions, how to get env files from the maintainer, the DEV ONLY role selector in the register form (and why it exists), database reset procedure, and useful commands. Must be accurate — contributors will follow it exactly.

Type of Issue

• Documentation

Branch strategy

✅ docs/issue-N-contributor-setup → consolidation-pattern

Expected Behavior

docs/contributing/setup.md covering:

1. Fork, clone, checkout consolidation-pattern

2. pnpm install

3. Get env files from maintainer — which variables need maintainer-provided values

4. Backend bootstrap — cd infra/backend && bin/start safetrust hotel_industry

5. Test account creation — register with DEV ONLY role selector (amber box in register form)

6. Branch naming — feat/issue-N-description, fix/issue-N-description, docs/issue-N-description

7. PR checklist — target branch consolidation-pattern, CodeRabbit response required, issue linked

8. DB reset — docker compose down -v && bin/start safetrust hotel_industry

9. Useful commands — kill ports, open Hasura console, TypeScript check

Files to create

File	Approx lines
docs/contributing/setup.md	~130

Make sure to follow the Git Guidelines for Atomic Commits and read Contributing Guide

• Contributing Guide
• Git Guidelines

---

Issue L — dApp-SafeTrust

Title: docs: write docs/contributing/issue-template.md — 8-section issue anatomy, GrantFox A-rating criteria, and acceptance criteria checklist format

Issue Summary

Documents the mandatory 8-section issue template that every SafeTrust issue follows. Contributors who create issues (wave participants, maintainer) need this to write issues that pass the quality bar for GrantFox grading and CodeRabbit review. Includes a real example for each section and the GrantFox A-rating criteria table.

Type of Issue

• Documentation

Branch strategy

✅ docs/issue-N-issue-template → consolidation-pattern

Expected Behavior

docs/contributing/issue-template.md covering:

1. All 8 sections — Issue Summary, Type of Issue, Branch Strategy, Current Behavior, Expected Behavior, Reproduction Steps, Environment Details, Supporting Information — with a "good vs bad" example for the most important section (Issue Summary)

2. GrantFox A-rating criteria table — all 6 criteria that must be present together

3. Issue title format — type(scope): description with valid types and examples

4. Acceptance criteria format — checkbox checklist at the end of every issue

5. What gets issues returned — missing sections, invented problems, single-file trivial changes

Files to create

File	Approx lines
docs/contributing/issue-template.md	~120

Make sure to follow the Git Guidelines for Atomic Commits and read Contributing Guide

• Contributing Guide
• Git Guidelines

---

[GABRIELOFGOD]

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

Please assign to me, I will fix it.

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

[DeePrincipal-dev-lang]

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

Hi there! I'd like to work on this issue if it's still open.
I'm a prompt engineer with a detail oriented, methodical approach to debugging and testing. I went through the issue description and already have a clear plan for tackling it. Happy to outline my approach before diving in if that would be useful for review.
I can start right away and will keep you posted on progress as I go, including test coverage and the PR link, so you have visibility the whole way through.
Would love to be assigned this one. Thanks for maintaining the repo!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @DeePrincipal-dev-lang to this issue.

[AGWAM001]

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

I'll love to work on this issue immediately after being assigned

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

[Duyicoda]

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

Hello there Team, I would love the opportunity to work on this issue, i have gone through the project requirements and issue scope and i can get it done in max of 72 hours, thanks for the consideration

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

[Ghostcecode]

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

Hi, I've taken the time to go through the requirements and I'm confident I can put together a solution that satisfies the acceptance criteria. I'd be grateful if this could be assigned to me.

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

[MaxiTech444]

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

CAN I WORK ON THIS PLEASE?

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

[drips-wave]

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

🧑‍💻 @kodinaka30-ship-it: 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]

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

🧑‍💻 @GABRIELOFGOD: 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 is assigned to @GABRIELOFGOD via the Stellar Wave Program.

Other assignees have been removed. To reassign, please unassign the current contributor through Drips Wave first.

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @GABRIELOFGOD as part of the Stellar Wave Program's 8th Wave 🥳

Moderator's reason: [Auto-assessed] The contributor GABRIELOFGOD had their PR #400 successfully merged by maintainer @sotoJ24, and the PR explicitly closes issue #382 (along with #370), fulfilling all requirements for documentation setup.

😎 @GABRIELOFGOD: 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.

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

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.