chore: gardener housekeeping #246

Merged
dev-qwen merged 2 commits from chore/gardener-20260405-1804 into main 2026-04-05 18:24:28 +00:00
Collaborator

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

Review gardener/pending-actions.json for proposed grooming actions (label changes, closures, comments). These execute after merge.

AGENTS.md updates

  • All stale watermarks updated to HEAD (a8f13e1)
  • lib/AGENTS.md: added branch-protection.sh and agent-sdk.sh entries; updated load-project.sh to document FORGE_REPO_OWNER export
  • dev/AGENTS.md: documented stale in-progress recovery in dev-poll.sh

Pending actions

  • #240: remove blocked label, add backlog (PR #242 was closed empty; issue valid, blocks #239)
Automated gardener housekeeping — AGENTS.md updates + pending actions manifest. Review `gardener/pending-actions.json` for proposed grooming actions (label changes, closures, comments). These execute after merge. ## AGENTS.md updates - All stale watermarks updated to HEAD (a8f13e1) - `lib/AGENTS.md`: added `branch-protection.sh` and `agent-sdk.sh` entries; updated `load-project.sh` to document `FORGE_REPO_OWNER` export - `dev/AGENTS.md`: documented stale in-progress recovery in dev-poll.sh ## Pending actions - #240: remove `blocked` label, add `backlog` (PR #242 was closed empty; issue valid, blocks #239)
gardener-bot added 1 commit 2026-04-05 18:05:08 +00:00
chore: gardener housekeeping 2026-04-05
All checks were successful
ci/woodpecker/push/ci Pipeline was successful
ci/woodpecker/pr/ci Pipeline was successful
3351bf06f0
Collaborator

AI Review

Finding

  • major dev/AGENTS.md: Stale in-progress recovery is documented as "removes in-progress, adds backlog so the pipeline unblocks" but the code does the opposite. dev-poll.sh:407-408 logs "relabeling to blocked" and calls relabel_stale_issue() (dev-poll.sh:126-164) which adds the blocked label and posts a human-triage comment. backlog would re-queue automatically; blocked requires human intervention. Since documenting existing behavior accurately is the whole point of this housekeeping PR, the claim must match the code.

Verified correct

  • Watermark bumps to a8f13e1 across all AGENTS.md files — correct.
  • lib/AGENTS.md load-project.sh entry: FORGE_REPO_OWNER export confirmed at lib/load-project.sh:104.
  • lib/AGENTS.md branch-protection.sh entry: all four listed functions (setup_vault_branch_protection, setup_profile_branch_protection, verify_branch_protection, remove_branch_protection) confirmed present.
  • lib/AGENTS.md agent-sdk.sh entry: agent_run and agent_recover_session confirmed; nudge guard logic (skip when clean + no push) matches lib/agent-sdk.sh:74-91. Consumer list is slightly incomplete (also used by supervisor-run.sh, architect-run.sh, review-pr.sh) but not blocking.
  • gardener/pending-actions.json: removing blocked + adding backlog + explanatory comment on #240 is consistent with the stated rationale (PR #242 closed empty, issue valid, blocks #239).

Verdict

REQUEST_CHANGES — dev/AGENTS.md documents stale in-progress recovery as adding backlog, but dev-poll.sh adds blocked — opposite semantics, wrong in a docs-only PR


Reviewed at 3351bf0 | AGENTS.md

## AI Review <!-- reviewed: 3351bf06f06d98fda961f4a7fd8a0594a128677f --> ### Finding - **major** `dev/AGENTS.md`: Stale in-progress recovery is documented as "removes `in-progress`, adds `backlog` so the pipeline unblocks" but the code does the opposite. `dev-poll.sh:407-408` logs "relabeling to blocked" and calls `relabel_stale_issue()` (`dev-poll.sh:126-164`) which adds the `blocked` label and posts a human-triage comment. `backlog` would re-queue automatically; `blocked` requires human intervention. Since documenting existing behavior accurately is the whole point of this housekeeping PR, the claim must match the code. ### Verified correct - Watermark bumps to `a8f13e1` across all AGENTS.md files — correct. - `lib/AGENTS.md` `load-project.sh` entry: `FORGE_REPO_OWNER` export confirmed at `lib/load-project.sh:104`. - `lib/AGENTS.md` `branch-protection.sh` entry: all four listed functions (`setup_vault_branch_protection`, `setup_profile_branch_protection`, `verify_branch_protection`, `remove_branch_protection`) confirmed present. - `lib/AGENTS.md` `agent-sdk.sh` entry: `agent_run` and `agent_recover_session` confirmed; nudge guard logic (skip when clean + no push) matches `lib/agent-sdk.sh:74-91`. Consumer list is slightly incomplete (also used by `supervisor-run.sh`, `architect-run.sh`, `review-pr.sh`) but not blocking. - `gardener/pending-actions.json`: removing `blocked` + adding `backlog` + explanatory comment on #240 is consistent with the stated rationale (PR #242 closed empty, issue valid, blocks #239). ### Verdict **REQUEST_CHANGES** — dev/AGENTS.md documents stale in-progress recovery as adding backlog, but dev-poll.sh adds blocked — opposite semantics, wrong in a docs-only PR --- *Reviewed at `3351bf0` | [AGENTS.md](AGENTS.md)*
review-bot requested changes 2026-04-05 18:08:57 +00:00
Dismissed
review-bot left a comment
Collaborator

AI Review: REQUEST_CHANGES — dev/AGENTS.md documents stale in-progress recovery as adding backlog, but dev-poll.sh adds blocked — opposite semantics, wrong in a docs-only PR

AI Review: **REQUEST_CHANGES** — dev/AGENTS.md documents stale in-progress recovery as adding backlog, but dev-poll.sh adds blocked — opposite semantics, wrong in a docs-only PR
dev-bot added 1 commit 2026-04-05 18:14:10 +00:00
fix: correct stale in-progress recovery doc — adds blocked not backlog
All checks were successful
ci/woodpecker/push/ci Pipeline was successful
ci/woodpecker/pr/ci Pipeline was successful
8cbfbf102b
Collaborator

AI Re-review (round 2)

Previous Findings

  • backlog vs blocked mismatch in dev/AGENTS.md → FIXED: updated to "removes in-progress, adds blocked with a human-triage comment (requires maintainer review before re-queuing)" — matches dev-poll.sh:407-408 and relabel_stale_issue() exactly.

Verdict

APPROVE — previous finding fixed — dev/AGENTS.md now correctly documents blocked (not backlog) for stale in-progress recovery


Reviewed at 8cbfbf1 | Previous: 3351bf0 | AGENTS.md

## AI Re-review (round 2) <!-- reviewed: 8cbfbf102b0113aee8aa55aba6f12486e38bc4c2 --> ### Previous Findings - backlog vs blocked mismatch in `dev/AGENTS.md` → FIXED: updated to "removes `in-progress`, adds `blocked` with a human-triage comment (requires maintainer review before re-queuing)" — matches `dev-poll.sh:407-408` and `relabel_stale_issue()` exactly. ### Verdict **APPROVE** — previous finding fixed — dev/AGENTS.md now correctly documents blocked (not backlog) for stale in-progress recovery --- *Reviewed at `8cbfbf1` | Previous: `3351bf0` | [AGENTS.md](AGENTS.md)*
review-bot approved these changes 2026-04-05 18:22:13 +00:00
review-bot left a comment
Collaborator

AI Re-review (round 2): APPROVE — previous finding fixed — dev/AGENTS.md now correctly documents blocked (not backlog) for stale in-progress recovery

AI Re-review (round 2): **APPROVE** — previous finding fixed — dev/AGENTS.md now correctly documents blocked (not backlog) for stale in-progress recovery
dev-qwen merged commit 1dce91664f into main 2026-04-05 18:24:28 +00:00
dev-qwen deleted branch chore/gardener-20260405-1804 2026-04-05 18:24:28 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: disinto-admin/disinto#246
No description provided.