disinto-admin/disinto
1
0
Fork 0
Code Issues 11 Pull requests Projects Releases Packages Wiki Activity Actions

chore: gardener housekeeping 2026-04-09
All checks were successful
ci/woodpecker/push/ci Pipeline was successful
Details
ci/woodpecker/pr/ci Pipeline was successful
Details

Browse source
This commit is contained in:
Claude 2026-04-09 00:05:31 +00:00
parent d5e63a801e
commit faaaeb0a1f
10 changed files with 31 additions and 35 deletions
Download patch file Download diff file Expand all files Collapse all files

2
gardener/AGENTS.md
View file

@ -1,4 +1,4 @@
<!-- last-reviewed: ebadff09a1ce3c0140e4975985d383136a9a5504 -->
<!-- last-reviewed: d5e63a801ed48f9bd54c77e4915bc076b7490958 -->
# Gardener Agent
**Role**: Backlog grooming — detect duplicate issues, missing acceptance

13
gardener/pending-actions.json
View file

@ -1 +1,12 @@
[]
[
{
"action": "edit_body",
"issue": 454,
"body": "Flagged by AI reviewer in PR #453.\n\n## Problem\n\n`vault/vault-env.sh` `validate_vault_action` (line 70-73) validates field names against an allowlist that does NOT include `blast_radius`:\n\n```\nid|formula|context|secrets|model|tools|timeout_minutes\n```\n\nIf an operator adds `blast_radius = \"low\"` to a vault action TOML (as documented in `vault/SCHEMA.md` and supported by `vault/classify.sh`), the validator rejects it with \"ERROR: Unknown fields in TOML: blast_radius\". The feature is documented and implemented but cannot be exercised without triggering a validation error.\n\n## Fix\n\nAdd `blast_radius` to the allowed fields list in `validate_vault_action` in `vault/vault-env.sh`.\n\n---\n*Auto-created from AI review*\n\n## Affected files\n\n- `vault/vault-env.sh` (line 76 — `id|formula|context|secrets|model|tools|timeout_minutes|dispatch_mode` allowlist)\n\n## Acceptance criteria\n\n- [ ] `blast_radius` is added to the allowed fields list in `validate_vault_action` in `vault/vault-env.sh`\n- [ ] A vault action TOML containing `blast_radius = \"low\"` passes `validate_vault_action` without error\n- [ ] A vault action TOML containing an unrecognised field (e.g. `bogus_field = \"x\"`) still fails validation\n- [ ] `vault/validate.sh` and existing tests continue to pass after the change"
},
{
"action": "add_label",
"issue": 454,
"label": "backlog"
}
]