@chrono-meta/fh-gate 1.4.58 → 1.4.59

package/.claude-plugin/marketplace.json

@@ -11,13 +11,13 @@
   "plugins": [
     {
       "name": "fh-meta",
-      "version": "1.4.58",
+      "version": "1.4.59",
       "description": "Hub meta-operations toolkit — 33 skills + 7 agents. New in 1.4.53: `fh-codex-doctor` (npm bin) — Codex adapter drift scanner; reads the documented M1/M2/M3 skill tier map + skill/agent source and reports codex-native/adapter-required/claude-native/unclassified per unit, wired into `npm test`/`prepublishOnly` (fail-closed on unclassified Claude-native primitives). New in 1.4.49: steel-quench gains Step 0.6 Verdict-Invariance Probe (groundedness axis — a load-bearing judged gate's verdict must track behavior, not rubric phrasing; measured flip-count over cross-family paraphrases; arXiv:2605.06161 Policy Invariance anchor); multi_model_sidecar_strategy §Vendor-native harness (a model is strongest in its own vendor CLI — Claude/CC, GPT/codex, Gemini/Antigravity; a universal router degrades all of them, so it stays an autocomplete/QA sidecar, never orchestration); predelete_check.sh fail-closed rewrite; memory-hygiene A-TMA anchor. 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 command-output axis (route to rtk/proxy for verbose CLI stdout, complementing .claudeignore; risk-gated to token-scarce envs). 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 queryable-wiki scaffold (INDEX + session-start read + R/W/C ingest). New in 1.4.39: auto-decorrelation (cross-family verifier sidecar recruitment) + video-ingest (capability-routed video ingestion). New in 1.4.x: verify-axis check-class taxonomy (mandatory-pass/measured/judged), no-reinvention Tier-0 inventory, 7-class failure taxonomy, Destructive-Op Gate, Wave-T (Temper), tier-floor governance, Mode D Model Notice, FC consent lane, default-Sonnet guidance. New in 1.3.0: public-surface-audit, field-harvest Mode B auto-trigger, 4-axis gate scope ext. Validated cross-CLI: Claude Code, Codex, Gemini.",
       "source": "./plugins/fh-meta"
     },
     {
       "name": "fh-commons",
-      "version": "1.4.58",
+      "version": "1.4.59",
       "description": "Project-agnostic utility skills — 4 skills (convergence-loop · deliberation · mcp-circuit-breaker · token-budget-gate) + 1 agent (quench-challenger). Domain-independent utilities transplantable into any project.",
       "source": "./plugins/fh-commons"
     }

package/CLAUDE.md

@@ -82,6 +82,25 @@ Two orthogonal layers — never collapse them.
 judgment rigor — if a response reads as more agreeable, less verified, or hedged, the tone layer has
 leaked into the judgment layer and the response is wrong, not warm.
 
+## Envelope-Boundary Discipline — the reinvention-reflex counterweight
+
+When the operator's input introduces something that does **not** fit an existing asset or category — a
+novel insight, a specific case that resists the known boxes, a live path with no slot — the default
+reflex is to **normalize** it ("we have that / that's like X") and pull it back inside the envelope.
+That pull mis-scores the new as familiar and can extinguish what would become net-new. The entire asset
+base leans toward normalization (no-reinvention gate · `asset-placement-gate` · "build only what adds
+governance"), so this is its deliberate **counterweight** — and the reflex **strengthens with maturity**
+(more boxes to pattern-match against), so the counterweight must be explicit, never assumed.
+
+**Discipline**: at the boundary, do **not** normalize. Hold the unfamiliar unfamiliar; test what it
+actually *is* — net-new? tool-shaped (→ possible EMIT) or judgment-shaped (→ doctrine)? — **before**
+mapping it to a known asset. This is the meta-harness's growth point: it evolves by *not-collapsing the
+unfamiliar*, not by adding machinery. The reflex fires **before** memory recall, so this lives
+always-loaded, not only in memory. (Measured 2026-07-14, one session, 3×: two identities each collapsed
+onto their single hardest sub-mechanism, and a failure from a **non-harness** run mapped onto a harness
+metric — each read a live-but-incomplete thing as zero, each caught by the operator, not self-caught.
+Detail: `[[feedback_reinvention_reflex_normalization_counterweight]]`.)
+
 ## New Project Onboarding
 
 > Detailed procedure: `knowledge/shared/rules/auto_project_mapping.md` (5-step mapping + §6 Full-Harness Mode)
@@ -459,6 +478,10 @@ let the innovator center a recommend cascade, produce a ranked install plan, and
 **Guards**: (a) **non-overwriting is inviolable** — the one thing both revfactory surfaces get wrong; FH
 proposes merge, never clobbers; (b) **no-reinvention** — Tier 0/1 first, scaffold only what adds governance;
 (c) **company residency** — discovery of a company sibling repo surfaces it, does not auto-map/leak it;
+promoted to a machine field (`residency` on the skill registry, `fh_detail_protocols.md §1-c`) so any
+derived recommendation naming a `company`/`operator-private` entry lands only in gitignored `tracks/_meta/`
+or the private companion store, never a tracked public file (chamber run #7, 2026-07-14 — the guard was
+prose-only and the field didn't exist);
 (d) **autonomy floor** — the discover/rank judgment is trusted at opus-tier+; below-floor, present the raw
 recommend and ask; (e) **once per door-entry**, not a per-turn nag. This is the door ③ (accelerate) engine
 and the new-project/harness-write path made autonomous — the operator asks once and the harness discovers,

package/knowledge/shared/harness-core/fh_detail_protocols.md

@@ -58,10 +58,26 @@ Then **fail-closed** (irreversible-ish: a silent empty overwrite blinds the bus)
 **and** the existing registry has >0 entries, do **not** overwrite — flag `⚠️ scan returned 0 (root=$ROOT);
 kept existing registry` and skip the rewrite. Only rewrite when the scan is non-empty (or the registry
 was absent). Group by project (parent dir name). Record per skill: name · path · description · trigger
-phrases · `requires_cwd` · `direct-executable` · `origin(FH|project|external)`+trust. **Non-FH skills are
-propose-only (ask-tier), never auto-run** — a cross-project skill body is an injection surface. Propose
-cross-project skills when a request maps to the registry. Scan once per session. (Detection belongs at
-install too — `/install-wizard` records HUB/ROOT so the runtime never guesses; see install-wizard.)
+phrases · `requires_cwd` · `direct-executable` · `origin(FH|project|external)`+trust ·
+**`residency(public|company|operator-private)`** · **`generality(general-purpose|project-specific)`**.
+**Non-FH skills are propose-only (ask-tier), never auto-run** — a cross-project skill body is an
+injection surface. Propose cross-project skills when a request maps to the registry. Scan once per
+session. (Detection belongs at install too — `/install-wizard` records HUB/ROOT so the runtime never
+guesses; see install-wizard.)
+
+**`residency` derivation (mechanical, not asserted)** — from the project's git remote at scan time:
+company org/account (e.g. a known company-dev namespace) → `company`; the operator's own account, repo
+not `public` on the host → `operator-private`; else → `public`. **`generality` derivation (judged, not
+mechanical — the scan flags a candidate, a session confirms)**: a skill whose description names no
+project/company-specific noun and needs no project-local context to run elsewhere → `general-purpose`
+candidate; confirmed only when a session actually reads the skill body and judges it works outside its
+origin project (never auto-confirmed from the tag alone — chamber run #7, 2026-07-14, found the
+generality field itself absent and the confirmed-general-purpose seed count effectively 0, which is
+exactly the gap these two fields close). **Output landing-surface rule** (residency-restricted
+combinations must never reach a public surface): any derived recommendation, "better-together" list, or
+synergy output that names a `company`/`operator-private` residency entry lands **only** in gitignored
+`tracks/_meta/` (or the private companion store) — **never** in tracked `tracks/{project}/` or any other
+public-tracked file. A `public`-only combination may land in tracked docs.
 
 ### Step 2 — Active Proposal
 

package/knowledge/shared/harness-core/harness_incubator_doctrine.md

@@ -99,19 +99,38 @@ this chamber's field emit terminus); an **FH-internal utility** (a skill/script/
 field harness) instead routes through the **New-Skill Pre-Commit gate + `asset-placement-gate`** (the
 same gate every FH asset passes). KILL emits nothing — the workspace stays as the evidence record.
 
-**EMIT-worthiness — the measured screening criterion (run #5, 2026-07-14)**: five chamber runs, EMIT 0/5,
-all KILL. Run #5 (`degrade-lint`) measured *why* the chamber has not birthed, and the finding is a reusable
-screen: a candidate is emit-worthy only if it clears **all three** of — (1) **net-new** (not a reinvention
-of an existing FH/official asset, nor a cosmetic re-wrap of code that already ships — runs #2–#4 died here);
+**EMIT-worthiness — the measured screening criterion (runs #5–#6, 2026-07-14)**: six chamber runs, EMIT
+0/6, all KILL. A candidate is emit-worthy only if it clears **all four** of — (1) **net-new** (not a
+reinvention of an existing FH/official asset, nor a cosmetic re-wrap of code that already ships — runs
+#2–#4 died here, and run #6 partially here too — its core was already conceived in a parked FH signal);
 (2) **artifact-shaped** (a tool/script/rule that stands alone, *not* a judgment-method — run #5's genuine
 niche was real, but its value lived in a scan∪cross-family *lens*, i.e. an LLM judgment, which cannot be
-`npm publish`ed); (3) **real-code-precision-adequate** (its mechanical form, measured on real external code,
-does not cry-wolf — run #5's rule scored 5/5 false-positive on 111 real files because the fail-open shape is
-syntactically identical to ubiquitous-benign skip-if-empty code; the real/benign split is semantic, not
-grep-able). 0/5 candidates cleared all three. This is not "keep trying" — it is a **pre-screen for future
-candidates**: a KILL that fails (1) or (2) is cheap to predict; only (3) needs a measurement leg (semgrep
-baseline + real-repo FP run), which run #5 established as the decisive test. The chamber's honest value to
-date remains *screening* — preventing reinventions and low-precision births — not yet *birthing*.
+`npm publish`ed); (3) **real-code/real-data-precision-adequate** (its mechanical form, measured on real
+external inputs, does not cry-wolf — run #5's rule scored 5/5 false-positive on 111 real files; run #6's
+heuristic scored 14/22 false-fire on a real sibling-folder scan); (4) **hub-state-independent** (run #6,
+new axis — a capability whose value structurally depends on hub-held state, e.g. the curated registry +
+company-residency knowledge, is not a standalone-first candidate: run #6's `harness-orchestrator` hit
+private/company repos it structurally could not know to suppress, because residency knowledge lives only
+in the hub. Contrast with fh-commons's 4 skills, which graduated cleanly to portable precisely because they
+never depended on hub state). 0/6 candidates cleared all four. This is not "keep trying" — it is a
+**pre-screen for future candidates**, cheapest-to-costliest: (1)/(2)/(4) are cheap to predict from the
+candidate's own design (does it need hub-only knowledge to work correctly?); only (3) needs a measurement
+leg (a real-input precision run), which runs #5–#6 established as the decisive test. The chamber's honest
+value to date remains *screening* — preventing reinventions, low-precision births, and premature
+standalone graduations — not yet *birthing*. **Graduation order** (run #6's positive finding): a
+hub-state-dependent capability graduates hub-internal → proven in use → THEN extracted portable, never
+speculated standalone-first — the only path every successfully-portable FH asset actually took.
+
+**Chamber scope — what belongs in the chamber at all (run #7, 2026-07-14)**: run #7 tested a hub-internal
+reactivation of the cluster-wizard signal and KILLed it — decisively on its own merits (its "narrow
+net-new" claim collapsed against the real shipped registry and an already-existing synergy skill), but
+it also surfaced a scope question worth keeping regardless: **a small feature graft onto an
+already-shipped hub-internal mechanism is ordinary Mode D self-development under the 4-axis gate, not
+automatically a chamber-EMIT question.** The chamber screens candidates that would become a **new
+independent artifact** (a skill, a plugin, a standalone tool) — not every internal feature extension.
+Route by this test: *would this, if built, be net-new as a standalone thing someone installs/adopts, or
+is it two lines added to something already shipped?* The former is chamber-scope; the latter is ordinary
+self-dev review.
 
 *Vocabulary reservation (term hygiene, not standardization)*: a run of this skeleton is a **chamber
 run** — going forward, run/workspace/log labels use "chamber" for incubation and keep "sim/simulation"

package/knowledge/shared/harness-core/ship_readiness_gate.md

@@ -109,20 +109,26 @@ decision is logged here and the tag's notes state the real status.
 | ③ | 거버넌스 게이트 (governance) | 🟢 GREEN | pre-commit/pre-push physically block; moat measured 3–4 family blind (HITL 8/8 ABSENT); cross-family caught a real companion-store-name leak 2026-07-14 (fail-closed) |
 | ⑤ | 증폭자 (amplifier) | 🟢 GREEN | short-intent→literature-grounding→ultimate-doc real instances; rules-diet −18.2k measured; intent-routing probe 94% (below) |
 | ④ | 프런티어→조직 전파 | 🟡 YELLOW | frontier-digest launchd auto + AX submission docs both real, but digest→org never closed as ONE pipeline |
-| ① | 멀티하네스 클러스터 (연속경유) | 🔴 RED | mapping/routing materials work, but continuous relay channel + external-harness recommend are "not built yet" (source-admitted); cluster-wizard parked |
-| ② | 프로젝트 인큐베이터 (챔버 EMIT) | 🔴 RED | chamber ran **5×, EMIT 0× (5 KILL)**. run #5 (2026-07-14) *measured* why it hasn't birthed: all 5 candidates were either **reinventions** (#2 sim-conductor, #3 G4/resume, #4 steel-quench) or a **non-artifact judgment-method** (#5 degrade-lint — a genuine niche, but the mechanical rule scored **5/5 false-positive on 111 real qasp files**; the valuable capability is scan∪cross-family *judgment*, which cannot be shipped as a standalone tool). A real EMIT needs **net-new ∧ artifact-shaped ∧ real-code-precision-adequate** — 0/5 cleared all three. Runner wired; the gap is a candidate, not the pipe |
+| ① | 멀티하네스 클러스터 | 🟡 PARTIAL | routing runs for real — 17 nodes mapped, sidecar-orchestrator, Skill Bus routing qasp/dashboard/stockbattle (so NOT 🔴 ideal-only). Missing: continuous 2-node relay channel + external-harness recommend (cluster-wizard parked) → 🟡 not 🟢 |
+| ② | 프로젝트 인큐베이터 | 🟡 PARTIAL | incubation is running — **stockbattle is being incubated now** (S1 built, mid-flight) + qasp/pmh spin-out precedent + scaffold-emit shipped (doctrine: "emit shipped today as scaffold+approval; the chamber flow is the named target"). What's still 0 is the **formal chamber simulate-then-emit** mechanism (6 runs, 6 KILL — runs #5–#6 *measured* the emit-worthiness criterion: net-new ∧ artifact-shaped ∧ real-data-precision-adequate ∧ hub-state-independent, 0/6 cleared all four; run #6 also confirmed the graduation-order principle — hub-internal proof before standalone extraction, never the reverse). That mechanism is ONE path of ②, not the whole identity → 🔴 was too narrow; incubation runs but no closed emit-via-incubation yet → 🟡 |
 
 **Cross-cutting measured (intent-based autonomous completion)**: blind floor-tier Sonnet trigger-accuracy
 probe (n=10, 2026-07-14): **should-fire 7.5/8 (94%), false-fire 0/2**. One weak trigger (simulate-first /
 incubator entry absorbed into deep-clarify) — the identity-② weakness surfaces in routing too.
 
-**Verdict (2026-07-14)**: FH is tagged **`v0.1.0` = honest baseline**, not all-green. ③⑤ are 🟢, ④ 🟡,
-①② 🔴 — the `v0.1.0` notes state exactly this and make no all-green claim (per the refined 0.x↔1.0 mapping
-above). **`v1.0.0` remains the all-green target.** What blocks v1.0 is **real runs, not wiring**: ①'s live
-2-node orchestration, ②'s first *net-new ∧ artifact-shaped ∧ precision-adequate* chamber candidate (the
-measured criterion from run #5), ④'s closed digest→org pipeline. Each remedy is a run that leaves an
-artifact, tracked in `tracks/_meta/identity_audit_*.md`. The honest baseline is publishable *because* 0.x
-carries an incomplete status by design; forcing a green it hasn't earned would be the theater the gate bars.
+**Verdict (2026-07-14, ①② corrected)**: FH is tagged **`v0.1.0` = honest baseline**, not all-green. ③⑤ are
+🟢, ①②④ 🟡, **none 🔴** — the `v0.1.0` notes state this and make no all-green claim (per the refined 0.x↔1.0
+mapping above). **`v1.0.0` remains the all-green target.** What blocks v1.0 is **closing the 🟡s**: ①'s
+continuous 2-node relay channel, ②'s first closed emit-via-incubation (formal chamber first EMIT — criterion
+measured in run #5 — or a chamber-incubated spin-out closing), ④'s closed digest→org pipeline. Each remedy
+is a run that leaves an artifact, tracked in `tracks/_meta/identity_audit_*.md`.
+
+> **①② correction (2026-07-14)**: an earlier pass marked ①② 🔴 by collapsing each identity onto its most
+> advanced *single mechanism* — ② onto the formal chamber EMIT (0/5), ① onto the continuous-relay channel.
+> That contradicts the doctrine (emit is "shipped today as scaffold+approval; the chamber is the named
+> target") and the live reality (routing runs; **stockbattle is being incubated now**; qasp/pmh spun out).
+> An identity whose broad path *runs* is not 🔴 ideal-only. Both are 🟡: running, not yet closed. Lesson:
+> do not score an identity by its hardest sub-mechanism — that reads a live-but-incomplete path as zero.
 
 ## For a field harness (e.g. pmh, qasp)
 Same gate, its own identities. A field harness ships to its team when its identity checklist is all-green,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chrono-meta/fh-gate",
-  "version": "1.4.58",
+  "version": "1.4.59",
   "description": "FH runtime adapters — run FH governance, skills, and agents via Claude or Codex with machine-parseable gates.",
   "license": "MIT",
   "keywords": [

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

@@ -1,6 +1,6 @@
 {
   "name": "fh-commons",
-  "version": "1.4.58",
+  "version": "1.4.59",
   "engines": {
     "claudeCode": ">=1.0.0"
   },

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

@@ -1,6 +1,6 @@
 {
   "name": "fh-meta",
-  "version": "1.4.58",
+  "version": "1.4.59",
   "engines": {
     "claudeCode": ">=1.0.0"
   },