@chrono-meta/fh-gate 2.6.0 → 2.8.0

package/scripts/test_wizard_snippet_merge_lanes.sh

@@ -282,6 +282,46 @@ SessionStart REGISTRATION of the script that reports on them. So the wizard's un
 message (GAP 1) is never contradicted by anything, and the check whose job is announcing an unwired \
 machine can itself be unwired silently."
 
+# ── SHIP-1/2: 출하되는 모든 스니펫이 머지 코드가 읽는 키를 갖고 있나 (2026-08-22 신설) ─────
+# 🟥 왜 이 레인이 뒤늦게 생겼나 — 이 파일은 «머지 코드가 옳게 동작하나» 만 재고 있었고,
+#    «출하물이 그 코드가 읽는 모양인가» 는 아무도 안 봤다. 그 사이
+#    templates/settings.PriorArt.snippet.json 이 project_settings_json 래퍼 **없이** 출하됐고,
+#    머지 코드는 그 키가 없으면 `SKIP (no project_settings_json)` 로 **조용히 건너뛴다**.
+#    결과: install-wizard 를 돌려도 그 훅은 **한 번도 등록된 적이 없었다.**
+#    실측 2026-08-22: 스니펫 5개 중 4개 래퍼 O · PriorArt 만 부재(전수, 컨트롤 = 나머지 넷).
+#    ⇒ 레인이 «구현» 만 보고 «출하물» 을 안 보면 이 클래스는 영원히 초록이다.
+echo
+echo "── SHIP: shipped-snippet schema conformance ──"
+_ship_total=0; _ship_bad=0
+for _snip in "$ROOT"/templates/settings.*.snippet.json; do
+  [ -f "$_snip" ] || continue
+  _ship_total=$((_ship_total+1))
+  if ! python3 -c "import json,sys; d=json.load(open(sys.argv[1])); sys.exit(0 if isinstance(d.get('project_settings_json'),dict) else 1)" "$_snip" 2>/dev/null; then
+    _ship_bad=$((_ship_bad+1))
+    _fail "SHIP-1 $(basename "$_snip") has no dict 'project_settings_json' — install-wizard will SKIP it silently"
+  fi
+done
+if [ "$_ship_total" -eq 0 ]; then
+  # 부재를 통과로 렌더하지 않는다 — 0 개를 스캔하고 PASS 하면 계기가 죽은 것이다
+  _fail "SHIP-1 scanned ZERO snippets — instrument dead, not a pass (glob or ROOT wrong)"
+elif [ "$_ship_bad" -eq 0 ]; then
+  _pass "SHIP-1 all $_ship_total shipped snippet(s) carry a dict 'project_settings_json'"
+fi
+
+# SHIP-2 컨트롤 — 이 검사가 실제로 판별하나. 래퍼를 뗀 픽스처는 반드시 걸려야 한다.
+_ctl=$(mktemp -t fh_ship_ctl.XXXXXX) || _ctl=""
+if [ -n "$_ctl" ]; then
+  printf '%s\n' '{"hooks":{"PreToolUse":[]}}' > "$_ctl"
+  if python3 -c "import json,sys; d=json.load(open(sys.argv[1])); sys.exit(0 if isinstance(d.get('project_settings_json'),dict) else 1)" "$_ctl" 2>/dev/null; then
+    _fail "SHIP-2 CONTROL — a wrapper-less fixture PASSED the check; the check does not discriminate"
+  else
+    _pass "SHIP-2 CONTROL — wrapper-less fixture is caught (check discriminates)"
+  fi
+  rm -f "$_ctl"
+else
+  _fail "SHIP-2 CONTROL could not run (mktemp failed) — reported as a gap, not a pass"
+fi
+
 echo
 echo "──────────────────────────────────────────────"
 if [ "$FAILED" -ne 0 ]; then

package/templates/.git-hooks/pre-commit

@@ -356,6 +356,7 @@ else
     fi
   else
     PSA_LEAK=0
+    PSA_DEAD=0
     # NUL-delimited (regression caught by the refactor's own cross-family review): the pre-refactor
     # loop read this list with `read -r -d ''`, and the rewrite dropped back to a line-oriented read.
     # `core.quotePath=false` stops git quoting NON-ASCII names, but a path holding a backslash or a
@@ -367,7 +368,11 @@ else
       added=$(git diff --cached -- "$f" 2>/dev/null | grep -E '^\+' | sed 's/^\+//' || true)
       [ -z "$added" ] && continue
       # Per-line pass, path-tagged so the LOW file allowlist applies.
-      if ! printf '%s\n' "$added" | sed "s|^|$f	|" | psa_scan_tagged; then PSA_LEAK=1; fi
+      # 🟥 rc 를 «비영» 으로 뭉개지 마라 (cross-family, 2026-08-21): 1=유출 · 3=계기 사망.
+      #    둘을 합치면 아래 PUBLIC_SURFACE_OK 가 **계기 사망까지 «승인된 유출»로 통과**시킨다.
+      _psa_rc=0
+      printf '%s\n' "$added" | sed "s|^|$f	|" | psa_scan_tagged || _psa_rc=$?
+      case "$_psa_rc" in 0) ;; 3) PSA_DEAD=1 ;; *) PSA_LEAK=1 ;; esac
       # Split-token backstop (pre-commit ONLY — this surface is a DIFF, so a literal can be wrapped
       # mid-word across two added lines and neither line matches). TIGHT-join, no separator, so
       # "fh-\nbe" becomes "fh-be". Accepted residual, verified not a missed fix: two whitespace-
@@ -375,15 +380,31 @@ else
       # PUBLIC_SURFACE_OK escape. A sentinel separator would close the fusion but RE-OPEN the split
       # catch, which is the more important case since real literals have no internal whitespace.
       joined=$(printf '%s' "$added" | tr -d '\n\r')
-      if ! printf '%s\t%s\n' "$f" "$joined" | psa_scan_tagged >/dev/null 2>&1; then
+      _psa_rc2=0
+      printf '%s\t%s\n' "$f" "$joined" | psa_scan_tagged >/dev/null 2>&1 || _psa_rc2=$?
+      [ "$_psa_rc2" = "3" ] && PSA_DEAD=1
+      if [ "$_psa_rc2" != "0" ] && [ "$_psa_rc2" != "3" ]; then
         # Only report if the per-line pass did not already flag this file, to avoid double-reporting.
         if ! printf '%s\n' "$added" | sed "s|^|$f	|" | psa_scan_tagged >/dev/null 2>&1; then :; else
+          # 🟥 **표시 전용 — 판정 경로가 아니다** (2026-08-21 배선 리뷰 R-1). 이 파이프는 비말단이라
+          #    `$?` 가 `sed` 것이다. 그래도 되는 이유는 도달 조건이 **이미 «유출 확정»** 이고 바로
+          #    다음 줄이 `PSA_LEAK=1` 을 무조건 세우기 때문이다. 판정은 위 `_psa_rc` 3분기가 쥔다.
+          #    ⚠️ 이 주석이 없으면 다음 사람이 판정 경로로 읽고 «고친다» — 그게 이 줄을 위험하게 만든다.
           printf '%s\t%s\n' "$f" "$joined" | psa_scan_tagged | sed 's/leak —/leak (line-split) —/'
           PSA_LEAK=1
         fi
       fi
     done < <(git -c core.quotePath=false diff --cached --name-only --no-renames --diff-filter=ACMR -z 2>/dev/null || true)
-    if [ "$PSA_LEAK" -eq 1 ]; then
+    # 🟥 계기 사망은 override 대상이 **아니다.** override 는 «알고 있는 언급»을 승인하는 것이지
+    #    «안 잰 표면»을 승인하는 게 아니다. 초판은 1 과 3 을 합쳐서, PUBLIC_SURFACE_OK=1 이면
+    #    스캐너가 죽은 상태도 통과했다 — 비가역 표면에서 가장 나쁜 조합이다.
+    if [ "${PSA_DEAD:-0}" -eq 1 ]; then
+      echo "  ⛔ INSTRUMENT DEAD — the public-surface scan did NOT run (rc=3). NOT SCANNED is not clean."
+      echo "     PUBLIC_SURFACE_OK does NOT cover this. Fix the scanner, then commit:"
+      echo "       · run under bash (zsh special vars can blank PATH inside the matcher)"
+      echo "       · confirm psa_load ran and PSA_STREAM is non-empty"
+      FAILED=1
+    elif [ "$PSA_LEAK" -eq 1 ]; then
       if [ "${PUBLIC_SURFACE_OK:-0}" = "1" ]; then
         echo "  ⚠️  public-surface hit(s) allowed by PUBLIC_SURFACE_OK=1 (conscious, reviewed intent)"
         echo "$(date +%Y-%m-%dT%H:%M:%S) PUBLIC_SURFACE_OK override — branch $BRANCH — review suppressed hit(s) above" \
@@ -575,6 +596,86 @@ marker_recreate_hint() {
 # VALUE is a closed enum; the three degrade values additionally require a non-vacuous reason
 # on the SAME line (keeping the established one-line marker convention rather than adding a
 # second field). Returns 0 = accepted, 1 = block.
+validate_defense_leg() { # $1 = marker path — fires ONLY at the floor tiers (see call site)
+  # Wave 1-D defense line. Absorbed from a sibling harness 2026-08-20, but the machine is OURS:
+  # 🟥 the source document claimed "the commit hook reads that line" and "pinned by
+  # test_marker_floor_lanes.sh" — measured twice with a control (`crossfamily` 21 hits), BOTH were
+  # 0 hits there. Porting the prose without building this function would have imported the phantom.
+  #
+  # WHY IT EXISTS: measured n=6 in the origin field — a floor-tier pass executes the attack angles
+  # without defect but does NOT spontaneously ask these three of its own numbers. That is a
+  # checklist gap, not a capability gap, and a harness whose behaviour depends on which model drives
+  # it is defective by sonnet_floor_doctrine.md rather than merely limited.
+  # FH-side corroboration (2026-08-20, this session, n=1): a comparison was published from two
+  # DIFFERENT package versions and read as a defect ("15 lanes vs 13 lanes — two vanished"). The
+  # 비교공정성 question — *were the two arms measured under the same conditions?* — asks exactly
+  # that, and the claim was retracted only because a later step happened to surface the version gap.
+  #
+  # SCOPE, and why it is not wider: `below-floor` occurs 0 times across the existing marker corpus,
+  # so gating on it alone would be a decoration that never fires. `sonnet-floor` occurs 11 times.
+  # Both are gated here; the wide reading ("any marker carrying numbers") is deliberately NOT taken —
+  # it would price this axis at a near-universal rate, which is the over-trigger §7 rejects.
+  #
+  # 🟥 WHAT WAS NOT IMPORTED: the origin also amends its floor rule so that below-floor + this line
+  # + a crossfamily record PASSES WITHOUT the operator ack. That is a LOOSENING of an existing FH
+  # gate and it is not adopted. Here this leg is purely additive: below-floor still requires
+  # below-floor-ack, unchanged.
+  local m="$1" line r f e
+  if [ ! -f "$m" ] || ! grep -qE '^[[:space:]]*axis2-defense:[[:space:]]*[^[:space:]]' "$m"; then
+    echo "  ❌ FAIL — floor-tier marker with no 'axis2-defense:' line."
+    echo "     At the floor tier the attack angles run but the three defense questions do not get"
+    echo "     asked spontaneously. Ask them OF YOUR OWN findings and numbers, then record:"
+    echo "       axis2-defense: reproducibility=<exact command or file:line another session runs>"
+    echo "                      fairness=<reps/inputs/env named for BOTH arms>"
+    echo "                      estimation-layer=<per number: measured | estimate | quotation;"
+    echo "                                        for measured, what showed the instrument works here>"
+    echo "     Append to: $m"
+    return 1
+  fi
+  if [ "$(grep -cE '^[[:space:]]*axis2-defense:' "$m")" -gt 1 ]; then
+    echo "  ❌ FAIL — marker carries MORE THAN ONE 'axis2-defense:' line."
+    grep -nE '^[[:space:]]*axis2-defense:' "$m" | sed 's/^/       /'
+    echo "     The reader takes the FIRST, so an appended correction is silently shadowed."
+    echo "     Leave exactly one line."
+    return 1
+  fi
+  # The whole value, including any continuation lines, up to the next top-level field.
+  line=$(sed -n '/^[[:space:]]*axis2-defense:/,/^[a-z0-9-]*:[[:space:]]/p' "$m"          | sed -E '2,$ { /^[a-z0-9-]+:[[:space:]]/d; }' | tr '\n' ' ')
+  r=$(printf '%s' "$line" | sed -nE 's/.*reproducibility=([^ ].*)/\1/p' | sed -E 's/(fairness=|estimation-layer=).*//')
+  f=$(printf '%s' "$line" | sed -nE 's/.*fairness=([^ ].*)/\1/p' | sed -E 's/(reproducibility=|estimation-layer=).*//')
+  e=$(printf '%s' "$line" | sed -nE 's/.*estimation-layer=([^ ].*)/\1/p' | sed -E 's/(reproducibility=|fairness=).*//')
+  local missing=""
+  [ -n "$r" ] || missing="$missing reproducibility"
+  [ -n "$f" ] || missing="$missing fairness"
+  [ -n "$e" ] || missing="$missing estimation-layer"
+  if [ -n "$missing" ]; then
+    echo "  ❌ FAIL — axis2-defense: missing sub-answer(s):$missing"
+    echo "     All three are required. A partially-filled form is not a defense — the question you"
+    echo "     skipped is the one you did not want to answer."
+    return 1
+  fi
+  # Non-vacuity. `ok` / `yes` / `n/a` / `done` are a FILLED FORM, not an answer — the same shape the
+  # crossfamily leg rejects. Anything under 12 chars cannot name a command, a reps count, or a layer.
+  local bad=""
+  for pair in "reproducibility:$r" "fairness:$f" "estimation-layer:$e"; do
+    local k="${pair%%:*}" v="${pair#*:}"
+    v=$(printf '%s' "$v" | sed -E 's/^[[:space:]]+//; s/[[:space:]]+$//')
+    case "$(printf '%s' "$v" | tr 'A-Z' 'a-z')" in
+      ok|yes|y|n/a|na|none|done|true|-|tbd|todo) bad="$bad $k(vacuous:'$v')" ;;
+      *) [ "${#v}" -ge 12 ] || bad="$bad $k(too short:'$v')" ;;
+    esac
+  done
+  if [ -n "$bad" ]; then
+    echo "  ❌ FAIL — axis2-defense: vacuous answer(s):$bad"
+    echo "     'ok'/'yes'/'n/a' is a filled form, not an answer. Name the command, the reps, the layer."
+    echo "     🟥 The hook checks PRESENCE and NON-VACUITY only. It cannot check whether the answers"
+    echo "     are TRUE — that stays with the operator and the weekly audit, exactly like every other"
+    echo "     marker field. Do not read a PASS here as a claim that these answers were verified."
+    return 1
+  fi
+  return 0
+}
+
 validate_crossfamily_leg() { # $1 = marker path
   local m="$1" line val reason fams
   if [ ! -f "$m" ] || ! grep -qE '^[[:space:]]*crossfamily:[[:space:]]*[^[:space:]]' "$m"; then
@@ -971,6 +1072,263 @@ validate_thirdparty_leg() { # $1 = marker path
   return 0
 }
 
+SOUL_PRESENT_GRACE_DATE="2026-08-21"
+validate_soul_present_leg() { # $1 = marker path
+  # ── ①영혼 존재 검사 (2026-08-21) ──────────────────────────────────────────────
+  # CLAUDE.md §자기 대조 has mandated an ①영혼 line (성공 정의 / 절대 안 함) on every marker
+  # since 2026-08-09. MEASURED on the real corpus this day, with the instrument calibrated over
+  # EIGHT spellings and two controls (`axes-run` and `axis2-engine` = 98/98): of 98 post-grace
+  # markers, 61 carry it and **37 (37.8%) carry no form of it at all**.
+  #
+  # 🟥 The first pass of that same measurement grepped only the exact `①영혼` string and returned
+  # "92.9% missing". That would have been a false alarm ([[feedback_measured_scope_vs_claimed_scope]]
+  # — hand-enumerating spellings). The union + hand-verification of one negative sample is what
+  # makes the 37 real: `.axes_23_passed_feat_target-freeze-gate_2026-08-18.marker` was opened by
+  # eye — a panel-reviewed, 28-lane, controls-alive marker with every OTHER field filled, and no
+  # soul line in any spelling.
+  #
+  # 🟥 WHY THIS IS NOT THE THING THE ①영혼 COMMENT BELOW DECLINES. That comment refuses to check
+  # «was it written BEFORE designing» — unverifiable from a file, correctly excluded, and this
+  # lane does not check it. PRESENCE is a different question and is trivially decidable. The
+  # impossible question carried the possible one out on its ticket.
+  #
+  # SCOPE — channel, not judgment. Asserts the field EXISTS and is not vacuous. Says nothing about
+  # whether the success definition is good, was honoured, or was written in advance.
+  local m="$1" n body words
+  # Grace: only markers dated on/after the grace date are required to carry it. Retroactive
+  # enforcement would block every in-flight branch, and that over-block trains `--no-verify`,
+  # which would disarm the Destructive-Op gate living in this same hook.
+  local mdate
+  mdate=$(printf '%s' "$m" | sed -nE 's/.*_([0-9]{4}-[0-9]{2}-[0-9]{2})\.marker$/\1/p')
+  # 🟥 An unparseable date used to `return 0` — fail-OPEN. The hook itself builds this filename
+  # as `..._${TODAY}.marker`, so a name without a date is unexpected, not old. Unknown is not
+  # exempt ([[feedback_not_found_is_not_zero_family]]); it falls through to the presence check.
+  [ -z "$mdate" ] || { [ "$mdate" \< "$SOUL_PRESENT_GRACE_DATE" ] && return 0; }
+  # 🟥 agy (claims axis): the comment above says the MEASUREMENT swept eight spellings; this
+  # regex carries FOUR alternatives (①영혼 · a `soul:` key · 성공[ ]?정의 · 절대 안 함). Both are
+  # true and they are different instruments — but writing only the first invites reading the
+  # second's coverage off it ([[feedback_rule_misdescribes_its_own_machine]]). The four are the
+  # ones the corpus actually uses as a FIELD; the other four measured spellings appeared only
+  # inside prose, which this leg deliberately excludes.
+  # 🟥 The soul detector must NOT read the `soul-check:` line itself. codex's alignment fix widened
+  # the pattern and G8 flipped to PASS: `soul-check: reflected(…성공정의…)` matched as its own
+  # evidence — self-referential FP ([[feedback_lane_runner_self_referential_fp]]). The claim can
+  # never be its own ground. Same reason comment/prose lines are excluded: a marker that merely
+  # SAYS 성공 정의 in narration has not declared one.
+  # 🟥 A DECLARATION, not a MENTION. First real use (isolated clone, 2026-08-21) broke this on
+  # attempt #1: this very delta's marker says «change: 마커의 ①영혼 슬롯에 소비처가 0이던 것을…»
+  # in a prose FIELD VALUE, and the leg reported "①영혼 present: 10 words" for a marker that
+  # declares nothing. Excluding `#` and `soul-check:` was not enough — any field whose value
+  # discusses the axis satisfies a substring test, and markers ABOUT this axis always will.
+  # 39 lanes, codex (diff axis) and agy (claims axis) all missed it; running it once did not
+  # ([[feedback_adversarial_review_not_substitute_for_first_use]]).
+  # So the token must sit at LINE START as the key (a leading markdown `#` is allowed — the real
+  # corpus writes «## ①영혼 — 설계 전에 쓴 …» as a heading, and P7 flipped to BLOCK when the first
+  # version of this regex forbade it. The known-pair caught that in one run).
+  # Prose inside a field VALUE can no longer vote.
+  _soul_src=$(grep -E '^[[:space:]]*#*[[:space:]]*(①영혼|soul|절대 안 함|성공 ?정의)[[:space:]]*[:—-]' "$m" 2>/dev/null \
+              | grep -vE '^[[:space:]]*soul-check[[:space:]]*:')
+  n=$(printf '%s\n' "$_soul_src" | grep -cE '①영혼|^[[:space:]]*soul:|성공 ?정의|절대 안 함'); n=${n:-0}
+  if [ "$n" -eq 0 ]; then
+    echo "  ❌ FAIL — marker carries no ①영혼 line (성공 정의 / 절대 안 함)."
+    echo "     CLAUDE.md §자기 대조 requires it on every marker. Measured 2026-08-21: 37 of 98"
+    echo "     post-grace markers had none — including panel-reviewed ones with every other"
+    echo "     field filled. Nothing read the field, so nothing noticed."
+    echo "     Write, before the design: 성공 정의 = «…». 절대 안 함 = «…»."
+    echo "     🟥 This checks PRESENCE, not provenance. «Was it written first» stays unverifiable"
+    echo "     and unchecked — see the ①영혼 comment below. Presence is not that question."
+    return 1
+  fi
+  # Non-vacuity — counted in WORDS, not characters (Korean corpus; ${#} is locale-dependent).
+  body=$(awk '/①영혼|^[[:space:]]*soul:|성공 ?정의|절대 안 함/{if (!f) f=1}
+              f && /^[[:space:]]*$/{exit}
+              f && seen && /^[[:space:]]*[A-Za-z][A-Za-z0-9_-]*:/{exit}
+              f{print; seen=1}' <<< "$_soul_src")
+  words=$(printf '%s' "$body" | wc -w | tr -d ' '); words=${words:-0}
+  # 🟥 A DECLARED ABSENCE IS A VALUE, not a gap. CLAUDE.md §자기 대조 explicitly permits
+  # «없으면 `없음`», and the first version of this leg BLOCKED a bare `soul: 없음` (2 words) while
+  # PASSING a 33-word paragraph whose content was «I did not write one». That punishes the honest
+  # form and rewards padding — [[feedback_unreachable_done_when_trains_evasion]] exactly. Found by
+  # a peer session's first real use of this gate (forge-harness-59, 2026-08-21); self-detection 0,
+  # and 41 lanes + two cross-family panels had all passed.
+  # Same shape as the sibling axes' `UNKNOWN`: recorded, not silent, and never free of a record.
+  # 🟥 `$body` — this leg's own local. The first version read `$soul_body`, which is the OTHER
+  # leg's variable name; unset here, so the case never matched and the fix was inert while the
+  # lane suite stayed green ([[feedback_unedited_parts_of_my_own_file]] · half-fix).
+  _sbare=$(printf '%s' "$body" | sed -E 's/^[[:space:]]*#*[[:space:]]*(①영혼|soul|절대 안 함|성공 ?정의)[[:space:]]*[:—-]*//' | tr -d '[:space:].·]')
+  case "$_sbare" in
+    없음|없음—|none|None|NONE|n/a|N/A|-|해당없음)
+      echo "  ⚠️  ①영혼: 없음 — declared absent. Recorded, not silent."
+      echo "     🟥 A marker that declares no success definition cannot carry"
+      echo "     soul-check: reflected(...) — there is nothing to reflect against."
+      return 0 ;;
+  esac
+  if [ "$words" -lt 6 ]; then
+    echo "  ❌ FAIL — ①영혼 line is vacuous ($words word(s)). Name the success definition AND"
+    echo "     the 절대 안 함. A one-word placeholder trains the ritual this field exists to avoid."
+    return 1
+  fi
+  echo "  ✅ ①영혼 present: $words word(s)"
+  return 0
+}
+
+validate_soul_check_leg() { # $1 = marker path
+  # ── ⓒ 격리 그라운딩 — 사전 선언으로 확장 (2026-08-21) ─────────────────────────
+  # 🟥 NOT a seventh axis. Classified against `fh_three_layer_canon.md §1-a-2`, whose
+  # discriminator is explicit: «축은 «얼마나 적대적인가»로 갈리지 않는다. «무엇을 받았는가»로
+  # 갈린다.» ⓒ 격리 그라운딩 receives «저자가 쓴 문장 + 지금의 트리» — which is, character for
+  # character, what this leg receives (①영혼 is 저자가 쓴 문장; the delta is 지금의 트리).
+  # The tense differs (사전 선언 vs 사후 주장) and tense is a posture, not an axis, exactly as
+  # that section says adversarialness is («적대성은 자세지 축이 아니다»).
+  # Precedent, in the canon itself: the author attributed 5 findings to ⓓ and two independent
+  # cross-family classifiers reclassified 3 of them — «그 셋은 축이 필요했던 게 아니라 다른 축이
+  # 놓친 것이다». Minting ⓖ would have been that mistake a second time.
+  # ⇒ ⓒ's 「받는 것」 widens to «저자가 쓴 문장(사후 주장 및 **사전 선언**)», and `soul-check:`
+  # is ⓒ's own field in the same shape `standpoint:` is ⓑ's. The six axes stay six.
+  # WHY: CLAUDE.md §자기 대조 has required an `①영혼` line (성공 정의 / 절대 안 함) on every
+  # marker since 2026-08-09, and it is written 4/4 on the real corpus. NOTHING has ever read it
+  # back. Measured this day with a control: `crossfamily` = 21 hits in this hook, `①영혼`/`soul`
+  # = 0 lines of consuming code anywhere in templates/ or scripts/; `fh_4axis_gate.md` does not
+  # even name the field. That is the half-externalization shape — a slot with zero consumers,
+  # which always reports "done" because presence is doing the judging.
+  #
+  # 🟥 The reason this hook gave for NOT checking the field answers a DIFFERENT question. Line
+  # ~1058 declines it because «did you write it BEFORE designing» is unverifiable from a file —
+  # true, and correctly excluded. But «was it then SATISFIED» is a separate question that was
+  # never asked, and it rode out on the first one's ticket.
+  #
+  # SCOPE — channel, not judgment (CLAUDE.md §Mechanization Boundary). This lane asserts
+  # properties of the RECORD: single · closed enum · non-vacuous · not wearing another axis's
+  # tokens · **and consistent with the ①영혼 line in the same file**. It never asserts the
+  # read-back reached the right conclusion. A fabricated `reflected(...)` with a fluent reason
+  # PASSES — that hole is §4-b's (cross-family reads the marker), not this lane's, and it is
+  # named here rather than papered over.
+  local m="$1" line val reason n soul_n soul_body
+  n=$(grep -cE '^[[:space:]]*soul-check:' "$m" 2>/dev/null); n=${n:-0}
+  if [ "$n" -eq 0 ]; then
+    # 🟥 A near-miss key reads as "absent" and takes the grace exit — silent, and the author
+    # believes they recorded it. Absent is legal; MISSPELLED is not.
+    if grep -qE '^[[:space:]]*(soul[ _-]?check[[:space:]]*:|soulcheck:|soul-checks:)' "$m" 2>/dev/null \
+       && ! grep -qE '^[[:space:]]*soul-check:' "$m" 2>/dev/null; then
+      echo "  ❌ FAIL — a line looks like a soul-check key but is not exactly 'soul-check:'."
+      grep -nE '^[[:space:]]*(soul[ _-]?check[[:space:]]*:|soulcheck:|soul-checks:)' "$m" | sed 's/^/       /'
+      return 1
+    fi
+    return 0   # genuinely absent — adoption is incremental, same as thirdparty:
+  fi
+  if [ "$n" -gt 1 ]; then
+    echo "  ❌ FAIL — marker carries MORE THAN ONE 'soul-check:' line."
+    grep -nE '^[[:space:]]*soul-check:' "$m" | sed 's/^/       /'
+    echo "     Readers take the first, so an appended correction is silently shadowed."
+    return 1
+  fi
+  line=$(grep -m1 -E '^[[:space:]]*soul-check:' "$m" | sed -E 's/^[[:space:]]*soul-check:[[:space:]]*//')
+  val=$(printf '%s' "$line" | sed -E 's/\(.*$//' | sed -E 's/[[:space:]]*(—|--).*$//' | sed -E 's/[[:space:]]+$//')
+
+  # Cross-axis contamination — the other three axes ask different questions.
+  case "$val" in
+    tier1|tier1b|tier2|tier2b|tier3|panel|declined|checked|none-found|peer-review|\
+DEGRADED_SINGLE_FAMILY|DEGRADED_PANEL_UNUSED|DEGRADED_NO_TARGET_ACCESS|DEGRADED_NO_ACCESS)
+      echo "  ❌ FAIL — '$val' belongs to another axis, not soul-check:."
+      echo "     standpoint = whose repo was ground truth · crossfamily = which model family reviewed"
+      echo "     thirdparty = was this already done outside · soul-check = was THIS marker's own"
+      echo "     ①영혼 (성공 정의 / 절대 안 함) read back against the delta."
+      return 1 ;;
+  esac
+
+  # Is there an ①영혼 line in this same marker, and does it carry content?
+  # 🟥 The soul detector must NOT read the `soul-check:` line itself. codex's alignment fix widened
+  # the pattern and G8 flipped to PASS: `soul-check: reflected(…성공정의…)` matched as its own
+  # evidence — self-referential FP ([[feedback_lane_runner_self_referential_fp]]). The claim can
+  # never be its own ground. Same reason comment/prose lines are excluded: a marker that merely
+  # SAYS 성공 정의 in narration has not declared one.
+  # 🟥 A DECLARATION, not a MENTION. First real use (isolated clone, 2026-08-21) broke this on
+  # attempt #1: this very delta's marker says «change: 마커의 ①영혼 슬롯에 소비처가 0이던 것을…»
+  # in a prose FIELD VALUE, and the leg reported "①영혼 present: 10 words" for a marker that
+  # declares nothing. Excluding `#` and `soul-check:` was not enough — any field whose value
+  # discusses the axis satisfies a substring test, and markers ABOUT this axis always will.
+  # 39 lanes, codex (diff axis) and agy (claims axis) all missed it; running it once did not
+  # ([[feedback_adversarial_review_not_substitute_for_first_use]]).
+  # So the token must sit at LINE START as the key (a leading markdown `#` is allowed — the real
+  # corpus writes «## ①영혼 — 설계 전에 쓴 …» as a heading, and P7 flipped to BLOCK when the first
+  # version of this regex forbade it. The known-pair caught that in one run).
+  # Prose inside a field VALUE can no longer vote.
+  _soul_src=$(grep -E '^[[:space:]]*#*[[:space:]]*(①영혼|soul|절대 안 함|성공 ?정의)[[:space:]]*[:—-]' "$m" 2>/dev/null \
+              | grep -vE '^[[:space:]]*soul-check[[:space:]]*:')
+  soul_n=$(printf '%s\n' "$_soul_src" | grep -cE '①영혼|^[[:space:]]*soul:|성공 ?정의|절대 안 함'); soul_n=${soul_n:-0}
+  # Body = the ①영혼 block only: stop at a blank line OR at the next ASCII field key. An earlier
+  # draft ran the range to EOF, so a marker reading «①영혼: 없음» followed by any other field was
+  # scored as having content — the fixture G9 caught it.
+  # 🟥 Counted in WORDS, not characters. `${#var}` on Korean text is bytes-or-chars depending on
+  # locale, and this corpus is Korean — a char threshold silently changes meaning per machine
+  # ⚠️ Honest caveat, measured: `wc -w` is NOT a human word count on Korean either («①영혼: 완주»
+  # reports 3, not 2). It is stable per-machine and monotonic, which is all a floor needs — but
+  # every threshold here was calibrated by RUNNING it, never by reasoning about word counts.
+  # ([[feedback_instrument_vs_target_and_budget]], 단위 혼동). Word count is locale-independent.
+  soul_body=$(awk '/①영혼|^[[:space:]]*soul:|성공 ?정의|절대 안 함/{if (!f) f=1}
+                   f && /^[[:space:]]*$/{exit}
+                   f && seen && /^[[:space:]]*[A-Za-z][A-Za-z0-9_-]*:/{exit}
+                   f{print; seen=1}' "$m" 2>/dev/null \
+              | sed -E '1s/^[[:space:]]*(①영혼|soul)[^[:alnum:]«]*//')
+  soul_words=$(printf '%s' "$soul_body" | wc -w | tr -d ' ')
+  soul_words=${soul_words:-0}
+
+  case "$val" in
+    UNKNOWN)
+      echo "  ⚠️  soul-check leg: UNKNOWN — 안 봤다. Recorded, not silent." ;;
+    reflected|violated|DEGRADED_NOT_RUN|DEGRADED_NO_SOUL|not-applicable)
+      case "$line" in *\(*) ;; *)
+        echo "  ❌ FAIL — '$val' without a (<grounds>) parenthetical."
+        echo "     A read-back that names neither WHAT read it nor WHAT came back is"
+        echo "     indistinguishable from not running it."
+        return 1 ;;
+      esac
+      # 🟥 Measure INSIDE the parens. The old form took everything after the first `(`, so
+      # `reflected() — <long tail>` passed on text that was never grounds (codex, diff axis).
+      reason=$(printf '%s' "$line" | sed -E 's/^[^(]*\(//; s/\)[^)]*$//')
+      # 🟥 agy (claims axis, 2026-08-21): this leg's own comment above condemns `${#var}` on
+      # Korean text and then used `${#reason}` twelve lines later — [[feedback_citing_a_rule_is_not_obeying_it]],
+      # verbatim. Inherited from the sibling legs, which does not excuse it here. Word count.
+      _rwords=$(printf '%s' "$reason" | wc -w | tr -d ' '); _rwords=${_rwords:-0}
+      if [ "$_rwords" -lt 3 ]; then
+        echo "  ❌ FAIL — '$val(...)' grounds are vacuous. Name what read the ①영혼 line back,"
+        echo "     against what, and what came back."
+        return 1
+      fi
+      # ── the consistency check that makes this lane non-decorative ──────────────
+      # Two fields in ONE record, mechanically decidable. Not a conclusion.
+      case "$val" in
+        reflected|violated)
+          if [ "$soul_n" -eq 0 ] || [ "$soul_words" -lt 6 ]; then
+            echo "  ❌ FAIL — '$val' claims the ①영혼 line was read back, but this marker has"
+            echo "     no ①영혼 line with content (found: $soul_n line(s), $soul_words word(s))."
+            echo "     🟥 Reflecting against an absent success-definition is the exact"
+            echo "     half-externalization this lane exists to catch. Write ①영혼 first,"
+            echo "     or record DEGRADED_NO_SOUL(<why>)."
+            return 1
+          fi ;;
+        DEGRADED_NO_SOUL)
+          if [ "$soul_n" -gt 0 ] && [ "$soul_words" -ge 6 ]; then
+            echo "  ❌ FAIL — 'DEGRADED_NO_SOUL' says there is nothing to reflect against, but"
+            echo "     this marker DOES carry an ①영혼 line with content ($soul_n line(s))."
+            echo "     A recorded absence contradicted by the same record is worse than silence."
+            return 1
+          fi ;;
+      esac
+      echo "  ✅ soul-check leg: $val" ;;
+    *)
+      echo "  ❌ FAIL — '$val' is not a member of the soul-check: enum."
+      echo "     Closed enum: reflected(<what came back — 어긋남 여부. NOT just who reviewed:
+     that is crossfamily's column, and duplicating it double-counts one event>) ·"
+      echo "     violated(<which half broke — 성공정의 미달 / 절대안함 위반 — and what was done>) ·"
+      echo "     DEGRADED_NOT_RUN(<why>) · DEGRADED_NO_SOUL(<why>) · UNKNOWN · not-applicable(<why>)"
+      echo "     🟥 'violated' is a legal value ON PURPOSE. A recorded violation is worth more"
+      echo "     than a hidden one, and a lane that only admits success trains erasure."
+      return 1 ;;
+  esac
+  return 0
+}
+
 
 
 # ── 4축 자기 대조 — «어느 축을 돌렸고 어느 축을 안 돌렸나» 형식 검사 ────────────
@@ -1292,7 +1650,27 @@ if [ "$GATE_MODE" = "full" ]; then
   MARKER="$MARKER_DIR/.axes_23_passed_${BRANCH_SLUG}_${TODAY}.marker"
 
   if [ -f "$MARKER" ]; then
-    if validate_marker_floor "$MARKER" && validate_marker_axes_run "$MARKER"; then
+    # Wave 1-D defense leg — floor tiers only (sonnet-floor / below-floor), on ANY full-gate marker.
+    # 🟥 It was first wired inside the LOAD-BEARING block below, which made the real condition
+    # "load-bearing AND floor tier" while the skill documented "floor tiers only" — a SKILL.md
+    # change at sonnet-floor would have passed with no defense line. Found by cross-family review
+    # (codex/gpt-5.5, 2026-08-20); self-detection 0. The scope the doctrine states is the scope
+    # the hook now has.
+    _DEFENSE_OK=1
+    if grep -qE '^[[:space:]]*floor-status:[[:space:]]*(sonnet-floor|below-floor)' "$MARKER"; then
+      validate_defense_leg "$MARKER" || _DEFENSE_OK=0
+    fi
+    # ⓒ 사전 선언 (①영혼) — scope is EVERY marker (CLAUDE.md §자기 대조 mandates ①영혼 on all of them), so it
+    # belongs HERE and not in the load-bearing block below.
+    # 🟥 It was first wired there, exactly like `validate_defense_leg` above — the real condition
+    # would have been "load-bearing AND has a marker" while the doctrine says every marker. The
+    # note recording that precedent is ~8 lines above this one and was in the file at the time;
+    # the same defect was made one day later anyway ([[feedback_unedited_parts_of_my_own_file]]).
+    # Caught by the operator asking «배선 완료되었나?», not by a lane and not by cross-family.
+    _SOUL_OK=1
+    validate_soul_present_leg "$MARKER" || _SOUL_OK=0
+    validate_soul_check_leg "$MARKER" || _SOUL_OK=0
+    if [ "$_DEFENSE_OK" -eq 1 ] && [ "$_SOUL_OK" -eq 1 ] && validate_marker_floor "$MARKER" && validate_marker_axes_run "$MARKER"; then
       echo "  ✅ PASS (marker confirmed + floor/axes fields valid:"
       echo "     .axes_23_passed_${BRANCH_SLUG}_${TODAY}.marker)"
     else
@@ -1827,6 +2205,24 @@ PTR_EOF
   fi
 fi
 
+# ── 상주 유입 게이트 (mandatory-pass — blocks) ────────────────────────────────
+# 왜 여기 있나 (2026-08-20 실측): 감량은 유출이 아니라 **유입** 문제다.
+#   CLAUDE.md 23,839(05-26) → 70,758(07-20 «11.9% 감량» 직후) → 144,138(08-20)
+#   07-20 이후 31일 +73,380 = 약 2,367 bytes/일. 같은 기간 어블레이션 CUT 판정 **0건**.
+#   최대 감량 후보 절(22k)조차 유입 9일치 ⇒ 나가는 문만 당기면 구조적으로 진다.
+# 검사하는 것은 **기록의 속성**이지 결론이 아니다(§Mechanization Boundary):
+# 「이 문단이 상주할 가치가 있나」를 판정하지 않고 「저자가 유형을 선언했나」만 본다.
+# Anchor: scripts/test_residency_admission_lanes.sh (레인 10 · 컨트롤 2 · 가드 7 전수 되돌림 격리)
+RESID="$REPO_ROOT/scripts/residency_admission_check.sh"
+if [ -f "$RESID" ]; then
+  echo "[Residency] 상주 유입 게이트..."
+  resid_out=$(bash "$RESID" "$REPO_ROOT" 2>&1); resid_rc=$?
+  printf '%s\n' "$resid_out" | sed 's/^/  /'
+  if [ "$resid_rc" -ne 0 ]; then FAILED=1; fi
+else
+  echo "  ⚠️  상주 유입 게이트 미설치 (scripts/residency_admission_check.sh) — skipped, not passed"
+fi
+
 # ── Verdict ───────────────────────────────────────────────────────────────────
 echo ""
 echo "══════════════════════════════════════════════"

package/templates/.git-hooks/pre-push

@@ -357,10 +357,25 @@ PPRANGES
       [ "${PUBLIC_SURFACE_OK:-0}" = "1" ] || exit 1
     fi
     if [ "${_pp_count:-0}" -gt 0 ]; then
-      if printf '%s\n' "$_pp_added" | awk '
+      # 🟥 rc 를 «비영» 으로 뭉개지 마라 (cross-family, 2026-08-21): 1=유출 · 3=계기 사망.
+      #    합치면 아래 PUBLIC_SURFACE_OK 가 **계기 사망까지 승인**한다 — push 는 비가역이다.
+      _pp_rc=0
+      printf '%s\n' "$_pp_added" | awk '
            /^\+\+\+ b\// { f = substr($0, 7); next }
            /^\+/         { print f "\t" substr($0, 2) }
-         ' | psa_scan_tagged; then
+         ' | psa_scan_tagged || _pp_rc=$?
+      if [ "$_pp_rc" = "3" ]; then
+        echo ""
+        echo "══════════════════════════════════════════════"
+        echo " ⛔ FH Pre-Publish Gate (pre-push) — INSTRUMENT DEAD, scan did NOT run"
+        echo "══════════════════════════════════════════════"
+        echo "  rc=3 = NOT SCANNED. That is not «no token found» — nothing was measured."
+        echo "  PUBLIC_SURFACE_OK does NOT cover this: an override approves a KNOWN mention,"
+        echo "  never an unmeasured surface. Fix the scanner first (run under bash; psa_load)."
+        echo "══════════════════════════════════════════════"
+        exit 1
+      fi
+      if [ "$_pp_rc" = "0" ]; then
         echo "  ✅ FH Pre-Publish: no operator-private token in the TEXT added by ${_pp_count} commit(s)"
         echo "     (not covered: annotated-tag messages · binary blobs — named residuals)"
       else

package/templates/settings.PriorArt.snippet.json

@@ -0,0 +1,44 @@
+{
+  "_README": [
+    "prior-art 프롬프트 훅 스니펫 — install-wizard 가 사용자 로컬 .claude/settings.json 에 머지하는",
+    "tracked SOURCE 다. 이 레포의 .claude/settings*.json 은 전부 gitignored 라 **훅 등록 자체를",
+    "tracked 로 둘 수 없다.** 머지 단계가 없으면 훅은 돌지 않는다 —",
+    "**스크립트를 출하하는 것과 배선하는 것은 같은 명제가 아니다.**",
+    "",
+    "🟥 왜 이 래퍼가 뒤늦게 생겼나 (2026-08-22 실측, 컨트롤 동반):",
+    "  이 파일은 형제 스니펫 넷과 달리 `project_settings_json` 래퍼 **없이** 출하되고 있었다.",
+    "  install-wizard 의 실제 머지 코드(install-wizard/SKILL_detail.md:642-645)는 그 키가 없으면",
+    "    print(\"SKIP (no project_settings_json)\", ...); continue",
+    "  로 **조용히 건너뛴다.** 즉 이 훅은 「아직 안 돌렸다」가 아니라",
+    "  **「install-wizard 를 돌려도 항상 스킵돼서 한 번도 등록된 적이 없다」** 였다.",
+    "  전수 실측: Compaction·FieldCanon·PreToolUse·SessionStart = 래퍼 O · PriorArt = 혼자 부재.",
+    "  머지 코드를 그대로 복사해 실행한 수리 전/후 대조로 SKIP→등록 전이를 확인했다.",
+    "  ⇒ built_but_not_wired 보다 나쁘다. **설치기가 자기 출하물을 조용히 건너뛰는** 형태다.",
+    "  회귀 앵커: scripts/test_wizard_snippet_merge_lanes.sh 의 전수 래퍼 검사(이 수리와 같이 들어갔다).",
+    "",
+    "무엇을 하나: 새 메커니즘을 짓기 직전에 «책장 먼저, 없으면 도서관» 을 띄운다.",
+    "정체성 ④(프런티어 답습)의 **빌드 시점 격발 표면**이다.",
+    "🟥 명시된 잔여: matcher 가 `Write|Bash` 라도 **auto-mode 세션이 heredoc 으로 파일을 만드는",
+    "경로는 Bash 로 잡히지만**, 그 안에서 실제로 새 메커니즘을 짓는지까지는 훅이 모른다.",
+    "표면화까지가 훅의 몫이고 판정은 사람/세션이 한다 — 판정하는 훅을 만들면",
+    "§Mechanization Boundary 가 금하는 «결론을 단언하는 체크»가 된다.",
+    "",
+    "PRIVATE PATH 없음 → .claude/settings.json(프로젝트 로컬)에 속한다.",
+    "머지하되 덮어쓰지 마라: 기존 PreToolUse 엔트리를 보존하고 스크립트 이름을 키로 FH 것만 교체."
+  ],
+  "project_settings_json": {
+    "hooks": {
+      "PreToolUse": [
+        {
+          "matcher": "Write|Bash",
+          "hooks": [
+            {
+              "type": "command",
+              "command": "bash \"$CLAUDE_PROJECT_DIR/scripts/prior_art_prompt.sh\""
+            }
+          ]
+        }
+      ]
+    }
+  }
+}