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

Merged

gotoi-agent merged 8 commits from issue/66-docs-sync into agent-develop

2026-10-08 06:23:24 +02:00

gotoi-agent commented

2026-10-07 22:04:30 +02:00

Collaborator

No description provided.

gotoi-agent added 7 commits

2026-10-07 22:04:30 +02:00

docs(agents): the branch law names agent-develop as the PR target cd9b1d62ff

AGENTS.md still said every change lands on develop and issue branches are cut
from it. Three live sources disagree: the runner cron's law 2 sends issue
branches from origin/agent-develop and targets agent-develop, origin/agent-develop
is an ancestor of HEAD while origin/develop is not, and the integrator cron (PR
#61) operates agent-develop -> develop as a promotion.

State the three-branch flow: agent-develop absorbs agent PRs, develop receives
one promotion PR per batch, main receives the release cut.

Refs #66

docs(agent-pipeline): the integrator is wired; what blocks it is the CI trigger 9dd9f93c6d

integration-branch.md said `integrate.py` does not exist and nothing merges into
agent-develop — stale since the tool and its cron landed. triage.md §3 and
agent-issue-pipeline.md §5 repeated the same claim in passing.

Read back what is actually true: integrate.py is wired as the gotoi-integrator
cron (every 30 min, no-agent) and does trial-merge + required-context scoring +
sync + one promotion PR, but neither workflow triggers a pull_request run on
agent-develop (build-agent.yml:15, agent-guards.yml:10), so the five required
contexts never report, every PR scores not-green, and every merge so far is the
operator's (PR#63/#64/#65, merged_by EduarD3V).

Refs #66

docs(agent-pipeline): S10 is built, the guards use the PR base ref, run-capture is off f354d118d5

Three claims that no longer match the code:
- phase3-design.md S10 'not built' — hidden-tests.sh (manifest/inject/run/proof)
  landed 2026-10-06 12:20 (commit 70d37dd), after this file (a385678, 10:17);
  hidden-tests.md describes the proof. Mark built, keep the container gap.
- anti-tampering.md cites --base origin/develop; agent-guards.yml:37,44 passes
  --base "origin/$BASE_REF" with BASE_REF: github.base_ref, so the guard runs on
  main PRs too.
- reviewer.md says the report file is archived hourly by gotoi-run-capture; that
  cron job is disabled (paused 2026-10-07T07:37), so the file stays in RUN_ROOT.

Refs #66

docs(scripts): the TUI registry is five services, not three bb39774042

scripts/tui.py SERVICES has middleware, postgres, dashboard, docs (:3000) and
marketing (:5174); scripts/dev.sh:27 SERVICE_IDS matches. The layout diagram
showed three services, the key row read 1..3, and the prose said 'only gotoi
services (middleware, postgres, dashboard)'.

Also fix the branch-switch sentence: _restart_repo_services restarts every
running service whose type is 'bun', which now includes docs and marketing.

Refs #66

docs(skills): three forgejo.py copies, and what actually blocks auto-merge 2d1d8bb48b

The skill said two API-helper copies; there are three, md5-identical
(679a921f6181cfe6333c2acacbc8c4f1) — repo, ~/.claude and the orchestrator's
~/.hermes skill. The closing paragraph said the integrator 'does not exist';
it is wired as the gotoi-integrator cron and the runner law already targets
agent-develop — it merges nothing because CI never reports on an agent-develop
PR.

Refs #66

review(agent-pipeline): PR63's head reported statuses; silent ticks are not not-green aead4dffcd

The evidence block claimed every merge into the repo happened on heads with an
empty status list and that every cron tick prints not-green. API check: PR#63's
head carries 21 statuses (CI runs on develop PRs), and only ticks that see an
open PR print not-green (21 of 50 recorded outputs; the rest are silent).

Refs #66

review(agent-pipeline): phase3 no longer contradicts its own S10/S13 headings 55872c191d

The heading said S10 built while 'What remains' still listed it as pending, and
S13 read 'built once the queue carried real work' next to an empty-queue verdict
in the present tense. Remaining item is now the S10 container path; S13's
requirement/evidence text is marked as the original verdict and the planner is
described as offline-only (queue-plan.md: nothing calls it yet, selftest 8/8).

Refs #66

gotoi-agent referenced this pull request

2026-10-07 22:04:41 +02:00

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

EduarD3V added 1 commit

2026-10-08 06:09:53 +02:00

Merge branch 'agent-develop' into issue/66-docs-sync 924b95eac8

gotoi-agent merged commit 84ff46b58c into agent-develop

2026-10-08 06:23:24 +02:00

gotoi-agent referenced this pull request from a commit

2026-10-08 06:23:29 +02:00

Merge pull request 'Issue #66: Docs sync — verify every document against the code and fix the drift' (#69) from issue/66-docs-sync into agent-develop

gotoi-agent referenced this pull request