@goondocks/myco 0.1.0

package/dist/src/capture/prompts/prompts/schema.yaml

@@ -0,0 +1,97 @@
+# Myco Observation Schema
+#
+# Defines the observation types that the LLM uses for classification.
+# Ported from open-agent-kit's battle-tested schema.
+#
+# Each type has:
+#   - description: What this type captures (shown to LLM)
+#   - examples: Example observations of this type (help LLM understand)
+
+version: "1.0"
+
+observation_types:
+  gotcha:
+    description: "Non-obvious behaviors, edge cases, or tricky parts that could trip someone up"
+    examples:
+      - "The API returns 200 even for validation errors, check the response body for success field"
+      - "File paths must be absolute, relative paths silently fail"
+      - "The cache TTL is in seconds, not milliseconds despite the variable name"
+
+  bug_fix:
+    description: "Bugs that were identified and fixed, including root cause and solution"
+    examples:
+      - "Race condition in async handler - added mutex lock around shared state"
+      - "Off-by-one error in pagination - fixed boundary check in slice operation"
+      - "Memory leak from unclosed connections - added try/finally cleanup"
+
+  decision:
+    description: "Architecture choices, design decisions, or approach selections with rationale"
+    examples:
+      - "Chose SQLite over PostgreSQL for activity storage - simpler deployment, sufficient for single-user"
+      - "Using background thread instead of async for file watcher - better isolation from event loop"
+      - "Storing tags as comma-separated string - avoids metadata array limitations"
+
+  discovery:
+    description: "Important facts learned about the codebase, APIs, patterns, or conventions"
+    examples:
+      - "The config is loaded lazily on first access via __getattr__"
+      - "All API routes use dependency injection for state"
+      - "Test fixtures are shared across modules via conftest.py"
+
+  trade_off:
+    description: "Trade-offs that were considered, alternatives evaluated, and why current approach was chosen"
+    examples:
+      - "Chose simplicity over performance - O(n) scan acceptable for expected data size"
+      - "Sacrificed type safety for flexibility - using dict instead of typed model for config"
+      - "Accepted eventual consistency for better throughput in background processing"
+
+activity_classifications:
+  exploration:
+    description: "Reading code, searching, understanding the codebase"
+    indicators:
+      - "Mostly Read, Grep, Glob tools"
+      - "Few or no file modifications"
+      - "Questions about how things work"
+
+  debugging:
+    description: "Investigating errors, fixing bugs, troubleshooting"
+    indicators:
+      - "Error messages in output"
+      - "Test failures"
+      - "Iterative fixes to same files"
+
+  implementation:
+    description: "Writing new code, adding features, creating new files"
+    indicators:
+      - "New files created"
+      - "Significant Write/Edit operations"
+      - "Feature-related file names"
+
+  refactoring:
+    description: "Modifying existing code structure without adding new functionality"
+    indicators:
+      - "Edits without new files"
+      - "Moving/renaming operations"
+      - "No new test files"
+
+session_origin_types:
+  planning:
+    description: "Planning-phase session"
+    indicators:
+      - "High read:edit ratio"
+      - "Few file modifications"
+  investigation:
+    description: "Exploration/debugging session"
+    indicators:
+      - "Many file reads"
+      - "Minimal edits"
+  implementation:
+    description: "Active coding session"
+    indicators:
+      - "Significant file modifications"
+      - "Low read:edit ratio"
+  mixed:
+    description: "Combined activity types"
+    indicators:
+      - "Both reads and edits"
+      - "Does not fit other categories"

package/dist/src/capture/prompts/prompts/session-summary.md

@@ -0,0 +1,65 @@
+---
+name: session-summary
+description: Generate a high-level summary of what was accomplished in the session
+---
+
+You are summarizing a coding session to help future sessions understand what was done.
+
+The developer working in this session is **{{developer_name}}**. Refer to them by name instead of "the user" or "the developer".
+
+## Session Statistics
+
+- Duration: {{session_duration}} minutes
+- Prompt batches: {{prompt_batch_count}}
+- Files read: {{files_read_count}}
+- Files modified: {{files_modified_count}}
+- Files created: {{files_created_count}}
+- Total tool calls: {{tool_calls}}
+- **Session Origin Type:** {{session_origin_type}}
+
+## Prompt Batches
+
+{{prompt_batches}}
+
+## Session Origin Type
+
+The session origin type indicates the dominant activity pattern:
+- **planning**: Primarily reading and planning, few file modifications
+- **investigation**: Exploration and debugging, many reads with minimal edits
+- **implementation**: Active coding with significant file modifications
+- **mixed**: Combined activity patterns
+
+When summarizing, note whether observations are planning-phase findings (may become
+stale once work is implemented) versus implementation learnings (more likely to remain
+relevant long-term).
+
+## Task
+
+Write a concise summary of this session. You have access to both the user's prompts and the agent's actions, so capture the full picture:
+
+- **Developer intent**: What was {{developer_name}} trying to accomplish? What was their approach or priority?
+- **Key actions**: What did the agent do? Which files were modified and why?
+- **Outcomes**: What was achieved? Any decisions made or problems solved?
+- **Context**: Any constraints, trade-offs, or discoveries worth noting?
+
+Be specific - include file names, feature names, and technical details when relevant.
+
+## Output Format
+
+Respond with ONLY the summary text. No JSON, no code blocks, just plain text. A bulleted list is acceptable if it improves clarity.
+
+## Examples
+
+Good (captures intent + actions + outcome):
+- "Chris wanted to add dark mode support. Implemented theme toggle in settings/ThemeProvider.tsx using CSS variables, added useTheme hook, and updated 12 components to use theme tokens instead of hardcoded colors. Chose CSS variables over styled-components for better performance."
+
+Good (captures debugging journey):
+- "Alex reported intermittent test failures in CI. Investigated flaky tests in tests/api/, discovered race condition in database cleanup. Fixed by adding proper test isolation with transaction rollbacks. Also identified that TestClient was sharing state across tests."
+
+Good (captures exploration with learnings):
+- "Sam needed to understand the payment processing flow before adding refund support. Traced code from PaymentController through StripeService to webhook handlers. Key finding: payments use idempotency keys stored in Redis, refunds will need similar pattern."
+
+Bad (too vague):
+- "Fixed some bugs and added a feature"
+- "Worked on authentication"
+- "Made improvements to the codebase"

package/dist/src/capture/prompts/prompts/session-title.md

@@ -0,0 +1,46 @@
+---
+name: session-title
+description: Generate a short title from a session summary
+---
+
+Generate a short, descriptive title (6-12 words) for this coding session based on its summary.
+
+## Session Summary
+
+{{session_summary}}
+
+## Task
+
+Create a brief title that captures the main accomplishment or focus of this session. The title should:
+- Be 6-12 words maximum
+- Start with an action verb when appropriate (Add, Fix, Implement, Refactor, Debug, Update, Configure, etc.)
+- Capture the primary task or feature worked on
+- Be specific enough to distinguish from other sessions
+- If this is a continuation session, emphasize what THIS session specifically did, not the overall goal
+
+## Output Format
+
+Respond with ONLY the title text as plain text.
+- No JSON
+- No quotes
+- No markdown
+- No punctuation at the end
+- No explanation or preamble
+
+Just the title itself, nothing else.
+
+## Examples
+
+Good titles:
+- Add dark mode theme support
+- Fix authentication token refresh bug
+- Implement user profile settings page
+- Refactor payment processing service
+- Debug CI pipeline test failures
+- Port OAK prompt templates to Myco
+
+Bad titles (too vague):
+- Working on code
+- Bug fix
+- Feature implementation
+- Updates

package/dist/src/capture/prompts/schema.yaml

@@ -0,0 +1,97 @@
+# Myco Observation Schema
+#
+# Defines the observation types that the LLM uses for classification.
+# Ported from open-agent-kit's battle-tested schema.
+#
+# Each type has:
+#   - description: What this type captures (shown to LLM)
+#   - examples: Example observations of this type (help LLM understand)
+
+version: "1.0"
+
+observation_types:
+  gotcha:
+    description: "Non-obvious behaviors, edge cases, or tricky parts that could trip someone up"
+    examples:
+      - "The API returns 200 even for validation errors, check the response body for success field"
+      - "File paths must be absolute, relative paths silently fail"
+      - "The cache TTL is in seconds, not milliseconds despite the variable name"
+
+  bug_fix:
+    description: "Bugs that were identified and fixed, including root cause and solution"
+    examples:
+      - "Race condition in async handler - added mutex lock around shared state"
+      - "Off-by-one error in pagination - fixed boundary check in slice operation"
+      - "Memory leak from unclosed connections - added try/finally cleanup"
+
+  decision:
+    description: "Architecture choices, design decisions, or approach selections with rationale"
+    examples:
+      - "Chose SQLite over PostgreSQL for activity storage - simpler deployment, sufficient for single-user"
+      - "Using background thread instead of async for file watcher - better isolation from event loop"
+      - "Storing tags as comma-separated string - avoids metadata array limitations"
+
+  discovery:
+    description: "Important facts learned about the codebase, APIs, patterns, or conventions"
+    examples:
+      - "The config is loaded lazily on first access via __getattr__"
+      - "All API routes use dependency injection for state"
+      - "Test fixtures are shared across modules via conftest.py"
+
+  trade_off:
+    description: "Trade-offs that were considered, alternatives evaluated, and why current approach was chosen"
+    examples:
+      - "Chose simplicity over performance - O(n) scan acceptable for expected data size"
+      - "Sacrificed type safety for flexibility - using dict instead of typed model for config"
+      - "Accepted eventual consistency for better throughput in background processing"
+
+activity_classifications:
+  exploration:
+    description: "Reading code, searching, understanding the codebase"
+    indicators:
+      - "Mostly Read, Grep, Glob tools"
+      - "Few or no file modifications"
+      - "Questions about how things work"
+
+  debugging:
+    description: "Investigating errors, fixing bugs, troubleshooting"
+    indicators:
+      - "Error messages in output"
+      - "Test failures"
+      - "Iterative fixes to same files"
+
+  implementation:
+    description: "Writing new code, adding features, creating new files"
+    indicators:
+      - "New files created"
+      - "Significant Write/Edit operations"
+      - "Feature-related file names"
+
+  refactoring:
+    description: "Modifying existing code structure without adding new functionality"
+    indicators:
+      - "Edits without new files"
+      - "Moving/renaming operations"
+      - "No new test files"
+
+session_origin_types:
+  planning:
+    description: "Planning-phase session"
+    indicators:
+      - "High read:edit ratio"
+      - "Few file modifications"
+  investigation:
+    description: "Exploration/debugging session"
+    indicators:
+      - "Many file reads"
+      - "Minimal edits"
+  implementation:
+    description: "Active coding session"
+    indicators:
+      - "Significant file modifications"
+      - "Low read:edit ratio"
+  mixed:
+    description: "Combined activity types"
+    indicators:
+      - "Both reads and edits"
+      - "Does not fit other categories"

package/dist/src/capture/prompts/session-summary.md

@@ -0,0 +1,65 @@
+---
+name: session-summary
+description: Generate a high-level summary of what was accomplished in the session
+---
+
+You are summarizing a coding session to help future sessions understand what was done.
+
+The developer working in this session is **{{developer_name}}**. Refer to them by name instead of "the user" or "the developer".
+
+## Session Statistics
+
+- Duration: {{session_duration}} minutes
+- Prompt batches: {{prompt_batch_count}}
+- Files read: {{files_read_count}}
+- Files modified: {{files_modified_count}}
+- Files created: {{files_created_count}}
+- Total tool calls: {{tool_calls}}
+- **Session Origin Type:** {{session_origin_type}}
+
+## Prompt Batches
+
+{{prompt_batches}}
+
+## Session Origin Type
+
+The session origin type indicates the dominant activity pattern:
+- **planning**: Primarily reading and planning, few file modifications
+- **investigation**: Exploration and debugging, many reads with minimal edits
+- **implementation**: Active coding with significant file modifications
+- **mixed**: Combined activity patterns
+
+When summarizing, note whether observations are planning-phase findings (may become
+stale once work is implemented) versus implementation learnings (more likely to remain
+relevant long-term).
+
+## Task
+
+Write a concise summary of this session. You have access to both the user's prompts and the agent's actions, so capture the full picture:
+
+- **Developer intent**: What was {{developer_name}} trying to accomplish? What was their approach or priority?
+- **Key actions**: What did the agent do? Which files were modified and why?
+- **Outcomes**: What was achieved? Any decisions made or problems solved?
+- **Context**: Any constraints, trade-offs, or discoveries worth noting?
+
+Be specific - include file names, feature names, and technical details when relevant.
+
+## Output Format
+
+Respond with ONLY the summary text. No JSON, no code blocks, just plain text. A bulleted list is acceptable if it improves clarity.
+
+## Examples
+
+Good (captures intent + actions + outcome):
+- "Chris wanted to add dark mode support. Implemented theme toggle in settings/ThemeProvider.tsx using CSS variables, added useTheme hook, and updated 12 components to use theme tokens instead of hardcoded colors. Chose CSS variables over styled-components for better performance."
+
+Good (captures debugging journey):
+- "Alex reported intermittent test failures in CI. Investigated flaky tests in tests/api/, discovered race condition in database cleanup. Fixed by adding proper test isolation with transaction rollbacks. Also identified that TestClient was sharing state across tests."
+
+Good (captures exploration with learnings):
+- "Sam needed to understand the payment processing flow before adding refund support. Traced code from PaymentController through StripeService to webhook handlers. Key finding: payments use idempotency keys stored in Redis, refunds will need similar pattern."
+
+Bad (too vague):
+- "Fixed some bugs and added a feature"
+- "Worked on authentication"
+- "Made improvements to the codebase"

package/dist/src/capture/prompts/session-title.md

@@ -0,0 +1,46 @@
+---
+name: session-title
+description: Generate a short title from a session summary
+---
+
+Generate a short, descriptive title (6-12 words) for this coding session based on its summary.
+
+## Session Summary
+
+{{session_summary}}
+
+## Task
+
+Create a brief title that captures the main accomplishment or focus of this session. The title should:
+- Be 6-12 words maximum
+- Start with an action verb when appropriate (Add, Fix, Implement, Refactor, Debug, Update, Configure, etc.)
+- Capture the primary task or feature worked on
+- Be specific enough to distinguish from other sessions
+- If this is a continuation session, emphasize what THIS session specifically did, not the overall goal
+
+## Output Format
+
+Respond with ONLY the title text as plain text.
+- No JSON
+- No quotes
+- No markdown
+- No punctuation at the end
+- No explanation or preamble
+
+Just the title itself, nothing else.
+
+## Examples
+
+Good titles:
+- Add dark mode theme support
+- Fix authentication token refresh bug
+- Implement user profile settings page
+- Refactor payment processing service
+- Debug CI pipeline test failures
+- Port OAK prompt templates to Myco
+
+Bad titles (too vague):
+- Working on code
+- Bug fix
+- Feature implementation
+- Updates

package/dist/src/capture/prompts.d.ts

@@ -0,0 +1,77 @@
+/**
+ * Prompt template system for activity observation extraction.
+ *
+ * Templates are loaded from markdown files with YAML frontmatter.
+ * Schema is loaded from schema.yaml as the single source of truth
+ * for observation types and activity classifications.
+ *
+ * Ported from open-agent-kit's Python implementation.
+ */
+export interface ObservationType {
+    name: string;
+    description: string;
+    examples: string[];
+}
+export interface ClassificationType {
+    name: string;
+    description: string;
+    indicators: string[];
+}
+export interface Schema {
+    version: string;
+    observationTypes: ObservationType[];
+    classificationTypes: ClassificationType[];
+}
+export interface PromptTemplate {
+    name: string;
+    description: string;
+    prompt: string;
+    activityFilter?: string[];
+    minActivities: number;
+}
+export interface RenderContext {
+    activities: string;
+    session_duration: string;
+    files_read: string;
+    files_modified: string;
+    files_created: string;
+    errors: string;
+    observation_types: string;
+    classification_types: string;
+    type_names: string;
+    developer_name?: string;
+    prompt_batch_count?: string;
+    files_read_count?: string;
+    files_modified_count?: string;
+    files_created_count?: string;
+    tool_calls?: string;
+    session_origin_type?: string;
+    prompt_batches?: string;
+    session_summary?: string;
+    tool_summary?: string;
+    has_errors?: string;
+}
+export declare function loadSchema(schemaPath?: string): Schema;
+export declare function formatObservationTypes(schema: Schema): string;
+export declare function formatClassificationTypes(schema: Schema): string;
+export declare function getTypeNamesString(schema: Schema): string;
+export declare function loadTemplate(filePath: string): PromptTemplate | null;
+export declare function loadAllTemplates(promptsDir?: string): Map<string, PromptTemplate>;
+export declare function selectTemplate(templates: Map<string, PromptTemplate>, toolNames: string[], hasErrors: boolean): PromptTemplate;
+export type SessionOriginType = 'planning' | 'investigation' | 'implementation' | 'mixed';
+export declare function classifySessionOrigin(toolNames: string[]): SessionOriginType;
+export declare function renderPrompt(template: PromptTemplate, context: Partial<RenderContext>): string;
+export interface ActivityEvent {
+    tool?: string;
+    tool_name?: string;
+    input?: Record<string, unknown>;
+    output?: string;
+    error?: string;
+    timestamp?: string;
+}
+export declare function formatActivities(events: ActivityEvent[], maxItems?: number): string;
+export declare function extractFilesList(events: ActivityEvent[], toolFilter: string[]): string[];
+export declare function extractErrors(events: ActivityEvent[]): string[];
+export declare function extractToolNames(events: ActivityEvent[]): string[];
+export declare function buildExtractionContext(events: ActivityEvent[], sessionDuration: number, schema: Schema): Partial<RenderContext>;
+//# sourceMappingURL=prompts.d.ts.map

package/dist/src/capture/prompts.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"prompts.d.ts","sourceRoot":"","sources":["../../../src/capture/prompts.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAUH,MAAM,WAAW,eAAe;IAC9B,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,EAAE,MAAM,CAAC;IACpB,QAAQ,EAAE,MAAM,EAAE,CAAC;CACpB;AAED,MAAM,WAAW,kBAAkB;IACjC,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,EAAE,MAAM,CAAC;IACpB,UAAU,EAAE,MAAM,EAAE,CAAC;CACtB;AAED,MAAM,WAAW,MAAM;IACrB,OAAO,EAAE,MAAM,CAAC;IAChB,gBAAgB,EAAE,eAAe,EAAE,CAAC;IACpC,mBAAmB,EAAE,kBAAkB,EAAE,CAAC;CAC3C;AAID,MAAM,WAAW,cAAc;IAC7B,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,EAAE,MAAM,CAAC;IACpB,MAAM,EAAE,MAAM,CAAC;IACf,cAAc,CAAC,EAAE,MAAM,EAAE,CAAC;IAC1B,aAAa,EAAE,MAAM,CAAC;CACvB;AAID,MAAM,WAAW,aAAa;IAC5B,UAAU,EAAE,MAAM,CAAC;IACnB,gBAAgB,EAAE,MAAM,CAAC;IACzB,UAAU,EAAE,MAAM,CAAC;IACnB,cAAc,EAAE,MAAM,CAAC;IACvB,aAAa,EAAE,MAAM,CAAC;IACtB,MAAM,EAAE,MAAM,CAAC;IACf,iBAAiB,EAAE,MAAM,CAAC;IAC1B,oBAAoB,EAAE,MAAM,CAAC;IAC7B,UAAU,EAAE,MAAM,CAAC;IAEnB,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB,kBAAkB,CAAC,EAAE,MAAM,CAAC;IAC5B,gBAAgB,CAAC,EAAE,MAAM,CAAC;IAC1B,oBAAoB,CAAC,EAAE,MAAM,CAAC;IAC9B,mBAAmB,CAAC,EAAE,MAAM,CAAC;IAC7B,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,mBAAmB,CAAC,EAAE,MAAM,CAAC;IAC7B,cAAc,CAAC,EAAE,MAAM,CAAC;IAExB,eAAe,CAAC,EAAE,MAAM,CAAC;IAEzB,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,UAAU,CAAC,EAAE,MAAM,CAAC;CACrB;AA6BD,wBAAgB,UAAU,CAAC,UAAU,CAAC,EAAE,MAAM,GAAG,MAAM,CAuCtD;AAID,wBAAgB,sBAAsB,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,CAS7D;AAED,wBAAgB,yBAAyB,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,CAIhE;AAED,wBAAgB,kBAAkB,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,CAEzD;AAID,wBAAgB,YAAY,CAAC,QAAQ,EAAE,MAAM,GAAG,cAAc,GAAG,IAAI,CAqBpE;AAED,wBAAgB,gBAAgB,CAAC,UAAU,CAAC,EAAE,MAAM,GAAG,GAAG,CAAC,MAAM,EAAE,cAAc,CAAC,CAejF;AAID,wBAAgB,cAAc,CAC5B,SAAS,EAAE,GAAG,CAAC,MAAM,EAAE,cAAc,CAAC,EACtC,SAAS,EAAE,MAAM,EAAE,EACnB,SAAS,EAAE,OAAO,GACjB,cAAc,CAoBhB;AAID,MAAM,MAAM,iBAAiB,GAAG,UAAU,GAAG,eAAe,GAAG,gBAAgB,GAAG,OAAO,CAAC;AAE1F,wBAAgB,qBAAqB,CAAC,SAAS,EAAE,MAAM,EAAE,GAAG,iBAAiB,CAc5E;AAID,wBAAgB,YAAY,CAAC,QAAQ,EAAE,cAAc,EAAE,OAAO,EAAE,OAAO,CAAC,aAAa,CAAC,GAAG,MAAM,CAQ9F;AAID,MAAM,WAAW,aAAa;IAC5B,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,KAAK,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;IAChC,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAED,wBAAgB,gBAAgB,CAAC,MAAM,EAAE,aAAa,EAAE,EAAE,QAAQ,SAAK,GAAG,MAAM,CAqB/E;AAED,wBAAgB,gBAAgB,CAAC,MAAM,EAAE,aAAa,EAAE,EAAE,UAAU,EAAE,MAAM,EAAE,GAAG,MAAM,EAAE,CASxF;AAED,wBAAgB,aAAa,CAAC,MAAM,EAAE,aAAa,EAAE,GAAG,MAAM,EAAE,CAM/D;AAED,wBAAgB,gBAAgB,CAAC,MAAM,EAAE,aAAa,EAAE,GAAG,MAAM,EAAE,CAElE;AAID,wBAAgB,sBAAsB,CACpC,MAAM,EAAE,aAAa,EAAE,EACvB,eAAe,EAAE,MAAM,EACvB,MAAM,EAAE,MAAM,GACb,OAAO,CAAC,aAAa,CAAC,CA0BxB"}