[Hooks Cannot See] (2) Require the output to entail the claim, not merely agree

[EdbertChan]

Summary

A written rule tells people how to support statements with command output. It helps readers judge whether evidence truly proves what a sentence says.

One check proved a single container image lacked a package. The report widened that result into a claim about newer runtime versions.

No check tested the version boundary, so the output was true but the sentence reached beyond it.

The new paragraph requires narrowing the sentence to the tested case and naming broader claims as open.

Review Claim

Approve one paragraph that requires pasted output to prove the full statement, not merely point in the same direction.

Review Lane

behavior

Review Unit

corpus-lesson

Safety Invariant

Only the body of pull request #519 changes. No commits, pushes, branch changes, labels, comments, or edits to any other pull request are made. The body is published only after the checker passes, and the live body is checked again after publication.

Slice Rationale

Split from slice (1) because docs/ecosystem.md forbids engine runtime and corpus lessons in the same PR, and scripts/check_ecosystem_boundaries.py rejected the combined branch by name.

It sits after (1) because (1) is the mechanical half of the same reflect pass; a reviewer who reads the detectors first has the concrete failure in hand before the general rule.

Non-goals

Does not add a hook. Judging whether pasted output entails a sentence is a meaning question, not a regex one; the mechanical candidate is an llm-judge and is not in this slice.

Does not touch engine/. That is slice (1).

Does not restate the existing missing-check or hedge rules, which already cover their cases.

Test Plan

Test Plan

Prose-only slice; the gates that apply are the skill and ecosystem checks.

check_hook_test_coverage exit=0
check_ecosystem_boundaries exit=0
check_skills_three_harnesses exit=0
check_skill_file_refs exit=0

Whole repo suite on the combined branch before the split:

Ran 463 tests in 1146.986s
OK
EXIT=0

• python3 scripts/check_ecosystem_boundaries.py
• python3 scripts/check_skill_file_refs.py
• python3 scripts/check_skills_three_harnesses.py
• bash scripts/run_all_tests.sh — 49 directories, 0 failures

Revert Plan

Revert Plan

• Safe to revert? Yes
• Revert command: git revert <sha>
• Post-revert steps: None. The paragraph disappears from the skill; no runtime behaviour depends on it.
• Data migration? No

[EdbertChan]

This pull request is part of a Mergify stack:

#	Pull Request	Link
1	[Hooks Cannot See] (1) Teach two hooks the checks they could not see	#518
2	[Hooks Cannot See] (2) Require the output to entail the claim, not merely agree	#519	👈

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_bac5280c-bd98-4100-8056-7d56a041abd8)