agent-develop #37

Merged
EduarD3V merged 13 commits from agent-develop into develop 2026-10-06 22:45:11 +02:00
Owner
No description provided.
Agents' branches target agent-develop; the bot is allowlisted to merge there and absent
from develop's whitelist, so the forge refuses the same actor one branch over. No closing
keyword: Refs #25, #26, #27, #28.
The server returns merge_whitelist_usernames reordered, so the positional comparison
reported a false READ-BACK MISMATCH on the first apply and told the operator to roll back
a rule that was already correct. Refs #28.
Verified every copy against the live pipeline. agent-develop was documented nowhere;
the ~/.claude copy of the issue-flow manual still claimed the runner merges into develop
automatically (removed from the repo copy on 2026-10-05) and is now re-synced; verifier.md
said shadow mode where the measured state is off; triage.md's auto-merge tier line had a
tier it could now name; the contract had no mention of the hidden test set.

Adds docs/agent-pipeline/integration-branch.md and a self-contained flow-canvas.html.
Refs #26, #28.
The contract's index pointed at .claude/skills/gotoi-coding-agent/, which does not exist:
the law lives in the Hermes profile. The canonical skill still named Forgejo 15.0.9 in two
places (the instance reports 16.0.5+gitea-1.22.0). Refs #26, #28.
An agent that stops on NEEDS-DECISION had no way to be answered: nothing in the law read
the thread, and the helper could not set a label at all. Adds forgejo.py label add|rm
(one label, never a wholesale set — that would drop ai-assist and unqueue the issue), the
needs_attention label as the triage skip, and the DECISION: protocol in the contract and
the omp manual. Only an operator-authored comment counts as a decision. Refs #26.
The skip rule as first written deadlocked every decision: triage skipped any issue carrying
the label, so the run could never pick one up to read the DECISION: comment, and so would
never clear the label. The label now means exactly 'waiting on the operator': a DECISION:
comment newer than the agent's own last comment on that thread unblocks the issue. Refs #26.
Sync, retarget, merge, promote. The bot merges each issue PR into agent-develop once its trial
merge is clean and its required checks are green, and one promotion PR carries the batch to
develop. Two things the first live run taught, both now fixed: a protected branch refuses
direct pushes (pre-receive hook declined), so the sync is a PR too; and the promote step read
stale refs after a server-side merge, so every step re-fetches. --quiet exists for a scheduler.
Refs #26.
feat: agent work integrates on agent-develop, and one promotion PR carries the batch
All checks were successful
agent-guards / test-tampering (pull_request) Successful in 32s
CI and agent release / check-docs (pull_request) Successful in 26s
CI and agent release / test-agent (pull_request) Successful in 1m32s
CI and agent release / test-dashboard (pull_request) Successful in 2m37s
CI and agent release / test-middleware (pull_request) Successful in 8m21s
CI and agent release / build (pull_request) Has been skipped
CI and agent release / release (pull_request) Has been skipped
CI and agent release / publish-images (pull_request) Has been skipped
4ea617f2e8
With more than one issue in flight, PRs to develop make the operator rebase each one and let two
issues collide on the shipping branch. Issue PRs now target agent-develop, the integrator merges
them there once their trial merge is clean and their checks are green, and a single promotion PR
carries the batch to develop. The run still never merges anything: the merging is the integrator's
separate job, so the session that wrote the code cannot land it. Refs #26.
Only grafana and checkmk define a pull adapter (middleware/src/providers/),
the source preset says "This preset is push-only"
(middleware/src/source-presets.ts:165), and middleware/tests/uc-mw-pull.test.ts:350-355
pins grafana/checkmk true, alertmanager false. The landing copy, the loop
diagram's ingest hop, the integrations summary, the hero console's sources
pane, and the docs-site port all claimed otherwise.

Copy now matches docs-site/content/docs/sources.mdx ("Uptime Kuma (push today)")
and docs-site/content/docs/faq.mdx, which were already correct.

Refs #28
Merge branch 'develop' into chore/integration-branch
Some checks failed
CI and agent release / check-docs (pull_request) Successful in 25s
agent-guards / test-tampering (pull_request) Successful in 35s
CI and agent release / test-agent (pull_request) Successful in 1m36s
CI and agent release / test-dashboard (pull_request) Successful in 2m33s
CI and agent release / build (pull_request) Has been cancelled
CI and agent release / release (pull_request) Has been cancelled
CI and agent release / publish-images (pull_request) Has been cancelled
CI and agent release / test-middleware (pull_request) Has been cancelled
1835ecfa99
Reviewed-on: #33
Merge pull request 'Issue #28: production and selling review of marketing + docs-site' (#36) from issue/28-production-selling-audit into agent-develop
All checks were successful
agent-guards / test-tampering (pull_request) Successful in 29s
CI and agent release / check-docs (pull_request) Successful in 29s
CI and agent release / test-agent (pull_request) Successful in 1m30s
CI and agent release / test-dashboard (pull_request) Successful in 2m22s
CI and agent release / test-middleware (pull_request) Successful in 14m2s
CI and agent release / release (pull_request) Has been skipped
CI and agent release / build (pull_request) Has been skipped
CI and agent release / publish-images (pull_request) Has been skipped
d40ffbb00b
Reviewed-on: #36
EduarD3V merged commit 0cba7e39c8 into develop 2026-10-06 22:45:11 +02:00
Sign in to join this conversation.
No description provided.