@voiden/runner 2.2.0 → 2.3.0-beta.10

package/dist/parser.d.ts

@@ -1,24 +0,0 @@
-/**
- * Parser: .void file content (markdown string) → Block[]
- *
- * Adapted from apps/ui/src/core/editors/voiden/markdownConverter.ts
- * - No TipTap/ProseMirror dependency
- * - No schema validation — trusts the YAML type field as-is
- */
-import type { Block } from './types.js';
-/**
- * Parse .void file content into an array of blocks.
- * Extracts all ```void ... ``` fenced code blocks from the markdown.
- */
-export declare function parseVoidFile(content: string): Block[];
-export interface VoidSection {
-    /** Label from the request-separator block, if present */
-    label?: string;
-    blocks: Block[];
-}
-/**
- * Parse .void file content into sections split at request-separator blocks.
- * A file with no separators returns a single section.
- */
-export declare function parseVoidFileSections(content: string): VoidSection[];
-//# sourceMappingURL=parser.d.ts.map

package/dist/parser.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"parser.d.ts","sourceRoot":"","sources":["../src/parser.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAGH,OAAO,KAAK,EAAE,KAAK,EAAE,MAAM,YAAY,CAAA;AA6CvC;;;GAGG;AACH,wBAAgB,aAAa,CAAC,OAAO,EAAE,MAAM,GAAG,KAAK,EAAE,CActD;AAED,MAAM,WAAW,WAAW;IAC1B,yDAAyD;IACzD,KAAK,CAAC,EAAE,MAAM,CAAA;IACd,MAAM,EAAE,KAAK,EAAE,CAAA;CAChB;AAED;;;GAGG;AACH,wBAAgB,qBAAqB,CAAC,OAAO,EAAE,MAAM,GAAG,WAAW,EAAE,CAiBpE"}

package/dist/parser.js

@@ -1,87 +0,0 @@
-/**
- * Parser: .void file content (markdown string) → Block[]
- *
- * Adapted from apps/ui/src/core/editors/voiden/markdownConverter.ts
- * - No TipTap/ProseMirror dependency
- * - No schema validation — trusts the YAML type field as-is
- */
-import YAML from 'yaml';
-/**
- * Restore %%EMPTY_LINE%% placeholders back to empty strings.
- * These appear in script/code node bodies when saved.
- */
-function restoreEmptyLineMarkers(value) {
-    if (typeof value === 'string') {
-        return value.replace(/%%EMPTY_LINE%%/g, '');
-    }
-    if (Array.isArray(value)) {
-        return value.map(restoreEmptyLineMarkers);
-    }
-    if (value && typeof value === 'object') {
-        const result = {};
-        for (const [k, v] of Object.entries(value)) {
-            result[k] = restoreEmptyLineMarkers(v);
-        }
-        return result;
-    }
-    return value;
-}
-/**
- * Parse a single void code block text (the YAML inside the fenced block).
- * Returns null if the block is malformed.
- */
-function parseVoidBlockText(text) {
-    const lines = text.trim().split('\n');
-    if (lines[0]?.trim() !== '---')
-        return null;
-    const headerEnd = lines.indexOf('---', 1);
-    if (headerEnd === -1)
-        return null;
-    const yamlText = lines.slice(1, headerEnd).join('\n');
-    try {
-        let node = YAML.parse(yamlText);
-        node = restoreEmptyLineMarkers(node);
-        return node;
-    }
-    catch {
-        return null;
-    }
-}
-/**
- * Parse .void file content into an array of blocks.
- * Extracts all ```void ... ``` fenced code blocks from the markdown.
- */
-export function parseVoidFile(content) {
-    const blocks = [];
-    // Match ```void\n...\n``` fenced code blocks
-    const regex = /^```void\n([\s\S]*?)^```/gm;
-    let match;
-    while ((match = regex.exec(content)) !== null) {
-        const block = parseVoidBlockText(match[1]);
-        if (block) {
-            blocks.push(block);
-        }
-    }
-    return blocks;
-}
-/**
- * Parse .void file content into sections split at request-separator blocks.
- * A file with no separators returns a single section.
- */
-export function parseVoidFileSections(content) {
-    const allBlocks = parseVoidFile(content);
-    const sections = [{ blocks: [] }];
-    for (const block of allBlocks) {
-        if (block.type === 'request-separator') {
-            sections.push({
-                label: block.attrs?.label,
-                blocks: [],
-            });
-        }
-        else {
-            sections[sections.length - 1].blocks.push(block);
-        }
-    }
-    return sections.filter(s => s.blocks.length > 0);
-}
-//# sourceMappingURL=parser.js.map

package/dist/parser.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"parser.js","sourceRoot":"","sources":["../src/parser.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,OAAO,IAAI,MAAM,MAAM,CAAA;AAGvB;;;GAGG;AACH,SAAS,uBAAuB,CAAC,KAAc;IAC7C,IAAI,OAAO,KAAK,KAAK,QAAQ,EAAE,CAAC;QAC9B,OAAO,KAAK,CAAC,OAAO,CAAC,iBAAiB,EAAE,EAAE,CAAC,CAAA;IAC7C,CAAC;IACD,IAAI,KAAK,CAAC,OAAO,CAAC,KAAK,CAAC,EAAE,CAAC;QACzB,OAAO,KAAK,CAAC,GAAG,CAAC,uBAAuB,CAAC,CAAA;IAC3C,CAAC;IACD,IAAI,KAAK,IAAI,OAAO,KAAK,KAAK,QAAQ,EAAE,CAAC;QACvC,MAAM,MAAM,GAA4B,EAAE,CAAA;QAC1C,KAAK,MAAM,CAAC,CAAC,EAAE,CAAC,CAAC,IAAI,MAAM,CAAC,OAAO,CAAC,KAAgC,CAAC,EAAE,CAAC;YACtE,MAAM,CAAC,CAAC,CAAC,GAAG,uBAAuB,CAAC,CAAC,CAAC,CAAA;QACxC,CAAC;QACD,OAAO,MAAM,CAAA;IACf,CAAC;IACD,OAAO,KAAK,CAAA;AACd,CAAC;AAED;;;GAGG;AACH,SAAS,kBAAkB,CAAC,IAAY;IACtC,MAAM,KAAK,GAAG,IAAI,CAAC,IAAI,EAAE,CAAC,KAAK,CAAC,IAAI,CAAC,CAAA;IACrC,IAAI,KAAK,CAAC,CAAC,CAAC,EAAE,IAAI,EAAE,KAAK,KAAK;QAAE,OAAO,IAAI,CAAA;IAE3C,MAAM,SAAS,GAAG,KAAK,CAAC,OAAO,CAAC,KAAK,EAAE,CAAC,CAAC,CAAA;IACzC,IAAI,SAAS,KAAK,CAAC,CAAC;QAAE,OAAO,IAAI,CAAA;IAEjC,MAAM,QAAQ,GAAG,KAAK,CAAC,KAAK,CAAC,CAAC,EAAE,SAAS,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAA;IAErD,IAAI,CAAC;QACH,IAAI,IAAI,GAAG,IAAI,CAAC,KAAK,CAAC,QAAQ,CAAC,CAAA;QAC/B,IAAI,GAAG,uBAAuB,CAAC,IAAI,CAAC,CAAA;QACpC,OAAO,IAAa,CAAA;IACtB,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,IAAI,CAAA;IACb,CAAC;AACH,CAAC;AAED;;;GAGG;AACH,MAAM,UAAU,aAAa,CAAC,OAAe;IAC3C,MAAM,MAAM,GAAY,EAAE,CAAA;IAC1B,6CAA6C;IAC7C,MAAM,KAAK,GAAG,4BAA4B,CAAA;IAC1C,IAAI,KAA6B,CAAA;IAEjC,OAAO,CAAC,KAAK,GAAG,KAAK,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC,KAAK,IAAI,EAAE,CAAC;QAC9C,MAAM,KAAK,GAAG,kBAAkB,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,CAAA;QAC1C,IAAI,KAAK,EAAE,CAAC;YACV,MAAM,CAAC,IAAI,CAAC,KAAK,CAAC,CAAA;QACpB,CAAC;IACH,CAAC;IAED,OAAO,MAAM,CAAA;AACf,CAAC;AAQD;;;GAGG;AACH,MAAM,UAAU,qBAAqB,CAAC,OAAe;IACnD,MAAM,SAAS,GAAG,aAAa,CAAC,OAAO,CAAC,CAAA;IAExC,MAAM,QAAQ,GAAkB,CAAC,EAAE,MAAM,EAAE,EAAE,EAAE,CAAC,CAAA;IAEhD,KAAK,MAAM,KAAK,IAAI,SAAS,EAAE,CAAC;QAC9B,IAAI,KAAK,CAAC,IAAI,KAAK,mBAAmB,EAAE,CAAC;YACvC,QAAQ,CAAC,IAAI,CAAC;gBACZ,KAAK,EAAE,KAAK,CAAC,KAAK,EAAE,KAA2B;gBAC/C,MAAM,EAAE,EAAE;aACX,CAAC,CAAA;QACJ,CAAC;aAAM,CAAC;YACN,QAAQ,CAAC,QAAQ,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,MAAM,CAAC,IAAI,CAAC,KAAK,CAAC,CAAA;QAClD,CAAC;IACH,CAAC;IAED,OAAO,QAAQ,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,MAAM,CAAC,MAAM,GAAG,CAAC,CAAC,CAAA;AAClD,CAAC"}

package/dist/skillContent.d.ts

@@ -1,8 +0,0 @@
-/**
- * Standalone skill installed by `voiden-runner mcp install` for CLI-only
- * users (no Voiden app, so none of its richer composed .void-authoring
- * skill is available). Focused on the MCP tools this package ships —
- * list/run/verify/write-back — not on full block-authoring syntax.
- */
-export declare const RUNNER_SKILL_MARKDOWN = "---\nname: voiden-runner\ndescription: Run and verify .void API requests via the voiden-mcp-server MCP tools \u2014 list requests, execute them for real, read structured results, and record them back into the file.\n---\n\n# Voiden Runner \u2014 Running & Verifying .void Requests\n\n.void files describe HTTP/GraphQL/WebSocket/gRPC requests (see https://docs.voiden.md for the full authoring format, or the Voiden app's own \"voiden\" skill if it's installed). This skill covers a different, complementary job: **actually executing** those requests and checking the result, instead of only ever generating text that looks correct.\n\nA request block that merely looks well-formed can still be wrong (bad URL, wrong auth, malformed body). Don't stop at \"this looks right\" when you can check that it *is* right.\n\n## Tools\n\n| Tool | Use it to |\n|------|-----------|\n| `list_void_files` | See which `.void` files exist in the project |\n| `list_requests` | See what requests a file contains (label, request uid, method, URL) without running anything |\n| `run_request` | Actually execute a request (or a whole file) \u2014 makes a real network call and returns a structured result: `success`, `status`, `statusText`, `durationMs`, `body`, `error`, headers |\n| `write_result` | Record a `run_request` result back into the `.void` file, as a `response` block placed right after the request it belongs to |\n\n## Workflow\n\n1. Call `list_void_files` / `list_requests` to see what's actually in the project before assuming.\n2. Call `run_request` (with `sectionLabel` if you only want one request) to execute it for real.\n3. Read the result, don't just assume success:\n   - `success: false` or a non-2xx `status` \u2014 read `error`/`body` for why, fix the request block, and re-run. A request that \"looks right\" but 404s or 401s is not done.\n   - `success: true` \u2014 sanity-check the response `body` actually matches what the request was supposed to do.\n4. Optionally call `write_result` with the `requestUid` and the specific `results[i].result` object (not the whole `run_request` response) to persist what actually happened into the file.\n\n## Caveats\n\n- `run_request` makes a real call against whatever `BASE_URL`/auth/tokens are in scope for the target environment \u2014 treat it like running the request for real, not like generating text. Check which env/profile is active before running against anything that matters (e.g. don't hit `prod` by accident).\n- `write_result` has no file locking. Don't call it on a file that's open with unsaved edits elsewhere (e.g. in the Voiden app right now) \u2014 the next save there can overwrite it, or it can overwrite in-progress edits.\n- For CI/CD validation, prefer the plain `voiden-runner run --json` CLI command over this agent loop \u2014 it's deterministic and doesn't need an LLM in the loop. These tools are for interactive authoring/iteration, not as a CI gate.\n";
-//# sourceMappingURL=skillContent.d.ts.map

package/dist/skillContent.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"skillContent.d.ts","sourceRoot":"","sources":["../src/skillContent.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AACH,eAAO,MAAM,qBAAqB,g4FAkCjC,CAAA"}

package/dist/skillContent.js

@@ -1,42 +0,0 @@
-/**
- * Standalone skill installed by `voiden-runner mcp install` for CLI-only
- * users (no Voiden app, so none of its richer composed .void-authoring
- * skill is available). Focused on the MCP tools this package ships —
- * list/run/verify/write-back — not on full block-authoring syntax.
- */
-export const RUNNER_SKILL_MARKDOWN = `---
-name: voiden-runner
-description: Run and verify .void API requests via the voiden-mcp-server MCP tools — list requests, execute them for real, read structured results, and record them back into the file.
----
-
-# Voiden Runner — Running & Verifying .void Requests
-
-.void files describe HTTP/GraphQL/WebSocket/gRPC requests (see https://docs.voiden.md for the full authoring format, or the Voiden app's own "voiden" skill if it's installed). This skill covers a different, complementary job: **actually executing** those requests and checking the result, instead of only ever generating text that looks correct.
-
-A request block that merely looks well-formed can still be wrong (bad URL, wrong auth, malformed body). Don't stop at "this looks right" when you can check that it *is* right.
-
-## Tools
-
-| Tool | Use it to |
-|------|-----------|
-| \`list_void_files\` | See which \`.void\` files exist in the project |
-| \`list_requests\` | See what requests a file contains (label, request uid, method, URL) without running anything |
-| \`run_request\` | Actually execute a request (or a whole file) — makes a real network call and returns a structured result: \`success\`, \`status\`, \`statusText\`, \`durationMs\`, \`body\`, \`error\`, headers |
-| \`write_result\` | Record a \`run_request\` result back into the \`.void\` file, as a \`response\` block placed right after the request it belongs to |
-
-## Workflow
-
-1. Call \`list_void_files\` / \`list_requests\` to see what's actually in the project before assuming.
-2. Call \`run_request\` (with \`sectionLabel\` if you only want one request) to execute it for real.
-3. Read the result, don't just assume success:
-   - \`success: false\` or a non-2xx \`status\` — read \`error\`/\`body\` for why, fix the request block, and re-run. A request that "looks right" but 404s or 401s is not done.
-   - \`success: true\` — sanity-check the response \`body\` actually matches what the request was supposed to do.
-4. Optionally call \`write_result\` with the \`requestUid\` and the specific \`results[i].result\` object (not the whole \`run_request\` response) to persist what actually happened into the file.
-
-## Caveats
-
-- \`run_request\` makes a real call against whatever \`BASE_URL\`/auth/tokens are in scope for the target environment — treat it like running the request for real, not like generating text. Check which env/profile is active before running against anything that matters (e.g. don't hit \`prod\` by accident).
-- \`write_result\` has no file locking. Don't call it on a file that's open with unsaved edits elsewhere (e.g. in the Voiden app right now) — the next save there can overwrite it, or it can overwrite in-progress edits.
-- For CI/CD validation, prefer the plain \`voiden-runner run --json\` CLI command over this agent loop — it's deterministic and doesn't need an LLM in the loop. These tools are for interactive authoring/iteration, not as a CI gate.
-`;
-//# sourceMappingURL=skillContent.js.map

package/dist/skillContent.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"skillContent.js","sourceRoot":"","sources":["../src/skillContent.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AACH,MAAM,CAAC,MAAM,qBAAqB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAkCpC,CAAA"}