Home
Contributing
Production-grade workflow for adding coral source / table / function coverage.
Two-laptop rule
rendering…
- Laptop A (FiscalMindset): github source only. Branch prefix \`probe/github-*\`. Lock label
laptop-A. - Laptop B: any other source. Branch prefix \`probe/<source>-<surface>\`. Lock label
laptop-B. - One source per branch. One branch per laptop per session.
- Push cadence: every 5–10 probes.
Source claim protocol
- Branch off latest main:
git checkout -b probe/<source>-<surface> - File a lock issue so other agents don't double-team:
gh issue create \ --label source,claiming,laptop-X \ --title "[claim] <source> on laptop-X" \ --body "Source: <source>\nLaptop: <X>\nExpected start: <UTC>\nExpected end: <UTC|loop>" - Run the probe. Commit JSON + MD together.
- Open a PR with title
probe(<source>/<surface>): <verb> - Wait for CI; merge on green.
Per-PR checklist
- Branch is
probe/<source>-<surface> - Lock issue linked in PR body
- Per-table JSON committed (one file per surface)
- Per-table MD rendered (with Mermaid)
- Conventional commit messages, scoped per source
- No edits to shared-infra files unless PR title is prefixed
infra: