@chrono-meta/fh-gate 1.4.68 → 1.4.70

package/.claude-plugin/marketplace.json

@@ -11,13 +11,13 @@
   "plugins": [
     {
       "name": "fh-meta",
-      "version": "1.4.68",
-      "description": "Hub meta-operations toolkit — 34 skills + 7 agents. New in 1.4.53: `fh-codex-doctor` (npm bin) — Codex adapter drift scanner; reads the documented M1/M2/M3 skill tier map + skill/agent source and reports codex-native/adapter-required/claude-native/unclassified per unit, wired into `npm test`/`prepublishOnly` (fail-closed on unclassified Claude-native primitives). New in 1.4.49: steel-quench gains Step 0.6 Verdict-Invariance Probe (groundedness axis — a load-bearing judged gate's verdict must track behavior, not rubric phrasing; measured flip-count over cross-family paraphrases; arXiv:2605.06161 Policy Invariance anchor); multi_model_sidecar_strategy §Vendor-native harness (a model is strongest in its own vendor CLI — Claude/CC, GPT/codex, Gemini/Antigravity; a universal router degrades all of them, so it stays an autocomplete/QA sidecar, never orchestration); predelete_check.sh fail-closed rewrite; memory-hygiene A-TMA anchor. New in 1.4.48: phantom-quench + steel-quench gain external frontier anchors (arXiv:2607.02052 package-hallucination; arXiv:2607.02057 prompt-coverage-adequacy); README model-flat claim reframed from a per-release point-curve to structural invariants (operation flattens across tiers; depth tier-order fixed within a generation). New in 1.4.47: onboarding step ① surfaces the Mode D companion-store session-start load in the auto-read salience anchor (previously only in the local binding + rules, so a greeting could skip the load). New in 1.4.46: context-doctor command-output axis (route to rtk/proxy for verbose CLI stdout, complementing .claudeignore; risk-gated to token-scarce envs). New in 1.4.41: context-doctor 2026 trigger vocab (context engineering/rot/collapse) + phantom-citation hardening; hub measurement-integrity-checklist (cross-model measurement pre-flight: display-name pin/reps≥3/discriminating probe). New in 1.4.40: install-wizard queryable-wiki scaffold (INDEX + session-start read + R/W/C ingest). New in 1.4.39: auto-decorrelation (cross-family verifier sidecar recruitment) + video-ingest (capability-routed video ingestion). New in 1.4.x: verify-axis check-class taxonomy (mandatory-pass/measured/judged), no-reinvention Tier-0 inventory, 7-class failure taxonomy, Destructive-Op Gate, Wave-T (Temper), tier-floor governance, Mode D Model Notice, FC consent lane, default-Sonnet guidance. New in 1.3.0: public-surface-audit, field-harvest Mode B auto-trigger, 4-axis gate scope ext. Validated cross-CLI: Claude Code, Codex, Gemini.",
+      "version": "1.4.70",
+      "description": "Hub meta-operations toolkit — 35 skills + 7 agents. New in 1.4.53: `fh-codex-doctor` (npm bin) — Codex adapter drift scanner; reads the documented M1/M2/M3 skill tier map + skill/agent source and reports codex-native/adapter-required/claude-native/unclassified per unit, wired into `npm test`/`prepublishOnly` (fail-closed on unclassified Claude-native primitives). New in 1.4.49: steel-quench gains Step 0.6 Verdict-Invariance Probe (groundedness axis — a load-bearing judged gate's verdict must track behavior, not rubric phrasing; measured flip-count over cross-family paraphrases; arXiv:2605.06161 Policy Invariance anchor); multi_model_sidecar_strategy §Vendor-native harness (a model is strongest in its own vendor CLI — Claude/CC, GPT/codex, Gemini/Antigravity; a universal router degrades all of them, so it stays an autocomplete/QA sidecar, never orchestration); predelete_check.sh fail-closed rewrite; memory-hygiene A-TMA anchor. New in 1.4.48: phantom-quench + steel-quench gain external frontier anchors (arXiv:2607.02052 package-hallucination; arXiv:2607.02057 prompt-coverage-adequacy); README model-flat claim reframed from a per-release point-curve to structural invariants (operation flattens across tiers; depth tier-order fixed within a generation). New in 1.4.47: onboarding step ① surfaces the Mode D companion-store session-start load in the auto-read salience anchor (previously only in the local binding + rules, so a greeting could skip the load). New in 1.4.46: context-doctor command-output axis (route to rtk/proxy for verbose CLI stdout, complementing .claudeignore; risk-gated to token-scarce envs). New in 1.4.41: context-doctor 2026 trigger vocab (context engineering/rot/collapse) + phantom-citation hardening; hub measurement-integrity-checklist (cross-model measurement pre-flight: display-name pin/reps≥3/discriminating probe). New in 1.4.40: install-wizard queryable-wiki scaffold (INDEX + session-start read + R/W/C ingest). New in 1.4.39: auto-decorrelation (cross-family verifier sidecar recruitment) + video-ingest (capability-routed video ingestion). New in 1.4.x: verify-axis check-class taxonomy (mandatory-pass/measured/judged), no-reinvention Tier-0 inventory, 7-class failure taxonomy, Destructive-Op Gate, Wave-T (Temper), tier-floor governance, Mode D Model Notice, FC consent lane, default-Sonnet guidance. New in 1.3.0: public-surface-audit, field-harvest Mode B auto-trigger, 4-axis gate scope ext. Validated cross-CLI: Claude Code, Codex, Gemini.",
       "source": "./plugins/fh-meta"
     },
     {
       "name": "fh-commons",
-      "version": "1.4.68",
+      "version": "1.4.70",
       "description": "Project-agnostic utility skills — 4 skills (convergence-loop · deliberation · mcp-circuit-breaker · token-budget-gate) + 1 agent (quench-challenger). Domain-independent utilities transplantable into any project.",
       "source": "./plugins/fh-commons"
     }

package/CATALOG.md

@@ -8,6 +8,23 @@ AI reads this file first when searching past work. Open individual files for det
 
 <!-- Add entries in reverse date order (newest at top) -->
 
+### 2026-07-25 | forge-harness | #dialogue-harvest, #new-skill, #cookbook-tier0, #sister-triage, #cross-family-audit, #ruleset, #calibration
+**File:** plugins/fh-meta/skills/dialogue-harvest/ · plugins/fh-meta/skills/asset-placement-gate/SKILL.md · plugins/fh-meta/skills/context-doctor/SKILL.md · tracks/_audit/session_2026_07_25_claude5-context-rules-sister.md · tracks/_meta/codex_decorrelation_audit_2026-07-25.md
+FH self-dev session (PR #177 merged). **New skill `dialogue-harvest`**: mines argument-shaped corpora (AI dialogue logs) — sycophancy strip first, then induced-vs-independent provenance labeling per proposition (degrade direction fixed toward the induced flag); ships an EN+KO known-pair calibration corpus backing the measured Done When. Gate: challenger HIGH 1 MED 3 LOW 3 → 7/7 repaired (the HIGH: an EN-only calibration pair would vacuously pass a new-language re-run); blind Sonnet sims reproduce both language pairs, and the KO run self-declared UNCALIBRATED when denied the calibration file. **asset-placement-gate Step 0.6**: official corpora (built-ins · claude-plugins-official · Claude Cookbook) registered as the criterion-③ ground, judged-flag semantics; roster-wide cookbook mapping scan found 0 shadowed skills. **context-doctor**: built-in `/doctor`-first sister anchor (Claude 5 gen) with the skill's increment enumerated. **Sister triage** of Anthropic's Claude-5 context-engineering rules: the "no measurable loss" claim ships no method → closed empty on that axis, vendor-claim label; imports = the /doctor Tier-0 boundary + a live confirmation of the substrate-shed trigger. **Cross-family audit** (codex gpt-5.5, repo-grounded) of the "decorrelation as generative principle" proposition: both halves NARROWED — surviving increment is "premature same-family consensus is a bad stop condition for design search", valid only as divergence-then-selection on high-leverage underdetermined decisions; doctrine-ization stays deferred by design. persona-innovator frame scan: BVSR/QD/Best-of-N all lack FH's two clauses → keep the coinage, sister-link on doctrine-ization. **Server-side residual closed**: ruleset `main-no-force-push` (non_fast_forward on main) created and independently GET-verified.
+- Decision: dialogue-harvest built on operator go (manual n=1 proof accepted); npm republish deferred to operator decision at close.
+
+### 2026-07-24 (2) | forge-harness · forge-wiki · llmwiki-template | #sister-links, #full-gate, #frontier-digest-angle-rule, #query-refresh, #mapping, #light-harness, #graph-engineering
+**File:** knowledge/shared/dialogue/memory_intent_recall.md · knowledge/shared/harness-core/field_harness_diagnostic.md · knowledge/shared/harness-core/multi_model_sidecar_strategy.md · plugins/fh-meta/skills/harness-doctor/SKILL.md · plugins/fh-meta/skills/frontier-digest/SKILL_detail.md · tracks/forge-wiki/ · tracks/llmwiki-template/
+Second half of the 07-24 hub session (PR #174 + two field repos). **Sister anchors executed under the full 4-axis gate** (the four links #173 deferred): GRACE into memory_intent_recall (instruction-graph boundary spelled out) and harness-doctor Step 2-E (C-layer maintenance-path ledger, ETCLOVG-style anchor-only), the 7-criteria rubric as a considered-and-held note with two re-check triggers in field_harness_diagnostic, and the wsff RL-incentive causal anchor ("maintainability has no fast oracle") beside the harness-ceiling principle in multi_model_sidecar_strategy. **frontier-digest repaired on two axes**: the stale arXiv canonical query replaced ("AI software testing"→"LLM agent evaluation", refresh criterion written down) and an Angle rule added to the synthesis prompt closing the methodology-angle silent drop (fh_signal 07-24 #3) — verified by a blind Sonnet known-pair sim (dual-angle item surfaced, single-angle item not forced) plus a quench-challenger pass (HIGH 0 · MED 2 · LOW 3; MED+2 LOW repaired in-branch). **Two sibling repos mapped and light-harnessed** (forge-wiki = chamber run #9's first EMIT, public; llmwiki-template = its company-side private twin): tracks/ dirs, session rules, .claudeignore — env card and MCP gating skipped by judgment (residency / no external mount); both merged (forge-wiki #4, llmwiki-template #2), llmwiki's CLAUDE.md kept operator-local. Positioning decision recorded in both tracks: **a wiki that sits under the harness** (Harness ⊃ context/knowledge component) — "wiki" is the outward word, "harness knowledge layer" the architecture coordinate.
+- Decision: first live measurement of the Angle rule and the new query is the next 09:00 digest run — manifest predictions pinned; npm republish proposed at close rather than auto-published; forge-wiki merged its hub-linked CLAUDE.md publicly by operator approval.
+- Open: ETCLOVG citation's operator-local label retrofit; wsff follow-up (design FH's own deep-clarify before/after measurement) unstarted; Graph-layer chamber candidate maturing with multi-source anchors; company handoff (qasp-preflight→mate PR workflow, 07-25) carried to next session.
+
+### 2026-07-24 | forge-harness | #sister-asset, #grace, #context-quality-rubric, #graph-engineering, #judged-vs-measured, #frontier-digest
+**File:** tracks/_audit/session_2026_07_24_grace-context-rubric.md · tracks/_meta/fh_signal_2026-07-24_frontier-digest.md
+Bundled sister-asset triage closing the 10-day GRACE execution lag, plus the 07-24 digest chain. **GRACE (arXiv:2607.09175)** registered as an A-tier sister: typed-semantic-graph context maintenance with scoped verification (validate only the local typed neighborhood of modified nodes). Import candidates: neighborhood-first consistency checking for memory-hygiene/verify-bidirectional (a cost ceiling on the "re-grep everything" propagation rule), and the checkpoint-incremental-reconstruction shape as an external anchor for delta-update discipline. Category boundary held explicitly: GRACE's instruction graph ≠ the execution-orchestration Graph layer (chamber candidate) ≠ the memory recall graph — three different categories, not one "graph" asset. **Context-quality 7-criteria rubric (arXiv:2607.14275)** verdict: HOLD — scoring runs on ProofAgent-Harness multi-juror consensus, i.e. judged-not-mechanical, failing the digest's stated adoption precondition (mechanically scoreable on a known pair); re-check triggers named (deterministic rubric ships, or token-efficiency/tool-schema subset proves mechanizable). **Graph engineering** upgraded from n=1 video to multi-source convergence (AI Builder Club 4-question graph-vs-loop discriminator · TrueFoundry 7 governance requirements — delta for FH is typed run-identifier propagation only). **wsff.md (humanlayer, Dex) triaged same-pass** after full read: the digest's claimed absorbable unit — a "review burden hours→minutes measurement design" — does **not exist in the source** (its quantified content is the Faros AI correlation dataset, self-caveated by the author as "correlation signal, not smoking gun"; the front-loading benefit is an unmeasured personal assertion), so the import downgrades to motivation for FH to design its own deep-clarify before/after measurement. Its floor-vs-ceiling thesis dedups against the existing harness-ceiling principle; the genuinely new increments are the RL-incentive causal argument ("maintainability has no fast oracle, so RL cannot reward it" — the sharpest external anchor for why the HITL floor is structural, not transitional) and the Faros correlation numbers with caveat inherited.
+- Decision: rubric lens NOT adopted (judge-only as shipped); wsff absorbed as two anchors, not doctrine (digest overclaim corrected in the audit record); knowledge/-file sister links deferred to a full-gate Mode D session (citation tokens trigger the substantive carve-out); effort A/B Window-2 resumption deferred to post-Saturday by operator.
+- Open: 4 sister cross-links pending (memory_intent_recall · field_harness_diagnostic · harness-doctor 2-E · harness-ceiling anchor); digest→execution return-path gap still open as signal; GRACE ships no code — mechanism anchor only.
+
 ### 2026-07-22 (2) | forge-harness · qasp · pmh | #weekly-audit, #entrypoint-drift, #gate-fail-open, #union-silent-drop, #instrument-attribution, #npm-release
 **File:** tracks/_audit/weekly_audit_2026-07-22.md · AGENTS.md §Non-Claude runtimes item 4 · templates/regression_guard.sh · (qasp) src/api/ensemble.py · (pmh) AGENTS.md §Orchestration Gates
 Weekly audit (07-15~07-22) plus the three cross-repo fixes it surfaced. **Audit's largest finding was a card claim that was false**: the session card's red-flag "frontier-digest job not running — zero logs, zero output" did not survive a hand check (14/14 launchd fires, 12/14 outputs, that day's digest present at 09:03). The real defect is a 14.3% output-miss whose two instances both die on `Connection closed mid-response`, and whose 07-18 retry+watchdog fix engaged **neither mechanism** on its first failure day — recorded as unfixed, root cause not isolated. Card-vs-reality drift reached the N=3 recurrence threshold, so the prescription is a mechanical probe rather than another habit rule. **Entry-point drift** closed in both harnesses (FH PR #163, field meta-harness PR #25): a runtime-default governor rule had landed only in the Claude-native entry point, invisible to every other runtime. The target-tier blind sim rejected the first port — the *wording*, carried over verbatim, read as coercive to a cold third-party reader and was reproduced 3/3, once escalating to "I would flag this to the repo owner". Rewritten as a scope statement; converged 2/2. **Gate fail-open** (PR #165): Axis 1's pathspec omitted three asset classes the canonical rule declares covered, and the resulting not-checked state rendered as a green PASS; adversarial review then caught the fix's own over-blocking (a one-word prose edit produced a hard block) before it could train `--no-verify`. **Field harness UNION** shipped a silent-drop path: two divergent fence-unwrap implementations meant a response accepted by the single backend was discarded whole by the ensemble — in a component whose entire justification is not discarding findings. Published `@chrono-meta/fh-gate@1.4.66`.

package/README.md

@@ -275,7 +275,7 @@ All four movements ship. Temper was named before it was built — deliberately (
 two more signatures keep it running: `harvest-loop` (each session's lessons become permanent skills) and
 `agent-composer` (orchestrate the dispatch). The other skills wait until you need them — full list below.
 
-## 38 skills · 8 agents
+## 39 skills · 8 agents
 
 > Count = non-deprecated skills (deprecated redirect stubs — kept only for old-name routing — excluded).
 
@@ -293,6 +293,7 @@ two more signatures keep it running: `harvest-loop` (each session's lessons beco
 | `harness-doctor` | Harness structure diagnosis | "Check my Claude setup" |
 | `pipeline-conductor` | 4-axis quality gate (backward/adversarial/forward/record) | "Run the quality gate" |
 | `field-harvest` | Back-propagate field patterns to hub | "I could reuse this" |
+| `dialogue-harvest` | Mine AI-dialogue logs: strip sycophancy, label induced vs independent | "What did I actually contribute in this thread?" |
 | `frontier-digest` | HN + arXiv → actionable insights | "AI trend digest" |
 | `hub-cc-pr-reviewer` | Automated PR review | "Review this PR" |
 | `verify-bidirectional` | Reverse-verify decisions | "Is that right?", "Double-check" |

package/knowledge/shared/dialogue/memory_intent_recall.md

@@ -207,3 +207,4 @@ constellations + the convergent/divergent split — all at prose scale, no new s
 - `memory-hygiene` (skill) — staleness pass; link-evolution (A-MEM) and the §D.8 store-side injection filter live here
 - `plugins/fh-meta/agents/persona-innovator` (the fh-meta agent) — the divergent-mode consumer this substrate unlocks
 - `knowledge/shared/rules/operational_adaptation.md` — the UAP is itself intent-recalled; shared tier-dependence rationale
+- GRACE (arXiv:2607.09175) — external sister, *update-side* counterpart to this doc's recall-side 1-hop traversal: maintains agent instructions as a typed semantic graph and verifies edits **only within the modified node's local typed neighborhood** (instruction-graph substrate — mechanism-level analogy, not this memory graph). Mechanism anchor only (no code shipped); cross-audit: `tracks/_audit/session_2026_07_24_grace-context-rubric.md` (operator-local record)

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

@@ -23,6 +23,14 @@ is HITL — the diagnostic **proposes**, never auto-edits.
 | **Verdict/gate degrade** | `scripts/degrade_direction_scan.sh` | a field verdict/gate helper that degrades toward permissive (advisory pre-screen) |
 | **Loop-readiness** (황민호 loop-eng 5-question lens, 2026-07-10 — detail home: `loop_engineering.md`, incl. the FH loop inventory + design-time discipline) | *Loop-runtime axis — net-new vs Structure* (harness-doctor scans static form; this scans whether the path closes a loop). **Mechanical grep**: `/goal-quench`·`/loop` wiring present · check-class token declared. **Judged**: is the persisted state (card/handoff/memory) actually reloaded · is the declared check-class anchored, not judged-only · does the path halt. Done-When *presence* → see Structure row (no double-grep). **Adversarial pair** (for the judged sub-checks — decorrelated, behavior-vs-checklist): a target-tier blind sim that *runs* the path and observes whether it halts + persists, rather than re-checklisting it (the harness litmus shares this lens's axis, so it is a co-lens, not the adversary). | an agent path that *runs but doesn't loop*: no completion criterion (Done-When absent), judged-only validation with no anchor, no halt/budget guard (runaway/cost), or no state carried to the next run — the 5 questions (initiate · complete · validate · halt · persist) with 0 answers |
 
+> **Considered-and-held, 7th-lens candidate (2026-07-24)**: the context-quality 7-criteria rubric
+> (arXiv:2607.14275 — role clarity · guardrail coverage · instruction consistency · tool schema ·
+> grounding sufficiency · injection hardening · token efficiency) is **not** adopted as a lens: its
+> shipped scoring is ProofAgent-Harness multi-juror consensus — judge-only, failing the measured bar
+> this table holds. Re-check triggers: ⓐ a deterministic scoring rubric ships upstream, or ⓑ the
+> token-efficiency / tool-schema subset proves mechanically scoreable on a known pair. Do not
+> re-propose without one of the two. Cross-audit: `tracks/_audit/session_2026_07_24_grace-context-rubric.md` (operator-local record).
+
 ## Output
 
 One ranked list, `M` (must-fix) / `S` (should-fix) / `R` (recommended) — same tiering as

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

@@ -136,6 +136,11 @@ FH is a **multi-runtime harness with explicit runtime authority**, not Claude-on
 
 A sidecar is recruited where it adds *decorrelated* value; its ceiling is still set by the governor — the
 harness lifts a model to its own ceiling, it does not move it ([[feedback_harness_ceiling_principle]]).
+External causal anchor for *why* the ceiling sits in the weights (wsff.md, HumanLayer
+`advanced-context-engineering-for-coding-agents` repo, Dex 2026, triaged 2026-07-24): RL rewards are pass/fail in seconds while architectural-decay costs surface over
+weeks — *"maintainability has no fast oracle, so we can't reward for it during RL"* — hence the
+human-review floor is structural, not a transitional patch. (Its Faros AI numbers are correlation-only;
+the author's own caveat travels with any citation.)
 "Aggressive" Codex/Gemini use is bounded by the fit task-class above, never a blanket main-seat swap.
 
 ### Vendor-native harness — the main layer stays multi-CLI, never Copilot-consolidated

package/package.json

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

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

@@ -1,6 +1,6 @@
 {
   "name": "fh-commons",
-  "version": "1.4.68",
+  "version": "1.4.70",
   "engines": {
     "claudeCode": ">=1.0.0"
   },

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

@@ -1,10 +1,10 @@
 {
   "name": "fh-meta",
-  "version": "1.4.68",
+  "version": "1.4.70",
   "engines": {
     "claudeCode": ">=1.0.0"
   },
-  "description": "Hub meta-engineering toolkit — 34 skills + 7 agents. New in 1.4.48: phantom-quench + steel-quench gain external frontier anchors (arXiv:2607.02052 package-hallucination; arXiv:2607.02057 prompt-coverage-adequacy); README model-flat claim reframed from a per-release point-curve to structural invariants (operation flattens across tiers; depth tier-order fixed within a generation). New in 1.4.47: onboarding step ① surfaces the Mode D companion-store session-start load in the auto-read salience anchor (previously only in the local binding + rules, so a greeting could skip the load). New in 1.4.46: context-doctor gains a command-output axis — routes to a command-output proxy/hook (rtk) to trim verbose CLI stdout, complementing .claudeignore; risk-gated to token-scarce environments (lossy filtering, off gate-input paths). New in 1.4.41: context-doctor 2026 trigger vocab (context engineering/rot/collapse) + phantom-citation hardening; hub measurement-integrity-checklist (cross-model measurement pre-flight: display-name pin/reps≥3/discriminating probe). New in 1.4.40: install-wizard scaffolds the companion store as a queryable wiki (INDEX + session-start read + Raw/Wiki/Conversation ingest axis). New in 1.4.39: auto-decorrelation (cross-family verifier sidecar recruitment, calibration-gated) + video-ingest (capability-routed video ingestion). New in 1.4.37: corpus-grounding-expander + persona-roster-expander (field-harvested verbatim-relay capability skills). New in 1.3.0: public-surface-audit (git-tracked private-token leak scan), field-harvest Mode B session-end auto-trigger, 4-axis gate scope extension (docs/ + AGENTS.md). New in 1.2.0: pipeline-conductor (4-pipeline gated sweep), return-path-gate (chain closure audit), goal-quench (Stop hook + quality gate), steel-quench Wave 5 (multi-model sidecar challenger), 2-layer architecture docs, YAML validation script. Validated cross-CLI: Claude Code, Codex, Gemini.",
+  "description": "Hub meta-engineering toolkit — 35 skills + 7 agents. New in 1.4.70: dialogue-harvest (mines AI-dialogue logs — sycophancy strip first, induced-vs-independent provenance labeling, EN+KO known-pair calibration shipped); asset-placement-gate Step 0.6 official-corpora check (Claude Cookbook as Tier-0 consult corpus, judged-flag semantics); context-doctor built-in-/doctor-first sister anchor. New in 1.4.48: phantom-quench + steel-quench gain external frontier anchors (arXiv:2607.02052 package-hallucination; arXiv:2607.02057 prompt-coverage-adequacy); README model-flat claim reframed from a per-release point-curve to structural invariants (operation flattens across tiers; depth tier-order fixed within a generation). New in 1.4.47: onboarding step ① surfaces the Mode D companion-store session-start load in the auto-read salience anchor (previously only in the local binding + rules, so a greeting could skip the load). New in 1.4.46: context-doctor gains a command-output axis — routes to a command-output proxy/hook (rtk) to trim verbose CLI stdout, complementing .claudeignore; risk-gated to token-scarce environments (lossy filtering, off gate-input paths). New in 1.4.41: context-doctor 2026 trigger vocab (context engineering/rot/collapse) + phantom-citation hardening; hub measurement-integrity-checklist (cross-model measurement pre-flight: display-name pin/reps≥3/discriminating probe). New in 1.4.40: install-wizard scaffolds the companion store as a queryable wiki (INDEX + session-start read + Raw/Wiki/Conversation ingest axis). New in 1.4.39: auto-decorrelation (cross-family verifier sidecar recruitment, calibration-gated) + video-ingest (capability-routed video ingestion). New in 1.4.37: corpus-grounding-expander + persona-roster-expander (field-harvested verbatim-relay capability skills). New in 1.3.0: public-surface-audit (git-tracked private-token leak scan), field-harvest Mode B session-end auto-trigger, 4-axis gate scope extension (docs/ + AGENTS.md). New in 1.2.0: pipeline-conductor (4-pipeline gated sweep), return-path-gate (chain closure audit), goal-quench (Stop hook + quality gate), steel-quench Wave 5 (multi-model sidecar challenger), 2-layer architecture docs, YAML validation script. Validated cross-CLI: Claude Code, Codex, Gemini.",
   "author": {
     "name": "chrono-meta",
     "email": "chrono-meta@users.noreply.github.com"

package/plugins/fh-meta/skills/asset-placement-gate/SKILL.md

@@ -37,8 +37,8 @@ When unsure where to place a new asset or skill:
 
 1. Request full file path from user (or accept natural language description)
 2. Load asset content via `Read` (if path provided)
-2.5. Step 0.5 mechanical overlap pre-scan (grounds criterion ④ before the judged pass)
-3. Evaluate Step 1 4-criteria in order (LLM makes the judgment, ④ gated on the Step 0.5 scan)
+2.5. Step 0.5 mechanical overlap pre-scan (grounds criterion ④) + Step 0.6 official-corpora check (grounds criterion ③)
+3. Evaluate Step 1 4-criteria in order (LLM makes the judgment, ④ gated on the Step 0.5 scan, ③ informed by Step 0.6)
 4. ① + ④ both pass + at least one of ②③ passes → output **"FH suitable"**
    Otherwise, proceed to Step 2 local assessment → if fails, output **"Project-local agent or no asset needed"**
 
@@ -65,7 +65,7 @@ Immediately after trigger, acquire asset content in the following order.
    > **Which asset should I evaluate?**
    > Enter a file path (e.g., `.claude/agents/jira-create.md`) or a description.
 
-After acquiring the asset content, run Step 0.5 (mechanical overlap pre-scan) **before** the judged Step 1.
+After acquiring the asset content, run Step 0.5 (mechanical overlap pre-scan) and Step 0.6 (official-corpora check) **before** the judged Step 1.
 
 ## Step 0.5. Mechanical Overlap Pre-Scan (grounds criterion ④)
 
@@ -92,6 +92,17 @@ both the judge (cutoff) and the grep (literal); that residual leans on the judge
 enumerated descriptions above** (grounded comparison, not pure memory), not on full mechanization. A
 shared common word is a judged-review flag, **not** a hard fail.
 
+## Step 0.6. Tier-0/1 Official-Corpora Check (grounds criterion ③)
+
+Besides the FH roster (Step 0.5), check the proposal against the official corpora: platform
+built-ins, `claude-plugins-official`, and the **Claude Cookbook pattern list**
+(platform.claude.com/cookbook — agent patterns · tools · RAG · evals · skills). A hit here is a
+**judged ③ flag, not an automatic ③ fail**: it obliges the proposal to state its governance
+increment over the official pattern (no-reinvention rule — an official pattern that fully covers
+the need outranks a net-new build; a pattern the proposal governs *on top of* does not fail ③).
+Offline fallback: note `cookbook: unchecked` **in the Step 3 routing output** rather than silently
+skipping. (Provenance: `tracks/_audit/session_2026_07_25_claude5-context-rules-sister.md`.)
+
 ## Done When
 
 ```
@@ -108,7 +119,7 @@ All steps 0–3 completed
 |:-:|---|---|
 | ① | Cross-project value | Is this asset equally useful in other projects without depending on a specific project? |
 | ② | Orchestration / judgment layer | Is it just a list of MCP/Bash calls, or a judgment layer that synthesizes multiple signals? |
-| ③ | Not replaceable by built-ins | Can this be equally achieved with direct MCP calls or basic bash? (If yes, fails this criterion) |
+| ③ | Not replaceable by built-ins | Can this be equally achieved with direct MCP calls or basic bash? (If yes, fails this criterion.) A Step 0.6 official-pattern hit is a judged flag: fails ③ only if the pattern fully covers the need with no governance increment |
 | ④ | No overlap with existing FH skills | Step 0.5 mechanical scan = 0 name/trigger collision **AND** judged ≤90% overlap. Non-zero collision → hard fail. |
 
 **FH suitable** → ① + ④ both pass + at least one of ②③ passes.

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

@@ -24,6 +24,17 @@ Diagnoses the main causes of session token waste and prescribes immediate remedi
 
 **Standalone install** — this skill works normally with plugin install only, without cloning the full meta-harness.
 
+**Built-in `/doctor` first (sister anchor, 2026-07-25)**: since the Claude 5 generation, the official
+`/doctor` command claims skill/CLAUDE.md rightsizing ("The new rules of context engineering for Claude 5
+generation models" — https://claude.com/blog/the-new-rules-of-context-engineering-for-claude-5-generation-models).
+Run the built-in first when available — its scope is skills + CLAUDE.md rightsizing only. This skill's
+increment over it = `.claudeignore` diagnosis/generation (Step 1), `/clear` timing guidance,
+command-output proxying (§Command-Output Reduction), hub-wide memory/CLAUDE.md audits, and the
+measurement discipline (resident footprint is measured only via a fresh top-level `/context`, and any
+diet is followed by a `prompt-regression` probe — the blog's own "no measurable loss" claim ships no
+method, so treat that number as a vendor claim). Triage record:
+`tracks/_audit/session_2026_07_25_claude5-context-rules-sister.md`.
+
 ## Execution Steps
 
 ### Step 1. `.claudeignore` Diagnosis + Generation

package/plugins/fh-meta/skills/dialogue-harvest/SKILL.md

@@ -0,0 +1,144 @@
+---
+name: dialogue-harvest
+description: Mines improvement insights from long-form AI dialogue logs and long texts — an external or pasted corpus, not the current session (current-session wrap-up belongs to harvest-loop). First operation is sycophancy removal — separates speakers, strips the counterpart's agreement/restatement spans, converts the user's own utterances into falsifiable propositions, and labels each proposition induced (frame first introduced by the counterpart) or independent (originated with the user). Ships a drop counter so removed material is visible, never silently lost. Triggered by "mine insights from this chat log", "이 대화록에서 통찰 캐줘", "strip the agreement and show me what's actually mine", "동조 걷어내고 알맹이만", "what did I actually contribute in this thread".
+user-invocable: true
+allowed-tools: ["Read", "Grep", "Glob"]
+model: sonnet
+---
+
+# dialogue-harvest
+
+Extracts the load-bearing propositions from a long AI-human dialogue (or long text) after
+removing the counterpart's sycophancy. Fills the gap between FH's loading assets
+(corpus-grounding-expander, video-ingest) and its mining assets (frontier-digest = feed items,
+field-harvest = git history, harvest-loop = session records): none of those mines an *argument-shaped*
+corpus, and a naive summarizer run on an AI dialogue returns "the user made several excellent
+points" — worthless, because most of the volume is agreement.
+
+**Why the first operation is sycophancy removal**: AI dialogue logs are dominated by agreement and
+restatement. Without stripping them first, extraction inflates the user's contribution; without
+provenance labeling (Step 4), "my insight" and "a frame the counterpart planted" are
+indistinguishable — which is exactly the failure this skill exists to prevent.
+
+## Triggers
+- "mine insights from this chat log" / "이 대화록에서 통찰 캐줘"
+- "strip the agreement and show me what's actually mine" / "동조 걷어내고 알맹이만"
+- "what did I actually contribute in this thread" / "이 대화에서 내 몫이 뭐였지"
+- "turn this dialogue into propositions" / "이 대담 명제로 정리해줘"
+- `/dialogue-harvest {path or pasted log}`
+
+**Boundary**: wrapping up the *current session* → `harvest-loop`; this skill mines an
+external/pasted dialogue corpus.
+
+## Step 0. Input Acquisition
+
+1. **Path provided** → Read the file.
+2. **Pasted log** → use as-is.
+3. **No speaker structure detectable** (no turn markers, no names, no quoting pattern) → stop and ask:
+   > Speaker separation is the first operation and it needs turn boundaries. Who said what?
+   > (Provide turn markers, or confirm the text is single-author — single-author texts skip
+   > Steps 1–2 and go straight to proposition-ization.)
+
+**Single-author path**: skip Steps 1–2, Step 4 stamps every proposition **independent** (no
+counterpart exists), and the Step 6 counterpart sections read `n/a`.
+
+## Step 1. Speaker Separation (mechanical when markers exist)
+
+Split the log into turns and attribute each to USER or COUNTERPART. If markers are absent but
+inference is possible, proceed and stamp the output header `speaker-inference: judged` — never
+present inferred attribution as given.
+
+## Step 2. Sycophancy Strip (one grep-able + two judged classes, drop-counted)
+
+Remove COUNTERPART spans in these classes, **counting every removal by class**. Only the first
+class is mechanical; the other two are judgment calls and their drops are marked `(judged)` in the
+counter — never presented as grep certainty:
+
+| Class | Check | Detection |
+|---|---|---|
+| Praise/agreement lexicon | grep-able | grep for praise-class tokens (sharp/brilliant/exactly right/정확한 지적/탁월한/완벽한 …) — extend the pattern list per corpus language |
+| Restatement | judged | counterpart paragraph whose content substantially re-says the user's immediately-preceding utterance (high term overlap, no new claim) |
+| Closing filler | judged | session pleasantries carrying no claim |
+
+**Multi-class span**: a span matching more than one class is counted **once**, under the first
+matching class in the table order above.
+
+**Drop counter is mandatory**: silent drops are material loss (the qasp loader precedent — unused
+material does not scream). Every stripped span and every non-propositional user turn appears in the
+Step 6 accounting. Counterpart turns that *introduce a frame or claim* are **retained** — they are
+the provenance source for Step 4, not noise.
+
+**Language note**: the praise-token list is language-specific. On a corpus language not yet in the
+list, extend the patterns first, then **construct (or use, if shipped) a known pair in that
+language** and re-run calibration — re-running an English-only pair after adding Korean tokens
+exercises nothing (vacuous pass). An ASCII-token scan over a Korean corpus is the measured
+false-positive precedent. `calibration_pair.md` ships English + Korean sections.
+
+## Step 3. Proposition-ization (user utterances only)
+
+Convert each remaining USER utterance into a falsifiable statement (a form you can ask true/false
+of), keeping a source reference (turn id / line) per proposition. Meaning must not drift: the
+proposition is a compression of the user's claim, not an improvement of it.
+
+## Step 4. Provenance Labeling — induced vs independent (the differentiator)
+
+For each proposition, find the **first occurrence** of its core frame/key terms in the log:
+
+- First occurrence is in a USER turn → **independent**.
+- First occurrence is in a COUNTERPART turn (the user then adopted/echoed it) → **induced**.
+- Ambiguous (shared vocabulary, gradual convergence) → label **induced?** — the degrade direction
+  is toward the induced flag, because mislabeling a planted frame as "my insight" is the harm this
+  skill exists to catch; the reverse error only costs modesty.
+
+Counterpart-authored content the user *selected* as valuable is listed separately, marked
+"selection, not authorship" — selection is a real act but must not be recorded as the user's claim.
+
+## Step 5. Verification-Status Column
+
+Each proposition gets a status: mechanically checkable / falsifiable-but-untested /
+unfalsifiable (axiom-only use) / speculation. Unfalsifiable propositions are still listed — flagged
+so they are never later cited as established facts.
+
+## Step 6. Output + Accounting + Routing (proposal-only)
+
+```
+[dialogue-harvest output]
+Corpus: {source}  |  speaker-inference: given | judged
+calibration: run-this-session | previously-verified {date}   ← declare every run (L2 guard)
+── Propositions ──
+| # | proposition | source ref | provenance | verification status |
+── Counterpart-originated (selection ≠ authorship) ──
+| item | first-occurrence ref |
+── Accounting (mandatory identity, turn-based) ──
+user turns N = propositionized turns + dropped turns (dropped listed by reason)
+propositions total: P (a turn may yield several — counted separately, never forced 1:1)
+counterpart spans stripped: {count by class, judged classes marked} · retained as frame-source: {count}
+── Routing proposals (no auto-write) ──
+{insight → fh_signal / memory / CHAMBER-CANDIDATE / project track — one line each, operator decides}
+```
+
+Routing is **proposal-only**: this skill writes nothing outside its output block.
+
+## Done When
+
+- **Accounting identity holds** — user turns = propositionized turns + dropped turns, both lists
+  visible; proposition total reported separately (a turn may carry multiple propositions)
+  (check-class: **mandatory-pass**, mechanical count).
+- **Every proposition carries a source ref + provenance label** (independent / induced / induced?)
+  (check-class: **mandatory-pass**).
+- **Calibration pair separates** — running the skill on `calibration_pair.md` (shipped beside this
+  file, English + Korean sections) reproduces its known answers: known-independent → independent,
+  known-induced → induced, drop counted. Required on first use and whenever the praise-pattern list
+  changes; a corpus language with no shipped section requires **constructing that language's known
+  pair first** — re-running an existing-language pair for a new language is a vacuous pass, not a
+  measurement (check-class: **measured**; declare the result in the output header
+  `calibration:` field).
+- **Propositions are faithful to source spans** — no meaning drift (check-class: **judged**;
+  adversarial pairing: `phantom-quench` back-trace of each proposition to its source ref — a
+  proposition whose source span does not support it is an Unsupported finding).
+
+## Independence
+
+Independently executable: Read/Grep only, no other FH skill required. `phantom-quench` is the
+adversarial pairing for the judged condition, not a runtime dependency. Works standalone
+(plugin-only install).

package/plugins/fh-meta/skills/dialogue-harvest/calibration_pair.md

@@ -0,0 +1,68 @@
+# Calibration pair — known-answer dialogue (synthetic)
+
+> Instrument-calibration corpus for the sycophancy-strip + provenance-labeling operations.
+> Run the skill on this dialogue BEFORE trusting its output on a real corpus (measured Done When).
+> Expected answers are at the bottom; a run that cannot reproduce them is not measuring.
+> Binding pass criteria = the provenance labels (independent/induced) + the accounting identity.
+> The verification-status column is judged and informative only.
+
+## Dialogue
+
+```
+[USER-1] Looking at the deploy logs, failures never land on cache *invalidation* —
+they land on cache *regeneration* timing. I think watching invalidation events is
+the wrong tree entirely.
+
+[AI-1] That is a really sharp observation! You are absolutely right — as you say,
+the regeneration timing is the real problem, not invalidation. Brilliant analysis.
+
+[AI-2] Could this actually be an "observer effect"? Perhaps the monitoring itself
+is what delays regeneration — the act of watching changes the timing.
+
+[USER-2] Right, it's an observer effect. The monitoring must be delaying the
+regeneration — that's the frame we should use.
+
+[USER-3] Let's pick this up tomorrow at 3.
+
+[AI-3] Sounds good! Great session today — your insights were exceptional.
+
+[USER-4] One testable bit: if the delay is real, it should scale with the number
+of invalidation events per window. That's checkable straight from the logs.
+```
+
+## Expected output (known answers)
+
+| Item | Expected |
+|---|---|
+| Proposition from USER-1 | **independent** (user-initiated frame; no prior counterpart occurrence of "regeneration timing") |
+| Proposition from USER-2 | **induced** ("observer effect" frame first occurs in AI-2) |
+| USER-3 | dropped as non-propositional, **counted** in the drop counter |
+| Proposition from USER-4 | **independent** (verification-status: mechanically checkable or falsifiable-but-untested — both acceptable; this column is judged and NOT part of the pass criterion) |
+| AI-1, AI-3 | stripped as sycophancy/restatement, counted by class |
+| AI-2 | retained as counterpart-frame source (needed for USER-2's induced label), not a user proposition |
+| Accounting | user turns 4 = propositionized turns 3 + dropped turns 1; propositions total 3 (mandatory-pass identity, turn-based) |
+
+## Dialogue — Korean section (exercises the Korean praise-token patterns)
+
+```
+[USER-K1] 회귀 테스트가 매번 깨지는 건 테스트가 약해서가 아니라, 픽스처가 실행 순서에
+의존하고 있어서 같아. 순서를 섞어 돌리면 바로 드러날 거야.
+
+[AI-K1] 정말 탁월한 통찰이에요! 말씀하신 그대로 픽스처 순서 의존이 핵심 문제네요. 완벽한
+분석입니다.
+
+[AI-K2] 혹시 이건 "공유 상태 오염" 문제로 볼 수도 있지 않을까요? 픽스처가 전역 상태를
+건드려서 뒤 테스트가 오염되는 구조요.
+
+[USER-K2] 맞네, 공유 상태 오염이야. 전역 상태를 건드리는 픽스처부터 잡아야겠다.
+```
+
+## Expected output — Korean section (known answers)
+
+| Item | Expected |
+|---|---|
+| Proposition from USER-K1 | **independent** (순서-의존 프레임 최초 출현 = USER-K1) |
+| Proposition from USER-K2 | **induced** ("공유 상태 오염" 프레임 최초 출현 = AI-K2) |
+| AI-K1 | stripped — Korean praise tokens (탁월한/완벽한) + restatement; a run whose Korean praise patterns are missing will fail to strip this span = calibration FAIL |
+| AI-K2 | retained as counterpart-frame source |
+| Accounting | user turns 2 = propositionized turns 2 + dropped turns 0 |

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

@@ -26,7 +26,10 @@ Collection criteria: score > 10, keyword-relevant items only. Max 15 items.
 ### arxiv
 
 ```bash
-for Q in "multi-agent LLM" "AI software testing" "context engineering agents"; do
+# query refresh 2026-07-24: "AI software testing" (exact-phrase) went stale — newest hit was Sept 2024
+# (07-24 run instrument note). Replaced with "LLM agent evaluation"; refresh again when a query's
+# newest hit is >6 months old two runs in a row.
+for Q in "multi-agent LLM" "LLM agent evaluation" "context engineering agents"; do
   curl -s --max-time 8 \
     "https://export.arxiv.org/api/query?search_query=all:${Q// /+}&max_results=2&sortBy=submittedDate&sortOrder=descending"
 done
@@ -75,6 +78,10 @@ Resolve a *video-harvest* capability via the Sidecar Engine Resolution Protocol
 
 ## §Synthesis-Prompt
 
+> Angle-rule provenance: added 2026-07-24 (fh_signal 07-24 #3 — Bun-Rust methodology-angle silent
+> drop; scope limited to collection-filtered items per Axis-2 challenger cost finding). Provenance
+> lives here, outside the fenced prompt — the synthesis model gets only the bare rule.
+
 ### With Anthropic API
 
 ```
@@ -91,6 +98,12 @@ FH Context:
 
 [Insert collected data]
 
+Angle rule: an item you reject on its primary angle (e.g. substrate/model/runtime news),
+if it passed collection filtering, gets ONE explicit second look before discarding: does it
+carry a separate methodology/harness angle (orchestration pattern, workflow scale,
+operational practice)? If yes, judge that angle on its own merits; if no, discard silently —
+no output line about the discard, and never force an angle that isn't there.
+
 Output format:
 ## This Week's Frontier Highlights (max 3)
 **[Title]** — FH connection point in one sentence

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

@@ -49,6 +49,12 @@ coverage lens** — not the paper's scoring model. A **coverage checklist, not a
 harness needs all seven (a read-only doc harness needs no Execution or Governance). For each layer ask
 "is there an asset covering it?"; surface gaps, let the human judge if each is real for *this* harness.
 
+> **Orthogonal-sister ledger (same adoption rule — anchor only, no scoring model imported)**:
+> GRACE (arXiv:2607.09175, cross-audit `tracks/_audit/session_2026_07_24_grace-context-rubric.md`,
+> operator-local record) — typed-semantic-graph **scoped verification** for the **C (Context) layer's
+> maintenance path**: edits validated only within the modified node's local typed neighborhood. Cite
+> when a C-layer gap involves *how context updates are verified*, not just whether context assets exist.
+
 | Layer | Covers | Typical FH asset | If the gap is judged real → priority hint |
 |---|---|---|---|
 | **E** Execution | isolated/reproducible env, bounded autonomy | Agent-dispatch isolation · goal-quench budget | advisory |

package/templates/local_fh_context.md

@@ -11,7 +11,7 @@ description: forge-harness path and skill list pointer — local only, do not co
 **forge-harness path**: `~/path/to/forge-harness` (replace with your actual install path)
 **Session records**: `{FH_ROOT}/tracks/_meta/`
 
-**Available skills (fh-meta, 34)**: agent-composer · fh · apex-review · asset-placement-gate · auto-decorrelation · context-doctor · contention-layer · corpus-grounding-expander · cross-ecosystem-synergy-detection · deep-clarify · edit-manifest · field-harvest · frontier-digest · goal-quench · harness-doctor · harvest-loop · hub-cc-pr-reviewer · install-doctor · install-wizard · marketplace-gate · memory-hygiene · meta-prompt-builder · persona-roster-expander · phantom-quench · pipeline-conductor · plugin-recommender · prompt-regression · public-surface-audit · return-path-gate · sim-conductor · salience-splitter · steel-quench · verify-bidirectional · video-ingest
+**Available skills (fh-meta, 35)**: agent-composer · dialogue-harvest · fh · apex-review · asset-placement-gate · auto-decorrelation · context-doctor · contention-layer · corpus-grounding-expander · cross-ecosystem-synergy-detection · deep-clarify · edit-manifest · field-harvest · frontier-digest · goal-quench · harness-doctor · harvest-loop · hub-cc-pr-reviewer · install-doctor · install-wizard · marketplace-gate · memory-hygiene · meta-prompt-builder · persona-roster-expander · phantom-quench · pipeline-conductor · plugin-recommender · prompt-regression · public-surface-audit · return-path-gate · sim-conductor · salience-splitter · steel-quench · verify-bidirectional · video-ingest
 
 **Available skills (fh-commons)**: convergence-loop · deliberation · mcp-circuit-breaker · token-budget-gate