ai-devkit 0.15.0 → 0.16.0

package/templates/commands/new-requirement.md

@@ -5,14 +5,15 @@ description: Scaffold feature documentation from requirements through planning.
 Guide me through adding a new feature, from requirements documentation to implementation readiness.
 
 1. **Capture Requirement** — If not already provided, ask for: feature name (kebab-case, e.g., `user-authentication`), what problem it solves and who will use it, and key user stories.
-2. **Create Feature Documentation Structure** — Copy each template's content (preserving YAML frontmatter and section headings) into feature-specific files:
+2. **Use Memory for Context** — Before asking repetitive clarification questions, search memory for related decisions or conventions via `npx ai-devkit@latest memory search --query "<feature/topic>"` and reuse relevant context.
+3. **Create Feature Documentation Structure** — Copy each template's content (preserving YAML frontmatter and section headings) into feature-specific files:
    - `docs/ai/requirements/README.md` → `docs/ai/requirements/feature-{name}.md`
    - `docs/ai/design/README.md` → `docs/ai/design/feature-{name}.md`
    - `docs/ai/planning/README.md` → `docs/ai/planning/feature-{name}.md`
    - `docs/ai/implementation/README.md` → `docs/ai/implementation/feature-{name}.md`
    - `docs/ai/testing/README.md` → `docs/ai/testing/feature-{name}.md`
-3. **Requirements Phase** — Fill out `docs/ai/requirements/feature-{name}.md`: problem statement, goals/non-goals, user stories, success criteria, constraints, open questions.
-4. **Design Phase** — Fill out `docs/ai/design/feature-{name}.md`: architecture changes, data models, API/interfaces, components, design decisions, security and performance considerations.
-5. **Planning Phase** — Fill out `docs/ai/planning/feature-{name}.md`: task breakdown with subtasks, dependencies, effort estimates, implementation order, risks.
-6. **Documentation Review** — Run `/review-requirements` and `/review-design` to validate the drafted docs.
-7. **Next Steps** — This command focuses on documentation. When ready to implement, use `/execute-plan`. Generate a PR description covering: summary, requirements doc link, key changes, test status, and a readiness checklist.
+4. **Requirements Phase** — Fill out `docs/ai/requirements/feature-{name}.md`: problem statement, goals/non-goals, user stories, success criteria, constraints, open questions.
+5. **Design Phase** — Fill out `docs/ai/design/feature-{name}.md`: architecture changes, data models, API/interfaces, components, design decisions, security and performance considerations.
+6. **Planning Phase** — Fill out `docs/ai/planning/feature-{name}.md`: task breakdown with subtasks, dependencies, effort estimates, implementation order, risks.
+7. **Store Reusable Knowledge** — When important conventions or decisions are finalized, store them via `npx ai-devkit@latest memory store --title "<title>" --content "<knowledge>" --tags "<tags>"`.
+8. **Next Command Guidance** — Run `/review-requirements` first, then `/review-design`. If both pass, continue with `/execute-plan`.

package/templates/commands/remember.md

@@ -2,9 +2,11 @@
 description: Store reusable guidance in the knowledge memory service.
 ---
 
-When I say "remember this" or want to save a reusable rule, help me store it in the knowledge memory service.
+Help me store it in the knowledge memory service.
 
 1. **Capture Knowledge** — If not already provided, ask for: a short explicit title (5-12 words), detailed content (markdown, examples encouraged), optional tags (keywords like "api", "testing"), and optional scope (`global`, `project:<name>`, `repo:<name>`). If vague, ask follow-ups to make it specific and actionable.
-2. **Validate Quality** — Ensure it is specific and reusable (not generic advice). Avoid storing secrets or sensitive data.
-3. **Store** — Call `memory.storeKnowledge` with title, content, tags, scope. If MCP tools are unavailable, use `npx ai-devkit@latest memory store` instead.
-4. **Confirm** — Summarize what was saved and offer to store more knowledge if needed.
+2. **Search Before Store** — Check for existing similar entries first with `npx ai-devkit@latest memory search --query "<topic>"` to avoid duplicates.
+3. **Validate Quality** — Ensure it is specific and reusable (not generic advice). Avoid storing secrets or sensitive data.
+4. **Store** — Call `memory.storeKnowledge` with title, content, tags, scope. If MCP tools are unavailable, use `npx ai-devkit@latest memory store` instead.
+5. **Confirm** — Summarize what was saved and offer to retrieve related memory entries when helpful.
+6. **Next Command Guidance** — Continue with the current lifecycle phase command (`/execute-plan`, `/check-implementation`, `/writing-test`, etc.) as needed.

package/templates/commands/review-design.md

@@ -2,14 +2,17 @@
 description: Review feature design for completeness.
 ---
 
-Review the design documentation in docs/ai/design/feature-{name}.md (and the project-level README if relevant). Summarize:
+Review the design documentation in `docs/ai/design/feature-{name}.md` (and the project-level README if relevant).
 
-- Architecture overview (ensure mermaid diagram is present and accurate)
-- Key components and their responsibilities
-- Technology choices and rationale
-- Data models and relationships
-- API/interface contracts (inputs, outputs, auth)
-- Major design decisions and trade-offs
-- Non-functional requirements that must be preserved
-
-Highlight any inconsistencies, missing sections, or diagrams that need updates.
+1. **Use Memory for Context** — Search memory for prior architecture constraints/patterns: `npx ai-devkit@latest memory search --query "<feature design architecture>"`.
+2. Summarize:
+   - Architecture overview (ensure mermaid diagram is present and accurate)
+   - Key components and their responsibilities
+   - Technology choices and rationale
+   - Data models and relationships
+   - API/interface contracts (inputs, outputs, auth)
+   - Major design decisions and trade-offs
+   - Non-functional requirements that must be preserved
+3. Highlight inconsistencies, missing sections, or diagrams that need updates.
+4. **Store Reusable Knowledge** — Persist approved design patterns/constraints with `npx ai-devkit@latest memory store ...` when they will help future work.
+5. **Next Command Guidance** — If requirements gaps are found, return to `/review-requirements`; if design is sound, continue to `/execute-plan`.

package/templates/commands/review-requirements.md

@@ -2,12 +2,15 @@
 description: Review feature requirements for completeness.
 ---
 
-Review `docs/ai/requirements/feature-{name}.md` and the project-level template `docs/ai/requirements/README.md` to ensure structure and content alignment. Summarize:
+Review `docs/ai/requirements/feature-{name}.md` and the project-level template `docs/ai/requirements/README.md` to ensure structure and content alignment.
 
-- Core problem statement and affected users
-- Goals, non-goals, and success criteria
-- Primary user stories & critical flows
-- Constraints, assumptions, open questions
-- Any missing sections or deviations from the template
-
-Identify gaps or contradictions and suggest clarifications.
+1. **Use Memory for Context** — Search memory for related requirements/domain decisions before starting: `npx ai-devkit@latest memory search --query "<feature requirements>"`.
+2. Summarize:
+   - Core problem statement and affected users
+   - Goals, non-goals, and success criteria
+   - Primary user stories & critical flows
+   - Constraints, assumptions, open questions
+   - Any missing sections or deviations from the template
+3. Identify gaps or contradictions and suggest clarifications.
+4. **Store Reusable Knowledge** — If new reusable requirement conventions are agreed, store them with `npx ai-devkit@latest memory store ...`.
+5. **Next Command Guidance** — If fundamentals are missing, go back to `/new-requirement`; otherwise continue to `/review-design`.

package/templates/commands/simplify-implementation.md

@@ -5,6 +5,9 @@ description: Simplify existing code to reduce complexity.
 Help me simplify an existing implementation while maintaining or improving its functionality.
 
 1. **Gather Context** — If not already provided, ask for: target file(s) or component(s) to simplify, current pain points (hard to understand, maintain, or extend?), performance or scalability concerns, constraints (backward compatibility, API stability, deadlines), and relevant design docs or requirements.
-2. **Analyze Current Complexity** — For each target: identify complexity sources (deep nesting, duplication, unclear abstractions, tight coupling, over-engineering, magic values), assess cognitive load for future maintainers, and identify scalability blockers (single points of failure, sync-where-async-needed, missing caching, inefficient algorithms).
-3. **Propose Simplifications** — Prioritize readability over brevity — apply the 30-second test: can a new team member understand each change quickly? For each issue, suggest concrete improvements (extract, consolidate, flatten, decouple, remove dead code, replace with built-ins). Provide before/after snippets.
-4. **Prioritize & Plan** — Rank by impact vs risk: (1) high impact, low risk — do first, (2) high impact, higher risk — plan carefully, (3) low impact, low risk — quick wins if time permits, (4) low impact, high risk — skip or defer. For each change specify risk level, testing requirements, and effort. Produce a prioritized action plan with recommended execution order.
+2. **Use Memory for Context** — Search memory for established patterns and prior refactors in this area: `npx ai-devkit@latest memory search --query "<component simplification pattern>"`.
+3. **Analyze Current Complexity** — For each target: identify complexity sources (deep nesting, duplication, unclear abstractions, tight coupling, over-engineering, magic values), assess cognitive load for future maintainers, and identify scalability blockers (single points of failure, sync-where-async-needed, missing caching, inefficient algorithms).
+4. **Propose Simplifications** — Prioritize readability over brevity; apply the 30-second test: can a new team member understand each change quickly? For each issue, suggest concrete improvements (extract, consolidate, flatten, decouple, remove dead code, replace with built-ins). Provide before/after snippets.
+5. **Prioritize & Plan** — Rank by impact vs risk: (1) high impact, low risk — do first, (2) high impact, higher risk — plan carefully, (3) low impact, low risk — quick wins if time permits, (4) low impact, high risk — skip or defer. For each change specify risk level, testing requirements, and effort. Produce a prioritized action plan with recommended execution order.
+6. **Store Reusable Knowledge** — Save reusable simplification patterns and trade-offs via `npx ai-devkit@latest memory store ...`.
+7. **Next Command Guidance** — After implementation, run `/check-implementation` and `/writing-test`.

package/templates/commands/update-planning.md

@@ -5,6 +5,9 @@ description: Update planning docs to reflect implementation progress.
 Help me reconcile current implementation progress with the planning documentation.
 
 1. **Gather Context** — If not already provided, ask for: feature/branch name and brief status, tasks completed since last update, new tasks discovered, current blockers or risks, and planning doc path (default `docs/ai/planning/feature-{name}.md`).
-2. **Review & Reconcile** — Summarize existing milestones, task breakdowns, and dependencies from the planning doc. For each planned task: mark status (done / in progress / blocked / not started), note scope changes, record blockers, identify skipped or added tasks.
-3. **Produce Updated Task List** — Generate an updated checklist grouped by: Done, In Progress, Blocked, Newly Discovered Work — with short notes per task.
-4. **Next Steps & Summary** — Suggest the next 2-3 actionable tasks and highlight risky areas. Prepare a summary paragraph for the planning doc covering: current state, major risks/blockers, upcoming focus, and any scope/timeline changes.
+2. **Use Memory for Context** — Search memory for prior decisions that affect priorities/scope: `npx ai-devkit@latest memory search --query "<feature planning updates>"`.
+3. **Review & Reconcile** — Summarize existing milestones, task breakdowns, and dependencies from the planning doc. For each planned task: mark status (done / in progress / blocked / not started), note scope changes, record blockers, identify skipped or added tasks.
+4. **Produce Updated Task List** — Generate an updated checklist grouped by: Done, In Progress, Blocked, Newly Discovered Work — with short notes per task.
+5. **Store Reusable Knowledge** — If new planning conventions or risk-handling rules emerge, store them with `npx ai-devkit@latest memory store ...`.
+6. **Next Steps & Summary** — Suggest the next 2-3 actionable tasks and prepare a summary paragraph for the planning doc.
+7. **Next Command Guidance** — Return to `/execute-plan` for remaining work. When all implementation tasks are complete, run `/check-implementation`.

package/templates/commands/writing-test.md

@@ -5,8 +5,11 @@ description: Add tests for a new feature.
 Review `docs/ai/testing/feature-{name}.md` and ensure it mirrors the base template before writing tests.
 
 1. **Gather Context** — If not already provided, ask for: feature name/branch, summary of changes (link to design & requirements docs), target environment, existing test suites, and any flaky/slow tests to avoid.
-2. **Analyze Testing Template** — Identify required sections from `docs/ai/testing/feature-{name}.md`. Confirm success criteria and edge cases from requirements & design docs. Note available mocks/stubs/fixtures.
-3. **Unit Tests (aim for 100% coverage)** — For each module/function: list behavior scenarios (happy path, edge cases, error handling), generate test cases with assertions using existing utilities/mocks, and highlight missing branches preventing full coverage.
-4. **Integration Tests** — Identify critical cross-component flows. Define setup/teardown steps and test cases for interaction boundaries, data contracts, and failure modes.
-5. **Coverage Strategy** — Recommend coverage tooling commands. Call out files/functions still needing coverage and suggest additional tests if <100%.
-6. **Update Documentation** — Summarize tests added or still missing. Update `docs/ai/testing/feature-{name}.md` with links to test files and results. Flag deferred tests as follow-up tasks.
+2. **Use Memory for Context** — Search memory for existing testing patterns and prior edge cases: `npx ai-devkit@latest memory search --query "<feature testing strategy>"`.
+3. **Analyze Testing Template** — Identify required sections from `docs/ai/testing/feature-{name}.md`. Confirm success criteria and edge cases from requirements & design docs. Note available mocks/stubs/fixtures.
+4. **Unit Tests (aim for 100% coverage)** — For each module/function: list behavior scenarios (happy path, edge cases, error handling), generate test cases with assertions using existing utilities/mocks, and highlight missing branches preventing full coverage.
+5. **Integration Tests** — Identify critical cross-component flows. Define setup/teardown steps and test cases for interaction boundaries, data contracts, and failure modes.
+6. **Coverage Strategy** — Recommend coverage tooling commands. Call out files/functions still needing coverage and suggest additional tests if <100%.
+7. **Store Reusable Knowledge** — Save reusable testing patterns or tricky fixtures with `npx ai-devkit@latest memory store ...`.
+8. **Update Documentation** — Summarize tests added or still missing. Update `docs/ai/testing/feature-{name}.md` with links to test files and results. Flag deferred tests as follow-up tasks.
+9. **Next Command Guidance** — If tests expose design issues, return to `/review-design`; otherwise continue to `/code-review`.

package/dist/lib/AgentManager.d.ts

@@ -1,104 +0,0 @@
-/**
- * Agent Manager
- *
- * Orchestrates agent detection across multiple adapter types.
- * Manages adapter registration and aggregates results from all adapters.
- */
-import type { AgentAdapter, AgentInfo } from './adapters/AgentAdapter';
-/**
- * Agent Manager Class
- *
- * Central manager for detecting AI agents across different types.
- * Supports multiple adapters (Claude Code, Gemini CLI, etc.)
- *
- * @example
- * ```typescript
- * const manager = new AgentManager();
- * manager.registerAdapter(new ClaudeCodeAdapter());
- *
- * const agents = await manager.listAgents();
- * console.log(`Found ${agents.length} agents`);
- * ```
- */
-export declare class AgentManager {
-    private adapters;
-    /**
-     * Register an adapter for a specific agent type
-     *
-     * @param adapter Agent adapter to register
-     * @throws Error if an adapter for this type is already registered
-     *
-     * @example
-     * ```typescript
-     * manager.registerAdapter(new ClaudeCodeAdapter());
-     * ```
-     */
-    registerAdapter(adapter: AgentAdapter): void;
-    /**
-     * Unregister an adapter by type
-     *
-     * @param type Agent type to unregister
-     * @returns True if adapter was removed, false if not found
-     */
-    unregisterAdapter(type: string): boolean;
-    /**
-     * Get all registered adapters
-     *
-     * @returns Array of registered adapters
-     */
-    getAdapters(): AgentAdapter[];
-    /**
-     * Check if an adapter is registered for a specific type
-     *
-     * @param type Agent type to check
-     * @returns True if adapter is registered
-     */
-    hasAdapter(type: string): boolean;
-    /**
-     * List all running AI agents detected by registered adapters
-     *
-     * Queries all registered adapters and aggregates results.
-     * Handles errors gracefully - if one adapter fails, others still run.
-     *
-     * @returns Array of detected agents from all adapters
-     *
-     * @example
-     * ```typescript
-     * const agents = await manager.listAgents();
-     *
-     * agents.forEach(agent => {
-     *   console.log(`${agent.name}: ${agent.status}`);
-     * });
-     * ```
-     */
-    listAgents(): Promise<AgentInfo[]>;
-    /**
-     * Sort agents by status priority
-     *
-     * Priority order: waiting > running > idle > unknown
-     * This ensures agents that need attention appear first.
-     *
-     * @param agents Array of agents to sort
-     * @returns Sorted array of agents
-     */
-    private sortAgentsByStatus;
-    /**
-     * Get count of registered adapters
-     *
-     * @returns Number of registered adapters
-     */
-    getAdapterCount(): number;
-    /**
-     * Clear all registered adapters
-     */
-    clear(): void;
-    /**
-     * Resolve an agent by name (exact or partial match)
-     *
-     * @param input Name to search for
-     * @param agents List of agents to search within
-     * @returns Matched agent (unique), array of agents (ambiguous), or null (none)
-     */
-    resolveAgent(input: string, agents: AgentInfo[]): AgentInfo | AgentInfo[] | null;
-}
-//# sourceMappingURL=AgentManager.d.ts.map

package/dist/lib/AgentManager.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"AgentManager.d.ts","sourceRoot":"","sources":["../../src/lib/AgentManager.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,OAAO,KAAK,EAAE,YAAY,EAAE,SAAS,EAAE,MAAM,yBAAyB,CAAC;AAGvE;;;;;;;;;;;;;;GAcG;AACH,qBAAa,YAAY;IACrB,OAAO,CAAC,QAAQ,CAAwC;IAExD;;;;;;;;;;OAUG;IACH,eAAe,CAAC,OAAO,EAAE,YAAY,GAAG,IAAI;IAU5C;;;;;OAKG;IACH,iBAAiB,CAAC,IAAI,EAAE,MAAM,GAAG,OAAO;IAIxC;;;;OAIG;IACH,WAAW,IAAI,YAAY,EAAE;IAI7B;;;;;OAKG;IACH,UAAU,CAAC,IAAI,EAAE,MAAM,GAAG,OAAO;IAIjC;;;;;;;;;;;;;;;;OAgBG;IACG,UAAU,IAAI,OAAO,CAAC,SAAS,EAAE,CAAC;IAsCxC;;;;;;;;OAQG;IACH,OAAO,CAAC,kBAAkB;IAe1B;;;;OAIG;IACH,eAAe,IAAI,MAAM;IAIzB;;OAEG;IACH,KAAK,IAAI,IAAI;IAIb;;;;;;OAMG;IACH,YAAY,CAAC,KAAK,EAAE,MAAM,EAAE,MAAM,EAAE,SAAS,EAAE,GAAG,SAAS,GAAG,SAAS,EAAE,GAAG,IAAI;CAiBnF"}

package/dist/lib/AgentManager.js

@@ -1,185 +0,0 @@
-"use strict";
-/**
- * Agent Manager
- *
- * Orchestrates agent detection across multiple adapter types.
- * Manages adapter registration and aggregates results from all adapters.
- */
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.AgentManager = void 0;
-const AgentAdapter_1 = require("./adapters/AgentAdapter");
-/**
- * Agent Manager Class
- *
- * Central manager for detecting AI agents across different types.
- * Supports multiple adapters (Claude Code, Gemini CLI, etc.)
- *
- * @example
- * ```typescript
- * const manager = new AgentManager();
- * manager.registerAdapter(new ClaudeCodeAdapter());
- *
- * const agents = await manager.listAgents();
- * console.log(`Found ${agents.length} agents`);
- * ```
- */
-class AgentManager {
-    constructor() {
-        this.adapters = new Map();
-    }
-    /**
-     * Register an adapter for a specific agent type
-     *
-     * @param adapter Agent adapter to register
-     * @throws Error if an adapter for this type is already registered
-     *
-     * @example
-     * ```typescript
-     * manager.registerAdapter(new ClaudeCodeAdapter());
-     * ```
-     */
-    registerAdapter(adapter) {
-        const adapterKey = adapter.type;
-        if (this.adapters.has(adapterKey)) {
-            throw new Error(`Adapter for type "${adapterKey}" is already registered`);
-        }
-        this.adapters.set(adapterKey, adapter);
-    }
-    /**
-     * Unregister an adapter by type
-     *
-     * @param type Agent type to unregister
-     * @returns True if adapter was removed, false if not found
-     */
-    unregisterAdapter(type) {
-        return this.adapters.delete(type);
-    }
-    /**
-     * Get all registered adapters
-     *
-     * @returns Array of registered adapters
-     */
-    getAdapters() {
-        return Array.from(this.adapters.values());
-    }
-    /**
-     * Check if an adapter is registered for a specific type
-     *
-     * @param type Agent type to check
-     * @returns True if adapter is registered
-     */
-    hasAdapter(type) {
-        return this.adapters.has(type);
-    }
-    /**
-     * List all running AI agents detected by registered adapters
-     *
-     * Queries all registered adapters and aggregates results.
-     * Handles errors gracefully - if one adapter fails, others still run.
-     *
-     * @returns Array of detected agents from all adapters
-     *
-     * @example
-     * ```typescript
-     * const agents = await manager.listAgents();
-     *
-     * agents.forEach(agent => {
-     *   console.log(`${agent.name}: ${agent.status}`);
-     * });
-     * ```
-     */
-    async listAgents() {
-        const allAgents = [];
-        const errors = [];
-        // Query all adapters in parallel
-        const adapterPromises = Array.from(this.adapters.values()).map(async (adapter) => {
-            try {
-                const agents = await adapter.detectAgents();
-                return { type: adapter.type, agents, error: null };
-            }
-            catch (error) {
-                // Capture error but don't throw - allow other adapters to continue
-                const err = error instanceof Error ? error : new Error(String(error));
-                errors.push({ type: adapter.type, error: err });
-                return { type: adapter.type, agents: [], error: err };
-            }
-        });
-        const results = await Promise.all(adapterPromises);
-        // Aggregate all successful results
-        for (const result of results) {
-            if (result.error === null) {
-                allAgents.push(...result.agents);
-            }
-        }
-        // Log errors if any (but don't throw - partial results are useful)
-        if (errors.length > 0) {
-            console.error(`Warning: ${errors.length} adapter(s) failed:`);
-            errors.forEach(({ type, error }) => {
-                console.error(`  - ${type}: ${error.message}`);
-            });
-        }
-        // Sort by status priority (waiting first, then running, then idle)
-        return this.sortAgentsByStatus(allAgents);
-    }
-    /**
-     * Sort agents by status priority
-     *
-     * Priority order: waiting > running > idle > unknown
-     * This ensures agents that need attention appear first.
-     *
-     * @param agents Array of agents to sort
-     * @returns Sorted array of agents
-     */
-    sortAgentsByStatus(agents) {
-        const statusPriority = {
-            [AgentAdapter_1.AgentStatus.WAITING]: 0,
-            [AgentAdapter_1.AgentStatus.RUNNING]: 1,
-            [AgentAdapter_1.AgentStatus.IDLE]: 2,
-            [AgentAdapter_1.AgentStatus.UNKNOWN]: 3,
-        };
-        return agents.sort((a, b) => {
-            const priorityA = statusPriority[a.status] ?? 999;
-            const priorityB = statusPriority[b.status] ?? 999;
-            return priorityA - priorityB;
-        });
-    }
-    /**
-     * Get count of registered adapters
-     *
-     * @returns Number of registered adapters
-     */
-    getAdapterCount() {
-        return this.adapters.size;
-    }
-    /**
-     * Clear all registered adapters
-     */
-    clear() {
-        this.adapters.clear();
-    }
-    /**
-     * Resolve an agent by name (exact or partial match)
-     *
-     * @param input Name to search for
-     * @param agents List of agents to search within
-     * @returns Matched agent (unique), array of agents (ambiguous), or null (none)
-     */
-    resolveAgent(input, agents) {
-        if (!input || agents.length === 0)
-            return null;
-        const lowerInput = input.toLowerCase();
-        // 1. Exact match (case-insensitive)
-        const exactMatch = agents.find(a => a.name.toLowerCase() === lowerInput);
-        if (exactMatch)
-            return exactMatch;
-        // 2. Partial match (prefix or contains)
-        const matches = agents.filter(a => a.name.toLowerCase().includes(lowerInput));
-        if (matches.length === 1)
-            return matches[0];
-        if (matches.length > 1)
-            return matches;
-        return null;
-    }
-}
-exports.AgentManager = AgentManager;
-//# sourceMappingURL=AgentManager.js.map

package/dist/lib/AgentManager.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"AgentManager.js","sourceRoot":"","sources":["../../src/lib/AgentManager.ts"],"names":[],"mappings":";AAAA;;;;;GAKG;;;AAGH,0DAAsD;AAEtD;;;;;;;;;;;;;;GAcG;AACH,MAAa,YAAY;IAAzB;QACY,aAAQ,GAA8B,IAAI,GAAG,EAAE,CAAC;IA2K5D,CAAC;IAzKG;;;;;;;;;;OAUG;IACH,eAAe,CAAC,OAAqB;QACjC,MAAM,UAAU,GAAG,OAAO,CAAC,IAAI,CAAC;QAEhC,IAAI,IAAI,CAAC,QAAQ,CAAC,GAAG,CAAC,UAAU,CAAC,EAAE,CAAC;YAChC,MAAM,IAAI,KAAK,CAAC,qBAAqB,UAAU,yBAAyB,CAAC,CAAC;QAC9E,CAAC;QAED,IAAI,CAAC,QAAQ,CAAC,GAAG,CAAC,UAAU,EAAE,OAAO,CAAC,CAAC;IAC3C,CAAC;IAED;;;;;OAKG;IACH,iBAAiB,CAAC,IAAY;QAC1B,OAAO,IAAI,CAAC,QAAQ,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC;IACtC,CAAC;IAED;;;;OAIG;IACH,WAAW;QACP,OAAO,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,QAAQ,CAAC,MAAM,EAAE,CAAC,CAAC;IAC9C,CAAC;IAED;;;;;OAKG;IACH,UAAU,CAAC,IAAY;QACnB,OAAO,IAAI,CAAC,QAAQ,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC;IACnC,CAAC;IAED;;;;;;;;;;;;;;;;OAgBG;IACH,KAAK,CAAC,UAAU;QACZ,MAAM,SAAS,GAAgB,EAAE,CAAC;QAClC,MAAM,MAAM,GAA0C,EAAE,CAAC;QAEzD,iCAAiC;QACjC,MAAM,eAAe,GAAG,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,QAAQ,CAAC,MAAM,EAAE,CAAC,CAAC,GAAG,CAAC,KAAK,EAAE,OAAO,EAAE,EAAE;YAC7E,IAAI,CAAC;gBACD,MAAM,MAAM,GAAG,MAAM,OAAO,CAAC,YAAY,EAAE,CAAC;gBAC5C,OAAO,EAAE,IAAI,EAAE,OAAO,CAAC,IAAI,EAAE,MAAM,EAAE,KAAK,EAAE,IAAI,EAAE,CAAC;YACvD,CAAC;YAAC,OAAO,KAAK,EAAE,CAAC;gBACb,mEAAmE;gBACnE,MAAM,GAAG,GAAG,KAAK,YAAY,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,IAAI,KAAK,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC,CAAC;gBACtE,MAAM,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,OAAO,CAAC,IAAI,EAAE,KAAK,EAAE,GAAG,EAAE,CAAC,CAAC;gBAChD,OAAO,EAAE,IAAI,EAAE,OAAO,CAAC,IAAI,EAAE,MAAM,EAAE,EAAE,EAAE,KAAK,EAAE,GAAG,EAAE,CAAC;YAC1D,CAAC;QACL,CAAC,CAAC,CAAC;QAEH,MAAM,OAAO,GAAG,MAAM,OAAO,CAAC,GAAG,CAAC,eAAe,CAAC,CAAC;QAEnD,mCAAmC;QACnC,KAAK,MAAM,MAAM,IAAI,OAAO,EAAE,CAAC;YAC3B,IAAI,MAAM,CAAC,KAAK,KAAK,IAAI,EAAE,CAAC;gBACxB,SAAS,CAAC,IAAI,CAAC,GAAG,MAAM,CAAC,MAAM,CAAC,CAAC;YACrC,CAAC;QACL,CAAC;QAED,mEAAmE;QACnE,IAAI,MAAM,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;YACpB,OAAO,CAAC,KAAK,CAAC,YAAY,MAAM,CAAC,MAAM,qBAAqB,CAAC,CAAC;YAC9D,MAAM,CAAC,OAAO,CAAC,CAAC,EAAE,IAAI,EAAE,KAAK,EAAE,EAAE,EAAE;gBAC/B,OAAO,CAAC,KAAK,CAAC,OAAO,IAAI,KAAK,KAAK,CAAC,OAAO,EAAE,CAAC,CAAC;YACnD,CAAC,CAAC,CAAC;QACP,CAAC;QAED,mEAAmE;QACnE,OAAO,IAAI,CAAC,kBAAkB,CAAC,SAAS,CAAC,CAAC;IAC9C,CAAC;IAED;;;;;;;;OAQG;IACK,kBAAkB,CAAC,MAAmB;QAC1C,MAAM,cAAc,GAAgC;YAChD,CAAC,0BAAW,CAAC,OAAO,CAAC,EAAE,CAAC;YACxB,CAAC,0BAAW,CAAC,OAAO,CAAC,EAAE,CAAC;YACxB,CAAC,0BAAW,CAAC,IAAI,CAAC,EAAE,CAAC;YACrB,CAAC,0BAAW,CAAC,OAAO,CAAC,EAAE,CAAC;SAC3B,CAAC;QAEF,OAAO,MAAM,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE;YACxB,MAAM,SAAS,GAAG,cAAc,CAAC,CAAC,CAAC,MAAM,CAAC,IAAI,GAAG,CAAC;YAClD,MAAM,SAAS,GAAG,cAAc,CAAC,CAAC,CAAC,MAAM,CAAC,IAAI,GAAG,CAAC;YAClD,OAAO,SAAS,GAAG,SAAS,CAAC;QACjC,CAAC,CAAC,CAAC;IACP,CAAC;IAED;;;;OAIG;IACH,eAAe;QACX,OAAO,IAAI,CAAC,QAAQ,CAAC,IAAI,CAAC;IAC9B,CAAC;IAED;;OAEG;IACH,KAAK;QACD,IAAI,CAAC,QAAQ,CAAC,KAAK,EAAE,CAAC;IAC1B,CAAC;IAED;;;;;;OAMG;IACH,YAAY,CAAC,KAAa,EAAE,MAAmB;QAC3C,IAAI,CAAC,KAAK,IAAI,MAAM,CAAC,MAAM,KAAK,CAAC;YAAE,OAAO,IAAI,CAAC;QAE/C,MAAM,UAAU,GAAG,KAAK,CAAC,WAAW,EAAE,CAAC;QAEvC,oCAAoC;QACpC,MAAM,UAAU,GAAG,MAAM,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC,WAAW,EAAE,KAAK,UAAU,CAAC,CAAC;QACzE,IAAI,UAAU;YAAE,OAAO,UAAU,CAAC;QAElC,wCAAwC;QACxC,MAAM,OAAO,GAAG,MAAM,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC,WAAW,EAAE,CAAC,QAAQ,CAAC,UAAU,CAAC,CAAC,CAAC;QAE9E,IAAI,OAAO,CAAC,MAAM,KAAK,CAAC;YAAE,OAAO,OAAO,CAAC,CAAC,CAAC,CAAC;QAC5C,IAAI,OAAO,CAAC,MAAM,GAAG,CAAC;YAAE,OAAO,OAAO,CAAC;QAEvC,OAAO,IAAI,CAAC;IAChB,CAAC;CACJ;AA5KD,oCA4KC"}

package/dist/lib/TerminalFocusManager.d.ts

@@ -1,22 +0,0 @@
-export interface TerminalLocation {
-    type: 'tmux' | 'iterm2' | 'terminal-app' | 'unknown';
-    identifier: string;
-    tty: string;
-}
-export declare class TerminalFocusManager {
-    /**
-     * Find the terminal location (emulator info) for a given process ID
-     */
-    findTerminal(pid: number): Promise<TerminalLocation | null>;
-    /**
-     * Focus the terminal identified by the location
-     */
-    focusTerminal(location: TerminalLocation): Promise<boolean>;
-    private findTmuxPane;
-    private findITerm2Session;
-    private findTerminalAppWindow;
-    private focusTmuxPane;
-    private focusITerm2Session;
-    private focusTerminalAppWindow;
-}
-//# sourceMappingURL=TerminalFocusManager.d.ts.map

package/dist/lib/TerminalFocusManager.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"TerminalFocusManager.d.ts","sourceRoot":"","sources":["../../src/lib/TerminalFocusManager.ts"],"names":[],"mappings":"AAMA,MAAM,WAAW,gBAAgB;IAC7B,IAAI,EAAE,MAAM,GAAG,QAAQ,GAAG,cAAc,GAAG,SAAS,CAAC;IACrD,UAAU,EAAE,MAAM,CAAC;IACnB,GAAG,EAAE,MAAM,CAAC;CACf;AAED,qBAAa,oBAAoB;IAC7B;;OAEG;IACG,YAAY,CAAC,GAAG,EAAE,MAAM,GAAG,OAAO,CAAC,gBAAgB,GAAG,IAAI,CAAC;IA8BjE;;OAEG;IACG,aAAa,CAAC,QAAQ,EAAE,gBAAgB,GAAG,OAAO,CAAC,OAAO,CAAC;YAiBnD,YAAY;YAyBZ,iBAAiB;YAkCjB,qBAAqB;YAgCrB,aAAa;YASb,kBAAkB;YAoBlB,sBAAsB;CAkBvC"}