27cad971d0
* enhance(#2115): tighten AI-integration gate keywords per re-triage pin Apply the maintainer-pinned scope from the 2026-07-31 re-triage on #2115 exactly: `eval` -> `llm eval`, `ai system` dropped, every other token and the surrounding sentence byte-identical. Supersedes the stale-closed PR #3131, whose broader whole-word-matching rework went beyond the pin. * chore(#2115): set changeset fragment pr to 3431
908 B
908 B
type, pr
| type | pr |
|---|---|
| Changed | 3431 |
The plan-phase AI-integration capability gate no longer lists substring-collidable keywords — bare eval (a substring of ordinary phase-goal words like evaluation and retrieval) is replaced by llm eval, and the under-specified ai system is dropped, per maintainer triage on the linked issue. The gate is a capability prompt, not a hard block, so this is a precision improvement: phase goals like "add evaluation metrics" or "build the retrieval layer" no longer invite a spurious AI-SPEC branch, and genuinely AI-flavored goals still match on the precise framework and technique names. (#2115)