This directory is the human-readable entry for the repository harness.
The harness has three audiences:
- maintainers planning releases and managing GitHub work
- contributors trying to make a correct change
- coding agents resolving context and validation from changed files
Start here when managing release scope, milestones, issue flow, PR review, or architecture debt:
- maintainer-ops.md
- plans/README.md
- tech-debt/README.md
- tech-debt-register.md
- architecture-scorecard.md
Current maintainer rule:
- one active release plan per release
- one active debt plan for non-release debt
- one
wg/*owner per project issue, with[Epic]parents marked byepic - generated issue/PR board under
.agent-harness/maintainer/
Start here when changing code or docs:
- repo-map.md
- change-surfaces.md
- module-boundaries.md
- testing-strategy.md
- feature-complete-checklist.md
- nearest local
AGENTS.md
Contributor-facing wrappers also live in:
- ../../CONTRIBUTING.md
- ../../.github/PULL_REQUEST_TEMPLATE.md
- ../../.github/ISSUE_TEMPLATE/001_feature_request.yaml
- ../../.github/ISSUE_TEMPLATE/002_bug_report.yaml
- ../../.prowlabels.yaml
Start here when resolving task context mechanically:
The default loop is:
make agent-report ENV=cpu CHANGED_FILES="..."
make agent-ci-gate CHANGED_FILES="..."