CUST-WP-0060 T01-T03: canon ratified active, terminology v0.2, schemas + validator

- work-record-types_v0.1.md + autonomy-lanes_v0.1.md: status active
  (founder ratification 2026-07-20, hub decision f4640f9e); registry
  grandfathers legacy task-id variants (-T1, -LEGACY-Txx)
- workplan-terminology-fleet: v0.2 addendum — work-record umbrella,
  kind vocabulary, suggestion as legacy bridge name (T02)
- canon/standards/schemas/work-records/: spine + intake/decision/
  engagement JSON schemas (T03); conditional spine requirements,
  historical grace for terminal records
- tools/validate_work_records.py: registry+schema validator for CI
  (T04); jsonschema with inlined spine refs, fallback checks without;
  proof runs clean: the-custodian 384 records, binky-control 45

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

canon/standards/autonomy-lanes_v0.1.md

@@ -3,7 +3,7 @@ id: canon-autonomy-lanes
 type: standard
 title: "Autonomy Lanes (Fleet) v0.1"
 domain: custodian
-status: draft
+status: active
 version: "0.1"
 created: "2026-07-20"
 updated: "2026-07-20"
@@ -16,7 +16,7 @@ origin: binky-control/AutonomyPolicy.md (ratified for Binky 2026-07-16, DEC-2026
 
 # Autonomy Lanes (Fleet) v0.1
 
-> Draft pending founder ratification (CUST-WP-0060-T01). Promotes the
+> Ratified by founder 2026-07-20 (CUST-WP-0060-T01, hub decision f4640f9e). Promotes the
 > binky-control AutonomyPolicy lane model to fleet canon, unchanged in
 > substance. binky-control's `AutonomyPolicy.md` remains the company-level
 > policy instance; this standard makes the lane vocabulary and enforcement