feat(self-check): harness smoke tests lock in the 1.4.0 invariants (VERSION 1.4.1)

Adds a 'harness' category to /self-check (Task 12, self-check half) so the harness-
optimization gains can't silently regress. All read-only / non-invasive:
- VERSION marker present + not older than manifest.harness.min_version
- skill-registry description budget (sum of all SKILL.md description: fields under
  registry_desc_budget_chars) -- the metric that catches Task 5 bloating back
- global deploy targets ~/.claude/skills + ~/.claude/commands populated (Mac-wipe failure)
- harness-guard.sh present + wired into sync.sh
- core scripts parse (bash -n on sync/guard/now-phoenix); now-phoenix.sh emits a valid date

Tunables in baseline/manifest.json 'harness' block. Verified 9/9 PASS; budget WARN
negative-tested at a synthetic over-budget value.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

specs/claudetools-harness-optimization/plan.md

@@ -40,6 +40,10 @@
   left in place — recall grep covers both layouts; NO mass migration (would break wiki `source_logs`
   refs for low payoff).
 - **P1+P2+P3 COMPLETE (2026-06-08, VERSION 1.4.0).**
+- [DONE] Task 12 (self-check half) — `/self-check` now has a `harness` category enforcing the
+  1.4.0 invariants (VERSION/min-version, skill-registry description budget, global deploy targets
+  populated, guard wired, core scripts parse, now-phoenix valid). Read-only; 9/9 PASS; budget WARN
+  negative-tested. Tunables in `self-check/baseline/manifest.json` `harness` block. (VERSION 1.4.1.)
 - REMAINING (ops follow-ups, not blocking):
   - Promote the warn-only guard (Task 4) to FATAL after a clean warn window (check
     `.claude/harness/guard.log` across the fleet).