@crouton-kit/crouter 0.3.32 → 0.3.34

package/dist/core/skill-sync/builtins.js

@@ -1,112 +0,0 @@
-/**
- * Built-in export registry for the skill-sync subsystem.
- *
- * These are the crtr-*generated* host artifacts — the `crtr-skills` boot skill
- * and any CLI slash-commands. Unlike the user-authored bidirectional manifest
- * pairs (engine.ts), an export pair has a single source of truth (code), so it
- * is one-way: render → marker-guarded write (see export.ts). The generators
- * (`bootSkillBody`, `renderSlashTemplate`) and their version markers were moved
- * here verbatim from bootstrap.ts when skill-sync became the sole host writer —
- * marker strings are byte-identical so already-deployed artifacts roll forward.
- */
-import { homedir } from 'node:os';
-import { join } from 'node:path';
-import { collectSlashSpecs } from '../command.js';
-// ── Boot skill ───────────────────────────────────────────────────────────────
-const BOOT_SKILL_NAME = 'crtr-skills';
-const BOOT_SKILL_MARKER = '<!-- crtr-boot-skill v2 -->';
-export const BOOT_SKILL_MARKER_PREFIX = '<!-- crtr-boot-skill v';
-function bootSkillBody() {
-    return `---
-name: crtr-skills
-description: 'Author, list, search, and load crtr memory documents (knowledge, preferences) via the crtr CLI. These are durable agent memory — markdown future LLM sessions load on demand. Use when the user wants to remember/save knowledge, build a context primer, or recall a previously saved doc. Triggers: "save", "remember", "build context for", "what skills do we have", "skill for X".'
-argument-hint: [topic or verb]
----
-
-${BOOT_SKILL_MARKER}
-
-# /crtr-skills — crtr memory router
-
-crtr memory documents = durable agent memory (kind: knowledge or preference).
-Written for **future LLM sessions**, not the user. \`crtr memory\` is the
-surface — author, discover, and load them.
-
-## Route by intent
-
-- **Capture** ("save", "remember", "build context for", "make a skill"):
-  \`crtr memory write <name> --kind <knowledge|preference>\` with the
-  body piped on stdin — e.g.
-  \`crtr memory write $ARGUMENTS --kind knowledge <<'EOF' … EOF\`. Run
-  \`crtr memory write -h\` for the full frontmatter schema
-  (--when-and-why-to-read, --short-form, --scope, visibility rungs), then
-  \`crtr memory lint\` to validate what you wrote.
-- **Find** ("what do we have on X"): \`crtr memory find "$ARGUMENTS"\` →
-  \`crtr memory read <name>\` on the best hit (add --body/--grep to search
-  bodies).
-- **Load by name**: \`crtr memory read <name>\`.
-- **List all**: \`crtr memory list\`.
-
-If \`$ARGUMENTS\` is empty, ask the user what they want before running.
-
-## Rules
-
-- CLI stdout is the prompt — act on it, don't paraphrase to the user.
-- Append \`-h\` at any leaf (\`crtr memory write -h\`) for its full schema
-  before authoring.
-- If \`crtr\` is not on PATH, tell the user and stop.
-`;
-}
-// ── Slash commands ───────────────────────────────────────────────────────────
-const SLASH_CMD_MARKER = '<!-- crtr-mode-cmd v1 -->';
-export const SLASH_CMD_MARKER_PREFIX = '<!-- crtr-mode-cmd v';
-/** Render a SlashSpec to a full template file (frontmatter + marker + body). */
-function renderSlashTemplate(spec) {
-    const hint = spec.argumentHint !== undefined
-        ? `argument-hint: ${JSON.stringify(spec.argumentHint)}\n`
-        : '';
-    return `---\ndescription: ${spec.description}\n${hint}---\n\n${SLASH_CMD_MARKER}\n\n${spec.body}\n`;
-}
-// ── Host roots ───────────────────────────────────────────────────────────────
-function claudeSkillsRoot() {
-    return join(homedir(), '.claude', 'skills');
-}
-function piSkillsRoot() {
-    return join(homedir(), '.pi', 'agent', 'skills');
-}
-function claudeCommandsRoot() {
-    return join(homedir(), '.claude', 'commands');
-}
-function piPromptsRoot() {
-    return join(homedir(), '.pi', 'agent', 'prompts');
-}
-// ── Registry ─────────────────────────────────────────────────────────────────
-/** The crtr-generated export artifacts for this command tree: the boot skill
- *  (both hosts, bundle layout) plus one pair per opted-in slash command (both
- *  hosts, file layout). */
-export function builtinExportPairs(root) {
-    const pairs = [
-        {
-            id: '@boot/crtr-skills',
-            name: BOOT_SKILL_NAME,
-            markerPrefix: BOOT_SKILL_MARKER_PREFIX,
-            render: bootSkillBody,
-            targets: [
-                { host: 'claude', dir: claudeSkillsRoot, layout: 'bundle' },
-                { host: 'pi', dir: piSkillsRoot, layout: 'bundle' },
-            ],
-        },
-    ];
-    for (const spec of collectSlashSpecs(root)) {
-        pairs.push({
-            id: `@cmd/${spec.name}`,
-            name: spec.name,
-            markerPrefix: SLASH_CMD_MARKER_PREFIX,
-            render: () => renderSlashTemplate(spec),
-            targets: [
-                { host: 'claude', dir: claudeCommandsRoot, layout: 'file' },
-                { host: 'pi', dir: piPromptsRoot, layout: 'file' },
-            ],
-        });
-    }
-    return pairs;
-}

package/dist/core/skill-sync/claude-plugins.d.ts

@@ -1,23 +0,0 @@
-/**
- * Claude-plugin endpoint resolution for skill-sync.
- *
- * The `claude-plugin` endpoint scope addresses a skill IN PLACE at the path
- * where Claude actually installs the owning plugin — `<installPath>/skills/<name>`
- * — instead of forcing a copy under `~/.claude/skills/`. The install path is read
- * from Claude's OWN registry (`~/.claude/plugins/installed_plugins.json`), keyed
- * by the marketplace-qualified plugin key (`<plugin>@<marketplace>`), gated on the
- * enable state in `~/.claude/settings.json` → `enabledPlugins`.
- *
- * This is Claude's registry, deliberately NOT crtr's plugin registry
- * (`resolver.ts` / `findPluginByName`): the two are independent installs.
- *
- * Strictness (no lenient fallback): a key that is unknown, disabled, or whose
- * recorded install path is missing on disk is a HARD error naming it.
- */
-/**
- * Resolve a Claude plugin's on-disk install path from its marketplace-qualified
- * key (`<plugin>@<marketplace>`, e.g. `devcore@crouton-kit`). Throws naming the
- * key when it is not installed, not enabled, or has no install path present on
- * disk.
- */
-export declare function resolveClaudePluginInstallPath(key: string): string;

package/dist/core/skill-sync/claude-plugins.js

@@ -1,71 +0,0 @@
-/**
- * Claude-plugin endpoint resolution for skill-sync.
- *
- * The `claude-plugin` endpoint scope addresses a skill IN PLACE at the path
- * where Claude actually installs the owning plugin — `<installPath>/skills/<name>`
- * — instead of forcing a copy under `~/.claude/skills/`. The install path is read
- * from Claude's OWN registry (`~/.claude/plugins/installed_plugins.json`), keyed
- * by the marketplace-qualified plugin key (`<plugin>@<marketplace>`), gated on the
- * enable state in `~/.claude/settings.json` → `enabledPlugins`.
- *
- * This is Claude's registry, deliberately NOT crtr's plugin registry
- * (`resolver.ts` / `findPluginByName`): the two are independent installs.
- *
- * Strictness (no lenient fallback): a key that is unknown, disabled, or whose
- * recorded install path is missing on disk is a HARD error naming it.
- */
-import { existsSync, readFileSync } from 'node:fs';
-import { homedir } from 'node:os';
-import { join } from 'node:path';
-import { usage } from '../errors.js';
-function claudeDir() {
-    return join(homedir(), '.claude');
-}
-/**
- * Resolve a Claude plugin's on-disk install path from its marketplace-qualified
- * key (`<plugin>@<marketplace>`, e.g. `devcore@crouton-kit`). Throws naming the
- * key when it is not installed, not enabled, or has no install path present on
- * disk.
- */
-export function resolveClaudePluginInstallPath(key) {
-    const registryPath = join(claudeDir(), 'plugins', 'installed_plugins.json');
-    if (!existsSync(registryPath)) {
-        throw usage(`skill-sync: Claude plugin registry not found at ${registryPath}`);
-    }
-    let registry;
-    try {
-        registry = JSON.parse(readFileSync(registryPath, 'utf8'));
-    }
-    catch (err) {
-        throw usage(`skill-sync: invalid ${registryPath}: ${err.message}`);
-    }
-    const entries = registry.plugins?.[key];
-    if (!Array.isArray(entries) || entries.length === 0) {
-        throw usage(`skill-sync: Claude plugin "${key}" is not installed ` +
-            `(no entry in ${registryPath})`);
-    }
-    if (!isClaudePluginEnabled(key)) {
-        throw usage(`skill-sync: Claude plugin "${key}" is installed but not enabled ` +
-            `(settings.json enabledPlugins)`);
-    }
-    const install = entries.find((e) => e.installPath && existsSync(e.installPath));
-    if (!install?.installPath) {
-        throw usage(`skill-sync: Claude plugin "${key}" has no install path present on disk`);
-    }
-    return install.installPath;
-}
-/** True iff `enabledPlugins[key] === true` in `~/.claude/settings.json`. A
- *  missing or unparseable settings file means "not enabled" — the caller turns
- *  that into a hard error naming the key. */
-function isClaudePluginEnabled(key) {
-    const settingsPath = join(claudeDir(), 'settings.json');
-    if (!existsSync(settingsPath))
-        return false;
-    try {
-        const settings = JSON.parse(readFileSync(settingsPath, 'utf8'));
-        return settings.enabledPlugins?.[key] === true;
-    }
-    catch {
-        return false;
-    }
-}

package/dist/core/skill-sync/engine.d.ts

@@ -1,42 +0,0 @@
-/**
- * Reconcile engine (Phase P6) — the single, per-pair, direction-agnostic
- * reconcile for bidirectional crtr ↔ Claude skill sync.
- *
- * `reconcilePair` is the ONLY reconcile routine (R-U3): there is no forward
- * path + reverse path. Body and asset reconciliation is a symmetric 3-way merge
- * (base = snapshot, ours = crtr, theirs = claude); frontmatter is the only
- * asymmetric axis and all of that asymmetry lives in the translation profile
- * (P5). The snapshot (P3) is the sole change-detector (R-U4): nothing here reads
- * mtimes, fingerprints, or a stamp file.
- *
- * Strictness (R-U6): a conflict — overlapping body/asset merge, a both-sides
- * non-equivalent frontmatter divergence, an asset deleted-on-one ∧ edited-on-the
- * other, or a first-sync divergence with no common base — writes NOTHING for the
- * pair, leaves both endpoints + the snapshot byte-untouched, and surfaces a
- * git-style conflict report. There is no "best-effort" partial write and no
- * silent side-pick.
- *
- * `--dry-run` (R-O1): every merge is computed and the would-be status returned,
- * but no endpoint file, snapshot, or conflict report is touched.
- */
-import type { Pair } from './manifest.js';
-import type { TranslationProfile } from './profile.js';
-/** The outcome of reconciling one pair. `wrote` counts endpoint files
- *  created/updated (never deletions, never the snapshot bookkeeping). */
-export interface PairResult {
-    id: string;
-    status: 'synced' | 'conflict' | 'noop';
-    wrote: number;
-}
-export interface ReconcileOpts {
-    dryRun: boolean;
-}
-/**
- * Reconcile a single enrolled pair (R-E2). Resolves both endpoints, loads (or
- * seeds) the snapshot, 3-way merges body + assets and translate-and-owns the
- * frontmatter, then either writes through cleanly to both sides or reports the
- * conflict and skips. Never throws on a *content* conflict (that is a reported
- * outcome); throws only on a structural/configuration error (an unresolvable
- * endpoint, both endpoints missing) so the caller surfaces it as a hard stop.
- */
-export declare function reconcilePair(pair: Pair, profile: TranslationProfile, opts: ReconcileOpts): PairResult;