@chrono-meta/fh-gate 1.4.89 → 1.4.91

package/scripts/reviewer_capability_corpus.tsv

@@ -0,0 +1,124 @@
+# reviewer_capability_corpus.tsv — SHARED known-pair corpus for "can this model be an
+
+# adversarial reviewer?". Language-neutral DATA, deliberately not code.
+#
+# WHY DATA AND NOT A SHARED LIBRARY. The same judgment lives in at least three places, in
+# three languages, across a public/private repo boundary: a public gate hook (bash), a
+# field probe (shell), and a review backend (python). They cannot import each other —
+# different repos, and the private side's vocabulary contains identifiers that must not
+# reach a public repo. So the shareable artifact is the CORPUS, not the classifier: each
+# side implements in its own language and proves agreement by running these rows.
+#
+# Measured drift 2026-08-08, before this file existed: 19 probe ids, **10 disagreements**
+# between two of the implementations — and asymmetrically, 9 of them were the private side
+# reading INCAPABLE models as CAPABLE. A permissive drift on the side that faces a real
+# model catalog is the dangerous direction: it inflates panel size and family-diversity
+# counts simultaneously, so the defense reports green while the panel cannot review.
+#
+# RESIDENCY: this file is PUBLIC. Generic capability classes and publicly-documented model
+# families only. A corp/internal model id NEVER goes here — carry those in a local overlay
+# corpus alongside (gitignored), same two-layer shape as the public-surface pattern file.
+#
+# NAMESPACES — declare what you own, skip what you do not (OPA-bundle `roots` shape).
+# Two different things get classified under the same question and they are NOT interchangeable:
+#   ns:cli       sidecar / CLI names a panel is composed of  — `codex`, `gemini`, `agy`
+#   ns:model-id  concrete served model identifiers            — `voyage-3`, `glm-ocr`
+# A consumer that classifies model ids has no opinion on `codex`; a consumer that composes
+# panels has no opinion on `bge-m3`. Mixing them silently is a defect: measured 2026-08-08,
+# the first draft of this corpus put both in one list and a model-id classifier failed the
+# `codex` row — reported as implementation drift when it was corpus scope error. An adapter
+# MUST declare its namespaces and SKIP rows outside them EXPLICITLY (a skipped row is
+# reported, never silently counted as passing — unmeasured is not clean).
+#
+# FORMAT (tab-separated):  id <TAB> expected <TAB> ns:<namespace>/<class> <TAB> why
+#   expected ∈ CAPABLE | INCAPABLE | UNDECIDABLE
+#     CAPABLE      a generative model of a family known to return prose findings
+#     INCAPABLE    emits vectors / scores / labels / transcripts — cannot return a finding
+#     UNDECIDABLE  unrecognised. NOT "capable by default" — default-deny, because a
+#                  denylist cannot know that `voyage-3` is an embedding model. An
+#                  implementation that answers CAPABLE here is failing open.
+#
+#   THE CORPUS STATES GROUND TRUTH, NOT WHAT ANY IMPLEMENTATION CAN SEE. `voyage-3` IS an
+#   embedding model, so the row says INCAPABLE — even though a pattern classifier cannot
+#   tell from the string. Grading is therefore on OUTCOME SAFETY, not label identity:
+#
+#     hard FAIL   want ∈ {INCAPABLE, UNDECIDABLE} and got = CAPABLE     (permissive — ships a
+#                 broken panel; the only direction that can actually hurt)
+#     hard FAIL   want = CAPABLE and got ≠ CAPABLE                      (over-block — an
+#                 always-red gate teaches --no-verify)
+#     DEVIATION   INCAPABLE ↔ UNDECIDABLE in either direction           (reported, not failed:
+#                 both BLOCK under default-deny, so the outcome is identical)
+#
+#   This rule exists because the first draft graded on label identity and was silently fitted
+#   to one implementation's regex — `armorm` was written UNDECIDABLE and `voyage-3` INCAPABLE
+#   purely because that regex caught one and not the other. Two ids with the same property,
+#   two different standards, and the corpus was grading itself. Worse, it made "delete the
+#   row" the rational move for whoever maintained the weaker classifier.
+#
+# ORDERING INVARIANT the rows enforce: ineligibility must be tested BEFORE eligibility.
+# Rows marked `overlap` match a valid family AND an incapable class simultaneously; an
+# eligibility-first implementation admits them silently. They are the anchor for the ORDER,
+# not for the list.
+
+# ── CONTRACT PIN ───────────────────────────────────────────────────────────────
+#CORPUS-VERSION	2
+#CORPUS-SHA256	e0d8d83b9ae042e4
+#  Hash covers the DATA rows only (comments/format may be reworded without a version bump).
+#  Recompute EXACTLY this way — two ways of computing it is itself a drift source, and the
+#  first draft of this pin failed on a trailing-newline difference between two implementations:
+#      grep -E '^[^#[:space:]]' reviewer_capability_corpus.tsv | shasum -a 256 | cut -c1-16
+#  Every consumer recomputes it and compares. A mismatch is HARNESS_ERROR — not PASS, not FAIL:
+#  it means the consumer is reading a DIFFERENT corpus than the one this contract names, and a
+#  drifted local copy is the failure mode that makes every downstream instrument report healthy
+#  while nothing is actually shared. (Independent precedent: OPA bundle `roots`, test262/CNCF
+#  conformance-suite-as-contract; failure taxonomy: local-first resolution · silent skipping ·
+#  drifted duplicates.)
+
+# ── capable: generative families ────────────────────────────────────────────────
+codex	CAPABLE	ns:cli/generative	GPT-family agent CLI
+gpt-5.5	CAPABLE	ns:model-id/generative	GPT family
+gemini	CAPABLE	ns:cli/generative	Gemini family
+qwen3-32b	CAPABLE	ns:model-id/generative	Qwen family, generative variant
+glm-4.6	CAPABLE	ns:model-id/generative	GLM family, generative variant
+deepseek-v3	CAPABLE	ns:model-id/generative	DeepSeek family
+mistral-large	CAPABLE	ns:model-id/generative	Mistral family
+llama-4-70b	CAPABLE	ns:model-id/generative	Llama family
+
+# ── incapable: named by class token ─────────────────────────────────────────────
+text-embedding-3-large	INCAPABLE	ns:model-id/embedding	emits vectors
+some-reranker-v1	INCAPABLE	ns:model-id/reranker	emits scores
+generic-ocr-2b	INCAPABLE	ns:model-id/ocr	emits transcribed text, not judgment
+acme-safeguard-8b	INCAPABLE	ns:model-id/safeguard	classifier — emits labels
+text-moderation-latest	INCAPABLE	ns:model-id/moderation	classifier — emits labels
+whisper-large-v3	INCAPABLE	ns:model-id/speech	speech-to-text
+
+# ── incapable WITHOUT a class token in the name (the denylist's blind spot) ─────
+# These are why a denylist alone is insufficient and default-deny is required: nothing in
+# the string says "embedding". Every one is a real, publicly-documented model.
+voyage-3	INCAPABLE	ns:model-id/embedding	embedding model; name carries no class token
+bge-m3	INCAPABLE	ns:model-id/embedding	embedding model; name carries no class token
+gte-large	INCAPABLE	ns:model-id/embedding	embedding model; name carries no class token
+all-minilm-l6-v2	INCAPABLE	ns:model-id/embedding	embedding model; name carries no class token
+armorm	INCAPABLE	ns:model-id/reward	reward model — emits a scalar; opaque name, no class token
+starling-rm	INCAPABLE	ns:model-id/reward	reward model — emits a scalar
+cohere-rank-v3	INCAPABLE	ns:model-id/reranker	reranker named `rank`, not `rerank`
+
+# ── overlap: matches a VALID family AND an incapable class (ordering anchor) ────
+glm-ocr	INCAPABLE	ns:model-id/overlap	matches `glm` (capable) and `ocr` (incapable) — order decides
+qwen3-embedding-8b	INCAPABLE	ns:model-id/overlap	matches `qwen` (capable) and `embed` (incapable)
+snowflake-arctic-embed-l-v2.0	INCAPABLE	ns:model-id/overlap	family prefix unrecognised; `embed` decides
+
+# ── undecidable: unrecognised → default-deny, never assumed capable ─────────────
+some-new-model-x	UNDECIDABLE	ns:model-id/unknown	no known family; answering CAPABLE here is fail-open
+internal-model-7	UNDECIDABLE	ns:model-id/unknown	no known family
+codeguardian	UNDECIDABLE	ns:cli/unknown	NOT auto-incapable — a bare `guard` substring rule blocks this legitimately-named review tool; unrecognised, so default-deny applies, but as UNDECIDABLE not INCAPABLE
+
+# ── same-family exclusion (decorrelation, not capability) ──────────────────────
+# Capable models that must still be REJECTED as panel members when the governor is of that
+# family. Capability and decorrelation are different axes; an implementation that only
+# checks capability passes a same-family panel. Marked separately so an adapter that does
+# not own the decorrelation axis can skip this block explicitly rather than silently.
+#SAMEFAMILY	claude
+#SAMEFAMILY	opus
+#SAMEFAMILY	sonnet
+#SAMEFAMILY	haiku

package/scripts/selfcheck.sh

@@ -211,6 +211,45 @@ else
   fail=1
 fi
 
+# embedded --self-test suites (compaction_probe · judgment_circuit_lint · novelty_claim_check).
+# These three carry their lanes INSIDE the script (`--self-test`) rather than in a sibling
+# test_*_lanes.sh, so the name-list wiring above skipped them silently: 48 lanes existed and ran
+# only when a human typed the command. That is built-but-not-wired applied to the anchors themselves
+# — a later edit that breaks a lane stays green everywhere the project actually checks
+# (high re-review 2026-08-08). Same shape as the block above: subject absent → SKIP, subject present
+# but self-test missing → FAIL, never a silent pass.
+for _subj in compaction_probe judgment_circuit_lint novelty_claim_check; do
+  if [ ! -f "scripts/$_subj.sh" ]; then
+    echo "SKIP  $_subj --self-test (subject scripts/$_subj.sh absent)"
+  else
+    # ⚠️ **문자열 존재로 판정하지 마라.** 초판은 `grep -q -- '--self-test'` 였는데, 그 문자열은
+    # 헤더 주석과 usage echo 에도 있어서 **디스패처 한 줄만 지워도 여전히 매치**한다. 그리고
+    # 인식 못 한 모드에서 스크립트가 usage 를 찍고 exit 0 을 내므로, selfcheck 는 rc=0 을 보고
+    # 조용히 통과했다 — 25개 레인이 통째로 사라져도 `npm test` 는 PASS (high 3차 리뷰 실측).
+    # 존재검사가 진위를 못 본다는 그 클래스의 재발이다. **실행이 일어났다는 증거**를 요구한다.
+    # `< /dev/null` 필수: 인식 못 한 모드로 떨어지면 스크립트가 stdin 을 기다려 **무한 대기**한다
+    # (실측 — 디스패처 제거 known-negative 가 2분 타임아웃). CI 를 멈추는 건 조용한 통과보다 나쁘다.
+    # `timeout` 은 GNU coreutils 이고 **stock macOS 에 없다**. 가용성 확인 없이 부르면 rc=127 +
+    # 빈 출력 → 아래 `*)` 가 발동해 "dispatcher missing?" 이라는 **틀린 원인**으로 거짓 FAIL 이
+    # 난다(실측: homebrew 없는 PATH 에서 3개 subject 전부). 소비자 머신에서 `npm test` 와
+    # `prepublishOnly` 를 깨뜨리는 경로다. 정답 폼은 이미 레포에 있다(sync-from-be.sh:134).
+    # 없으면 무한대기 방지를 잃는 대신 도는 쪽을 택한다 — `< /dev/null` 이 그 방어의 본체다.
+    local _to=""; command -v timeout >/dev/null 2>&1 && _to="timeout 120"
+    _st_out="$($_to bash "scripts/$_subj.sh" --self-test < /dev/null 2>&1)"; _st_rc=$?
+    case "$_st_out" in
+      *캘리브레이션*) : ;;
+      *) echo "FAIL  $_subj: --self-test produced no calibration verdict (dispatcher missing?)"
+         printf '%s\n' "$_st_out" | head -3 | sed 's/^/      /'
+         fail=1; _st_rc=0 ;;   # 이미 FAIL 로 셌으니 아래서 중복 계상 안 한다
+    esac
+    if [ "$_st_rc" -ne 0 ]; then
+      echo "FAIL  $_subj --self-test (exit $_st_rc)"
+      printf '%s\n' "$_st_out" | tail -6 | sed 's/^/      /'
+      fail=1
+    fi
+  fi
+done
+
 # memory-link-check — the memory store is a GRAPH (memory_intent_recall.md: nodes=files,
 # edges=[[links]], recall walks one hop). Measured 2026-07-28: 50 of 872 edges pointed at a note
 # that existed under a different separator and 22 at nothing — a dead edge returns nothing and is
@@ -281,6 +320,34 @@ else
   fail=1
 fi
 
+# branch-claim lanes — shipped with 27 hand-run lanes and ZERO callers, so CI never ran one of them.
+# That is the exact defect its own subject guards against (a gate nobody claims against passes
+# forever), reproduced one layer up in its anchor. Same SKIP/FAIL shape: a missing subject is a
+# legitimate skip, a present subject with a missing anchor is a real failure. The lanes are hermetic
+# (per-PID temp dirs under the worktree, no network, no API spend), so running them here costs
+# nothing.
+#
+# ⚠️ Subject-absent is a FAIL here, NOT the SKIP the sibling blocks use. The SKIP arm exists for
+# subjects that may legitimately not ship; branch_claim.sh IS in package.json files[], so it is
+# present in the source checkout AND in the published package — absence can only mean deletion.
+# Nothing else catches that: measured 2026-08-09, package_coverage_check.sh returns PASS on a
+# files[] entry whose file does not exist, so a deleted subject would be green on every surface
+# (SKIP here + PASS there + npm silently omitting it). A cross-family reviewer caught this; the
+# first draft of this block used SKIP and would have silenced exactly that case.
+# Named residual, deliberately not fixed here: the sibling blocks above carry the same hole for
+# their own shipped subjects. Fixing them is a separate change with its own verification.
+if [ ! -f scripts/branch_claim.sh ]; then
+  echo "FAIL  scripts/branch_claim.sh is in package.json files[] but absent — a deleted subject, not a skip"
+  fail=1
+elif [ -f scripts/test_branch_claim_lanes.sh ]; then
+  if ! bash scripts/test_branch_claim_lanes.sh; then
+    fail=1
+  fi
+else
+  echo "FAIL  test_branch_claim_lanes.sh: branch_claim.sh present but its anchor is missing"
+  fail=1
+fi
+
 # And the ablation calibrator, for the third instance of the same reason. Its whole job is telling
 # apart states that look identical from outside — "the arm could not answer" vs "the runner is dead"
 # vs "the runner read the answer off disk" — and round 2 of its own adversarial review found that
@@ -439,6 +506,18 @@ else
   fail=1
 fi
 
+# hook_source_gate 는 subject 가 session_close_check.sh 가 아니라 별도로 돌린다 — 위 루프의
+# SKIP 조건(subject 부재)에 얹으면 엉뚱한 이유로 건너뛴다.
+if [ -f scripts/test_hook_source_gate_lanes.sh ]; then
+  if bash scripts/test_hook_source_gate_lanes.sh >/dev/null 2>&1; then
+    echo "PASS  test_hook_source_gate_lanes.sh"
+  else
+    echo "FAIL  test_hook_source_gate_lanes.sh (SessionStart source 게이트 쌍 붕괴)"
+    bash scripts/test_hook_source_gate_lanes.sh 2>&1 | grep "❌" | head -5 | sed "s/^/      /"
+    fail=1
+  fi
+fi
+
 for _anchor in scripts/test_session_close_lanes.sh scripts/test_card_drift_probe.sh scripts/test_session_close_chain_lanes.sh; do
   if [ ! -f scripts/session_close_check.sh ]; then
     echo "SKIP  ${_anchor##*/} (subject scripts/session_close_check.sh absent)"
@@ -520,6 +599,33 @@ else
   fail=1
 fi
 
+# utterance landing check — the close chain's CONTENT anchor, and it has to be RUN, not parsed.
+# Measured 2026-08-08 on the branch that introduced it: the only thing in this file that touched
+# `scripts/utterance_landing_check.sh` was the `bash -n` syntax sweep at the top. Syntax passing is
+# not the instrument working, so the script shipped via files[] with zero behavioural callers —
+# [[feedback_built_but_not_wired]] in its purest form, where the sole caller is prose in CLAUDE.md.
+#
+# What the self-test defends is specifically the DEGRADE DIRECTION. This checker's whole reason for
+# existing is that a dead grep prints zero hits and zero hits read as "nothing landed" — a fail-open
+# that manufactures a clean verdict out of a broken instrument. Its known-pair set pins that apart:
+# a genuine miss must exit 1 while a dead control must exit 10, and 10 must never collapse into 1.
+# Left unrun, the file rots exactly where it is load-bearing and nothing here would notice.
+# Absence is a FAIL, not a SKIP — and the distinction is mechanical, not stylistic. The SKIP arm
+# above for `probe_scope_check.sh` is correct because that file genuinely never ships; this one is
+# listed in package.json files[], so in BOTH a source tree and an installed package it must be here.
+# A SKIP would convert `rm scripts/utterance_landing_check.sh` into a green run — deletion as a
+# clean bill of health, which is the same fail-open shape the checker itself exists to refuse.
+if [ ! -f scripts/utterance_landing_check.sh ]; then
+  echo "FAIL  utterance_landing_check.sh: missing — it ships via package.json files[], so absence is deletion, not package mode"
+  fail=1
+elif _out=$(bash scripts/utterance_landing_check.sh --self-test 2>&1); then
+  echo "PASS  utterance_landing_check.sh (known-pair self-test: control-death → 10, target-miss → 1)"
+else
+  echo "FAIL  utterance_landing_check.sh: self-test failed — the close-chain content anchor cannot be trusted"
+  _show_failure "$_out"
+  fail=1
+fi
+
 # tag/version consistency guard. Wired with the guard it anchors: the guard exists because a wrong
 # tag reached the remote and a publish from the wrong tree was stopped only by npm's own collision
 # check, so an unrun anchor here would be the same luck-as-floor arrangement one layer up.

package/scripts/session_close_check.sh

@@ -94,6 +94,128 @@ if command -v gh >/dev/null 2>&1; then
   [ "${PRS:-0}" -gt 0 ] && echo "⚠️  ①-b $PRS open PR(s) by you — classify: self-mergeable vs awaiting-external"
 fi
 
+# ── ①-d CLOSE RE-OPENED? ──────────────────────────────────────────────────────
+# WHY: a session that closed cleanly and then kept working looks IDENTICAL to one that never
+# closed — both read Completed from outside, and ①-c cannot separate them. Measured 2026-08-09:
+# this session ran step 5 eleven times and a peer independently named the same gap. The two need
+# opposite actions — an unfinished close must be FINISHED, a re-opened one must be RE-FOLDED.
+# HOW: stamp each close-gated pass and count. Self-attested (whoever runs the check writes it):
+# it detects the pattern, it does not prove it.
+CLOSE_STAMP="$FH/tracks/_meta/.close_stamps_$TODAY"
+if [ "${FH_SESSION_CLOSE:-0}" = "1" ]; then
+  mkdir -p "$(dirname "$CLOSE_STAMP")" 2>/dev/null
+  date -u +%Y-%m-%dT%H:%M:%SZ >> "$CLOSE_STAMP" 2>/dev/null || true
+fi
+if [ -f "$CLOSE_STAMP" ]; then
+  CLOSE_N=$(grep -c . "$CLOSE_STAMP" 2>/dev/null | tr -d ' ')
+  if [ "${CLOSE_N:-0}" -gt 1 ]; then
+    echo "ℹ️  ①-d close ran $CLOSE_N times today — CLOSED-THEN-WORKED, not a stalled close."
+    echo "     Both look Completed from outside; only this counter separates them."
+    echo "     Every re-open owes a FULL step 5: append to fh_completed FIRST, then rewrite the card."
+  fi
+fi
+
+# ── ①-c LIVE PEER SESSIONS in this same harness ─────────────────────────────────
+# WHY: FH's close chain has an agreed two-axis order (peer appends → ping → **ask "더 있나" before
+# folding** → fold → re-check merged PRs), and it lived only in the session card as prose. Measured
+# 2026-08-09, the first two-axis close: the ping surfaced four deltas the closing session did not
+# know about, and **two of them were structurally invisible to `gh pr list`** (an inheritance
+# channel and a landing check — no PR exists for either). So a PR sweep is not a substitute; the
+# question is. This block does the DETECTION half mechanically. It never merges anything and never
+# blocks — the merge is where the loss risk is (two sessions writing one card is the shared-checkout
+# hazard this repo already named), and one occurrence is below this repo's own mechanization bar.
+#
+# HOW: a live session owns /tmp/cc-socks/<pid>.sock. pid → cwd resolves the ONE thing that actually
+# matters, "is this peer in MY harness" — which the agent-facing session list cannot answer, because
+# it reports names, not directories. Stale sockets are detectable (pid gone), so absence here is a
+# measurement rather than silence.
+# SCOPE (operator, 2026-08-09): this is a **claude-agents / Agent-View** feature — the surface where
+# sessions are deliberately run in parallel. A plain solo terminal must not be nagged because some
+# other window happens to be open. Discriminator is env, set by the parent that spawns the session.
+#   ⚠️ NEGATIVE ARM UNVERIFIED: a child session cannot observe a top-level session's environment, so
+#   "a real top-level session lacks these vars" is asserted, not measured. The lane simulates absence
+#   by unsetting them, which tests THIS SCRIPT'S logic — not that claim. Verify from a plain terminal.
+if [ -z "${CLAUDE_CODE_CHILD_SESSION:-}${CLAUDE_CODE_AGENT:-}" ] && [ "${FH_PEER_SCAN_FORCE:-0}" != "1" ]; then
+  : # solo/top-level surface — ①-c is out of scope here, and silence is the correct output
+else
+PEER_LIVE=0; PEER_UNKNOWN=0; PEER_STALE=0; PEER_SPARE=0; PEER_IDS=""
+SOCK_DIR="${FH_PEER_SOCK_DIR:-/tmp/cc-socks}"
+# Self-exclusion must walk the ANCESTOR chain, not compare `$$`. This script is a grandchild of the
+# session process that owns the socket, so `$$` never matches it — measured: the first run counted
+# the calling session as its own peer, i.e. it would tell you to go ask yourself.
+SELF_CHAIN=" $$ "
+_p=$$
+while :; do
+  _p=$(ps -o ppid= -p "$_p" 2>/dev/null | tr -d ' ')
+  case "$_p" in ''|0|1) break ;; esac
+  SELF_CHAIN="$SELF_CHAIN$_p "
+done
+_peer_cwd() { # $1=pid → cwd on stdout, empty if unresolvable
+  if [ -r "/proc/$1/cwd" ]; then readlink "/proc/$1/cwd" 2>/dev/null; return; fi
+  command -v lsof >/dev/null 2>&1 || return 0
+  lsof -a -p "$1" -d cwd -Fn 2>/dev/null | sed -n 's/^n//p' | head -1
+}
+if [ -d "$SOCK_DIR" ]; then
+  for _s in "$SOCK_DIR"/*.sock; do
+    [ -e "$_s" ] || continue
+    _pid="${_s##*/}"; _pid="${_pid%.sock}"
+    case "$_pid" in ''|*[!0-9]*) continue ;; esac
+    case "$SELF_CHAIN" in *" $_pid "*) continue ;; esac   # 나 자신(조상 체인)
+    if ! ps -p "$_pid" >/dev/null 2>&1; then PEER_STALE=$((PEER_STALE+1)); continue; fi
+    # bg-spare = pre-warmed worker, NOT a session. It owns a socket and a cwd like everything else,
+    # so cwd matching alone counts it as a peer — measured 2026-08-09, and it is a pure false
+    # positive with a clean signature. Exclude mechanically rather than explaining it away.
+    case "$(ps -p "$_pid" -o args= 2>/dev/null)" in *--bg-spare*) PEER_SPARE=$((PEER_SPARE+1)); continue ;; esac
+    _pcwd="$(_peer_cwd "$_pid")"
+    if [ -z "$_pcwd" ]; then
+      # Alive but undirected. NOT zero — a peer we cannot place is exactly the case that must not
+      # render as "no peers" (not-found != zero).
+      PEER_UNKNOWN=$((PEER_UNKNOWN+1)); continue
+    fi
+    case "$_pcwd" in
+      "$FH"|"$FH"/*) PEER_LIVE=$((PEER_LIVE+1)); PEER_IDS="$PEER_IDS $_pid" ;;
+    esac
+  done
+else
+  PEER_UNKNOWN=-1
+fi
+if [ "$PEER_UNKNOWN" = "-1" ]; then
+  echo "ℹ️  ①-c peer scan UNMEASURED — no session-socket dir at $SOCK_DIR (not 'no peers')"
+elif [ "$PEER_LIVE" -gt 0 ]; then
+  echo "⚠️  ①-c $PEER_LIVE peer CANDIDATE(s) in THIS harness —$PEER_IDS"
+  echo "     The surplus over the fleet view Working list is MIXED — do not read it as one thing."
+  echo "     Measured 2026-08-09, three kinds land here and only the first needs a message:"
+  echo "       working session   → ask before folding"
+  echo "       idle terminal     → a real session sitting at a prompt. Not working. Usually skip."
+  echo "       lingering process → a close that never finished (seen once, had to be killed by hand)"
+  echo "     Only the fleet view separates them. An earlier version of this text called the whole"
+  echo "     surplus unfinished closes; that was one case generalised, and it was wrong."
+  echo "     Do NOT switch to the job state file to narrow it: it marked THIS session done"
+  echo "     (firstTerminalAt set) while it was still running — it under-reports as hard as"
+  echo "     sockets over-report. Cross-read with the fleet view; neither source alone is right."
+  echo "     THIS IS A DETECTION LIST, NOT A RECIPIENT LIST — do not message all of them."
+  echo "     What survives here is: a live PROCESS whose cwd is this harness, minus pre-warmed"
+  echo "     spares. That still includes IDLE TERMINALS sitting at a prompt. It is NOT a list of"
+  echo "     sessions that are working — nothing here can tell you that; the fleet view can."
+  echo "     Notify only the ones actually WORKING/BUSY right now. Messaging a finished session"
+  echo "     is noise, burns a recipient approval, and does not land in their record."
+     echo "     Of those still working, ASK '지금부터 마감이다, 더 있나' — the question is wider than a"
+  echo "     PR sweep: a peer's inheritance-channel or landing-check work has no PR to find."
+  echo "     Then fold, then re-check \`gh pr list --merged\`. Merging their delta stays MANUAL."
+  echo "     SENDING IS NOT DELIVERING — a cross-session message can be held for the recipient"
+  echo "     user approval and never arrive; the send call still reports success. Measured"
+  echo "     2026-08-09: 2 of 5 notices were held while the card already claimed all 5 informed."
+  echo "     Record ANSWERS, not sends, and put the unanswered count in the card."
+  [ "$PEER_UNKNOWN" -gt 0 ] && echo "     + $PEER_UNKNOWN live session(s) whose directory is UNKNOWN (counted, not dismissed)"
+elif [ "$PEER_UNKNOWN" -gt 0 ]; then
+  echo "⚠️  ①-c 0 peers placed in this harness, but $PEER_UNKNOWN live session(s) are UNPLACEABLE"
+  echo "     — treat as possible peers and ask; do not read this as 'closing alone'."
+else
+  echo "✅ ①-c no live peer in this harness (${PEER_STALE} stale · ${PEER_SPARE} pre-warmed spare(s) ignored)"
+fi
+
+fi
+
 # ② FH assets changed today → harvest-loop owed
 # NOTE: no `grep -q` here — under `set -o pipefail`, -q's early exit SIGPIPEs git log (141),
 # masking a real match as pipeline failure so the warning NEVER fired on true positives
@@ -219,7 +341,18 @@ DISPATCHED=$(_int "$(grep -c "^$TODAY$" "$TALLY" 2>/dev/null | tr -d ' ' || true
 # while anything appended via yaml.dump renders `- date: '"'"'2026-08-02'"'"'`. Matching one form counted
 # half the entries as absent — a divergent-normalizer miss inside the check that exists to catch
 # missing records. Known-pair calibrated below in test_dispatch_log_lanes.sh.
-LOGGED=$(_int "$(grep -cE "^- date: *'?$TODAY'?" "$LOG" 2>/dev/null | tr -d ' ' || true)")
+# ── 전환 설계: 레거시 단일 파일 ∪ 세션별 디렉터리를 **둘 다** 읽는다 ────────────
+# WHY: 같은 파일 끝에 여러 세션이 append 하면 브랜치 병합이 확정 충돌이고, 그 해소가
+# 조용히 손상된다 — git 이 엔트리 헤더 한 줄을 공통 접두로 밀어내서 «양쪽 다 보존»이라는
+# 정답 해소가 엔트리를 흡수시킨다(2026-08-09 재현: 항목 133/정답 134, 파싱은 통과).
+# 처방은 세션당 한 파일. 다만 **마이그레이션과 배선을 같은 커밋에 묶으면** 아직 머지 안 된
+# 원장 브랜치와 대형 충돌이 나므로, 소비자를 먼저 «둘 다 읽게» 만든다. 그러면 데이터가
+# 언제 옮겨가든 이 검사는 안 깨진다. 두 상태 모두 known-pair 로 고정돼 있다.
+LOGDIR="$FH/knowledge/shared/learnings/subagent_invocations"
+_cat_logs() {  # 다중 파일에 grep -c 를 직접 걸면 파일별 `경로:개수` 를 찍어 합산이 깨진다(실측).
+  { [ -f "$LOG" ] && cat "$LOG"; [ -d "$LOGDIR" ] && cat "$LOGDIR"/*.yaml; } 2>/dev/null
+}
+LOGGED=$(_int "$(_cat_logs | grep -cE "^- date: *'?$TODAY'?" | tr -d ' ' || true)")
 if [ "${DISPATCHED:-0}" -gt 0 ] && [ "${LOGGED:-0}" -eq 0 ]; then
   echo "❌ ④-e $DISPATCHED sub-agent dispatch(es) today and ZERO invocation-log entries — the 60/40"
   echo "     promotion gate and the UAP loop both read that file; an unlogged session is invisible to"

package/scripts/test_branch_claim_lanes.sh

@@ -0,0 +1,231 @@
+#!/usr/bin/env bash
+# test_branch_claim_lanes.sh — branch_claim.sh known-pair 앵커.
+#
+# 왜 실행 테스트인가: `bash -n` 은 계기가 아니다 — 문법만 보고 exit 0 을 내므로
+# «전부 통과»와 구분이 안 된다([[feedback_gate_verification_must_execute]]).
+# «막혔다» ≠ «옳게 막혔다» 이므로 BLOCK 레인은 **완성 문장**으로 매칭한다 —
+# 조각 매칭은 claim/HEAD 역할을 뒤집는 뮤테이션을 통과시켰다(적대검증 A-5 실측).
+# 그 역할 뒤바뀜은 사용자를 반대 브랜치로 보내므로 게이트가 사고를 만드는 쪽이 된다.
+#
+# 격리: 레인마다 임시 저장소를 새로 판다. 실제 레포는 안 건드린다.
+# 세션 시뮬레이션: FH_CLAIM_TEST=1 + FH_CLAIM_SESSION 으로 두 세션을 흉내낸다.
+#
+# usage: bash scripts/test_branch_claim_lanes.sh
+
+set -uo pipefail
+SCRIPT="$(cd "$(dirname "$0")" && pwd)/branch_claim.sh"
+PASS=0; FAIL=0; LIVE_PID=""
+
+cleanup() { [ -n "$LIVE_PID" ] && kill "$LIVE_PID" 2>/dev/null; return 0; }
+trap cleanup EXIT
+
+_mkrepo() {
+  local d; d=$(mktemp -d "${TMPDIR:-/tmp}/bclaim.XXXXXX")
+  git -C "$d" init -q -b main
+  git -C "$d" config user.email t@t; git -C "$d" config user.name t
+  echo x > "$d/f"; git -C "$d" add f; git -C "$d" commit -qm init
+  echo "$d"
+}
+# 살아있는 peer 세션 하나를 실제 프로세스로 만든다 (kill -0 이 참이 되도록)
+# ⚠️ 반드시 fd 를 닫아서 띄운다: 백그라운드 프로세스가 stdout 을 물고 있으면
+#    이 스크립트를 파이프에 물릴 때 파이프가 안 닫혀 무한 대기한다(실측: 120s 타임아웃).
+_spawn_live() { sleep 900 >/dev/null 2>&1 & LIVE_PID=$!; echo "$LIVE_PID"; }
+
+_lane() { # name expected_rc actual_rc [must_contain...]
+  local name="$1" exp="$2" got="$3"; shift 3
+  local out="$LANE_OUT" ok=1 pat
+  [ "$got" = "$exp" ] || { ok=0; echo "  ❌ $name — rc=$got (기대 $exp)"; }
+  for pat in "$@"; do
+    case "$out" in *"$pat"*) ;; *) ok=0; echo "  ❌ $name — 출력에 «${pat}» 없음";; esac
+  done
+  if [ "$ok" = 1 ]; then echo "  ✅ $name"; PASS=$((PASS+1)); else FAIL=$((FAIL+1));
+    echo "     ── 실제 출력 ──"; echo "$out" | sed 's/^/     /'; fi
+}
+_ok() { if [ "$2" = 1 ]; then echo "  ✅ $1"; PASS=$((PASS+1)); else echo "  ❌ $1"; FAIL=$((FAIL+1)); fi; }
+
+# 세션 B(=peer)의 claim 을 살아있는 pid 로 직접 심는다
+_plant_peer() { # repo branch pid
+  mkdir -p "$1/.git/fh-claims"
+  printf 'branch=%s\nlabel=peer\npid=%s\nat_epoch=%s\n' "$2" "$3" "$(date +%s)" \
+    > "$1/.git/fh-claims/session-PEER"
+}
+
+# ⚠️ 주변 환경을 흡입하지 않는다 — 이 한 줄이 없어서 이 스위트는 «거짓 초록» 이었다.
+# branch_claim.sh 의 `_session_pid() { echo "${CLAUDE_PID:-${PPID:-$$}}"; }` 때문에, 저자 셸에
+# CLAUDE_PID 가 있으면 claim 이 **살아있는 pid**(그 Claude 프로세스)를 기록한다. 레인 ③ 은
+# A 가 재-claim 해서 peer 기록을 덮는 시나리오라, 그 pid 가 살아있느냐가 판정을 통째로 뒤집는다.
+# 실측 2026-08-09 (known-pair, 같은 트리·같은 커밋):
+#   CLAUDE_PID 있음 → 24 PASS / 0 FAIL      (저자 로컬 — 초록)
+#   CLAUDE_PID 없음 → 23 PASS / 1 FAIL ③   (CI — 적색, rc=0 기대 1)
+# 즉 코드가 아니라 **저자 환경**을 재고 있었고, 그 초록이 S-1 재설계의 유일한 증명이었다.
+# 앵커가 배선되기 전까지(=호출부 0개) 이 사실은 드러날 수 없었다.
+unset CLAUDE_PID
+
+echo "[branch-claim] known-pair 앵커"
+PEERPID=$(_spawn_live)
+
+# ── ① 기록 없음 → 통과 (부재 ≠ 위반) ───────────────────────────────────────
+R=$(_mkrepo); LANE_OUT=$(cd "$R" && bash "$SCRIPT" check 2>&1); rc=$?
+_lane "① 기록 없음 → 통과" 0 "$rc"; rm -rf "$R"
+
+# ── ② 내 기록 == HEAD → 통과, 그리고 at_epoch 이 갱신된다 (A-6) ────────────
+R=$(_mkrepo)
+(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me FH_CLAIM_NOW=1000 bash "$SCRIPT" claim a >/dev/null 2>&1)
+before=$(sed -n 's/^at_epoch=//p' "$R/.git/fh-claims/me")
+LANE_OUT=$(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me FH_CLAIM_NOW=99000 bash "$SCRIPT" check 2>&1); rc=$?
+after=$(sed -n 's/^at_epoch=//p' "$R/.git/fh-claims/me")
+_lane "② 내 기록==HEAD → 통과" 0 "$rc"
+_ok "②-b at_epoch 갱신됨 (${before} -> ${after}) — 나이가 «유휴»를 재게 된다" "$([ "$after" = 99000 ] && echo 1 || echo 0)"
+rm -rf "$R"
+
+# ── ③ ★ S-1 회귀: 양쪽 세션이 다 프로토콜을 지켜도 잡는다 ──────────────────
+#    초판 설계는 여기서 통과했다(= 오늘 사고를 못 막았다). 이 레인이 그 반증이다.
+#    타임라인: B가 main claim → A가 switch+claim(프로토콜 준수) → B가 커밋 시도
+R=$(_mkrepo)
+(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=B bash "$SCRIPT" claim bee >/dev/null 2>&1)
+_plant_peer "$R" main "$PEERPID"                        # A 를 살아있는 peer 로
+git -C "$R" switch -q -c ifkakao                        # A 가 트리를 옮기고
+# A 는 «살아있는» 세션이다 — 그 사실을 환경에서 빌리지 말고 레인이 직접 고정한다.
+# CLAUDE_PID 를 안 주면 claim 이 곧 죽을 서브셸의 PPID 를 기록하고, B 의 check 는
+# «살아있는 peer 0» 으로 통과한다 — 시나리오가 성립하지도 않은 채 초록이 된다.
+(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=session-PEER CLAUDE_PID="$PEERPID" bash "$SCRIPT" claim ay >/dev/null 2>&1)  # 프로토콜대로 claim
+LANE_OUT=$(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=B bash "$SCRIPT" check 2>&1); rc=$?
+_lane "③ ★S-1 회귀: 양쪽이 프로토콜을 지켜도 B 는 차단된다" 1 "$rc" \
+      "이 세션은 'main' 로 기록돼 있는데 HEAD 는 'ifkakao' 다" "git switch -- 'main'"
+rm -rf "$R"
+
+# ── ④ 불일치인데 살아있는 peer 없음 → 경고만, 통과 (A-2 과차단 방지) ───────
+R=$(_mkrepo)
+(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=solo bash "$SCRIPT" claim s >/dev/null 2>&1)
+git -C "$R" switch -q -c next
+LANE_OUT=$(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=solo bash "$SCRIPT" check 2>&1); rc=$?
+_lane "④ 1인 세션(살아있는 peer 0) → 차단 안 함" 0 "$rc" "살아있는 peer 세션이 없어"
+rm -rf "$R"
+
+# ── ④-b 컨트롤: 같은 상황에 살아있는 peer 가 있으면 차단 ───────────────────
+R=$(_mkrepo)
+(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=solo bash "$SCRIPT" claim s >/dev/null 2>&1)
+_plant_peer "$R" whatever "$PEERPID"
+git -C "$R" switch -q -c next
+LANE_OUT=$(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=solo bash "$SCRIPT" check 2>&1); rc=$?
+_lane "④-b 컨트롤: peer 살아있으면 차단 (④가 무조건 통과가 아님)" 1 "$rc"
+rm -rf "$R"
+
+# ── ④-c 죽은 peer 는 동시성 증거가 아니다 ──────────────────────────────────
+R=$(_mkrepo)
+(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=solo bash "$SCRIPT" claim s >/dev/null 2>&1)
+_plant_peer "$R" whatever 999999                        # 존재하지 않는 pid
+git -C "$R" switch -q -c next
+LANE_OUT=$(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=solo bash "$SCRIPT" check 2>&1); rc=$?
+_lane "④-c 죽은 peer → 차단 안 함 (시간 상수 의존을 줄인다)" 0 "$rc"
+rm -rf "$R"
+
+# ── ⑤ STALE → 통과 / 임계 미만 → 차단 ──────────────────────────────────────
+R=$(_mkrepo)
+(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me FH_CLAIM_NOW=0 bash "$SCRIPT" claim s >/dev/null 2>&1)
+_plant_peer "$R" x "$PEERPID"; git -C "$R" switch -q -c other
+LANE_OUT=$(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me FH_CLAIM_NOW=$((13*3600)) bash "$SCRIPT" check 2>&1); rc=$?
+_lane "⑤ STALE(13h) → 통과" 0 "$rc" "STALE"
+LANE_OUT=$(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me FH_CLAIM_NOW=$((11*3600)) bash "$SCRIPT" check 2>&1); rc=$?
+_lane "⑤-b 컨트롤: 11h → 여전히 차단" 1 "$rc"
+rm -rf "$R"
+
+# ── ⑥ override → 통과 + **파일에 실제로 기록** (A-4 팬텀 주장 수리) ────────
+R=$(_mkrepo)
+(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me bash "$SCRIPT" claim s >/dev/null 2>&1)
+_plant_peer "$R" x "$PEERPID"; git -C "$R" switch -q -c other
+LANE_OUT=$(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me FH_BRANCH_CLAIM_OK=1 bash "$SCRIPT" check 2>&1); rc=$?
+_lane "⑥ override → 통과" 0 "$rc" "FH_BRANCH_CLAIM_OK"
+_ok "⑥-b override 로그 파일이 실제로 생성·append 됨" \
+    "$([ -s "$R/.git/fh-branch-claim-overrides.log" ] && echo 1 || echo 0)"
+rm -rf "$R"
+
+# ── ⑦ detached / rebase 중 → 통과 (A-1 과차단 수리) ────────────────────────
+R=$(_mkrepo)
+(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me bash "$SCRIPT" claim s >/dev/null 2>&1)
+_plant_peer "$R" x "$PEERPID"; git -C "$R" checkout -q --detach
+LANE_OUT=$(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me bash "$SCRIPT" check 2>&1); rc=$?
+_lane "⑦ detached HEAD → 통과 (rebase/bisect 중 커밋을 막지 않는다)" 0 "$rc"
+rm -rf "$R"
+R=$(_mkrepo)
+(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me bash "$SCRIPT" claim s >/dev/null 2>&1)
+_plant_peer "$R" x "$PEERPID"; git -C "$R" switch -q -c other; mkdir -p "$R/.git/rebase-merge"
+LANE_OUT=$(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me bash "$SCRIPT" check 2>&1); rc=$?
+_lane "⑦-b rebase 진행 중 → 통과" 0 "$rc"
+rm -rf "$R"
+
+# ── ⑧ 테스트 노브는 FH_CLAIM_TEST=1 없이 무시된다 (A-3 무음 우회 차단) ─────
+R=$(_mkrepo)
+(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me bash "$SCRIPT" claim s >/dev/null 2>&1)
+_plant_peer "$R" x "$PEERPID"; git -C "$R" switch -q -c other
+# 테스트 모드 없이 노브만 주면 → 세션ID 폴백이 달라 기록을 못 찾아 통과할 수 있으므로,
+# 실제 세션ID를 고정해 두고 STALE/NOW 노브가 먹지 않는지만 본다
+export CLAUDE_CODE_SESSION_ID=me
+LANE_OUT=$(cd "$R" && FH_CLAIM_STALE_HOURS=0 FH_CLAIM_NOW=99999999999 bash "$SCRIPT" check 2>&1); rc=$?
+_lane "⑧ FH_CLAIM_TEST 없이 STALE/NOW 노브 → 무시되고 차단 유지" 1 "$rc"
+unset CLAUDE_CODE_SESSION_ID
+rm -rf "$R"
+
+# ── ⑨ 워크트리는 기록이 분리된다 ───────────────────────────────────────────
+R=$(_mkrepo)
+(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me bash "$SCRIPT" claim s >/dev/null 2>&1)
+WT="$R-wt"; git -C "$R" worktree add -q -b wtb "$WT" >/dev/null 2>&1
+if [ -d "$WT" ]; then
+  LANE_OUT=$(cd "$WT" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me bash "$SCRIPT" check 2>&1); rc=$?
+  _lane "⑨ 워크트리는 기록 분리 → 통과" 0 "$rc"
+  git -C "$R" worktree remove --force "$WT" >/dev/null 2>&1
+else echo "  ⚠️  ⑨ 워크트리 생성 실패 — SKIPPED(통과로 세지 않음)"; fi
+rm -rf "$R" "$WT"
+
+# ── ⑩ 서브디렉터리에서도 같은 기록을 본다 (상대 .git 절대화) ───────────────
+R=$(_mkrepo)
+(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me bash "$SCRIPT" claim s >/dev/null 2>&1)
+_plant_peer "$R" x "$PEERPID"; git -C "$R" switch -q -c other; mkdir -p "$R/deep/nested"
+LANE_OUT=$(cd "$R/deep/nested" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me bash "$SCRIPT" check 2>&1); rc=$?
+_lane "⑩ 서브디렉터리에서도 차단" 1 "$rc"
+_ok "⑩-b 기록이 저장소 .git 에만 생성됨" \
+    "$([ -d "$R/.git/fh-claims" ] && [ ! -d "$R/deep/nested/.git" ] && echo 1 || echo 0)"
+rm -rf "$R"
+
+# ── ⑪ release / reap / show 도 앵커가 있다 (B-3 무앵커 경로 수리) ──────────
+R=$(_mkrepo)
+(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me bash "$SCRIPT" claim s >/dev/null 2>&1)
+(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me bash "$SCRIPT" release >/dev/null 2>&1)
+_ok "⑪ release 가 실제로 기록을 지운다" "$([ ! -f "$R/.git/fh-claims/me" ] && echo 1 || echo 0)"
+_plant_peer "$R" x 999999
+(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me bash "$SCRIPT" reap >/dev/null 2>&1)
+_ok "⑪-b reap 이 죽은 세션 기록을 지운다" "$([ ! -f "$R/.git/fh-claims/session-PEER" ] && echo 1 || echo 0)"
+_plant_peer "$R" zzz "$PEERPID"
+LANE_OUT=$(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me bash "$SCRIPT" show 2>&1); rc=$?
+_lane "⑪-c show 가 HEAD·세션·peer 를 낸다" 0 "$rc" "HEAD" "살아있는 peer claim: 1" "zzz"
+rm -rf "$R"
+
+# ── ⑫ 복구 명령의 브랜치명이 shell-quote 된다 (cross-family B-6) ──────────
+#     git ref 는 공백은 못 쓰지만 `;` `$` 는 허용한다. 복붙 시 주입형 사고.
+R=$(_mkrepo); B='a;touch$IFS/tmp/BCLAIM_PWNED'
+git -C "$R" branch "$B" >/dev/null 2>&1 && git -C "$R" switch -q "$B"
+(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me bash "$SCRIPT" claim s >/dev/null 2>&1)
+_plant_peer "$R" x "$PEERPID"; git -C "$R" switch -q main
+LANE_OUT=$(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me bash "$SCRIPT" check 2>&1); rc=$?
+EXPECT="git switch -- '${B}'"
+_lane "⑫ metachar 브랜치명이 인용된 채 출력된다" 1 "$rc" "$EXPECT"
+rm -rf "$R"
+
+# ── ⑬ --if-absent: 없으면 만들고, 있으면 안 덮는다 (세션시작 훅이 부르는 형태) ──
+#     훅 안에 같은 로직을 복제하면 앵커가 안 걸리므로 스크립트에 두고 여기서 잡는다.
+R=$(_mkrepo)
+LANE_OUT=$(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me bash "$SCRIPT" claim --if-absent s 2>&1); rc=$?
+_ok "⑬ --if-absent: 기록 없으면 생성" \
+    "$([ "$rc" = 0 ] && [ -f "$R/.git/fh-claims/me" ] && echo 1 || echo 0)"
+git -C "$R" switch -q -c moved            # 브랜치가 옮겨진 뒤 다시 불러도
+LANE_OUT=$(cd "$R" && FH_CLAIM_TEST=1 FH_CLAIM_SESSION=me bash "$SCRIPT" claim --if-absent s 2>&1); rc=$?
+kept=$(sed -n 's/^branch=//p' "$R/.git/fh-claims/me")
+_lane "⑬-b --if-absent: 기록 있으면 덮지 않는다" 0 "$rc" "이미 있다"
+_ok "⑬-c 기존 값 보존 (main 이어야 함 · 지금=$kept)" "$([ "$kept" = main ] && echo 1 || echo 0)"
+# ★ 이게 중요한 이유: 덮으면 「내가 믿는 브랜치」가 매 세션시작마다 HEAD 로 갱신돼
+#   게이트가 영원히 통과한다 — 자동화가 게이트를 무장해제하는 경로다
+rm -rf "$R"
+
+echo
+echo "[branch-claim] PASS=$PASS  FAIL=$FAIL"
+[ "$FAIL" -eq 0 ] || exit 1