Files
computer-playbook/docs/agents/action/debug/local.md
kevinveenbirkenbachandClaude Opus 4.8 9c029870fe feat(cli): add CI-logs download and analyze tooling
python -m cli.meta.ci.logs.download fetches a run's job logs and artefacts in parallel, with conclusion filters (-s/-f/-c/-k), a jobs.json/summary.tsv manifest, per-request jitter to dodge API rate limits, and idempotent re-runs. python -m cli.meta.ci.logs.analyze clusters the downloaded logs by their root failing task.

Rename the agent CI-triage page debug/pipeline.md to debug/ci.md, point its download/inspect step at the new CLI, and reference the tooling from the contributing CI-debugging page. Add unit tests for both commands.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-26 17:01:08 +02:00

11 lines
554 B
Markdown

# Local Deploy Debugging
Use this page when a local deploy fails. For automated GitHub Actions / CI triage, see [ci.md](ci.md). For inspecting log files the operator has manually placed in the repository workdir, see [log.md](log.md).
- You MUST debug from the live local output and local logs.
- If a local deploy is still progressing and the user has not asked you to change course, you MUST wait for it to finish instead of interrupting it.
## Retry Loop
- For the shared local retry loop, you MUST follow [Compose Loop](../iteration/compose.md).