Systematically resolve a set of open iroh-http issues through evidence-based triage, compatible vertical slices, focused verification, reviewed commits, and a branch pull request. Use when working through the backlog or resolving multiple related issues. Do not use for creating issues or bypassing review with a direct main-branch push.
Write a failing regression test before fixing any bug that escaped a release. USE FOR: any bug reported against a published version (e.g. "this broke in v0.2.1"), any issue filed after a release, any case where CI passed but the bug reached users. DO NOT USE FOR: bugs caught before release by existing tests, new features, refactors.
Analyze any Git diff or revision range and generate a self-contained HTML review report with exact additions/deletions, per-file and per-directory visualization, code/comment/blank classification, production-versus-test accounting including inline Rust tests, and architectural concentration signals. Use when reviewing PR size, explaining where lines came from, separating operational code from tests/docs/generated files, auditing module responsibility, or producing a reusable diff artifact.
Create, triage, update, and close GitHub issues for iroh-http with duplicate checks, evidence-backed classification, durable agent briefs, safe public comments, and merge-aware closure. Use when reporting a bug or enhancement, organizing issue state, preparing work for an agent or human, or closing resolved issues.