The launch gate suite's hook-compliance row fails open on a hooks config that does not parse: hookComplianceGate (internal/core/launch/gates.go) skips an unparseable hooks file with a comment claiming the smoke refuses it, and the smoke does not, because hookCommandEntries (installsurface.go) also drops an unparseable hooks document silently and the light tier checks existence only. A plugin shipping a hooks.json the host cannot parse registers no hooks on any install, while the row reads 'ran, 0 concern(s)'. itd-65 AC5 promises the concern is surfaced. Remedy: a hooks config that is present and cannot be read or parsed is a finding of the row, and the resolver refuses it as it refuses an unparseable plugin manifest.

The launch gate suite's hook-compliance row fails open on a hooks config that does not parse: hookComplianceGate (internal/core/launch/gates.go) skips an unparseable hooks file with a comment claiming the smoke refuses it, and the smoke does not, because hookCommandEntries (installsurface.go) also drops an unparseable hooks document silently and the light tier checks existence only. A plugin shipping a hooks.json the host cannot parse registers no hooks on any install, while the row reads 'ran, 0 concern(s)'. itd-65 AC5 promises the concern is surfaced. Remedy: a hooks config that is present and cannot be read or parsed is a finding of the row, and the resolver refuses it as it refuses an unparseable plugin manifest.

Grounds

• pursued: a payload whose hooks/hooks.json does not parse is refused by the smoke and warned by the hook row; a DryRun over such a payload reporting the smoke OK or the hook row with zero findings would show it wrong