Outlaw Panel documentation
Developer Guide
Development follows the repository architecture, quality gate, documentation policy, and GitHub workflow.
Purpose
Help contributors make safe, reviewable changes.
Step-by-step
- Read AGENTS, project context, and the Developer Manual.
- Analyze existing boundaries before editing.
- Implement the smallest approved change.
- Build, lint, type-check, and test.
- Update documentation and run `OutlawPanel-CHECK.ps1`.
- Commit and push only after PASS.
Example
Production behavior changes require tests and matching documentation.
Best practices
- Never commit secrets.
- Preserve unrelated work.
- Use locked dependencies.
Troubleshooting
- Use the canonical repository and scripts.
- Do not weaken failing checks.