@chrono-meta/fh-gate 1.4.11 → 1.4.13

package/CLAUDE.md

@@ -103,6 +103,8 @@ Simplification guard: trivial denials with one obvious fix → state block + sin
 
 **4-step summary**: ① Auto-read CLAUDE.md + CATALOG + session card + registry scan → ② One-line proposal (new user / exploratory / returning branches) → ③ 5-skill cascade (plugin-recommender → synergy → .claudeignore → model → verify) → ④ Approval + setup
 
+**Returning-user door skeleton (summary-level — applies even if the detail file read is skipped; returning users only, new/exploratory branches stay in the detail file)**: open with the fixed 3-door menu — *"① Connect/map a project · ② Work on a mapped project — {field candidates} · ③ FH self-development — {FH worklist}"* — composing session-card candidates **into doors ②/③**, never as a raw priority dump that replaces the menu. An urgent open item (time-windowed handoff · blocking external deadline) outranks the menu; an explicit task utterance skips it entirely (see Guards below); cadence reminders (§Cadence Rules) ride below it, they don't displace it. Canonical source: `fh_detail_protocols.md` Step 2 §Returning user — keep door labels in sync.
+
 **Identity marker**: every greeting response (Step ②) opens with 🐿️ on its own line. FH's session-start signal — see `fh_detail_protocols.md` Step 2 for full greeting templates.
 
 **Guards**: explicit task-entry utterance → skip onboarding · once per session · code/debug requests → start working directly · project routing is a suggestion, mention at most once
@@ -153,6 +155,31 @@ FH asset modified → Axis 1 (regression_guard.sh --pr {BRANCH})
 
 **Unavailable axis**: If steel-quench or phantom-quench are not installed, note `Axis N: skipped (skill unavailable)` and proceed. Axis 1 PASS alone is sufficient to unblock a PR when Axes 2–3 are unavailable. Axis 4 (edit-manifest): if the skill is not installed, substitute a manual one-line prediction appended to `tracks/_meta/edit_manifest.yaml` — the record is what matters, not the skill.
 
+**Target-tier sim gate (Mode D supplement — all change classes: fix, improvement, new asset)**: the
+discriminator is not the change class but the **enforcement column**: does the asset's effect depend on
+a session *following prose instructions* (salience-dependent — rules, onboarding scaffolds, SKILL.md
+trigger behavior), or is it mechanically enforced (hooks, scripts — tier-independent, normal 4-axis
+path, exempt)? For salience-dependent changes, verify with a **blind simulation in an isolated Agent**
+(no main-session reasoning inherited — isolation is the FH mechanism that keeps the sim honest) with
+`model:` pinned to the tier the change must survive on. Application strength scales with context:
+- **Mode D (FH self-dev) — near-mandatory**: any salience-dependent FH asset change runs the sim
+  before Done. Mandatory without exception when the change fixes a behavioral miss *observed* on a
+  specific tier — sim at that same tier (the verification tier must match the failure tier; fixing on
+  a stronger model and verifying by review alone leaves "does it fire on the weaker tier?" unanswered).
+- **Field harness assets (templates/ propagated via Full-Harness Mode) — conditional**: sim at the
+  default field tier (Sonnet) when the behavior is load-bearing (gates, onboarding, destructive/publish
+  paths); skip with a one-line note for low-stakes prose.
+- **Light mapping (tracks/ registration, CATALOG entries) — exempt**, alongside mechanical changes
+  (hook logic, scripts, file moves — tier-independent by construction).
+
+**Autonomy floor**: the skip/run *judgment* on conditional cases is itself depth-sensitive — trust it
+only at opus-tier or above. A below-floor orchestrator does not silently skip: it runs the sim or asks
+the operator (one line), mirroring §Floor governance.
+
+If `model:`-pinned dispatch is unavailable (plan/billing gate), fall back to a cross-session headless
+run (`claude -p "<trigger>" --model <tier>` in the target cwd) — stronger isolation, zero instruction
+contamination. Record sim results in the Axes 2–3 marker + sub-agent invocation log.
+
 **Axis ownership** (each skill is already complete — orchestrator only coordinates):
 
 | Axis | Skill | What it catches |

package/package.json

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