@chrono-meta/fh-gate 1.4.52 → 1.4.54

package/plugins/fh-commons/.claude-plugin/plugin.json

@@ -0,0 +1,23 @@
+{
+  "name": "fh-commons",
+  "version": "1.4.54",
+  "engines": {
+    "claudeCode": ">=1.0.0"
+  },
+  "description": "Cross-project utility skill bundle — 4 skills + 1 agent. Domain-agnostic and portable: convergence-loop, deliberation, mcp-circuit-breaker, token-budget-gate + quench-challenger agent.",
+  "author": {
+    "name": "chrono-meta",
+    "email": "chrono-meta@users.noreply.github.com"
+  },
+  "keywords": [
+    "commons",
+    "convergence-loop",
+    "gate-reinforcement",
+    "multi-round-validation",
+    "deliberation",
+    "multi-perspective-synthesis",
+    "forge-skill",
+    "domain-agnostic",
+    "cross-project"
+  ]
+}

package/plugins/fh-meta/.claude-plugin/plugin.json

@@ -0,0 +1,36 @@
+{
+  "name": "fh-meta",
+  "version": "1.4.54",
+  "engines": {
+    "claudeCode": ">=1.0.0"
+  },
+  "description": "Hub meta-engineering toolkit — 33 skills + 7 agents. New in 1.4.48: phantom-quench + steel-quench gain external frontier anchors (arXiv:2607.02052 package-hallucination; arXiv:2607.02057 prompt-coverage-adequacy); README model-flat claim reframed from a per-release point-curve to structural invariants (operation flattens across tiers; depth tier-order fixed within a generation). New in 1.4.47: onboarding step ① surfaces the Mode D companion-store session-start load in the auto-read salience anchor (previously only in the local binding + rules, so a greeting could skip the load). New in 1.4.46: context-doctor gains a command-output axis — routes to a command-output proxy/hook (rtk) to trim verbose CLI stdout, complementing .claudeignore; risk-gated to token-scarce environments (lossy filtering, off gate-input paths). New in 1.4.41: context-doctor 2026 trigger vocab (context engineering/rot/collapse) + phantom-citation hardening; hub measurement-integrity-checklist (cross-model measurement pre-flight: display-name pin/reps≥3/discriminating probe). New in 1.4.40: install-wizard scaffolds the companion store as a queryable wiki (INDEX + session-start read + Raw/Wiki/Conversation ingest axis). New in 1.4.39: auto-decorrelation (cross-family verifier sidecar recruitment, calibration-gated) + video-ingest (capability-routed video ingestion). New in 1.4.37: corpus-grounding-expander + persona-roster-expander (field-harvested verbatim-relay capability skills). New in 1.3.0: public-surface-audit (git-tracked private-token leak scan), field-harvest Mode B session-end auto-trigger, 4-axis gate scope extension (docs/ + AGENTS.md). New in 1.2.0: pipeline-conductor (4-pipeline gated sweep), return-path-gate (chain closure audit), goal-quench (Stop hook + quality gate), steel-quench Wave 5 (multi-model sidecar challenger), 2-layer architecture docs, YAML validation script. Validated cross-CLI: Claude Code, Codex, Gemini.",
+  "author": {
+    "name": "chrono-meta",
+    "email": "chrono-meta@users.noreply.github.com"
+  },
+  "keywords": [
+    "hub-meta",
+    "fact-check",
+    "self-verification",
+    "bidirectional-validation",
+    "cross-ecosystem-synergy",
+    "plugin-recommender",
+    "pr-review",
+    "harness-engineering",
+    "ai-collaboration",
+    "token-efficiency",
+    "context-doctor",
+    "harness-doctor",
+    "install-doctor",
+    "install-conflict-detection",
+    "install-wizard",
+    "onboarding-automation",
+    "marketplace-gate",
+    "marketplace-readiness",
+    "meta-prompt-builder",
+    "prompt-delegation",
+    "circular-validation",
+    "2d-adversary"
+  ]
+}

package/scripts/count_check.sh

@@ -0,0 +1,95 @@
+#!/usr/bin/env bash
+# count_check.sh — skill/agent count-consistency check (single source).
+# Class: mandatory-pass (harness_6axis_framework.md §Axis 5) — exit 1 on drift.
+#
+# Called by ALL THREE count-consistency boundaries so one logic runs everywhere:
+#   - scripts/selfcheck.sh            → publish-readiness (prepublishOnly + npm test)
+#   - templates/.git-hooks/pre-commit → local commit time, `--staged` (index mode)
+#   - .github/workflows/validate.yml  → PR/merge boundary (checked-out tree == committed)
+#
+# Origin (fh_signal_2026-06-21): the count check used to live ONLY at the publish boundary.
+# But the actor that breaks it — a commit/merge that adds/removes a skill dir — acts at
+# commit/merge time, so a skill-adding PR (#111) merged with stale counts and they sat
+# undetected on main until the next publish. This is the gate-locality gap (a gate must
+# live where the breaking action happens). One source, three boundaries, no reinvention.
+#
+# Modes:
+#   (default)  count the WORKING TREE — selfcheck (publish; tree == HEAD) and CI
+#              (a checked-out PR IS the committed state). cat/glob the on-disk files.
+#   --staged   count the INDEX (exactly what THIS commit will contain) — the pre-commit
+#              hook. Fixes steel-quench S1 (2026-06-21): a worktree-only count can
+#              FALSE-PASS a commit that stages a skill add but leaves the count-file
+#              updates unstaged — the gate would verify a different tree than it commits.
+set -u
+cd "$(dirname "${BASH_SOURCE[0]}")/.." || { echo "COUNT-CHECK: FAIL (cannot cd to repo root)"; exit 1; }
+
+MODE="worktree"
+[ "${1:-}" = "--staged" ] && MODE="staged"
+fail=0
+
+# Read a tracked file's content from the active tree (index in --staged, disk otherwise).
+read_tree() { # read_tree <path>
+  if [ "$MODE" = staged ]; then git show ":$1" 2>/dev/null; else cat "$1" 2>/dev/null; fi
+}
+# List a plugin's top-level SKILL.md paths in the active tree.
+list_skills() { # list_skills <plugin>
+  if [ "$MODE" = staged ]; then
+    git ls-files --cached -- "plugins/$1/skills" 2>/dev/null \
+      | grep -E "^plugins/$1/skills/[^/]+/SKILL\.md$"
+  else
+    local s
+    for s in plugins/"$1"/skills/*/SKILL.md; do [ -f "$s" ] && echo "$s"; done
+  fi
+}
+# Count a plugin's top-level agent .md files in the active tree.
+count_agents() { # count_agents <plugin>
+  if [ "$MODE" = staged ]; then
+    git ls-files --cached -- "plugins/$1/agents" 2>/dev/null \
+      | grep -cE "^plugins/$1/agents/[^/]+\.md$"
+  else
+    ls plugins/"$1"/agents/*.md 2>/dev/null | wc -l | tr -d ' '
+  fi
+}
+# Active skill = SKILL.md whose head (first 20 lines) carries no deprecation marker
+# (a whole-file grep false-positives on skills that merely mention the word).
+count_active() { # count_active <plugin>
+  local n=0 s
+  while IFS= read -r s; do
+    [ -z "$s" ] && continue
+    read_tree "$s" | head -20 | grep -qE 'deprecated: true|DEPRECATED' || n=$((n+1))
+  done < <(list_skills "$1")
+  echo "$n"
+}
+
+meta_sk=$(count_active fh-meta); meta_ag=$(count_agents fh-meta)
+com_sk=$(count_active fh-commons); com_ag=$(count_agents fh-commons)
+total_sk=$((meta_sk + com_sk)); total_ag=$((meta_ag + com_ag))
+
+# Impossible-zero guard (steel-quench A4 — fail CLOSED): fh-meta always has active skills.
+# A 0 means the tree/glob resolved to nothing (wrong cwd, empty index, sh-as-bash shim) —
+# a gate must never return "consistent" from an empty tree.
+if [ "$meta_sk" -eq 0 ]; then
+  echo "COUNT-CHECK: FAIL (0 active fh-meta skills — empty/wrong tree, mode=$MODE)"
+  exit 1
+fi
+
+count_check() { # count_check <label> <file> <expected-string>
+  if read_tree "$2" | grep -q "$3"; then
+    echo "PASS  count: $1"
+  else
+    echo "FAIL  count: $1 — expected \"$3\" in $2 (actual: fh-meta ${meta_sk}sk/${meta_ag}ag, fh-commons ${com_sk}sk/${com_ag}ag)"
+    fail=1
+  fi
+}
+count_check "fh-meta plugin.json"      plugins/fh-meta/.claude-plugin/plugin.json    "${meta_sk} skills + ${meta_ag} agents"
+count_check "fh-commons plugin.json"   plugins/fh-commons/.claude-plugin/plugin.json "${com_sk} skills"
+count_check "marketplace.json fh-meta" .claude-plugin/marketplace.json               "${meta_sk} skills + ${meta_ag} agents"
+count_check "README header"            README.md                                     "${total_sk} skills · ${total_ag} agents"
+count_check "local_fh_context fh-meta" templates/local_fh_context.md                 "(fh-meta, ${meta_sk})"
+
+if [ "$fail" -ne 0 ]; then
+  echo "COUNT-CHECK: FAIL"
+  exit 1
+fi
+echo "COUNT-CHECK: PASS (mode=$MODE)"
+exit 0

package/scripts/selfcheck.sh

@@ -25,6 +25,11 @@ for f in bin/*.js; do
   check "node --check $f" node --check "$f"
 done
 
+# Codex adapter drift: the thin Codex runtime must keep reading canonical FH
+# skill/agent surfaces without silently accepting Claude-native primitives as
+# Codex-native.
+check "fh-codex-doctor --strict" bash -c 'node bin/fh-codex-doctor.js --strict >/dev/null'
+
 # Bash surface: npm-shipped scripts + local bin wrappers + gate-chain infra
 for f in scripts/*.sh bin/fh-gate bin/fh-run bin/fh-goal \
          templates/regression_guard.sh templates/temper_check.sh templates/predelete_check.sh templates/.git-hooks/pre-commit; do
@@ -43,26 +48,28 @@ if ! bash scripts/count_check.sh; then
   fail=1
 fi
 
-# Referenced-path existence: backtick-quoted repo-relative file refs in the always-loaded
-# governance surface (CLAUDE.md + .claude/rules/*.md) must exist. Phantom-reference class
-# recurred N>=3 in the 2026-06-11 audit window (operations.md _scanner.sh, claude-chrono path,
-# stale templates ref) — instrument-not-habit. Globs/placeholders/{vars} are excluded by the
-# filter; tracks/ is machine-local and deliberately out of scope. Gitignored refs (e.g.
-# `.claude/settings.json` named in prose *about* gitignored files) are skipped — they exist
-# locally but not on a fresh clone, and "must exist" here means "must ship".
-while IFS= read -r p; do
-  if git check-ignore -q "$p" 2>/dev/null; then
-    echo "SKIP  ref-path (gitignored): $p"
-  elif [ -f "$p" ]; then
-    echo "PASS  ref-path: $p"
-  else
-    echo "FAIL  ref-path: $p — referenced in CLAUDE.md/.claude/rules but missing"
-    fail=1
-  fi
-done < <(grep -hoE '\`[^\` ]+\`' CLAUDE.md .claude/rules/*.md 2>/dev/null \
-  | sed 's/\`//g' \
-  | grep -E '^(knowledge|templates|scripts|docs|plugins|\.claude)/[^*{}<>$]+\.(md|sh|ya?ml|jsonc|json)$' \
-  | sort -u)
+# Referenced-path existence is a source-tree check. The npm package intentionally
+# ships a narrower runtime surface, so package-mode selfcheck skips this section.
+if [ -d ".claude/rules" ]; then
+  # Backtick-quoted repo-relative file refs in the always-loaded governance surface
+  # (CLAUDE.md + .claude/rules/*.md) must exist. Phantom-reference class recurred
+  # N>=3 in the 2026-06-11 audit window — instrument-not-habit.
+  while IFS= read -r p; do
+    if git check-ignore -q "$p" 2>/dev/null; then
+      echo "SKIP  ref-path (gitignored): $p"
+    elif [ -f "$p" ]; then
+      echo "PASS  ref-path: $p"
+    else
+      echo "FAIL  ref-path: $p — referenced in CLAUDE.md/.claude/rules but missing"
+      fail=1
+    fi
+  done < <(grep -hoE '\`[^\` ]+\`' CLAUDE.md .claude/rules/*.md 2>/dev/null \
+    | sed 's/\`//g' \
+    | grep -E '^(knowledge|templates|scripts|docs|plugins|\.claude)/[^*{}<>$]+\.(md|sh|ya?ml|jsonc|json)$' \
+    | sort -u)
+else
+  echo "SKIP  ref-path (package mode: .claude/rules absent)"
+fi
 
 if [ "$fail" -ne 0 ]; then
   echo "SELFCHECK: FAIL"

package/templates/CLAUDE.md

@@ -0,0 +1,87 @@
+# CLAUDE.md
+
+## Session Start
+
+When a user starts a session with greetings like "hello", "let's start", "resume", "continuing from where we left off", or says "read root memory", **both layers must activate**:
+
+### Layer A — Auto read (4 steps required)
+
+1. **Read CATALOG.md** — `~/projects/forge-harness/CATALOG.md` (recent work context + latest meta cwd work cross-link)
+2. **Read latest session file** — `~/projects/forge-harness/tracks/{project}/` most recent mtime item (last work on domain + next round reverse-injection intent persistence location / use `ls -lat` or `find -mtime`)
+3. **Check MEMORY.md next-session trigger** — if project memory `MEMORY.md` auto-load is truncated, explicitly Read to supplement the next-session trigger section
+4. **Check todo/plan files if present** — `*todo*`/`*plan*` pattern (supplementary materials)
+5. **Search for duplicate installs in same root** — `ls ../ | grep -iE '(harness|forge)'` to catch sibling assets in parent directory. If found, report to user + delegate branching decision (use existing install / proceed with new / archive then proceed)
+
+### Layer B — Proactive initiative (active onboarding 5-skill cascade)
+
+After Layer A completes, **when the user enters a task**, activate AI proactive initiative mode:
+
+1. **Auto-initiative (1-line question)** — *"What task/project would you like to start? (e.g., 'Spring Boot API development', 'React component refactoring', 'continue existing [X] track')"* (if active track exists: *"Would you like to continue active track [X], or enter a new task?"*)
+2. **5-skill cascade** — `plugin-recommender` (internal GHE → external → built-in candidates) → `cross-ecosystem-synergy-detection` (synergy grade table) → `.claudeignore` standard initiative (`cp templates/.claudeignore`) → model switching guidance (default `/model sonnet` — FH dispatches floored skills/agents at higher tiers itself; pin a stronger model for harness-editing sessions, or when the Field Depth-Escalation Notice below fires — see README §Model setup) → `verify-bidirectional`·`harvest-loop` natural emergence waiting
+3. **User consent → actual setup** — plugin install / skill pre-activation / `.claudeignore` application / model switch
+4. **Project cwd handover guidance** — *"Setup complete. Move to the project cwd and call `claude` to start working."*
+
+**Simplification guard**: When an explicit task utterance is made (e.g., "debug X code"), enter task immediately (skip onboarding). Activates once per session.
+
+### Field Depth-Escalation Notice (advisory — once per session)
+
+The Sonnet default covers routine field work because FH dispatches floored skills/agents at higher
+tiers itself. But when **main-thread development visibly strains the session tier**, surface a
+one-line escalation proposal — do not leave it to recall:
+
+**Triggers** (any one): the same problem survives 2–3 correction loops · the work enters
+architecture/design reasoning that cannot be decomposed into a dispatchable unit · the user
+signals being stuck ("keeps failing", "why is this still wrong").
+
+**Two-step ladder** (propose the cheaper rung first):
+1. **Opus dispatch (sidecar)** — if the heavy reasoning packages into a unit (a design review, a
+   root-cause hunt, an adversarial pass), propose dispatching it to an Opus agent: the session
+   stays on Sonnet, cost stays local to the unit.
+2. **Session pin** — if the work is inherently main-thread (iterative dialogue design, repeated
+   whole-context reasoning), propose: *"This work demands session-level design depth — pinning
+   `/model opus` is recommended. Proceeding as-is also works: dispatches still cover floored units."*
+3. **No higher tier available** — common in metered API routing (a Bedrock-style Sonnet-only
+   deployment) or alternative runtimes (Hermes / OpenCode-class) that don't offer higher Claude
+   tiers: skip the proposal, proceed at the available tier, and **flag depth-sensitive
+   deliverables with an explicit below-floor limitation note** (F2 semantics — tier-floor
+   resolution, `multi_model_sidecar_strategy.md §Tier-floor`). Silent proceeding is the failure
+   mode this rung exists to prevent; the note makes the deliverable a re-review candidate when a
+   floor tier becomes reachable.
+
+**Guards** (mirrors the hub's Mode D Model Notice): once per session · advisory only — **never
+switch the session model autonomously** (human override is inviolable) · sessions where nothing
+strains never see it — the Sonnet default stays friction-free.
+
+**Basis**: Meta-harness mission *"easy and convenient + no setup burden + token savings"* direct implementation mechanism. Natural hub/action-leader division (single trigger in meta-harness cwd → handover to action-leader cwd).
+
+**3 usage modes — "don't block those who come, don't stop those who leave"** (meta-harness operating philosophy):
+- **Mode A (standard)**: meta-harness cwd setup → handover to separate project cwd (4 steps above)
+- **Mode B (resident)**: create **separate project directory** within the forge-harness install environment and work there. Keep the forge-harness directory itself as reference only — use `.gitignore` to block forge-harness assets from mixing into the project
+- **Mode C (plugin/skill only)**: install only plugins/skills without going through forge-harness (available via marketplace without cloning). Skill output accumulates as history within the user's own project. No automatic signals from the forge-harness side expected — indirect contribution depends on user's active communication (issues · PR · channels)
+
+If the user explicitly states a mode, immediately guide that mode. Do not force standard mode. Do not accumulate personal work artifacts in the forge-harness directory itself (protect reference asset identity).
+
+## Asset Synergy Branching Decision (meta vs. action-leader)
+
+When persisting new assets (memory · feedback · patterns · rules) during a session, asset location determination is required:
+
+| Location | Nature | Examples |
+|---|---|---|
+| **Meta-harness side seed** | Useful as-is when installed in other projects (cross-project synergy) | User baseline propositions, environment common conventions, common action rules for all personas, session operation patterns |
+| **Action-leader project side persistence** | Meaningful only in this project's domain/session context | Domain knowledge, session records, domain-specific validation loop outputs, per-project identity |
+
+When the judgment is ambiguous, the AI **states synergy potential first** then delegates the location decision to the user.
+
+## Knowledge Hub (forge-harness)
+
+Persistent knowledge for this project is stored at `~/projects/forge-harness/`.
+
+- **Past work search**: First read `~/projects/forge-harness/CATALOG.md`, identify related files by tags
+- **Learnings/feedback originals**: `~/projects/forge-harness/tracks/{project_name}/`
+- **At session end**: follow the Sync Protocol in `~/projects/forge-harness/CLAUDE.md` to sync
+- **When new patterns are found**: follow the Push Protocol in `~/projects/forge-harness/CLAUDE.md` to feed back
+
+<!-- [CUSTOMIZE] Replace {project_name} with the actual project name -->
+<!-- [CUSTOMIZE] If there is a domain knowledge path, add:
+- **Domain knowledge**: `~/projects/forge-harness/knowledge/domain/{domain}/`
+-->

package/templates/local_fh_context.md

@@ -0,0 +1,18 @@
+---
+scope: local-only
+description: forge-harness path and skill list pointer — local only, do not commit to shared repo
+---
+
+# forge-harness Cross-Context
+
+> Install: `cp {FH_ROOT}/templates/local_fh_context.md .claude/rules/local_fh_context.md`
+> Local only: `echo ".claude/rules/local_fh_context.md" >> .git/info/exclude`
+
+**forge-harness path**: `~/path/to/forge-harness` (replace with your actual install path)
+**Session records**: `{FH_ROOT}/tracks/_meta/`
+
+**Available skills (fh-meta, 33)**: agent-composer · apex-review · asset-placement-gate · auto-decorrelation · context-doctor · contention-layer · corpus-grounding-expander · cross-ecosystem-synergy-detection · deep-clarify · edit-manifest · field-harvest · frontier-digest · goal-quench · harness-doctor · harvest-loop · hub-cc-pr-reviewer · install-doctor · install-wizard · marketplace-gate · memory-hygiene · meta-prompt-builder · persona-roster-expander · phantom-quench · pipeline-conductor · plugin-recommender · prompt-regression · public-surface-audit · return-path-gate · sim-conductor · salience-splitter · steel-quench · verify-bidirectional · video-ingest
+
+**Available skills (fh-commons)**: convergence-loop · deliberation · mcp-circuit-breaker · token-budget-gate
+
+Skill details available on demand at `{FH_ROOT}/plugins/{plugin}/skills/{skill-name}/SKILL.md`.