feat(gates): wire GATE 0 into the four orchestrator skill restatements

The include is authoritative, but feat/bugfix/ship-feature/init-project
each restate the verify loop inline — an orchestrator following the
restatement alone would have skipped the floor. Each now carries the
GATE 0 bullet ahead of GATE 1 (4 new structure locks, flip-tested).
The contract-interview weight table stops promising a hotfix oracle
nothing executes: hotfix runs no floor, the hotfixer runs the suite
itself. CHANGELOG extended with the wiring + the RED result.

lib/contract-interview.md

@@ -140,10 +140,11 @@ Print one line to the user, then continue the flow:
 | init-project | Full. The interviewer's PROJECT BRIEF pours into the contract (V1 features → criteria). |
 | onboard | Audit-scope contract (interview answers → what to audit, which axes). |
 
-Oracles follow the same proportion. hotfix: the build/tests criterion carries
-its `CHECK:`, nothing else. feat / bugfix: the suite criterion at minimum, and
-for bugfix the regression test the DIAGNOSIS names — its `CHECK:` runs that
-test alone, so a green result means the reproduction actually flipped.
+Oracles follow the same proportion. hotfix: none — that flow runs no floor
+(and no verifier); the hotfixer runs build/tests itself. feat / bugfix: the
+suite criterion at minimum, and for bugfix the regression test the DIAGNOSIS
+names — its `CHECK:` runs that test alone, so a green result means the
+reproduction actually flipped.
 ship-feature / init-project: build, suite, and every criterion a command can
 settle. onboard: audit criteria are mostly judgement — leave them oracle-free
 rather than invent a check that cannot fail.