ctxr-cli 0.8.0 → 0.10.0

package/dist/core/migrations/drop-access-axes.js

@@ -1,54 +0,0 @@
-import path from 'node:path';
-import { readConfig } from '../../config/load.js';
-import { renderStoreConfig } from '../../config/render.js';
-import { writeFileAtomic } from '../fs/atomic.js';
-const CONFIG_DELTA = {
-    path: 'contexture.yaml',
-    description: 'remove the visibility:, disclosure:, and fields: blocks, and set schema_version to 8',
-};
-/** The retired top-level keys, named here as fixed historical literals — no constant for them survives. */
-const RETIRED_KEYS = ['visibility', 'disclosure', 'fields'];
-/**
- * retire-the-access-axes: the visibility and disclosure axes are removed, and
- * with them `fields.visibility` (the configurable name of the visibility
- * frontmatter key).
- *
- * Unlike 0005, this migration cannot lean on `readConfig` having already
- * stripped the legacy shape: all three keys are TOP-LEVEL, and
- * `StoreConfigSchema` is `.passthrough()`, so they survive parsing intact.
- * Deleting them explicitly is the whole job.
- *
- * No note is rewritten (design.md D3). A note's retired visibility-field key
- * stays in its frontmatter, unread — `parseNote` reads frontmatter into a
- * `Record<string, unknown>` and nothing consumes that key any more, so it
- * costs nothing at runtime and keeps the removal cheap to reverse. Stripping
- * it would make re-entry a hand re-labelling pass over every note.
- *
- * Pending-ness is `schema_version < 8`, not key presence — the rule every
- * migration from 0002 onward established. A store could have had its config
- * hand-edited to drop the keys while still sitting at an older version, and
- * it still needs the version bump.
- */
-export const dropAccessAxesMigration = {
-    id: '0008-drop-access-axes',
-    fromVersion: 7,
-    toVersion: 8,
-    description: 'Remove the visibility:, disclosure:, and fields: blocks from contexture.yaml, and bump schema_version to 8. No note is modified.',
-    async plan(store) {
-        if (store.config.schema_version >= 8)
-            return [];
-        return [CONFIG_DELTA];
-    },
-    async apply(store) {
-        if (store.config.schema_version >= 8)
-            return [];
-        const configPath = path.join(store.root, 'contexture.yaml');
-        const currentConfig = await readConfig(store.root);
-        const nextConfig = { ...currentConfig, schema_version: 8 };
-        for (const key of RETIRED_KEYS)
-            delete nextConfig[key];
-        await writeFileAtomic(configPath, renderStoreConfig(nextConfig));
-        return [CONFIG_DELTA];
-    },
-};
-//# sourceMappingURL=drop-access-axes.js.map

package/dist/core/migrations/drop-access-axes.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"drop-access-axes.js","sourceRoot":"","sources":["../../../src/core/migrations/drop-access-axes.ts"],"names":[],"mappings":"AAAA,OAAO,IAAI,MAAM,WAAW,CAAC;AAC7B,OAAO,EAAE,UAAU,EAAE,MAAM,sBAAsB,CAAC;AAClD,OAAO,EAAE,iBAAiB,EAAE,MAAM,wBAAwB,CAAC;AAC3D,OAAO,EAAE,eAAe,EAAE,MAAM,iBAAiB,CAAC;AAGlD,MAAM,YAAY,GAAmB;IACnC,IAAI,EAAE,iBAAiB;IACvB,WAAW,EAAE,sFAAsF;CACpG,CAAC;AAEF,2GAA2G;AAC3G,MAAM,YAAY,GAAG,CAAC,YAAY,EAAE,YAAY,EAAE,QAAQ,CAAU,CAAC;AAErE;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,MAAM,CAAC,MAAM,uBAAuB,GAAc;IAChD,EAAE,EAAE,uBAAuB;IAC3B,WAAW,EAAE,CAAC;IACd,SAAS,EAAE,CAAC;IACZ,WAAW,EACT,kIAAkI;IAEpI,KAAK,CAAC,IAAI,CAAC,KAAK;QACd,IAAI,KAAK,CAAC,MAAM,CAAC,cAAc,IAAI,CAAC;YAAE,OAAO,EAAE,CAAC;QAChD,OAAO,CAAC,YAAY,CAAC,CAAC;IACxB,CAAC;IAED,KAAK,CAAC,KAAK,CAAC,KAAK;QACf,IAAI,KAAK,CAAC,MAAM,CAAC,cAAc,IAAI,CAAC;YAAE,OAAO,EAAE,CAAC;QAEhD,MAAM,UAAU,GAAG,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC,IAAI,EAAE,iBAAiB,CAAC,CAAC;QAC5D,MAAM,aAAa,GAAG,MAAM,UAAU,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;QACnD,MAAM,UAAU,GAA4B,EAAE,GAAG,aAAa,EAAE,cAAc,EAAE,CAAC,EAAE,CAAC;QACpF,KAAK,MAAM,GAAG,IAAI,YAAY;YAAE,OAAO,UAAU,CAAC,GAAG,CAAC,CAAC;QACvD,MAAM,eAAe,CAAC,UAAU,EAAE,iBAAiB,CAAC,UAAqD,CAAC,CAAC,CAAC;QAE5G,OAAO,CAAC,YAAY,CAAC,CAAC;IACxB,CAAC;CACF,CAAC"}

package/dist/core/migrations/drop-forge-and-workspaces-external.d.ts

@@ -1,19 +0,0 @@
-import type { Migration } from './types.js';
-/**
- * session-keeps-only-what-git-cannot-do (design D2): `ctxr session
- * submit`/`land`/`abandon`/`reap` and the `forge` adapter kind are removed;
- * `session.workspaces_external` goes with them, its skill-rendering half
- * never having worked as shipped. Both legacy shapes are ALREADY stripped
- * by the time `readConfig` returns — the adapters field's lenient schema
- * transform drops a `kind: forge` entry (session-keeps-only-what-git-cannot-do
- * D2), and `SessionSchema`'s default strip-unknown-keys behavior drops
- * `workspaces_external` — so this migration's only real work is bumping
- * `schema_version` and writing the already-clean config back to disk.
- *
- * Pending-ness is `schema_version < 5`, not key presence — the same rule
- * 0002 and 0004 established, for the same reason: an unmigrated store
- * already parses as though the legacy shape were gone, so its presence in
- * the parsed config can't distinguish migrated from not.
- */
-export declare const dropForgeAndWorkspacesExternalMigration: Migration;
-//# sourceMappingURL=drop-forge-and-workspaces-external.d.ts.map

package/dist/core/migrations/drop-forge-and-workspaces-external.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"drop-forge-and-workspaces-external.d.ts","sourceRoot":"","sources":["../../../src/core/migrations/drop-forge-and-workspaces-external.ts"],"names":[],"mappings":"AAIA,OAAO,KAAK,EAAE,SAAS,EAAkB,MAAM,YAAY,CAAC;AAO5D;;;;;;;;;;;;;;;GAeG;AACH,eAAO,MAAM,uCAAuC,EAAE,SA0BrD,CAAC"}

package/dist/core/migrations/drop-forge-and-workspaces-external.js

@@ -1,49 +0,0 @@
-import path from 'node:path';
-import { readConfig } from '../../config/load.js';
-import { renderStoreConfig } from '../../config/render.js';
-import { writeFileAtomic } from '../fs/atomic.js';
-const CONFIG_DELTA = {
-    path: 'contexture.yaml',
-    description: 'strip any legacy kind: forge adapter declarations and the session.workspaces_external key, and set schema_version to 5',
-};
-/**
- * session-keeps-only-what-git-cannot-do (design D2): `ctxr session
- * submit`/`land`/`abandon`/`reap` and the `forge` adapter kind are removed;
- * `session.workspaces_external` goes with them, its skill-rendering half
- * never having worked as shipped. Both legacy shapes are ALREADY stripped
- * by the time `readConfig` returns — the adapters field's lenient schema
- * transform drops a `kind: forge` entry (session-keeps-only-what-git-cannot-do
- * D2), and `SessionSchema`'s default strip-unknown-keys behavior drops
- * `workspaces_external` — so this migration's only real work is bumping
- * `schema_version` and writing the already-clean config back to disk.
- *
- * Pending-ness is `schema_version < 5`, not key presence — the same rule
- * 0002 and 0004 established, for the same reason: an unmigrated store
- * already parses as though the legacy shape were gone, so its presence in
- * the parsed config can't distinguish migrated from not.
- */
-export const dropForgeAndWorkspacesExternalMigration = {
-    id: '0005-drop-forge-and-workspaces-external',
-    fromVersion: 4,
-    toVersion: 5,
-    description: 'Strip any legacy kind: forge adapter declarations and the session.workspaces_external key from contexture.yaml, and bump schema_version to 5.',
-    async plan(store) {
-        if (store.config.schema_version >= 5)
-            return [];
-        return [CONFIG_DELTA];
-    },
-    async apply(store) {
-        if (store.config.schema_version >= 5)
-            return [];
-        const configPath = path.join(store.root, 'contexture.yaml');
-        // readConfig() already applies the lenient schema — a raw `kind: forge`
-        // entry and a raw `session.workspaces_external` key are both gone from
-        // this object before this line runs; writing it back is what removes
-        // them from disk.
-        const currentConfig = await readConfig(store.root);
-        const nextConfig = { ...currentConfig, schema_version: 5 };
-        await writeFileAtomic(configPath, renderStoreConfig(nextConfig));
-        return [CONFIG_DELTA];
-    },
-};
-//# sourceMappingURL=drop-forge-and-workspaces-external.js.map

package/dist/core/migrations/drop-forge-and-workspaces-external.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"drop-forge-and-workspaces-external.js","sourceRoot":"","sources":["../../../src/core/migrations/drop-forge-and-workspaces-external.ts"],"names":[],"mappings":"AAAA,OAAO,IAAI,MAAM,WAAW,CAAC;AAC7B,OAAO,EAAE,UAAU,EAAE,MAAM,sBAAsB,CAAC;AAClD,OAAO,EAAE,iBAAiB,EAAE,MAAM,wBAAwB,CAAC;AAC3D,OAAO,EAAE,eAAe,EAAE,MAAM,iBAAiB,CAAC;AAGlD,MAAM,YAAY,GAAmB;IACnC,IAAI,EAAE,iBAAiB;IACvB,WAAW,EAAE,wHAAwH;CACtI,CAAC;AAEF;;;;;;;;;;;;;;;GAeG;AACH,MAAM,CAAC,MAAM,uCAAuC,GAAc;IAChE,EAAE,EAAE,yCAAyC;IAC7C,WAAW,EAAE,CAAC;IACd,SAAS,EAAE,CAAC;IACZ,WAAW,EACT,+IAA+I;IAEjJ,KAAK,CAAC,IAAI,CAAC,KAAK;QACd,IAAI,KAAK,CAAC,MAAM,CAAC,cAAc,IAAI,CAAC;YAAE,OAAO,EAAE,CAAC;QAChD,OAAO,CAAC,YAAY,CAAC,CAAC;IACxB,CAAC;IAED,KAAK,CAAC,KAAK,CAAC,KAAK;QACf,IAAI,KAAK,CAAC,MAAM,CAAC,cAAc,IAAI,CAAC;YAAE,OAAO,EAAE,CAAC;QAEhD,MAAM,UAAU,GAAG,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC,IAAI,EAAE,iBAAiB,CAAC,CAAC;QAC5D,wEAAwE;QACxE,uEAAuE;QACvE,qEAAqE;QACrE,kBAAkB;QAClB,MAAM,aAAa,GAAG,MAAM,UAAU,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;QACnD,MAAM,UAAU,GAAG,EAAE,GAAG,aAAa,EAAE,cAAc,EAAE,CAAC,EAAE,CAAC;QAC3D,MAAM,eAAe,CAAC,UAAU,EAAE,iBAAiB,CAAC,UAAU,CAAC,CAAC,CAAC;QAEjE,OAAO,CAAC,YAAY,CAAC,CAAC;IACxB,CAAC;CACF,CAAC"}

package/dist/core/migrations/registry.d.ts

@@ -1,16 +0,0 @@
-import type { Migration } from './types.js';
-/**
- * Every migration contexture ships, in ascending fromVersion order. Later
- * phases append here, nothing else.
- *
- * The chain is deliberately NOT contiguous: the 1 -> 2 visibility-field
- * rename was retired with the field itself (retire-the-access-axes D7), so a
- * schema-1 store's first pending migration is the 2 -> 3 one, which guards on
- * `schema_version < 3` and carries it straight there. `pendingMigrations`
- * selects on `fromVersion >= current`, never on adjacency, so a gap costs
- * nothing.
- */
-export declare const MIGRATIONS: readonly Migration[];
-/** Every migration a store currently at `fromVersion` still needs to reach the CLI's supported version, in order. */
-export declare function pendingMigrations(fromVersion: number): Migration[];
-//# sourceMappingURL=registry.d.ts.map

package/dist/core/migrations/registry.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"registry.d.ts","sourceRoot":"","sources":["../../../src/core/migrations/registry.ts"],"names":[],"mappings":"AAMA,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,YAAY,CAAC;AAE5C;;;;;;;;;;GAUG;AACH,eAAO,MAAM,UAAU,EAAE,SAAS,SAAS,EAO1C,CAAC;AAEF,qHAAqH;AACrH,wBAAgB,iBAAiB,CAAC,WAAW,EAAE,MAAM,GAAG,SAAS,EAAE,CAElE"}

package/dist/core/migrations/registry.js

@@ -1,30 +0,0 @@
-import { addExplanationCraftSkillMigration } from './add-explanation-craft-skill.js';
-import { archiveDestinationFromTaxonomyMigration } from './archive-destination-from-taxonomy.js';
-import { dropAccessAxesMigration } from './drop-access-axes.js';
-import { dropForgeAndWorkspacesExternalMigration } from './drop-forge-and-workspaces-external.js';
-import { renameConventionsPathMigration } from './rename-conventions-path.js';
-import { renameProceduresPathMigration } from './rename-procedures-path.js';
-/**
- * Every migration contexture ships, in ascending fromVersion order. Later
- * phases append here, nothing else.
- *
- * The chain is deliberately NOT contiguous: the 1 -> 2 visibility-field
- * rename was retired with the field itself (retire-the-access-axes D7), so a
- * schema-1 store's first pending migration is the 2 -> 3 one, which guards on
- * `schema_version < 3` and carries it straight there. `pendingMigrations`
- * selects on `fromVersion >= current`, never on adjacency, so a gap costs
- * nothing.
- */
-export const MIGRATIONS = [
-    renameProceduresPathMigration,
-    renameConventionsPathMigration,
-    dropForgeAndWorkspacesExternalMigration,
-    archiveDestinationFromTaxonomyMigration,
-    addExplanationCraftSkillMigration,
-    dropAccessAxesMigration,
-];
-/** Every migration a store currently at `fromVersion` still needs to reach the CLI's supported version, in order. */
-export function pendingMigrations(fromVersion) {
-    return MIGRATIONS.filter((m) => m.fromVersion >= fromVersion).slice().sort((a, b) => a.fromVersion - b.fromVersion);
-}
-//# sourceMappingURL=registry.js.map

package/dist/core/migrations/registry.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"registry.js","sourceRoot":"","sources":["../../../src/core/migrations/registry.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,iCAAiC,EAAE,MAAM,kCAAkC,CAAC;AACrF,OAAO,EAAE,uCAAuC,EAAE,MAAM,wCAAwC,CAAC;AACjG,OAAO,EAAE,uBAAuB,EAAE,MAAM,uBAAuB,CAAC;AAChE,OAAO,EAAE,uCAAuC,EAAE,MAAM,yCAAyC,CAAC;AAClG,OAAO,EAAE,8BAA8B,EAAE,MAAM,8BAA8B,CAAC;AAC9E,OAAO,EAAE,6BAA6B,EAAE,MAAM,6BAA6B,CAAC;AAG5E;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,UAAU,GAAyB;IAC9C,6BAA6B;IAC7B,8BAA8B;IAC9B,uCAAuC;IACvC,uCAAuC;IACvC,iCAAiC;IACjC,uBAAuB;CACxB,CAAC;AAEF,qHAAqH;AACrH,MAAM,UAAU,iBAAiB,CAAC,WAAmB;IACnD,OAAO,UAAU,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,WAAW,IAAI,WAAW,CAAC,CAAC,KAAK,EAAE,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,WAAW,GAAG,CAAC,CAAC,WAAW,CAAC,CAAC;AACtH,CAAC"}

package/dist/core/migrations/rename-conventions-path.d.ts

@@ -1,26 +0,0 @@
-import type { Migration } from './types.js';
-/**
- * rename-conventions-path-to-guidance-path (compose-store-guidance-documents
- * design.md D1/D7): unlike 0003's pure key rename, the key's *default value*
- * also changes (`.contexture/conventions/` -> `.contexture/guidance/`), so a
- * store that never customized the path needs its directory moved on disk,
- * not merely its config key renamed. An operator-customized path is left
- * exactly where it is — only the key spelling changes for them.
- *
- * Migrations only see `Store` (`root` + `config`, no `GitRunner` — see
- * core/store.ts), so the directory move is a plain filesystem rename, not
- * `git mv`. History is still preserved: whatever commits this migration's
- * output (the normal session-submit flow) stages a coherent delete-old,
- * add-new diff, which `git log --follow`'s content-similarity rename
- * detection recognizes identically to an explicit `git mv` — git never
- * records "this was a rename" as a distinct fact in its object model
- * either way.
- *
- * Pending-ness is `store.config.schema_version < 4`, the same
- * schema-version-not-key-presence rule 0003 established, for the same
- * reason: `HarnessSchema`'s fallback transform already populates
- * `guidance_path` on an unmigrated store, so its presence can't distinguish
- * migrated from not.
- */
-export declare const renameConventionsPathMigration: Migration;
-//# sourceMappingURL=rename-conventions-path.d.ts.map

package/dist/core/migrations/rename-conventions-path.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"rename-conventions-path.d.ts","sourceRoot":"","sources":["../../../src/core/migrations/rename-conventions-path.ts"],"names":[],"mappings":"AAOA,OAAO,KAAK,EAAE,SAAS,EAAkB,MAAM,YAAY,CAAC;AAiB5D;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,eAAO,MAAM,8BAA8B,EAAE,SA+C5C,CAAC"}

package/dist/core/migrations/rename-conventions-path.js

@@ -1,86 +0,0 @@
-import { existsSync } from 'node:fs';
-import { rename } from 'node:fs/promises';
-import path from 'node:path';
-import { readConfig } from '../../config/load.js';
-import { renderStoreConfig } from '../../config/render.js';
-import { writeFileAtomic } from '../fs/atomic.js';
-const OLD_DEFAULT_GUIDANCE_PATH = '.contexture/conventions/';
-const NEW_DEFAULT_GUIDANCE_PATH = '.contexture/guidance/';
-const CONFIG_DELTA = {
-    path: 'contexture.yaml',
-    description: 'rename harness.conventions_path to harness.guidance_path and set schema_version to 4',
-};
-function directoryDelta() {
-    return {
-        path: NEW_DEFAULT_GUIDANCE_PATH,
-        description: `move the default-valued guidance directory from ${OLD_DEFAULT_GUIDANCE_PATH} to ${NEW_DEFAULT_GUIDANCE_PATH}`,
-    };
-}
-/**
- * rename-conventions-path-to-guidance-path (compose-store-guidance-documents
- * design.md D1/D7): unlike 0003's pure key rename, the key's *default value*
- * also changes (`.contexture/conventions/` -> `.contexture/guidance/`), so a
- * store that never customized the path needs its directory moved on disk,
- * not merely its config key renamed. An operator-customized path is left
- * exactly where it is — only the key spelling changes for them.
- *
- * Migrations only see `Store` (`root` + `config`, no `GitRunner` — see
- * core/store.ts), so the directory move is a plain filesystem rename, not
- * `git mv`. History is still preserved: whatever commits this migration's
- * output (the normal session-submit flow) stages a coherent delete-old,
- * add-new diff, which `git log --follow`'s content-similarity rename
- * detection recognizes identically to an explicit `git mv` — git never
- * records "this was a rename" as a distinct fact in its object model
- * either way.
- *
- * Pending-ness is `store.config.schema_version < 4`, the same
- * schema-version-not-key-presence rule 0003 established, for the same
- * reason: `HarnessSchema`'s fallback transform already populates
- * `guidance_path` on an unmigrated store, so its presence can't distinguish
- * migrated from not.
- */
-export const renameConventionsPathMigration = {
-    id: '0004-rename-conventions-path-to-guidance-path',
-    fromVersion: 3,
-    toVersion: 4,
-    description: 'Rename the harness.conventions_path config key to harness.guidance_path, move the guidance directory when it sat at the old default, and bump schema_version to 4.',
-    async plan(store) {
-        if (store.config.schema_version >= 4)
-            return [];
-        const deltas = [CONFIG_DELTA];
-        if (store.config.harness.guidance_path === OLD_DEFAULT_GUIDANCE_PATH)
-            deltas.push(directoryDelta());
-        return deltas;
-    },
-    async apply(store) {
-        if (store.config.schema_version >= 4)
-            return [];
-        const configPath = path.join(store.root, 'contexture.yaml');
-        // readConfig() already resolves harness.guidance_path via HarnessSchema's
-        // fallback (from conventions_path if that's all the file has), so
-        // currentConfig.harness carries no conventions_path key at all —
-        // rendering it below writes only guidance_path to disk.
-        const currentConfig = await readConfig(store.root);
-        const appliedDeltas = [CONFIG_DELTA];
-        let guidancePath = currentConfig.harness.guidance_path;
-        if (guidancePath === OLD_DEFAULT_GUIDANCE_PATH) {
-            const oldDir = path.join(store.root, OLD_DEFAULT_GUIDANCE_PATH);
-            const newDir = path.join(store.root, NEW_DEFAULT_GUIDANCE_PATH);
-            // Absent when the store never carried any convention files — nothing
-            // to move on disk, only the config value changes.
-            if (existsSync(oldDir)) {
-                await rename(oldDir, newDir);
-            }
-            guidancePath = NEW_DEFAULT_GUIDANCE_PATH;
-            appliedDeltas.push(directoryDelta());
-        }
-        const nextConfig = {
-            ...currentConfig,
-            schema_version: 4,
-            harness: { ...currentConfig.harness, guidance_path: guidancePath },
-        };
-        await writeFileAtomic(configPath, renderStoreConfig(nextConfig));
-        return appliedDeltas;
-    },
-};
-//# sourceMappingURL=rename-conventions-path.js.map

package/dist/core/migrations/rename-conventions-path.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"rename-conventions-path.js","sourceRoot":"","sources":["../../../src/core/migrations/rename-conventions-path.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAE,MAAM,SAAS,CAAC;AACrC,OAAO,EAAE,MAAM,EAAE,MAAM,kBAAkB,CAAC;AAC1C,OAAO,IAAI,MAAM,WAAW,CAAC;AAC7B,OAAO,EAAE,UAAU,EAAE,MAAM,sBAAsB,CAAC;AAClD,OAAO,EAAE,iBAAiB,EAAE,MAAM,wBAAwB,CAAC;AAC3D,OAAO,EAAE,eAAe,EAAE,MAAM,iBAAiB,CAAC;AAIlD,MAAM,yBAAyB,GAAG,0BAA0B,CAAC;AAC7D,MAAM,yBAAyB,GAAG,uBAAuB,CAAC;AAE1D,MAAM,YAAY,GAAmB;IACnC,IAAI,EAAE,iBAAiB;IACvB,WAAW,EAAE,sFAAsF;CACpG,CAAC;AAEF,SAAS,cAAc;IACrB,OAAO;QACL,IAAI,EAAE,yBAAyB;QAC/B,WAAW,EAAE,mDAAmD,yBAAyB,OAAO,yBAAyB,EAAE;KAC5H,CAAC;AACJ,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,MAAM,CAAC,MAAM,8BAA8B,GAAc;IACvD,EAAE,EAAE,+CAA+C;IACnD,WAAW,EAAE,CAAC;IACd,SAAS,EAAE,CAAC;IACZ,WAAW,EACT,oKAAoK;IAEtK,KAAK,CAAC,IAAI,CAAC,KAAK;QACd,IAAI,KAAK,CAAC,MAAM,CAAC,cAAc,IAAI,CAAC;YAAE,OAAO,EAAE,CAAC;QAChD,MAAM,MAAM,GAAqB,CAAC,YAAY,CAAC,CAAC;QAChD,IAAI,KAAK,CAAC,MAAM,CAAC,OAAO,CAAC,aAAa,KAAK,yBAAyB;YAAE,MAAM,CAAC,IAAI,CAAC,cAAc,EAAE,CAAC,CAAC;QACpG,OAAO,MAAM,CAAC;IAChB,CAAC;IAED,KAAK,CAAC,KAAK,CAAC,KAAK;QACf,IAAI,KAAK,CAAC,MAAM,CAAC,cAAc,IAAI,CAAC;YAAE,OAAO,EAAE,CAAC;QAEhD,MAAM,UAAU,GAAG,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC,IAAI,EAAE,iBAAiB,CAAC,CAAC;QAC5D,0EAA0E;QAC1E,kEAAkE;QAClE,iEAAiE;QACjE,wDAAwD;QACxD,MAAM,aAAa,GAAG,MAAM,UAAU,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;QACnD,MAAM,aAAa,GAAqB,CAAC,YAAY,CAAC,CAAC;QAEvD,IAAI,YAAY,GAAG,aAAa,CAAC,OAAO,CAAC,aAAa,CAAC;QACvD,IAAI,YAAY,KAAK,yBAAyB,EAAE,CAAC;YAC/C,MAAM,MAAM,GAAG,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC,IAAI,EAAE,yBAAyB,CAAC,CAAC;YAChE,MAAM,MAAM,GAAG,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC,IAAI,EAAE,yBAAyB,CAAC,CAAC;YAChE,qEAAqE;YACrE,kDAAkD;YAClD,IAAI,UAAU,CAAC,MAAM,CAAC,EAAE,CAAC;gBACvB,MAAM,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;YAC/B,CAAC;YACD,YAAY,GAAG,yBAAyB,CAAC;YACzC,aAAa,CAAC,IAAI,CAAC,cAAc,EAAE,CAAC,CAAC;QACvC,CAAC;QAED,MAAM,UAAU,GAAG;YACjB,GAAG,aAAa;YAChB,cAAc,EAAE,CAAC;YACjB,OAAO,EAAE,EAAE,GAAG,aAAa,CAAC,OAAO,EAAE,aAAa,EAAE,YAAY,EAAE;SACnE,CAAC;QACF,MAAM,eAAe,CAAC,UAAU,EAAE,iBAAiB,CAAC,UAAU,CAAC,CAAC,CAAC;QAEjE,OAAO,aAAa,CAAC;IACvB,CAAC;CACF,CAAC"}

package/dist/core/migrations/rename-procedures-path.d.ts

@@ -1,17 +0,0 @@
-import type { Migration } from './types.js';
-/**
- * rename-procedures-to-skills (design.md D2): a single-delta migration —
- * unlike the visibility-field rename, no note frontmatter is touched, since
- * only the config key's spelling changes, never any store file's location
- * (DEFAULT_SKILLS_PATH is already DEFAULT_PROCEDURES_PATH's old value).
- *
- * Pending-ness is `store.config.schema_version < 3`, NOT the presence or
- * absence of `store.config.harness.skills_path` — that field is populated
- * by HarnessSchema's fallback transform even on an unmigrated v2 store (so
- * every command keeps working before `ctxr migrate` runs), which means its
- * presence can never distinguish "already migrated" from "not yet
- * migrated." `schema_version` is the one signal the fallback doesn't mask,
- * and this migration is the only thing that ever sets it to 3.
- */
-export declare const renameProceduresPathMigration: Migration;
-//# sourceMappingURL=rename-procedures-path.d.ts.map

package/dist/core/migrations/rename-procedures-path.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"rename-procedures-path.d.ts","sourceRoot":"","sources":["../../../src/core/migrations/rename-procedures-path.ts"],"names":[],"mappings":"AAKA,OAAO,KAAK,EAAE,SAAS,EAAkB,MAAM,YAAY,CAAC;AAO5D;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,6BAA6B,EAAE,SAwB3C,CAAC"}

package/dist/core/migrations/rename-procedures-path.js

@@ -1,45 +0,0 @@
-import path from 'node:path';
-import { readConfig } from '../../config/load.js';
-import { renderStoreConfig } from '../../config/render.js';
-import { writeFileAtomic } from '../fs/atomic.js';
-const CONFIG_DELTA = {
-    path: 'contexture.yaml',
-    description: 'rename harness.procedures_path to harness.skills_path and set schema_version to 3',
-};
-/**
- * rename-procedures-to-skills (design.md D2): a single-delta migration —
- * unlike the visibility-field rename, no note frontmatter is touched, since
- * only the config key's spelling changes, never any store file's location
- * (DEFAULT_SKILLS_PATH is already DEFAULT_PROCEDURES_PATH's old value).
- *
- * Pending-ness is `store.config.schema_version < 3`, NOT the presence or
- * absence of `store.config.harness.skills_path` — that field is populated
- * by HarnessSchema's fallback transform even on an unmigrated v2 store (so
- * every command keeps working before `ctxr migrate` runs), which means its
- * presence can never distinguish "already migrated" from "not yet
- * migrated." `schema_version` is the one signal the fallback doesn't mask,
- * and this migration is the only thing that ever sets it to 3.
- */
-export const renameProceduresPathMigration = {
-    id: '0003-rename-procedures-path-to-skills-path',
-    fromVersion: 2,
-    toVersion: 3,
-    description: 'Rename the harness.procedures_path config key to harness.skills_path, and bump schema_version to 3.',
-    async plan(store) {
-        return store.config.schema_version < 3 ? [CONFIG_DELTA] : [];
-    },
-    async apply(store) {
-        if (store.config.schema_version >= 3)
-            return [];
-        const configPath = path.join(store.root, 'contexture.yaml');
-        // readConfig() already resolves harness.skills_path via HarnessSchema's
-        // fallback (from procedures_path if that's all the file has), so
-        // currentConfig.harness carries no procedures_path key at all —
-        // rendering it below writes only skills_path to disk.
-        const currentConfig = await readConfig(store.root);
-        const nextConfig = { ...currentConfig, schema_version: 3 };
-        await writeFileAtomic(configPath, renderStoreConfig(nextConfig));
-        return [CONFIG_DELTA];
-    },
-};
-//# sourceMappingURL=rename-procedures-path.js.map

package/dist/core/migrations/rename-procedures-path.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"rename-procedures-path.js","sourceRoot":"","sources":["../../../src/core/migrations/rename-procedures-path.ts"],"names":[],"mappings":"AAAA,OAAO,IAAI,MAAM,WAAW,CAAC;AAC7B,OAAO,EAAE,UAAU,EAAE,MAAM,sBAAsB,CAAC;AAClD,OAAO,EAAE,iBAAiB,EAAE,MAAM,wBAAwB,CAAC;AAC3D,OAAO,EAAE,eAAe,EAAE,MAAM,iBAAiB,CAAC;AAIlD,MAAM,YAAY,GAAmB;IACnC,IAAI,EAAE,iBAAiB;IACvB,WAAW,EAAE,mFAAmF;CACjG,CAAC;AAEF;;;;;;;;;;;;;GAaG;AACH,MAAM,CAAC,MAAM,6BAA6B,GAAc;IACtD,EAAE,EAAE,4CAA4C;IAChD,WAAW,EAAE,CAAC;IACd,SAAS,EAAE,CAAC;IACZ,WAAW,EAAE,qGAAqG;IAElH,KAAK,CAAC,IAAI,CAAC,KAAK;QACd,OAAO,KAAK,CAAC,MAAM,CAAC,cAAc,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,YAAY,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC;IAC/D,CAAC;IAED,KAAK,CAAC,KAAK,CAAC,KAAK;QACf,IAAI,KAAK,CAAC,MAAM,CAAC,cAAc,IAAI,CAAC;YAAE,OAAO,EAAE,CAAC;QAEhD,MAAM,UAAU,GAAG,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC,IAAI,EAAE,iBAAiB,CAAC,CAAC;QAC5D,wEAAwE;QACxE,iEAAiE;QACjE,gEAAgE;QAChE,sDAAsD;QACtD,MAAM,aAAa,GAAG,MAAM,UAAU,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;QACnD,MAAM,UAAU,GAAG,EAAE,GAAG,aAAa,EAAE,cAAc,EAAE,CAAC,EAAE,CAAC;QAC3D,MAAM,eAAe,CAAC,UAAU,EAAE,iBAAiB,CAAC,UAAU,CAAC,CAAC,CAAC;QAEjE,OAAO,CAAC,YAAY,CAAC,CAAC;IACxB,CAAC;CACF,CAAC"}

package/dist/core/migrations/types.d.ts

@@ -1,27 +0,0 @@
-import type { Store } from '../store.js';
-/** One concrete, reportable change a migration made (or would make). */
-export interface MigrationDelta {
-    /** The file touched, relative to the store root — 'contexture.yaml' for the config itself. */
-    path: string;
-    description: string;
-}
-/**
- * store-lifecycle spec: "named, dry-runnable, resumable." A migration's
- * `plan()` and `apply()` both re-derive what still needs doing from the
- * store's CURRENT on-disk state, never from separately-tracked progress —
- * so re-running `apply()` after an interruption naturally skips whatever
- * was already done (it no longer matches the "needs migrating" condition)
- * and finishes the rest, with no separate progress file to go stale or
- * corrupt.
- */
-export interface Migration {
-    id: string;
-    fromVersion: number;
-    toVersion: number;
-    description: string;
-    /** Computes exactly what apply() would change, without writing anything. */
-    plan(store: Store): Promise<MigrationDelta[]>;
-    /** Applies only what plan() would still report as pending; returns what it actually changed. */
-    apply(store: Store): Promise<MigrationDelta[]>;
-}
-//# sourceMappingURL=types.d.ts.map

package/dist/core/migrations/types.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"types.d.ts","sourceRoot":"","sources":["../../../src/core/migrations/types.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,KAAK,EAAE,MAAM,aAAa,CAAC;AAEzC,wEAAwE;AACxE,MAAM,WAAW,cAAc;IAC7B,8FAA8F;IAC9F,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,EAAE,MAAM,CAAC;CACrB;AAED;;;;;;;;GAQG;AACH,MAAM,WAAW,SAAS;IACxB,EAAE,EAAE,MAAM,CAAC;IACX,WAAW,EAAE,MAAM,CAAC;IACpB,SAAS,EAAE,MAAM,CAAC;IAClB,WAAW,EAAE,MAAM,CAAC;IACpB,4EAA4E;IAC5E,IAAI,CAAC,KAAK,EAAE,KAAK,GAAG,OAAO,CAAC,cAAc,EAAE,CAAC,CAAC;IAC9C,gGAAgG;IAChG,KAAK,CAAC,KAAK,EAAE,KAAK,GAAG,OAAO,CAAC,cAAc,EAAE,CAAC,CAAC;CAChD"}

package/dist/core/migrations/types.js

@@ -1,2 +0,0 @@
-export {};
-//# sourceMappingURL=types.js.map

package/dist/core/migrations/types.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"types.js","sourceRoot":"","sources":["../../../src/core/migrations/types.ts"],"names":[],"mappings":""}