@sweny-ai/core 0.1.14 → 0.1.16

package/dist/__tests__/schema.test.js

@@ -1,7 +1,6 @@
 import { describe, it, expect } from "vitest";
 import { workflowZ, nodeZ, edgeZ, skillZ, toolZ, parseWorkflow, validateWorkflow, workflowJsonSchema, } from "../schema.js";
-import { triageWorkflow } from "../workflows/triage.js";
-import { implementWorkflow } from "../workflows/implement.js";
+import { triageWorkflow, implementWorkflow } from "../workflows/index.js";
 // ─── Test fixtures ───────────────────────────────────────────────
 const validWorkflow = {
     id: "test-wf",

package/dist/cli/main.js

@@ -7,9 +7,7 @@ const _require = createRequire(import.meta.url);
 const { version } = _require("../../package.json");
 import chalk from "chalk";
 import { execute } from "../executor.js";
-import { triageWorkflow } from "../workflows/triage.js";
-import { implementWorkflow } from "../workflows/implement.js";
-import { seedContentWorkflow } from "../workflows/seed-content.js";
+import { triageWorkflow, implementWorkflow, seedContentWorkflow } from "../workflows/index.js";
 import { consoleLogger } from "../types.js";
 import { ClaudeClient } from "../claude.js";
 import { createSkillMap, configuredSkills } from "../skills/index.js";

package/dist/executor.test.js

@@ -7,8 +7,7 @@ import { execute } from "./executor.js";
 import { MockClaude, createFileSkill } from "./testing.js";
 import { createSkillMap } from "./skills/index.js";
 import { validateWorkflow, parseWorkflow } from "./schema.js";
-import { triageWorkflow } from "./workflows/triage.js";
-import { implementWorkflow } from "./workflows/implement.js";
+import { triageWorkflow, implementWorkflow } from "./workflows/index.js";
 // ─── Test fixtures ───────────────────────────────────────────────
 const tmpBase = path.join(tmpdir(), "sweny-core-test");
 function freshDir(name) {

package/dist/workflows/browser.js

@@ -0,0 +1,3 @@
+export const triageWorkflow = {"id":"triage","name":"Alert Triage","description":"Investigate a production alert, determine root cause, create an issue, implement a fix, and notify the team","entry":"prepare","nodes":{"prepare":{"name":"Load Rules & Context","instruction":"You are preparing for a triage workflow. Your job is to fetch and review any knowledge documents listed in the input.\n\n1. Check input for `rules_urls` and `context_urls` arrays.\n2. For each URL, fetch its content:\n   - Linear document URLs → use the Linear MCP tools (get_document or search_documentation)\n   - Other HTTP URLs → fetch directly\n3. Summarize the key rules and context that downstream workflow nodes should follow.\n4. Output the consolidated information so it's available to all subsequent steps.\n\nIf there are no URLs to fetch, just pass through — this step is a no-op.","skills":["linear"]},"gather":{"name":"Gather Context","instruction":"You are investigating a production alert. Gather all relevant context using the available tools:\n\n1. **Observability**: Pull error details, stack traces, recent logs, metrics, and active incidents around the time of the alert. Use whichever observability tools are available to you.\n2. **Source control**: Check recent commits, pull requests, and deploys that might be related.\n3. **Issue tracker**: Search for similar past issues or known problems.\n\nBe thorough — the investigation step depends on complete context. Use every tool available to you.","skills":["github","sentry","datadog","betterstack","linear"]},"investigate":{"name":"Root Cause Analysis","instruction":"Based on the gathered context, classify every distinct issue you found into one of two buckets: **novel** or **duplicate**.\n\nFor EACH issue found:\n1. Identify the root cause and affected code/service.\n2. Assess severity: critical (service down), high (major feature broken), medium (degraded), low (cosmetic/minor).\n3. Assess fix complexity: \"simple\" (a few lines, clear change), \"moderate\" (multiple files but well-understood), or \"complex\" (architectural, risky, or unclear).\n4. **Novelty check (REQUIRED):** Search the issue tracker for existing issues (BOTH open AND closed) that cover the same root cause, error pattern, or affected service. Use github_search_issues and/or linear_search_issues with multiple keyword variations.\n   - A match = same root cause, same error message/pattern, or a human would call it \"the same bug.\"\n   - If matched → it's a **duplicate**. Record the existing issue ID.\n   - If no match → it's **novel**.\n\n**Output rules:**\n- `findings`: array of ALL issues found (both novel and duplicate).\n- `novel_count`: how many findings are novel (not duplicates).\n- `highest_severity`: the highest severity across ALL findings.\n- `recommendation`: what should happen next.\n\nDownstream nodes will act ONLY on novel findings. Duplicates will be +1'd automatically.","skills":["github","linear"],"output":{"type":"object","properties":{"findings":{"type":"array","items":{"type":"object","properties":{"title":{"type":"string","description":"Short description of the issue"},"root_cause":{"type":"string"},"severity":{"type":"string","enum":["critical","high","medium","low"]},"affected_services":{"type":"array","items":{"type":"string"}},"is_duplicate":{"type":"boolean"},"duplicate_of":{"type":"string","description":"Existing issue ID/URL if duplicate"},"fix_approach":{"type":"string"},"fix_complexity":{"type":"string","enum":["simple","moderate","complex"]}},"required":["title","root_cause","severity","is_duplicate"]}},"novel_count":{"type":"number","description":"Count of novel (non-duplicate) findings"},"highest_severity":{"type":"string","enum":["critical","high","medium","low"]},"recommendation":{"type":"string"}},"required":["findings","novel_count","highest_severity","recommendation"]}},"create_issue":{"name":"Create Issues & Triage Duplicates","instruction":"Process ALL findings from the investigation. The findings array contains both novel and duplicate issues.\n\n**For each NOVEL finding** (is_duplicate = false):\n1. Create a new issue with a clear, actionable title.\n2. Include: root cause, severity, affected services, reproduction steps, and recommended fix.\n3. Add appropriate labels (bug, severity level, affected service).\n4. Link to relevant commits, PRs, or existing issues.\n\n**For each DUPLICATE finding** (is_duplicate = true):\n1. Find the existing issue (check duplicate_of field).\n2. Check the issue's comments — if the most recent comment is already from SWEny (contains \"+1\") within the last 24 hours, skip adding another comment.\n3. Otherwise add a SHORT comment: \"+1 — seen again {UTC timestamp}. {one sentence of new context}.\" (Keep it under 2 lines. No markdown headers, no emoji, no formatting.)\n4. If the existing issue is closed/done, reopen it.\n\nIf context.issueTemplate is provided, use it as the format for new issue bodies. Otherwise use a clear structure with: Summary, Root Cause, Impact, Steps to Reproduce, and Recommended Fix.\n\nUse whichever issue tracker is available to you. Output the created/updated issue identifiers.","skills":["linear","github"]},"skip":{"name":"Skip — All Duplicates or Low Priority","instruction":"Every finding from the investigation was either a duplicate or low-priority. No new issues need to be created.\n\nFor each **duplicate** finding (check the findings array for items where is_duplicate = true):\n1. Find the existing issue (check duplicate_of field).\n2. Check the issue's comments — if the most recent comment is already from SWEny (contains \"+1\") within the last 24 hours, skip adding another comment.\n3. Otherwise add a SHORT comment: \"+1 — seen again {UTC timestamp}. {one sentence of new context}.\" (Keep it under 2 lines. No markdown headers, no emoji, no formatting.)\n4. If the issue is closed/done, reopen it.\n\nFor **low priority** findings, log a brief note about why they were skipped.","skills":["linear","github"]},"implement":{"name":"Implement Fix","instruction":"Implement the fix identified during investigation:\n\n1. Create a feature branch from the base branch (check context for baseBranch, default \"main\").\n2. Read the relevant source files to understand the current code.\n3. Make the necessary code changes — fix the bug, nothing more.\n4. Run any existing tests if available to verify the fix doesn't break anything.\n5. Stage and commit with a clear commit message referencing the issue.\n\nKeep changes minimal and focused. Do not refactor surrounding code or add unrelated improvements.\n\nIf the fix turns out to be more complex than expected, stop and explain why — do not force a bad fix.","skills":["github"]},"create_pr":{"name":"Open Pull Request","instruction":"Open a pull request for the fix:\n\n1. Push the branch to the remote.\n2. Create a PR with a clear title referencing the issue (e.g. \"[OFF-1020] fix: guard empty pdf_texts before access\").\n3. In the PR body, include: summary of the bug, what the fix does, and a link to the issue.\n4. Add appropriate labels if available.\n\nIf context.prTemplate is provided, use it as the format for the PR body. Otherwise use a clear structure with: Summary, Changes, Testing, and Related Issues.\n\nReturn the PR URL and number.","skills":["github"]},"notify":{"name":"Notify Team","instruction":"Send a notification summarizing the triage result:\n\n1. Include: alert summary, severity, root cause (1-2 sentences), and links to any created issues or PRs.\n2. For critical/high severity, make the notification urgent.\n3. For medium/low, a standard notification is fine.\n\nUse whichever notification channel is available to you.","skills":["slack","notification"]}},"edges":[{"from":"prepare","to":"gather"},{"from":"gather","to":"investigate"},{"from":"investigate","to":"create_issue","when":"novel_count is greater than 0 AND highest_severity is medium or higher"},{"from":"investigate","to":"skip","when":"novel_count is 0, OR highest_severity is low"},{"from":"create_issue","to":"implement","when":"at least one novel finding has fix_complexity simple or moderate AND fix_approach is provided"},{"from":"create_issue","to":"notify","when":"all novel findings have fix_complexity complex, OR no clear fix_approach"},{"from":"skip","to":"notify"},{"from":"implement","to":"create_pr"},{"from":"create_pr","to":"notify"}]};
+export const implementWorkflow = {"id":"implement","name":"Implement Fix","description":"Implement a code fix for an issue and open a pull request","entry":"analyze","nodes":{"analyze":{"name":"Analyze Issue","instruction":"Read the issue details and understand what needs to be fixed:\n\n1. Fetch the issue from the tracker (GitHub or Linear).\n2. Read the relevant source files to understand the current code.\n3. Identify the exact files and lines that need to change.\n4. Plan the fix approach.\n\nOutput a clear analysis of what needs to change and why.","skills":["github","linear"],"output":{"type":"object","properties":{"issue_summary":{"type":"string"},"files_to_change":{"type":"array","items":{"type":"string"}},"fix_plan":{"type":"string"},"risk_level":{"type":"string","enum":["low","medium","high"]}},"required":["issue_summary","fix_plan"]}},"implement":{"name":"Implement Fix","instruction":"Implement the planned fix:\n\n1. Create a feature branch.\n2. Make the necessary code changes.\n3. Ensure changes are minimal and focused — fix the bug, nothing more.\n4. Stage and commit with a clear commit message referencing the issue.\n\nIf the fix is too risky or complex, explain why and skip.","skills":["github"]},"create_pr":{"name":"Open Pull Request","instruction":"Open a pull request for the fix:\n\n1. Push the branch to the remote.\n2. Create a PR with a clear title and description.\n3. Reference the original issue in the PR body.\n4. Add appropriate reviewers or labels if possible.\n\nIf context.prTemplate is provided, use it as the format for the PR body. Otherwise use a clear structure with: Summary, Changes, Testing, and Related Issues.\n\nReturn the PR URL.","skills":["github"]},"notify":{"name":"Notify","instruction":"Send a notification about the implementation result:\n\n1. Include: issue reference, PR link, brief summary of changes.\n2. Keep it concise — one message, not a wall of text.","skills":["slack","notification"]},"skip":{"name":"Skip — Too Complex","instruction":"The fix was determined to be too complex or risky for automated implementation.\nAdd a comment to the issue explaining what was found and why it needs manual attention.","skills":["github","linear"]}},"edges":[{"from":"analyze","to":"implement","when":"Fix risk level is low or medium and a clear plan exists"},{"from":"analyze","to":"skip","when":"Fix is too complex, risky, or unclear"},{"from":"implement","to":"create_pr"},{"from":"create_pr","to":"notify"}]};
+export const seedContentWorkflow = {"id":"seed-content","name":"Content Generation Pipeline","description":"Audit content gaps, generate educational content, validate quality, and publish to Supabase","entry":"audit","nodes":{"audit":{"name":"Audit Content Gaps","instruction":"You are auditing an educational platform's content library.\n\nUse supabase_count to check how many items exist for each combination of:\n- Content types: worksheets, games, lessons\n- Subjects: math, science, english, history, geography, economics, music, art, life-skills, foreign-language\n- Difficulties: beginner, easy, medium, hard\n\nAlso check the input parameters — if the user specified a subject, topic, difficulty, and count,\nskip the full audit and just report what they want generated.\n\nReturn a structured content plan: what to generate, how many, at what difficulty and grade level.\nPrioritize gaps where a subject has ZERO content of a given type.","skills":["supabase"],"output":{"type":"object","properties":{"plan":{"type":"array","items":{"type":"object","properties":{"contentType":{"type":"string"},"subject":{"type":"string"},"topic":{"type":"string"},"difficulty":{"type":"string"},"gradeLevel":{"type":"string"},"count":{"type":"number"},"reason":{"type":"string"}},"required":["contentType","subject","topic","difficulty","count"]}},"summary":{"type":"string"}},"required":["plan","summary"]}},"generate":{"name":"Generate Content","instruction":"You are an expert educator creating content for children ages 5-14.\n\nFor each item in the content plan from the previous step, generate the content directly.\nThe content must be high-quality, engaging, age-appropriate, and educationally sound.\n\n**For worksheets:**\nGenerate a JSON array of problems. Each problem needs: \"problem\", \"answer\", \"format\" (answer-line | multiple-choice | write-on).\nRequirements:\n- Every answer MUST be correct. Double-check math, facts, spelling.\n- Problems must progress in difficulty within the set.\n- Use at least 2 different problem structures (e.g., equations + word problems for math).\n- Vary phrasing — no two problems should feel copy-pasted.\n- For the target grade level, use appropriate vocabulary and complexity.\n\n**For lessons:**\nGenerate complete HTML + CSS + JS for an interactive lesson.\nRequirements:\n- Must have substantial educational content (not just a shell with navigation).\n- Include interactive elements: quizzes, click-to-reveal, drag-and-drop.\n- Must be visually engaging with colors, icons, and clear typography.\n- Include practice exercises with immediate feedback.\n- Minimum 5 teaching sections plus 2 practice activities.\n\n**For games:**\nGenerate a description and educational requirements only (actual game code is generated\nby the platform's Phaser-based generator).\n\nUse supabase_insert to write each piece of content to the appropriate table.\n\nTable schemas:\n- worksheets: id (auto), title, subject, topic, difficulty, grade_level, num_questions, problems (jsonb), status='published', source='ai-seed'\n- lessons: id (auto), title, subject, difficulty, grade_level, lesson_type, html_code, css_code, js_code, status='published', source='ai-seed'\n- games: id (auto), title, subject, difficulty, grade_level, game_type, html_code, css_code, js_code, status='published', source='ai-seed'\n\nReturn a summary of what was generated and inserted.","skills":["supabase"],"output":{"type":"object","properties":{"generated":{"type":"array","items":{"type":"object","properties":{"contentType":{"type":"string"},"title":{"type":"string"},"subject":{"type":"string"},"id":{"type":"string"},"status":{"type":"string"}}}},"totalGenerated":{"type":"number"},"errors":{"type":"array","items":{"type":"string"}}},"required":["generated","totalGenerated"]}},"validate":{"name":"Validate Content Quality","instruction":"Review the content that was just generated and inserted.\n\nFor each item, use supabase_query to fetch it back and verify:\n\n**Worksheets:**\n- Parse the problems JSON — are all answers correct?\n- Are problems diverse (not repetitive)?\n- Is difficulty appropriate for the stated grade level?\n- Are there the right number of questions?\n\n**Lessons:**\n- Is the HTML substantial (> 500 characters)?\n- Does it contain actual educational content (not just navigation shells)?\n- Are there interactive elements?\n\n**Games:**\n- Does the HTML contain a working game structure?\n\nFlag any issues. If critical issues are found (wrong answers, empty content),\nuse supabase_update to set status='draft' and add a note.\n\nReturn a quality report.","skills":["supabase"],"output":{"type":"object","properties":{"totalReviewed":{"type":"number"},"passed":{"type":"number"},"flagged":{"type":"number"},"issues":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"title":{"type":"string"},"issue":{"type":"string"},"severity":{"type":"string"},"action":{"type":"string"}}}},"summary":{"type":"string"}},"required":["totalReviewed","passed","flagged","summary"]}},"report":{"name":"Generate Report","instruction":"Compile a final report of the content generation run.\n\nInclude:\n- Total content generated by type and subject\n- Quality validation results\n- Any issues found and actions taken\n- Recommendations for next content generation run (what gaps remain)\n\nFormat as a clean markdown summary that a solo operator can scan in 30 seconds.","skills":[],"output":{"type":"object","properties":{"markdown":{"type":"string"},"nextPriorities":{"type":"array","items":{"type":"string"}}},"required":["markdown"]}}},"edges":[{"from":"audit","to":"generate"},{"from":"generate","to":"validate"},{"from":"validate","to":"report"}]};

package/dist/workflows/implement.yml

@@ -0,0 +1,103 @@
+id: implement
+name: Implement Fix
+description: Implement a code fix for an issue and open a pull request
+entry: analyze
+nodes:
+  analyze:
+    name: Analyze Issue
+    instruction: |-
+      Read the issue details and understand what needs to be fixed:
+
+      1. Fetch the issue from the tracker (GitHub or Linear).
+      2. Read the relevant source files to understand the current code.
+      3. Identify the exact files and lines that need to change.
+      4. Plan the fix approach.
+
+      Output a clear analysis of what needs to change and why.
+    skills:
+      - github
+      - linear
+    output:
+      type: object
+      properties:
+        issue_summary:
+          type: string
+        files_to_change:
+          type: array
+          items:
+            type: string
+        fix_plan:
+          type: string
+        risk_level:
+          type: string
+          enum:
+            - low
+            - medium
+            - high
+      required:
+        - issue_summary
+        - fix_plan
+  implement:
+    name: Implement Fix
+    instruction: |-
+      Implement the planned fix:
+
+      1. Create a feature branch.
+      2. Make the necessary code changes.
+      3. Ensure changes are minimal and focused — fix the bug, nothing more.
+      4. Stage and commit with a clear commit message referencing the issue.
+
+      If the fix is too risky or complex, explain why and skip.
+    skills:
+      - github
+  create_pr:
+    name: Open Pull Request
+    instruction: >-
+      Open a pull request for the fix:
+
+
+      1. Push the branch to the remote.
+
+      2. Create a PR with a clear title and description.
+
+      3. Reference the original issue in the PR body.
+
+      4. Add appropriate reviewers or labels if possible.
+
+
+      If context.prTemplate is provided, use it as the format for the PR body. Otherwise use a clear structure with:
+      Summary, Changes, Testing, and Related Issues.
+
+
+      Return the PR URL.
+    skills:
+      - github
+  notify:
+    name: Notify
+    instruction: |-
+      Send a notification about the implementation result:
+
+      1. Include: issue reference, PR link, brief summary of changes.
+      2. Keep it concise — one message, not a wall of text.
+    skills:
+      - slack
+      - notification
+  skip:
+    name: Skip — Too Complex
+    instruction: |-
+      The fix was determined to be too complex or risky for automated implementation.
+      Add a comment to the issue explaining what was found and why it needs manual attention.
+    skills:
+      - github
+      - linear
+edges:
+  - from: analyze
+    to: implement
+    when: Fix risk level is low or medium and a clear plan exists
+  - from: analyze
+    to: skip
+    when: Fix is too complex, risky, or unclear
+  - from: implement
+    to: create_pr
+  - from: create_pr
+    to: notify

package/dist/workflows/index.d.ts

@@ -1,3 +1,4 @@
-export { triageWorkflow } from "./triage.js";
-export { implementWorkflow } from "./implement.js";
-export { seedContentWorkflow } from "./seed-content.js";
+import type { Workflow } from "../types.js";
+export declare const triageWorkflow: Workflow;
+export declare const implementWorkflow: Workflow;
+export declare const seedContentWorkflow: Workflow;

package/dist/workflows/index.js

@@ -1,3 +1,12 @@
-export { triageWorkflow } from "./triage.js";
-export { implementWorkflow } from "./implement.js";
-export { seedContentWorkflow } from "./seed-content.js";
+import * as fs from "node:fs";
+import * as path from "node:path";
+import { fileURLToPath } from "node:url";
+import { parse as parseYaml } from "yaml";
+const __dirname = path.dirname(fileURLToPath(import.meta.url));
+function loadBuiltinWorkflow(filename) {
+    const filePath = path.join(__dirname, filename);
+    return parseYaml(fs.readFileSync(filePath, "utf-8"));
+}
+export const triageWorkflow = loadBuiltinWorkflow("triage.yml");
+export const implementWorkflow = loadBuiltinWorkflow("implement.yml");
+export const seedContentWorkflow = loadBuiltinWorkflow("seed-content.yml");

package/dist/workflows/seed-content.yml

@@ -0,0 +1,242 @@
+id: seed-content
+name: Content Generation Pipeline
+description: Audit content gaps, generate educational content, validate quality, and publish to Supabase
+entry: audit
+nodes:
+  audit:
+    name: Audit Content Gaps
+    instruction: |-
+      You are auditing an educational platform's content library.
+
+      Use supabase_count to check how many items exist for each combination of:
+      - Content types: worksheets, games, lessons
+      - Subjects: math, science, english, history, geography, economics, music, art, life-skills, foreign-language
+      - Difficulties: beginner, easy, medium, hard
+
+      Also check the input parameters — if the user specified a subject, topic, difficulty, and count,
+      skip the full audit and just report what they want generated.
+
+      Return a structured content plan: what to generate, how many, at what difficulty and grade level.
+      Prioritize gaps where a subject has ZERO content of a given type.
+    skills:
+      - supabase
+    output:
+      type: object
+      properties:
+        plan:
+          type: array
+          items:
+            type: object
+            properties:
+              contentType:
+                type: string
+              subject:
+                type: string
+              topic:
+                type: string
+              difficulty:
+                type: string
+              gradeLevel:
+                type: string
+              count:
+                type: number
+              reason:
+                type: string
+            required:
+              - contentType
+              - subject
+              - topic
+              - difficulty
+              - count
+        summary:
+          type: string
+      required:
+        - plan
+        - summary
+  generate:
+    name: Generate Content
+    instruction: >-
+      You are an expert educator creating content for children ages 5-14.
+
+
+      For each item in the content plan from the previous step, generate the content directly.
+
+      The content must be high-quality, engaging, age-appropriate, and educationally sound.
+
+
+      **For worksheets:**
+
+      Generate a JSON array of problems. Each problem needs: "problem", "answer", "format" (answer-line |
+      multiple-choice | write-on).
+
+      Requirements:
+
+      - Every answer MUST be correct. Double-check math, facts, spelling.
+
+      - Problems must progress in difficulty within the set.
+
+      - Use at least 2 different problem structures (e.g., equations + word problems for math).
+
+      - Vary phrasing — no two problems should feel copy-pasted.
+
+      - For the target grade level, use appropriate vocabulary and complexity.
+
+
+      **For lessons:**
+
+      Generate complete HTML + CSS + JS for an interactive lesson.
+
+      Requirements:
+
+      - Must have substantial educational content (not just a shell with navigation).
+
+      - Include interactive elements: quizzes, click-to-reveal, drag-and-drop.
+
+      - Must be visually engaging with colors, icons, and clear typography.
+
+      - Include practice exercises with immediate feedback.
+
+      - Minimum 5 teaching sections plus 2 practice activities.
+
+
+      **For games:**
+
+      Generate a description and educational requirements only (actual game code is generated
+
+      by the platform's Phaser-based generator).
+
+
+      Use supabase_insert to write each piece of content to the appropriate table.
+
+
+      Table schemas:
+
+      - worksheets: id (auto), title, subject, topic, difficulty, grade_level, num_questions, problems (jsonb),
+      status='published', source='ai-seed'
+
+      - lessons: id (auto), title, subject, difficulty, grade_level, lesson_type, html_code, css_code, js_code,
+      status='published', source='ai-seed'
+
+      - games: id (auto), title, subject, difficulty, grade_level, game_type, html_code, css_code, js_code,
+      status='published', source='ai-seed'
+
+
+      Return a summary of what was generated and inserted.
+    skills:
+      - supabase
+    output:
+      type: object
+      properties:
+        generated:
+          type: array
+          items:
+            type: object
+            properties:
+              contentType:
+                type: string
+              title:
+                type: string
+              subject:
+                type: string
+              id:
+                type: string
+              status:
+                type: string
+        totalGenerated:
+          type: number
+        errors:
+          type: array
+          items:
+            type: string
+      required:
+        - generated
+        - totalGenerated
+  validate:
+    name: Validate Content Quality
+    instruction: |-
+      Review the content that was just generated and inserted.
+
+      For each item, use supabase_query to fetch it back and verify:
+
+      **Worksheets:**
+      - Parse the problems JSON — are all answers correct?
+      - Are problems diverse (not repetitive)?
+      - Is difficulty appropriate for the stated grade level?
+      - Are there the right number of questions?
+
+      **Lessons:**
+      - Is the HTML substantial (> 500 characters)?
+      - Does it contain actual educational content (not just navigation shells)?
+      - Are there interactive elements?
+
+      **Games:**
+      - Does the HTML contain a working game structure?
+
+      Flag any issues. If critical issues are found (wrong answers, empty content),
+      use supabase_update to set status='draft' and add a note.
+
+      Return a quality report.
+    skills:
+      - supabase
+    output:
+      type: object
+      properties:
+        totalReviewed:
+          type: number
+        passed:
+          type: number
+        flagged:
+          type: number
+        issues:
+          type: array
+          items:
+            type: object
+            properties:
+              id:
+                type: string
+              title:
+                type: string
+              issue:
+                type: string
+              severity:
+                type: string
+              action:
+                type: string
+        summary:
+          type: string
+      required:
+        - totalReviewed
+        - passed
+        - flagged
+        - summary
+  report:
+    name: Generate Report
+    instruction: |-
+      Compile a final report of the content generation run.
+
+      Include:
+      - Total content generated by type and subject
+      - Quality validation results
+      - Any issues found and actions taken
+      - Recommendations for next content generation run (what gaps remain)
+
+      Format as a clean markdown summary that a solo operator can scan in 30 seconds.
+    skills: []
+    output:
+      type: object
+      properties:
+        markdown:
+          type: string
+        nextPriorities:
+          type: array
+          items:
+            type: string
+      required:
+        - markdown
+edges:
+  - from: audit
+    to: generate
+  - from: generate
+    to: validate
+  - from: validate
+    to: report

package/dist/workflows/triage.yml

@@ -0,0 +1,279 @@
+id: triage
+name: Alert Triage
+description: Investigate a production alert, determine root cause, create an issue, implement a fix, and notify the team
+entry: prepare
+nodes:
+  prepare:
+    name: Load Rules & Context
+    instruction: >-
+      You are preparing for a triage workflow. Your job is to fetch and review any knowledge documents listed in the
+      input.
+
+
+      1. Check input for `rules_urls` and `context_urls` arrays.
+
+      2. For each URL, fetch its content:
+         - Linear document URLs → use the Linear MCP tools (get_document or search_documentation)
+         - Other HTTP URLs → fetch directly
+      3. Summarize the key rules and context that downstream workflow nodes should follow.
+
+      4. Output the consolidated information so it's available to all subsequent steps.
+
+
+      If there are no URLs to fetch, just pass through — this step is a no-op.
+    skills:
+      - linear
+  gather:
+    name: Gather Context
+    instruction: >-
+      You are investigating a production alert. Gather all relevant context using the available tools:
+
+
+      1. **Observability**: Pull error details, stack traces, recent logs, metrics, and active incidents around the time
+      of the alert. Use whichever observability tools are available to you.
+
+      2. **Source control**: Check recent commits, pull requests, and deploys that might be related.
+
+      3. **Issue tracker**: Search for similar past issues or known problems.
+
+
+      Be thorough — the investigation step depends on complete context. Use every tool available to you.
+    skills:
+      - github
+      - sentry
+      - datadog
+      - betterstack
+      - linear
+  investigate:
+    name: Root Cause Analysis
+    instruction: >-
+      Based on the gathered context, classify every distinct issue you found into one of two buckets: **novel** or
+      **duplicate**.
+
+
+      For EACH issue found:
+
+      1. Identify the root cause and affected code/service.
+
+      2. Assess severity: critical (service down), high (major feature broken), medium (degraded), low (cosmetic/minor).
+
+      3. Assess fix complexity: "simple" (a few lines, clear change), "moderate" (multiple files but well-understood),
+      or "complex" (architectural, risky, or unclear).
+
+      4. **Novelty check (REQUIRED):** Search the issue tracker for existing issues (BOTH open AND closed) that cover
+      the same root cause, error pattern, or affected service. Use github_search_issues and/or linear_search_issues with
+      multiple keyword variations.
+         - A match = same root cause, same error message/pattern, or a human would call it "the same bug."
+         - If matched → it's a **duplicate**. Record the existing issue ID.
+         - If no match → it's **novel**.
+
+      **Output rules:**
+
+      - `findings`: array of ALL issues found (both novel and duplicate).
+
+      - `novel_count`: how many findings are novel (not duplicates).
+
+      - `highest_severity`: the highest severity across ALL findings.
+
+      - `recommendation`: what should happen next.
+
+
+      Downstream nodes will act ONLY on novel findings. Duplicates will be +1'd automatically.
+    skills:
+      - github
+      - linear
+    output:
+      type: object
+      properties:
+        findings:
+          type: array
+          items:
+            type: object
+            properties:
+              title:
+                type: string
+                description: Short description of the issue
+              root_cause:
+                type: string
+              severity:
+                type: string
+                enum:
+                  - critical
+                  - high
+                  - medium
+                  - low
+              affected_services:
+                type: array
+                items:
+                  type: string
+              is_duplicate:
+                type: boolean
+              duplicate_of:
+                type: string
+                description: Existing issue ID/URL if duplicate
+              fix_approach:
+                type: string
+              fix_complexity:
+                type: string
+                enum:
+                  - simple
+                  - moderate
+                  - complex
+            required:
+              - title
+              - root_cause
+              - severity
+              - is_duplicate
+        novel_count:
+          type: number
+          description: Count of novel (non-duplicate) findings
+        highest_severity:
+          type: string
+          enum:
+            - critical
+            - high
+            - medium
+            - low
+        recommendation:
+          type: string
+      required:
+        - findings
+        - novel_count
+        - highest_severity
+        - recommendation
+  create_issue:
+    name: Create Issues & Triage Duplicates
+    instruction: >-
+      Process ALL findings from the investigation. The findings array contains both novel and duplicate issues.
+
+
+      **For each NOVEL finding** (is_duplicate = false):
+
+      1. Create a new issue with a clear, actionable title.
+
+      2. Include: root cause, severity, affected services, reproduction steps, and recommended fix.
+
+      3. Add appropriate labels (bug, severity level, affected service).
+
+      4. Link to relevant commits, PRs, or existing issues.
+
+
+      **For each DUPLICATE finding** (is_duplicate = true):
+
+      1. Find the existing issue (check duplicate_of field).
+
+      2. Check the issue's comments — if the most recent comment is already from SWEny (contains "+1") within the last
+      24 hours, skip adding another comment.
+
+      3. Otherwise add a SHORT comment: "+1 — seen again {UTC timestamp}. {one sentence of new context}." (Keep it under
+      2 lines. No markdown headers, no emoji, no formatting.)
+
+      4. If the existing issue is closed/done, reopen it.
+
+
+      If context.issueTemplate is provided, use it as the format for new issue bodies. Otherwise use a clear structure
+      with: Summary, Root Cause, Impact, Steps to Reproduce, and Recommended Fix.
+
+
+      Use whichever issue tracker is available to you. Output the created/updated issue identifiers.
+    skills:
+      - linear
+      - github
+  skip:
+    name: Skip — All Duplicates or Low Priority
+    instruction: >-
+      Every finding from the investigation was either a duplicate or low-priority. No new issues need to be created.
+
+
+      For each **duplicate** finding (check the findings array for items where is_duplicate = true):
+
+      1. Find the existing issue (check duplicate_of field).
+
+      2. Check the issue's comments — if the most recent comment is already from SWEny (contains "+1") within the last
+      24 hours, skip adding another comment.
+
+      3. Otherwise add a SHORT comment: "+1 — seen again {UTC timestamp}. {one sentence of new context}." (Keep it under
+      2 lines. No markdown headers, no emoji, no formatting.)
+
+      4. If the issue is closed/done, reopen it.
+
+
+      For **low priority** findings, log a brief note about why they were skipped.
+    skills:
+      - linear
+      - github
+  implement:
+    name: Implement Fix
+    instruction: |-
+      Implement the fix identified during investigation:
+
+      1. Create a feature branch from the base branch (check context for baseBranch, default "main").
+      2. Read the relevant source files to understand the current code.
+      3. Make the necessary code changes — fix the bug, nothing more.
+      4. Run any existing tests if available to verify the fix doesn't break anything.
+      5. Stage and commit with a clear commit message referencing the issue.
+
+      Keep changes minimal and focused. Do not refactor surrounding code or add unrelated improvements.
+
+      If the fix turns out to be more complex than expected, stop and explain why — do not force a bad fix.
+    skills:
+      - github
+  create_pr:
+    name: Open Pull Request
+    instruction: >-
+      Open a pull request for the fix:
+
+
+      1. Push the branch to the remote.
+
+      2. Create a PR with a clear title referencing the issue (e.g. "[OFF-1020] fix: guard empty pdf_texts before
+      access").
+
+      3. In the PR body, include: summary of the bug, what the fix does, and a link to the issue.
+
+      4. Add appropriate labels if available.
+
+
+      If context.prTemplate is provided, use it as the format for the PR body. Otherwise use a clear structure with:
+      Summary, Changes, Testing, and Related Issues.
+
+
+      Return the PR URL and number.
+    skills:
+      - github
+  notify:
+    name: Notify Team
+    instruction: |-
+      Send a notification summarizing the triage result:
+
+      1. Include: alert summary, severity, root cause (1-2 sentences), and links to any created issues or PRs.
+      2. For critical/high severity, make the notification urgent.
+      3. For medium/low, a standard notification is fine.
+
+      Use whichever notification channel is available to you.
+    skills:
+      - slack
+      - notification
+edges:
+  - from: prepare
+    to: gather
+  - from: gather
+    to: investigate
+  - from: investigate
+    to: create_issue
+    when: novel_count is greater than 0 AND highest_severity is medium or higher
+  - from: investigate
+    to: skip
+    when: novel_count is 0, OR highest_severity is low
+  - from: create_issue
+    to: implement
+    when: at least one novel finding has fix_complexity simple or moderate AND fix_approach is provided
+  - from: create_issue
+    to: notify
+    when: all novel findings have fix_complexity complex, OR no clear fix_approach
+  - from: skip
+    to: notify
+  - from: implement
+    to: create_pr
+  - from: create_pr
+    to: notify

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sweny-ai/core",
-  "version": "0.1.14",
+  "version": "0.1.16",
   "type": "module",
   "bin": {
     "sweny": "./dist/cli/main.js"
@@ -42,7 +42,7 @@
     "dist"
   ],
   "scripts": {
-    "build": "tsc",
+    "build": "tsc && cp src/workflows/*.yml dist/workflows/ && node scripts/build-workflow-browser.mjs",
     "typecheck": "tsc --noEmit",
     "test": "vitest run --exclude 'src/__tests__/integration/**'",
     "test:integration": "vitest run --config vitest.integration.config.ts"

package/dist/workflows/implement.d.ts

@@ -1,11 +0,0 @@
-/**
- * Implement Workflow
- *
- * Given an issue, implement a fix and open a pull request.
- *
- * Compare: the previous version was 8 files, ~2000 lines.
- * This version is a DAG definition — Claude does the implementation
- * work at each node using the available skill tools.
- */
-import type { Workflow } from "../types.js";
-export declare const implementWorkflow: Workflow;

package/dist/workflows/implement.js

@@ -1,85 +0,0 @@
-/**
- * Implement Workflow
- *
- * Given an issue, implement a fix and open a pull request.
- *
- * Compare: the previous version was 8 files, ~2000 lines.
- * This version is a DAG definition — Claude does the implementation
- * work at each node using the available skill tools.
- */
-export const implementWorkflow = {
-    id: "implement",
-    name: "Implement Fix",
-    description: "Implement a code fix for an issue and open a pull request",
-    entry: "analyze",
-    nodes: {
-        analyze: {
-            name: "Analyze Issue",
-            instruction: `Read the issue details and understand what needs to be fixed:
-
-1. Fetch the issue from the tracker (GitHub or Linear).
-2. Read the relevant source files to understand the current code.
-3. Identify the exact files and lines that need to change.
-4. Plan the fix approach.
-
-Output a clear analysis of what needs to change and why.`,
-            skills: ["github", "linear"],
-            output: {
-                type: "object",
-                properties: {
-                    issue_summary: { type: "string" },
-                    files_to_change: { type: "array", items: { type: "string" } },
-                    fix_plan: { type: "string" },
-                    risk_level: { type: "string", enum: ["low", "medium", "high"] },
-                },
-                required: ["issue_summary", "fix_plan"],
-            },
-        },
-        implement: {
-            name: "Implement Fix",
-            instruction: `Implement the planned fix:
-
-1. Create a feature branch.
-2. Make the necessary code changes.
-3. Ensure changes are minimal and focused — fix the bug, nothing more.
-4. Stage and commit with a clear commit message referencing the issue.
-
-If the fix is too risky or complex, explain why and skip.`,
-            skills: ["github"],
-        },
-        create_pr: {
-            name: "Open Pull Request",
-            instruction: `Open a pull request for the fix:
-
-1. Push the branch to the remote.
-2. Create a PR with a clear title and description.
-3. Reference the original issue in the PR body.
-4. Add appropriate reviewers or labels if possible.
-
-If context.prTemplate is provided, use it as the format for the PR body. Otherwise use a clear structure with: Summary, Changes, Testing, and Related Issues.
-
-Return the PR URL.`,
-            skills: ["github"],
-        },
-        notify: {
-            name: "Notify",
-            instruction: `Send a notification about the implementation result:
-
-1. Include: issue reference, PR link, brief summary of changes.
-2. Keep it concise — one message, not a wall of text.`,
-            skills: ["slack", "notification"],
-        },
-        skip: {
-            name: "Skip — Too Complex",
-            instruction: `The fix was determined to be too complex or risky for automated implementation.
-Add a comment to the issue explaining what was found and why it needs manual attention.`,
-            skills: ["github", "linear"],
-        },
-    },
-    edges: [
-        { from: "analyze", to: "implement", when: "Fix risk level is low or medium and a clear plan exists" },
-        { from: "analyze", to: "skip", when: "Fix is too complex, risky, or unclear" },
-        { from: "implement", to: "create_pr" },
-        { from: "create_pr", to: "notify" },
-    ],
-};

package/dist/workflows/seed-content.d.ts

@@ -1,30 +0,0 @@
-/**
- * Content Generation Workflow
- *
- * A DAG that audits a Supabase-backed educational platform for content gaps,
- * generates high-quality content using Claude, validates it, and publishes it.
- *
- * Designed for solo operators bootstrapping educational SaaS platforms.
- * Uses Claude (via your existing subscription) for generation instead of
- * burning API credits on external AI gateways.
- *
- * @example
- * ```ts
- * import { execute, ClaudeClient, createSkillMap, supabase } from '@sweny-ai/core'
- * import { seedContentWorkflow } from '@sweny-ai/core/workflows'
- *
- * const skills = createSkillMap([supabase])
- * const claude = new ClaudeClient()
- *
- * const results = await execute(seedContentWorkflow, {
- *   contentType: 'worksheet',           // 'worksheet' | 'game' | 'lesson'
- *   subject: 'math',
- *   topic: 'fractions',
- *   difficulty: 'easy',
- *   gradeLevel: '3rd-grade',
- *   count: 5,
- * }, { skills, claude })
- * ```
- */
-import type { Workflow } from "../types.js";
-export declare const seedContentWorkflow: Workflow;

package/dist/workflows/seed-content.js

@@ -1,217 +0,0 @@
-/**
- * Content Generation Workflow
- *
- * A DAG that audits a Supabase-backed educational platform for content gaps,
- * generates high-quality content using Claude, validates it, and publishes it.
- *
- * Designed for solo operators bootstrapping educational SaaS platforms.
- * Uses Claude (via your existing subscription) for generation instead of
- * burning API credits on external AI gateways.
- *
- * @example
- * ```ts
- * import { execute, ClaudeClient, createSkillMap, supabase } from '@sweny-ai/core'
- * import { seedContentWorkflow } from '@sweny-ai/core/workflows'
- *
- * const skills = createSkillMap([supabase])
- * const claude = new ClaudeClient()
- *
- * const results = await execute(seedContentWorkflow, {
- *   contentType: 'worksheet',           // 'worksheet' | 'game' | 'lesson'
- *   subject: 'math',
- *   topic: 'fractions',
- *   difficulty: 'easy',
- *   gradeLevel: '3rd-grade',
- *   count: 5,
- * }, { skills, claude })
- * ```
- */
-export const seedContentWorkflow = {
-    id: "seed-content",
-    name: "Content Generation Pipeline",
-    description: "Audit content gaps, generate educational content, validate quality, and publish to Supabase",
-    entry: "audit",
-    nodes: {
-        // ─── Step 1: Audit ─────────────────────────────────────
-        audit: {
-            name: "Audit Content Gaps",
-            instruction: `You are auditing an educational platform's content library.
-
-Use supabase_count to check how many items exist for each combination of:
-- Content types: worksheets, games, lessons
-- Subjects: math, science, english, history, geography, economics, music, art, life-skills, foreign-language
-- Difficulties: beginner, easy, medium, hard
-
-Also check the input parameters — if the user specified a subject, topic, difficulty, and count,
-skip the full audit and just report what they want generated.
-
-Return a structured content plan: what to generate, how many, at what difficulty and grade level.
-Prioritize gaps where a subject has ZERO content of a given type.`,
-            skills: ["supabase"],
-            output: {
-                type: "object",
-                properties: {
-                    plan: {
-                        type: "array",
-                        items: {
-                            type: "object",
-                            properties: {
-                                contentType: { type: "string" },
-                                subject: { type: "string" },
-                                topic: { type: "string" },
-                                difficulty: { type: "string" },
-                                gradeLevel: { type: "string" },
-                                count: { type: "number" },
-                                reason: { type: "string" },
-                            },
-                            required: ["contentType", "subject", "topic", "difficulty", "count"],
-                        },
-                    },
-                    summary: { type: "string" },
-                },
-                required: ["plan", "summary"],
-            },
-        },
-        // ─── Step 2: Generate ──────────────────────────────────
-        generate: {
-            name: "Generate Content",
-            instruction: `You are an expert educator creating content for children ages 5-14.
-
-For each item in the content plan from the previous step, generate the content directly.
-The content must be high-quality, engaging, age-appropriate, and educationally sound.
-
-**For worksheets:**
-Generate a JSON array of problems. Each problem needs: "problem", "answer", "format" (answer-line | multiple-choice | write-on).
-Requirements:
-- Every answer MUST be correct. Double-check math, facts, spelling.
-- Problems must progress in difficulty within the set.
-- Use at least 2 different problem structures (e.g., equations + word problems for math).
-- Vary phrasing — no two problems should feel copy-pasted.
-- For the target grade level, use appropriate vocabulary and complexity.
-
-**For lessons:**
-Generate complete HTML + CSS + JS for an interactive lesson.
-Requirements:
-- Must have substantial educational content (not just a shell with navigation).
-- Include interactive elements: quizzes, click-to-reveal, drag-and-drop.
-- Must be visually engaging with colors, icons, and clear typography.
-- Include practice exercises with immediate feedback.
-- Minimum 5 teaching sections plus 2 practice activities.
-
-**For games:**
-Generate a description and educational requirements only (actual game code is generated
-by the platform's Phaser-based generator).
-
-Use supabase_insert to write each piece of content to the appropriate table.
-
-Table schemas:
-- worksheets: id (auto), title, subject, topic, difficulty, grade_level, num_questions, problems (jsonb), status='published', source='ai-seed'
-- lessons: id (auto), title, subject, difficulty, grade_level, lesson_type, html_code, css_code, js_code, status='published', source='ai-seed'
-- games: id (auto), title, subject, difficulty, grade_level, game_type, html_code, css_code, js_code, status='published', source='ai-seed'
-
-Return a summary of what was generated and inserted.`,
-            skills: ["supabase"],
-            output: {
-                type: "object",
-                properties: {
-                    generated: {
-                        type: "array",
-                        items: {
-                            type: "object",
-                            properties: {
-                                contentType: { type: "string" },
-                                title: { type: "string" },
-                                subject: { type: "string" },
-                                id: { type: "string" },
-                                status: { type: "string" },
-                            },
-                        },
-                    },
-                    totalGenerated: { type: "number" },
-                    errors: { type: "array", items: { type: "string" } },
-                },
-                required: ["generated", "totalGenerated"],
-            },
-        },
-        // ─── Step 3: Validate ──────────────────────────────────
-        validate: {
-            name: "Validate Content Quality",
-            instruction: `Review the content that was just generated and inserted.
-
-For each item, use supabase_query to fetch it back and verify:
-
-**Worksheets:**
-- Parse the problems JSON — are all answers correct?
-- Are problems diverse (not repetitive)?
-- Is difficulty appropriate for the stated grade level?
-- Are there the right number of questions?
-
-**Lessons:**
-- Is the HTML substantial (> 500 characters)?
-- Does it contain actual educational content (not just navigation shells)?
-- Are there interactive elements?
-
-**Games:**
-- Does the HTML contain a working game structure?
-
-Flag any issues. If critical issues are found (wrong answers, empty content),
-use supabase_update to set status='draft' and add a note.
-
-Return a quality report.`,
-            skills: ["supabase"],
-            output: {
-                type: "object",
-                properties: {
-                    totalReviewed: { type: "number" },
-                    passed: { type: "number" },
-                    flagged: { type: "number" },
-                    issues: {
-                        type: "array",
-                        items: {
-                            type: "object",
-                            properties: {
-                                id: { type: "string" },
-                                title: { type: "string" },
-                                issue: { type: "string" },
-                                severity: { type: "string" },
-                                action: { type: "string" },
-                            },
-                        },
-                    },
-                    summary: { type: "string" },
-                },
-                required: ["totalReviewed", "passed", "flagged", "summary"],
-            },
-        },
-        // ─── Step 4: Report ────────────────────────────────────
-        report: {
-            name: "Generate Report",
-            instruction: `Compile a final report of the content generation run.
-
-Include:
-- Total content generated by type and subject
-- Quality validation results
-- Any issues found and actions taken
-- Recommendations for next content generation run (what gaps remain)
-
-Format as a clean markdown summary that a solo operator can scan in 30 seconds.`,
-            skills: [],
-            output: {
-                type: "object",
-                properties: {
-                    markdown: { type: "string" },
-                    nextPriorities: {
-                        type: "array",
-                        items: { type: "string" },
-                    },
-                },
-                required: ["markdown"],
-            },
-        },
-    },
-    edges: [
-        { from: "audit", to: "generate" },
-        { from: "generate", to: "validate" },
-        { from: "validate", to: "report" },
-    ],
-};

package/dist/workflows/triage.d.ts

@@ -1,18 +0,0 @@
-/**
- * Triage Workflow
- *
- * Investigate a production alert → gather context → determine root cause →
- * create/update issue → implement fix → open PR → notify team.
- *
- * Provider-agnostic: nodes list all compatible skills per category.
- * The executor uses whichever skills are configured. Pre-execution
- * validation ensures required categories have at least one provider.
- *
- * Categories used:
- *   git:            github (+ bitbucket, gitlab in future)
- *   observability:  sentry, datadog, betterstack (+ aws, pagerduty in future)
- *   tasks:          linear, github (issues) (+ jira in future)
- *   notification:   slack, notification (discord/teams/webhook)
- */
-import type { Workflow } from "../types.js";
-export declare const triageWorkflow: Workflow;

package/dist/workflows/triage.js

@@ -1,207 +0,0 @@
-/**
- * Triage Workflow
- *
- * Investigate a production alert → gather context → determine root cause →
- * create/update issue → implement fix → open PR → notify team.
- *
- * Provider-agnostic: nodes list all compatible skills per category.
- * The executor uses whichever skills are configured. Pre-execution
- * validation ensures required categories have at least one provider.
- *
- * Categories used:
- *   git:            github (+ bitbucket, gitlab in future)
- *   observability:  sentry, datadog, betterstack (+ aws, pagerduty in future)
- *   tasks:          linear, github (issues) (+ jira in future)
- *   notification:   slack, notification (discord/teams/webhook)
- */
-export const triageWorkflow = {
-    id: "triage",
-    name: "Alert Triage",
-    description: "Investigate a production alert, determine root cause, create an issue, implement a fix, and notify the team",
-    entry: "prepare",
-    nodes: {
-        prepare: {
-            name: "Load Rules & Context",
-            instruction: `You are preparing for a triage workflow. Your job is to fetch and review any knowledge documents listed in the input.
-
-1. Check input for \`rules_urls\` and \`context_urls\` arrays.
-2. For each URL, fetch its content:
-   - Linear document URLs → use the Linear MCP tools (get_document or search_documentation)
-   - Other HTTP URLs → fetch directly
-3. Summarize the key rules and context that downstream workflow nodes should follow.
-4. Output the consolidated information so it's available to all subsequent steps.
-
-If there are no URLs to fetch, just pass through — this step is a no-op.`,
-            skills: ["linear"],
-        },
-        gather: {
-            name: "Gather Context",
-            instruction: `You are investigating a production alert. Gather all relevant context using the available tools:
-
-1. **Observability**: Pull error details, stack traces, recent logs, metrics, and active incidents around the time of the alert. Use whichever observability tools are available to you.
-2. **Source control**: Check recent commits, pull requests, and deploys that might be related.
-3. **Issue tracker**: Search for similar past issues or known problems.
-
-Be thorough — the investigation step depends on complete context. Use every tool available to you.`,
-            skills: ["github", "sentry", "datadog", "betterstack", "linear"],
-        },
-        investigate: {
-            name: "Root Cause Analysis",
-            instruction: `Based on the gathered context, classify every distinct issue you found into one of two buckets: **novel** or **duplicate**.
-
-For EACH issue found:
-1. Identify the root cause and affected code/service.
-2. Assess severity: critical (service down), high (major feature broken), medium (degraded), low (cosmetic/minor).
-3. Assess fix complexity: "simple" (a few lines, clear change), "moderate" (multiple files but well-understood), or "complex" (architectural, risky, or unclear).
-4. **Novelty check (REQUIRED):** Search the issue tracker for existing issues (BOTH open AND closed) that cover the same root cause, error pattern, or affected service. Use github_search_issues and/or linear_search_issues with multiple keyword variations.
-   - A match = same root cause, same error message/pattern, or a human would call it "the same bug."
-   - If matched → it's a **duplicate**. Record the existing issue ID.
-   - If no match → it's **novel**.
-
-**Output rules:**
-- \`findings\`: array of ALL issues found (both novel and duplicate).
-- \`novel_count\`: how many findings are novel (not duplicates).
-- \`highest_severity\`: the highest severity across ALL findings.
-- \`recommendation\`: what should happen next.
-
-Downstream nodes will act ONLY on novel findings. Duplicates will be +1'd automatically.`,
-            skills: ["github", "linear"],
-            output: {
-                type: "object",
-                properties: {
-                    findings: {
-                        type: "array",
-                        items: {
-                            type: "object",
-                            properties: {
-                                title: { type: "string", description: "Short description of the issue" },
-                                root_cause: { type: "string" },
-                                severity: { type: "string", enum: ["critical", "high", "medium", "low"] },
-                                affected_services: { type: "array", items: { type: "string" } },
-                                is_duplicate: { type: "boolean" },
-                                duplicate_of: { type: "string", description: "Existing issue ID/URL if duplicate" },
-                                fix_approach: { type: "string" },
-                                fix_complexity: { type: "string", enum: ["simple", "moderate", "complex"] },
-                            },
-                            required: ["title", "root_cause", "severity", "is_duplicate"],
-                        },
-                    },
-                    novel_count: { type: "number", description: "Count of novel (non-duplicate) findings" },
-                    highest_severity: { type: "string", enum: ["critical", "high", "medium", "low"] },
-                    recommendation: { type: "string" },
-                },
-                required: ["findings", "novel_count", "highest_severity", "recommendation"],
-            },
-        },
-        create_issue: {
-            name: "Create Issues & Triage Duplicates",
-            instruction: `Process ALL findings from the investigation. The findings array contains both novel and duplicate issues.
-
-**For each NOVEL finding** (is_duplicate = false):
-1. Create a new issue with a clear, actionable title.
-2. Include: root cause, severity, affected services, reproduction steps, and recommended fix.
-3. Add appropriate labels (bug, severity level, affected service).
-4. Link to relevant commits, PRs, or existing issues.
-
-**For each DUPLICATE finding** (is_duplicate = true):
-1. Find the existing issue (check duplicate_of field).
-2. Check the issue's comments — if the most recent comment is already from SWEny (contains "+1") within the last 24 hours, skip adding another comment.
-3. Otherwise add a SHORT comment: "+1 — seen again {UTC timestamp}. {one sentence of new context}." (Keep it under 2 lines. No markdown headers, no emoji, no formatting.)
-4. If the existing issue is closed/done, reopen it.
-
-If context.issueTemplate is provided, use it as the format for new issue bodies. Otherwise use a clear structure with: Summary, Root Cause, Impact, Steps to Reproduce, and Recommended Fix.
-
-Use whichever issue tracker is available to you. Output the created/updated issue identifiers.`,
-            skills: ["linear", "github"],
-        },
-        skip: {
-            name: "Skip — All Duplicates or Low Priority",
-            instruction: `Every finding from the investigation was either a duplicate or low-priority. No new issues need to be created.
-
-For each **duplicate** finding (check the findings array for items where is_duplicate = true):
-1. Find the existing issue (check duplicate_of field).
-2. Check the issue's comments — if the most recent comment is already from SWEny (contains "+1") within the last 24 hours, skip adding another comment.
-3. Otherwise add a SHORT comment: "+1 — seen again {UTC timestamp}. {one sentence of new context}." (Keep it under 2 lines. No markdown headers, no emoji, no formatting.)
-4. If the issue is closed/done, reopen it.
-
-For **low priority** findings, log a brief note about why they were skipped.`,
-            skills: ["linear", "github"],
-        },
-        implement: {
-            name: "Implement Fix",
-            instruction: `Implement the fix identified during investigation:
-
-1. Create a feature branch from the base branch (check context for baseBranch, default "main").
-2. Read the relevant source files to understand the current code.
-3. Make the necessary code changes — fix the bug, nothing more.
-4. Run any existing tests if available to verify the fix doesn't break anything.
-5. Stage and commit with a clear commit message referencing the issue.
-
-Keep changes minimal and focused. Do not refactor surrounding code or add unrelated improvements.
-
-If the fix turns out to be more complex than expected, stop and explain why — do not force a bad fix.`,
-            skills: ["github"],
-        },
-        create_pr: {
-            name: "Open Pull Request",
-            instruction: `Open a pull request for the fix:
-
-1. Push the branch to the remote.
-2. Create a PR with a clear title referencing the issue (e.g. "[OFF-1020] fix: guard empty pdf_texts before access").
-3. In the PR body, include: summary of the bug, what the fix does, and a link to the issue.
-4. Add appropriate labels if available.
-
-If context.prTemplate is provided, use it as the format for the PR body. Otherwise use a clear structure with: Summary, Changes, Testing, and Related Issues.
-
-Return the PR URL and number.`,
-            skills: ["github"],
-        },
-        notify: {
-            name: "Notify Team",
-            instruction: `Send a notification summarizing the triage result:
-
-1. Include: alert summary, severity, root cause (1-2 sentences), and links to any created issues or PRs.
-2. For critical/high severity, make the notification urgent.
-3. For medium/low, a standard notification is fine.
-
-Use whichever notification channel is available to you.`,
-            skills: ["slack", "notification"],
-        },
-    },
-    edges: [
-        // prepare → gather (always)
-        { from: "prepare", to: "gather" },
-        // gather → investigate (always)
-        { from: "gather", to: "investigate" },
-        // investigate → create_issue (novel findings worth acting on)
-        {
-            from: "investigate",
-            to: "create_issue",
-            when: "novel_count is greater than 0 AND highest_severity is medium or higher",
-        },
-        // investigate → skip (everything is a duplicate or low priority)
-        {
-            from: "investigate",
-            to: "skip",
-            when: "novel_count is 0, OR highest_severity is low",
-        },
-        // create_issue → implement (novel findings have a clear, feasible fix)
-        {
-            from: "create_issue",
-            to: "implement",
-            when: "at least one novel finding has fix_complexity simple or moderate AND fix_approach is provided",
-        },
-        // create_issue → notify (fixes too complex)
-        {
-            from: "create_issue",
-            to: "notify",
-            when: "all novel findings have fix_complexity complex, OR no clear fix_approach",
-        },
-        // skip → notify (nothing to implement — all duplicates +1'd or low priority)
-        { from: "skip", to: "notify" },
-        // implement → create_pr (always after successful implementation)
-        { from: "implement", to: "create_pr" },
-        // create_pr → notify (always)
-        { from: "create_pr", to: "notify" },
-    ],
-};