EduarD3V/gotoi

Watch

Fork 0

Docs sync: verify every document against the code and fix the drift #66

New issue

Closed

opened 2026-10-07 20:35:01 +02:00 by gotoi-agent · 5 comments

gotoi-agent commented

2026-10-07 20:35:01 +02:00

Collaborator

Goal

Audit every agent-pipeline and repo document against the code that actually implements it, fix the
drift you find, and report what you could not prove.

Scope (docs → code)

docs/agent-issue-pipeline.md → the real run loop, cron jobs (gotoi-issue-runner,
gotoi-guard, gotoi-integrator), PR targets (agent-develop), comment protocol.
docs/agent-pipeline/*.md (verifier, reviewer, hidden-tests, integration-branch,
forgejo-enforcement, quarantine, queue-plan, threat-model) → scripts/agent-pipeline/*.
AGENTS.md, README.md, scripts/README.md → commands, gates, paths, branch rules.
.claude/skills/* → the behaviour they instruct (forgejo.py subcommands, gate lists).
Product docs (docs/use-cases/README.md, docs/templates.md, docs-site/content/) →
middleware/dashboard/agent behaviour only where you can cite a contradicting file:line or a
command's output.

Method

For each doc claim, locate the implementing code/command. Mark SYNC, STALE or UNVERIFIABLE.
Fix STALE with a minimal docs commit per area (docs(<area>): …, Refs #<N>).
Never "fix" a doc by making it vaguer; delete or correct the claim.
Post ONE comment: findings table (doc → claim → verdict → evidence), commits made, and an
explicit UNVERIFIABLE list — claims that need a human or a live system to confirm.

Constraints

Docs-only commits unless a code change is itself the drift (then say so in the comment first).
No closing keywords anywhere (Refs #<N> only). No pushing beyond your branch (the orchestrator
publishes).
Boring path over speculation: an unverifiable claim is reported, not guessed at.

## Goal Audit every agent-pipeline and repo document against the code that actually implements it, fix the drift you find, and report what you could not prove. ## Scope (docs → code) - `docs/agent-issue-pipeline.md` → the real run loop, cron jobs (`gotoi-issue-runner`, `gotoi-guard`, `gotoi-integrator`), PR targets (`agent-develop`), comment protocol. - `docs/agent-pipeline/*.md` (verifier, reviewer, hidden-tests, integration-branch, forgejo-enforcement, quarantine, queue-plan, threat-model) → `scripts/agent-pipeline/*`. - `AGENTS.md`, `README.md`, `scripts/README.md` → commands, gates, paths, branch rules. - `.claude/skills/*` → the behaviour they instruct (forgejo.py subcommands, gate lists). - Product docs (`docs/use-cases/README.md`, `docs/templates.md`, `docs-site/content/`) → middleware/dashboard/agent behaviour **only where you can cite a contradicting file:line or a command's output**. ## Method 1. For each doc claim, locate the implementing code/command. Mark `SYNC`, `STALE` or `UNVERIFIABLE`. 2. Fix `STALE` with a minimal docs commit per area (`docs(<area>): …`, `Refs #<N>`). 3. Never "fix" a doc by making it vaguer; delete or correct the claim. 4. Post ONE comment: findings table (doc → claim → verdict → evidence), commits made, and an explicit `UNVERIFIABLE` list — claims that need a human or a live system to confirm. ## Constraints - Docs-only commits unless a code change is itself the drift (then say so in the comment first). - No closing keywords anywhere (`Refs #<N>` only). No pushing beyond your branch (the orchestrator publishes). - Boring path over speculation: an unverifiable claim is reported, not guessed at.

gotoi-agent added the

ai-assist

label

2026-10-07 20:35:02 +02:00

gotoi-agent added reference issue/66-docs-sync

2026-10-07 21:03:04 +02:00

gotoi-agent commented

2026-10-07 21:14:18 +02:00

Author

Collaborator

Claimed — branch issue/66-docs-sync. Doing: audit docs/agent-issue-pipeline.md, docs/agent-pipeline/.md, AGENTS.md, README.md, scripts/README.md and .claude/skills/ against scripts/code, fix STALE claims, report UNVERIFIABLE.

Claimed — branch `issue/66-docs-sync`. Doing: audit docs/agent-issue-pipeline.md, docs/agent-pipeline/*.md, AGENTS.md, README.md, scripts/README.md and .claude/skills/* against scripts/code, fix STALE claims, report UNVERIFIABLE.

gotoi-agent commented

2026-10-07 21:22:50 +02:00

Author

Collaborator

Issue #66 — Docs sync: verify every document against the code and fix the drift

Restated goal

Audit every agent-pipeline and repo document claim against the code, script, workflow, or live
system that actually implements it; record SYNC / STALE / UNVERIFIABLE per claim with
file:line or command output as evidence; fix every STALE claim with the minimum docs commit
(docs(<area>): …, Refs #66); post exactly one findings comment plus the four protocol comments.

"Done" for the operator means: the docs a contributor or the coding agent reads before acting —
AGENTS.md branch rules, docs/agent-issue-pipeline.md, docs/agent-pipeline/*.md,
scripts/README.md, .claude/skills/* — no longer send them to a branch, script, or cron that does
not exist, or omit one that does. Claims that cannot be checked without a human (cron internals,
Forgejo UI behaviour, operator credentials) are listed explicitly as UNVERIFIABLE, not guessed.

Scope

Files I intend to change (docs only):

AGENTS.md — Branches table, mermaid, and the three branch bullets (issue branches cut from and
PR'd against agent-develop, not develop).
docs/agent-pipeline/integration-branch.md — §"What is NOT wired yet".
docs/agent-pipeline/reviewer.md — the gotoi-run-capture "archived hourly" claim (cron disabled).
scripts/README.md — service registry (3 → 5) and the TUI layout/keys line.
.claude/skills/gotoi-issue-flow/SKILL.md — the closing "Auto-merge … do not exist" paragraph and
the "Two copies exist" count.

Files I will not touch (explicit non-scope):

Any middleware/, dashboard/, agent/ code — no contradicting code found yet; if the drift
turns out to be code, I stop and say so in the comment first (issue constraint).
/home/eduardez/workspace/gotoi (live checkout), ~/.hermes/** (outside the worktree, HARD LAW 5),
plans/ (product content, HARD LAW 6).
Other docs/agent-pipeline/*.md (threat-model, forgejo-enforcement, quarantine, hidden-tests,
verifier/verifier-matrix, queue-plan, anti-tampering, baseline, triage, ci-breakdown,
phase*) — spot-checked and matching so far; touched only if a new contradiction appears.

UC decision

No UC. The issue is internal dev/agent tooling documentation (docs/agent-issue-pipeline.md
itself documents tooling that lives outside the product), not a middleware route, agent entry point,
dashboard page, CLI subcommand, or operator-facing capability. docs/agent-issue-pipeline.md's own
header scopes it as operator-run pipeline docs. Adding a UC for a docs-sync pass would violate
gotoi-uc-gate step 2 (Implementation must cite a real handler). Nothing in the diff adds or renames
a feature, so docs/use-cases/_check.py must stay green without a new file; that is the gate.

Ordered tasks (each with its verifying command)

Confirm the four STALE findings against the live system, one command each.
Verify: git rev-list --left-right --count origin/develop...origin/agent-develop (topology),
ls scripts/agent-pipeline/ (integrate.py exists), ls ~/.hermes/cron/jobs.json +
rg -n 'gotoi-(integrator|run-capture)' ~/.hermes/cron/jobs.json (cron entries),
sed -n '63,118p' scripts/tui.py (SERVICES = 5) — already run, evidence in hand.
Fix AGENTS.md branch block. Issue branches cut from origin/agent-develop, PR targets
agent-develop; develop keeps the promotion role.
Verify: rg -n 'agent-develop' AGENTS.md shows the issue→agent-develop edges and no remaining
"PR targets develop" line for issue branches.
Fix docs/agent-pipeline/integration-branch.md §"What is NOT wired yet". integrate.py
exists (339 lines), is wired as cron gotoi-integrator (every 30 min, no_agent,
~/.hermes/scripts/gotoi-integrate.sh), and the runner law already targets agent-develop.
Verify: rg -n 'NOT wired' docs/agent-pipeline/integration-branch.md returns nothing stale;
every remaining claim in the section cites a file or command that exists.
Fix .claude/skills/gotoi-issue-flow/SKILL.md. Replace the "Auto-merge … do not exist"
paragraph with the live wiring; "two copies" → three, md5-identical.
Verify: rg -n 'do not exist|two copies' .claude/skills/gotoi-issue-flow/SKILL.md empty.
Fix scripts/README.md. Registry is five services; ASCII layout and key row updated.
Verify: rg -n 'middleware.*,.*postgres.*,.*dashboard' scripts/README.md shows 5 ids.
Fix docs/agent-pipeline/reviewer.md. The gotoi-run-capture cron is disabled
(paused 2026-10-07); state the artifact is a snapshot, not hourly.
Verify: rg -n 'run-capture' docs/agent-pipeline/reviewer.md no longer claims hourly archiving.
Gates. python3 docs/use-cases/_check.py; python3 scripts/check-ai-headers.py;
python3 scripts/check-type-mirror.py; rg -n 'Showing lines' --glob '!node_modules' --glob '!.git'.
No code touched → bun test/go test not required; run them anyway if anything beyond markdown moves.
Report + Done comment. /home/eduardez/workspace/gotoi-wt/meta/issue-66.report.md, then the
DONE|PARTIAL|BLOCKED comment with hashes and one line per gate.

Open questions → assumptions I proceed on

Is agent-develop really the live PR target? Three independent live sources agree: the
gotoi-issue-runner cron prompt (law 2), the gotoi-integrator APPLY output, and branch topology
(origin/agent-develop contains the merge commit b64f46a for issue #58). → Assume yes; AGENTS.md
is the drift.
Is the integrator "wired" if the cron is a no_agent script? Assumption: "wired" means a cron
entry exists and its script execs the repo tool — true here → the doc's "does not exist" claim is STALE.
Does fixing AGENTS.md on this branch fix develop? No — origin/develop:AGENTS.md carries the
same stale text; the promotion PR is the path. → Report it; do not touch develop.
~/.hermes/* drift (skill copy, run-capture cron) is outside the worktree → reported as
UNVERIFIABLE/note, never edited (HARD LAW 5).

Risk and fallback

Risk: renaming develop→agent-develop in AGENTS.md could contradict a genuine release-merge
rule. Fallback: keep the main/develop release sentence untouched, change only the
issue-branch rows/bullets, and note the split explicitly.
Risk: the AI-header gate flags an edited non-markdown file. Fallback: none of the planned
files carry the five-field header except docs/agent-pipeline/*.md if they have one — update Last:
there; AGENTS.md and scripts/README.md have no header.
Risk: a "fix" would make a claim vaguer. Fallback: delete or correct the claim instead
(issue constraint 3).

# Issue #66 — Docs sync: verify every document against the code and fix the drift ## Restated goal Audit every agent-pipeline and repo document claim against the code, script, workflow, or live system that actually implements it; record `SYNC` / `STALE` / `UNVERIFIABLE` per claim with `file:line` or command output as evidence; fix every `STALE` claim with the minimum docs commit (`docs(<area>): …`, `Refs #66`); post exactly one findings comment plus the four protocol comments. "Done" for the operator means: the docs a contributor or the coding agent reads before acting — `AGENTS.md` branch rules, `docs/agent-issue-pipeline.md`, `docs/agent-pipeline/*.md`, `scripts/README.md`, `.claude/skills/*` — no longer send them to a branch, script, or cron that does not exist, or omit one that does. Claims that cannot be checked without a human (cron internals, Forgejo UI behaviour, operator credentials) are listed explicitly as `UNVERIFIABLE`, not guessed. ## Scope Files I intend to change (docs only): - `AGENTS.md` — Branches table, mermaid, and the three branch bullets (issue branches cut from and PR'd against `agent-develop`, not `develop`). - `docs/agent-pipeline/integration-branch.md` — §"What is NOT wired yet". - `docs/agent-pipeline/reviewer.md` — the `gotoi-run-capture` "archived hourly" claim (cron disabled). - `scripts/README.md` — service registry (3 → 5) and the TUI layout/keys line. - `.claude/skills/gotoi-issue-flow/SKILL.md` — the closing "Auto-merge … do not exist" paragraph and the "Two copies exist" count. Files I will **not** touch (explicit non-scope): - Any `middleware/`, `dashboard/`, `agent/` code — no contradicting code found yet; if the drift turns out to be code, I stop and say so in the comment first (issue constraint). - `/home/eduardez/workspace/gotoi` (live checkout), `~/.hermes/**` (outside the worktree, HARD LAW 5), `plans/` (product content, HARD LAW 6). - Other `docs/agent-pipeline/*.md` (`threat-model`, `forgejo-enforcement`, `quarantine`, `hidden-tests`, `verifier`/`verifier-matrix`, `queue-plan`, `anti-tampering`, `baseline`, `triage`, `ci-breakdown`, `phase*`) — spot-checked and matching so far; touched only if a new contradiction appears. ## UC decision **No UC.** The issue is internal dev/agent tooling documentation (`docs/agent-issue-pipeline.md` itself documents tooling that lives outside the product), not a middleware route, agent entry point, dashboard page, CLI subcommand, or operator-facing capability. `docs/agent-issue-pipeline.md`'s own header scopes it as operator-run pipeline docs. Adding a UC for a docs-sync pass would violate `gotoi-uc-gate` step 2 (Implementation must cite a real handler). Nothing in the diff adds or renames a feature, so `docs/use-cases/_check.py` must stay green without a new file; that is the gate. ## Ordered tasks (each with its verifying command) 1. **Confirm the four STALE findings against the live system, one command each.** Verify: `git rev-list --left-right --count origin/develop...origin/agent-develop` (topology), `ls scripts/agent-pipeline/` (`integrate.py` exists), `ls ~/.hermes/cron/jobs.json` + `rg -n 'gotoi-(integrator|run-capture)' ~/.hermes/cron/jobs.json` (cron entries), `sed -n '63,118p' scripts/tui.py` (SERVICES = 5) — already run, evidence in hand. 2. **Fix `AGENTS.md` branch block.** Issue branches cut from `origin/agent-develop`, PR targets `agent-develop`; `develop` keeps the promotion role. Verify: `rg -n 'agent-develop' AGENTS.md` shows the issue→agent-develop edges and no remaining "PR targets `develop`" line for issue branches. 3. **Fix `docs/agent-pipeline/integration-branch.md` §"What is NOT wired yet".** `integrate.py` exists (339 lines), is wired as cron `gotoi-integrator` (every 30 min, `no_agent`, `~/.hermes/scripts/gotoi-integrate.sh`), and the runner law already targets `agent-develop`. Verify: `rg -n 'NOT wired' docs/agent-pipeline/integration-branch.md` returns nothing stale; every remaining claim in the section cites a file or command that exists. 4. **Fix `.claude/skills/gotoi-issue-flow/SKILL.md`.** Replace the "Auto-merge … do not exist" paragraph with the live wiring; "two copies" → three, md5-identical. Verify: `rg -n 'do not exist|two copies' .claude/skills/gotoi-issue-flow/SKILL.md` empty. 5. **Fix `scripts/README.md`.** Registry is five services; ASCII layout and key row updated. Verify: `rg -n 'middleware.*,.*postgres.*,.*dashboard' scripts/README.md` shows 5 ids. 6. **Fix `docs/agent-pipeline/reviewer.md`.** The `gotoi-run-capture` cron is disabled (paused 2026-10-07); state the artifact is a snapshot, not hourly. Verify: `rg -n 'run-capture' docs/agent-pipeline/reviewer.md` no longer claims hourly archiving. 7. **Gates.** `python3 docs/use-cases/_check.py`; `python3 scripts/check-ai-headers.py`; `python3 scripts/check-type-mirror.py`; `rg -n 'Showing lines' --glob '!node_modules' --glob '!.git'`. No code touched → `bun test`/`go test` not required; run them anyway if anything beyond markdown moves. 8. **Report + Done comment.** `/home/eduardez/workspace/gotoi-wt/meta/issue-66.report.md`, then the `DONE|PARTIAL|BLOCKED` comment with hashes and one line per gate. ## Open questions → assumptions I proceed on - **Is `agent-develop` really the live PR target?** Three independent live sources agree: the `gotoi-issue-runner` cron prompt (law 2), the `gotoi-integrator` APPLY output, and branch topology (`origin/agent-develop` contains the merge commit `b64f46a` for issue #58). → Assume yes; AGENTS.md is the drift. - **Is the integrator "wired" if the cron is a `no_agent` script?** Assumption: "wired" means a cron entry exists and its script execs the repo tool — true here → the doc's "does not exist" claim is STALE. - **Does fixing AGENTS.md on this branch fix `develop`?** No — `origin/develop:AGENTS.md` carries the same stale text; the promotion PR is the path. → Report it; do not touch `develop`. - **`~/.hermes/*` drift** (skill copy, run-capture cron) is outside the worktree → reported as `UNVERIFIABLE`/note, never edited (HARD LAW 5). ## Risk and fallback - **Risk:** renaming `develop`→`agent-develop` in AGENTS.md could contradict a genuine release-merge rule. **Fallback:** keep the `main`/`develop` release sentence untouched, change only the issue-branch rows/bullets, and note the split explicitly. - **Risk:** the AI-header gate flags an edited non-markdown file. **Fallback:** none of the planned files carry the five-field header except `docs/agent-pipeline/*.md` if they have one — update `Last:` there; `AGENTS.md` and `scripts/README.md` have no header. - **Risk:** a "fix" would make a claim vaguer. **Fallback:** delete or correct the claim instead (issue constraint 3).

gotoi-agent commented

2026-10-07 21:35:16 +02:00

Author

Collaborator

DONE — docs sync audit complete. Branch issue/66-docs-sync, 5 commits, not pushed.

Commits:

cd9b1d62 docs(agents): the branch law names agent-develop as the PR target
9dd9f93c docs(agent-pipeline): the integrator is wired; what blocks it is the CI trigger
f354d118 docs(agent-pipeline): S10 is built, the guards use the PR base ref, run-capture is off
bb397740 docs(scripts): the TUI registry is five services, not three
2d1d8bb4 docs(skills): three forgejo.py copies, and what actually blocks auto-merge

Gates (all exit 0):

docs/use-cases/_check.py        exit 0
scripts/check-ai-headers.py     exit 0  (573 ok, 0 missing, 0 malformed)
scripts/check-type-mirror.py    exit 0
rg -n 'Showing lines'           only hit: RELEASING_INSTRUCTIONS.md:37 (the command inside a checklist item)

bun test / bun run check / go test not run: markdown only, zero code touched.

STALE claims fixed (10 in 9 files):

AGENTS.md — said every change lands on develop and issue branches are cut from it. Really agent-develop is the PR target; develop takes one promotion PR per batch.
integration-branch.md — said integrate.py "does not exist" and "nothing merges"; tool + gotoi-integrator cron exist. It merges nothing because CI never reports on an agent-develop PR.
triage.md §3, docs/agent-issue-pipeline.md §2/§5 — same correction.
phase3-design.md — S10 hidden tests marked "not built"; hidden-tests.sh landed after the file.
anti-tampering.md — cited --base origin/develop; workflow passes github.base_ref.
reviewer.md — said the run report is archived hourly by gotoi-run-capture; that job is disabled.
scripts/README.md — registry is five services (docs, marketing missing), keys 1..5.
gotoi-issue-flow/SKILL.md — "two copies" of forgejo.py (three, md5-identical); integrator "does not exist".

Verified SYNC, no change needed: README env/API tables + agent-updates.ts routes + deploy paths; job HMAC is the enroll secret on both sides; most of docs/agent-pipeline/; queue-plan.md:67 and phase1-readiness.md:100 still accurate.

Needs a human decision (documented in integration-branch.md §"What is still missing", not fixed here — it is a workflow change, outside a docs issue):

CI never runs on a PR into agent-develop (build-agent.yml:15, agent-guards.yml:10 list main/develop). The branch rule requires the same five contexts, so the bot can never satisfy them and integrate.py refuses every merge — not-green on every tick, total_count: 0 on PRs #61/#64/#65, and PR#63/#64/#65 were all merged_by: EduarD3V. One line per workflow adds agent-develop.
origin/develop:AGENTS.md still carries the stale branch text — this fix only lands via the promotion PR.

UNVERIFIABLE (outside the worktree, law 5): ~/.hermes/skills/gotoi/gotoi-coding-agent/SKILL.md:373 says gotoi-run-capture runs hourly; the job is disabled (paused 2026-10-07T07:37).

**DONE** — docs sync audit complete. Branch `issue/66-docs-sync`, 5 commits, not pushed. Commits: ``` cd9b1d62 docs(agents): the branch law names agent-develop as the PR target 9dd9f93c docs(agent-pipeline): the integrator is wired; what blocks it is the CI trigger f354d118 docs(agent-pipeline): S10 is built, the guards use the PR base ref, run-capture is off bb397740 docs(scripts): the TUI registry is five services, not three 2d1d8bb4 docs(skills): three forgejo.py copies, and what actually blocks auto-merge ``` Gates (all exit 0): ``` docs/use-cases/_check.py exit 0 scripts/check-ai-headers.py exit 0 (573 ok, 0 missing, 0 malformed) scripts/check-type-mirror.py exit 0 rg -n 'Showing lines' only hit: RELEASING_INSTRUCTIONS.md:37 (the command inside a checklist item) ``` `bun test` / `bun run check` / `go test` not run: markdown only, zero code touched. STALE claims fixed (10 in 9 files): - `AGENTS.md` — said every change lands on `develop` and issue branches are cut from it. Really `agent-develop` is the PR target; `develop` takes one promotion PR per batch. - `integration-branch.md` — said `integrate.py` "does not exist" and "nothing merges"; tool + `gotoi-integrator` cron exist. It merges nothing because CI never reports on an `agent-develop` PR. - `triage.md` §3, `docs/agent-issue-pipeline.md` §2/§5 — same correction. - `phase3-design.md` — S10 hidden tests marked "not built"; `hidden-tests.sh` landed after the file. - `anti-tampering.md` — cited `--base origin/develop`; workflow passes `github.base_ref`. - `reviewer.md` — said the run report is archived hourly by `gotoi-run-capture`; that job is disabled. - `scripts/README.md` — registry is five services (docs, marketing missing), keys `1..5`. - `gotoi-issue-flow/SKILL.md` — "two copies" of `forgejo.py` (three, md5-identical); integrator "does not exist". Verified SYNC, no change needed: README env/API tables + `agent-updates.ts` routes + deploy paths; job HMAC is the enroll secret on both sides; most of `docs/agent-pipeline/`; `queue-plan.md:67` and `phase1-readiness.md:100` still accurate. Needs a human decision (documented in `integration-branch.md` §"What is still missing", not fixed here — it is a workflow change, outside a docs issue): 1. **CI never runs on a PR into `agent-develop`** (`build-agent.yml:15`, `agent-guards.yml:10` list `main`/`develop`). The branch rule requires the same five contexts, so the bot can never satisfy them and `integrate.py` refuses every merge — `not-green` on every tick, `total_count: 0` on PRs #61/#64/#65, and PR#63/#64/#65 were all `merged_by: EduarD3V`. One line per workflow adds `agent-develop`. 2. `origin/develop:AGENTS.md` still carries the stale branch text — this fix only lands via the promotion PR. UNVERIFIABLE (outside the worktree, law 5): `~/.hermes/skills/gotoi/gotoi-coding-agent/SKILL.md:373` says `gotoi-run-capture` runs hourly; the job is disabled (paused 2026-10-07T07:37).

gotoi-agent commented

2026-10-07 21:58:05 +02:00

Author

Collaborator

REVIEW: FIXED 2 — findings: (1) integration-branch.md claimed all operator merges happened on empty status lists and that every cron tick prints not-green — PR#63's head has 21 statuses and only 21 of 50 recorded ticks print not-green; fixed in aead4df. (2) phase3-design.md contradicted itself — S10 heading said built while 'What remains' still listed it pending, and S13 read 'built once the queue carried real work' beside an empty-queue verdict; fixed in 55872c1. (3) plan fidelity: 4 files outside the plan's Scope list were touched (agent-issue-pipeline.md, anti-tampering.md, phase3-design.md, triage.md) — all inside the issue's own scope or the plan's conditional clause, no fix needed. (4) report coverage gaps: no explicit verdict recorded for docs/agent-pipeline/hidden-tests.md, the product docs (use-cases/README.md, templates.md, docs-site), or the non-issue-flow skill gate lists — spot-checked SYNC here (hidden-tests.sh CLI matches hidden-tests.md; docs-site commands/ports match the code), rest UNFIXED. (5) AGENTS.md's new 'gotoi-agent is on agent-develop's merge allowlist' claim rests on integration-branch.md's proven table: GET /branch_protections 403s as the bot, not re-verifiable. Gates re-run green: _check.py, check-ai-headers.py, check-type-mirror.py, no 'Showing lines' artifacts, 9/9 files markdown, selftest-integrate 15/15, selftest-queue-plan 8/8. UNFIXED: (4) full product-doc and skill gate-list audit, (5) whitelist re-verification — both need operator/API access beyond this session.

REVIEW: FIXED 2 — findings: (1) integration-branch.md claimed all operator merges happened on empty status lists and that every cron tick prints not-green — PR#63's head has 21 statuses and only 21 of 50 recorded ticks print not-green; fixed in aead4df. (2) phase3-design.md contradicted itself — S10 heading said built while 'What remains' still listed it pending, and S13 read 'built once the queue carried real work' beside an empty-queue verdict; fixed in 55872c1. (3) plan fidelity: 4 files outside the plan's Scope list were touched (agent-issue-pipeline.md, anti-tampering.md, phase3-design.md, triage.md) — all inside the issue's own scope or the plan's conditional clause, no fix needed. (4) report coverage gaps: no explicit verdict recorded for docs/agent-pipeline/hidden-tests.md, the product docs (use-cases/README.md, templates.md, docs-site), or the non-issue-flow skill gate lists — spot-checked SYNC here (hidden-tests.sh CLI matches hidden-tests.md; docs-site commands/ports match the code), rest UNFIXED. (5) AGENTS.md's new 'gotoi-agent is on agent-develop's merge allowlist' claim rests on integration-branch.md's proven table: GET /branch_protections 403s as the bot, not re-verifiable. Gates re-run green: _check.py, check-ai-headers.py, check-type-mirror.py, no 'Showing lines' artifacts, 9/9 files markdown, selftest-integrate 15/15, selftest-queue-plan 8/8. UNFIXED: (4) full product-doc and skill gate-list audit, (5) whitelist re-verification — both need operator/API access beyond this session.