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>

.claude/harness/CHANGELOG.md

@@ -46,3 +46,15 @@ or old harness during a heterogeneous rollout. See
   --fmt` formats. `post-bot-alert.sh` already uses `jq -nc --arg` (verified, no change needed).
 - Deferred (unchanged): full Python port = separate spec; Task 8 shard command bodies; promote
   guard to FATAL after a clean warn window; schedule memory-dream --apply-safe per-machine.
+
+## 1.4.1 — 2026-06-08  (Task 12: self-check smoke tests)
+- /self-check gained a `harness` category that locks in the 1.4.0 invariants (all read-only):
+  VERSION present + not older than manifest min_version; **skill-registry description budget**
+  (sum of all SKILL.md description: fields under manifest.harness.registry_desc_budget_chars —
+  WARN on regrowth, the metric that would catch Task 5 bloating back); global deploy targets
+  ~/.claude/skills + ~/.claude/commands populated (the Mac-wipe failure); harness-guard.sh wired
+  into sync.sh; core scripts parse (bash -n on sync/guard/now-phoenix); now-phoenix.sh emits a
+  valid date. Tunables live in baseline/manifest.json `harness` block. Verified: 9/9 PASS on this
+  machine; budget WARN trips correctly on a synthetic over-budget value.
+- Also reconciled the remaining "GrepAI first" docs (standard + CODING_GUIDELINES) with the
+  wiki-first recall hierarchy (started in CLAUDE_EXTENDED).

.claude/harness/VERSION

@@ -1 +1 @@
-1.4.0
+1.4.1