chore: add community health files and changelog

- CONTRIBUTING.md with setup, code standards, and commit conventions
- CHANGELOG.md documenting v0.1.0 release
- Issue templates: bug report, feature request
- PR template with testing checklist

Author: MarcusDavidG

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,25 @@
+---
+name: Bug Report
+about: Report a bug in the smart contract
+labels: bug
+---
+
+**Describe the bug**
+A clear description of what the bug is.
+
+**Contract method**
+Which function were you calling? (e.g. `create_invoice`, `pay`, `release_escrow`)
+
+**To Reproduce**
+Steps to reproduce the behaviour.
+
+**Expected behaviour**
+What you expected to happen.
+
+**Environment**
+- Network: [ ] Testnet [ ] Mainnet
+- Stellar CLI version:
+- soroban-sdk version:
+
+**Additional context**
+Add any other context, transaction hashes, or error messages.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature Request
+about: Suggest a new feature or improvement to the contract
+labels: enhancement
+---
+
+**Problem / motivation**
+What problem does this solve? What use case does it enable?
+
+**Proposed solution**
+Describe the contract change or new function you'd like to see.
+
+**Stellar ecosystem impact**
+How does this benefit the Stellar/Soroban ecosystem?
+
+**Alternatives considered**
+Any alternative approaches you've thought about.
+
+**Additional context**
+Any other context, references, or examples.

.github/pull_request_template.md

@@ -0,0 +1,18 @@
+## Summary
+<!-- What does this PR do? -->
+
+## Related Issue
+Closes #
+
+## Changes
+- 
+
+## Testing
+- [ ] `cargo test` passes
+- [ ] `cargo build --release --target wasm32-unknown-unknown` succeeds
+- [ ] Tested on testnet
+
+## Checklist
+- [ ] Code follows existing patterns
+- [ ] New functions have doc comments
+- [ ] No `unwrap()` in production paths

CHANGELOG.md

@@ -0,0 +1,32 @@
+# Changelog
+
+All notable changes to the Sharpy smart contract are documented here.
+
+## [0.1.0] - 2026-06-01
+
+### Added
+- `initialize` — set admin and treasury addresses
+- `create_invoice` — single invoice with split rules and escrow options
+- `create_batch` — create up to 10 invoices in one transaction
+- `create_recurring` — recurring invoice that auto-generates next invoice on release
+- `pay` — pay toward an invoice with token transfer
+- `pool_pay` — pay multiple invoices in a single call
+- `release_escrow` — release escrow-held invoice after delay
+- `release` — manual release for fully funded invoices
+- `refund` — refund all payers after deadline passes
+- `cancel_invoice` — creator cancels and refunds all payments
+- `get_invoice` — read invoice state
+- `get_audit_log` — full audit trail per invoice
+- `get_payer_total` — total paid by a specific address
+- `get_next_recurring` — get the next invoice in a recurring chain
+- `pause` / `unpause` — admin circuit breaker
+- Split rules: `Fixed`, `Percentage`, `Tiered(threshold, bps)`
+- Events: `created`, `payment`, `released`, `refunded`, `pyr`
+- CI: GitHub Actions — test + WASM build on every PR
+- Deployed to Stellar testnet: `CAYTIFPD6RFWVHMK5SPPUUIWWAAANHKOJB6GOAJS5SR5MBKZMEY2UODZ`
+
+### Fixed
+- `SplitRule::Tiered` converted from named fields to tuple variant for `#[contracttype]` compatibility
+- `symbol_short!` length violations in event publishing
+- `Address::random()` replaced with `Address::generate()` for soroban-sdk v22
+- `testutils` feature isolated to `dev-dependencies` to allow wasm32 build

CONTRIBUTING.md

@@ -0,0 +1,65 @@
+# Contributing to Sharpy Contracts
+
+Thank you for your interest in contributing to Sharpy! This repo contains the core Soroban smart contract powering the Sharpy split payment protocol on Stellar.
+
+## Getting Started
+
+### Prerequisites
+
+- Rust (stable)
+- `wasm32-unknown-unknown` target: `rustup target add wasm32-unknown-unknown`
+- Stellar CLI: `cargo install --locked stellar-cli --features opt`
+
+### Setup
+
+```bash
+git clone https://github.com/stellar-sharpy/sharpy-contracts.git
+cd sharpy-contracts
+cargo test
+```
+
+## How to Contribute
+
+### Reporting Bugs
+
+Open an issue using the **Bug Report** template. Include:
+- What you expected vs what happened
+- Steps to reproduce
+- Relevant contract method and parameters
+
+### Suggesting Features
+
+Open an issue using the **Feature Request** template. Describe the use case and why it adds value to the Stellar ecosystem.
+
+### Submitting a Pull Request
+
+1. Fork the repo and create a branch from `main`
+2. Make your changes with clear, focused commits
+3. Ensure `cargo test` passes
+4. Ensure `cargo build --release --target wasm32-unknown-unknown` succeeds
+5. Open a PR against `main` with a clear description
+
+## Code Standards
+
+- Follow existing patterns in `lib.rs`
+- All public contract functions must have a doc comment
+- New features require at least one unit test in `test.rs`
+- No `unwrap()` in production paths — use `expect("descriptive message")`
+
+## Commit Messages
+
+Use conventional commits:
+- `feat:` new contract functionality
+- `fix:` bug fix
+- `test:` test additions
+- `docs:` documentation only
+- `chore:` build/config changes
+- `refactor:` code restructure without behaviour change
+
+## Security
+
+Do not open public issues for security vulnerabilities. Email the maintainers directly. See `SECURITY.md` for details.
+
+## License
+
+By contributing, you agree your contributions will be licensed under the MIT License.