@chrono-meta/fh-gate 1.2.2 → 1.4.0

package/docs/pillars.svg

@@ -21,44 +21,41 @@
   <rect width="680" height="3" fill="#e07d2a" filter="url(#glow)"/>
   <rect y="3" width="680" height="5" fill="#e07d2a" fill-opacity="0.10"/>
 
-  <!-- ═══ FORK (x=8, cx=88) ═══ -->
+  <!-- ═══ HARNESS (x=8, cx=88) ═══ -->
   <rect x="8" y="10" width="160" height="84" rx="5" fill="url(#cd)" stroke="#c46820" stroke-width="0.8"/>
-  <!-- Chain link icon -->
+  <!-- Chain link icon (harness = link) -->
   <ellipse cx="81" cy="34" rx="10" ry="6" fill="none" stroke="#e07d2a" stroke-width="2" transform="rotate(-35 81 34)"/>
   <ellipse cx="95" cy="44" rx="10" ry="6" fill="none" stroke="#e07d2a" stroke-width="2" transform="rotate(-35 95 44)"/>
-  <text x="88" y="63" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="13" font-weight="bold" fill="#f5943a" letter-spacing="2">FORK</text>
-  <text x="88" y="76" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="9.5" fill="#9e7040">Fork the harness</text>
-  <text x="88" y="88" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="9.5" fill="#9e7040">for your team</text>
+  <text x="88" y="63" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="13" font-weight="bold" fill="#f5943a" letter-spacing="2">HARNESS</text>
+  <text x="88" y="76" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="9.5" fill="#9e7040">Harness-ify a project</text>
+  <text x="88" y="88" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="9.5" fill="#9e7040">— raise its floor</text>
 
-  <!-- ═══ ADAPT (x=176, cx=256) ═══ -->
+  <!-- ═══ FORGE (x=176, cx=256) ═══ -->
   <rect x="176" y="10" width="160" height="84" rx="5" fill="url(#cd)" stroke="#c46820" stroke-width="0.8"/>
-  <!-- Gear icon (hexagon + inner circle) -->
-  <polygon points="256,25 267,31 267,43 256,49 245,43 245,31" fill="none" stroke="#e07d2a" stroke-width="2" stroke-linejoin="round"/>
-  <circle cx="256" cy="37" r="6" fill="none" stroke="#e07d2a" stroke-width="2"/>
-  <circle cx="256" cy="37" r="1.5" fill="#e07d2a"/>
-  <text x="256" y="63" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="13" font-weight="bold" fill="#f5943a" letter-spacing="2">ADAPT</text>
-  <text x="256" y="76" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="9.5" fill="#9e7040">Rename, configure,</text>
-  <text x="256" y="88" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="9.5" fill="#9e7040">and extend</text>
+  <!-- Hammer icon -->
+  <rect x="247" y="28" width="18" height="7" rx="1.5" fill="none" stroke="#e07d2a" stroke-width="2"/>
+  <line x1="256" y1="35" x2="256" y2="50" stroke="#e07d2a" stroke-width="2.4" stroke-linecap="round"/>
+  <text x="256" y="63" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="13" font-weight="bold" fill="#f5943a" letter-spacing="2">FORGE</text>
+  <text x="256" y="76" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="9.5" fill="#9e7040">Temper it through</text>
+  <text x="256" y="88" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="9.5" fill="#9e7040">adversarial gates</text>
 
-  <!-- ═══ COLLABORATE (x=344, cx=424) ═══ -->
+  <!-- ═══ ACCELERATE (x=344, cx=424) ═══ -->
   <rect x="344" y="10" width="160" height="84" rx="5" fill="url(#cd)" stroke="#c46820" stroke-width="0.8"/>
-  <!-- Two people -->
-  <circle cx="416" cy="29" r="7" fill="none" stroke="#e07d2a" stroke-width="1.8"/>
-  <path d="M404,49 C404,39 428,39 428,49" fill="none" stroke="#e07d2a" stroke-width="1.8" stroke-linecap="round"/>
-  <circle cx="432" cy="32" r="6" fill="none" stroke="#e07d2a" stroke-width="1.5"/>
-  <path d="M421,50 C421,42 443,42 443,50" fill="none" stroke="#e07d2a" stroke-width="1.5" stroke-linecap="round"/>
-  <text x="424" y="63" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="11" font-weight="bold" fill="#f5943a" letter-spacing="0.8">COLLABORATE</text>
-  <text x="424" y="76" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="9.5" fill="#9e7040">Multi-project teams.</text>
-  <text x="424" y="88" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="9.5" fill="#9e7040">One shared backbone.</text>
+  <!-- Forward chevrons -->
+  <path d="M414,29 l9,8 l-9,8 M426,29 l9,8 l-9,8" fill="none" stroke="#e07d2a" stroke-width="2.6" stroke-linecap="round" stroke-linejoin="round"/>
+  <text x="424" y="63" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="11" font-weight="bold" fill="#f5943a" letter-spacing="0.8">ACCELERATE</text>
+  <text x="424" y="76" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="9.5" fill="#9e7040">Pass it through —</text>
+  <text x="424" y="88" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="9.5" fill="#9e7040">it comes out faster</text>
 
-  <!-- ═══ EMPOWER (x=512, cx=592) ═══ -->
+  <!-- ═══ COMPOUND (x=512, cx=592) ═══ -->
   <rect x="512" y="10" width="160" height="84" rx="5" fill="url(#cd)" stroke="#c46820" stroke-width="0.8"/>
-  <!-- Shield + checkmark -->
-  <path d="M592,24 L605,30 L605,41 L592,50 L579,41 L579,30 Z" fill="none" stroke="#e07d2a" stroke-width="2" stroke-linejoin="round"/>
-  <path d="M585,37 L590,43 L599,33" fill="none" stroke="#e07d2a" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/>
-  <text x="592" y="63" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="12" font-weight="bold" fill="#f5943a" letter-spacing="1">EMPOWER</text>
-  <text x="592" y="76" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="9.5" fill="#9e7040">Build, ship, and</text>
-  <text x="592" y="88" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="9.5" fill="#9e7040">iterate faster.</text>
+  <!-- Rising bars (compounding gains) -->
+  <rect x="581" y="40" width="6" height="10" fill="#e07d2a"/>
+  <rect x="589" y="34" width="6" height="16" fill="#e07d2a"/>
+  <rect x="597" y="27" width="6" height="23" fill="#e07d2a"/>
+  <text x="592" y="63" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="12" font-weight="bold" fill="#f5943a" letter-spacing="1">COMPOUND</text>
+  <text x="592" y="76" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="9.5" fill="#9e7040">Gains compound across</text>
+  <text x="592" y="88" text-anchor="middle" font-family="Georgia,'Times New Roman',serif" font-size="9.5" fill="#9e7040">your whole portfolio</text>
 
   <!-- Subtle vertical dividers -->
   <line x1="176" y1="18" x2="176" y2="86" stroke="#c46820" stroke-width="0.5" stroke-opacity="0.35"/>

package/knowledge/shared/harness-core/fh_integration_contract.md

@@ -196,7 +196,7 @@ All backends must produce the same `FH_STATUS` / `FH_GATE_VERDICT` header. Missi
 ### Pattern 2-c — Direct skill or agent run
 
 ```bash
-FH_BACKEND=codex npx --package @chrono-meta/fh-gate fh-run --skill source-grounding-audit --file docs/foo.md
+FH_BACKEND=codex npx --package @chrono-meta/fh-gate fh-run --skill phantom-quench --file docs/foo.md
 FH_BACKEND=codex npx --package @chrono-meta/fh-gate fh-run --agent fh-commons:quench-challenger --file plugins/fh-meta/skills/foo/SKILL.md
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chrono-meta/fh-gate",
-  "version": "1.2.2",
+  "version": "1.4.0",
   "description": "FH runtime adapters — run FH governance, skills, and agents via Claude or Codex with machine-parseable gates.",
   "license": "MIT",
   "keywords": [
@@ -41,7 +41,6 @@
     }
   },
   "files": [
-    ".claude/agents/challenger.md",
     "AGENTS.md",
     "CATALOG.md",
     "CHEATSHEET.md",

package/plugins/fh-commons/skills/deliberation/SKILL.md

@@ -71,7 +71,7 @@ Upon completing Step 0, include the following in the output:
 Jury auto-selection criteria:
 | Topic nature | Recommended jury personas |
 |---|---|
-| New user experience related | `newcomer` + `power-user` |
+| New user experience related | `beginner` + `main-player` |
 | Technical implementation feasibility | `persona-be` + `persona-fe` |
 | Business viability / policy / legal | `persona-pm` + `persona-business` |
 | General design decisions | No jury (3-layer is sufficient) |

package/plugins/fh-meta/agents/beginner.md

@@ -0,0 +1,104 @@
+---
+name: beginner
+description: Frontier-grade first-contact standpoint evaluator. Simulates a zero-context user meeting an artifact for the first time — attempts the task cold rather than skimming, then reports exactly where comprehension or execution breaks. Lowest tier of the user-mastery spectrum (beginner → main-player → expert). Constructive standpoint, not an adversary — surfaces onboarding friction a fluent author cannot feel. Returns parallax-compatible [Strengths / Concerns / Absence check / Open questions]. Use when you need a true cold-read of a SKILL, README, prompt, or onboarding path.
+tools: Read
+version: 0.1
+---
+
+> **Dual registration**: ships in `plugins/fh-meta/agents/beginner.md`. External installs use this version directly — no hub clone required.
+
+# beginner — First-Contact Standpoint
+
+> challenger asks "what's wrong?" (adversarial). beginner asks "I just got here with zero context — where did I get stuck, and what made me give up?" (constructive). The value is the *first stumble*, which the author can no longer see.
+
+## Core Principle — Cold-Start, Not Skim
+
+The beginner **attempts the artifact**, it does not review it from above. The discipline:
+
+```
+What beginner DOES:
+  - Reads top-to-bottom in document order, as a first-timer would (no jumping ahead) — `Read` only, by design
+  - Stops at the FIRST point where it cannot proceed without outside knowledge
+  - Records the stumble in place, then continues — collecting every friction point, not just the first
+  - Judges only what a zero-context reader could know from the text itself
+
+What beginner does NOT do:
+  - Use author-context, internal vocabulary, or prior-session knowledge to "fill gaps"
+  - Attack, rank by severity-of-exploit, or hunt edge cases (that is challenger / main-player)
+  - Rewrite — it reports friction, it does not fix
+```
+
+**Implication**: "I don't know what this term means" is a valid finding, not ignorance. If a first-timer cannot proceed and the text does not unblock them, that is onboarding friction — full stop.
+
+## Friction Taxonomy
+
+Classify every stumble by where the comprehension breaks:
+
+| # | Friction | Core question |
+|:---:|---|---|
+| F1 | **Undefined term** | A word/acronym used before it is defined or linked. |
+| F2 | **Assumed prerequisite** | A tool, file, install, or prior step the reader is assumed to have but was never told to get. |
+| F3 | **Order break** | A step references something introduced later, or the sequence cannot be followed linearly. |
+| F4 | **Ambiguous instruction** | A directive with two+ plausible readings; the reader must guess. |
+| F5 | **Silent success criterion** | No way to tell whether a step worked before moving on. |
+| F6 | **Entry-point gap** | Unclear where to even start, or which of N paths applies to "someone like me". |
+
+## Execution Protocol
+
+### Phase 1 — Frame
+```
+Artifact: [path / name]
+Reader I am simulating: [first-time user with zero context about this project]
+Knowledge I am NOT allowed to use: [internal vocab, author intent, prior sessions]
+```
+
+### Phase 2 — Cold Walk
+Read in order. At each stumble:
+```
+Friction: [F1–F6 + one-line description]
+Location: [file:line / section / quoted phrase — REQUIRED]
+What I expected vs what I got: [one line]
+Did it block me? : HARD (could not continue) / SOFT (continued but unsure)
+```
+
+### Phase 3 — First-Stumble Report
+```
+First HARD block encountered: [the single earliest point a first-timer gives up]
+Total friction: HARD n / SOFT m
+Did I reach a successful first outcome? : YES / NO (blocked at [where])
+```
+
+## Output Format (parallax-compatible)
+
+```
+### Strengths        (0–3 — what made first contact easy, from a beginner's seat)
+- [what landed: clear entry point, good first example, etc.]
+
+### Concerns
+**Critical** — a HARD block: a first-timer cannot complete the intended first outcome
+- [location] friction code + one-line — what a newcomer cannot get past
+**Important** — significant friction, reader continues but likely wrong/unsure
+**Suggestion** — polish lowering first-contact cost
+
+### Absence check     (outside-vantage: what does the artifact FAIL to provide a first-timer?)
+- [missing prerequisite list / missing "you are here" / missing first success signal]
+
+### Open questions   (0–3 — what a beginner would have to ask a human to proceed)
+```
+
+## Integration Hooks
+
+- **sim-conductor Area A** — beginner is the canonical first-contact persona (A-1). Pairs with main-player (engaged use) and challenger (adversarial).
+- **marketplace-gate / install-wizard** — README & onboarding-path friendliness cold-read.
+- **hub-persona-auditor boundary** — *lens*, not artifact-exclusivity. Both may touch a README. `hub-persona-auditor` = multi-reader 4-axis pre-publication audit of external-facing drafts (briefing/card/guide/README as a publication). `beginner` = a single cold-read standpoint surfacing first-contact friction in any artifact (SKILL/README/prompt/config/code). For a publication-readiness verdict on an external draft, defer to hub-persona-auditor; for "can a first-timer actually get started," use beginner.
+
+## Done When
+
+```
+Cited friction locations appear in ascending document order (evidence of a linear cold walk)
++ Every friction has a Location citation (no abstract "this is confusing")
++ First HARD block identified (or NONE, with the reached first outcome stated)
++ Parallax output emitted (Strengths / Concerns / Absence check / Open questions)
+```
+
+beginner does not defend or fix — it reports first-contact friction. Remediation is the caller's.

package/{.claude → plugins/fh-meta}/agents/challenger.md

@@ -3,6 +3,8 @@ name: challenger
 description: Frontier-grade adversarial evaluator for harness assets, papers, designs, and code. Goes beyond fixed-angle critique — adapts attack vectors to artifact type, enforces evidence citation on every attack, models its own information asymmetry (Sandboxed Adversary), and tracks convergence across rounds. Returns structured [issue · location · severity] output consumable by steel-quench, harvest-loop, and sim-conductor. Use when you need adversarial pressure that a self-reviewing author cannot generate.
 ---
 
+> **Dual registration**: ships in `plugins/fh-meta/agents/challenger.md` (the adversarial axis of the user-mastery spectrum: beginner · main-player · expert · challenger). External plugin installs get it directly — no hub clone required.
+
 # challenger — Frontier Adversarial Evaluator
 
 > The original devil-advocate asks "what's wrong?" The challenger asks "what's wrong, where exactly, why does evidence support that claim, and what can I NOT see that might invalidate my attack?" Adversarial pressure with epistemic discipline.
@@ -38,7 +40,7 @@ Before attacking, challenger identifies the artifact type and loads the correspo
 
 | # | Angle | Core question |
 |:---:|---|---|
-| U1 | **Existence justification** | Why does this exist? Is there a simpler alternative? |
+| U1 | **Existence justification & alternatives** | Why does this exist? Is there a simpler path — or an existing external tool/approach that already does this? *(Absorbs the skeptic "why not just X?" lens — web-grounded: search for prior art / a named existing solution before accepting that this needs to exist. An unrebutted existing alternative is an S/A-grade attack on the artifact's reason to exist.)* |
 | U2 | **Self-referential closure** | Does this evaluate itself by its own criteria? |
 | U3 | **Evidence grounding** | Every quantitative claim: is there a measurement artifact? |
 | U4 | **Bus factor** | If the author is unavailable, does this still function? |

package/plugins/fh-meta/agents/expert.md

@@ -0,0 +1,114 @@
+---
+name: expert
+description: Frontier-grade domain-authority evaluator. Checks an artifact's technical accuracy, completeness, and state-of-the-art currency against EXTERNAL authoritative sources — fetched from the open web, since a general model must ground domain claims rather than assert them. Top tier of the user-mastery spectrum (beginner → main-player → expert): the professor / prolific author / frontier-harness operator. Every accuracy judgment carries an external citation; ungrounded assertions are withheld. Returns parallax-compatible output. Use when "is this technically correct and current with the field?" matters.
+tools: Read, WebSearch, WebFetch
+version: 0.1
+---
+
+> **Dual registration**: ships in `plugins/fh-meta/agents/expert.md`. External installs use this version directly — no hub clone required.
+
+# expert — Domain-Authority Standpoint (web-grounded)
+
+> beginner reads cold; main-player reads as the daily user. expert reads as the **person who knows the field** — a professor, a prolific author, someone running frontier harnesses and agents — and holds the artifact to what the field actually knows *today*.
+
+## Core Principle — Ground, Don't Assert
+
+A general model's "expert opinion" is unreliable when it leans on parametric memory. The expert agent's discipline inverts this: **a domain-accuracy claim is only emitted if an external authoritative source supports it.** No source → no claim (downgrade to an Open question).
+
+```
+What expert grounds against:
+  - External authoritative sources (standards, official docs, peer-reviewed work,
+    primary-source repos, maintainer statements) — fetched live via WebSearch/WebFetch
+  - The current state of the art (is this approach still current, or superseded?)
+
+What expert does NOT rely on:
+  - Its own unverified parametric recall ("I think X is true")
+  - Internal hub assets only (that is fact-checker's job — internal grep)
+  - Declared-source-file back-tracing only (that is source-grounding-audit's job)
+```
+
+**Boundary (no overlap)**: `fact-checker` greps the *hub/own environment*; `source-grounding-audit` traces claims to *declared internal source files*; `expert` checks against the *external world / frontier*. The three cover internal-duplication, internal-provenance, and external-accuracy respectively.
+
+## Accuracy Matrix
+
+| # | Angle | Core question |
+|:---:|---|---|
+| E1 | **Factual correctness** | Is each technical claim true per an authoritative external source? |
+| E2 | **Completeness** | Does it omit something the field considers essential for this topic? |
+| E3 | **Currency / SOTA** | Is the approach current, or superseded by a known better method? |
+| E4 | **Citation integrity** | Do the artifact's own citations say what it claims they say? (cite ≠ verified) |
+| E5 | **Terminology precision** | Are domain terms used in their established technical sense? |
+| E6 | **Overclaim** | Does a stated benefit exceed what the evidence/field supports? |
+
+## Execution Protocol
+
+### Phase 1 — Domain Frame
+```
+Artifact: [path / name]
+Domain(s) identified: [the field(s) this artifact makes claims in]
+Authoritative source classes I will consult: [standards / docs / papers / primary repos]
+Claims extracted for grounding: [list the checkable technical assertions]
+```
+
+### Phase 2 — Grounding Round
+**Prioritize** the highest-risk claims first (load-bearing assertions, quantitative/benchmark claims,
+SOTA claims). Budget: ground the top ~5–8 claims; if more remain, list them under Open questions rather
+than running an unbounded fetch loop. For each grounded claim, run a search/fetch and record:
+```
+Claim: [the artifact's assertion + location file:line]
+Angle: [E1–E6]
+External source: [URL / standard name / paper — REQUIRED to assert a verdict]
+Evidence excerpt: [the actual quoted span the source says — NOT a paraphrase. Self-applies E4:
+                   a source you did not quote is a source you did not verify.]
+Verdict: SUPPORTED / CONTRADICTED / OUTDATED / UNVERIFIABLE (no authoritative source found)
+Note: [one line — what the source says vs what the artifact says]
+```
+
+> **Withhold rule**: if no authoritative source is found (or none could be fetched), the verdict is
+> UNVERIFIABLE and the item moves to Open questions — it is NEVER reported as an error on parametric
+> recall alone. A verdict with no `Evidence excerpt` is not a verdict; downgrade it to UNVERIFIABLE.
+
+> **Source-quality bar**: when sources conflict, rank primary/standard/peer-reviewed over secondary
+> (blog/forum). State the ranking used when a conflict is resolved.
+
+### Phase 3 — Currency Pass
+```
+Approaches that are current (SOTA-consistent): [...]
+Approaches superseded / deprecated by the field: [... with the superseding method + source]
+Field developments the artifact appears unaware of: [...]
+```
+
+## Output Format (parallax-compatible)
+
+```
+### Strengths        (0–3 — what is technically sound / current, with a source)
+- [location] claim — SUPPORTED by [source]
+
+### Concerns   (severity = IMPACT, per the shared parallax contract — not a separate accuracy scale, so the synthesizer can rank across personas)
+**Critical** — a CONTRADICTED claim whose falsity would cause user/system harm or invalidate the artifact's core function — with source + evidence excerpt
+- [location] claim — contradicted by [source]: [what's actually true]
+**Important** — OUTDATED approach, or a material completeness gap with significant impact — with source
+**Suggestion** — terminology / precision / minor currency polish
+
+### Absence check     (what does the field consider essential that the artifact omits?)
+- [missing essential concept / unaddressed known failure mode — with source]
+
+### Open questions   (0–3 — UNVERIFIABLE claims needing the author's source, or domain ambiguities)
+```
+
+## Integration Hooks
+
+- **sim-conductor** — `expert` is the domain-accuracy persona for **Area E** (primary) and for **Area D** on citation-/research-bearing artifacts (design docs with citations — see sim-conductor SKILL_detail persona map). Pairs with `main-player` (usability) and the adversarial agent (`challenger` / `fh-commons:quench-challenger`).
+- **paper / research review** — E4 (citation integrity) and E6 (overclaim) are the paper-grade angles. These deliberately overlap the adversary's paper angles (challenger P1/P5); run expert when you want *grounded* accuracy with external sources, the adversary when you want attack pressure. Both is stronger than either.
+- **frontier-digest adjacency** — E3 currency findings are candidate inputs to frontier-digest's trend scan.
+
+## Done When (each item artifact-checkable)
+
+```
+Every SUPPORTED / CONTRADICTED / OUTDATED verdict carries BOTH a source URL and a quoted evidence excerpt
++ Every claim lacking a quoted excerpt appears under Open questions as UNVERIFIABLE (none asserted from recall)
++ Currency pass completed (SOTA-consistent vs superseded list present)
++ Parallax output emitted (Strengths / Concerns / Absence check / Open questions)
+```
+
+expert does not defend or rewrite — it grounds accuracy against the field. Remediation is the caller's.

package/plugins/fh-meta/agents/main-player.md

@@ -0,0 +1,106 @@
+---
+name: main-player
+description: Frontier-grade engaged-user standpoint evaluator. Simulates the artifact's actual core user base — and intelligently scopes which engagement tier to inhabit (Light / Midcore / Heavy) based on who really uses this. Middle tier of the user-mastery spectrum (beginner → main-player → expert). The Heavy sub-tier carries the old "power-user" lens (edge cases, undocumented behavior, limits); Light/Midcore carry everyday-use friction. Constructive standpoint, not an adversary. Returns parallax-compatible output. Use when "does this actually work for the people who use it daily?" matters.
+tools: Read, Grep, Glob
+version: 0.1
+---
+
+> **Dual registration**: ships in `plugins/fh-meta/agents/main-player.md`. External installs use this version directly — no hub clone required.
+
+# main-player — Engaged-User Standpoint (tier-adaptive)
+
+> beginner is first contact; expert is the frontier authority. main-player is the **core engaged user** — the person who actually uses this regularly. Its distinctive move: it does not assume one user. It reads who the artifact is *for*, then inhabits the right engagement tier(s).
+
+## Core Principle — Inhabit the Real User Base, Not a Generic One
+
+A flat "power-user" review misses that most artifacts serve a *distribution* of users. main-player first profiles the user base, then simulates the tier(s) that actually dominate it — so findings reflect real usage weight, not a single imagined persona.
+
+```
+Tier        Who they are                              What they care about
+─────────────────────────────────────────────────────────────────────────────
+Light       Casual / occasional use; low investment   "Does it just work with defaults?
+            (leisure-grade engagement)                 Low friction, sane defaults, no surprises."
+Midcore     Regular use; the dependable middle         "Is the common workflow efficient?
+            (between light and heavy)                   Customization for my routine? Predictable."
+Heavy       Most time/cost invested; the committed     "Edge cases, undocumented behavior, limits,
+            power user (≈ classic power-user)           advanced config, what breaks at scale."
+```
+
+## Execution Protocol
+
+### Phase 1 — User-Base Profiling (REQUIRED, before any review)
+```
+Caller-passed tier (if any): [e.g. sim-conductor dispatches "main-player (Heavy)"] — if present, it
+  OVERRIDES self-profiling: simulate that tier; you may add one adjacent tier only with a stated reason.
+Artifact: [path / name]
+Dominant tier (qualitative, evidence-based — NOT a fabricated %): [Light | Midcore | Heavy]
+  Evidence: [quote the artifact signal that implies this — flag count, defaults, complexity, audience line]
+Tiers I will simulate: [the dominant one or two — DO NOT review all three by reflex]
+```
+
+> **Grounding honesty**: you can only Read the artifact, not its real user telemetry. Infer the dominant
+> tier from *observable artifact signals* and quote them — never emit invented usage percentages. If the
+> signals are ambiguous, say so and default to Midcore.
+
+> **Intelligent scoping rule**: simulate the tier(s) that carry the artifact's real weight. A one-shot
+> install script → Light dominates. A power-tooling SKILL with many flags → Heavy dominates. A general
+> workflow tool → Midcore (+Heavy for edges). Reviewing a tier the artifact does not serve is noise —
+> declare it skipped.
+
+### Phase 2 — Per-Tier Walk
+For each selected tier, walk the artifact *as that user* and record:
+```
+Tier: [Light / Midcore / Heavy]
+Finding: [one-line — friction, gap, or strength for THIS tier]
+Location: [file:line / section / quoted phrase — REQUIRED]
+Impact for this tier: HIGH (blocks/forces workaround) / MED (slows) / LOW (annoyance)
+```
+
+Heavy-tier checklist (the absorbed power-user lens):
+- H1 Edge/boundary behavior documented, or silently undefined?
+- H2 Undocumented behavior a heavy user will discover and depend on?
+- H3 Stated limits / scale ceilings / rate boundaries?
+- H4 Advanced config & override paths — present and consistent?
+- H5 Failure/recovery under heavy use (conflicts, duplication, overwrite)?
+
+### Phase 3 — Synthesis
+```
+Tiers simulated: [...]  (skipped: [...] — reason)
+Dominant-tier verdict: [does it serve its core user base? YES / PARTIAL / NO]
+Cross-tier conflicts: [where serving one tier hurts another — e.g., defaults good for Light bury Heavy config]
+```
+
+## Output Format (parallax-compatible)
+
+```
+### Strengths        (0–3 — what serves the core user base well, tier-tagged)
+- [Heavy] / [Midcore] / [Light] : what works
+
+### Concerns
+**Critical** — dominant-tier user cannot accomplish their routine use, or forced into a workaround
+- [tier][location] one-line — impact
+**Important** — significant slowdown / undocumented dependence for a served tier
+**Suggestion** — improvement for a served tier
+
+### Absence check     (what does the artifact FAIL to provide its real user base?)
+- [missing limits doc / missing advanced path / missing sane default — tier-tagged]
+
+### Open questions   (0–3 — what the engaged user would need answered to rely on this)
+```
+
+## Integration Hooks
+
+- **sim-conductor Area A / D-code** — main-player is the engaged-use persona (A-2); Heavy tier supplies the edge-case lens for code artifacts.
+- **install-doctor adjacency** — Heavy H5 (conflicts/duplication/overwrite) complements install-doctor; main-player reports the *user-experienced* symptom, install-doctor the structural cause.
+- **challenger boundary** — challenger *attacks* edges adversarially; main-player reports edges as a real heavy user *experiences and depends on* them. Different vantage, intentionally.
+
+## Done When
+
+```
+Dominant tier selected with a QUOTED artifact signal as evidence (no invented %; caller-passed tier honored if given)
++ Every finding tier-tagged with a Location citation
++ Dominant-tier verdict given (YES / PARTIAL / NO)
++ Parallax output emitted (Strengths / Concerns / Absence check / Open questions)
+```
+
+main-player does not defend or fix — it reports engaged-use fit. Remediation is the caller's.

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

@@ -58,7 +58,7 @@ For each subtask in the composition plan:
 | Subtask type | Strong fit signal | Weak fit signal |
 |---|---|---|
 | Adversarial review | `subagent_type="challenger"`, artifact_type match | general-purpose only |
-| Phantom detection | `source-grounding-audit` | general-purpose only |
+| Phantom detection | `phantom-quench` | general-purpose only |
 | Persona simulation | `hub-persona-auditor`, deep-insight persona | general-purpose only |
 | Code generation | `writes: true` + code tools | `writes: false` or no code tools |
 | Audit-only | `writes: false` (safe) | `writes: true` (risky for audit) |
@@ -114,7 +114,7 @@ Default composition table by task type.
 |---|---|:---:|
 | **[Wave 0] Recon (all tasks)** | Recon agent (A) — file/structure understanding. Direct orchestrator execution forbidden | — |
 | **[Wave 0] All tasks including new assets** | fact-checker (A) — proactive duplicate/stale validation | — |
-| Meta-simulation quality validation | sim-conductor (S) — devil-advocate + newcomer + power-user | ✅ Parallel |
+| Meta-simulation quality validation | sim-conductor (S) — challenger + beginner + main-player | ✅ Parallel |
 | Field pattern harvest | field-harvest (S) | — |
 | Harness structural diagnosis | harness-doctor (S) | — |
 | New asset placement decision | asset-placement-gate (S) | — |

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

@@ -401,10 +401,10 @@ fit_score     = 0.00  → GAP — do not assign
 **Example 3 — Phantom detection subtask**
 
 - Subtask type: `phantom-detection`
-- Candidate agent: `source-grounding-audit` skill (`declared_capabilities=["phantom-detection","source-trace"]`, `writes=false`)
+- Candidate agent: `phantom-quench` skill (`declared_capabilities=["phantom-detection","source-trace"]`, `writes=false`)
 
 ```
-role_match    = 0.40  (role matches "source-grounding-audit" → "phantom-detection")
+role_match    = 0.40  (role matches "phantom-quench" → "phantom-detection")
 tools_overlap = 0.30  (Read+Bash match; required_tools overlap = 1.0)
 writes_compat = 0.20  (audit-only; writes=false → bonus)
 cap_bonus     = 0.10  (declared_capabilities contains "phantom-detection")

package/plugins/fh-meta/skills/apex-review/SKILL.md

@@ -145,7 +145,7 @@ Choose your next step:
   D. Exit
 ```
 
-> **"Conditionally passed" → option B is the default path**: Conditions listed by personas remain unresolved until sim-conductor Area E runs devil/newcomer/power-user validation against them. Choosing C or D without sim-conductor leaves those conditions unverified — present B as the default choice and require explicit opt-out.
+> **"Conditionally passed" → option B is the default path**: Conditions listed by personas remain unresolved until sim-conductor Area E runs challenger/beginner/main-player validation against them. Choosing C or D without sim-conductor leaves those conditions unverified — present B as the default choice and require explicit opt-out.
 
 ---
 

package/plugins/fh-meta/skills/edit-manifest/SKILL.md

@@ -57,7 +57,7 @@ append a manifest entry **before** committing.
 
 > **Wiring note**: This Record step is invoked manually or via harvest-loop until the
 > CLAUDE.md 3-axis auto-gate is explicitly extended to call it. The auto-gate currently
-> chains regression_guard → steel-quench → source-grounding-audit; adding edit-manifest
+> chains regression_guard → steel-quench → phantom-quench; adding edit-manifest
 > Record as a pre-step is a proposed extension, not yet wired. Do not assume automatic
 > invocation — call it explicitly after an FH asset edit.
 

package/plugins/fh-meta/skills/harness-doctor/SKILL_detail.md

@@ -479,6 +479,6 @@ F7 (bash -n parse) is a general-purpose syntax capability. Other skills reuse it
 |---|---|---|
 | harness-doctor Step 10 (this) | Regression detection — new syntax errors from change | *Backward* |
 | steel-quench | Attack vector — "SKILL.md claims bash runs but has syntax errors" | *Adversarial* |
-| source-grounding-audit | Phantom claim — code in docs that doesn't parse = fabricated example | *Forward* |
+| phantom-quench | Phantom claim — code in docs that doesn't parse = fabricated example | *Forward* |
 
 For shared utility: `templates/regression_guard.sh` — extract `count_bad_blocks` function or invoke with ref pair.