SpecsCLIIP-106-cli-harness-reporting
Implementation Notes: IP-106 CLI-Backed Harness Reporting
Implementation Notes: IP-106 CLI-Backed Harness Reporting
Execution Mode
Sequential Wave B after IP-105 telemetry/reporting foundation.
Issue Coverage
| Issue | Status | Evidence |
|---|---|---|
| IP-133 | Implemented | punks report submits structured reports through the typed control-plane client; API accepts authenticated reports; successful submission triggers best-effort cli.harness.report.submitted. |
| IP-134 | Implemented | Report status/type/severity/GitHub-link schema and support-loop docs preserve local vs systemic triage and keep Linear as product planning. |
Validation
bun run test --filter=@punks/contract --filter=@punks/api --filter=@punks/cli: passed.bun run check-types --filter=@punks/contract --filter=@punks/api --filter=@punks/db --filter=@punks/cli: passed.- Built CLI smoke passed:
punks --help,punks report --help, missing-control-plane failure, and local APIpunks report --jsonsubmission withDP_API_STORAGE=memory. - Full repo validation passed:
git diff --check, wikimeta.jsonJSON validation,bun run check,bun run check-types,bun run test, andbun run build.
Review
Delivery-owned $review-phase initially tightened report telemetry ordering. Codex PR review then identified the awaited telemetry as a hang risk after successful report submission, so it is now best-effort again and captured in docs/reference/tech-debt/cli/M4-trust-telemetry-lifecycle/pr-6-telemetry-review-findings.md.
Docs Ingest
Docs updated for punks report, GitHub follow-up, Linear planning boundary, and support feedback loop.