refactor(skills): put the coverage conditionals on their own lines

This commit is contained in:
Ian 2026-10-23 16:31:05 -04:00 • committed by Ahmed Allam
parent 898bbb4741
commit bac386e509
2 changed files with 12 additions and 4 deletions

View file

@ -33,8 +33,12 @@ that sentence, you are not in `ruled_out`.
**3. `open_proof_gap`** — the candidate is plausible, you could not
confirm it, and you also could not name a control that rules it out. This
is a legitimate, expected outcome. {% if coverage_tools %}Record it with
`record_coverage(outcome="needs_follow_up")`, carry{% else %}Carry{% endif %} it up in
{% if coverage_tools %}
is a legitimate, expected outcome. Record it with
`record_coverage(outcome="needs_follow_up")`, carry it up in
{% else %}
is a legitimate, expected outcome. Carry it up in
{% endif %}
`agent_finish(open_items=[...])`, and reflect it in `counterevidence` /
`confidence_rationale` if you file a related report. Do **not** convert
it to `ruled_out` to tidy up your worklist.

View file

@ -207,6 +207,10 @@ Not worth it: "this could use more validation" with no path, style and
maintainability complaints, and cosmetic variants of a candidate you
already opened.
Keep reading until no distinct plausible candidate remains{% if coverage_tools %} — then record
{% if coverage_tools %}
Keep reading until no distinct plausible candidate remains — then record
what you swept with `record_coverage`, including the families that came
back clean{% endif %}.
back clean.
{% else %}
Keep reading until no distinct plausible candidate remains.
{% endif %}