peaks-loop 4.0.0-beta.7 → 4.0.0-beta.8

package/dist/src/services/standards/loop-engineering-lint.d.ts

@@ -1,38 +0,0 @@
-/**
- * Loop Engineering guidelines linter (M0).
- *
- * Pure function: takes the raw markdown text of
- * `.peaks/standards/loop-engineering-guidelines.md` and returns either
- * `{ ok: true, redLines: [...] }` or `{ ok: false, findings: [...] }`.
- *
- * The four required sections per red line (karpathy-style form) are:
- *   - Failure modes
- *   - Rewrite
- *   - Self-check
- *   - Out-of-scope
- *
- * Each red line is identified by a heading like `## RL-0 — ...`.
- *
- * The lint intentionally does NOT touch any application-level code; it
- * only parses the guideline file. The peaks CLI command
- * `peaks standards lint --category loop-engineering` (registered in M0's
- * plan) will read this file from disk and call this function.
- */
-export declare const EXPECTED_RED_LINE_IDS: readonly ["RL-0", "RL-1", "RL-2", "RL-3", "RL-4", "RL-5", "RL-6", "RL-7", "RL-8", "RL-9"];
-export type RedLineId = (typeof EXPECTED_RED_LINE_IDS)[number];
-export declare const REQUIRED_SECTIONS: readonly ["Failure modes", "Rewrite", "Self-check", "Out-of-scope"];
-export type RedLineSection = (typeof REQUIRED_SECTIONS)[number];
-export interface RedLineReport {
-    id: RedLineId;
-    title: string;
-    sections: Partial<Record<RedLineSection, string>>;
-}
-export type LintResult = {
-    ok: true;
-    redLines: RedLineReport[];
-} | {
-    ok: false;
-    findings: string[];
-    redLines: RedLineReport[];
-};
-export declare function lintLoopEngineeringGuidelines(raw: string): LintResult;

package/dist/src/services/standards/loop-engineering-lint.js

@@ -1,101 +0,0 @@
-/**
- * Loop Engineering guidelines linter (M0).
- *
- * Pure function: takes the raw markdown text of
- * `.peaks/standards/loop-engineering-guidelines.md` and returns either
- * `{ ok: true, redLines: [...] }` or `{ ok: false, findings: [...] }`.
- *
- * The four required sections per red line (karpathy-style form) are:
- *   - Failure modes
- *   - Rewrite
- *   - Self-check
- *   - Out-of-scope
- *
- * Each red line is identified by a heading like `## RL-0 — ...`.
- *
- * The lint intentionally does NOT touch any application-level code; it
- * only parses the guideline file. The peaks CLI command
- * `peaks standards lint --category loop-engineering` (registered in M0's
- * plan) will read this file from disk and call this function.
- */
-export const EXPECTED_RED_LINE_IDS = [
-    'RL-0',
-    'RL-1',
-    'RL-2',
-    'RL-3',
-    'RL-4',
-    'RL-5',
-    'RL-6',
-    'RL-7',
-    'RL-8',
-    'RL-9',
-];
-export const REQUIRED_SECTIONS = [
-    'Failure modes',
-    'Rewrite',
-    'Self-check',
-    'Out-of-scope',
-];
-const RED_LINE_HEADING = /^##\s+(RL-\d+)\s+[—-]\s+(.+?)\s*$/gm;
-const SECTION_HEADING = /^##\s+(Failure modes|Rewrite|Self-check|Out-of-scope)\s*$/gm;
-export function lintLoopEngineeringGuidelines(raw) {
-    const findings = [];
-    if (!raw || raw.trim().length === 0) {
-        return { ok: false, findings: ['guideline file is empty'], redLines: [] };
-    }
-    const redLines = parseRedLines(raw);
-    if (redLines.length === 0) {
-        findings.push('no red line headings (`## RL-N — ...`) found');
-    }
-    for (const id of EXPECTED_RED_LINE_IDS) {
-        const rl = redLines.find((r) => r.id === id);
-        if (!rl) {
-            findings.push(`missing red line: ${id}`);
-            continue;
-        }
-        for (const section of REQUIRED_SECTIONS) {
-            if (!rl.sections[section] || rl.sections[section].trim().length === 0) {
-                findings.push(`${id} is missing section "${section}"`);
-            }
-        }
-    }
-    if (findings.length > 0) {
-        return { ok: false, findings, redLines };
-    }
-    return { ok: true, redLines };
-}
-function parseRedLines(raw) {
-    const headingRegex = new RegExp(RED_LINE_HEADING.source, RED_LINE_HEADING.flags);
-    const sectionRegex = new RegExp(SECTION_HEADING.source, SECTION_HEADING.flags);
-    const headings = [];
-    let m;
-    while ((m = headingRegex.exec(raw)) !== null) {
-        headings.push({ id: m[1] ?? '', title: m[2] ?? '', start: m.index + m[0].length, end: raw.length });
-    }
-    for (let i = 0; i < headings.length - 1; i++) {
-        headings[i].end = headings[i + 1].start;
-    }
-    if (headings.length > 0) {
-        headings[headings.length - 1].end = raw.length;
-    }
-    return headings.map((h) => {
-        const body = raw.slice(h.start, h.end);
-        const sections = {};
-        const sectionMatches = [];
-        let sm;
-        while ((sm = sectionRegex.exec(body)) !== null) {
-            sectionMatches.push({ name: sm[1], start: sm.index + sm[0].length });
-        }
-        for (let i = 0; i < sectionMatches.length; i++) {
-            const start = sectionMatches[i].start;
-            const end = i + 1 < sectionMatches.length ? sectionMatches[i + 1].start - sectionMatches[i].start : body.length - start;
-            const text = body.slice(start, start + end);
-            sections[sectionMatches[i].name] = text;
-        }
-        return {
-            id: h.id,
-            title: h.title,
-            sections,
-        };
-    });
-}

package/dist/src/services/standards/loop-engineering-readiness-lint.d.ts

@@ -1,111 +0,0 @@
-/**
- * Loop Engineering Readiness linter (M6 — peak-spec §7.5 + §8.4).
- *
- * Pure function: takes the raw markdown text of a peaks-* SKILL.md
- * file and returns either
- *   { ok: true, findings: [] }
- * or
- *   { ok: false, findings: string[] }.
- *
- * The lint asserts three structural properties the spec binds every
- * Loop-Engineering-participating peaks-* skill to:
- *
- *   1. The skill references the shared guideline file
- *      `.peaks/standards/loop-engineering-guidelines.md` (or its
- *      alias `.peaks/standards/loop-engineering-guidelines.md`).
- *      Reference may appear anywhere in the body — code fence,
- *      plain prose, or list item — as long as the literal token is
- *      present.
- *
- *   2. The skill does NOT introduce a CLI verb that bypasses the
- *      LLM-coordinated model. We flag lines that look like
- *      "Run `peaks <verb>` to …" where `<verb>` is not in the
- *      allowlist of LLM-owned sediment / asset / evolution verbs.
- *      The user types NL; the LLM runs the CLI on the user's behalf
- *      (RL-1 / Human-NL-Choice-Only).
- *
- *   3. The skill does NOT introduce a JSON / manifest
- *      hand-authoring surface. We flag lines containing phrases
- *      like "Edit the manifest", "write the JSON", "fill the JSON
- *      file", etc., when they are not part of an explicit allowlist
- *      (allowlist only references; never an instructional phrase).
- *
- * Each finding is a single line of the form:
- *   "<rule>: <offending excerpt>"
- * so a downstream CLI can render it directly without further
- * parsing.
- *
- * The lint intentionally does NOT touch any application-level
- * code; it only parses a SKILL.md text. The peaks CLI command
- * `peaks skill lint --category loop-engineering-readiness
- *   --path <skill-dir>`
- * (registered in src/cli/commands/skill-loop-engineering-readiness.ts)
- * reads the SKILL.md from disk and calls this function.
- *
- * Per RL-1 / Human-NL-Choice-Only and
- * `.peaks/memory/two-forms-only-rule.md`, the user only ever picks
- * via AskUserQuestion or describes in NL; the LLM runs the CLI.
- * This lint is what stops a future peaks-* skill from regressing
- * that rule at the textual layer.
- */
-export type LintFinding = string;
-export type ReadinessLintResult = {
-    ok: true;
-    findings: [];
-} | {
-    ok: false;
-    findings: LintFinding[];
-};
-/**
- * The shared guideline file that every Loop-Engineering-participating
- * peaks-* skill must reference. Both the canonical path and the
- * common alias are accepted.
- *
- * The alias is intentionally identical to the canonical path here:
- * the spec sometimes renders it as
- *   `.peaks/standards/loop-engineering-guidelines.md`
- * with a slash prefix and sometimes without. We accept both.
- */
-export declare const LOOP_ENGINEERING_GUIDELINE_PATHS: readonly [".peaks/standards/loop-engineering-guidelines.md"];
-/**
- * The allowlist of CLI verbs that a peaks-* SKILL.md may legitimately
- * instruct an LLM to invoke on the user's behalf. These are the
- * sediment / asset / evolution surface verbs introduced in
- * 2026-07-07-loop-engineering-crystallization-design §7.4 plus the
- * 18-verb sediment pool from 2026-07-04-peaks-maker-dynamic-skill-
- * sediment-design §4.2.
- *
- * Any other `peaks <verb>` token that appears in the form
- *   "Run `peaks <verb>` to …"
- * is treated as a CLI-verb-bypass attempt and flagged.
- */
-export declare const ALLOWED_CLI_VERBS: Set<string>;
-/**
- * Phrases that constitute a JSON / manifest hand-authoring surface.
- * If a SKILL.md instructs the user to perform one of these actions,
- * it violates RL-1 / Human-NL-Choice-Only and is flagged.
- *
- * Each entry is a lowercase substring matched against each line of
- * the SKILL.md. The match is case-insensitive; the surrounding
- * `<verb>` placeholders in the original spec are matched literally.
- */
-export declare const JSON_HAND_AUTHORING_PHRASES: ReadonlyArray<string>;
-/**
- * Phrases that explicitly reference a JSON / manifest surface but
- * in an ALLOWED way — e.g. "the manifest is written by the CLI" or
- * "see manifest schema for details". A line that contains one of
- * these allowlisted phrases is NOT flagged even if it contains a
- * JSON-hand-authoring phrase elsewhere on the same line.
- *
- * The allowlist is intentionally narrow; it must mention either
- * the CLI as the writer OR a schema reference, NOT an instructional
- * verb targeting the user.
- */
-export declare const JSON_REFERENCE_ALLOWLIST: ReadonlyArray<string>;
-/**
- * Lint a SKILL.md text for Loop Engineering readiness.
- *
- * @param skillMdText raw markdown text of a peaks-* SKILL.md
- * @returns a ReadinessLintResult
- */
-export declare function lintSkillLoopEngineeringReadiness(skillMdText: string): ReadinessLintResult;

package/dist/src/services/standards/loop-engineering-readiness-lint.js

@@ -1,248 +0,0 @@
-/**
- * Loop Engineering Readiness linter (M6 — peak-spec §7.5 + §8.4).
- *
- * Pure function: takes the raw markdown text of a peaks-* SKILL.md
- * file and returns either
- *   { ok: true, findings: [] }
- * or
- *   { ok: false, findings: string[] }.
- *
- * The lint asserts three structural properties the spec binds every
- * Loop-Engineering-participating peaks-* skill to:
- *
- *   1. The skill references the shared guideline file
- *      `.peaks/standards/loop-engineering-guidelines.md` (or its
- *      alias `.peaks/standards/loop-engineering-guidelines.md`).
- *      Reference may appear anywhere in the body — code fence,
- *      plain prose, or list item — as long as the literal token is
- *      present.
- *
- *   2. The skill does NOT introduce a CLI verb that bypasses the
- *      LLM-coordinated model. We flag lines that look like
- *      "Run `peaks <verb>` to …" where `<verb>` is not in the
- *      allowlist of LLM-owned sediment / asset / evolution verbs.
- *      The user types NL; the LLM runs the CLI on the user's behalf
- *      (RL-1 / Human-NL-Choice-Only).
- *
- *   3. The skill does NOT introduce a JSON / manifest
- *      hand-authoring surface. We flag lines containing phrases
- *      like "Edit the manifest", "write the JSON", "fill the JSON
- *      file", etc., when they are not part of an explicit allowlist
- *      (allowlist only references; never an instructional phrase).
- *
- * Each finding is a single line of the form:
- *   "<rule>: <offending excerpt>"
- * so a downstream CLI can render it directly without further
- * parsing.
- *
- * The lint intentionally does NOT touch any application-level
- * code; it only parses a SKILL.md text. The peaks CLI command
- * `peaks skill lint --category loop-engineering-readiness
- *   --path <skill-dir>`
- * (registered in src/cli/commands/skill-loop-engineering-readiness.ts)
- * reads the SKILL.md from disk and calls this function.
- *
- * Per RL-1 / Human-NL-Choice-Only and
- * `.peaks/memory/two-forms-only-rule.md`, the user only ever picks
- * via AskUserQuestion or describes in NL; the LLM runs the CLI.
- * This lint is what stops a future peaks-* skill from regressing
- * that rule at the textual layer.
- */
-/**
- * The shared guideline file that every Loop-Engineering-participating
- * peaks-* skill must reference. Both the canonical path and the
- * common alias are accepted.
- *
- * The alias is intentionally identical to the canonical path here:
- * the spec sometimes renders it as
- *   `.peaks/standards/loop-engineering-guidelines.md`
- * with a slash prefix and sometimes without. We accept both.
- */
-export const LOOP_ENGINEERING_GUIDELINE_PATHS = [
-    '.peaks/standards/loop-engineering-guidelines.md',
-];
-/**
- * The allowlist of CLI verbs that a peaks-* SKILL.md may legitimately
- * instruct an LLM to invoke on the user's behalf. These are the
- * sediment / asset / evolution surface verbs introduced in
- * 2026-07-07-loop-engineering-crystallization-design §7.4 plus the
- * 18-verb sediment pool from 2026-07-04-peaks-maker-dynamic-skill-
- * sediment-design §4.2.
- *
- * Any other `peaks <verb>` token that appears in the form
- *   "Run `peaks <verb>` to …"
- * is treated as a CLI-verb-bypass attempt and flagged.
- */
-export const ALLOWED_CLI_VERBS = new Set([
-    // sediment pool verbs (M6 reference; peak-maker's owned surface)
-    'add-segment',
-    'add-bee',
-    'refine-bee',
-    'clone-bee',
-    'promote',
-    'retire',
-    'dispose',
-    'releases',
-    'release-show',
-    'release-diff',
-    'export',
-    'import',
-    'gc-blobs',
-    'list',
-    'show',
-    'search',
-    'recent',
-    'rebuild-index',
-    // loop crystallizer surface (§7.4)
-    'loop',
-    'crystallize',
-    // evolution ratchet surface (§7.4)
-    'evolution',
-    'propose',
-    'evaluate',
-    'revert',
-    'mark-keep',
-    // umbrella asset surface (§7.4)
-    'asset',
-    'status',
-    // adapter surface (peaks-maker's owned skill runtime)
-    'adapter',
-    // lint surface (this command's own kind)
-    'lint',
-    'standards',
-    'skill',
-    'ready',
-]);
-/**
- * Phrases that constitute a JSON / manifest hand-authoring surface.
- * If a SKILL.md instructs the user to perform one of these actions,
- * it violates RL-1 / Human-NL-Choice-Only and is flagged.
- *
- * Each entry is a lowercase substring matched against each line of
- * the SKILL.md. The match is case-insensitive; the surrounding
- * `<verb>` placeholders in the original spec are matched literally.
- */
-export const JSON_HAND_AUTHORING_PHRASES = [
-    'edit the manifest',
-    'edit your manifest',
-    'edit the json',
-    'edit the .json file',
-    'write the json',
-    'write the json manifest',
-    'write the manifest json',
-    'fill the json',
-    'fill in the json',
-    'fill in the manifest',
-    'fill in the manifest.json',
-    'hand-author the manifest',
-    'hand-author the json',
-    'open the manifest and',
-    'open the manifest.json and',
-    'manually edit the manifest',
-    'manually edit the json',
-];
-/**
- * Phrases that explicitly reference a JSON / manifest surface but
- * in an ALLOWED way — e.g. "the manifest is written by the CLI" or
- * "see manifest schema for details". A line that contains one of
- * these allowlisted phrases is NOT flagged even if it contains a
- * JSON-hand-authoring phrase elsewhere on the same line.
- *
- * The allowlist is intentionally narrow; it must mention either
- * the CLI as the writer OR a schema reference, NOT an instructional
- * verb targeting the user.
- */
-export const JSON_REFERENCE_ALLOWLIST = [
-    'the cli writes',
-    'written by the cli',
-    'written by peaks',
-    'manifest schema',
-    'see the manifest schema',
-    'see manifest schema',
-    'schema_version',
-    'peaks.bundle/1',
-    'peaks.loop/1',
-    'peaks.bee/1',
-];
-// ---------------------------------------------------------------------------
-// Pure function
-// ---------------------------------------------------------------------------
-/**
- * Lint a SKILL.md text for Loop Engineering readiness.
- *
- * @param skillMdText raw markdown text of a peaks-* SKILL.md
- * @returns a ReadinessLintResult
- */
-export function lintSkillLoopEngineeringReadiness(skillMdText) {
-    const findings = [];
-    if (typeof skillMdText !== 'string' || skillMdText.trim().length === 0) {
-        return {
-            ok: false,
-            findings: ['skill-md-empty: SKILL.md text is empty or missing'],
-        };
-    }
-    checkGuidelineReference(skillMdText, findings);
-    checkCliVerbBypass(skillMdText, findings);
-    checkJsonHandAuthoring(skillMdText, findings);
-    if (findings.length > 0) {
-        return { ok: false, findings };
-    }
-    return { ok: true, findings: [] };
-}
-// ---------------------------------------------------------------------------
-// Individual checks
-// ---------------------------------------------------------------------------
-function checkGuidelineReference(text, findings) {
-    // Strip code fences before checking — references inside ``` blocks
-    // are still valid references (the lint accepts them), but we strip
-    // so the substring match is unambiguous.
-    const stripped = text;
-    for (const ref of LOOP_ENGINEERING_GUIDELINE_PATHS) {
-        if (stripped.includes(ref)) {
-            return;
-        }
-    }
-    findings.push(`missing-guideline-reference: SKILL.md must reference ${LOOP_ENGINEERING_GUIDELINE_PATHS[0]} (spec §7.5 / §8.4 / RL-8)`);
-}
-function checkCliVerbBypass(text, findings) {
-    // Match lines that contain `peaks <verb>` in a run-this-command
-    // pattern: "Run `peaks <verb>` to …" or "`peaks <verb>` to …" or
-    // "use `peaks <verb>` to …".
-    //
-    // The regex is intentionally narrow: it requires backticks around
-    // `peaks <verb>` so prose that mentions "peaks <verb>" as a noun
-    // (e.g. "peaks skill sediment list") is not flagged. The verb
-    // token is captured as the first `[a-z][a-z0-9-]*` chunk after
-    // "peaks "; everything between the verb and the closing backtick
-    // is allowed (e.g. `peaks custom-evolve my-bee` — verb is
-    // "custom-evolve", args are "my-bee").
-    const lineRegex = /^\s*[-*]?\s*(?:Run|Use|Type|Execute)\s+`peaks\s+([a-z][a-z0-9-]*)[^`]*`/gim;
-    const lines = text.split(/\r?\n/);
-    for (let i = 0; i < lines.length; i++) {
-        const line = lines[i];
-        let m;
-        lineRegex.lastIndex = 0;
-        while ((m = lineRegex.exec(line)) !== null) {
-            const verb = m[1];
-            if (!ALLOWED_CLI_VERBS.has(verb)) {
-                const excerpt = line.trim().slice(0, 120);
-                findings.push(`cli-verb-bypass: line ${i + 1} introduces CLI verb \`peaks ${verb}\` to be typed by the user (${excerpt}) — only LLM-coordinated verbs from the sediment/asset/evolution surface are allowed (RL-1)`);
-            }
-        }
-    }
-}
-function checkJsonHandAuthoring(text, findings) {
-    const lines = text.split(/\r?\n/);
-    for (let i = 0; i < lines.length; i++) {
-        const line = lines[i];
-        const lowered = line.toLowerCase();
-        const matchedPhrase = JSON_HAND_AUTHORING_PHRASES.find((p) => lowered.includes(p));
-        if (!matchedPhrase)
-            continue;
-        const isAllowlisted = JSON_REFERENCE_ALLOWLIST.some((p) => lowered.includes(p));
-        if (isAllowlisted)
-            continue;
-        const excerpt = line.trim().slice(0, 120);
-        findings.push(`json-hand-authoring: line ${i + 1} introduces JSON / manifest hand-authoring surface ("${matchedPhrase}") — ${excerpt} (RL-1: user only picks or describes in NL)`);
-    }
-}

package/dist/src/services/standards/migrate-claude-rules-service.d.ts

@@ -1,19 +0,0 @@
-export interface MigrateClaudeRulesInput {
-    readonly projectRoot: string;
-    readonly apply?: boolean;
-}
-export interface MigrateClaudeRulesData {
-    readonly backupPath: string | null;
-    readonly thinnedFiles: readonly string[];
-    readonly scaffoldedFiles: readonly string[];
-    readonly preservedFiles: readonly string[];
-    readonly wouldChange: boolean;
-    readonly applied: boolean;
-    readonly nextActions: readonly string[];
-}
-export interface MigrateClaudeRulesResult {
-    readonly ok: true;
-    readonly data: MigrateClaudeRulesData;
-    readonly warnings: readonly string[];
-}
-export declare function migrateClaudeRules(input: MigrateClaudeRulesInput): MigrateClaudeRulesResult;