2.4 KiB
Harness, indexes, and verification evidence
Use this topic for collaboration rules, indexes, regression scope, commands, and local reports. Execution guidance is in the Harness README.
| Question | Read first | Follow through |
|---|---|---|
| Agent entry points and topic selection | Root guidance, static task index | Topic indexes, cross-module map |
| Delegation for complex tasks | Using subagents when useful | Root guidance |
| CLI, context, and targeted checks | Scope registry, CLI implementation | CLI regressions, root check commands |
| Full checks, reports, and historical decisions | Verification and evidence, CI | Development plan and design review, toolchain record |
Update affected index links when moving source. For new topics, update the scope registry, matching Markdown file, and static entry point together. Keep lengthy contracts in their owning modules. The existing CLI writes reports to ignored .harness-local/runs/; do not put screenshots or other temporary evidence in the indexes.
Targeted verification: run pnpm harness check for index validity. After CLI or scope-registration changes, run pnpm harness verify harness. For full-workflow changes, use a real pnpm harness verify all run to verify reporting. Collaboration rules, indexes, and the CLI do not themselves change pages, so they do not need UI/UX verification.