chore: gardener housekeeping #295
No reviewers
Labels
No labels
action
backlog
blocked
bug-report
in-progress
prediction/actioned
prediction/dismissed
prediction/unreviewed
priority
tech-debt
underspecified
vision
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: disinto-admin/disinto#295
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/gardener-20260406-1205"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Automated gardener housekeeping — AGENTS.md updates + pending actions manifest.
Review
gardener/pending-actions.jsonfor proposed grooming actions (label changes, closures, comments). These execute after merge.AGENTS.md updates
8d32168AGENTS.md: removed deletedprofile.sh, addedstack-lock.shto lib listinglib/AGENTS.md: removed deletedfile-action-issue.shentry; addedstack-lock.shandci-log-reader.pyentries; updatedformula-session.shto documentresolve_agent_identity()and notecheck_memory()consolidation into env.sh; updatedci-helpers.shto reflect removal ofensure_blocked_label_id(); fixedsecret-scan.shsourced-by referencearchitect/AGENTS.md: fixed invalidauto-generatedwatermarkPending actions (4 items)
#288: enrich body with acceptance criteria + affected files, promote tobacklog#275: enrich body with acceptance criteria + affected files, promote tobacklogBoth are clear, focused tech-debt fixes ready for dev-agent pickup.
AI Review — Error\n\nReview failed.\n---\n
b1695d8AI Review
Summary
Pure housekeeping: watermark bumps, lib table corrections, and two well-formed pending-actions entries. All structural claims verified against the actual code.
Verified correct
8d32168— matches HEAD.lib/.lib/.lib/stack-lock.sh; functions match the table description.lib/ci-log-reader.py;ci_get_logs()in ci-helpers.sh calls it at line 276.issue-lifecycle.shdoes source it (lines 30–31). Previousfile-action-issue.shreference was stale.memory_guard()lives in env.sh.AGENT_IDENTITYonly (see note below).git fetch originat lines 131 and 162; description and acceptance criteria are accurate.jq -r '.[0].sha1 // empty'at line 797; description and acceptance criteria are accurate.auto-generatedwatermark fixed: Correct.Findings
minor
lib/AGENTS.md(stack-lock.sh row, Sourced-by column): Listsdocker/edge/dispatcher.shas a user, butdispatcher.shcontains no reference tostack-lock.sh. The actual caller isdocker/reproduce/entrypoint-reproduce.sh. Thereproduce formulahalf of the entry is correct.minor
lib/AGENTS.md(formula-session.sh row): The new inline description reads "resolve_agent_identity()— setsFORGE_TOKEN,AGENT_IDENTITY,FORGE_REMOTEfrom per-agent token env vars and FORGE_URL remote detection." The function (line 59–74) only setsAGENT_IDENTITY.FORGE_REMOTEis set by the separateresolve_forge_remote()function (line 83);FORGE_TOKENis not set here at all. The description over-attributes to a single function what is actually a two-function pair.Neither finding affects runtime behaviour — they are documentation-only inaccuracies. Both can be corrected in the next gardener cycle.
Verdict
APPROVE — Watermarks, lib table, and pending-actions are all accurate; two minor doc inaccuracies noted but non-blocking
Reviewed at
b1695d8| AGENTS.mdAI Review: APPROVE — Watermarks, lib table, and pending-actions are all accurate; two minor doc inaccuracies noted but non-blocking