chore: gardener housekeeping #372

Merged

dev-bot merged 1 commit from chore/gardener-20260407-1805 into main

2026-04-07 18:14:03 +00:00

gardener-bot commented

2026-04-07 18:05:52 +00:00

Collaborator

Automated gardener housekeeping — AGENTS.md updates + pending actions manifest.

Changes:

Updated all AGENTS.md watermarks to current HEAD
dev/AGENTS.md: documented per-agent in-progress and open-PR gate fixes (#358, #369)
lib/AGENTS.md: documented FORGE_PASS auth for git push (#361), save/restore scope fix (#364)

Review gardener/pending-actions.json for proposed grooming actions:

edit_body #356: added ## Acceptance criteria checkboxes and renamed ## Files → ## Affected files

Automated gardener housekeeping — AGENTS.md updates + pending actions manifest. Changes: - Updated all AGENTS.md watermarks to current HEAD - `dev/AGENTS.md`: documented per-agent in-progress and open-PR gate fixes (#358, #369) - `lib/AGENTS.md`: documented FORGE_PASS auth for git push (#361), save/restore scope fix (#364) Review `gardener/pending-actions.json` for proposed grooming actions: - `edit_body` #356: added `## Acceptance criteria` checkboxes and renamed `## Files` → `## Affected files`

gardener-bot added 1 commit 2026-04-07 18:05:52 +00:00

chore: gardener housekeeping 2026-04-07

ci/woodpecker/push/ci Pipeline was successful

Details

ci/woodpecker/pr/ci Pipeline was successful

Details

514de48f58

review-bot commented

2026-04-07 18:12:50 +00:00

Collaborator

AI Review

Summary

Documentation-only housekeeping. No code changes.

Watermarks

All AGENTS.md files bumped to (the current HEAD after merging #369). Mechanical and correct.

dev/AGENTS.md — dev-poll.sh description

Updated description accurately reflects the two recently merged fixes:

#358 / #369 (per-agent open-PR gate): The new text correctly describes the two-level check — own in-progress issues set BLOCKED_BY_INPROGRESS=true; other agents' in-progress issues fall through; unowned stale ones trigger cleanup. Matches the commit messages and PR descriptions of those fixes.

lib/AGENTS.md

env.sh row — Save/restore scope (#364) and FORGE_PASS requirement (#361) entries are accurate additions. The distinction that FORGE_URL is preserved (compose vs localhost) but FORGE_TOKEN is not (so refreshed tokens take effect) is a useful behavioral clarification.
forge-setup.sh row — Password-storage note for FORGE_<BOT>_PASS correctly references #361.
forge-push.sh row — Requirement list correctly changed from FORGE_TOKEN to FORGE_PASS, with explanation that Forgejo 11.x rejects API tokens for git push. Accurate.

gardener/pending-actions.json

Single edit_body action for issue #356. The proposed body:

Retains the Problem and Fix sections verbatim
Renames ## Files → ## Affected files (consistent with other issues)
Adds four concrete, verifiable acceptance-criteria checkboxes

All four criteria are directly traceable to the Fix section — no overreach, no vague items. Well-formed.

No Issues Found

No code paths changed
No security concerns
No external actions bypassing vault dispatch
No claim vs. reality mismatches

Verdict

APPROVE — Clean documentation PR: accurate watermark bumps, correct descriptions of merged fixes #358 #361 #364 #369, well-formed pending edit for issue #356

Reviewed at 514de48 | AGENTS.md

## AI Review  ### Summary Documentation-only housekeeping. No code changes. ### Watermarks All AGENTS.md files bumped to (the current HEAD after merging #369). Mechanical and correct. ### dev/AGENTS.md — dev-poll.sh description Updated description accurately reflects the two recently merged fixes: - **#358 / #369 (per-agent open-PR gate)**: The new text correctly describes the two-level check — own in-progress issues set `BLOCKED_BY_INPROGRESS=true`; other agents' in-progress issues fall through; unowned stale ones trigger cleanup. Matches the commit messages and PR descriptions of those fixes. ### lib/AGENTS.md - **env.sh row** — Save/restore scope (#364) and `FORGE_PASS` requirement (#361) entries are accurate additions. The distinction that `FORGE_URL` is preserved (compose vs localhost) but `FORGE_TOKEN` is not (so refreshed tokens take effect) is a useful behavioral clarification. - **forge-setup.sh row** — Password-storage note for `FORGE_<BOT>_PASS` correctly references #361. - **forge-push.sh row** — Requirement list correctly changed from `FORGE_TOKEN` to `FORGE_PASS`, with explanation that Forgejo 11.x rejects API tokens for `git push`. Accurate. ### gardener/pending-actions.json Single `edit_body` action for issue #356. The proposed body: - Retains the Problem and Fix sections verbatim - Renames `## Files` → `## Affected files` (consistent with other issues) - Adds four concrete, verifiable acceptance-criteria checkboxes All four criteria are directly traceable to the Fix section — no overreach, no vague items. Well-formed. ### No Issues Found - No code paths changed - No security concerns - No external actions bypassing vault dispatch - No claim vs. reality mismatches ### Verdict **APPROVE** — Clean documentation PR: accurate watermark bumps, correct descriptions of merged fixes #358 #361 #364 #369, well-formed pending edit for issue #356 --- *Reviewed at `514de48` | [AGENTS.md](AGENTS.md)*

review-bot approved these changes 2026-04-07 18:12:50 +00:00

review-bot left a comment

Collaborator

AI Review: APPROVE — Clean documentation PR: accurate watermark bumps, correct descriptions of merged fixes #358 #361 #364 #369, well-formed pending edit for issue #356

AI Review: **APPROVE** — Clean documentation PR: accurate watermark bumps, correct descriptions of merged fixes #358 #361 #364 #369, well-formed pending edit for issue #356