sylas-edge-worker 0.2.21

package/dist/prompts/subroutines/user-testing-summary.md

@@ -0,0 +1,87 @@
+# User Testing Summary - Final Response for Linear
+
+Generate a comprehensive summary of the user testing session for posting to Linear.
+
+## Your Task
+
+Create a clear, structured summary that covers:
+
+### 1. Testing Overview
+- What was tested (features, workflows, integrations)
+- Testing approach and methodology used
+- Scope of the testing session
+
+### 2. Test Results
+- Total number of scenarios/tests executed
+- Pass/fail breakdown
+- Key observations and findings
+
+### 3. Issues Discovered (if any)
+- Description of each issue found
+- Severity assessment (critical/high/medium/low)
+- Reproduction steps for failures
+- Relevant error messages or logs
+
+### 4. Recommendations
+- Suggested fixes or follow-up actions
+- Areas that may need additional testing
+- Any improvements identified during testing
+
+## Format Requirements
+
+- **Be concise but comprehensive** - aim for a well-structured summary
+- Use clear, professional language suitable for Linear
+- Use markdown formatting for readability
+- Focus on what matters to stakeholders
+- **To mention someone**: Use `https://linear.app/linear/profiles/username` syntax where `username` is the Linear username (e.g., `https://linear.app/linear/profiles/alice` to mention @alice)
+
+## Constraints
+
+- **You have exactly 1 turn** - generate the summary in a single response
+- This is the final output that will be posted to Linear
+- Make it informative and actionable
+
+## Example Format
+
+```
+## Testing Summary
+
+[Brief overview of what was tested and the testing approach]
+
+### Results
+
+| Status | Count |
+|--------|-------|
+| ✅ Passed | X |
+| ❌ Failed | Y |
+| ⚠️ Observations | Z |
+
++++Test Details
+- [Test 1]: [Result and notes]
+- [Test 2]: [Result and notes]
++++
+
++++Issues Found
+1. **[Issue title]** - [Severity]
+   - Description: [What went wrong]
+   - Steps to reproduce: [How to trigger]
+   - Notes: [Additional context]
++++
+
+## Recommendations
+
+[Next steps and suggested actions]
+
+## Status
+
+[Overall testing status and conclusions]
+```
+
+## Collapsible Sections
+
+**IMPORTANT**: When creating your summary, make the following sections collapsible (collapsed by default):
+
+- **"Test Details"** section - Wrap with `+++Test Details\n...\n+++`
+- **"Issues Found"** section - Wrap with `+++Issues Found\n...\n+++`
+
+This keeps the summary concise while preserving detailed information for those who want to expand and read it.

package/dist/prompts/subroutines/user-testing.md

@@ -0,0 +1,48 @@
+# User Testing Phase
+
+Perform testing as requested by the user. This subroutine allows interactive testing based on user instructions.
+
+## Your Task
+
+Execute the testing activities requested by the user:
+
+### 1. Understand the Testing Request
+- Review the user's testing requirements from the issue description
+- Identify what needs to be tested (features, workflows, integrations, etc.)
+- Clarify the scope and success criteria for the testing
+
+### 2. Execute Tests
+- Run the tests or testing scenarios as requested
+- Follow any specific testing instructions provided by the user
+- Document test results and observations as you go
+- Note any unexpected behavior or issues discovered
+
+### 3. Interactive Testing
+- Be responsive to user feedback during the testing process
+- The user may provide additional instructions or adjustments mid-session
+- Adapt your testing approach based on user guidance
+- Report progress and findings to enable real-time feedback
+
+### 4. Document Findings
+- Track all test results (pass/fail/observations)
+- Note any bugs, issues, or areas of concern discovered
+- Document reproduction steps for any failures
+- Capture relevant logs, error messages, or screenshots if applicable
+
+## Important Notes
+
+- **Do NOT commit or push changes** - that happens in a separate subroutine if needed
+- **Do NOT create or update PRs** - focus on testing only
+- **Be thorough and methodical** - test systematically based on user requirements
+- **Communicate clearly** - report findings as you discover them
+- **Follow user instructions** - this is a user-driven testing session
+
+## Expected Output
+
+Provide a completion message summarizing the testing session:
+
+```
+Testing complete - [X] scenarios tested, [Y] passed, [Z] issues found.
+```
+
+Example: "Testing complete - 5 scenarios tested, 4 passed, 1 issue found (login redirect failure)."

package/dist/prompts/subroutines/validation-fixer.md

@@ -0,0 +1,56 @@
+# Validation Fixer - Fix Verification Failures
+
+The previous verification step failed. Your task is to fix the specific issues identified.
+
+## Failure Context
+
+<validation_failure>
+{{FAILURE_REASON}}
+</validation_failure>
+
+<iteration_info>
+Attempt {{ITERATION}} of {{MAX_ITERATIONS}}
+</iteration_info>
+
+{{#if PREVIOUS_ATTEMPTS}}
+<previous_attempts>
+{{PREVIOUS_ATTEMPTS}}
+</previous_attempts>
+{{/if}}
+
+## Your Task
+
+Fix ONLY the specific issues mentioned in the failure reason above. Do not make unrelated changes.
+
+### Guidelines
+
+1. **Focus on the specific failures** - Address only what failed, nothing else
+2. **Read error messages carefully** - The failure reason contains specific error details
+3. **Make minimal changes** - Fix the issue with the smallest possible change
+4. **Avoid introducing new issues** - Be careful not to break other things while fixing
+5. **If you've seen this error before** - Check the previous attempts to understand what didn't work
+
+### Common Fix Patterns
+
+- **Acceptance criteria failures**: Re-read the specific criterion that failed, understand what's missing, and implement the missing functionality
+- **Test failures**: Read the failing test, understand the expected vs actual behavior, fix the code or test
+- **TypeScript errors**: Check the type definitions and ensure proper typing
+- **Linting errors**: Run the linter with auto-fix first, then manually fix what remains
+- **Build errors**: Check imports, exports, and module resolution
+
+## Important Notes
+
+- **Do NOT commit or push changes** - just fix the issues
+- **Do NOT create or update PRs** - that happens in a later subroutine
+- **Do NOT post Linear comments** - your output is for internal workflow only
+- Be thorough but efficient - we have limited retry attempts
+
+## Expected Output
+
+After fixing the issues, provide a brief completion message (1 sentence max):
+
+```
+Fixed: [brief description of what was fixed]
+```
+
+Example: "Fixed: Corrected type error in UserService.ts by adding missing optional chaining"

package/dist/prompts/subroutines/verbose-summary.md

@@ -0,0 +1,46 @@
+# Summary Phase - Final Response Generation
+
+You have completed both the primary work and closure review. Now generate a comprehensive summary of everything accomplished.
+
+## Your Task
+
+Create a clear, concise summary for Linear that covers:
+
+### 1. Work Completed
+- What features were implemented or bugs were fixed
+- Key technical decisions made
+- Any changes to the original scope or approach
+
+### 2. Implementation Details
+- High-level overview of the implementation approach
+- Key files modified or created
+- Any new dependencies, tools, or patterns introduced
+
+### 3. Testing & Quality Assurance
+- What testing was performed
+- Test results and coverage
+- Any known limitations or edge cases
+
+### 4. Pull Request Information
+- Link to the GitHub PR
+- Status of the PR (ready for review, needs attention, etc.)
+- Any special review notes or areas that need extra attention
+
+### 5. Next Steps (if applicable)
+- Any follow-up tasks or future improvements identified
+- Configuration or deployment steps required
+- Notes for reviewers
+
+## Format Requirements
+
+- Use clear, professional language suitable for Linear
+- Be concise but comprehensive
+- Use markdown formatting for readability
+- Focus on what matters to stakeholders and reviewers
+- **To mention someone**: Use `https://linear.app/linear/profiles/username` syntax where `username` is the Linear username (e.g., `https://linear.app/linear/profiles/alice` to mention @alice)
+
+## Constraints
+
+- **You have exactly 1 turn** - generate the summary in a single response
+- This is the final output that will be posted to Linear
+- Make it informative and actionable

package/dist/prompts/subroutines/verifications.md

@@ -0,0 +1,77 @@
+# Verifications - Testing and Quality Checks
+
+You have completed the primary work on this issue. Now perform thorough verification to ensure everything works correctly and meets quality standards.
+
+## Your Tasks
+
+### 1. Acceptance Criteria Validation (CRITICAL - Do This First)
+
+Use the issue tracker `get_issue` tool to fetch the current issue details. The issue identifier is available in your conversation context (e.g., "CYPACK-123").
+
+**Steps:**
+1. Fetch the issue using the issue tracker `get_issue` tool with the issue identifier
+2. Extract ALL acceptance criteria from the issue description (look for bullet points, numbered lists, checkboxes, or sections labeled "Acceptance Criteria", "Requirements", "Definition of Done", etc.)
+3. For EACH acceptance criterion, verify that the implementation satisfies it
+4. Document which criteria pass and which fail
+
+**Important:** If no explicit acceptance criteria are found, extract implied requirements from the issue title and description. Every issue has requirements that must be verified.
+
+### 2. Code Quality Review
+- Review all code changes for quality, consistency, and best practices
+- Ensure proper error handling and edge cases are covered
+- Verify code follows project conventions and patterns
+- Check for any code smells or areas that need refactoring
+
+### 3. Testing & Verification
+- Run all relevant tests and ensure they pass
+- **Do NOT fix failing tests yourself** - just report the failures
+- Verify the implementation meets all requirements from the issue description
+- Check that existing functionality wasn't broken by the changes
+
+### 4. Linting & Type Checking
+- Run linting tools and report any issues
+- Run TypeScript type checking (if applicable) and report any errors
+- **Do NOT fix linting/type errors yourself** - just report them
+
+### 5. Documentation Review
+- Check if relevant documentation needs updating
+- Note any debug code, console.logs, or commented-out sections that should be removed
+
+## Important Notes
+
+- **Do NOT commit or push changes** - that happens in a later subroutine
+- **Do NOT create or update PRs** - that also happens in a later subroutine
+- **Do NOT touch the changelog** - a separate subroutine handles changelog updates
+- **Do NOT fix issues yourself** - your job is to verify and report
+- **Do NOT post Linear comments** - your output is for internal workflow only
+- Be thorough in running and reporting verification results
+- **Acceptance criteria validation is MANDATORY** - failing to validate against acceptance criteria counts as a failed verification
+
+## Expected FINAL Message Output Format
+
+You MUST respond in your FINAL message with a JSON object in exactly this format:
+
+```json
+{
+  "pass": true,
+  "reason": "All 3 acceptance criteria met. 47 tests passing, linting clean, types valid"
+}
+```
+
+Or if there are failures:
+
+```json
+{
+  "pass": false,
+  "reason": "Acceptance criteria failed: 'Support pagination' not implemented. TypeScript error in src/services/UserService.ts:42 - Property 'email' does not exist on type 'User'. 3 tests failing in auth.test.ts"
+}
+```
+
+### Output Rules
+
+1. **pass**: Set to `true` if ALL verifications pass (including ALL acceptance criteria), `false` if ANY fail
+2. **reason**:
+   - If passing: Brief summary that mentions acceptance criteria status, e.g., "All X acceptance criteria met. Y tests passing, linting clean, types valid"
+   - If failing: Specific error details that would help someone fix the issues. **Always list any failing acceptance criteria first**, then other failures.
+
+**CRITICAL**: Your entire final response message must be valid JSON matching the schema above. Do not include any text before or after the JSON.

package/dist/prompts/todolist-system-prompt-extension.md

@@ -0,0 +1,15 @@
+<task_management_instructions>
+CRITICAL: You MUST use the TodoWrite and TodoRead tools extensively:
+- IMMEDIATELY create a comprehensive task list at the beginning of your work
+- Break down complex tasks into smaller, actionable items
+- Mark tasks as 'in_progress' when you start them
+- Mark tasks as 'completed' immediately after finishing them
+- Only have ONE task 'in_progress' at a time
+- Add new tasks as you discover them during your work
+- Your first response should focus on creating a thorough task breakdown
+
+Remember: Your first message is internal planning. Use this time to:
+1. Thoroughly analyze the issue and requirements
+2. Create detailed todos using TodoWrite
+3. Plan your approach systematically
+</task_management_instructions>

package/dist/sinks/IActivitySink.d.ts

@@ -0,0 +1,60 @@
+import type { AgentActivityContent } from "sylas-core";
+/**
+ * String literal type for activity signals.
+ * Maps to platform-specific signal enums (e.g., Linear's AgentActivitySignal).
+ */
+export type ActivitySignal = "auth" | "select" | "stop" | "continue";
+/**
+ * Options for posting an activity.
+ */
+export interface ActivityPostOptions {
+    /** Whether the activity is ephemeral (disappears when replaced by next activity) */
+    ephemeral?: boolean;
+    /** Signal modifier for how the activity should be interpreted */
+    signal?: ActivitySignal;
+    /** Additional metadata for the signal */
+    signalMetadata?: Record<string, unknown>;
+}
+/**
+ * Result of posting an activity.
+ */
+export interface ActivityPostResult {
+    /** The ID of the created activity, if available */
+    activityId?: string;
+}
+/**
+ * Interface for activity sinks that receive and process agent session activities.
+ *
+ * IActivitySink decouples activity posting from IIssueTrackerService, enabling
+ * multiple activity sinks (Linear workspaces, GitHub, etc.) to receive session
+ * activities based on session context.
+ *
+ * Implementations should:
+ * - Provide a unique identifier (workspace ID, org ID, etc.)
+ * - Support posting activities to agent sessions
+ * - Support creating new agent sessions on issues
+ */
+export interface IActivitySink {
+    /**
+     * Unique identifier for this sink (e.g., Linear workspace ID, GitHub org ID).
+     * Used by GlobalSessionRegistry to route activities to the correct sink.
+     */
+    readonly id: string;
+    /**
+     * Post an activity to an existing agent session.
+     *
+     * @param sessionId - The agent session ID to post to
+     * @param activity - The activity content (thought, action, response, error, etc.)
+     * @param options - Optional settings for ephemeral, signal, signalMetadata
+     * @returns Promise that resolves with the result of the activity post
+     */
+    postActivity(sessionId: string, activity: AgentActivityContent, options?: ActivityPostOptions): Promise<ActivityPostResult>;
+    /**
+     * Create a new agent session on an issue.
+     *
+     * @param issueId - The issue ID to attach the session to
+     * @returns Promise that resolves with the created session ID
+     */
+    createAgentSession(issueId: string): Promise<string>;
+}
+//# sourceMappingURL=IActivitySink.d.ts.map

package/dist/sinks/IActivitySink.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"IActivitySink.d.ts","sourceRoot":"","sources":["../../src/sinks/IActivitySink.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,YAAY,CAAC;AAEvD;;;GAGG;AACH,MAAM,MAAM,cAAc,GAAG,MAAM,GAAG,QAAQ,GAAG,MAAM,GAAG,UAAU,CAAC;AAErE;;GAEG;AACH,MAAM,WAAW,mBAAmB;IACnC,oFAAoF;IACpF,SAAS,CAAC,EAAE,OAAO,CAAC;IACpB,iEAAiE;IACjE,MAAM,CAAC,EAAE,cAAc,CAAC;IACxB,yCAAyC;IACzC,cAAc,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;CACzC;AAED;;GAEG;AACH,MAAM,WAAW,kBAAkB;IAClC,mDAAmD;IACnD,UAAU,CAAC,EAAE,MAAM,CAAC;CACpB;AAED;;;;;;;;;;;GAWG;AACH,MAAM,WAAW,aAAa;IAC7B;;;OAGG;IACH,QAAQ,CAAC,EAAE,EAAE,MAAM,CAAC;IAEpB;;;;;;;OAOG;IACH,YAAY,CACX,SAAS,EAAE,MAAM,EACjB,QAAQ,EAAE,oBAAoB,EAC9B,OAAO,CAAC,EAAE,mBAAmB,GAC3B,OAAO,CAAC,kBAAkB,CAAC,CAAC;IAE/B;;;;;OAKG;IACH,kBAAkB,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,MAAM,CAAC,CAAC;CACrD"}

package/dist/sinks/IActivitySink.js

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

package/dist/sinks/IActivitySink.js.map

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

package/dist/sinks/LinearActivitySink.d.ts

@@ -0,0 +1,69 @@
+import { type AgentActivityContent, type IIssueTrackerService } from "sylas-core";
+import type { ActivityPostOptions, ActivityPostResult, IActivitySink } from "./IActivitySink.js";
+/**
+ * Linear-specific implementation of IActivitySink.
+ *
+ * LinearActivitySink wraps an IIssueTrackerService instance to provide activity
+ * sink functionality for Linear workspaces. It delegates activity posting and
+ * session creation to the underlying issue tracker service.
+ *
+ * @example
+ * ```typescript
+ * const issueTracker = new LinearIssueTrackerService(linearClient, {
+ *   workspaceId: 'workspace-123',
+ *   // ... other OAuth config
+ * });
+ *
+ * const sink = new LinearActivitySink(issueTracker, 'workspace-123');
+ *
+ * // Create a session
+ * const sessionId = await sink.createAgentSession('issue-id-456');
+ *
+ * // Post activities
+ * const result = await sink.postActivity(sessionId, {
+ *   type: 'thought',
+ *   body: 'Analyzing the issue...'
+ * });
+ * ```
+ */
+export declare class LinearActivitySink implements IActivitySink {
+    /**
+     * Unique identifier for this sink (Linear workspace ID).
+     */
+    readonly id: string;
+    private readonly issueTracker;
+    /**
+     * Create a new LinearActivitySink.
+     *
+     * @param issueTracker - The IIssueTrackerService instance to delegate to
+     * @param workspaceId - The Linear workspace ID (used as sink ID)
+     */
+    constructor(issueTracker: IIssueTrackerService, workspaceId: string);
+    /**
+     * Map a platform-agnostic ActivitySignal string to Linear's AgentActivitySignal enum.
+     */
+    private mapSignal;
+    /**
+     * Post an activity to an existing agent session.
+     *
+     * Wraps IIssueTrackerService.createAgentActivity() to provide a simplified
+     * interface for activity posting.
+     *
+     * @param sessionId - The agent session ID to post to
+     * @param activity - The activity content (thought, action, response, error, etc.)
+     * @param options - Optional settings for ephemeral, signal, signalMetadata
+     * @returns Promise that resolves with the activity post result
+     */
+    postActivity(sessionId: string, activity: AgentActivityContent, options?: ActivityPostOptions): Promise<ActivityPostResult>;
+    /**
+     * Create a new agent session on an issue.
+     *
+     * Wraps IIssueTrackerService.createAgentSessionOnIssue() to provide a simplified
+     * interface for session creation.
+     *
+     * @param issueId - The issue ID to attach the session to
+     * @returns Promise that resolves with the created session ID
+     */
+    createAgentSession(issueId: string): Promise<string>;
+}
+//# sourceMappingURL=LinearActivitySink.d.ts.map

package/dist/sinks/LinearActivitySink.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"LinearActivitySink.d.ts","sourceRoot":"","sources":["../../src/sinks/LinearActivitySink.ts"],"names":[],"mappings":"AAAA,OAAO,EACN,KAAK,oBAAoB,EAEzB,KAAK,oBAAoB,EACzB,MAAM,YAAY,CAAC;AACpB,OAAO,KAAK,EACX,mBAAmB,EACnB,kBAAkB,EAElB,aAAa,EACb,MAAM,oBAAoB,CAAC;AAE5B;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AACH,qBAAa,kBAAmB,YAAW,aAAa;IACvD;;OAEG;IACH,SAAgB,EAAE,EAAE,MAAM,CAAC;IAE3B,OAAO,CAAC,QAAQ,CAAC,YAAY,CAAuB;IAEpD;;;;;OAKG;gBACS,YAAY,EAAE,oBAAoB,EAAE,WAAW,EAAE,MAAM;IAKnE;;OAEG;IACH,OAAO,CAAC,SAAS;IAajB;;;;;;;;;;OAUG;IACG,YAAY,CACjB,SAAS,EAAE,MAAM,EACjB,QAAQ,EAAE,oBAAoB,EAC9B,OAAO,CAAC,EAAE,mBAAmB,GAC3B,OAAO,CAAC,kBAAkB,CAAC;IAmB9B;;;;;;;;OAQG;IACG,kBAAkB,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,MAAM,CAAC;CAqB1D"}

package/dist/sinks/LinearActivitySink.js

@@ -0,0 +1,111 @@
+import { AgentActivitySignal, } from "sylas-core";
+/**
+ * Linear-specific implementation of IActivitySink.
+ *
+ * LinearActivitySink wraps an IIssueTrackerService instance to provide activity
+ * sink functionality for Linear workspaces. It delegates activity posting and
+ * session creation to the underlying issue tracker service.
+ *
+ * @example
+ * ```typescript
+ * const issueTracker = new LinearIssueTrackerService(linearClient, {
+ *   workspaceId: 'workspace-123',
+ *   // ... other OAuth config
+ * });
+ *
+ * const sink = new LinearActivitySink(issueTracker, 'workspace-123');
+ *
+ * // Create a session
+ * const sessionId = await sink.createAgentSession('issue-id-456');
+ *
+ * // Post activities
+ * const result = await sink.postActivity(sessionId, {
+ *   type: 'thought',
+ *   body: 'Analyzing the issue...'
+ * });
+ * ```
+ */
+export class LinearActivitySink {
+    /**
+     * Unique identifier for this sink (Linear workspace ID).
+     */
+    id;
+    issueTracker;
+    /**
+     * Create a new LinearActivitySink.
+     *
+     * @param issueTracker - The IIssueTrackerService instance to delegate to
+     * @param workspaceId - The Linear workspace ID (used as sink ID)
+     */
+    constructor(issueTracker, workspaceId) {
+        this.issueTracker = issueTracker;
+        this.id = workspaceId;
+    }
+    /**
+     * Map a platform-agnostic ActivitySignal string to Linear's AgentActivitySignal enum.
+     */
+    mapSignal(signal) {
+        switch (signal) {
+            case "auth":
+                return AgentActivitySignal.Auth;
+            case "select":
+                return AgentActivitySignal.Select;
+            case "stop":
+                return AgentActivitySignal.Stop;
+            case "continue":
+                return AgentActivitySignal.Continue;
+        }
+    }
+    /**
+     * Post an activity to an existing agent session.
+     *
+     * Wraps IIssueTrackerService.createAgentActivity() to provide a simplified
+     * interface for activity posting.
+     *
+     * @param sessionId - The agent session ID to post to
+     * @param activity - The activity content (thought, action, response, error, etc.)
+     * @param options - Optional settings for ephemeral, signal, signalMetadata
+     * @returns Promise that resolves with the activity post result
+     */
+    async postActivity(sessionId, activity, options) {
+        const result = await this.issueTracker.createAgentActivity({
+            agentSessionId: sessionId,
+            content: activity,
+            ...(options?.ephemeral !== undefined && { ephemeral: options.ephemeral }),
+            ...(options?.signal && { signal: this.mapSignal(options.signal) }),
+            ...(options?.signalMetadata && {
+                signalMetadata: options.signalMetadata,
+            }),
+        });
+        if (result.success && result.agentActivity) {
+            const agentActivity = await result.agentActivity;
+            return { activityId: agentActivity.id };
+        }
+        return {};
+    }
+    /**
+     * Create a new agent session on an issue.
+     *
+     * Wraps IIssueTrackerService.createAgentSessionOnIssue() to provide a simplified
+     * interface for session creation.
+     *
+     * @param issueId - The issue ID to attach the session to
+     * @returns Promise that resolves with the created session ID
+     */
+    async createAgentSession(issueId) {
+        const result = await this.issueTracker.createAgentSessionOnIssue({
+            issueId,
+        });
+        if (!result.success) {
+            throw new Error(`Failed to create agent session for issue ${issueId}: request was not successful`);
+        }
+        // Extract session ID from the result
+        // Result has `agentSession` property that may be a Promise
+        const session = await result.agentSession;
+        if (!session) {
+            throw new Error(`Failed to create agent session for issue ${issueId}: session is undefined`);
+        }
+        return session.id;
+    }
+}
+//# sourceMappingURL=LinearActivitySink.js.map

package/dist/sinks/LinearActivitySink.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"LinearActivitySink.js","sourceRoot":"","sources":["../../src/sinks/LinearActivitySink.ts"],"names":[],"mappings":"AAAA,OAAO,EAEN,mBAAmB,GAEnB,MAAM,YAAY,CAAC;AAQpB;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AACH,MAAM,OAAO,kBAAkB;IAC9B;;OAEG;IACa,EAAE,CAAS;IAEV,YAAY,CAAuB;IAEpD;;;;;OAKG;IACH,YAAY,YAAkC,EAAE,WAAmB;QAClE,IAAI,CAAC,YAAY,GAAG,YAAY,CAAC;QACjC,IAAI,CAAC,EAAE,GAAG,WAAW,CAAC;IACvB,CAAC;IAED;;OAEG;IACK,SAAS,CAAC,MAAsB;QACvC,QAAQ,MAAM,EAAE,CAAC;YAChB,KAAK,MAAM;gBACV,OAAO,mBAAmB,CAAC,IAAI,CAAC;YACjC,KAAK,QAAQ;gBACZ,OAAO,mBAAmB,CAAC,MAAM,CAAC;YACnC,KAAK,MAAM;gBACV,OAAO,mBAAmB,CAAC,IAAI,CAAC;YACjC,KAAK,UAAU;gBACd,OAAO,mBAAmB,CAAC,QAAQ,CAAC;QACtC,CAAC;IACF,CAAC;IAED;;;;;;;;;;OAUG;IACH,KAAK,CAAC,YAAY,CACjB,SAAiB,EACjB,QAA8B,EAC9B,OAA6B;QAE7B,MAAM,MAAM,GAAG,MAAM,IAAI,CAAC,YAAY,CAAC,mBAAmB,CAAC;YAC1D,cAAc,EAAE,SAAS;YACzB,OAAO,EAAE,QAAQ;YACjB,GAAG,CAAC,OAAO,EAAE,SAAS,KAAK,SAAS,IAAI,EAAE,SAAS,EAAE,OAAO,CAAC,SAAS,EAAE,CAAC;YACzE,GAAG,CAAC,OAAO,EAAE,MAAM,IAAI,EAAE,MAAM,EAAE,IAAI,CAAC,SAAS,CAAC,OAAO,CAAC,MAAM,CAAC,EAAE,CAAC;YAClE,GAAG,CAAC,OAAO,EAAE,cAAc,IAAI;gBAC9B,cAAc,EAAE,OAAO,CAAC,cAAc;aACtC,CAAC;SACF,CAAC,CAAC;QAEH,IAAI,MAAM,CAAC,OAAO,IAAI,MAAM,CAAC,aAAa,EAAE,CAAC;YAC5C,MAAM,aAAa,GAAG,MAAM,MAAM,CAAC,aAAa,CAAC;YACjD,OAAO,EAAE,UAAU,EAAE,aAAa,CAAC,EAAE,EAAE,CAAC;QACzC,CAAC;QAED,OAAO,EAAE,CAAC;IACX,CAAC;IAED;;;;;;;;OAQG;IACH,KAAK,CAAC,kBAAkB,CAAC,OAAe;QACvC,MAAM,MAAM,GAAG,MAAM,IAAI,CAAC,YAAY,CAAC,yBAAyB,CAAC;YAChE,OAAO;SACP,CAAC,CAAC;QAEH,IAAI,CAAC,MAAM,CAAC,OAAO,EAAE,CAAC;YACrB,MAAM,IAAI,KAAK,CACd,4CAA4C,OAAO,8BAA8B,CACjF,CAAC;QACH,CAAC;QAED,qCAAqC;QACrC,2DAA2D;QAC3D,MAAM,OAAO,GAAG,MAAM,MAAM,CAAC,YAAY,CAAC;QAC1C,IAAI,CAAC,OAAO,EAAE,CAAC;YACd,MAAM,IAAI,KAAK,CACd,4CAA4C,OAAO,wBAAwB,CAC3E,CAAC;QACH,CAAC;QACD,OAAO,OAAO,CAAC,EAAE,CAAC;IACnB,CAAC;CACD"}

package/dist/sinks/NoopActivitySink.d.ts

@@ -0,0 +1,13 @@
+import type { AgentActivityContent } from "sylas-core";
+import type { ActivityPostOptions, ActivityPostResult, IActivitySink } from "./IActivitySink.js";
+/**
+ * A no-op activity sink that silently discards all activities.
+ * Used for platforms like Slack where activities are not posted to an external tracker.
+ */
+export declare class NoopActivitySink implements IActivitySink {
+    readonly id: string;
+    constructor(id?: string);
+    postActivity(_sessionId: string, _activity: AgentActivityContent, _options?: ActivityPostOptions): Promise<ActivityPostResult>;
+    createAgentSession(_issueId: string): Promise<string>;
+}
+//# sourceMappingURL=NoopActivitySink.d.ts.map

package/dist/sinks/NoopActivitySink.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"NoopActivitySink.d.ts","sourceRoot":"","sources":["../../src/sinks/NoopActivitySink.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,YAAY,CAAC;AACvD,OAAO,KAAK,EACX,mBAAmB,EACnB,kBAAkB,EAClB,aAAa,EACb,MAAM,oBAAoB,CAAC;AAE5B;;;GAGG;AACH,qBAAa,gBAAiB,YAAW,aAAa;IACrD,QAAQ,CAAC,EAAE,EAAE,MAAM,CAAC;gBAER,EAAE,SAAS;IAIjB,YAAY,CACjB,UAAU,EAAE,MAAM,EAClB,SAAS,EAAE,oBAAoB,EAC/B,QAAQ,CAAC,EAAE,mBAAmB,GAC5B,OAAO,CAAC,kBAAkB,CAAC;IAIxB,kBAAkB,CAAC,QAAQ,EAAE,MAAM,GAAG,OAAO,CAAC,MAAM,CAAC;CAG3D"}

package/dist/sinks/NoopActivitySink.js

@@ -0,0 +1,17 @@
+/**
+ * A no-op activity sink that silently discards all activities.
+ * Used for platforms like Slack where activities are not posted to an external tracker.
+ */
+export class NoopActivitySink {
+    id;
+    constructor(id = "noop") {
+        this.id = id;
+    }
+    async postActivity(_sessionId, _activity, _options) {
+        return {};
+    }
+    async createAgentSession(_issueId) {
+        return "";
+    }
+}
+//# sourceMappingURL=NoopActivitySink.js.map

package/dist/sinks/NoopActivitySink.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"NoopActivitySink.js","sourceRoot":"","sources":["../../src/sinks/NoopActivitySink.ts"],"names":[],"mappings":"AAOA;;;GAGG;AACH,MAAM,OAAO,gBAAgB;IACnB,EAAE,CAAS;IAEpB,YAAY,EAAE,GAAG,MAAM;QACtB,IAAI,CAAC,EAAE,GAAG,EAAE,CAAC;IACd,CAAC;IAED,KAAK,CAAC,YAAY,CACjB,UAAkB,EAClB,SAA+B,EAC/B,QAA8B;QAE9B,OAAO,EAAE,CAAC;IACX,CAAC;IAED,KAAK,CAAC,kBAAkB,CAAC,QAAgB;QACxC,OAAO,EAAE,CAAC;IACX,CAAC;CACD"}

package/dist/sinks/index.d.ts

@@ -0,0 +1,9 @@
+/**
+ * Activity sinks for posting agent session activities to various platforms.
+ *
+ * @module sinks
+ */
+export type { ActivityPostOptions, ActivityPostResult, ActivitySignal, IActivitySink, } from "./IActivitySink.js";
+export { LinearActivitySink } from "./LinearActivitySink.js";
+export { NoopActivitySink } from "./NoopActivitySink.js";
+//# sourceMappingURL=index.d.ts.map

package/dist/sinks/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/sinks/index.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,YAAY,EACX,mBAAmB,EACnB,kBAAkB,EAClB,cAAc,EACd,aAAa,GACb,MAAM,oBAAoB,CAAC;AAC5B,OAAO,EAAE,kBAAkB,EAAE,MAAM,yBAAyB,CAAC;AAC7D,OAAO,EAAE,gBAAgB,EAAE,MAAM,uBAAuB,CAAC"}

package/dist/sinks/index.js

@@ -0,0 +1,8 @@
+/**
+ * Activity sinks for posting agent session activities to various platforms.
+ *
+ * @module sinks
+ */
+export { LinearActivitySink } from "./LinearActivitySink.js";
+export { NoopActivitySink } from "./NoopActivitySink.js";
+//# sourceMappingURL=index.js.map

package/dist/sinks/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/sinks/index.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAQH,OAAO,EAAE,kBAAkB,EAAE,MAAM,yBAAyB,CAAC;AAC7D,OAAO,EAAE,gBAAgB,EAAE,MAAM,uBAAuB,CAAC"}