Document day-to-day PR workflow used throughout the project:
- What is a PR and why we use them
- Complete workflow from branch creation to merge
- Branch naming conventions (fix/, feat/, docs/, refactor/, test/)
- Commit message format with good/bad examples
- Review checklist and common patterns
- Merging strategy (squash vs regular)
- After merge cleanup steps
- Troubleshooting guide
- Real examples from recent PRs (eval-harness-phase1, smoke-to-test, sl-wiki-cross-links)
Captures the practical PR workflow we use daily in chat and makes
it accessible as reference documentation.
Sam & Claude
Replace jargon term 'golden tests' with clearer 'fixtures tests' throughout
the codebase. This aligns with the project's preference for explicit,
understandable terminology over obscure testing jargon.
Changes:
- Renamed crates/colibri-contracts/tests/golden.rs → fixtures.rs
- Updated comments in fixtures.rs and session.rs
- Updated docs: AGENTS.md, README.md, colibri.md, index.md
- Updated wiki: contracts.md, runtime-inventory.md, sl/contracts.md
Note: Kept intentional 'golden line' metaphor in COLIBRI-TOKENOMICS-TRIFECTA.md
as it refers to the concept, not the test file.
All gates pass:
- cargo fmt, clippy, test (14/14 in contracts)
- wiki-lint: 187/0
