@compilr-dev/sdk 0.29.5 → 0.29.7

package/dist/actions/index.d.ts

@@ -25,5 +25,4 @@
  * ```
  */
 export type { ActionContext, ActionDefinition } from './types.js';
-export { ACTION_REGISTRY, getActionsForContext, getActionById } from './registry.js';
-export { resolveActionPrompt, buildContextSummary, getSuggestedRole } from './resolver.js';
+export { resolveActionPrompt, buildContextSummary } from './resolver.js';

package/dist/actions/index.js

@@ -25,6 +25,14 @@
  * ```
  */
 // Registry
-export { ACTION_REGISTRY, getActionsForContext, getActionById } from './registry.js';
+/*
+  ⚠️ ACTION_REGISTRY IS GONE — superseded, not merely unused. `MACRO_META_REGISTRY` replaced it
+  during the macro rename and is a strict superset (55 entries against 14, every id present). The
+  old one kept an IPC handler and a preload binding alive that nothing called, which made it look
+  like the action source and cost a wrong assumption in the Projects plan.
+
+  `resolveActionPrompt` never read it: it resolves by skill NAME from the array it is given, so
+  the live path was never coupled to the dead one.
+*/
 // Resolver
-export { resolveActionPrompt, buildContextSummary, getSuggestedRole } from './resolver.js';
+export { resolveActionPrompt, buildContextSummary } from './resolver.js';

package/dist/actions/resolver.d.ts

@@ -23,7 +23,3 @@ export declare function resolveActionPrompt(actionId: string, context: ActionCon
  * Used by the ActionCard component to show a brief description.
  */
 export declare function buildContextSummary(context: ActionContext): string;
-/**
- * Get the suggested agent role for an action.
- */
-export declare function getSuggestedRole(actionId: string): string | undefined;

package/dist/actions/resolver.js

@@ -7,7 +7,6 @@
  *
  * Used by both CLI and desktop to turn user actions into agent prompts.
  */
-import { getActionById } from './registry.js';
 /**
  * Resolve an action + context into a final prompt for the agent.
  *
@@ -99,9 +98,3 @@ export function buildContextSummary(context) {
     }
     return '';
 }
-/**
- * Get the suggested agent role for an action.
- */
-export function getSuggestedRole(actionId) {
-    return getActionById(actionId)?.suggestedRole;
-}

package/dist/index.d.ts

@@ -87,7 +87,7 @@ export type { MacroListEntry, BuildMacroListOptions } from './skills/index.js';
 export { generateSkillCatalog, toCatalogEntry, createLoadSkillTool } from './skills/index.js';
 export type { SkillCatalogEntry, SkillSource } from './skills/index.js';
 export { platformMacros, designMacro, sketchMacro, prdMacro, refineMacro, refineItemMacro, architectureMacro, sessionNotesMacro, buildMacro, scaffoldMacro, outlineMacro, literatureReviewMacro, draftSectionMacro, peerReviewMacro, researchScaffoldMacro, businessVisionMacro, marketAnalysisMacro, competitorAnalysisMacro, financialModelMacro, pitchOutlineMacro, businessReviewMacro, brandSetupMacro, contentStrategyMacro, contentCalendarMacro, createContentMacro, contentReviewMacro, curriculumDesignMacro, lessonPlanMacro, assessmentDesignMacro, courseReviewMacro, bookOutlineMacro, characterDesignMacro, plotThreadsMacro, sceneBreakdownMacro, bookReviewMacro, } from './skills/index.js';
-export { ACTION_REGISTRY, getActionsForContext, getActionById, resolveActionPrompt, buildContextSummary, getSuggestedRole, } from './actions/index.js';
+export { resolveActionPrompt, buildContextSummary } from './actions/index.js';
 export type { ActionContext, ActionDefinition } from './actions/index.js';
 export { PROJECT_TYPES, getProjectTypeConfig, getEnrichedProjectTypeConfig, getProjectTypesByCategory, generalConfig, softwareConfig, researchConfig, businessPlanConfig, contentConfig, techDocsConfig, courseConfig, MACRO_META_REGISTRY, resolveActionMeta, getRelevantMacros, getMacroMeta, getAllMacroMeta, } from './project-types/index.js';
 export type { ActionMeta, MacroMeta, MacroCategory, MacroCapabilities, } from './project-types/index.js';

package/dist/index.js

@@ -166,7 +166,7 @@ export { platformMacros, designMacro, sketchMacro, prdMacro, refineMacro, refine
 // =============================================================================
 // Contextual Actions (skill invocations with context)
 // =============================================================================
-export { ACTION_REGISTRY, getActionsForContext, getActionById, resolveActionPrompt, buildContextSummary, getSuggestedRole, } from './actions/index.js';
+export { resolveActionPrompt, buildContextSummary } from './actions/index.js';
 // =============================================================================
 // Project Types
 // =============================================================================

package/dist/platform/file-anchor-service.d.ts

@@ -10,7 +10,7 @@
  *     └── project-{id}.json     # Per-project anchors
  */
 import { AnchorManager } from '@compilr-dev/agents';
-import type { Anchor, AnchorInput, AnchorQueryOptions } from '@compilr-dev/agents';
+import type { Anchor, AnchorInput, AnchorPriority, AnchorQueryOptions } from '@compilr-dev/agents';
 import type { IAnchorService } from './services.js';
 export interface ProjectAnchorStoreConfig {
     /** Directory for anchor JSON files (e.g. ~/.compilr-dev/anchors/) */
@@ -36,6 +36,55 @@ export declare class ProjectAnchorStore {
     addAnchor(input: AnchorInput & {
         projectId?: string;
     }): Anchor;
+    /**
+     * Find an anchor by id, and say which file holds it.
+     *
+     * Searches the active project's manager then the global one — the same two the UI lists, and
+     * the same order `toService().remove` already uses. It deliberately does not sweep
+     * `this.managers`: those are lazily cached, so which ones exist depends on what happened
+     * earlier in the session, and the answer would drift with it.
+     *
+     * The null check on `currentProjectId` is defensive rather than behavioural — `String(null)`
+     * would key an empty manager and the lookup would fall through to global with the same
+     * result, and `loadPersistent` writes nothing for a file that does not exist. It is here so
+     * the intent is legible, not because a test can tell the difference. Mutating it away leaves
+     * every test green, and that is correct.
+     */
+    findAnchor(id: string, currentProjectId?: string | null): {
+        anchor: Anchor;
+        projectKey: string | null;
+    } | undefined;
+    /** Remove an anchor by id from whichever file holds it. */
+    removeAnchorById(id: string, currentProjectId?: string | null): {
+        removed: boolean;
+        scope?: 'global' | 'project';
+    };
+    /**
+     * Edit an anchor in place, keeping its id.
+     *
+     * ⚠️ WHY THE ID MATTERS. Without this the caller has to remove and re-add, which mints a new
+     * id — an open tab would then point at an anchor that no longer exists, and the row would
+     * jump in the list. `AnchorInput` accepts an id, so the re-add reuses the old one and both
+     * stay put.
+     *
+     * ⚠️ CHANGING SCOPE IS A MOVE BETWEEN FILES, not a field edit. Global anchors live in
+     * `global.json` and project ones in `project-<id>.json`, so switching "applies to" removes
+     * from one manager and adds to the other. The id survives that too.
+     *
+     * ⚠️ `createdAt` IS RESET, deliberately. `AnchorManager.add` always stamps `new Date()` and
+     * its `savePersistent` is private, so the only ways to keep the original are to mutate a
+     * stored object behind the manager's back or to widen `AnchorInput` in @compilr-dev/agents.
+     * Nothing displays `createdAt`; it is read only by the two eviction tie-breakers
+     * (`makeRoom`, `removeOldestLowPriority`), so on an edited anchor it now means "last edited"
+     * and that anchor is evicted last under budget pressure. Built-ins keep `new Date(0)` because
+     * they cannot be edited at all. See F-4.
+     */
+    updateAnchor(id: string, patch: {
+        content?: string;
+        priority?: AnchorPriority;
+        tags?: string[];
+        scope?: 'global' | 'project';
+    }, currentProjectId?: string | null): Anchor | undefined;
     /** Get all anchors across all cached managers. */
     getAllAnchors(options?: AnchorQueryOptions): Anchor[];
     /** Clear all anchors for a project and delete the persistence file. */
@@ -53,6 +102,29 @@ export declare class ProjectAnchorStore {
         projectCounts: Map<string, number>;
         totalTokens: number;
     };
+    /**
+     * Usage against the caps, per file.
+     *
+     * ⚠️ THE CAPS ARE PER FILE, NOT COMBINED. Each `AnchorManager` enforces `maxAnchors` and
+     * `maxTokens` on its own store, so global.json and project-<id>.json each get the full
+     * budget. A single meter summing the two and measuring it against one cap would read half
+     * full at the moment an `anchor_add` starts evicting — which is the opposite of the point,
+     * since the meter exists to show the limit before it bites.
+     *
+     * Both are returned and the caller shows the fuller one.
+     */
+    getUsage(projectId?: string | null): {
+        global: {
+            anchors: number;
+            tokens: number;
+        };
+        project: {
+            anchors: number;
+            tokens: number;
+        } | null;
+        maxAnchors: number;
+        maxTokens: number;
+    };
     /** Clear all cached managers (useful for testing or refresh). */
     clearCache(): void;
     /** Create an IAnchorService implementation for use with createPlatformTools(). */

package/dist/platform/file-anchor-service.js

@@ -52,6 +52,89 @@ export class ProjectAnchorStore {
         const manager = this.getManager(input.projectId ?? null);
         return manager.add(input);
     }
+    /**
+     * Find an anchor by id, and say which file holds it.
+     *
+     * Searches the active project's manager then the global one — the same two the UI lists, and
+     * the same order `toService().remove` already uses. It deliberately does not sweep
+     * `this.managers`: those are lazily cached, so which ones exist depends on what happened
+     * earlier in the session, and the answer would drift with it.
+     *
+     * The null check on `currentProjectId` is defensive rather than behavioural — `String(null)`
+     * would key an empty manager and the lookup would fall through to global with the same
+     * result, and `loadPersistent` writes nothing for a file that does not exist. It is here so
+     * the intent is legible, not because a test can tell the difference. Mutating it away leaves
+     * every test green, and that is correct.
+     */
+    findAnchor(id, currentProjectId) {
+        if (currentProjectId != null && currentProjectId !== '') {
+            const projectManager = this.getManager(currentProjectId);
+            const anchor = projectManager.get(id);
+            if (anchor)
+                return { anchor, projectKey: currentProjectId };
+        }
+        const anchor = this.getGlobalManager().get(id);
+        return anchor ? { anchor, projectKey: null } : undefined;
+    }
+    /** Remove an anchor by id from whichever file holds it. */
+    removeAnchorById(id, currentProjectId) {
+        const found = this.findAnchor(id, currentProjectId);
+        if (!found)
+            return { removed: false };
+        const removed = this.getManager(found.projectKey).remove(id);
+        return { removed, scope: found.projectKey === null ? 'global' : 'project' };
+    }
+    /**
+     * Edit an anchor in place, keeping its id.
+     *
+     * ⚠️ WHY THE ID MATTERS. Without this the caller has to remove and re-add, which mints a new
+     * id — an open tab would then point at an anchor that no longer exists, and the row would
+     * jump in the list. `AnchorInput` accepts an id, so the re-add reuses the old one and both
+     * stay put.
+     *
+     * ⚠️ CHANGING SCOPE IS A MOVE BETWEEN FILES, not a field edit. Global anchors live in
+     * `global.json` and project ones in `project-<id>.json`, so switching "applies to" removes
+     * from one manager and adds to the other. The id survives that too.
+     *
+     * ⚠️ `createdAt` IS RESET, deliberately. `AnchorManager.add` always stamps `new Date()` and
+     * its `savePersistent` is private, so the only ways to keep the original are to mutate a
+     * stored object behind the manager's back or to widen `AnchorInput` in @compilr-dev/agents.
+     * Nothing displays `createdAt`; it is read only by the two eviction tie-breakers
+     * (`makeRoom`, `removeOldestLowPriority`), so on an edited anchor it now means "last edited"
+     * and that anchor is evicted last under budget pressure. Built-ins keep `new Date(0)` because
+     * they cannot be edited at all. See F-4.
+     */
+    updateAnchor(id, patch, currentProjectId) {
+        const found = this.findAnchor(id, currentProjectId);
+        if (!found)
+            return undefined;
+        const { anchor, projectKey } = found;
+        let targetKey = projectKey;
+        if (patch.scope !== undefined) {
+            if (patch.scope === 'project') {
+                if (currentProjectId == null || currentProjectId === '') {
+                    throw new Error('Cannot scope an anchor to a project: no active project. Use scope: "global" instead.');
+                }
+                targetKey = currentProjectId;
+            }
+            else {
+                targetKey = null;
+            }
+        }
+        // Remove first: re-adding the same id into the same manager would otherwise be an
+        // overwrite whose budget accounting counts the content twice.
+        this.getManager(projectKey).remove(id);
+        return this.getManager(targetKey).add({
+            id,
+            content: patch.content ?? anchor.content,
+            priority: patch.priority ?? anchor.priority,
+            scope: anchor.scope,
+            tags: patch.tags ?? anchor.tags,
+            metadata: anchor.metadata,
+            expiresAt: anchor.expiresAt,
+            projectId: targetKey ?? undefined,
+        });
+    }
     /** Get all anchors across all cached managers. */
     getAllAnchors(options) {
         const all = [];
@@ -127,6 +210,30 @@ export class ProjectAnchorStore {
             totalTokens,
         };
     }
+    /**
+     * Usage against the caps, per file.
+     *
+     * ⚠️ THE CAPS ARE PER FILE, NOT COMBINED. Each `AnchorManager` enforces `maxAnchors` and
+     * `maxTokens` on its own store, so global.json and project-<id>.json each get the full
+     * budget. A single meter summing the two and measuring it against one cap would read half
+     * full at the moment an `anchor_add` starts evicting — which is the opposite of the point,
+     * since the meter exists to show the limit before it bites.
+     *
+     * Both are returned and the caller shows the fuller one.
+     */
+    getUsage(projectId) {
+        const globalManager = this.getGlobalManager();
+        const hasProject = projectId != null && projectId !== '';
+        const projectManager = hasProject ? this.getManager(projectId) : null;
+        return {
+            global: { anchors: globalManager.size, tokens: globalManager.getTotalTokens() },
+            project: projectManager === null
+                ? null
+                : { anchors: projectManager.size, tokens: projectManager.getTotalTokens() },
+            maxAnchors: this.config.maxAnchors ?? 50,
+            maxTokens: this.config.maxTokens ?? 4000,
+        };
+    }
     /** Clear all cached managers (useful for testing or refresh). */
     clearCache() {
         this.managers.clear();
@@ -164,6 +271,32 @@ export class ProjectAnchorStore {
                     tags: anchor.tags,
                 });
             },
+            update: (id, patch) => {
+                const projId = this.config.getCurrentProjectId();
+                const updated = this.updateAnchor(id, patch, projId == null ? null : String(projId));
+                if (!updated)
+                    return Promise.resolve(null);
+                return Promise.resolve({
+                    id: updated.id,
+                    content: updated.content,
+                    priority: updated.priority,
+                    scope: updated.projectId === undefined ? 'global' : 'project',
+                    tags: updated.tags,
+                });
+            },
+            get: (id) => {
+                const projId = this.config.getCurrentProjectId();
+                const found = this.findAnchor(id, projId == null ? null : String(projId));
+                if (!found)
+                    return Promise.resolve(null);
+                return Promise.resolve({
+                    id: found.anchor.id,
+                    content: found.anchor.content,
+                    priority: found.anchor.priority,
+                    scope: found.projectKey === null ? 'global' : 'project',
+                    tags: found.anchor.tags,
+                });
+            },
             remove: (id) => {
                 let removed = false;
                 let scope;

package/dist/platform/services.d.ts

@@ -23,6 +23,21 @@ export interface IAnchorService {
         removed: boolean;
         scope?: string;
     }>;
+    /**
+     * Edit an anchor in place, keeping its id.
+     *
+     * Optional so existing hosts are unaffected. Without it a caller has to remove and re-add,
+     * which mints a new id — anything holding the old one (an open tab, a row in a list) is then
+     * pointing at an anchor that no longer exists.
+     */
+    update?(id: string, patch: {
+        content?: string;
+        priority?: AnchorPriority;
+        tags?: string[];
+        scope?: 'global' | 'project';
+    }): Promise<AnchorData | null>;
+    /** One anchor by id, or null. */
+    get?(id: string): Promise<AnchorData | null>;
     list(options?: {
         scope?: 'global' | 'project' | 'all';
         priority?: AnchorPriority;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@compilr-dev/sdk",
-  "version": "0.29.5",
+  "version": "0.29.7",
   "description": "Universal agent runtime for building AI-powered applications",
   "type": "module",
   "main": "dist/index.js",

package/dist/actions/registry.d.ts

@@ -1,17 +0,0 @@
-/**
- * Action Registry — Defines which actions are available and where.
- *
- * Each action maps to a skill (from platformMacros/builtinSkills)
- * but adds UI metadata: icon, label, category, applicable contexts,
- * and suggested agent role.
- */
-import type { ActionDefinition } from './types.js';
-export declare const ACTION_REGISTRY: ActionDefinition[];
-/**
- * Get actions applicable to a given context type.
- */
-export declare function getActionsForContext(contextType: 'project' | 'workitem' | 'document'): ActionDefinition[];
-/**
- * Get an action definition by ID.
- */
-export declare function getActionById(id: string): ActionDefinition | undefined;

package/dist/actions/registry.js

@@ -1,161 +0,0 @@
-/**
- * Action Registry — Defines which actions are available and where.
- *
- * Each action maps to a skill (from platformMacros/builtinSkills)
- * but adds UI metadata: icon, label, category, applicable contexts,
- * and suggested agent role.
- */
-export const ACTION_REGISTRY = [
-    // ─── Project-level actions ─────────────────────────────────────────────
-    {
-        id: 'design',
-        label: 'Design App',
-        description: 'Describe an idea, get a full application design',
-        icon: 'Wand2',
-        applicableTo: ['project'],
-        category: 'design',
-        // BA owns requirements: the 'ba' role (analyst profile) has both
-        // backlog_write and documents, so it can complete the full /design action
-        // (create work items + write the PRD). The architect profile lacks
-        // backlog_write and cannot create the backlog.
-        suggestedRole: 'ba',
-        needsInput: true,
-        inputPrompt: 'What would you like to design?',
-    },
-    {
-        id: 'sketch',
-        label: 'Quick Sketch',
-        description: 'Quickly sketch out an idea or concept',
-        icon: 'Pencil',
-        applicableTo: ['project'],
-        category: 'design',
-        needsInput: true,
-        inputPrompt: 'What would you like to sketch?',
-    },
-    {
-        id: 'prd',
-        label: 'Write PRD',
-        description: 'Create a product requirements document',
-        icon: 'FileText',
-        applicableTo: ['project'],
-        // PRD is artifact-authoring (requirements), grouped with design/architecture
-        // rather than backlog-breakdown 'planning' (refine/refine-item).
-        category: 'design',
-        // Requirements work → Business Analyst, not PM. The 'ba' role (analyst
-        // profile) is purpose-built for requirements gathering and has the
-        // documents tools needed to author the PRD.
-        suggestedRole: 'ba',
-    },
-    {
-        id: 'architecture',
-        label: 'Architecture',
-        description: 'Design the system architecture',
-        icon: 'Network',
-        applicableTo: ['project'],
-        category: 'design',
-        suggestedRole: 'architect',
-    },
-    {
-        id: 'scaffold',
-        label: 'Scaffold',
-        description: 'Generate project code from the app model',
-        icon: 'Layers',
-        applicableTo: ['project'],
-        category: 'development',
-        suggestedRole: 'developer',
-    },
-    {
-        id: 'session-notes',
-        label: 'Session Notes',
-        description: 'Summarize what was accomplished in this session',
-        icon: 'StickyNote',
-        applicableTo: ['project'],
-        category: 'documentation',
-    },
-    // ─── Work item actions ─────────────────────────────────────────────────
-    {
-        id: 'refine',
-        label: 'Refine',
-        description: 'Break down into smaller tasks',
-        icon: 'RefreshCw',
-        applicableTo: ['project', 'workitem'],
-        category: 'planning',
-        suggestedRole: 'pm',
-    },
-    {
-        id: 'refine-item',
-        label: 'Refine Item',
-        description: 'Add detail and acceptance criteria to this item',
-        icon: 'RefreshCw',
-        applicableTo: ['workitem'],
-        category: 'planning',
-        suggestedRole: 'pm',
-    },
-    {
-        id: 'build',
-        label: 'Build',
-        description: 'Implement this work item',
-        icon: 'Hammer',
-        applicableTo: ['workitem'],
-        category: 'development',
-        suggestedRole: 'developer',
-    },
-    {
-        id: 'code-review',
-        label: 'Code Review',
-        description: 'Review code for quality and correctness',
-        icon: 'Search',
-        applicableTo: ['project', 'workitem'],
-        category: 'development',
-        suggestedRole: 'qa',
-    },
-    {
-        id: 'debug',
-        label: 'Debug',
-        description: 'Debug an issue or error',
-        icon: 'Bug',
-        applicableTo: ['project', 'workitem'],
-        category: 'development',
-        suggestedRole: 'developer',
-    },
-    // ─── Document actions ──────────────────────────────────────────────────
-    {
-        id: 'explain',
-        label: 'Explain',
-        description: 'Explain this code or document',
-        icon: 'BookOpen',
-        applicableTo: ['document', 'workitem'],
-        category: 'documentation',
-    },
-    // ─── Analysis actions ──────────────────────────────────────────────────
-    {
-        id: 'security-review',
-        label: 'Security Review',
-        description: 'Review for security vulnerabilities',
-        icon: 'Shield',
-        applicableTo: ['project'],
-        category: 'analysis',
-        suggestedRole: 'security',
-    },
-    {
-        id: 'refactor',
-        label: 'Refactor',
-        description: 'Improve code quality without changing behavior',
-        icon: 'Scissors',
-        applicableTo: ['project', 'workitem'],
-        category: 'development',
-        suggestedRole: 'developer',
-    },
-];
-/**
- * Get actions applicable to a given context type.
- */
-export function getActionsForContext(contextType) {
-    return ACTION_REGISTRY.filter((a) => a.applicableTo.includes(contextType));
-}
-/**
- * Get an action definition by ID.
- */
-export function getActionById(id) {
-    return ACTION_REGISTRY.find((a) => a.id === id);
-}