@sweny-ai/core 0.1.69 → 0.1.71

package/dist/__tests__/executor.test.js

@@ -448,4 +448,94 @@ describe("executor", () => {
         // Should still complete — falls back to first valid edge target
         expect(results.size).toBe(2);
     });
+    describe("node.verify", () => {
+        // Context: a create_issue node can satisfy its output schema (issueIdentifier
+        // present) while never actually calling the Linear/GitHub create-issue tool.
+        // The verify block catches this by requiring a real, successful tool call.
+        const verifyWorkflow = {
+            id: "verify-create-issue",
+            name: "Verify Create Issue",
+            description: "Single node that must call linear_create_issue",
+            entry: "create",
+            nodes: {
+                create: {
+                    name: "Create",
+                    instruction: "Create an issue",
+                    skills: [],
+                    verify: { any_tool_called: ["linear_create_issue", "github_create_issue"] },
+                },
+            },
+            edges: [],
+        };
+        it("marks node failed when required tool was never called", async () => {
+            const claude = {
+                async run() {
+                    return {
+                        status: "success",
+                        data: { issueIdentifier: "OFF-9999", issueTitle: "hallucinated", issueUrl: "https://" },
+                        toolCalls: [{ tool: "linear_search_issues", input: {}, output: [] }],
+                    };
+                },
+                async evaluate(opts) {
+                    return opts.choices[0]?.id;
+                },
+            };
+            const { results } = await execute(verifyWorkflow, {}, { skills: createSkillMap([]), claude, config: {} });
+            const r = results.get("create");
+            expect(r.status).toBe("failed");
+            expect(r.data.error).toMatch(/verify\.any_tool_called failed/);
+            expect(r.data.error).toMatch(/linear_create_issue/);
+        });
+        it("marks node failed when required tool erred (output.error set)", async () => {
+            const claude = {
+                async run() {
+                    return {
+                        status: "success",
+                        data: { issueIdentifier: "OFF-9999" },
+                        toolCalls: [{ tool: "linear_create_issue", input: {}, output: { error: "Linear API 403" } }],
+                    };
+                },
+                async evaluate(opts) {
+                    return opts.choices[0]?.id;
+                },
+            };
+            const { results } = await execute(verifyWorkflow, {}, { skills: createSkillMap([]), claude, config: {} });
+            expect(results.get("create").status).toBe("failed");
+        });
+        it("passes when a required tool was invoked successfully", async () => {
+            const claude = {
+                async run() {
+                    return {
+                        status: "success",
+                        data: { issueIdentifier: "OFF-1234" },
+                        toolCalls: [
+                            {
+                                tool: "linear_create_issue",
+                                input: { title: "t" },
+                                output: { issueCreate: { success: true, issue: { identifier: "OFF-1234" } } },
+                            },
+                        ],
+                    };
+                },
+                async evaluate(opts) {
+                    return opts.choices[0]?.id;
+                },
+            };
+            const { results } = await execute(verifyWorkflow, {}, { skills: createSkillMap([]), claude, config: {} });
+            expect(results.get("create").status).toBe("success");
+        });
+        it("leaves already-failed nodes alone (does not overwrite Claude errors)", async () => {
+            const claude = {
+                async run() {
+                    return { status: "failed", data: { error: "max_turns" }, toolCalls: [] };
+                },
+                async evaluate(opts) {
+                    return opts.choices[0]?.id;
+                },
+            };
+            const { results } = await execute(verifyWorkflow, {}, { skills: createSkillMap([]), claude, config: {} });
+            expect(results.get("create").status).toBe("failed");
+            expect(results.get("create").data.error).toBe("max_turns");
+        });
+    });
 });

package/dist/__tests__/schema.test.js

@@ -43,6 +43,20 @@ describe("Zod schemas", () => {
             });
             expect(result.output).toBeDefined();
         });
+        it("accepts a verify block with any_tool_called", () => {
+            const result = nodeZ.parse({
+                name: "S",
+                instruction: "I",
+                verify: { any_tool_called: ["linear_create_issue", "github_create_issue"] },
+            });
+            expect(result.verify?.any_tool_called).toEqual(["linear_create_issue", "github_create_issue"]);
+        });
+        it("rejects verify with no check declared", () => {
+            expect(() => nodeZ.parse({ name: "S", instruction: "I", verify: {} })).toThrow();
+        });
+        it("rejects verify with empty any_tool_called", () => {
+            expect(() => nodeZ.parse({ name: "S", instruction: "I", verify: { any_tool_called: [] } })).toThrow();
+        });
     });
     describe("edgeZ", () => {
         it("parses a simple edge", () => {

package/dist/__tests__/skills.test.js

@@ -93,7 +93,14 @@ describe("github skill", () => {
 describe("linear skill", () => {
     const ctx = () => mockCtx({ LINEAR_API_KEY: "lin_test" });
     it("create_issue sends correct GraphQL mutation", async () => {
-        fetchMock.mockResolvedValueOnce(mockResponse({ data: { issueCreate: { success: true, issue: { id: "1" } } } }));
+        fetchMock.mockResolvedValueOnce(mockResponse({
+            data: {
+                issueCreate: {
+                    success: true,
+                    issue: { id: "1", identifier: "TEST-1", url: "https://linear.app/test/issue/TEST-1", title: "Bug" },
+                },
+            },
+        }));
         const tool = findTool(linear.tools, "linear_create_issue");
         await tool.handler({ teamId: "team1", title: "Bug" }, ctx());
         const [url, opts] = fetchMock.mock.calls[0];
@@ -102,6 +109,16 @@ describe("linear skill", () => {
         const body = JSON.parse(opts.body);
         expect(body.query).toContain("issueCreate");
     });
+    it("throws when issueCreate returns no identifier (silent failure guard)", async () => {
+        fetchMock.mockResolvedValueOnce(mockResponse({ data: { issueCreate: { success: true, issue: { id: "1" } } } }));
+        const tool = findTool(linear.tools, "linear_create_issue");
+        await expect(tool.handler({ teamId: "team1", title: "Bug" }, ctx())).rejects.toThrow(/linear_create_issue returned no identifier/);
+    });
+    it("throws when issueCreate returns success: false", async () => {
+        fetchMock.mockResolvedValueOnce(mockResponse({ data: { issueCreate: { success: false } } }));
+        const tool = findTool(linear.tools, "linear_create_issue");
+        await expect(tool.handler({ teamId: "team1", title: "Bug" }, ctx())).rejects.toThrow(/linear_create_issue returned no identifier/);
+    });
     it("search_issues sends correct query", async () => {
         fetchMock.mockResolvedValueOnce(mockResponse({ data: { searchIssues: { nodes: [] } } }));
         const tool = findTool(linear.tools, "linear_search_issues");

package/dist/executor.js

@@ -121,6 +121,15 @@ export async function execute(workflow, input, options) {
                 safeObserve(observer, { type: "node:progress", node: currentId, message }, logger);
             },
         });
+        // Machine-checked post-condition. Enforced AFTER the LLM finishes so that
+        // a model claiming success cannot bypass side-effect requirements (e.g.
+        // reporting "issue created" when no `linear_create_issue` call was made).
+        const verifyError = evaluateVerify(node.verify, result);
+        if (verifyError && result.status === "success") {
+            result.status = "failed";
+            result.data = { ...result.data, error: verifyError };
+            logger.warn(`  verify failed: ${verifyError}`, { node: currentId });
+        }
         results.set(currentId, result);
         trace.steps.push({ node: currentId, status: result.status, iteration });
         safeObserve(observer, { type: "node:exit", node: currentId, result }, logger);
@@ -155,6 +164,31 @@ export async function execute(workflow, input, options) {
     return { results, trace };
 }
 // ─── Internals ───────────────────────────────────────────────────
+/**
+ * Evaluate a node's `verify` post-condition against the executed result.
+ *
+ * Returns an error string when the check fails, or null when the node
+ * passes verification (or has no verify block).
+ *
+ * Keep this deterministic and side-effect free — the executor calls it
+ * synchronously right after the LLM finishes.
+ */
+function evaluateVerify(verify, result) {
+    if (!verify)
+        return null;
+    if (verify.any_tool_called && verify.any_tool_called.length > 0) {
+        const required = new Set(verify.any_tool_called);
+        const success = result.toolCalls.some((c) => required.has(c.tool) &&
+            // Treat explicit error outputs (from coreToolToSdkTool's catch branch)
+            // as failed calls so a swallowed handler throw doesn't count as success.
+            !(c.output && typeof c.output === "object" && "error" in c.output));
+        if (!success) {
+            const called = result.toolCalls.map((c) => c.tool).join(", ") || "none";
+            return `verify.any_tool_called failed — required one of [${verify.any_tool_called.join(", ")}] to succeed, but tool calls were: [${called}]`;
+        }
+    }
+    return null;
+}
 /**
  * Build the full instruction for a node.
  *

package/dist/schema.d.ts

@@ -404,6 +404,17 @@ export declare const nodeSourcesZ: z.ZodUnion<[z.ZodArray<z.ZodUnion<[z.ZodStrin
     })[];
     only?: boolean | undefined;
 }>]>;
+export declare const nodeVerifyZ: z.ZodEffects<z.ZodObject<{
+    any_tool_called: z.ZodOptional<z.ZodArray<z.ZodString, "many">>;
+}, "strip", z.ZodTypeAny, {
+    any_tool_called?: string[] | undefined;
+}, {
+    any_tool_called?: string[] | undefined;
+}>, {
+    any_tool_called?: string[] | undefined;
+}, {
+    any_tool_called?: string[] | undefined;
+}>;
 export declare const nodeZ: z.ZodObject<{
     name: z.ZodString;
     instruction: z.ZodUnion<[z.ZodString, z.ZodObject<{
@@ -563,6 +574,17 @@ export declare const nodeZ: z.ZodObject<{
         })[];
         only?: boolean | undefined;
     }>]>>;
+    verify: z.ZodOptional<z.ZodEffects<z.ZodObject<{
+        any_tool_called: z.ZodOptional<z.ZodArray<z.ZodString, "many">>;
+    }, "strip", z.ZodTypeAny, {
+        any_tool_called?: string[] | undefined;
+    }, {
+        any_tool_called?: string[] | undefined;
+    }>, {
+        any_tool_called?: string[] | undefined;
+    }, {
+        any_tool_called?: string[] | undefined;
+    }>>;
 }, "strip", z.ZodTypeAny, {
     instruction: string | {
         inline: string;
@@ -612,6 +634,9 @@ export declare const nodeZ: z.ZodObject<{
     } | undefined;
     output?: Record<string, unknown> | undefined;
     max_turns?: number | undefined;
+    verify?: {
+        any_tool_called?: string[] | undefined;
+    } | undefined;
 }, {
     instruction: string | {
         inline: string;
@@ -661,6 +686,9 @@ export declare const nodeZ: z.ZodObject<{
     output?: Record<string, unknown> | undefined;
     skills?: string[] | undefined;
     max_turns?: number | undefined;
+    verify?: {
+        any_tool_called?: string[] | undefined;
+    } | undefined;
 }>;
 export declare const edgeZ: z.ZodObject<{
     from: z.ZodString;
@@ -841,6 +869,17 @@ export declare const workflowZ: z.ZodObject<{
             })[];
             only?: boolean | undefined;
         }>]>>;
+        verify: z.ZodOptional<z.ZodEffects<z.ZodObject<{
+            any_tool_called: z.ZodOptional<z.ZodArray<z.ZodString, "many">>;
+        }, "strip", z.ZodTypeAny, {
+            any_tool_called?: string[] | undefined;
+        }, {
+            any_tool_called?: string[] | undefined;
+        }>, {
+            any_tool_called?: string[] | undefined;
+        }, {
+            any_tool_called?: string[] | undefined;
+        }>>;
     }, "strip", z.ZodTypeAny, {
         instruction: string | {
             inline: string;
@@ -890,6 +929,9 @@ export declare const workflowZ: z.ZodObject<{
         } | undefined;
         output?: Record<string, unknown> | undefined;
         max_turns?: number | undefined;
+        verify?: {
+            any_tool_called?: string[] | undefined;
+        } | undefined;
     }, {
         instruction: string | {
             inline: string;
@@ -939,6 +981,9 @@ export declare const workflowZ: z.ZodObject<{
         output?: Record<string, unknown> | undefined;
         skills?: string[] | undefined;
         max_turns?: number | undefined;
+        verify?: {
+            any_tool_called?: string[] | undefined;
+        } | undefined;
     }>>;
     edges: z.ZodArray<z.ZodObject<{
         from: z.ZodString;
@@ -1156,6 +1201,9 @@ export declare const workflowZ: z.ZodObject<{
         } | undefined;
         output?: Record<string, unknown> | undefined;
         max_turns?: number | undefined;
+        verify?: {
+            any_tool_called?: string[] | undefined;
+        } | undefined;
     }>;
     edges: {
         to: string;
@@ -1232,6 +1280,9 @@ export declare const workflowZ: z.ZodObject<{
         output?: Record<string, unknown> | undefined;
         skills?: string[] | undefined;
         max_turns?: number | undefined;
+        verify?: {
+            any_tool_called?: string[] | undefined;
+        } | undefined;
     }>;
     edges: {
         to: string;
@@ -1338,6 +1389,9 @@ export declare function parseWorkflow(raw: unknown): {
         } | undefined;
         output?: Record<string, unknown> | undefined;
         max_turns?: number | undefined;
+        verify?: {
+            any_tool_called?: string[] | undefined;
+        } | undefined;
     }>;
     edges: {
         to: string;

package/dist/schema.js

@@ -75,6 +75,13 @@ export const nodeSourcesZ = z.union([
         sources: z.array(sourceZ),
     }),
 ]);
+export const nodeVerifyZ = z
+    .object({
+    any_tool_called: z.array(z.string().min(1)).min(1).optional(),
+})
+    .refine((v) => v.any_tool_called !== undefined, {
+    message: "verify must declare at least one check (e.g. any_tool_called)",
+});
 export const nodeZ = z.object({
     name: z.string().min(1),
     instruction: sourceZ,
@@ -83,6 +90,7 @@ export const nodeZ = z.object({
     max_turns: z.number().int().min(1).optional(),
     rules: nodeSourcesZ.optional(),
     context: nodeSourcesZ.optional(),
+    verify: nodeVerifyZ.optional(),
 });
 export const edgeZ = z.object({
     from: z.string().min(1),

package/dist/skills/linear.js

@@ -47,7 +47,13 @@ export const linear = {
                 },
                 required: ["teamId", "title"],
             },
-            handler: async (input, ctx) => linearGql(`mutation($input: IssueCreateInput!) { issueCreate(input: $input) { success issue { id identifier url title } } }`, { input }, ctx),
+            handler: async (input, ctx) => {
+                const data = await linearGql(`mutation($input: IssueCreateInput!) { issueCreate(input: $input) { success issue { id identifier url title } } }`, { input }, ctx);
+                if (!data?.issueCreate?.success || !data?.issueCreate?.issue?.identifier) {
+                    throw new Error(`[Linear] linear_create_issue returned no identifier — issue was not created. Raw response: ${JSON.stringify(data)}`);
+                }
+                return data;
+            },
         },
         {
             name: "linear_search_issues",
@@ -130,7 +136,11 @@ export const linear = {
             },
             handler: async (input, ctx) => {
                 const { issueId, ...updates } = input;
-                return linearGql(`mutation($id: String!, $input: IssueUpdateInput!) { issueUpdate(id: $id, input: $input) { success issue { id identifier url title state { name } } } }`, { id: issueId, input: updates }, ctx);
+                const data = await linearGql(`mutation($id: String!, $input: IssueUpdateInput!) { issueUpdate(id: $id, input: $input) { success issue { id identifier url title state { name } } } }`, { id: issueId, input: updates }, ctx);
+                if (!data?.issueUpdate?.success) {
+                    throw new Error(`[Linear] linear_update_issue failed for ${issueId}. Raw response: ${JSON.stringify(data)}`);
+                }
+                return data;
             },
         },
     ],

package/dist/types.d.ts

@@ -49,6 +49,26 @@ export type NodeSources = _Source[] | {
     only?: boolean;
     sources: _Source[];
 };
+/**
+ * Machine-checked post-condition for a node.
+ *
+ * Evaluated by the executor AFTER the LLM finishes. If the check fails, the
+ * node is marked `failed` even if the LLM itself returned success — this
+ * catches the common case of the model claiming success without actually
+ * invoking the side-effectful tool (e.g. reporting "issue created" when no
+ * `linear_create_issue` call was made, or the call errored).
+ *
+ * Keep the shape small and declarative. Anything richer should be a skill
+ * or a dedicated workflow node, not a verify clause.
+ */
+export interface NodeVerify {
+    /**
+     * At least one of the named tools must have been invoked successfully during
+     * this node's execution (no `output.error` recorded in `toolCalls`). The
+     * node is marked failed otherwise.
+     */
+    any_tool_called?: string[];
+}
 /** A node in the workflow DAG */
 export interface Node {
     /** Human-readable name */
@@ -65,6 +85,8 @@ export interface Node {
     rules?: NodeSources;
     /** Per-node background knowledge. Additive by default; set `{ only: true, sources: [...] }` to block cascade. */
     context?: NodeSources;
+    /** Machine-checked post-conditions. Enforced by the executor after the LLM finishes. */
+    verify?: NodeVerify;
 }
 /** An edge connecting two nodes */
 export interface Edge {

package/dist/workflows/browser.js

@@ -1,3 +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":"gather","nodes":{"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):** Filing a duplicate ticket is worse than under-reporting — the team inherits sprawl that humans have to clean up later. Complete EVERY step below before classifying anything as novel.\n4a. **Search broadly.** Run multiple queries against the issue tracker (BOTH open AND closed): the affected file or module path, the error message or log string verbatim, the feature or service name, and the symptom family (e.g. \"startup crash\", \"data dropped silently\"). Do not rely on a single keyword — a narrow search is how duplicates slip through.\n4b. **Read the full body of every promising candidate — do NOT match on title alone.** For each top match, open the issue and read its entire description, including any \"Recommended Fix\", \"Proposed Fix\", \"Action Items\", or \"Acceptance Criteria\" section. An existing open issue whose recommended fix already prescribes the change you were about to propose IS a duplicate, even if the symptom you just observed is a new instance of the same underlying bug.\n4c. **Check for meta-issues and bug families.** If an existing ticket names a pattern that your finding is another instance of (same root cause, same function/module, different input or caller), treat your finding as a sibling of that family and comment on the existing ticket. Do not file a parallel ticket per instance — that is the exact pattern that produces backlog sprawl.\n4d. **When uncertain, comment don't file.** If you are less than ~80% confident a finding is truly novel after steps 4a–4c, classify it as a duplicate and add a \"+1 — another instance\" comment to the closest existing issue with the new context. Over-reporting duplicates is cheap; ticket sprawl is expensive.\n\n   - If matched → **duplicate**. Record the existing issue ID in `duplicate_of`.\n   - If no match after 4a–4d → **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 the issue tracker specified in context (e.g. Linear, Jira, or GitHub Issues) — do NOT fall back to a different tracker. 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\nIf context.cloudRunId is provided, append this HTML comment to the end of the PR body: <!-- sweny:run_id:{context.cloudRunId} -->\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":"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"}],"skills":{}};
+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":"gather","nodes":{"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):** Filing a duplicate ticket is worse than under-reporting — the team inherits sprawl that humans have to clean up later. Complete EVERY step below before classifying anything as novel.\n4a. **Search broadly.** Run multiple queries against the issue tracker (BOTH open AND closed): the affected file or module path, the error message or log string verbatim, the feature or service name, and the symptom family (e.g. \"startup crash\", \"data dropped silently\"). Do not rely on a single keyword — a narrow search is how duplicates slip through.\n4b. **Read the full body of every promising candidate — do NOT match on title alone.** For each top match, open the issue and read its entire description, including any \"Recommended Fix\", \"Proposed Fix\", \"Action Items\", or \"Acceptance Criteria\" section. An existing open issue whose recommended fix already prescribes the change you were about to propose IS a duplicate, even if the symptom you just observed is a new instance of the same underlying bug.\n4c. **Check for meta-issues and bug families.** If an existing ticket names a pattern that your finding is another instance of (same root cause, same function/module, different input or caller), treat your finding as a sibling of that family and comment on the existing ticket. Do not file a parallel ticket per instance — that is the exact pattern that produces backlog sprawl.\n4d. **When uncertain, comment don't file.** If you are less than ~80% confident a finding is truly novel after steps 4a–4c, classify it as a duplicate and add a \"+1 — another instance\" comment to the closest existing issue with the new context. Over-reporting duplicates is cheap; ticket sprawl is expensive.\n\n   - If matched → **duplicate**. Record the existing issue ID in `duplicate_of`.\n   - If no match after 4a–4d → **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 by invoking the appropriate tool (`linear_create_issue` or `github_create_issue`). You MUST actually call the tool — do NOT synthesize an identifier from an alert ID, commit SHA, or your own imagination. If the tool errors, stop and report the failure; do not invent a fallback identifier.\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.\n5. Copy the identifier returned by the tool verbatim into the `issueIdentifier` output field. The identifier must match `^[A-Z][A-Z0-9]*-\\d+$` (e.g. `OFF-1234`) — do not prefix it with anything else.\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 the issue tracker specified in context (e.g. Linear, Jira, or GitHub Issues) — do NOT fall back to a different tracker. Output the created/updated issue identifiers.","skills":["linear","github"],"verify":{"any_tool_called":["linear_create_issue","github_create_issue"]},"output":{"type":"object","properties":{"issueIdentifier":{"type":"string","pattern":"^[A-Z][A-Z0-9]*-\\d+$","description":"Primary issue identifier (e.g. OFF-1234). MUST be the identifier returned by `linear_create_issue` / `github_create_issue` — do NOT invent a value from a Sentry short-ID or commit SHA. Used by downstream nodes for branch naming and PR linking."},"issueTitle":{"type":"string","description":"Title of the primary issue created"},"issueUrl":{"type":"string","pattern":"^https?://","description":"URL of the primary issue created, as returned by the create-issue tool"},"issues":{"type":"array","minItems":1,"description":"All issues created or updated during this step","items":{"type":"object","properties":{"identifier":{"type":"string"},"title":{"type":"string"},"url":{"type":"string"},"action":{"type":"string","enum":["created","updated","reopened"]}},"required":["identifier","action"]}}},"required":["issueIdentifier","issueTitle","issueUrl","issues"]}},"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. The issue created in the previous step is in your context — use its identifier for branch naming and commit messages.\n\n0. **Precondition — verify context.create_issue.issueIdentifier is well-formed.**\n   The identifier MUST match `^[A-Z][A-Z0-9]*-\\d+$` (e.g. `OFF-1234`). If it is\n   missing, empty, or matches a Sentry short-ID / slug / any other shape, STOP\n   immediately — do NOT invent a branch name from the Sentry event, commit SHA,\n   or alert payload. Return a failed status with a clear message instead; the\n   workflow will route to notify and a human will pick it up.\n\n1. Create a feature branch from the base branch (check context for baseBranch, default \"main\").\n   **Branch name MUST include the issue identifier** exactly as provided in\n   `context.create_issue.issueIdentifier`. Format: lowercase the identifier and use\n   it as a prefix, e.g. `off-1234-fix-null-check`. If the repository uses a different\n   branch convention (check context.branchPattern or the rules/CLAUDE.md for a\n   regex), follow that — but the identifier piece MUST still come from\n   `context.create_issue.issueIdentifier`, never from a Sentry short-ID.\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. Start the message with the issue identifier in brackets,\n   e.g. `[OFF-1234] fix: guard null projectId before database lookup`.\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. The issue identifier and URL are in your context from the create_issue step.\n\n1. Push the branch to the remote.\n2. Create a PR with a title that starts with the issue identifier in brackets. Format: `[{context.create_issue.issueIdentifier}] fix: {short description}`.\n3. In the PR body, include: summary of the bug, what the fix does, and a link to the issue (context.create_issue.issueUrl). If the investigation found a Sentry issue, include \"Fixes {sentryShortId}\" in the PR body so Sentry auto-resolves on merge.\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\nIf context.cloudRunId is provided, append this HTML comment to the end of the PR body: <!-- sweny:run_id:{context.cloudRunId} -->\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":"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"}],"skills":{}};
 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\nIf context.cloudRunId is provided, append this HTML comment to the end of the PR body: <!-- sweny:run_id:{context.cloudRunId} -->\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":"skip","to":"notify"},{"from":"create_pr","to":"notify"}],"skills":{}};
 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"}],"skills":{}};

package/dist/workflows/triage.yml

@@ -148,7 +148,10 @@ nodes:
 
       **For each NOVEL finding** (is_duplicate = false):
 
-      1. Create a new issue with a clear, actionable title.
+      1. Create a new issue with a clear, actionable title by invoking the appropriate tool
+      (`linear_create_issue` or `github_create_issue`). You MUST actually call the tool — do NOT
+      synthesize an identifier from an alert ID, commit SHA, or your own imagination. If the
+      tool errors, stop and report the failure; do not invent a fallback identifier.
 
       2. Include: root cause, severity, affected services, reproduction steps, and recommended fix.
 
@@ -156,6 +159,10 @@ nodes:
 
       4. Link to relevant commits, PRs, or existing issues.
 
+      5. Copy the identifier returned by the tool verbatim into the `issueIdentifier` output
+      field. The identifier must match `^[A-Z][A-Z0-9]*-\d+$` (e.g. `OFF-1234`) — do not
+      prefix it with anything else.
+
 
       **For each DUPLICATE finding** (is_duplicate = true):
 
@@ -179,6 +186,59 @@ nodes:
     skills:
       - linear
       - github
+    verify:
+      # Reject output that claims success without a real issue-creation tool call.
+      # The executor checks this after the node finishes; if none of these tools
+      # was invoked successfully, the node is marked failed and downstream nodes
+      # (implement, create_pr) never run with a hallucinated identifier.
+      any_tool_called:
+        - linear_create_issue
+        - github_create_issue
+    output:
+      type: object
+      properties:
+        issueIdentifier:
+          type: string
+          pattern: '^[A-Z][A-Z0-9]*-\d+$'
+          description: >-
+            Primary issue identifier (e.g. OFF-1234). MUST be the identifier returned by
+            `linear_create_issue` / `github_create_issue` — do NOT invent a value from a
+            Sentry short-ID or commit SHA. Used by downstream nodes for branch naming and
+            PR linking.
+        issueTitle:
+          type: string
+          description: Title of the primary issue created
+        issueUrl:
+          type: string
+          pattern: "^https?://"
+          description: URL of the primary issue created, as returned by the create-issue tool
+        issues:
+          type: array
+          minItems: 1
+          description: All issues created or updated during this step
+          items:
+            type: object
+            properties:
+              identifier:
+                type: string
+              title:
+                type: string
+              url:
+                type: string
+              action:
+                type: string
+                enum:
+                  - created
+                  - updated
+                  - reopened
+            required:
+              - identifier
+              - action
+      required:
+        - issueIdentifier
+        - issueTitle
+        - issueUrl
+        - issues
   skip:
     name: Skip — All Duplicates or Low Priority
     instruction: >-
@@ -205,13 +265,27 @@ nodes:
   implement:
     name: Implement Fix
     instruction: |-
-      Implement the fix identified during investigation:
+      Implement the fix identified during investigation. The issue created in the previous step is in your context — use its identifier for branch naming and commit messages.
+
+      0. **Precondition — verify context.create_issue.issueIdentifier is well-formed.**
+         The identifier MUST match `^[A-Z][A-Z0-9]*-\d+$` (e.g. `OFF-1234`). If it is
+         missing, empty, or matches a Sentry short-ID / slug / any other shape, STOP
+         immediately — do NOT invent a branch name from the Sentry event, commit SHA,
+         or alert payload. Return a failed status with a clear message instead; the
+         workflow will route to notify and a human will pick it up.
 
       1. Create a feature branch from the base branch (check context for baseBranch, default "main").
+         **Branch name MUST include the issue identifier** exactly as provided in
+         `context.create_issue.issueIdentifier`. Format: lowercase the identifier and use
+         it as a prefix, e.g. `off-1234-fix-null-check`. If the repository uses a different
+         branch convention (check context.branchPattern or the rules/CLAUDE.md for a
+         regex), follow that — but the identifier piece MUST still come from
+         `context.create_issue.issueIdentifier`, never from a Sentry short-ID.
       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.
+      5. Stage and commit with a clear commit message. Start the message with the issue identifier in brackets,
+         e.g. `[OFF-1234] fix: guard null projectId before database lookup`.
 
       Keep changes minimal and focused. Do not refactor surrounding code or add unrelated improvements.
 
@@ -221,15 +295,17 @@ nodes:
   create_pr:
     name: Open Pull Request
     instruction: >-
-      Open a pull request for the fix:
+      Open a pull request for the fix. The issue identifier and URL are in your context from the create_issue step.
 
 
       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").
+      2. Create a PR with a title that starts with the issue identifier in brackets.
+      Format: `[{context.create_issue.issueIdentifier}] fix: {short description}`.
 
-      3. In the PR body, include: summary of the bug, what the fix does, and a link to the issue.
+      3. In the PR body, include: summary of the bug, what the fix does, and a link to the issue
+      (context.create_issue.issueUrl). If the investigation found a Sentry issue, include "Fixes {sentryShortId}"
+      in the PR body so Sentry auto-resolves on merge.
 
       4. Add appropriate labels if available.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sweny-ai/core",
-  "version": "0.1.69",
+  "version": "0.1.71",
   "type": "module",
   "bin": {
     "sweny": "./dist/cli/main.js"