@chrono-meta/fh-gate 3.2.0 → 3.4.0

package/plugins/fh-meta/skills/agent-composer/SKILL.md

@@ -172,7 +172,7 @@ Default composition table by task type.
 | Plugin recommendation | plugin-recommender (S) | — |
 | Install conflict diagnosis | install-doctor (S) | — |
 | Onboarding install | install-wizard (S) — ⚠️ interactive; `--dry-run` for bg parallel | — |
-| Hub PR review | hub-cc-pr-reviewer (S) — requires PR number first | — |
+| Hub PR review | harness-pr-reviewer (S) — requires PR number first | — |
 | **Decision-maker approval review** | apex-review (S) — CTO/tech lead/QA lead personas + HTML deck | — |
 | **Project local skills** | LOCAL_SKILL_REGISTRY lookup → relevant project skill (A/S) | Per project |
 
@@ -360,7 +360,7 @@ After fan-in report, evaluate conditions and auto-suggest the next Wave:
 
 | Condition | Wave suggestion |
 |---|---|
-| ① M-tier > 0 | **Wave next-M**: fact-checker (A) → hub-cc-pr-reviewer (S) |
+| ① M-tier > 0 | **Wave next-M**: fact-checker (A) → harness-pr-reviewer (S) |
 | ② persona-innovator naming candidates > 0 | **Wave next-I**: delegate to user + asset-placement-gate (S) |
 | ③ External absorption signal High > 0 | **Wave next-E**: persona-innovator Mode E (A) + meta-prompt-builder (S) |
 | ⑤ Design conflict / 2+ conflicting suggestions | **Wave next-D**: deliberation (S) — verdict folds back into Step 4-b |

package/plugins/fh-meta/skills/auto-decorrelation/SKILL.md

@@ -229,6 +229,46 @@ format-checked `residency=(CLEAN|TAINTED|NOT_SCANNED)(...)` token on `DEGRADED_*
 `declined`. Fixtures: `scripts/test_marker_crossfamily_lanes.sh` (`r1`–`r13`). This is the SAME
 typed field Step 6 already emits into — one channel, not a second marker line.
 
+## Step 4.6 — `evidence=` : say WHAT the panel received (mandatory with `panel(...)`, 2026-09-12)
+
+`residency=` says the payload was safe to send. `evidence=` says **what was sent** — and that is the
+axis the outside world just measured as the dominant one. `arXiv:2609.10969` (48 task templates →
+2,880 scenarios, **fixed call budget** so the comparison is about the axis and not about spending
+more): a cross-model vote over **shared** evidence approved **62.9 %** of unsafe proposals against
+**22.9 %** with an **independent source** — source effect **40.9 pp** vs **11.3 pp** for model
+diversity, i.e. **3.6×**.
+
+Decide it from **how this run actually dispatched**, not from intent:
+
+| What happened | Token |
+|---|---|
+| Every member got the **same** payload (one prompt file / one diff fanned out) | `evidence=SHARED(<name the artifact>)` |
+| Each member produced its **own** evidence — own checkout, own run, own extraction | `evidence=INDEPENDENT(<what each got>)` |
+| Some of each | `evidence=MIXED(<which member got which>)` |
+
+🟥 **This skill's default flow is `SHARED`, by construction.** Step 4 builds **one** payload and fans
+it out, so a panel dispatched the ordinary way through this skill is the **62.9 % arm** — the axis it
+raises is model family, which the paper prices at 11.3 pp. That is not a reason to stop using it: a
+finder is worth its recall, and this skill's value was never precision
+(`[[feedback_decorrelation_is_a_cheap_finder]]`). It **is** a reason to stop recording that run as if
+it carried the stronger axis. Write `SHARED` and mean it.
+
+🟢 **`SHARED` is a legal, expected answer.** The hook does not block it; it blocks a `panel(...)` that
+does not say which it was, a value outside the closed three, a malformed or duplicated token, and a
+**vacuous body** on `SHARED`/`MIXED` (name the artifact — *"same staged diff"*, *"one findings.jsonl"*,
+*"identical prompt file"*). `INDEPENDENT` is self-describing and is not body-checked, deliberately:
+over-blocking the honest strong answer would train the override.
+
+**Where it lands**: the same grounds line as `residency=`, in the same `crossfamily:` field —
+`crossfamily: panel(codex) — residency=CLEAN(files=3) · evidence=SHARED(same staged diff to both) · R1, 3 findings`.
+Hook: `validate_crossfamily_leg` (grace `EVIDENCE_TOKEN_GRACE_DATE`, no retroactivity).
+Fixtures: `scripts/test_marker_crossfamily_lanes.sh` `e1`–`e10`.
+
+⚠️ **Named gap, not built today**: this skill has **no independent-source mode**. Giving it one
+(each member reconstructs the evidence itself rather than reading the author's payload) is the change
+that would move it onto the 40.9 pp axis; it is a design question, not a wiring one, and it is
+recorded as a signal rather than improvised here.
+
 🟥 **A stripped file is invisible to the reviewer, and a reviewer's default read of invisible is
 "absent," not "redacted"** (governor dogfood, 2026-09-05, same-day live use of this Step): two
 TAINTED files were stripped from a real payload and the CLEAN remainder sent cross-family — the

package/plugins/fh-meta/skills/frontier-digest/SKILL.md

@@ -215,7 +215,7 @@ Present Step 4 menu options [1]–[5]. Do not skip to [5] silently — surface t
 ## Simplification Guards
 
 - Video Tier-3 probe fails (any of `yt-dlp` / `curl_cffi` / `ffmpeg` missing, or timedtext returns 429) → fall through to operator summary; never assume `yt-dlp` works
-- If 3+ arxiv queries fail (HTTP 429): back off once → WebFetch the date-sorted `arxiv.org/list/cs.SE/recent` listing → only then HN-only. Never substitute WebSearch (recall channel, 5/5 REPEATs measured 2026-09-04); report `arxiv FAILED (429)`, never `0 items`. Detail: `SKILL_detail.md §Execution form`
+- 🟢 **arxiv transport, inverted 2026-09-12 (operator decision, condition met: 429 on 09-09·10·11·12)**: the **date-sorted `arxiv.org/list/cs.SE/recent` listing is PRIMARY**; the export API is the **fallback**; HN-only only if both fail. Same sort axis (submission date) is why the listing is promotable and WebSearch is not. 🟥 Cost of the promotion, not an oversight: the listing's ID↔title pairing is the weaker instrument, so **per-item `abs/{id}` re-resolution is now a PRIMARY-path requirement** and the progress line must name which transport produced the items. Never substitute WebSearch (recall channel, 5/5 REPEATs measured 2026-09-04); report `arxiv FAILED (429)`, never `0 items`. 🟥 **On the listing path, pair ID↔title INSIDE one list entry, never by zipping two ordered lists — measured 2026-09-12: 51 IDs vs 50 titles, so pairs drift partway down and mispair while looking well-formed (3 items caught, 0 shipped). Until that is what happened, per-item `abs/{id}` re-resolution is MANDATORY and a title mismatch DROPS the item.** Detail: `SKILL_detail.md §Execution form`
 - On curl timeout, skip that item and continue with the rest
 - If synthesis result exceeds 400 characters, retain top 3 items and truncate the rest
 - Without `--save`, do not create files (conversation output only)

package/plugins/fh-meta/skills/frontier-digest/SKILL_detail.md

@@ -28,14 +28,52 @@ load: on-demand
 > fell back to **WebSearch**, and the 09-04 run measured what that does: 5/5 papers it returned were
 > REPEATs. Search sorts by *canonicity*, the export API by *submission date* — a search fallback is
 > a **recall channel, not a discovery channel**, and swapping it in silently converts «unrun» into
-> «nothing new» (`not found ≠ 0`). Order on 429:
-> 1. back off once (≥30s), retry the same query;
-> 2. still 429 → WebFetch the **date-sorted HTML listing** `https://arxiv.org/list/cs.SE/recent`
+> «nothing new» (`not found ≠ 0`).
+>
+> 🟢 **TRANSPORT ORDER INVERTED 2026-09-12 (operator decision) — the listing is now PRIMARY.**
+> Condition stated by the operator was *«if the errors keep coming»*, and they did, measurably:
+> `429` appears in the digest record on **09-09 · 09-10 · 09-11 · 09-12 — four consecutive days**,
+> past the `N≥3` bar twice over. Paying two failed calls plus a backoff every single day to reach
+> items that the listing reaches anyway is not a fallback, it is a toll. New order:
+> 1. **PRIMARY — WebFetch the date-sorted HTML listing** `https://arxiv.org/list/cs.SE/recent`
 >    (and `https://arxiv.org/list/cs.AI/recent` if the first is empty of agent/harness items), keep
->    items whose title/abstract match the three query phrases, cap 6 — same sort axis as the API;
-> 3. only if that also fails → HN-only, and the progress line says `arxiv FAILED (429)`, never `0 items`.
+>    items whose title/abstract match the three query phrases, cap 6. **Same sort axis as the API**
+>    (submission date) — that property is *why* this one is promotable and WebSearch is not.
+> 2. **FALLBACK — the export API query** (back off ≥30s between attempts). Kept on the ladder on
+>    purpose: if arXiv redesigns the listing markup, the channel must not disappear with it.
+> 3. only if both fail → HN-only, and the progress line says `arxiv FAILED (<which transports, why>)`,
+>    never `0 items`.
+>
+> 🟥 **What this costs, stated rather than discovered later.** The listing path has the **weaker
+> instrument** — its ID↔title pairing is the defect documented immediately below, and promoting it
+> moves that defect from the fallback onto the **main** path. Therefore the two rules below are no
+> longer conditional-on-being-in-fallback: **per-item `abs/{id}` re-resolution is a PRIMARY-path
+> requirement**, one fetch per shipped ID, and a title mismatch drops the item. That is a real
+> per-run cost increase (≈N extra fetches for N shipped items) and it is the price of the promotion,
+> not an oversight. The old order paid 2 failed calls + a backoff instead; this pays N verified reads.
+> 🟥 The progress line must now name **which transport produced the items** (`arxiv via listing` /
+> `arxiv via export-api`) — otherwise a reader cannot tell which instrument's limits apply to the run.
 > 🟥 WebSearch is **not** on this ladder. If a run used it anyway, the arxiv leg is reported as
 > `RECALL-ONLY (WebSearch)` and its items are excluded from the NEW/REPEAT count.
+>
+> 🟥 **On the listing path, do NOT pair ID and title by position — pair them inside one block
+> (measured 2026-09-12, this runner, and it is the phantom class this skill already has on record).**
+> The listing yielded **51 IDs and 50 titles**, so two parallel extractions drift partway down and
+> every pair after the drift point is wrong *while looking well-formed*. Concretely measured that run:
+> `2609.10550` was attached to *"When Passing Tests Hides Vulnerabilities"* by the positional parse,
+> but its own `abs` page is *"Optimizing AI Inference Across the Deployment Stack"* (2026-07-01);
+> `2609.11060` and `2609.11008` mispaired the same way. 3 items dropped, 7 verified, **0 shipped
+> unverified** — it was caught only because every shipped ID was re-resolved.
+> **Two rules, and the second is the floor:**
+> ① read each entry as **one unit** (the ID and the title that sit in the *same* list item), never as
+>   two ordered lists zipped together. A count mismatch between the lists is not a warning to
+>   reconcile — it is proof the zip is already wrong.
+> ② until ① is demonstrably what happened, **per-item `abs/{id}` re-resolution is MANDATORY on this
+>   path**, not optional — one fetch per shipped ID, confirming the title. Any ID whose `abs` title
+>   disagrees is **dropped**, never shipped with a note.
+> ⚠️ There is no hook here and none is possible: the parse happens inside the session that read the
+> page, so this is salience over a manual floor. The floor that actually held on 2026-09-12 was ② —
+> keep it even after ① looks solved (`[[feedback_anchor_can_be_decorative]]`).
 
 ### HackerNews (Algolia API)
 

package/plugins/fh-meta/skills/{hub-cc-pr-reviewer → harness-pr-reviewer}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: hub-cc-pr-reviewer
+name: harness-pr-reviewer
 description: Checks a submitted PR against the environment's baseline assets (CLAUDE.md, memory, naming, asset classification) and attaches a review comment with a merge recommendation. 5 steps — diff read, 8-area consistency check, self-catch, comment, merge recommendation.
 user-invocable: true
 allowed-tools: ["Bash", "Read", "Grep", "Glob"]
@@ -15,13 +15,21 @@ complexity_routing:
 
 > **Note:** The original developer is the forge-harness original developer (development source + meta-monitoring home). In external user install environments, the install environment user themselves is the baseline integrity gate operator (following path B generalization baseline / `SKILL_detail.md §External User Environment Adaptation Path` §).
 
-# hub-cc-pr-reviewer — Hub Gate Operation Rule Automation
+# harness-pr-reviewer — Hub Gate Operation Rule Automation
 
 When a PR is submitted, checks consistency against the user environment's baseline assets (CLAUDE.md · memory · naming · asset classification) and attaches a review comment. 5-step: diff read → 8-matrix check → self-catch → comment attachment → merge recommendation.
 
 ## Activation Triggers
 
-1. **PR #N input**: *"Review PR #N"* / *"Check PR #N"* / *"hub review"* / *"baseline consistency check"*
+> **Renamed from `hub-cc-pr-reviewer` (2026-09-12, operator decision).** The old name said where it
+> was born (the hub's own cc reviewing its own PRs). What it actually is — measured on qasp/pmh PRs in
+> 2026-09 — is the **standalone doorway through which a field harness verifies its own submitted PR
+> with FH's review capability**. Old-name utterances ("hub-cc-pr-reviewer", "hub review", "hub cc
+> review") still route here; downstream forks that carry the old directory name (PMH) keep working
+> until they sync. No redirect stub directory is shipped (same policy as `phantom-quench`).
+
+
+1. **PR #N input**: *"Review PR #N"* / *"Check PR #N"* / *"hub review"* (old-name alias) / *"harness PR review"* / *"baseline consistency check"*
 2. **Action leader cc → hub sync point**: Large decision area PR catch (following Option C Hybrid policy — memory creation / CLAUDE.md change / CATALOG round / skill v0.x evolution / policy change / asset synergy branch judgment)
 3. **Hub cc session entry**: Layer A auto-read recent external commit catch (auto-discover new PRs)
 
@@ -75,6 +83,54 @@ Self-precision catch areas after first cc review (following previous PR self-cat
 
 Self-catch areas 0 items = skip this entire catch matrix — do not pad with token-filling to make the section look populated.
 
+🟥 **Self-catch is a CUE, not a verdict.** Its output is the *input* to Step 3.5 below. A self-catch
+that finds nothing does not clear Axis 2 or Axis 3 — measured 2026-09-08/11: a reviewer session with
+no external cue ran the load-bearing gate **0/51**, and a PMH session reviewing qasp PR #13 dispatched
+the cross-family panel only after the operator pushed (pmh-dev #77). The self-check *is* the reviewer;
+it cannot be its own decorrelation.
+
+### Step 3.5. Axis 2 · Axis 3 — mandatory dispatch lane (mechanical trigger, typed degrade)
+
+Axis 1 above is wired at mandatory strength (`--pr` mode, typed verdict). Until 2026-09-12 Axis 2
+(adversarial panel) and Axis 3 (phantom-quench) had **no dispatch block in this skill at all** — only
+the self-catch matrix — so they fired only when someone said so. This step closes that with a trigger
+that is decided from the PR, never from the reviewer's feel.
+
+**Trigger — mandatory if ANY of these holds** (compute all three; record which fired):
+
+```
+(i)   Step 2 matrix has ≥1 ❌  (Inconsistent)
+(ii)  the PR touches a load-bearing FH asset: SKILL.md · SKILL_detail.md · .claude/rules/*.md ·
+      knowledge/shared/rules/*.md · templates/** · scripts/**/*.sh · scripts/**/*.py ·
+      plugins/*/agents/**   (same list as CLAUDE.md §FH Improvement 4-Axis Auto-Gate)
+      → gh pr diff "$PR" --name-only | grep -E '(^|/)SKILL(_detail)?\.md$|^\.claude/rules/|^knowledge/shared/rules/|^templates/|^scripts/.*\.(sh|py)$|^plugins/[^/]+/agents/'
+(iii) a merge recommendation (Step 5) will be issued for this PR
+```
+
+None of the three → record `axis2: not-triggered(reason)` · `axis3: not-triggered(reason)` in the
+comment capsule and continue. This is the *only* non-run path, and it is stated, never silent.
+
+**Axis 2 — cross-family adversarial panel.** Dispatch **`auto-decorrelation`** on the PR diff (reuse,
+not a new engine — its Step 1 load-bearing predicate, Step 4.5 residency screen and Step 6 degrade
+ladder all apply unchanged). What this step owns is only the *decision to dispatch*. The result lands
+as the typed `crossfamily:` value: `panel(<families>)` with the source-grounded findings, or one of
+`declined` · `DEGRADED_SINGLE_FAMILY` · `DEGRADED_PANEL_UNUSED` · `UNKNOWN` **with grounds** — e.g.
+consent OFF, no different-family sidecar reachable, quota exhausted. A degrade value is allowed; an
+*absent* value is not. 🟥 A judgment-type question put to the panel (by-design vs fail-open, is this
+a regression) needs **reps ≥ 3**; a 1-of-3 split is recorded as *unresolved*, never as CONCUR
+(`field_verdict_crossfamily_gate.md` §4-2).
+
+**Axis 3 — phantom-quench.** Run `/phantom-quench` over the PR's changed documentation surfaces
+(any `*.md` in the diff, plus every path/citation the PR body asserts). Mechanical N/A only when
+`gh pr diff --name-only` has zero `*.md` files **and** the PR body cites no path — record
+`axis3: N/A(no doc surface)`. A phantom finding is a ❌ in the comment capsule, and it flips the Step 5
+recommendation the same way an Axis 1 M-tier block does.
+
+**Degrade direction.** This is a review surface (reversible): tooling-down does not block the
+*comment*, but the merge recommendation must carry the degrade value verbatim and read
+**NOT-CONVERGED** while Axis 2 is a `DEGRADED_*`/`UNKNOWN` value on a load-bearing PR. Silent
+same-family pass is the one outcome this step forbids.
+
 ### Step 4. Review Comment Attachment
 
 **Mandatory before any `gh pr comment`: run `/public-surface-audit` over the composed comment text.**
@@ -176,6 +232,22 @@ All 5 Steps completed
     passes; they mean Axis 1 did not examine this PR and the recommendation
     may not cite it as green
 
++ Step 3.5 trigger computed from the PR (matrix ❌ count · load-bearing path
+  grep · merge-recommendation requested) and recorded with which clause fired
+  — measured: the three booleans appear in the comment capsule. Absent = the
+    step did not run, which is the pre-2026-09-12 defect (pmh-dev #77)
+
++ Axis 2 dispatched via auto-decorrelation when triggered, landing a typed
+  `crossfamily:` value (panel(...) or a DEGRADED_*/UNKNOWN value WITH grounds)
+  — mandatory-pass: the value exists and is one of the closed enum. A
+    load-bearing PR whose value is DEGRADED_*/UNKNOWN leaves the merge
+    recommendation NOT-CONVERGED; judgment-type panel questions carry reps ≥ 3
+    or are recorded unresolved
+
++ Axis 3 phantom-quench run over the PR's doc surfaces when triggered, or
+  N/A(no doc surface) decided by `--name-only` grep, never by feel
+  — mandatory-pass: a phantom finding is a ❌ that flips the recommendation
+
 + /public-surface-audit run over the composed comment text BEFORE any
   gh pr comment
   — mandatory-pass, fail-closed: CLEAN attaches; REVIEW/LEAK redact-and-rescan;

package/plugins/fh-meta/skills/{hub-cc-pr-reviewer → harness-pr-reviewer}/SKILL_detail.md

@@ -1,6 +1,6 @@
 ---
-name: hub-cc-pr-reviewer-detail
-description: On-demand detail for hub-cc-pr-reviewer — step bash commands, comment template, sister-asset utilization, external-environment adaptation, disable path, and persona synergy handling. Read when executing a step or operating in an external/own-PRS/deep-insight environment.
+name: harness-pr-reviewer-detail
+description: On-demand detail for harness-pr-reviewer — step bash commands, comment template, sister-asset utilization, external-environment adaptation, disable path, and persona synergy handling. Read when executing a step or operating in an external/own-PRS/deep-insight environment.
 load: on-demand
 ---
 

package/plugins/fh-meta/skills/harvest-loop/SKILL_detail.md

@@ -35,7 +35,7 @@ Meaning of isolation: The Critic reads the synthesizer conclusion but does not i
 - FAIL after re-synthesis → auto-persist as `fh_signal` on hold (no additional retries)
 - Maximum retries: **1**
 
-**Post-Core-Skill Critic Verdict Connection**: Following core skills can have Critic called inline after completion: harness-doctor · verify-bidirectional · hub-cc-pr-reviewer · context-doctor · sim-conductor. Trigger: immediately after completion announcement + "steel-quench" / "re-validate" / "run Critic" utterance.
+**Post-Core-Skill Critic Verdict Connection**: Following core skills can have Critic called inline after completion: harness-doctor · verify-bidirectional · harness-pr-reviewer · context-doctor · sim-conductor. Trigger: immediately after completion announcement + "steel-quench" / "re-validate" / "run Critic" utterance.
 
 ---
 
@@ -150,7 +150,7 @@ grep -rl "complexity_routing" plugins/*/skills/*/SKILL.md
 
 # 2. Aggregate escalation records from fh_signal files
 grep -rh "" tracks/_meta/fh_signal_*.md 2>/dev/null | \
-  grep -oE "(harness-doctor|verify-bidirectional|hub-cc-pr-reviewer|context-doctor|sim-conductor|agent-composer|harvest-loop|steel-quench)" | \
+  grep -oE "(harness-doctor|verify-bidirectional|harness-pr-reviewer|context-doctor|sim-conductor|agent-composer|harvest-loop|steel-quench)" | \
   sort | uniq -c | sort -rn
 ```
 

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

@@ -169,7 +169,7 @@ grep -i -n "pr\|pull request\|audit\|review\|weekly" CLAUDE.md 2>/dev/null | hea
 ```
 
 Judgment:
-- Existing PR convention present → possible priority conflict with `hub-cc-pr-reviewer` ⚠️
+- Existing PR convention present → possible priority conflict with `harness-pr-reviewer` ⚠️
 - Existing weekly audit present → possible format conflict with `harvest-loop` ⚠️
 
 ### 2-2. Skill Trigger Conflicts

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

@@ -322,7 +322,7 @@ Only activate the cluster matching the utterance — loading all skills degrades
 | **A — Harvest/Evolution** | harvest · session wrap-up · pattern · reverse absorption · fh evolution | field-harvest · harvest-loop · contention-layer · verify-bidirectional |
 | **B — Diagnosis (doctor)** | diagnose · health · check · inspect · token waste · install conflict · doctor | harness-doctor · context-doctor · sim-conductor · install-doctor · install-wizard |
 | **C — Compose (composer)** | agent composition · parallel · compose prompt · context card | agent-composer · meta-prompt-builder |
-| **D — Audit/Review** | review · audit · PR review · steel quench · adversarial · lint · placement | hub-cc-pr-reviewer · steel-quench · apex-review · harness-doctor (--lint) · marketplace-gate · asset-placement-gate |
+| **D — Audit/Review** | review · audit · PR review · steel quench · adversarial · lint · placement | harness-pr-reviewer · steel-quench · apex-review · harness-doctor (--lint) · marketplace-gate · asset-placement-gate |
 | **E — Explore/Frontier** | trends · plugin recommendation · synergy · frontier | frontier-digest · plugin-recommender · cross-ecosystem-synergy-detection |
 | **F — Common (always-on)** | — | convergence-loop · deliberation (fh-commons) |
 

package/plugins/fh-meta/skills/meta-prompt-builder/SKILL.md

@@ -53,7 +53,7 @@ When Goal is provided in natural language (e.g., "I need to report to the team l
 | "analyze", "diagnose", "something seems off" | harness-doctor → context-doctor | Structural + contextual diagnosis simultaneously |
 | "simulate", "validate", "meta" | sim-conductor (D-code or Area B) | Multi-perspective validation |
 | "install", "setup", "onboarding" | plugin-recommender → install-wizard | Recommend then install |
-| "review", "code check" | sim-conductor D-code → hub-cc-pr-reviewer | Code review chain |
+| "review", "code check" | sim-conductor D-code → harness-pr-reviewer | Code review chain |
 
 Output format:
 ```

package/plugins/fh-meta/skills/pipeline-conductor/SKILL.md

@@ -246,7 +246,7 @@ Resume is scope-bound — the scope from Step 0 is preserved across resume calls
 After a `CLEAN (--full)` or `PENDING` sweep, the following are natural follow-ons:
 
 - `field-harvest` — harvest patterns surfaced during the sweep
-- `hub-cc-pr-reviewer` — if sweep was run pre-PR, feed results into PR review
+- `harness-pr-reviewer` — if sweep was run pre-PR, feed results into PR review
 - `agent-composer` — if multiple fix tasks are needed across the Pending list, compose agents to resolve them in parallel
 - `return-path-gate --all` — if Step 0.5 surfaced OPEN chains, run a full chain closure audit
 

package/plugins/fh-meta/skills/plugin-recommender/SKILL.md

@@ -98,7 +98,7 @@ When queried for a specific capability (e.g., "adversarial reviewer for bash cod
 ⚠️ **A failed or empty discovery lane is NOT "no candidates".** Both CLIs above list only *configured* marketplaces, and a non-zero exit / empty array means the lane did not answer — not that nothing exists. Report each lane's state explicitly (`EXECUTED` / `EMPTY` / `FAILED: <stderr>`) and never render a `FAILED` lane as a zero result; a lane that could not run must be re-run or replaced by the web-search fallback (Priority 3) before you tell the user nothing was found.
 
 **Discovery priority**: built-in (Tier 0) > installed > FH native > Tier 1 (any platform) > Tier 2 > Tier 3 > Tier 4
-**Tier 0 guard**: FH native wins over a built-in only when the FH skill adds governance the built-in lacks (e.g. `/goal` → `goal-quench` adds budget+quality gates; code diff review stays with built-in `/code-review`, FH-asset coherence with `hub-cc-pr-reviewer`)
+**Tier 0 guard**: FH native wins over a built-in only when the FH skill adds governance the built-in lacks (e.g. `/goal` → `goal-quench` adds budget+quality gates; code diff review stays with built-in `/code-review`, FH-asset coherence with `harness-pr-reviewer`)
 
 **When sim-conductor chains here for persona discovery**: apply the same platform-aware search scoped to persona/simulation/review capability tags. Return discovered agents with their Tier rating so sim-conductor can decide whether to install or use a built-in brief.
 

package/plugins/fh-meta/skills/sim-conductor/SKILL.md

@@ -542,7 +542,7 @@ Verdicts: PASS · CONDITIONAL_PASS (S/R only, or Area B cadence skip) · FAIL (M
 
 ## Operations Notes
 
-**AI-AI Loop Bias Defense**: sim-conductor → hub-cc-pr-reviewer → sim-conductor loop shares LLM cognitive blind spots. Internal convergence is "provisional convergence" — elevated only by external review or human gate. Area A/B convergence without human gate = incomplete.
+**AI-AI Loop Bias Defense**: sim-conductor → harness-pr-reviewer → sim-conductor loop shares LLM cognitive blind spots. Internal convergence is "provisional convergence" — elevated only by external review or human gate. Area A/B convergence without human gate = incomplete.
 
 ---
 

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

@@ -1,6 +1,6 @@
 {
   "name": "fh-qp",
-  "version": "3.2.0",
+  "version": "3.4.0",
   "engines": {
     "claudeCode": ">=1.0.0"
   },