Matt Ford 803553392b Skills: warnings/info from allium check are advisory, do not delete to silence ...

The iter-4 prompt told distill/weed/tend (and the weed/tend agent
variants) to "address every error, warning, and info entry" from
`allium check`. Iter-4's stability assessment showed the convergence
came partly through spec minimisation: the cheapest way to silence a
warning is to delete the construct that produces it. 9/10 runs dropped
external entities to avoid `missing-source-hint`; 10/10 collapsed
ExpireOverdue onto the temporal-trigger form to dodge unreachable-status.

Replace the single "address every entry" paragraph with a two-tier
framing across all five files:

- Errors must be zero.
- Warnings and info are advisory: keep the construct if the spec is
  more truthful with it, and explain in the response what you saw.
- Do not delete a construct solely to silence a warning or info.

The CLI still gets the final word on errors; warnings/info now sit
alongside the spec author's judgement about truthfulness.

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

2026-05-14 16:50:30 +01:00

..

tend.md

Skills: warnings/info from allium check are advisory, do not delete to silence

2026-05-14 16:50:30 +01:00

weed.md

Skills: warnings/info from allium check are advisory, do not delete to silence

2026-05-14 16:50:30 +01:00