@chrono-meta/fh-gate 1.4.10 → 1.4.12

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

package/package.json

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

package/plugins/fh-meta/skills/install-wizard/SKILL.md

@@ -97,11 +97,18 @@ Recommended layout:
   private: {org}/{hub}-be     (paper drafts, experiment logs,
                                raw signals, handoff files)
 
-Quick setup:
+Quick setup (remote-backed):
   gh repo create {org}/{hub}-be --private
   git clone https://github.com/{org}/{hub}-be ~/path/to/{hub}-be
   mkdir -p {hub}-be/{paper-drafts,paper-signals,digests,handoff}
 
+Local-only variant (no GitHub — your data never leaves the machine):
+  git init ~/path/to/{hub}-be      # no remote needed
+  mkdir -p ~/path/to/{hub}-be/{paper-drafts,paper-signals,digests,handoff}
+  → the sync script detects the missing upstream and skips push
+    automatically; local git history carries durability. Any store
+    name works — set BE_DIR (and HUB_DIR) env vars to your paths.
+
 Key rule: knowledge/shared/ drafts stay local via .gitignore glob.
 Push snapshots to the companion store explicitly — never auto-push.
 handoff/ files bridge cloud session → local without exposing content.
@@ -536,6 +543,7 @@ install-wizard — Complete
 
 🔬 Developing FH itself? Set up a private companion store:
    gh repo create {org}/{hub}-be --private   # paper drafts, experiment logs, handoffs
+   (or local-only: git init ~/path/{hub}-be — no remote; push is auto-skipped)
    → public mirror holds methodology · private store holds research artifacts
    → field projects (internal harness) can use the same dual-repo pattern