harness-onboardinglisted

# Harness Onboarding Documentation ## Overview HARNESS.md is written for agents and experienced team members. New contributors need something different — a friendly, practical guide that explains "here's how we work" without requiring them to parse constraint definitions and GC rule syntax. This skill generates `ONBOARDING.md` from three sources the project already maintains. No new data entry is needed — the onboarding document is a human-readable projection of existing harness state. --- ## Sources | Source | What it contributes | | --- | --- | | HARNESS.md | Stack, conventions, constraints, GC rules, observability cadence | | AGENTS.md | Gotchas, architecture decisions, test strategy, design decisions | | REFLECTION_LOG.md | Recent surprises with `context` or `workflow` signal | HARNESS.md, AGENTS.md, and REFLECTION_LOG.md are the single source of truth. Sync is one-way only — these files drive ONBOARDING.md. The generated document is never edited directly. --- ## Tone Write for a human who just joined the team and needs to ship their first PR. The reader is a skilled developer who knows nothing about this specific project. - **Friendly, not formal.** "We use markdownlint to keep files consistent" not "All markdown files must pass markdownlint." - **Practical, not theoretical.** Focus on what the contributor needs to do, not why the framework exists. - **Grouped by action.** Constraints grouped by when they fire (commit-time, PR-time), not by enforcement t