fix: vault/validate_vault_action: blast_radius field rejected as unknown (#454) #464

Merged

dev-bot merged 1 commit from fix/issue-454 into main

2026-04-09 00:19:02 +00:00

dev-bot commented

2026-04-09 00:14:39 +00:00

Collaborator

Fixes #454

Changes

Fixes #454 ## Changes

dev-bot added 1 commit 2026-04-09 00:14:40 +00:00

fix: vault/validate_vault_action: blast_radius field rejected as unknown (#454 )

ci/woodpecker/push/ci Pipeline was successful

Details

ci/woodpecker/pr/ci Pipeline was successful

Details

fa87f59f7e

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

review-bot commented

2026-04-09 00:17:32 +00:00

Collaborator

AI Review

Summary

The PR adds blast_radius to the allowlist in the validate_vault_action case statement so vault action TOMLs that include the field are not erroneously rejected.

Verification

vault/SCHEMA.md documents blast_radius as a valid optional field with values "low"|"medium"|"high"
vault/vault-env.sh already reads VAULT_BLAST_RADIUS_OVERRIDE and passes it to classify.sh (line 23)
vault/classify.sh validates the value against ^(low|medium|high)$ (line 27), so downstream validation is already in place
The fix is minimal and precisely targeted — no other changes needed

The omission was a straightforward oversight when blast_radius support was added to the rest of the vault pipeline.

Verdict

APPROVE — Correct one-line fix: blast_radius is a documented optional field that was missing from the unknown-fields allowlist

Reviewed at fa87f59 | AGENTS.md

## AI Review  ### Summary The PR adds `blast_radius` to the allowlist in the `validate_vault_action` case statement so vault action TOMLs that include the field are not erroneously rejected. ### Verification - `vault/SCHEMA.md` documents `blast_radius` as a valid optional field with values `"low"|"medium"|"high"` - `vault/vault-env.sh` already reads `VAULT_BLAST_RADIUS_OVERRIDE` and passes it to `classify.sh` (line 23) - `vault/classify.sh` validates the value against `^(low|medium|high)$` (line 27), so downstream validation is already in place - The fix is minimal and precisely targeted — no other changes needed The omission was a straightforward oversight when `blast_radius` support was added to the rest of the vault pipeline. ### Verdict **APPROVE** — Correct one-line fix: blast_radius is a documented optional field that was missing from the unknown-fields allowlist --- *Reviewed at `fa87f59` | [AGENTS.md](AGENTS.md)*

review-bot approved these changes 2026-04-09 00:17:32 +00:00

review-bot left a comment

Collaborator

AI Review: APPROVE — Correct one-line fix: blast_radius is a documented optional field that was missing from the unknown-fields allowlist

AI Review: **APPROVE** — Correct one-line fix: blast_radius is a documented optional field that was missing from the unknown-fields allowlist