fix(review): resolve the judged revalidation, setup-authority, plan-gate and findings-record ambiguities

The census review workflow judge scored clarity/actionability 3 on both
attempts: smoke-clock limits appeared to forbid post-repair revalidation,
the caller deadline was undefined, 'ask for setup' conflicted with the
report-only browser rule, fallback-sourced HIGH discrepancies had no gate
decision, and the Step 5.8 record omitted adversarial findings.

test/ship-workflow-clarity.test.ts

@@ -14,7 +14,7 @@ test('Ship initializes and applies its smoke guard independently of required pla
     expect(body).toContain('Run the shared preflight; start its smoke guard once. Guard every smoke probe.');
     expect(body.indexOf('start its smoke guard once')).toBeLessThan(body.indexOf('**3. Run smoke and plan checks.**'));
     expect(body).toContain('Required even for small diffs or missing plans/servers');
-    expect(body).toContain('Then run required plan checks, even after smoke expires');
+    expect(body).toContain('Then run required plan checks and revalidation, even after smoke expires');
     expect(body).toContain('using the same procedure but no smoke guard; never reset the clock');
   }
 });