Add CONTRIBUTING.md documenting setup, branch naming, commit conventions, and test workflow

[Jagadeeshftw]

📌 Description

The repo lacks a CONTRIBUTING.md file. Without one, contributors must infer branch naming conventions, commit message format (conventional commits), test commands, and how to run the Playwright e2e suite from scattered package.json scripts. Create CONTRIBUTING.md at the repo root covering all of these topics with runnable example commands.

💡 Why it matters: A clear contribution guide reduces onboarding friction and prevents inconsistent commit history and failing CI.

🧩 Requirements and context

• Document prerequisite versions: Node.js, pnpm/npm, Playwright browsers.
• Document the branch naming pattern: feat/, fix/, test/, refactor/, docs/.
• Document conventional commit format with examples for feat, fix, test, refactor.
• List the key npm scripts: dev, build, test, test:coverage, test:e2e, lint, format, size-check.
• Explain the VITE_* environment variables and how to create .env.local.
• Include a pull request checklist referencing the vitest coverage thresholds.

Non-functional requirements

• Must be secure, tested, and documented.
• Should be efficient and easy to review.

🛠️ Suggested execution

1. Fork the repo and create a branch

git checkout -b docs/contributing-guide

2. Implement changes

• Write/modify the relevant source: CONTRIBUTING.md
• Write comprehensive tests: no code changes; CI lint can validate Markdown format
• Add documentation: the file itself is the deliverable
• Validate security assumptions: do not include real API keys or wallet addresses in examples

3. Test and commit

• Run tests:

npm run lint

• Cover edge cases: document what to do when Playwright browser install fails, and how to skip e2e in unit-only PRs
• Include test output and security notes in the PR description.

Example commit message

docs: add CONTRIBUTING.md with setup, branch naming, commit conventions, and test workflow

✅ Acceptance criteria

• CONTRIBUTING.md exists at the repo root
• All npm scripts are listed with one-line descriptions
• Branch and commit naming conventions are documented with examples
• Environment variable setup is explained with a .env.local example
• PR checklist includes coverage threshold verification

🔒 Security notes

Do not include example .env values with real RPC URLs or contract IDs; use placeholder strings.

📋 Guidelines

• Minimum 95% test coverage
• Clear documentation
• Timeframe: 96 hours

[arisu6804]

Please consider assigning this issue to me, as I’m prepared to contribute wherever it’s needed, whether that involves protocol logic, interface creation, service-layer development, visual implementation, or cross-component coordination.

[grantfox-oss]

🦊 GrantFox — @arisu6804 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 #558)
2. Your PR will be reviewed by the Fluxora-Org maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@arisu6804's PR #602 was approved and merged by @Jagadeeshftw.

🏆 @arisu6804: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (118 total points). Track your full progress on GrantFox.

👏 Great work, @arisu6804! Keep contributing to Fluxora-Org.