@lmzhen/dsh-evolution-core 0.1.0 → 0.2.0-rc.2

package/lib/index.js

@@ -374,6 +374,17 @@ function latestActivityAt(record) {
 	return values.sort().reverse()[0] ?? null;
 }
 /**
+* Whether the library has ANY observed read evidence (C observation window):
+* reads were invisible to the usage sidecar before A2, so `view_count` zero
+* means "never read" ONLY after the first observed read exists anywhere in
+* the map. Before that, churn-based signals (write-ghost) are untrustworthy
+* and callers must suppress them. Pure and derived — never persisted.
+*/
+function usageObserved(usage) {
+	for (const record of usage.values()) if (record.view_count > 0) return true;
+	return false;
+}
+/**
 * Curator suppression sidecar: built-in skills the curator has archived stay
 * suppressed across re-seeds, so the lifecycle never fights a re-created
 * bundled skill. Best-effort load/save, mirroring the usage sidecar posture.
@@ -598,11 +609,18 @@ function parseCuratorNominations(text) {
 	const consolidations = [];
 	let section = null;
 	let currentFrom = "";
+	let currentMode;
 	for (const line of text.split("\n")) {
 		const consolidated = /^\s*-\s*from:\s*([a-z0-9][a-z0-9-]*)\s*$/.exec(line);
 		if (consolidated) {
 			section = "consolidations";
 			currentFrom = consolidated[1] ?? "";
+			currentMode = void 0;
+			continue;
+		}
+		const mode = /^\s*mode:\s*(append|reference)\s*$/.exec(line);
+		if (mode) {
+			if (currentFrom !== "") currentMode = mode[1] === "reference" ? "reference" : "append";
 			continue;
 		}
 		const into = /^\s*into:\s*([a-z0-9][a-z0-9-]*)\s*$/.exec(line);
@@ -610,9 +628,11 @@ function parseCuratorNominations(text) {
 			const intoName = into[1] ?? "";
 			if (section === "consolidations" && currentFrom !== "" && currentFrom !== intoName) consolidations.push({
 				from: currentFrom,
-				into: intoName
+				into: intoName,
+				...currentMode === void 0 ? {} : { mode: currentMode }
 			});
 			currentFrom = "";
+			currentMode = void 0;
 			continue;
 		}
 		const pruned = /^\s*-\s*name:\s*([a-z0-9][a-z0-9-]*)\s*$/.exec(line);
@@ -748,6 +768,15 @@ function computeLifecycleTransitions(usage, config, now = /* @__PURE__ */ new Da
 * learn on target X" is answerable. The aggregate `feedback.json` is a
 * rebuildable boot cache, never the truth.
 *
+* Usage events (C semantics, rc.73+): `type:'usage'` records are the
+* OBSERVATION WINDOW ANCHOR — written once, when the library's first observed
+* read (`view_count` 0 -> 1) happens. Before that anchor the usage sidecar
+* has no read evidence (reads were invisible pre-A2), so churn-based health
+* judgments are NOT trustworthy; the curator suppresses them (its
+* `usageObserved()` gate) until the anchor exists. `counts` on the event is a
+* cumulative library-wide snapshot (skills/views/use/patches) at that moment,
+* and `window.opened` pins the window start for the timeline.
+*
 * Rotation (rc.71, 007 design): when the active log reaches
 * `EVENT_LOG_ROTATE_AT` the older half is split into an archive
 * (`events-<lastArchivedSeq>.json`); the boot timeline merges active +
@@ -969,8 +998,8 @@ async function readEvolutionTimeline(io, path) {
 * changes semantically: the bundle digest is the fail-closed signal for
 * review workers, so a stale id across deployments must be distinguishable.
 */
-const PROMPT_BUNDLE_ID = "dsh-evolution@7";
-const PROMPT_BUNDLE_VERSION = 7;
+const PROMPT_BUNDLE_ID = "dsh-evolution@9";
+const PROMPT_BUNDLE_VERSION = 9;
 const MEMORY_REVIEW_PROMPT = `[Auto-review — Memory]
 Review the conversation above and consider saving to memory if appropriate.
 
@@ -1001,7 +1030,8 @@ Preference order — prefer the earliest action that fits, but do pick one when
      • templates/<name>.<ext> — starter files meant to be copied and modified (boilerplate configs, scaffolding, a known-good example the agent can reproduce with modifications).
      • scripts/<name>.<ext> — statically re-runnable actions the skill can invoke directly (verification scripts, fixture generators, deterministic probes, anything the agent should run rather than hand-type each time).
      Add support files via skill_manage action=write_file with file_path starting 'references/', 'templates/', or 'scripts/'. The umbrella's SKILL.md should gain a one-line pointer to any new support file so future agents know it exists.
-  4. CREATE A NEW CLASS-LEVEL UMBRELLA SKILL when no existing skill covers the class. The name MUST be at the class level. The name MUST NOT be a specific PR number, error string, feature codename, library-alone name, or 'fix-X / debug-Y / audit-Z-today' session artifact. If the proposed name only makes sense for today's task, it's wrong — fall back to (1), (2), or (3).
+  4. RESTRUCTURE a loaded skill whose body grew log-like — rc/sha/date-dense sections, session-detail spirals, or a fat body with no support files. Use skill_manage action=restructure with restructure: [{"heading": "<the exact ## heading text>", "to_file": "references/<topic>.md"}] — the ENTIRE ## section (from that heading to the next heading) moves into the support file and its position becomes a pointer line. The skill's name and directory never change. Only propose headings that exist verbatim in the body; never invent one, and never restructure a healthy small skill.
+  5. CREATE A NEW CLASS-LEVEL UMBRELLA SKILL when no existing skill covers the class. The name MUST be at the class level. The name MUST NOT be a specific PR number, error string, feature codename, library-alone name, or 'fix-X / debug-Y / audit-Z-today' session artifact. If the proposed name only makes sense for today's task, it's wrong — fall back to (1), (2), or (3).
 
 User-preference embedding (important): when the user expressed a style/format/workflow preference, the update belongs in the SKILL.md body, not just in memory. Memory captures 'who the user is and what the current situation and state of your operations are'; skills capture 'how to do this class of task for this user'. When they complain about how you handled a task, the skill that governs that task needs to carry the lesson.
 
@@ -1046,7 +1076,8 @@ Preference order for skills — pick the earliest that fits:
   1. UPDATE A CURRENTLY-LOADED SKILL. Check what skills were loaded or read in the conversation. If one of them covers the learning, PATCH it first. It was in play; it's the right place.
   2. UPDATE AN EXISTING UMBRELLA. Patch it.
   3. ADD A SUPPORT FILE under an existing umbrella via skill_manage action=write_file. Three kinds: references/<topic>.md for session-specific detail OR condensed knowledge banks (quoted research, API docs excerpts, domain notes) written concise and task-focused; templates/<name>.<ext> for starter files meant to be copied and modified; scripts/<name>.<ext> for statically re-runnable actions (verification, fixture generators, probes). Add a one-line pointer in SKILL.md so future agents find them.
-  4. CREATE A NEW CLASS-LEVEL UMBRELLA when nothing exists. Name at the class level — NOT a PR number, error string, codename, library-alone name, or 'fix-X / debug-Y' session artifact. If the name only fits today's task, fall back to (1), (2), or (3).
+  4. RESTRUCTURE a loaded skill whose body grew log-like (rc/sha/date-dense sections, session-detail spirals, fat body with no support files) via skill_manage action=restructure with restructure: [{"heading": "<the exact ## heading text>", "to_file": "references/<topic>.md"}] — the ENTIRE ## section moves into the support file and its position becomes a pointer line; the skill's name and directory never change. Only propose headings that exist verbatim in the body.
+  5. CREATE A NEW CLASS-LEVEL UMBRELLA when nothing exists. Name at the class level — NOT a PR number, error string, codename, library-alone name, or 'fix-X / debug-Y' session artifact. If the name only fits today's task, fall back to (1), (2), or (3).
 
 Two-tier deposition discipline (DSH addition): classify before writing — PATTERN (symptom → mechanism → fix → verification) goes in the SKILL.md body; LOG (commit SHAs, npm/profile states, this release's change list, this session's narrative) goes in a references/ file. Body density IS reuse rate; a pattern fits in 2-8 physical lines.
 
@@ -1112,6 +1143,7 @@ When done, write a human summary THEN the structured machine-readable block. The
 \`\`\`yaml
 consolidations:
   - from: <old-skill-name>
+    mode: reference  # optional — ONLY for a 'demote': source is narrow-but-valuable session detail, write it as references/<source>.md under the umbrella instead of appending to the body. Default is append. Place this line BEFORE into:. NEVER use reference when the source body links its own references/ templates/ scripts/ files.
     into: <umbrella-skill-name>
     reason: <one short sentence — why merged, not just 'similar'>
 prunings:
@@ -1166,12 +1198,12 @@ function sha256(text) {
 function createPromptBundle(prompts) {
 	const canonical = JSON.stringify({
 		id: PROMPT_BUNDLE_ID,
-		version: 7,
+		version: 9,
 		prompts: Object.fromEntries(Object.entries(prompts).sort())
 	});
 	return Object.freeze({
 		id: PROMPT_BUNDLE_ID,
-		version: 7,
+		version: 9,
 		prompts: Object.freeze({ ...prompts }),
 		sha256: sha256(canonical)
 	});
@@ -1187,10 +1219,10 @@ const PROMPT_BUNDLE = createPromptBundle({
 	skillsGuidance: SKILLS_GUIDANCE
 });
 function verifyPromptBundle(bundle = PROMPT_BUNDLE) {
-	if (bundle.id !== "dsh-evolution@7" || bundle.version !== 7) return false;
+	if (bundle.id !== "dsh-evolution@9" || bundle.version !== 9) return false;
 	const canonical = JSON.stringify({
 		id: PROMPT_BUNDLE_ID,
-		version: 7,
+		version: 9,
 		prompts: Object.fromEntries(Object.entries(bundle.prompts).sort())
 	});
 	return bundle.sha256 === sha256(canonical);
@@ -2167,6 +2199,61 @@ function computePrefixClusters(names) {
 	})).sort((a, b) => b.members.length - a.members.length || a.key.localeCompare(b.key));
 }
 //#endregion
+//#region lib/types/skill-health.js
+/**
+* Skill structure-health domain (rc.73 A1, 008 design): a SECOND assessment
+* dimension beside the six-factor usage quality — document hygiene, consumed
+* by the curator health view and the `/evolution skills health` command.
+*
+* PURE and DERIVED: nothing is persisted; every assessment is computed from
+* file facts at read time. The judgment split follows the original's
+* boundary/治理 layering — deterministic signals here, refinement proposals
+* stay in the review/curator judgment layer. Never become a 7th factor of
+* `computeQualityScores` (different dimension, different consumers).
+*/
+const DEFAULT_HEALTH_THRESHOLDS = {
+	softBodyChars: 4e4,
+	stampDensityPerKb: 2,
+	churnMinPatches: 20
+};
+const HEALTH_STAMP_RE = /\brc\.\d+\b|\b[0-9a-f]{7,40}\b|\b\d{4}-\d{2}-\d{2}(?:T[0-9:.]+Z)?\b/g;
+/**
+* Bodies below this size skip stamp-density assessment: a few dates or shas
+* in a short body are ordinary documentation, not log-like content. With the
+* 1KB density floor a 3-date sentence in a small skill measured 3.0/KB and
+* warned on a perfectly healthy body (audit 2026-08-31 X1).
+*/
+const MIN_STAMP_BODY_CHARS = 2e3;
+function assessStructureHealth(snapshot, thresholds = DEFAULT_HEALTH_THRESHOLDS) {
+	const reasons = [];
+	const dims = {
+		bodyChars: snapshot.bodyChars,
+		stampDensityPerKb: null,
+		supportGroups: snapshot.supportGroups,
+		churnPatches: null,
+		churnReads: null
+	};
+	const needs = snapshot.bodyChars >= thresholds.softBodyChars * 2;
+	if (needs) reasons.push(`body ${snapshot.bodyChars} chars is >= 2x the soft limit (${thresholds.softBodyChars}) — consider splitting or offloading`);
+	else if (snapshot.bodyChars >= thresholds.softBodyChars) reasons.push(`body ${snapshot.bodyChars} chars above the soft limit (${thresholds.softBodyChars})`);
+	if (snapshot.bodyText && snapshot.bodyChars >= MIN_STAMP_BODY_CHARS) {
+		const kb = Math.max(1, snapshot.bodyChars / 1024);
+		dims.stampDensityPerKb = (snapshot.bodyText.match(HEALTH_STAMP_RE) ?? []).length / kb;
+		if (dims.stampDensityPerKb >= thresholds.stampDensityPerKb) reasons.push(`stamp density ${dims.stampDensityPerKb.toFixed(1)}/KB (rc/sha/date lines — log-like content in the body)`);
+	}
+	if (snapshot.supportGroups === 0 && snapshot.bodyChars >= thresholds.softBodyChars / 2) reasons.push(`large body (${snapshot.bodyChars} chars) with NO support files — session detail may belong in references/`);
+	if (snapshot.patchCount !== void 0 && snapshot.readCount !== void 0) {
+		dims.churnPatches = snapshot.patchCount;
+		dims.churnReads = snapshot.readCount;
+		if (snapshot.patchCount >= thresholds.churnMinPatches && snapshot.readCount === 0) reasons.push(`patched ${snapshot.patchCount} times but never read (write-ghost — content may be dead)`);
+	}
+	return {
+		verdict: needs ? "needs-restructure" : reasons.length > 0 ? "warn" : "healthy",
+		dims,
+		reasons
+	};
+}
+//#endregion
 //#region lib/types/signals.js
 /**
 * Deterministic review signal gate.
@@ -2259,6 +2346,10 @@ const DEFAULT_SKILL_LIMITS = {
 	maxSkillContentChars: MAX_SKILL_CONTENT_CHARS,
 	maxSkillFileBytes: MAX_SKILL_FILE_BYTES
 };
+/** Upper bound of moves per restructure proposal (validator and core agree). */
+const MAX_RESTRUCTURE_MOVES = 5;
+/** Restructure targets are plain markdown files under references/ — no subdirectories, no other support kind. */
+const RESTRUCTURE_TARGET_RE = /^references\/[a-z0-9][a-z0-9._-]*\.md$/;
 /** Extra file name carried inside a snapshot's `extras/` directory. */
 const SNAPSHOT_EXTRA_NAME_RE = /^[a-z0-9][a-z0-9._-]*$/;
 function skillsRoot(env = process.env) {
@@ -2350,7 +2441,7 @@ function validateFrontmatter(content, expectedName, limits = DEFAULT_SKILL_LIMIT
 	if (expectedName && parsed.frontmatter.name !== expectedName) return `Frontmatter name "${parsed.frontmatter.name}" does not match target skill "${expectedName}".`;
 	if (!parsed.frontmatter.description) return "Frontmatter must include a description field.";
 	if (parsed.frontmatter.description.length > limits.maxDescriptionLength) return `Description exceeds ${limits.maxDescriptionLength} characters.`;
-	if (content.length > limits.maxSkillContentChars) return `SKILL.md content exceeds ${limits.maxSkillContentChars} characters.`;
+	if (content.length > limits.maxSkillContentChars) return `SKILL.md content exceeds ${limits.maxSkillContentChars} characters. Consider splitting into a smaller SKILL.md with supporting files.`;
 	return null;
 }
 /** Hermes authoring quality bar for descriptions (the 60-char Rule). The
@@ -2480,6 +2571,62 @@ function fuzzyPatch(content, oldString, newString, replaceAll = false) {
 	}
 	return null;
 }
+/**
+* Support-directory references in a markdown body (009 kernel): `references/…`,
+* `templates/…`, `scripts/…`, `assets/…` relative links. Pure — who checks
+* them and what the verdict is belongs to the caller's context (a moved/
+* appended body whose references travel with an archived source is a dangling
+* link; a restructure pointer is a fresh link to a file written in the same
+* plan).
+*/
+function supportRefs(content) {
+	const refs = [];
+	for (const match of content.matchAll(/\b(?:references|templates|scripts|assets)\/[A-Za-z0-9._-]+\.md/g)) refs.push(match[0]);
+	return refs;
+}
+function planRestructureSections(body, moves) {
+	const lines = body.split("\n");
+	const spans = [];
+	for (const move of moves) {
+		const wanted = move.heading.trim();
+		const starts = [];
+		for (let i = 0; i < lines.length; i += 1) if ((/^#{2}\s+(.+?)\s*$/.exec(lines[i] ?? "")?.[1]?.trim() ?? "") === wanted) starts.push(i);
+		const [start] = starts;
+		if (start === void 0) return { error: `no "## ${wanted}" heading in the body` };
+		if (starts.length > 1) return { error: `heading "## ${wanted}" appears ${starts.length} times (ambiguous anchor)` };
+		let end = lines.length;
+		for (let i = start + 1; i < lines.length; i += 1) if (/^#{2}\s/.test(lines[i] ?? "")) {
+			end = i;
+			break;
+		}
+		if (end === start + 1) return { error: `heading "## ${wanted}" has an empty section` };
+		if (spans.some((span) => start === span.start)) return { error: `heading "## ${wanted}" is moved twice` };
+		spans.push({
+			start,
+			end,
+			rel: move.toFile,
+			heading: wanted,
+			text: lines.slice(start, end).join("\n")
+		});
+	}
+	const byStart = new Map(spans.map((span) => [span.start, span]));
+	const rebuilt = [];
+	for (let i = 0; i < lines.length; i += 1) {
+		const span = byStart.get(i);
+		if (span) {
+			rebuilt.push(`> 详见 references/${span.rel.split("/").at(-1)}`);
+			i = span.end - 1;
+		} else rebuilt.push(lines[i] ?? "");
+	}
+	return {
+		body: rebuilt.join("\n"),
+		sections: spans.map(({ rel, heading, text }) => ({
+			rel,
+			heading,
+			text
+		}))
+	};
+}
 var SkillLibrary = class {
 	root;
 	limits;
@@ -2603,6 +2750,25 @@ var SkillLibrary = class {
 		}
 		return count;
 	}
+	/**
+	* Structure-health facts for one skill (rc.73 A1, 008 design): body
+	* chars/density from SKILL.md, support groups from countSupportDirs, plus
+	* optional usage counts (A2 churn dimension) when the caller has them.
+	* Derived, never persisted; null when the skill is unreadable.
+	*/
+	async assessHealth(rawName, thresholds = DEFAULT_HEALTH_THRESHOLDS, counts) {
+		const name = rawName.trim();
+		const content = await this.read(name);
+		if (content === null) return null;
+		return assessStructureHealth({
+			skillName: name,
+			bodyChars: content.length,
+			bodyText: content,
+			supportGroups: await this.countSupportDirs(name),
+			patchCount: counts?.patchCount,
+			readCount: counts?.readCount
+		}, thresholds);
+	}
 	/** Best-effort audit trail entry; never blocks the mutation. */
 	async audit(skillName, action, before, after, summary) {
 		try {
@@ -2790,7 +2956,7 @@ var SkillLibrary = class {
 		};
 		if (patched.length > this.limits.maxSkillContentChars && target === skillMd) return {
 			ok: false,
-			message: `Patched content exceeds ${this.limits.maxSkillContentChars} characters.`
+			message: `Patched content exceeds ${this.limits.maxSkillContentChars} characters. Consider splitting into a smaller SKILL.md with supporting files.`
 		};
 		const threat = scanContentThreats(patched);
 		if (threat) return {
@@ -2871,10 +3037,24 @@ var SkillLibrary = class {
 	* Merge the bodies of `sources` into `target` and archive the sources with
 	* an absorbed-into marker. Hermes-style consolidation: overlapping skills
 	* collapse into one, and the originals stay recoverable under `.archive/`.
+	*
+	* `mode:'append'` (default) appends each source body to the target. The
+	* target write goes through the tree-change kernel (009) — byte-level
+	* rollback, audit and the mutation event are kernel-owned. Package-integrity
+	* (009-I): append-mode consolidation REFUSES a source whose directory has
+	* support files or whose body carries support-directory links — an append
+	* would leave those references pointing at an archived package (dangling);
+	* the refusal message directs to the reference mode / whole-package archive.
+	*
+	* `mode:'reference'` writes each source's body (frontmatter stripped) into
+	* `target/references/<source>.md` and archives the source — the demote path
+	* (009-II). A source body with support-directory links is refused there too
+	* (the references file would carry links whose files were archived).
 	*/
-	async consolidate(target, sources, origin = "foreground") {
+	async consolidate(target, sources, origin = "foreground", options = {}) {
 		const targetName = target.trim();
 		const normalizedSources = [...new Set(sources.map((name) => name.trim()))].filter((name) => name !== targetName);
+		const mode = options.mode ?? "append";
 		if (normalizedSources.length === 0) return {
 			ok: false,
 			message: "Consolidation requires at least one distinct source skill."
@@ -2894,36 +3074,86 @@ var SkillLibrary = class {
 			ok: false,
 			message: `Skill "${targetName}" is protected (${targetProtection}).`
 		};
-		const parts = [];
-		for (const source of normalizedSources) {
-			const protection = await this.deleteProtection(source);
-			if (protection) return {
-				ok: false,
-				message: `Skill "${source}" is protected (${protection}).`
-			};
-			const sourceMd = await this.io.readText(join(this.dirOf(source), "SKILL.md"));
-			if (!sourceMd) return {
+		const writes = [];
+		if (mode === "append") {
+			const parts = [];
+			for (const source of normalizedSources) {
+				const protection = await this.deleteProtection(source);
+				if (protection) return {
+					ok: false,
+					message: `Skill "${source}" is protected (${protection}).`
+				};
+				const sourceMd = await this.io.readText(join(this.dirOf(source), "SKILL.md"));
+				if (!sourceMd) return {
+					ok: false,
+					message: `Skill "${source}" not found.`
+				};
+				const parsed = parseFrontmatter(sourceMd);
+				if (!parsed) return {
+					ok: false,
+					message: `Skill "${source}" has no valid frontmatter; refusing to merge.`
+				};
+				if (await this.countSupportDirs(source) > 0) return {
+					ok: false,
+					message: `Consolidation rejected: source "${source}" carries support files — use mode:'reference' or archive the whole package instead.`
+				};
+				const refs = supportRefs(parsed.body);
+				if (refs.length > 0) return {
+					ok: false,
+					message: `Consolidation rejected: source "${source}" body references support files (${refs.join(", ")}) that would be left behind — use mode:'reference' or archive the whole package instead.`
+				};
+				parts.push(`\n<!-- consolidated from ${source} at ${(/* @__PURE__ */ new Date()).toISOString()} -->\n${parsed.body.trim()}`);
+			}
+			const merged = targetMd.trimEnd() + parts.join("\n") + "\n";
+			const validation = validateFrontmatter(merged, targetName, this.limits);
+			if (validation) return {
 				ok: false,
-				message: `Skill "${source}" not found.`
+				message: `Consolidation rejected: ${validation}`
 			};
-			const parsed = parseFrontmatter(sourceMd);
-			if (!parsed) return {
+			writes.push({
+				target: join(targetDir, "SKILL.md"),
+				content: merged
+			});
+		} else {
+			for (const source of normalizedSources) {
+				const protection = await this.deleteProtection(source);
+				if (protection) return {
+					ok: false,
+					message: `Skill "${source}" is protected (${protection}).`
+				};
+				const sourceMd = await this.io.readText(join(this.dirOf(source), "SKILL.md"));
+				if (!sourceMd) return {
+					ok: false,
+					message: `Skill "${source}" not found.`
+				};
+				const parsed = parseFrontmatter(sourceMd);
+				if (!parsed) return {
+					ok: false,
+					message: `Skill "${source}" has no valid frontmatter; refusing to demote.`
+				};
+				const refs = supportRefs(parsed.body);
+				if (refs.length > 0) return {
+					ok: false,
+					message: `Consolidation rejected: source "${source}" body references support files (${refs.join(", ")}) that would be left behind — archive the whole package instead.`
+				};
+				const target = join(targetDir, "references", `${source}.md`);
+				writes.push({
+					target,
+					content: `<!-- demoted from ${source} at ${(/* @__PURE__ */ new Date()).toISOString()} -->\n${parsed.body.trim()}\n`
+				});
+			}
+			const pointerLines = normalizedSources.map((source) => `\n> 详见 references/${source}.md`).join("");
+			const extended = targetMd.trimEnd() + pointerLines + "\n";
+			const validation = validateFrontmatter(extended, targetName, this.limits);
+			if (validation) return {
 				ok: false,
-				message: `Skill "${source}" has no valid frontmatter; refusing to merge.`
+				message: `Consolidation rejected: ${validation}`
 			};
-			parts.push(`\n<!-- consolidated from ${source} at ${(/* @__PURE__ */ new Date()).toISOString()} -->\n${parsed.body.trim()}`);
+			writes.push({
+				target: join(targetDir, "SKILL.md"),
+				content: extended
+			});
 		}
-		const merged = targetMd.trimEnd() + parts.join("\n") + "\n";
-		const validation = validateFrontmatter(merged, targetName, this.limits);
-		if (validation) return {
-			ok: false,
-			message: `Consolidation rejected: ${validation}`
-		};
-		const threat = scanContentThreats(merged);
-		if (threat) return {
-			ok: false,
-			message: threat
-		};
 		const archived = [];
 		try {
 			for (const source of normalizedSources) {
@@ -2931,20 +3161,23 @@ var SkillLibrary = class {
 				if (!result.ok) throw new Error(result.message);
 				archived.push(source);
 			}
-			await this.io.writeText(join(targetDir, "SKILL.md"), merged);
+			const result = await this.applyTreeChange({
+				name: targetName,
+				origin,
+				protection: "write",
+				writes,
+				auditAction: "consolidate",
+				auditSummary: `consolidated ${normalizedSources.join(", ")} (${mode}) into ${targetName}`,
+				eventAction: "consolidate"
+			});
+			if (!result.ok) throw new Error(result.message);
 		} catch (error) {
-			await this.io.writeText(join(targetDir, "SKILL.md"), targetMd).catch(() => {});
 			for (const source of archived.reverse()) await this.restoreFromArchive(source).catch(() => {});
 			return {
 				ok: false,
 				message: `Consolidation failed and was rolled back: ${error instanceof Error ? error.message : String(error)}`
 			};
 		}
-		this.notifyMutation({
-			action: "consolidate",
-			name: targetName,
-			filePath: targetDir
-		});
 		return {
 			ok: true,
 			message: `Consolidated ${normalizedSources.join(", ")} into "${targetName}".`,
@@ -2952,6 +3185,197 @@ var SkillLibrary = class {
 		};
 	}
 	/**
+	* Content-distribution repair (008 batch B, 009-R kernel): move body
+	* sections — anchored by their exact `## heading` lines — into references/
+	* support files and replace each span with a pointer line. The skill
+	* name/dir never change (routing stays; only content location shifts, so a
+	* fat body sheds its log-like detail). Deterministic, never automatic:
+	* candidates come from an approved review plan. The write batch goes
+	* through the tree-change kernel — one commit point, byte-level rollback.
+	* Package integrity (009-R): a moved section whose text carries
+	* support-directory links is refused (those links' files stay behind in the
+	* same package; the moved text belongs in references/ beside them).
+	*/
+	async restructure(rawName, moves, origin = "foreground") {
+		const name = rawName.trim();
+		const badName = this.badName(name);
+		if (badName) return {
+			ok: false,
+			message: badName
+		};
+		if (moves.length === 0) return {
+			ok: false,
+			message: "Restructure requires at least one section move."
+		};
+		if (moves.length > 5) return {
+			ok: false,
+			message: `Restructure exceeds 5 moves.`
+		};
+		for (const move of moves) {
+			if (typeof move.heading !== "string" || !move.heading.trim()) return {
+				ok: false,
+				message: "Every restructure move needs a non-empty heading."
+			};
+			if (!RESTRUCTURE_TARGET_RE.test(move.toFile)) return {
+				ok: false,
+				message: `toFile must be references/<topic>.md (got "${move.toFile}").`
+			};
+		}
+		const dir = this.dirOf(name);
+		const md = await this.io.readText(join(dir, "SKILL.md"));
+		if (!md) return {
+			ok: false,
+			message: `Skill "${name}" not found.`
+		};
+		const normalized = md.replace(/\r\n/g, "\n");
+		const plan = planRestructureSections(normalized, moves);
+		if ("error" in plan) return {
+			ok: false,
+			message: `Restructure rejected: ${plan.error}`
+		};
+		const frontmatterEnd = normalized.indexOf("\n---", 3);
+		if (frontmatterEnd < 0) return {
+			ok: false,
+			message: "SKILL.md has no valid frontmatter; refusing to restructure."
+		};
+		const newMd = normalized.slice(0, frontmatterEnd + 4) + plan.body;
+		const newMdCheck = validateFrontmatter(newMd, name, this.limits);
+		if (newMdCheck) return {
+			ok: false,
+			message: `Restructure rejected: ${newMdCheck}`
+		};
+		for (const section of plan.sections) {
+			const refs = supportRefs(section.text);
+			if (refs.length > 0) return {
+				ok: false,
+				message: `Restructure rejected: section "## ${section.heading}" references support files (${refs.join(", ")}) that stay behind — split the section or move it with its files.`
+			};
+		}
+		const byRel = /* @__PURE__ */ new Map();
+		for (const section of plan.sections) {
+			const entry = byRel.get(section.rel) ?? {
+				rel: section.rel,
+				texts: []
+			};
+			entry.texts.push(section.text);
+			byRel.set(section.rel, entry);
+		}
+		const writes = [];
+		for (const entry of byRel.values()) {
+			const target = join(dir, ...entry.rel.split("/"));
+			const base = (await this.io.readText(target).catch(() => null))?.trimEnd() ?? "";
+			writes.push({
+				target,
+				content: base === "" ? entry.texts.join("\n\n") : `${base}\n\n${entry.texts.join("\n\n")}`
+			});
+		}
+		writes.push({
+			target: join(dir, "SKILL.md"),
+			content: newMd
+		});
+		const result = await this.applyTreeChange({
+			name,
+			origin,
+			protection: "write",
+			writes,
+			auditAction: "restructure",
+			auditSummary: `moved ${plan.sections.length} section(s): ${[...byRel.keys()].join(", ")}`,
+			eventAction: "restructure"
+		});
+		if (!result.ok) return result;
+		return {
+			ok: true,
+			message: `Restructured "${name}": moved ${plan.sections.length} section(s) to references/.`,
+			path: dir
+		};
+	}
+	/**
+	* Unified tree-change commit point (009 kernel): owns validation order,
+	* pre-read rollback bytes, two-phase write with byte-level rollback, audit
+	* and the mutation event. Mutators compose `TreeChangePlan`s — consolidate,
+	* restructure (and future reference-mode consolidations) never implement
+	* two-phase commit themselves.
+	*/
+	async applyTreeChange(plan) {
+		const name = plan.name.trim();
+		const badName = this.badName(name);
+		if (badName) return {
+			ok: false,
+			message: badName
+		};
+		const dir = this.dirOf(name);
+		const md = await this.io.readText(join(dir, "SKILL.md"));
+		if (!md) return {
+			ok: false,
+			message: `Skill "${name}" not found.`
+		};
+		const protection = plan.protection === "write" ? await this.writeProtection(name, plan.origin) : plan.protection === "delete" ? await this.deleteProtection(name) : null;
+		if (protection) return {
+			ok: false,
+			message: `Skill "${name}" is protected (${protection}).`
+		};
+		for (const precondition of plan.preconditions ?? []) {
+			const issue = await precondition({ dir });
+			if (issue) return {
+				ok: false,
+				message: issue
+			};
+		}
+		const landing = [];
+		for (const write of plan.writes) {
+			const previous = await this.io.readText(write.target).catch(() => null);
+			if (Buffer.byteLength(write.content, "utf8") > this.limits.maxSkillFileBytes) return {
+				ok: false,
+				message: `Write exceeds ${this.limits.maxSkillFileBytes} bytes: ${write.target}`
+			};
+			const threat = scanContentThreats(write.content);
+			if (threat) return {
+				ok: false,
+				message: threat
+			};
+			landing.push({
+				target: write.target,
+				content: write.content,
+				previous
+			});
+		}
+		const semantic = plan.validate?.({
+			dir,
+			currentMd: md
+		}) ?? null;
+		if (semantic) return {
+			ok: false,
+			message: semantic
+		};
+		const written = [];
+		try {
+			for (const entry of landing) {
+				await this.io.writeText(entry.target, entry.content);
+				written.push({
+					target: entry.target,
+					previous: entry.previous
+				});
+			}
+		} catch (error) {
+			for (const entry of written.reverse()) await (entry.previous === null ? this.io.remove(entry.target) : this.io.writeText(entry.target, entry.previous)).catch(() => {});
+			return {
+				ok: false,
+				message: `Tree change failed and was rolled back: ${error instanceof Error ? error.message : String(error)}`
+			};
+		}
+		await this.audit(name, plan.auditAction, md, landing.find((entry) => entry.target.endsWith("SKILL.md"))?.content ?? md, plan.auditSummary);
+		this.notifyMutation({
+			action: plan.eventAction,
+			name,
+			filePath: dir
+		});
+		return {
+			ok: true,
+			message: `${plan.eventAction} "${name}" succeeded.`,
+			path: dir
+		};
+	}
+	/**
 	* Restore one skill from `.archive/` back to the active root. Hermes-style
 	* recoverability: archival never deletes, and this is the control-plane
 	* path back. The `.archive-reason` marker is dropped on restore.
@@ -3262,4 +3686,4 @@ function evolutionHome(env = process.env) {
 	return join(env.DSH_HOME ?? join(homedir(), ".dsh"), "evolution");
 }
 //#endregion
-export { AUTHORING_DESCRIPTION_BAR, COMBINED_REVIEW_PLAN_PROMPT, COMBINED_REVIEW_PROMPT, COMPLETION_SKILL_REVIEW_PROMPT, CURATOR_DRY_RUN_BANNER, CURATOR_PROMPT, DEFAULT_ARCHIVE_AFTER_DAYS, DEFAULT_CONSOLIDATION_FAILURES, DEFAULT_CURATOR_INTERVAL_HOURS, DEFAULT_MAX_OPS_PER_PLAN, DEFAULT_MEMORY_CHAR_LIMIT, DEFAULT_MIN_IDLE_HOURS, DEFAULT_MUTATION_CAP, DEFAULT_REVIEW_MEMORY_INTERVAL, DEFAULT_REVIEW_SKILL_INTERVAL, DEFAULT_SKILL_CONTENT_CHARS, DEFAULT_SKILL_LIMITS, DEFAULT_SKILL_REVIEW_COMPLETION_MIN_TOOL_CALLS, DEFAULT_SKILL_REVIEW_TRIGGER, DEFAULT_STALE_AFTER_DAYS, DEFAULT_SUBSTANTIVE_MIN_AGENT_CHARS, DEFAULT_SUBSTANTIVE_MIN_TOOL_CALLS, DEFAULT_SUBSTANTIVE_MIN_USER_CHARS, DEFAULT_USER_CHAR_LIMIT, DSH_AUTHORING_STANDARDS, ENTRY_DELIMITER, EVENT_ARCHIVE_PREFIX, EVENT_LOG_RETAIN_ARCHIVES, EVENT_LOG_ROTATE_AT, EVENT_LOG_VERSION, EvolutionGateSet, LOW_QUALITY_THRESHOLD, MAX_DESCRIPTION_LENGTH, MAX_SKILL_CONTENT_CHARS, MAX_SKILL_FILE_BYTES, MAX_SKILL_NAME_LENGTH, MEMORY_REVIEW_PROMPT, MUTATIONS_FILE_VERSION, MemoryStore, PROMPT_BUNDLE, PROMPT_BUNDLE_ID, PROMPT_BUNDLE_VERSION, PROTECTED_BUILTIN_SKILLS, QUALITY_WEIGHTS, SKILLS_GUIDANCE, SKILL_NAME_RE, SKILL_REVIEW_PLAN_PROMPT, SKILL_REVIEW_PROMPT, SNAPSHOT_EXTRA_NAME_RE, SUPPORT_DIRS, SUPPRESSED_FILE_VERSION, SkillLibrary, advanceReview, appendEvolutionEvent, applyCuratorFields, applyCuratorLifecycleFields, applyCuratorMetaFields, authoringFeedback, buildCuratorRunReport, buildLearnPrompt, bumpPatch, bumpUse, bumpView, computeDedupGroups, computeLifecycleTransitions, computePrefixClusters, computeQualityScores, computeScopeView, contentHash, createGateSet, emptyRecord, evaluateThreat, eventsFile, evolutionHome, evolutionIoAdapter, foldCuratorFields, foldTurn, getRecord, latestActivityAt, lifecycleCandidate, listEventArchives, loadMutations, loadSuppressedNames, loadUsage, markAgentCreated, memoryRoot, mutateUsage, mutationsFile, nodeEvolutionIo, normalizeUsageRecord, observeEvent, parseCuratorNominations, parseEvolutionEvents, parseFrontmatter, readEvolutionEvents, readEvolutionTimeline, recordMutation, relatedSkillNames, renderCuratorReportMarkdown, resolveOrigins, retainEventArchives, reviewPrompt, saveSuppressedNames, saveUsage, scanContentThreats, scanMemoryThreats, scanThreats, skillsRoot, suppressedFile, transactIo, updateSuppressedNames, usageFile, validateFrontmatter, verifyPromptBundle };
+export { AUTHORING_DESCRIPTION_BAR, COMBINED_REVIEW_PLAN_PROMPT, COMBINED_REVIEW_PROMPT, COMPLETION_SKILL_REVIEW_PROMPT, CURATOR_DRY_RUN_BANNER, CURATOR_PROMPT, DEFAULT_ARCHIVE_AFTER_DAYS, DEFAULT_CONSOLIDATION_FAILURES, DEFAULT_CURATOR_INTERVAL_HOURS, DEFAULT_HEALTH_THRESHOLDS, DEFAULT_MAX_OPS_PER_PLAN, DEFAULT_MEMORY_CHAR_LIMIT, DEFAULT_MIN_IDLE_HOURS, DEFAULT_MUTATION_CAP, DEFAULT_REVIEW_MEMORY_INTERVAL, DEFAULT_REVIEW_SKILL_INTERVAL, DEFAULT_SKILL_CONTENT_CHARS, DEFAULT_SKILL_LIMITS, DEFAULT_SKILL_REVIEW_COMPLETION_MIN_TOOL_CALLS, DEFAULT_SKILL_REVIEW_TRIGGER, DEFAULT_STALE_AFTER_DAYS, DEFAULT_SUBSTANTIVE_MIN_AGENT_CHARS, DEFAULT_SUBSTANTIVE_MIN_TOOL_CALLS, DEFAULT_SUBSTANTIVE_MIN_USER_CHARS, DEFAULT_USER_CHAR_LIMIT, DSH_AUTHORING_STANDARDS, ENTRY_DELIMITER, EVENT_ARCHIVE_PREFIX, EVENT_LOG_RETAIN_ARCHIVES, EVENT_LOG_ROTATE_AT, EVENT_LOG_VERSION, EvolutionGateSet, LOW_QUALITY_THRESHOLD, MAX_DESCRIPTION_LENGTH, MAX_RESTRUCTURE_MOVES, MAX_SKILL_CONTENT_CHARS, MAX_SKILL_FILE_BYTES, MAX_SKILL_NAME_LENGTH, MEMORY_REVIEW_PROMPT, MUTATIONS_FILE_VERSION, MemoryStore, PROMPT_BUNDLE, PROMPT_BUNDLE_ID, PROMPT_BUNDLE_VERSION, PROTECTED_BUILTIN_SKILLS, QUALITY_WEIGHTS, RESTRUCTURE_TARGET_RE, SKILLS_GUIDANCE, SKILL_NAME_RE, SKILL_REVIEW_PLAN_PROMPT, SKILL_REVIEW_PROMPT, SNAPSHOT_EXTRA_NAME_RE, SUPPORT_DIRS, SUPPRESSED_FILE_VERSION, SkillLibrary, advanceReview, appendEvolutionEvent, applyCuratorFields, applyCuratorLifecycleFields, applyCuratorMetaFields, assessStructureHealth, authoringFeedback, buildCuratorRunReport, buildLearnPrompt, bumpPatch, bumpUse, bumpView, computeDedupGroups, computeLifecycleTransitions, computePrefixClusters, computeQualityScores, computeScopeView, contentHash, createGateSet, emptyRecord, evaluateThreat, eventsFile, evolutionHome, evolutionIoAdapter, foldCuratorFields, foldTurn, getRecord, latestActivityAt, lifecycleCandidate, listEventArchives, loadMutations, loadSuppressedNames, loadUsage, markAgentCreated, memoryRoot, mutateUsage, mutationsFile, nodeEvolutionIo, normalizeUsageRecord, observeEvent, parseCuratorNominations, parseEvolutionEvents, parseFrontmatter, readEvolutionEvents, readEvolutionTimeline, recordMutation, relatedSkillNames, renderCuratorReportMarkdown, resolveOrigins, retainEventArchives, reviewPrompt, saveSuppressedNames, saveUsage, scanContentThreats, scanMemoryThreats, scanThreats, skillsRoot, suppressedFile, transactIo, updateSuppressedNames, usageFile, usageObserved, validateFrontmatter, verifyPromptBundle };

package/lib/types/curator.d.ts

@@ -84,10 +84,14 @@ export declare function buildCuratorRunReport(input: CuratorReportInput): Curato
  * stale candidates / LLM nominations).
  */
 export declare function renderCuratorReportMarkdown(report: CuratorRunReport): string;
-/** One LLM-nominated consolidation: `from` merges into the umbrella `into`. */
+/** One LLM-nominated consolidation: `from` merges into the umbrella `into`.
+ * `mode:'reference'` demotes the source (its body becomes
+ * `references/<source>.md` under the umbrella) instead of appending to the
+ * target body (009-II); absent means append. */
 export interface CuratorConsolidation {
     from: string;
     into: string;
+    mode?: 'append' | 'reference' | undefined;
 }
 /** Structured result of the optional curator LLM nomination pass. */
 export interface CuratorNominations {

package/lib/types/evolution-events.d.ts

@@ -6,6 +6,15 @@
  * learn on target X" is answerable. The aggregate `feedback.json` is a
  * rebuildable boot cache, never the truth.
  *
+ * Usage events (C semantics, rc.73+): `type:'usage'` records are the
+ * OBSERVATION WINDOW ANCHOR — written once, when the library's first observed
+ * read (`view_count` 0 -> 1) happens. Before that anchor the usage sidecar
+ * has no read evidence (reads were invisible pre-A2), so churn-based health
+ * judgments are NOT trustworthy; the curator suppresses them (its
+ * `usageObserved()` gate) until the anchor exists. `counts` on the event is a
+ * cumulative library-wide snapshot (skills/views/use/patches) at that moment,
+ * and `window.opened` pins the window start for the timeline.
+ *
  * Rotation (rc.71, 007 design): when the active log reaches
  * `EVENT_LOG_ROTATE_AT` the older half is split into an archive
  * (`events-<lastArchivedSeq>.json`); the boot timeline merges active +
@@ -32,14 +41,27 @@ export interface EvolutionEvent {
     seq: number;
     /** ISO timestamp at append time. */
     at: string;
-    /** Tagged-union discriminator: feedback increments vs learn actions. */
-    type: 'feedback' | 'learn';
+    /** Tagged-union discriminator: feedback increments, learn actions, and
+     * usage observation anchors (C semantics: `usage` events carry the library-
+     * wide count snapshot at the moment the observation window opened). */
+    type: 'feedback' | 'learn' | 'usage';
     target?: string | undefined;
     kind?: 'skill' | 'session' | undefined;
     rating?: 'positive' | 'negative' | undefined;
     note?: string | undefined;
     source?: string | undefined;
     request?: string | undefined;
+    /** Library-wide usage totals (usage events; counts are cumulative, not deltas). */
+    counts?: {
+        skills?: number;
+        views?: number;
+        use?: number;
+        patches?: number;
+    } | undefined;
+    /** Anchor fields for one event (usage: the observation window). */
+    window?: {
+        opened?: string;
+    } | undefined;
 }
 export declare function eventsFile(home: string): string;
 /**

package/lib/types/index.d.ts

@@ -17,6 +17,7 @@ export * from './memory-store.ts';
 export * from './mutations.ts';
 export * from './prompts.ts';
 export * from './quality.ts';
+export * from './skill-health.ts';
 export * from './signals.ts';
 export * from './skill-store.ts';
 export * from './state-store.ts';

package/lib/types/prompts.d.ts

@@ -3,12 +3,12 @@
  * changes semantically: the bundle digest is the fail-closed signal for
  * review workers, so a stale id across deployments must be distinguishable.
  */
-export declare const PROMPT_BUNDLE_ID = "dsh-evolution@7";
-export declare const PROMPT_BUNDLE_VERSION = 7;
+export declare const PROMPT_BUNDLE_ID = "dsh-evolution@9";
+export declare const PROMPT_BUNDLE_VERSION = 9;
 export declare const MEMORY_REVIEW_PROMPT = "[Auto-review \u2014 Memory]\nReview the conversation above and consider saving to memory if appropriate.\n\nFocus on:\n1. Has the user revealed things about themselves \u2014 persona, desires, preferences, or personal details worth remembering?\n2. Has the user expressed expectations about how you should behave, their work style, or ways they want you to operate?\n\nIf something stands out, save it using the memory tool.\nIf nothing is worth saving, just say \"Nothing to save.\" and stop.";
-export declare const SKILL_REVIEW_PROMPT = "[Auto-review \u2014 Skills]\nReview the conversation above and update the skill library. Be ACTIVE \u2014 most sessions produce at least one skill update, even if small. A pass that does nothing is a missed learning opportunity, not a neutral outcome.\n\nTarget shape of the library: CLASS-LEVEL skills, each with a rich SKILL.md and a references/ directory for session-specific detail. Not a long flat list of narrow one-session-one-skill entries. This shapes HOW you update, not WHETHER you update.\n\nSignals to look for (any one of these warrants action):\n  \u2022 User corrected your style, tone, format, legibility, or verbosity. Frustration signals like 'stop doing X', 'this is too verbose', 'don't format like this', 'why are you explaining', 'just give me the answer', 'you always do Y and I hate it', or an explicit 'remember this' are FIRST-CLASS skill signals, not just memory signals. Update the relevant skill(s) to embed the preference so the next session starts already knowing.\n  \u2022 User corrected your workflow, approach, or sequence of steps. Encode the correction as a pitfall or explicit step in the skill that governs that class of task.\n  \u2022 Non-trivial technique, fix, workaround, debugging path, or tool-usage pattern emerged that a future session would benefit from. Capture it.\n  \u2022 A skill that got loaded or consulted this session turned out to be wrong, missing a step, or outdated. Patch it NOW.\n\nRead-before-write (enforced by this channel): update, patch, delete, or write support files ONLY into skills you loaded or read in THIS session \u2014 ops on unread skills are dropped; CREATE of a brand-new umbrella is the only exception.\n\nPreference order \u2014 prefer the earliest action that fits, but do pick one when a signal above fired:\n  1. UPDATE A CURRENTLY-LOADED SKILL. Look back through the conversation for skills the user loaded or you read. If any of them covers the territory of the new learning, PATCH that one first. It is the skill that was in play, so it's the right one to extend.\n  2. UPDATE AN EXISTING UMBRELLA. If no loaded skill fits but an existing class-level skill does, patch it. Add a subsection, a pitfall, or broaden a trigger.\n  3. ADD A SUPPORT FILE under an existing umbrella. Skills can be packaged with three kinds of support files \u2014 use the right directory per kind:\n     \u2022 references/<topic>.md \u2014 session-specific detail (error transcripts, reproduction recipes, provider quirks) AND condensed knowledge banks: quoted research, API docs, external authoritative excerpts, or domain notes you found while working on the problem. Write it concise and for the value of the task, not as a full mirror of upstream docs.\n     \u2022 templates/<name>.<ext> \u2014 starter files meant to be copied and modified (boilerplate configs, scaffolding, a known-good example the agent can reproduce with modifications).\n     \u2022 scripts/<name>.<ext> \u2014 statically re-runnable actions the skill can invoke directly (verification scripts, fixture generators, deterministic probes, anything the agent should run rather than hand-type each time).\n     Add support files via skill_manage action=write_file with file_path starting 'references/', 'templates/', or 'scripts/'. The umbrella's SKILL.md should gain a one-line pointer to any new support file so future agents know it exists.\n  4. CREATE A NEW CLASS-LEVEL UMBRELLA SKILL when no existing skill covers the class. The name MUST be at the class level. The name MUST NOT be a specific PR number, error string, feature codename, library-alone name, or 'fix-X / debug-Y / audit-Z-today' session artifact. If the proposed name only makes sense for today's task, it's wrong \u2014 fall back to (1), (2), or (3).\n\nUser-preference embedding (important): when the user expressed a style/format/workflow preference, the update belongs in the SKILL.md body, not just in memory. Memory captures 'who the user is and what the current situation and state of your operations are'; skills capture 'how to do this class of task for this user'. When they complain about how you handled a task, the skill that governs that task needs to carry the lesson.\n\nIf you notice two existing skills that overlap, note it in your reply \u2014 the background curator handles consolidation at scale.\n\nTwo-tier deposition discipline (DSH addition, same spirit as the umbrella rule): before writing, classify the knowledge:\n  \u2022 PATTERN (reusable \u2014 symptom \u2192 mechanism \u2192 fix \u2192 verification, still valuable next session) belongs in the SKILL.md body.\n  \u2022 LOG (one-off \u2014 commit SHAs, npm/profile states, what this release changed, this session's process narrative) belongs in a references/ file, never the body. Body density IS reuse rate. Keep new entries tight: a pattern fits in 2-8 physical lines; prefer changing the current-state pointer over appending history.\n\nProtected skills (DO NOT edit these):\n  \u2022 Bundled skills (shipped with the platform).\n  \u2022 Hub-installed skills (installed from a hub).\nPinned skills are read-only to THIS background review pass \u2014 the pinned write guard refuses background changes, so only the foreground may update or archive them. Foreground and delegated-subagent writes to pinned skills remain allowed.\nIf the only skills that need updating are protected, say 'Nothing to save.' and stop.\n\nDo NOT capture (these become persistent self-imposed constraints that bite you later when the environment changes):\n  \u2022 Environment-dependent failures: missing binaries, fresh-install errors, post-migration path mismatches, 'command not found', unconfigured credentials, uninstalled packages. The user can fix these \u2014 they are not durable rules.\n  \u2022 Negative claims about tools or features ('browser tools do not work', 'X tool is broken', 'cannot use Y'). These harden into refusals the agent cites against itself for months after the actual problem was fixed.\n  \u2022 Session-specific transient errors that resolved before the conversation ended. If retrying worked, the lesson is the retry pattern, not the original failure.\n  \u2022 One-off task narratives. A user asking 'summarize today's market' or 'analyze this PR' is not a class of work that warrants a skill.\n\nIf a tool failed because of setup state, capture the FIX (install command, config step, env var to set) under an existing setup or troubleshooting skill \u2014 never 'this tool does not work' as a standalone constraint.\n\n'Nothing to save.' is a real option but should NOT be the default. If the session ran smoothly with no corrections and produced no new technique, just say 'Nothing to save.' and stop. Otherwise, act.";
-export declare const COMBINED_REVIEW_PROMPT = "[Auto-review]\nReview the conversation above and update two things:\n\n**Memory**: who the user is. Did the user reveal persona, desires, preferences, personal details, or expectations about how you should behave? Save facts about the user and durable preferences with the memory tool.\n\n**Skills**: how to do this class of task. Be ACTIVE \u2014 most sessions produce at least one skill update. A pass that does nothing is a missed learning opportunity, not a neutral outcome.\n\nTarget shape of the skill library: CLASS-LEVEL skills with a rich SKILL.md and a references/ directory for session-specific detail. Not a long flat list of narrow one-session-one-skill entries.\n\nSignals that warrant a skill update (any one is enough):\n  \u2022 User corrected your style, tone, format, legibility, verbosity, or approach. Frustration is a FIRST-CLASS skill signal, not just a memory signal. 'stop doing X', 'don't format like this', 'I hate when you Y' \u2014 embed the lesson in the skill that governs that task so the next session starts fixed.\n  \u2022 Non-trivial technique, fix, workaround, or debugging path emerged.\n  \u2022 A skill that was loaded or consulted turned out wrong, missing, or outdated \u2014 patch it now.\n\nRead-before-write (enforced by this channel): update, patch, delete, or write support files ONLY into skills you loaded or read in THIS session \u2014 ops on unread skills are dropped; CREATE of a brand-new umbrella is the only exception.\n\nPreference order for skills \u2014 pick the earliest that fits:\n  1. UPDATE A CURRENTLY-LOADED SKILL. Check what skills were loaded or read in the conversation. If one of them covers the learning, PATCH it first. It was in play; it's the right place.\n  2. UPDATE AN EXISTING UMBRELLA. Patch it.\n  3. ADD A SUPPORT FILE under an existing umbrella via skill_manage action=write_file. Three kinds: references/<topic>.md for session-specific detail OR condensed knowledge banks (quoted research, API docs excerpts, domain notes) written concise and task-focused; templates/<name>.<ext> for starter files meant to be copied and modified; scripts/<name>.<ext> for statically re-runnable actions (verification, fixture generators, probes). Add a one-line pointer in SKILL.md so future agents find them.\n  4. CREATE A NEW CLASS-LEVEL UMBRELLA when nothing exists. Name at the class level \u2014 NOT a PR number, error string, codename, library-alone name, or 'fix-X / debug-Y' session artifact. If the name only fits today's task, fall back to (1), (2), or (3).\n\nTwo-tier deposition discipline (DSH addition): classify before writing \u2014 PATTERN (symptom \u2192 mechanism \u2192 fix \u2192 verification) goes in the SKILL.md body; LOG (commit SHAs, npm/profile states, this release's change list, this session's narrative) goes in a references/ file. Body density IS reuse rate; a pattern fits in 2-8 physical lines.\n\nUser-preference embedding: when the user complains about how you handled a task, update the skill that governs that task \u2014 memory alone isn't enough. Memory says 'who the user is and what the current situation and state of your operations are'; skills say 'how to do this class of task for this user'. Both should carry user-preference lessons when relevant.\n\nIf you notice overlapping existing skills, mention it \u2014 the background curator handles consolidation.\n\nProtected skills (DO NOT edit these):\n  \u2022 Bundled skills (shipped with the platform).\n  \u2022 Hub-installed skills (installed from a hub).\nPinned skills are read-only to THIS background review pass \u2014 the pinned write guard refuses background changes, so only the foreground may update or archive them. Foreground and delegated-subagent writes to pinned skills remain allowed.\nIf the only skills that need updating are protected, say 'Nothing to save.' and stop.\n\nDo NOT capture as skills (these become persistent self-imposed constraints that bite you later when the environment changes):\n  \u2022 Environment-dependent failures: missing binaries, fresh-install errors, post-migration path mismatches, 'command not found', unconfigured credentials, uninstalled packages. The user can fix these \u2014 they are not durable rules.\n  \u2022 Negative claims about tools or features ('browser tools do not work', 'X tool is broken', 'cannot use Y'). These harden into refusals the agent cites against itself for months after the actual problem was fixed.\n  \u2022 Session-specific transient errors that resolved before the conversation ended. If retrying worked, the lesson is the retry pattern, not the original failure.\n  \u2022 One-off task narratives. A user asking 'summarize today's market' or 'analyze this PR' is not a class of work that warrants a skill.\n\nIf a tool failed because of setup state, capture the FIX (install command, config step, env var to set) under an existing setup or troubleshooting skill \u2014 never 'this tool does not work' as a standalone constraint.\n\nAct on whichever of the two dimensions has real signal. If genuinely nothing stands out on either, say 'Nothing to save.' and stop \u2014 but don't reach for that conclusion as a default.";
-export declare const CURATOR_PROMPT = "You are the skill curator. Maintain a healthy, class-level skill library, not a flat pile of narrow one-session skills.\n\nThis is an UMBRELLA-BUILDING consolidation pass, not a passive audit and not a duplicate-finder.\n\nThe goal is a LIBRARY OF CLASS-LEVEL INSTRUCTIONS. A skill collection of many narrow skills where each captures one session's specific bug is a FAILURE of the library. An agent searching skills matches on descriptions, not exact names; one broad umbrella with labeled subsections beats five narrow siblings for discoverability.\n\nRight target shape: class-level skills with rich SKILL.md + references/, templates/, scripts/ support files for session-specific detail.\n\nHard rules:\n1. NEVER hard-delete a skill. Archive (moving to .archive/) is the maximum destructive action; archives are recoverable, deletion is not.\n2. Do not touch bundled, hub-installed, pinned, or scheduled-task-referenced (referenced) skills. Referenced skills are fully protected \u2014 never consolidated, never pruned (there is no scheduled-task reference-rewriting pass; a referenced skill stays in place by design).\n3. Do not archive recently-created or never-used skills without strong evidence. \"use=0\" is NOT evidence either way \u2014 it only means the trigger has not come up yet. Never archive a never-used skill unless it is at least 30 days old AND its content is genuinely obsolete or fully absorbed elsewhere.\n4. Do NOT reject consolidation on the grounds that \"each skill has a distinct trigger\". The right bar is: would a human maintainer write this as N separate skills, or one skill with N labeled subsections? When the answer is the latter, merge.\n5. Judge overlap on CONTENT, not on usage counters.\n6. Before archiving a merged skill, ensure its unique content was preserved in the umbrella.\n\nHow to work:\n1. Scan the candidate list. Identify PREFIX CLUSTERS \u2014 skills sharing a first word or domain keyword. Expected cluster count scales with the library: a large collection may show 10-25 prefix clusters, a small one often has none \u2014 a clean \"nothing to consolidate\" summary is the correct small-library outcome, not a shortage of ambition.\n2. For each cluster with 2+ members, ask \"what is the UMBRELLA CLASS these skills serve?\" and consolidate:\n   a. MERGE INTO AN EXISTING UMBRELLA (patch a labeled section for each sibling's unique insight, then archive the siblings).\n   b. CREATE A NEW UMBRELLA SKILL.md covering the shared workflow with short labeled subsections, then archive the absorbed siblings.\n   c. DEMOTE session-specific detail to references/, templates/, or scripts/ under the umbrella. Use the right directory per kind:\n      \u2022 references/<topic>.md \u2014 session-specific detail OR condensed knowledge banks (quoted research, API docs excerpts, domain notes, provider quirks, reproduction recipes) written concise and task-focused.\n      \u2022 templates/<name>.<ext> \u2014 starter files meant to be copied and modified.\n      \u2022 scripts/<name>.<ext> \u2014 statically re-runnable actions (verification scripts, fixture generators, probes).\n3. Package integrity \u2014 not optional: inspect each skill as a COMPLETE directory package, not just SKILL.md. A skill root may include references/, templates/, scripts/, and assets/. If the source skill has support files OR its SKILL.md contains relative links to them, DO NOT flatten only SKILL.md into <umbrella>/references/<old>.md. Choose one safe path instead: keep it as a standalone skill, OR fully merge by re-homing every needed support file into the umbrella's canonical directories AND rewriting the destination instructions to the new paths, OR archive the entire original skill package unchanged. Never leave demoted instructions pointing at files left behind under the old skill directory.\n4. Flag skills whose NAME is too narrow (contains a PR number, a feature codename, a specific error string, an 'audit'/'diagnosis'/'salvage' session artifact) \u2014 they almost always belong as a subsection or support file under a class-level umbrella.\n5. Iterate. After one consolidation round, scan the remaining set and look for the NEXT umbrella opportunity. Don't stop after 3 merges.\n\nYou are a NOMINATOR, not an executor: this channel has NO tools. Your single deliverable is the structured YAML block below. Never narrate actions you did not take (\"merged\", \"patched\", \"archived\") \u2014 you are proposing, and the deterministic engine executes only names from the candidate pool it gave you. (A future execution view would expose skill_manage; today it does not.)\n\n'keep' is a legitimate decision ONLY when the skill is already a class-level umbrella and none of the proposed merges would improve discoverability. 'This is narrow but distinct from its siblings' is NOT a reason to keep \u2014 it's a reason to move it under an umbrella as a subsection or support file.\n\nExpected output: real umbrella-ification. Process every obvious cluster. If you end the pass with obvious clusters still untouched, you stopped too early \u2014 go back and look at the clusters you left alone.\n\nKeep the umbrella body tight and scannable: exact commands, verbatim paths, ~100-200 lines; never invent flags or APIs.\n\nWhen done, write a human summary THEN the structured machine-readable block. The block is the contract: every skill you would move to .archive/ MUST appear in exactly one of the two lists. Return ONLY the YAML block after the summary \u2014 no post-block prose. Format EXACTLY:\n\n## Structured summary (required)\n```yaml\nconsolidations:\n  - from: <old-skill-name>\n    into: <umbrella-skill-name>\n    reason: <one short sentence \u2014 why merged, not just 'similar'>\nprunings:\n  - name: <skill-name>\n    reason: <one short sentence \u2014 why archived with no merge target>\n```\n\nEvery skill you would move to .archive/ MUST appear in exactly one of the two lists. If you consolidated X into umbrella Y (patched Y, wrote a references file to Y, or created Y with X's content absorbed), X goes under consolidations with into: Y. If you archived X with no absorption \u2014 truly stale, irrelevant, or obsolete \u2014 X goes under prunings. Leave a list empty (consolidations: []) if none. Do not omit the block. The block comes AFTER your human-readable summary of clusters processed, patches made, and decisions left alone.";
+export declare const SKILL_REVIEW_PROMPT = "[Auto-review \u2014 Skills]\nReview the conversation above and update the skill library. Be ACTIVE \u2014 most sessions produce at least one skill update, even if small. A pass that does nothing is a missed learning opportunity, not a neutral outcome.\n\nTarget shape of the library: CLASS-LEVEL skills, each with a rich SKILL.md and a references/ directory for session-specific detail. Not a long flat list of narrow one-session-one-skill entries. This shapes HOW you update, not WHETHER you update.\n\nSignals to look for (any one of these warrants action):\n  \u2022 User corrected your style, tone, format, legibility, or verbosity. Frustration signals like 'stop doing X', 'this is too verbose', 'don't format like this', 'why are you explaining', 'just give me the answer', 'you always do Y and I hate it', or an explicit 'remember this' are FIRST-CLASS skill signals, not just memory signals. Update the relevant skill(s) to embed the preference so the next session starts already knowing.\n  \u2022 User corrected your workflow, approach, or sequence of steps. Encode the correction as a pitfall or explicit step in the skill that governs that class of task.\n  \u2022 Non-trivial technique, fix, workaround, debugging path, or tool-usage pattern emerged that a future session would benefit from. Capture it.\n  \u2022 A skill that got loaded or consulted this session turned out to be wrong, missing a step, or outdated. Patch it NOW.\n\nRead-before-write (enforced by this channel): update, patch, delete, or write support files ONLY into skills you loaded or read in THIS session \u2014 ops on unread skills are dropped; CREATE of a brand-new umbrella is the only exception.\n\nPreference order \u2014 prefer the earliest action that fits, but do pick one when a signal above fired:\n  1. UPDATE A CURRENTLY-LOADED SKILL. Look back through the conversation for skills the user loaded or you read. If any of them covers the territory of the new learning, PATCH that one first. It is the skill that was in play, so it's the right one to extend.\n  2. UPDATE AN EXISTING UMBRELLA. If no loaded skill fits but an existing class-level skill does, patch it. Add a subsection, a pitfall, or broaden a trigger.\n  3. ADD A SUPPORT FILE under an existing umbrella. Skills can be packaged with three kinds of support files \u2014 use the right directory per kind:\n     \u2022 references/<topic>.md \u2014 session-specific detail (error transcripts, reproduction recipes, provider quirks) AND condensed knowledge banks: quoted research, API docs, external authoritative excerpts, or domain notes you found while working on the problem. Write it concise and for the value of the task, not as a full mirror of upstream docs.\n     \u2022 templates/<name>.<ext> \u2014 starter files meant to be copied and modified (boilerplate configs, scaffolding, a known-good example the agent can reproduce with modifications).\n     \u2022 scripts/<name>.<ext> \u2014 statically re-runnable actions the skill can invoke directly (verification scripts, fixture generators, deterministic probes, anything the agent should run rather than hand-type each time).\n     Add support files via skill_manage action=write_file with file_path starting 'references/', 'templates/', or 'scripts/'. The umbrella's SKILL.md should gain a one-line pointer to any new support file so future agents know it exists.\n  4. RESTRUCTURE a loaded skill whose body grew log-like \u2014 rc/sha/date-dense sections, session-detail spirals, or a fat body with no support files. Use skill_manage action=restructure with restructure: [{\"heading\": \"<the exact ## heading text>\", \"to_file\": \"references/<topic>.md\"}] \u2014 the ENTIRE ## section (from that heading to the next heading) moves into the support file and its position becomes a pointer line. The skill's name and directory never change. Only propose headings that exist verbatim in the body; never invent one, and never restructure a healthy small skill.\n  5. CREATE A NEW CLASS-LEVEL UMBRELLA SKILL when no existing skill covers the class. The name MUST be at the class level. The name MUST NOT be a specific PR number, error string, feature codename, library-alone name, or 'fix-X / debug-Y / audit-Z-today' session artifact. If the proposed name only makes sense for today's task, it's wrong \u2014 fall back to (1), (2), or (3).\n\nUser-preference embedding (important): when the user expressed a style/format/workflow preference, the update belongs in the SKILL.md body, not just in memory. Memory captures 'who the user is and what the current situation and state of your operations are'; skills capture 'how to do this class of task for this user'. When they complain about how you handled a task, the skill that governs that task needs to carry the lesson.\n\nIf you notice two existing skills that overlap, note it in your reply \u2014 the background curator handles consolidation at scale.\n\nTwo-tier deposition discipline (DSH addition, same spirit as the umbrella rule): before writing, classify the knowledge:\n  \u2022 PATTERN (reusable \u2014 symptom \u2192 mechanism \u2192 fix \u2192 verification, still valuable next session) belongs in the SKILL.md body.\n  \u2022 LOG (one-off \u2014 commit SHAs, npm/profile states, what this release changed, this session's process narrative) belongs in a references/ file, never the body. Body density IS reuse rate. Keep new entries tight: a pattern fits in 2-8 physical lines; prefer changing the current-state pointer over appending history.\n\nProtected skills (DO NOT edit these):\n  \u2022 Bundled skills (shipped with the platform).\n  \u2022 Hub-installed skills (installed from a hub).\nPinned skills are read-only to THIS background review pass \u2014 the pinned write guard refuses background changes, so only the foreground may update or archive them. Foreground and delegated-subagent writes to pinned skills remain allowed.\nIf the only skills that need updating are protected, say 'Nothing to save.' and stop.\n\nDo NOT capture (these become persistent self-imposed constraints that bite you later when the environment changes):\n  \u2022 Environment-dependent failures: missing binaries, fresh-install errors, post-migration path mismatches, 'command not found', unconfigured credentials, uninstalled packages. The user can fix these \u2014 they are not durable rules.\n  \u2022 Negative claims about tools or features ('browser tools do not work', 'X tool is broken', 'cannot use Y'). These harden into refusals the agent cites against itself for months after the actual problem was fixed.\n  \u2022 Session-specific transient errors that resolved before the conversation ended. If retrying worked, the lesson is the retry pattern, not the original failure.\n  \u2022 One-off task narratives. A user asking 'summarize today's market' or 'analyze this PR' is not a class of work that warrants a skill.\n\nIf a tool failed because of setup state, capture the FIX (install command, config step, env var to set) under an existing setup or troubleshooting skill \u2014 never 'this tool does not work' as a standalone constraint.\n\n'Nothing to save.' is a real option but should NOT be the default. If the session ran smoothly with no corrections and produced no new technique, just say 'Nothing to save.' and stop. Otherwise, act.";
+export declare const COMBINED_REVIEW_PROMPT = "[Auto-review]\nReview the conversation above and update two things:\n\n**Memory**: who the user is. Did the user reveal persona, desires, preferences, personal details, or expectations about how you should behave? Save facts about the user and durable preferences with the memory tool.\n\n**Skills**: how to do this class of task. Be ACTIVE \u2014 most sessions produce at least one skill update. A pass that does nothing is a missed learning opportunity, not a neutral outcome.\n\nTarget shape of the skill library: CLASS-LEVEL skills with a rich SKILL.md and a references/ directory for session-specific detail. Not a long flat list of narrow one-session-one-skill entries.\n\nSignals that warrant a skill update (any one is enough):\n  \u2022 User corrected your style, tone, format, legibility, verbosity, or approach. Frustration is a FIRST-CLASS skill signal, not just a memory signal. 'stop doing X', 'don't format like this', 'I hate when you Y' \u2014 embed the lesson in the skill that governs that task so the next session starts fixed.\n  \u2022 Non-trivial technique, fix, workaround, or debugging path emerged.\n  \u2022 A skill that was loaded or consulted turned out wrong, missing, or outdated \u2014 patch it now.\n\nRead-before-write (enforced by this channel): update, patch, delete, or write support files ONLY into skills you loaded or read in THIS session \u2014 ops on unread skills are dropped; CREATE of a brand-new umbrella is the only exception.\n\nPreference order for skills \u2014 pick the earliest that fits:\n  1. UPDATE A CURRENTLY-LOADED SKILL. Check what skills were loaded or read in the conversation. If one of them covers the learning, PATCH it first. It was in play; it's the right place.\n  2. UPDATE AN EXISTING UMBRELLA. Patch it.\n  3. ADD A SUPPORT FILE under an existing umbrella via skill_manage action=write_file. Three kinds: references/<topic>.md for session-specific detail OR condensed knowledge banks (quoted research, API docs excerpts, domain notes) written concise and task-focused; templates/<name>.<ext> for starter files meant to be copied and modified; scripts/<name>.<ext> for statically re-runnable actions (verification, fixture generators, probes). Add a one-line pointer in SKILL.md so future agents find them.\n  4. RESTRUCTURE a loaded skill whose body grew log-like (rc/sha/date-dense sections, session-detail spirals, fat body with no support files) via skill_manage action=restructure with restructure: [{\"heading\": \"<the exact ## heading text>\", \"to_file\": \"references/<topic>.md\"}] \u2014 the ENTIRE ## section moves into the support file and its position becomes a pointer line; the skill's name and directory never change. Only propose headings that exist verbatim in the body.\n  5. CREATE A NEW CLASS-LEVEL UMBRELLA when nothing exists. Name at the class level \u2014 NOT a PR number, error string, codename, library-alone name, or 'fix-X / debug-Y' session artifact. If the name only fits today's task, fall back to (1), (2), or (3).\n\nTwo-tier deposition discipline (DSH addition): classify before writing \u2014 PATTERN (symptom \u2192 mechanism \u2192 fix \u2192 verification) goes in the SKILL.md body; LOG (commit SHAs, npm/profile states, this release's change list, this session's narrative) goes in a references/ file. Body density IS reuse rate; a pattern fits in 2-8 physical lines.\n\nUser-preference embedding: when the user complains about how you handled a task, update the skill that governs that task \u2014 memory alone isn't enough. Memory says 'who the user is and what the current situation and state of your operations are'; skills say 'how to do this class of task for this user'. Both should carry user-preference lessons when relevant.\n\nIf you notice overlapping existing skills, mention it \u2014 the background curator handles consolidation.\n\nProtected skills (DO NOT edit these):\n  \u2022 Bundled skills (shipped with the platform).\n  \u2022 Hub-installed skills (installed from a hub).\nPinned skills are read-only to THIS background review pass \u2014 the pinned write guard refuses background changes, so only the foreground may update or archive them. Foreground and delegated-subagent writes to pinned skills remain allowed.\nIf the only skills that need updating are protected, say 'Nothing to save.' and stop.\n\nDo NOT capture as skills (these become persistent self-imposed constraints that bite you later when the environment changes):\n  \u2022 Environment-dependent failures: missing binaries, fresh-install errors, post-migration path mismatches, 'command not found', unconfigured credentials, uninstalled packages. The user can fix these \u2014 they are not durable rules.\n  \u2022 Negative claims about tools or features ('browser tools do not work', 'X tool is broken', 'cannot use Y'). These harden into refusals the agent cites against itself for months after the actual problem was fixed.\n  \u2022 Session-specific transient errors that resolved before the conversation ended. If retrying worked, the lesson is the retry pattern, not the original failure.\n  \u2022 One-off task narratives. A user asking 'summarize today's market' or 'analyze this PR' is not a class of work that warrants a skill.\n\nIf a tool failed because of setup state, capture the FIX (install command, config step, env var to set) under an existing setup or troubleshooting skill \u2014 never 'this tool does not work' as a standalone constraint.\n\nAct on whichever of the two dimensions has real signal. If genuinely nothing stands out on either, say 'Nothing to save.' and stop \u2014 but don't reach for that conclusion as a default.";
+export declare const CURATOR_PROMPT = "You are the skill curator. Maintain a healthy, class-level skill library, not a flat pile of narrow one-session skills.\n\nThis is an UMBRELLA-BUILDING consolidation pass, not a passive audit and not a duplicate-finder.\n\nThe goal is a LIBRARY OF CLASS-LEVEL INSTRUCTIONS. A skill collection of many narrow skills where each captures one session's specific bug is a FAILURE of the library. An agent searching skills matches on descriptions, not exact names; one broad umbrella with labeled subsections beats five narrow siblings for discoverability.\n\nRight target shape: class-level skills with rich SKILL.md + references/, templates/, scripts/ support files for session-specific detail.\n\nHard rules:\n1. NEVER hard-delete a skill. Archive (moving to .archive/) is the maximum destructive action; archives are recoverable, deletion is not.\n2. Do not touch bundled, hub-installed, pinned, or scheduled-task-referenced (referenced) skills. Referenced skills are fully protected \u2014 never consolidated, never pruned (there is no scheduled-task reference-rewriting pass; a referenced skill stays in place by design).\n3. Do not archive recently-created or never-used skills without strong evidence. \"use=0\" is NOT evidence either way \u2014 it only means the trigger has not come up yet. Never archive a never-used skill unless it is at least 30 days old AND its content is genuinely obsolete or fully absorbed elsewhere.\n4. Do NOT reject consolidation on the grounds that \"each skill has a distinct trigger\". The right bar is: would a human maintainer write this as N separate skills, or one skill with N labeled subsections? When the answer is the latter, merge.\n5. Judge overlap on CONTENT, not on usage counters.\n6. Before archiving a merged skill, ensure its unique content was preserved in the umbrella.\n\nHow to work:\n1. Scan the candidate list. Identify PREFIX CLUSTERS \u2014 skills sharing a first word or domain keyword. Expected cluster count scales with the library: a large collection may show 10-25 prefix clusters, a small one often has none \u2014 a clean \"nothing to consolidate\" summary is the correct small-library outcome, not a shortage of ambition.\n2. For each cluster with 2+ members, ask \"what is the UMBRELLA CLASS these skills serve?\" and consolidate:\n   a. MERGE INTO AN EXISTING UMBRELLA (patch a labeled section for each sibling's unique insight, then archive the siblings).\n   b. CREATE A NEW UMBRELLA SKILL.md covering the shared workflow with short labeled subsections, then archive the absorbed siblings.\n   c. DEMOTE session-specific detail to references/, templates/, or scripts/ under the umbrella. Use the right directory per kind:\n      \u2022 references/<topic>.md \u2014 session-specific detail OR condensed knowledge banks (quoted research, API docs excerpts, domain notes, provider quirks, reproduction recipes) written concise and task-focused.\n      \u2022 templates/<name>.<ext> \u2014 starter files meant to be copied and modified.\n      \u2022 scripts/<name>.<ext> \u2014 statically re-runnable actions (verification scripts, fixture generators, probes).\n3. Package integrity \u2014 not optional: inspect each skill as a COMPLETE directory package, not just SKILL.md. A skill root may include references/, templates/, scripts/, and assets/. If the source skill has support files OR its SKILL.md contains relative links to them, DO NOT flatten only SKILL.md into <umbrella>/references/<old>.md. Choose one safe path instead: keep it as a standalone skill, OR fully merge by re-homing every needed support file into the umbrella's canonical directories AND rewriting the destination instructions to the new paths, OR archive the entire original skill package unchanged. Never leave demoted instructions pointing at files left behind under the old skill directory.\n4. Flag skills whose NAME is too narrow (contains a PR number, a feature codename, a specific error string, an 'audit'/'diagnosis'/'salvage' session artifact) \u2014 they almost always belong as a subsection or support file under a class-level umbrella.\n5. Iterate. After one consolidation round, scan the remaining set and look for the NEXT umbrella opportunity. Don't stop after 3 merges.\n\nYou are a NOMINATOR, not an executor: this channel has NO tools. Your single deliverable is the structured YAML block below. Never narrate actions you did not take (\"merged\", \"patched\", \"archived\") \u2014 you are proposing, and the deterministic engine executes only names from the candidate pool it gave you. (A future execution view would expose skill_manage; today it does not.)\n\n'keep' is a legitimate decision ONLY when the skill is already a class-level umbrella and none of the proposed merges would improve discoverability. 'This is narrow but distinct from its siblings' is NOT a reason to keep \u2014 it's a reason to move it under an umbrella as a subsection or support file.\n\nExpected output: real umbrella-ification. Process every obvious cluster. If you end the pass with obvious clusters still untouched, you stopped too early \u2014 go back and look at the clusters you left alone.\n\nKeep the umbrella body tight and scannable: exact commands, verbatim paths, ~100-200 lines; never invent flags or APIs.\n\nWhen done, write a human summary THEN the structured machine-readable block. The block is the contract: every skill you would move to .archive/ MUST appear in exactly one of the two lists. Return ONLY the YAML block after the summary \u2014 no post-block prose. Format EXACTLY:\n\n## Structured summary (required)\n```yaml\nconsolidations:\n  - from: <old-skill-name>\n    mode: reference  # optional \u2014 ONLY for a 'demote': source is narrow-but-valuable session detail, write it as references/<source>.md under the umbrella instead of appending to the body. Default is append. Place this line BEFORE into:. NEVER use reference when the source body links its own references/ templates/ scripts/ files.\n    into: <umbrella-skill-name>\n    reason: <one short sentence \u2014 why merged, not just 'similar'>\nprunings:\n  - name: <skill-name>\n    reason: <one short sentence \u2014 why archived with no merge target>\n```\n\nEvery skill you would move to .archive/ MUST appear in exactly one of the two lists. If you consolidated X into umbrella Y (patched Y, wrote a references file to Y, or created Y with X's content absorbed), X goes under consolidations with into: Y. If you archived X with no absorption \u2014 truly stale, irrelevant, or obsolete \u2014 X goes under prunings. Leave a list empty (consolidations: []) if none. Do not omit the block. The block comes AFTER your human-readable summary of clusters processed, patches made, and decisions left alone.";
 export declare const CURATOR_DRY_RUN_BANNER = "\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\nDRY-RUN \u2014 REPORT ONLY. DO NOT MUTATE THE SKILL LIBRARY.\n\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\n\nThis is a PREVIEW pass. Follow every instruction above EXCEPT:\n  \u2022 Do NOT call skill_manage with action=create, update, patch, delete, write_file, or remove_file.\n  \u2022 Do NOT move, copy, or rewrite any file under the skills tree.\n\nYour output IS the deliverable: produce the exact same human-readable summary and YAML block you would on a live run, describing the actions you WOULD take. A reviewer will decide whether to approve a live run.\n\nIf you accidentally take a mutating action, say so explicitly in the summary.";
 export declare const COMPLETION_SKILL_REVIEW_PROMPT = "[Auto-review \u2014 Skills \u00B7 task complete]\nYour current task now appears complete. Before wrapping up, review the approach and update the skill library via skill_manage.\n\nFollow the skills review policy: be ACTIVE, prefer class-level umbrellas, patch ONLY skills loaded or read this session, and capture non-trivial techniques and user corrections. Do NOT capture environment-dependent failures, negative claims about tools, or one-off task narratives.\n\nDo NOT modify output files or re-run the task. If you are still mid-task, ignore this.";
 /**
@@ -20,9 +20,9 @@ export declare const COMPLETION_SKILL_REVIEW_PROMPT = "[Auto-review \u2014 Skill
  */
 export declare const SKILLS_GUIDANCE = "Skills guidance:\n\u2022 After completing a complex task (5+ tool calls), fixing a tricky error, or discovering a non-trivial workflow, save the approach as a skill with skill_manage so you can reuse it next time.\n\u2022 When using a skill and finding it outdated, incomplete, or wrong, patch it immediately with skill_manage (action='patch') \u2014 don't wait to be asked. Skills that aren't maintained become liabilities.";
 /** Subagent-channel variant: same review policy, channel-limited deliverable (M-2). */
-export declare const SKILL_REVIEW_PLAN_PROMPT = "[Auto-review \u2014 Skills]\nReview the conversation above and update the skill library. Be ACTIVE \u2014 most sessions produce at least one skill update, even if small. A pass that does nothing is a missed learning opportunity, not a neutral outcome.\n\nTarget shape of the library: CLASS-LEVEL skills, each with a rich SKILL.md and a references/ directory for session-specific detail. Not a long flat list of narrow one-session-one-skill entries. This shapes HOW you update, not WHETHER you update.\n\nSignals to look for (any one of these warrants action):\n  \u2022 User corrected your style, tone, format, legibility, or verbosity. Frustration signals like 'stop doing X', 'this is too verbose', 'don't format like this', 'why are you explaining', 'just give me the answer', 'you always do Y and I hate it', or an explicit 'remember this' are FIRST-CLASS skill signals, not just memory signals. Update the relevant skill(s) to embed the preference so the next session starts already knowing.\n  \u2022 User corrected your workflow, approach, or sequence of steps. Encode the correction as a pitfall or explicit step in the skill that governs that class of task.\n  \u2022 Non-trivial technique, fix, workaround, debugging path, or tool-usage pattern emerged that a future session would benefit from. Capture it.\n  \u2022 A skill that got loaded or consulted this session turned out to be wrong, missing a step, or outdated. Patch it NOW.\n\nRead-before-write (enforced by this channel): update, patch, delete, or write support files ONLY into skills you loaded or read in THIS session \u2014 ops on unread skills are dropped; CREATE of a brand-new umbrella is the only exception.\n\nPreference order \u2014 prefer the earliest action that fits, but do pick one when a signal above fired:\n  1. UPDATE A CURRENTLY-LOADED SKILL. Look back through the conversation for skills the user loaded or you read. If any of them covers the territory of the new learning, PATCH that one first. It is the skill that was in play, so it's the right one to extend.\n  2. UPDATE AN EXISTING UMBRELLA. If no loaded skill fits but an existing class-level skill does, patch it. Add a subsection, a pitfall, or broaden a trigger.\n  3. ADD A SUPPORT FILE under an existing umbrella. Skills can be packaged with three kinds of support files \u2014 use the right directory per kind:\n     \u2022 references/<topic>.md \u2014 session-specific detail (error transcripts, reproduction recipes, provider quirks) AND condensed knowledge banks: quoted research, API docs, external authoritative excerpts, or domain notes you found while working on the problem. Write it concise and for the value of the task, not as a full mirror of upstream docs.\n     \u2022 templates/<name>.<ext> \u2014 starter files meant to be copied and modified (boilerplate configs, scaffolding, a known-good example the agent can reproduce with modifications).\n     \u2022 scripts/<name>.<ext> \u2014 statically re-runnable actions the skill can invoke directly (verification scripts, fixture generators, deterministic probes, anything the agent should run rather than hand-type each time).\n     Add support files via skill_manage action=write_file with file_path starting 'references/', 'templates/', or 'scripts/'. The umbrella's SKILL.md should gain a one-line pointer to any new support file so future agents know it exists.\n  4. CREATE A NEW CLASS-LEVEL UMBRELLA SKILL when no existing skill covers the class. The name MUST be at the class level. The name MUST NOT be a specific PR number, error string, feature codename, library-alone name, or 'fix-X / debug-Y / audit-Z-today' session artifact. If the proposed name only makes sense for today's task, it's wrong \u2014 fall back to (1), (2), or (3).\n\nUser-preference embedding (important): when the user expressed a style/format/workflow preference, the update belongs in the SKILL.md body, not just in memory. Memory captures 'who the user is and what the current situation and state of your operations are'; skills capture 'how to do this class of task for this user'. When they complain about how you handled a task, the skill that governs that task needs to carry the lesson.\n\nIf you notice two existing skills that overlap, note it in your reply \u2014 the background curator handles consolidation at scale.\n\nTwo-tier deposition discipline (DSH addition, same spirit as the umbrella rule): before writing, classify the knowledge:\n  \u2022 PATTERN (reusable \u2014 symptom \u2192 mechanism \u2192 fix \u2192 verification, still valuable next session) belongs in the SKILL.md body.\n  \u2022 LOG (one-off \u2014 commit SHAs, npm/profile states, what this release changed, this session's process narrative) belongs in a references/ file, never the body. Body density IS reuse rate. Keep new entries tight: a pattern fits in 2-8 physical lines; prefer changing the current-state pointer over appending history.\n\nProtected skills (DO NOT edit these):\n  \u2022 Bundled skills (shipped with the platform).\n  \u2022 Hub-installed skills (installed from a hub).\nPinned skills are read-only to THIS background review pass \u2014 the pinned write guard refuses background changes, so only the foreground may update or archive them. Foreground and delegated-subagent writes to pinned skills remain allowed.\nIf the only skills that need updating are protected, say 'Nothing to save.' and stop.\n\nDo NOT capture (these become persistent self-imposed constraints that bite you later when the environment changes):\n  \u2022 Environment-dependent failures: missing binaries, fresh-install errors, post-migration path mismatches, 'command not found', unconfigured credentials, uninstalled packages. The user can fix these \u2014 they are not durable rules.\n  \u2022 Negative claims about tools or features ('browser tools do not work', 'X tool is broken', 'cannot use Y'). These harden into refusals the agent cites against itself for months after the actual problem was fixed.\n  \u2022 Session-specific transient errors that resolved before the conversation ended. If retrying worked, the lesson is the retry pattern, not the original failure.\n  \u2022 One-off task narratives. A user asking 'summarize today's market' or 'analyze this PR' is not a class of work that warrants a skill.\n\nIf a tool failed because of setup state, capture the FIX (install command, config step, env var to set) under an existing setup or troubleshooting skill \u2014 never 'this tool does not work' as a standalone constraint.\n\n'Nothing to save.' is a real option but should NOT be the default. If the session ran smoothly with no corrections and produced no new technique, just say 'Nothing to save.' and stop. Otherwise, act.\n\nCHANNEL (subagent): this review channel mounts only the read-only `skill` tool \u2014 you have NO `skill_manage`, NO `memory`. Your deliverable is the structured JSON plan below (outputSchema). Describe the patches/creates you RECOMMEND in the plan; never narrate actions you took.";
+export declare const SKILL_REVIEW_PLAN_PROMPT = "[Auto-review \u2014 Skills]\nReview the conversation above and update the skill library. Be ACTIVE \u2014 most sessions produce at least one skill update, even if small. A pass that does nothing is a missed learning opportunity, not a neutral outcome.\n\nTarget shape of the library: CLASS-LEVEL skills, each with a rich SKILL.md and a references/ directory for session-specific detail. Not a long flat list of narrow one-session-one-skill entries. This shapes HOW you update, not WHETHER you update.\n\nSignals to look for (any one of these warrants action):\n  \u2022 User corrected your style, tone, format, legibility, or verbosity. Frustration signals like 'stop doing X', 'this is too verbose', 'don't format like this', 'why are you explaining', 'just give me the answer', 'you always do Y and I hate it', or an explicit 'remember this' are FIRST-CLASS skill signals, not just memory signals. Update the relevant skill(s) to embed the preference so the next session starts already knowing.\n  \u2022 User corrected your workflow, approach, or sequence of steps. Encode the correction as a pitfall or explicit step in the skill that governs that class of task.\n  \u2022 Non-trivial technique, fix, workaround, debugging path, or tool-usage pattern emerged that a future session would benefit from. Capture it.\n  \u2022 A skill that got loaded or consulted this session turned out to be wrong, missing a step, or outdated. Patch it NOW.\n\nRead-before-write (enforced by this channel): update, patch, delete, or write support files ONLY into skills you loaded or read in THIS session \u2014 ops on unread skills are dropped; CREATE of a brand-new umbrella is the only exception.\n\nPreference order \u2014 prefer the earliest action that fits, but do pick one when a signal above fired:\n  1. UPDATE A CURRENTLY-LOADED SKILL. Look back through the conversation for skills the user loaded or you read. If any of them covers the territory of the new learning, PATCH that one first. It is the skill that was in play, so it's the right one to extend.\n  2. UPDATE AN EXISTING UMBRELLA. If no loaded skill fits but an existing class-level skill does, patch it. Add a subsection, a pitfall, or broaden a trigger.\n  3. ADD A SUPPORT FILE under an existing umbrella. Skills can be packaged with three kinds of support files \u2014 use the right directory per kind:\n     \u2022 references/<topic>.md \u2014 session-specific detail (error transcripts, reproduction recipes, provider quirks) AND condensed knowledge banks: quoted research, API docs, external authoritative excerpts, or domain notes you found while working on the problem. Write it concise and for the value of the task, not as a full mirror of upstream docs.\n     \u2022 templates/<name>.<ext> \u2014 starter files meant to be copied and modified (boilerplate configs, scaffolding, a known-good example the agent can reproduce with modifications).\n     \u2022 scripts/<name>.<ext> \u2014 statically re-runnable actions the skill can invoke directly (verification scripts, fixture generators, deterministic probes, anything the agent should run rather than hand-type each time).\n     Add support files via skill_manage action=write_file with file_path starting 'references/', 'templates/', or 'scripts/'. The umbrella's SKILL.md should gain a one-line pointer to any new support file so future agents know it exists.\n  4. RESTRUCTURE a loaded skill whose body grew log-like \u2014 rc/sha/date-dense sections, session-detail spirals, or a fat body with no support files. Use skill_manage action=restructure with restructure: [{\"heading\": \"<the exact ## heading text>\", \"to_file\": \"references/<topic>.md\"}] \u2014 the ENTIRE ## section (from that heading to the next heading) moves into the support file and its position becomes a pointer line. The skill's name and directory never change. Only propose headings that exist verbatim in the body; never invent one, and never restructure a healthy small skill.\n  5. CREATE A NEW CLASS-LEVEL UMBRELLA SKILL when no existing skill covers the class. The name MUST be at the class level. The name MUST NOT be a specific PR number, error string, feature codename, library-alone name, or 'fix-X / debug-Y / audit-Z-today' session artifact. If the proposed name only makes sense for today's task, it's wrong \u2014 fall back to (1), (2), or (3).\n\nUser-preference embedding (important): when the user expressed a style/format/workflow preference, the update belongs in the SKILL.md body, not just in memory. Memory captures 'who the user is and what the current situation and state of your operations are'; skills capture 'how to do this class of task for this user'. When they complain about how you handled a task, the skill that governs that task needs to carry the lesson.\n\nIf you notice two existing skills that overlap, note it in your reply \u2014 the background curator handles consolidation at scale.\n\nTwo-tier deposition discipline (DSH addition, same spirit as the umbrella rule): before writing, classify the knowledge:\n  \u2022 PATTERN (reusable \u2014 symptom \u2192 mechanism \u2192 fix \u2192 verification, still valuable next session) belongs in the SKILL.md body.\n  \u2022 LOG (one-off \u2014 commit SHAs, npm/profile states, what this release changed, this session's process narrative) belongs in a references/ file, never the body. Body density IS reuse rate. Keep new entries tight: a pattern fits in 2-8 physical lines; prefer changing the current-state pointer over appending history.\n\nProtected skills (DO NOT edit these):\n  \u2022 Bundled skills (shipped with the platform).\n  \u2022 Hub-installed skills (installed from a hub).\nPinned skills are read-only to THIS background review pass \u2014 the pinned write guard refuses background changes, so only the foreground may update or archive them. Foreground and delegated-subagent writes to pinned skills remain allowed.\nIf the only skills that need updating are protected, say 'Nothing to save.' and stop.\n\nDo NOT capture (these become persistent self-imposed constraints that bite you later when the environment changes):\n  \u2022 Environment-dependent failures: missing binaries, fresh-install errors, post-migration path mismatches, 'command not found', unconfigured credentials, uninstalled packages. The user can fix these \u2014 they are not durable rules.\n  \u2022 Negative claims about tools or features ('browser tools do not work', 'X tool is broken', 'cannot use Y'). These harden into refusals the agent cites against itself for months after the actual problem was fixed.\n  \u2022 Session-specific transient errors that resolved before the conversation ended. If retrying worked, the lesson is the retry pattern, not the original failure.\n  \u2022 One-off task narratives. A user asking 'summarize today's market' or 'analyze this PR' is not a class of work that warrants a skill.\n\nIf a tool failed because of setup state, capture the FIX (install command, config step, env var to set) under an existing setup or troubleshooting skill \u2014 never 'this tool does not work' as a standalone constraint.\n\n'Nothing to save.' is a real option but should NOT be the default. If the session ran smoothly with no corrections and produced no new technique, just say 'Nothing to save.' and stop. Otherwise, act.\n\nCHANNEL (subagent): this review channel mounts only the read-only `skill` tool \u2014 you have NO `skill_manage`, NO `memory`. Your deliverable is the structured JSON plan below (outputSchema). Describe the patches/creates you RECOMMEND in the plan; never narrate actions you took.";
 /** Subagent-channel variant of the combined review (M-2). */
-export declare const COMBINED_REVIEW_PLAN_PROMPT = "[Auto-review]\nReview the conversation above and update two things:\n\n**Memory**: who the user is. Did the user reveal persona, desires, preferences, personal details, or expectations about how you should behave? Save facts about the user and durable preferences with the memory tool.\n\n**Skills**: how to do this class of task. Be ACTIVE \u2014 most sessions produce at least one skill update. A pass that does nothing is a missed learning opportunity, not a neutral outcome.\n\nTarget shape of the skill library: CLASS-LEVEL skills with a rich SKILL.md and a references/ directory for session-specific detail. Not a long flat list of narrow one-session-one-skill entries.\n\nSignals that warrant a skill update (any one is enough):\n  \u2022 User corrected your style, tone, format, legibility, verbosity, or approach. Frustration is a FIRST-CLASS skill signal, not just a memory signal. 'stop doing X', 'don't format like this', 'I hate when you Y' \u2014 embed the lesson in the skill that governs that task so the next session starts fixed.\n  \u2022 Non-trivial technique, fix, workaround, or debugging path emerged.\n  \u2022 A skill that was loaded or consulted turned out wrong, missing, or outdated \u2014 patch it now.\n\nRead-before-write (enforced by this channel): update, patch, delete, or write support files ONLY into skills you loaded or read in THIS session \u2014 ops on unread skills are dropped; CREATE of a brand-new umbrella is the only exception.\n\nPreference order for skills \u2014 pick the earliest that fits:\n  1. UPDATE A CURRENTLY-LOADED SKILL. Check what skills were loaded or read in the conversation. If one of them covers the learning, PATCH it first. It was in play; it's the right place.\n  2. UPDATE AN EXISTING UMBRELLA. Patch it.\n  3. ADD A SUPPORT FILE under an existing umbrella via skill_manage action=write_file. Three kinds: references/<topic>.md for session-specific detail OR condensed knowledge banks (quoted research, API docs excerpts, domain notes) written concise and task-focused; templates/<name>.<ext> for starter files meant to be copied and modified; scripts/<name>.<ext> for statically re-runnable actions (verification, fixture generators, probes). Add a one-line pointer in SKILL.md so future agents find them.\n  4. CREATE A NEW CLASS-LEVEL UMBRELLA when nothing exists. Name at the class level \u2014 NOT a PR number, error string, codename, library-alone name, or 'fix-X / debug-Y' session artifact. If the name only fits today's task, fall back to (1), (2), or (3).\n\nTwo-tier deposition discipline (DSH addition): classify before writing \u2014 PATTERN (symptom \u2192 mechanism \u2192 fix \u2192 verification) goes in the SKILL.md body; LOG (commit SHAs, npm/profile states, this release's change list, this session's narrative) goes in a references/ file. Body density IS reuse rate; a pattern fits in 2-8 physical lines.\n\nUser-preference embedding: when the user complains about how you handled a task, update the skill that governs that task \u2014 memory alone isn't enough. Memory says 'who the user is and what the current situation and state of your operations are'; skills say 'how to do this class of task for this user'. Both should carry user-preference lessons when relevant.\n\nIf you notice overlapping existing skills, mention it \u2014 the background curator handles consolidation.\n\nProtected skills (DO NOT edit these):\n  \u2022 Bundled skills (shipped with the platform).\n  \u2022 Hub-installed skills (installed from a hub).\nPinned skills are read-only to THIS background review pass \u2014 the pinned write guard refuses background changes, so only the foreground may update or archive them. Foreground and delegated-subagent writes to pinned skills remain allowed.\nIf the only skills that need updating are protected, say 'Nothing to save.' and stop.\n\nDo NOT capture as skills (these become persistent self-imposed constraints that bite you later when the environment changes):\n  \u2022 Environment-dependent failures: missing binaries, fresh-install errors, post-migration path mismatches, 'command not found', unconfigured credentials, uninstalled packages. The user can fix these \u2014 they are not durable rules.\n  \u2022 Negative claims about tools or features ('browser tools do not work', 'X tool is broken', 'cannot use Y'). These harden into refusals the agent cites against itself for months after the actual problem was fixed.\n  \u2022 Session-specific transient errors that resolved before the conversation ended. If retrying worked, the lesson is the retry pattern, not the original failure.\n  \u2022 One-off task narratives. A user asking 'summarize today's market' or 'analyze this PR' is not a class of work that warrants a skill.\n\nIf a tool failed because of setup state, capture the FIX (install command, config step, env var to set) under an existing setup or troubleshooting skill \u2014 never 'this tool does not work' as a standalone constraint.\n\nAct on whichever of the two dimensions has real signal. If genuinely nothing stands out on either, say 'Nothing to save.' and stop \u2014 but don't reach for that conclusion as a default.\n\nCHANNEL (subagent): this review channel mounts only the read-only `skill` tool \u2014 you have NO `skill_manage`, NO `memory`. Your deliverable is the structured JSON plan below (outputSchema). Describe the patches/creates you RECOMMEND in the plan; never narrate actions you took.";
+export declare const COMBINED_REVIEW_PLAN_PROMPT = "[Auto-review]\nReview the conversation above and update two things:\n\n**Memory**: who the user is. Did the user reveal persona, desires, preferences, personal details, or expectations about how you should behave? Save facts about the user and durable preferences with the memory tool.\n\n**Skills**: how to do this class of task. Be ACTIVE \u2014 most sessions produce at least one skill update. A pass that does nothing is a missed learning opportunity, not a neutral outcome.\n\nTarget shape of the skill library: CLASS-LEVEL skills with a rich SKILL.md and a references/ directory for session-specific detail. Not a long flat list of narrow one-session-one-skill entries.\n\nSignals that warrant a skill update (any one is enough):\n  \u2022 User corrected your style, tone, format, legibility, verbosity, or approach. Frustration is a FIRST-CLASS skill signal, not just a memory signal. 'stop doing X', 'don't format like this', 'I hate when you Y' \u2014 embed the lesson in the skill that governs that task so the next session starts fixed.\n  \u2022 Non-trivial technique, fix, workaround, or debugging path emerged.\n  \u2022 A skill that was loaded or consulted turned out wrong, missing, or outdated \u2014 patch it now.\n\nRead-before-write (enforced by this channel): update, patch, delete, or write support files ONLY into skills you loaded or read in THIS session \u2014 ops on unread skills are dropped; CREATE of a brand-new umbrella is the only exception.\n\nPreference order for skills \u2014 pick the earliest that fits:\n  1. UPDATE A CURRENTLY-LOADED SKILL. Check what skills were loaded or read in the conversation. If one of them covers the learning, PATCH it first. It was in play; it's the right place.\n  2. UPDATE AN EXISTING UMBRELLA. Patch it.\n  3. ADD A SUPPORT FILE under an existing umbrella via skill_manage action=write_file. Three kinds: references/<topic>.md for session-specific detail OR condensed knowledge banks (quoted research, API docs excerpts, domain notes) written concise and task-focused; templates/<name>.<ext> for starter files meant to be copied and modified; scripts/<name>.<ext> for statically re-runnable actions (verification, fixture generators, probes). Add a one-line pointer in SKILL.md so future agents find them.\n  4. RESTRUCTURE a loaded skill whose body grew log-like (rc/sha/date-dense sections, session-detail spirals, fat body with no support files) via skill_manage action=restructure with restructure: [{\"heading\": \"<the exact ## heading text>\", \"to_file\": \"references/<topic>.md\"}] \u2014 the ENTIRE ## section moves into the support file and its position becomes a pointer line; the skill's name and directory never change. Only propose headings that exist verbatim in the body.\n  5. CREATE A NEW CLASS-LEVEL UMBRELLA when nothing exists. Name at the class level \u2014 NOT a PR number, error string, codename, library-alone name, or 'fix-X / debug-Y' session artifact. If the name only fits today's task, fall back to (1), (2), or (3).\n\nTwo-tier deposition discipline (DSH addition): classify before writing \u2014 PATTERN (symptom \u2192 mechanism \u2192 fix \u2192 verification) goes in the SKILL.md body; LOG (commit SHAs, npm/profile states, this release's change list, this session's narrative) goes in a references/ file. Body density IS reuse rate; a pattern fits in 2-8 physical lines.\n\nUser-preference embedding: when the user complains about how you handled a task, update the skill that governs that task \u2014 memory alone isn't enough. Memory says 'who the user is and what the current situation and state of your operations are'; skills say 'how to do this class of task for this user'. Both should carry user-preference lessons when relevant.\n\nIf you notice overlapping existing skills, mention it \u2014 the background curator handles consolidation.\n\nProtected skills (DO NOT edit these):\n  \u2022 Bundled skills (shipped with the platform).\n  \u2022 Hub-installed skills (installed from a hub).\nPinned skills are read-only to THIS background review pass \u2014 the pinned write guard refuses background changes, so only the foreground may update or archive them. Foreground and delegated-subagent writes to pinned skills remain allowed.\nIf the only skills that need updating are protected, say 'Nothing to save.' and stop.\n\nDo NOT capture as skills (these become persistent self-imposed constraints that bite you later when the environment changes):\n  \u2022 Environment-dependent failures: missing binaries, fresh-install errors, post-migration path mismatches, 'command not found', unconfigured credentials, uninstalled packages. The user can fix these \u2014 they are not durable rules.\n  \u2022 Negative claims about tools or features ('browser tools do not work', 'X tool is broken', 'cannot use Y'). These harden into refusals the agent cites against itself for months after the actual problem was fixed.\n  \u2022 Session-specific transient errors that resolved before the conversation ended. If retrying worked, the lesson is the retry pattern, not the original failure.\n  \u2022 One-off task narratives. A user asking 'summarize today's market' or 'analyze this PR' is not a class of work that warrants a skill.\n\nIf a tool failed because of setup state, capture the FIX (install command, config step, env var to set) under an existing setup or troubleshooting skill \u2014 never 'this tool does not work' as a standalone constraint.\n\nAct on whichever of the two dimensions has real signal. If genuinely nothing stands out on either, say 'Nothing to save.' and stop \u2014 but don't reach for that conclusion as a default.\n\nCHANNEL (subagent): this review channel mounts only the read-only `skill` tool \u2014 you have NO `skill_manage`, NO `memory`. Your deliverable is the structured JSON plan below (outputSchema). Describe the patches/creates you RECOMMEND in the plan; never narrate actions you took.";
 export declare function reviewPrompt(kind: 'memory' | 'skill' | 'combined', channel?: 'agent' | 'plan'): string;
 export interface PromptBundle {
     id: string;

package/lib/types/skill-health.d.ts

@@ -0,0 +1,52 @@
+/**
+ * Skill structure-health domain (rc.73 A1, 008 design): a SECOND assessment
+ * dimension beside the six-factor usage quality — document hygiene, consumed
+ * by the curator health view and the `/evolution skills health` command.
+ *
+ * PURE and DERIVED: nothing is persisted; every assessment is computed from
+ * file facts at read time. The judgment split follows the original's
+ * boundary/治理 layering — deterministic signals here, refinement proposals
+ * stay in the review/curator judgment layer. Never become a 7th factor of
+ * `computeQualityScores` (different dimension, different consumers).
+ */
+export interface SkillHealthThresholds {
+    /** Soft body limit: body chars at/below stay 'healthy' by size; above ->
+     * 'warn'; >= 2x -> 'needs-restructure'. */
+    softBodyChars: number;
+    /** Stamp-density ceiling per KB of body text: rc.NN / commit shas / ISO
+     * dates per KB at/above this -> 'warn' (log-like content living in the
+     * body — the "invalid info" indicator). */
+    stampDensityPerKb: number;
+    /** Patch count at/above this with zero reads -> 'warn' (write-ghost: the
+     * skill is churned but nothing ever loads it). */
+    churnMinPatches: number;
+}
+export declare const DEFAULT_HEALTH_THRESHOLDS: SkillHealthThresholds;
+export type SkillHealthVerdict = 'healthy' | 'warn' | 'needs-restructure';
+/** Facts a caller already has; assessors never do IO. */
+export interface SkillHealthSnapshot {
+    skillName: string;
+    bodyChars: number;
+    bodyText?: string | undefined;
+    /** Number of non-empty support groups (references/ templates/ scripts/). */
+    supportGroups: number;
+    /** Usage-side patch count, when the caller has it (A2 churn dimension). */
+    patchCount?: number | undefined;
+    /** Usage-side view count, when the caller has it (A2 churn dimension). */
+    readCount?: number | undefined;
+}
+export interface SkillHealthDim {
+    bodyChars: number;
+    stampDensityPerKb: number | null;
+    supportGroups: number;
+    /** Usage churn facts; null when the caller supplied no counts. */
+    churnPatches: number | null;
+    churnReads: number | null;
+}
+export interface SkillHealthAssessment {
+    verdict: SkillHealthVerdict;
+    dims: SkillHealthDim;
+    reasons: string[];
+}
+export declare function assessStructureHealth(snapshot: SkillHealthSnapshot, thresholds?: SkillHealthThresholds): SkillHealthAssessment;
+//# sourceMappingURL=skill-health.d.ts.map

package/lib/types/skill-store.d.ts

@@ -8,6 +8,7 @@
  */
 import { type EvolutionIoLike } from './io.ts';
 import { type MutationRecord } from './mutations.ts';
+import { type SkillHealthAssessment, type SkillHealthThresholds } from './skill-health.ts';
 import type { EvolutionSkillMutatedEvent } from './events.ts';
 export interface SkillLimits {
     maxNameLength: number;
@@ -29,6 +30,22 @@ export interface SkillActionResult {
     message: string;
     path?: string;
 }
+/**
+ * One section move of a restructure proposal (008 batch B): a body section
+ * anchored by its exact `## heading` line is moved to a references/ support
+ * file and replaced by a pointer line. The skill name/dir never change —
+ * restructure is a content-distribution repair, not a routing change.
+ */
+export interface SkillRestructureMove {
+    /** The `##` heading title, matched as an exact line (leading `##` + spaces); no fuzzy matching. */
+    heading: string;
+    /** Destination support file: `references/<topic>.md` (references/ only — moved content is log/detail, never a template or script). */
+    toFile: string;
+}
+/** Upper bound of moves per restructure proposal (validator and core agree). */
+export declare const MAX_RESTRUCTURE_MOVES = 5;
+/** Restructure targets are plain markdown files under references/ — no subdirectories, no other support kind. */
+export declare const RESTRUCTURE_TARGET_RE: RegExp;
 /** Extra file name carried inside a snapshot's `extras/` directory. */
 export declare const SNAPSHOT_EXTRA_NAME_RE: RegExp;
 /** An opaque side file stored under a snapshot's `extras/` (curator state etc.). */
@@ -151,6 +168,16 @@ export declare class SkillLibrary {
     isPinned(rawName: string): Promise<boolean>;
     /** Count non-empty support subdirectories (richness input for quality scoring). */
     countSupportDirs(rawName: string): Promise<number>;
+    /**
+     * Structure-health facts for one skill (rc.73 A1, 008 design): body
+     * chars/density from SKILL.md, support groups from countSupportDirs, plus
+     * optional usage counts (A2 churn dimension) when the caller has them.
+     * Derived, never persisted; null when the skill is unreadable.
+     */
+    assessHealth(rawName: string, thresholds?: SkillHealthThresholds, counts?: {
+        patchCount?: number;
+        readCount?: number;
+    }): Promise<SkillHealthAssessment | null>;
     /** Best-effort audit trail entry; never blocks the mutation. */
     private audit;
     /** Recent mutation audit records (read-only inspection surface). */
@@ -170,8 +197,44 @@ export declare class SkillLibrary {
      * Merge the bodies of `sources` into `target` and archive the sources with
      * an absorbed-into marker. Hermes-style consolidation: overlapping skills
      * collapse into one, and the originals stay recoverable under `.archive/`.
+     *
+     * `mode:'append'` (default) appends each source body to the target. The
+     * target write goes through the tree-change kernel (009) — byte-level
+     * rollback, audit and the mutation event are kernel-owned. Package-integrity
+     * (009-I): append-mode consolidation REFUSES a source whose directory has
+     * support files or whose body carries support-directory links — an append
+     * would leave those references pointing at an archived package (dangling);
+     * the refusal message directs to the reference mode / whole-package archive.
+     *
+     * `mode:'reference'` writes each source's body (frontmatter stripped) into
+     * `target/references/<source>.md` and archives the source — the demote path
+     * (009-II). A source body with support-directory links is refused there too
+     * (the references file would carry links whose files were archived).
+     */
+    consolidate(target: string, sources: string[], origin?: WriteOrigin, options?: {
+        mode?: 'append' | 'reference';
+    }): Promise<SkillActionResult>;
+    /**
+     * Content-distribution repair (008 batch B, 009-R kernel): move body
+     * sections — anchored by their exact `## heading` lines — into references/
+     * support files and replace each span with a pointer line. The skill
+     * name/dir never change (routing stays; only content location shifts, so a
+     * fat body sheds its log-like detail). Deterministic, never automatic:
+     * candidates come from an approved review plan. The write batch goes
+     * through the tree-change kernel — one commit point, byte-level rollback.
+     * Package integrity (009-R): a moved section whose text carries
+     * support-directory links is refused (those links' files stay behind in the
+     * same package; the moved text belongs in references/ beside them).
+     */
+    restructure(rawName: string, moves: SkillRestructureMove[], origin?: WriteOrigin): Promise<SkillActionResult>;
+    /**
+     * Unified tree-change commit point (009 kernel): owns validation order,
+     * pre-read rollback bytes, two-phase write with byte-level rollback, audit
+     * and the mutation event. Mutators compose `TreeChangePlan`s — consolidate,
+     * restructure (and future reference-mode consolidations) never implement
+     * two-phase commit themselves.
      */
-    consolidate(target: string, sources: string[], origin?: WriteOrigin): Promise<SkillActionResult>;
+    private applyTreeChange;
     /**
      * Restore one skill from `.archive/` back to the active root. Hermes-style
      * recoverability: archival never deletes, and this is the control-plane

package/lib/types/usage.d.ts

@@ -80,6 +80,14 @@ export declare function bumpUse(map: UsageMap, name: string, when?: Date): void;
 export declare function bumpPatch(map: UsageMap, name: string, when?: Date): void;
 export declare function markAgentCreated(map: UsageMap, name: string): void;
 export declare function latestActivityAt(record: UsageRecord): string | null;
+/**
+ * Whether the library has ANY observed read evidence (C observation window):
+ * reads were invisible to the usage sidecar before A2, so `view_count` zero
+ * means "never read" ONLY after the first observed read exists anywhere in
+ * the map. Before that, churn-based signals (write-ghost) are untrustworthy
+ * and callers must suppress them. Pure and derived — never persisted.
+ */
+export declare function usageObserved(usage: ReadonlyMap<string, UsageRecord>): boolean;
 /**
  * Curator suppression sidecar: built-in skills the curator has archived stay
  * suppressed across re-seeds, so the lifecycle never fights a re-created

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@lmzhen/dsh-evolution-core",
   "description": "Shared stores, prompts, signals and lifecycle logic for the dsh-evolution plugin family (community build)",
-  "version": "0.1.0",
+  "version": "0.2.0-rc.2",
   "publishConfig": {
     "access": "public"
   },