@method-ai-hq/sdk 0.0.0-stage → 0.14.2

package/dist/packages/sdk/package.json

@@ -0,0 +1,232 @@
+{
+    "name": "@method-ai-hq/sdk",
+    "version": "0.14.2",
+    "description": "Build and run reusable .method files with checked steps and saved results.",
+    "license": "MIT",
+    "type": "module",
+    "main": "dist/packages/sdk/src/index.js",
+    "types": "dist/packages/sdk/src/index.d.ts",
+    "bin": {
+        "method": "dist/packages/sdk/src/method.js",
+        "method-bridge": "dist/packages/sdk/src/bridge.js"
+    },
+    "files": [
+        "dist",
+        "README.md",
+        "LICENSE"
+    ],
+    "engines": {
+        "node": ">=22"
+    },
+    "repository": {
+        "type": "git",
+        "url": "https://github.com/method-ai-hq/method-sdk.git",
+        "directory": "packages/sdk"
+    },
+    "keywords": [
+        "workflow",
+        "agents",
+        "ai-agents",
+        "verification",
+        "mcp"
+    ],
+    "scripts": {
+        "build": "rm -rf dist && tsc -p tsconfig.build.json && chmod +x dist/packages/sdk/src/bridge.js dist/packages/sdk/src/method.js && node scripts/copy-examples.mjs",
+        "prepack": "npm --prefix ../.. run build"
+    },
+    "dependencies": {
+        "@withmethod/runtime": "https://codeload.github.com/method-ai-hq/method-spec/tar.gz/c45c5ba1a3432b8d4e90ff07a7457eef5ea0f371",
+        "fflate": "^0.8.3",
+        "yaml": "^2.9.0",
+        "zod": "^3.25.76"
+    },
+    "homepage": "https://docs.withmethod.ai/sdk/overview",
+    "exports": {
+        ".": {
+            "types": "./dist/packages/sdk/src/index.d.ts",
+            "import": "./dist/packages/sdk/src/index.js",
+            "default": "./dist/packages/sdk/src/index.js"
+        },
+        "./schema": {
+            "types": "./dist/packages/workflow-language/src/schema.d.ts",
+            "import": "./dist/packages/workflow-language/src/schema.js",
+            "default": "./dist/packages/workflow-language/src/schema.js"
+        },
+        "./validate": {
+            "types": "./dist/packages/workflow-language/src/validate.d.ts",
+            "import": "./dist/packages/workflow-language/src/validate.js",
+            "default": "./dist/packages/workflow-language/src/validate.js"
+        },
+        "./execution": {
+            "types": "./dist/packages/workflow-language/src/execution.d.ts",
+            "import": "./dist/packages/workflow-language/src/execution.js",
+            "default": "./dist/packages/workflow-language/src/execution.js"
+        },
+        "./inspection": {
+            "types": "./dist/packages/workflow-language/src/inspection.d.ts",
+            "import": "./dist/packages/workflow-language/src/inspection.js",
+            "default": "./dist/packages/workflow-language/src/inspection.js"
+        },
+        "./result-files": {
+            "types": "./dist/packages/workflow-language/src/result-files.d.ts",
+            "import": "./dist/packages/workflow-language/src/result-files.js",
+            "default": "./dist/packages/workflow-language/src/result-files.js"
+        },
+        "./identity": {
+            "types": "./dist/packages/contracts/src/identity.d.ts",
+            "import": "./dist/packages/contracts/src/identity.js",
+            "default": "./dist/packages/contracts/src/identity.js"
+        },
+        "./method-package": {
+            "types": "./dist/packages/contracts/src/method-package.d.ts",
+            "import": "./dist/packages/contracts/src/method-package.js",
+            "default": "./dist/packages/contracts/src/method-package.js"
+        },
+        "./conversion": {
+            "types": "./dist/packages/method-document/src/conversion-report.d.ts",
+            "import": "./dist/packages/method-document/src/conversion-report.js",
+            "default": "./dist/packages/method-document/src/conversion-report.js"
+        },
+        "./method-client": {
+            "types": "./dist/packages/sdk/src/method-client.d.ts",
+            "import": "./dist/packages/sdk/src/method-client.js",
+            "default": "./dist/packages/sdk/src/method-client.js"
+        },
+        "./method-sync": {
+            "types": "./dist/packages/sdk/src/method-sync.d.ts",
+            "import": "./dist/packages/sdk/src/method-sync.js",
+            "default": "./dist/packages/sdk/src/method-sync.js"
+        },
+        "./method": {
+            "types": "./dist/packages/sdk/src/method.d.ts",
+            "import": "./dist/packages/sdk/src/method.js",
+            "default": "./dist/packages/sdk/src/method.js"
+        },
+        "./files": {
+            "types": "./dist/packages/sdk/src/files.d.ts",
+            "import": "./dist/packages/sdk/src/files.js",
+            "default": "./dist/packages/sdk/src/files.js"
+        },
+        "./inspect": {
+            "types": "./dist/packages/sdk/src/inspect.d.ts",
+            "import": "./dist/packages/sdk/src/inspect.js",
+            "default": "./dist/packages/sdk/src/inspect.js"
+        },
+        "./process": {
+            "types": "./dist/packages/sdk/src/process.d.ts",
+            "import": "./dist/packages/sdk/src/process.js",
+            "default": "./dist/packages/sdk/src/process.js"
+        },
+        "./executable": {
+            "types": "./dist/packages/sdk/src/executable.d.ts",
+            "import": "./dist/packages/sdk/src/executable.js",
+            "default": "./dist/packages/sdk/src/executable.js"
+        },
+        "./authoring": {
+            "types": "./dist/packages/sdk/src/authoring.d.ts",
+            "import": "./dist/packages/sdk/src/authoring.js",
+            "default": "./dist/packages/sdk/src/authoring.js"
+        },
+        "./method-help": {
+            "types": "./dist/packages/sdk/src/method-help.d.ts",
+            "import": "./dist/packages/sdk/src/method-help.js",
+            "default": "./dist/packages/sdk/src/method-help.js"
+        },
+        "./current-runtime": {
+            "types": "./dist/packages/sdk/src/current-runtime.d.ts",
+            "import": "./dist/packages/sdk/src/current-runtime.js",
+            "default": "./dist/packages/sdk/src/current-runtime.js"
+        },
+        "./local-setup": {
+            "types": "./dist/packages/sdk/src/local-setup.d.ts",
+            "import": "./dist/packages/sdk/src/local-setup.js",
+            "default": "./dist/packages/sdk/src/local-setup.js"
+        },
+        "./current-inspection": {
+            "types": "./dist/packages/sdk/src/current-inspection.d.ts",
+            "import": "./dist/packages/sdk/src/current-inspection.js",
+            "default": "./dist/packages/sdk/src/current-inspection.js"
+        },
+        "./method-files": {
+            "types": "./dist/packages/sdk/src/method-files.d.ts",
+            "import": "./dist/packages/sdk/src/method-files.js",
+            "default": "./dist/packages/sdk/src/method-files.js"
+        },
+        "./versions": {
+            "types": "./dist/packages/sdk/src/versions.d.ts",
+            "import": "./dist/packages/sdk/src/versions.js",
+            "default": "./dist/packages/sdk/src/versions.js"
+        },
+        "./outbox": {
+            "types": "./dist/packages/sdk/src/outbox.d.ts",
+            "import": "./dist/packages/sdk/src/outbox.js",
+            "default": "./dist/packages/sdk/src/outbox.js"
+        },
+        "./computer-settings": {
+            "types": "./dist/packages/sdk/src/computer-settings.d.ts",
+            "import": "./dist/packages/sdk/src/computer-settings.js",
+            "default": "./dist/packages/sdk/src/computer-settings.js"
+        },
+        "./bindings": {
+            "types": "./dist/packages/sdk/src/bindings.d.ts",
+            "import": "./dist/packages/sdk/src/bindings.js",
+            "default": "./dist/packages/sdk/src/bindings.js"
+        },
+        "./capabilities": {
+            "types": "./dist/packages/sdk/src/capabilities.d.ts",
+            "import": "./dist/packages/sdk/src/capabilities.js",
+            "default": "./dist/packages/sdk/src/capabilities.js"
+        },
+        "./prepare": {
+            "types": "./dist/packages/sdk/src/prepare.d.ts",
+            "import": "./dist/packages/sdk/src/prepare.js",
+            "default": "./dist/packages/sdk/src/prepare.js"
+        },
+        "./run-worker": {
+            "types": "./dist/packages/sdk/src/run-worker.d.ts",
+            "import": "./dist/packages/sdk/src/run-worker.js",
+            "default": "./dist/packages/sdk/src/run-worker.js"
+        },
+        "./local-cli": {
+            "types": "./dist/packages/sdk/src/local-cli.d.ts",
+            "import": "./dist/packages/sdk/src/local-cli.js",
+            "default": "./dist/packages/sdk/src/local-cli.js"
+        },
+        "./doctor": {
+            "types": "./dist/packages/sdk/src/doctor.d.ts",
+            "import": "./dist/packages/sdk/src/doctor.js",
+            "default": "./dist/packages/sdk/src/doctor.js"
+        },
+        "./run-saved": {
+            "types": "./dist/packages/sdk/src/run-saved.d.ts",
+            "import": "./dist/packages/sdk/src/run-saved.js",
+            "default": "./dist/packages/sdk/src/run-saved.js"
+        },
+        "./sdk-result-files": {
+            "types": "./dist/packages/sdk/src/result-files.d.ts",
+            "import": "./dist/packages/sdk/src/result-files.js",
+            "default": "./dist/packages/sdk/src/result-files.js"
+        },
+        "./package.json": "./package.json",
+        "./authoring-prompt": {
+            "types": "./dist/packages/sdk/src/authoring-prompt.d.ts",
+            "import": "./dist/packages/sdk/src/authoring-prompt.js",
+            "default": "./dist/packages/sdk/src/authoring-prompt.js"
+        },
+        "./progress": {
+            "types": "./dist/packages/sdk/src/progress.d.ts",
+            "import": "./dist/packages/sdk/src/progress.js",
+            "default": "./dist/packages/sdk/src/progress.js"
+        },
+        "./run-method": {
+            "types": "./dist/packages/sdk/src/run-method.d.ts",
+            "import": "./dist/packages/sdk/src/run-method.js",
+            "default": "./dist/packages/sdk/src/run-method.js"
+        },
+        "./authoring-example": {
+            "types": "./dist/packages/sdk/src/authoring-example.d.ts",
+            "import": "./dist/packages/sdk/src/authoring-example.js",
+            "default": "./dist/packages/sdk/src/authoring-example.js"
+        }
+    }
+}

package/dist/packages/sdk/src/authoring-example.d.ts

@@ -0,0 +1,91 @@
+export declare const authoringExamples: readonly [{
+    readonly id: "notes-summary";
+    readonly description: "The smallest complete Method: reads a folder of meeting notes, finds decisions and action items with one model call that shows two good items, and saves a summary file. A recorded case keeps one correction.";
+    readonly teaches: "files connection, call with examples of good output, a recorded case in cases/";
+    readonly directory: "notes-summary";
+    readonly entrypoint: "notes-summary.method";
+    readonly lessonFiles: readonly ["TASK.md", "notes-summary.method", "read-notes.mjs", "save.mjs", "cases/dates-in-decisions/case.json", "README.md"];
+}, {
+    readonly id: "message-routing";
+    readonly description: "Classifies a customer message with Method's classifier, then a script rule chooses a support destination. ticket.method adds one ticket write that a retry does not repeat.";
+    readonly teaches: "classify with an unclear option, a threshold in a script, an effect that reads the ticket back, retry without a duplicate write";
+    readonly directory: "message-routing";
+    readonly entrypoint: "message-routing.method";
+    readonly lessonFiles: readonly ["TASK.md", "message-routing.method", "routing.mjs", "choose-destination.mjs", "inputs.json", "result.fixture.json", "ticket.method", "create-ticket.mjs", "README.md"];
+}, {
+    readonly id: "support-triage";
+    readonly description: "Reads a help desk ticket, classifies its team, refund request, and urgency, drafts a first reply, updates the ticket, and asks a person when the team is unclear.";
+    readonly teaches: "models and secrets, classify with options, yes_no and levels, an unclear path, ask, effects with an http observer, a committed case, run_data: device, method connect";
+    readonly directory: "support-triage";
+    readonly entrypoint: "support-triage.method";
+    readonly lessonFiles: readonly ["TASK.md", "support-triage.method", "triage.mjs", "helpdesk.mjs", "read-ticket.mjs", "route.mjs", "set-ticket.mjs", "triage.test.mjs", "inputs.json", "cases/double-charge-to-billing/case.json", "README.md"];
+}, {
+    readonly id: "outbound-management";
+    readonly description: "Reads email and prospect sources, updates persistent CRM state, and saves daily tasks and outreach drafts for review.";
+    readonly teaches: "state across runs, script checks, examples of good output, accept, fixtures";
+    readonly directory: "outbound-management";
+    readonly entrypoint: "outbound.method";
+    readonly lessonFiles: readonly ["TASK.md", "outbound.method", "read_crm.py", "crm.py", "check_sources.py", "check_plan.py", "save_day.py", "starter/crm.json", "inputs.json", "fixtures/crm.json", "fixtures/observations.json", "fixtures/plan.json", "fixtures/tasks.md", "fixtures/receipt.json", "fixtures/state.json", "README.md"];
+}, {
+    readonly id: "social-briefing";
+    readonly description: "Researches a topic through Grok, alphaXiv, and LinkedIn in the browser, then writes a briefing with quotes and source links.";
+    readonly teaches: "browser agent, call, no_effect_reason, accept";
+    readonly directory: "social-briefing";
+    readonly entrypoint: "social-briefing.method";
+    readonly lessonFiles: readonly ["TASK.md", "social-briefing.method", "inputs.json", "result.fixture.json", "README.md"];
+}, {
+    readonly id: "daily-briefing";
+    readonly description: "Turns prepared records of one fictional day into a cited briefing website, using an approved writing example, a source check, and rendering scripts.";
+    readonly teaches: "approved example as an input, script tool, source check, website result";
+    readonly directory: "daily-briefing";
+    readonly entrypoint: "daily-briefing.method";
+    readonly lessonFiles: readonly ["TASK.md", "daily-briefing.method", "approved-report.md", "briefing_check_inputs.py", "briefing_files.py", "briefing_artifacts.py", "briefing_times.py", "briefing_sessions.py", "briefing_validation.py", "briefing_render.py", "briefing_manifest.py", "briefing_markdown.py", "briefing_website.py", "briefing_progress.py", "reader/reader.css", "reader/reader.js", "inputs.json", "sample-report.md", "README.md"];
+}];
+export declare function exampleDirectory(id: string): {
+    example: {
+        readonly id: "notes-summary";
+        readonly description: "The smallest complete Method: reads a folder of meeting notes, finds decisions and action items with one model call that shows two good items, and saves a summary file. A recorded case keeps one correction.";
+        readonly teaches: "files connection, call with examples of good output, a recorded case in cases/";
+        readonly directory: "notes-summary";
+        readonly entrypoint: "notes-summary.method";
+        readonly lessonFiles: readonly ["TASK.md", "notes-summary.method", "read-notes.mjs", "save.mjs", "cases/dates-in-decisions/case.json", "README.md"];
+    } | {
+        readonly id: "message-routing";
+        readonly description: "Classifies a customer message with Method's classifier, then a script rule chooses a support destination. ticket.method adds one ticket write that a retry does not repeat.";
+        readonly teaches: "classify with an unclear option, a threshold in a script, an effect that reads the ticket back, retry without a duplicate write";
+        readonly directory: "message-routing";
+        readonly entrypoint: "message-routing.method";
+        readonly lessonFiles: readonly ["TASK.md", "message-routing.method", "routing.mjs", "choose-destination.mjs", "inputs.json", "result.fixture.json", "ticket.method", "create-ticket.mjs", "README.md"];
+    } | {
+        readonly id: "support-triage";
+        readonly description: "Reads a help desk ticket, classifies its team, refund request, and urgency, drafts a first reply, updates the ticket, and asks a person when the team is unclear.";
+        readonly teaches: "models and secrets, classify with options, yes_no and levels, an unclear path, ask, effects with an http observer, a committed case, run_data: device, method connect";
+        readonly directory: "support-triage";
+        readonly entrypoint: "support-triage.method";
+        readonly lessonFiles: readonly ["TASK.md", "support-triage.method", "triage.mjs", "helpdesk.mjs", "read-ticket.mjs", "route.mjs", "set-ticket.mjs", "triage.test.mjs", "inputs.json", "cases/double-charge-to-billing/case.json", "README.md"];
+    } | {
+        readonly id: "outbound-management";
+        readonly description: "Reads email and prospect sources, updates persistent CRM state, and saves daily tasks and outreach drafts for review.";
+        readonly teaches: "state across runs, script checks, examples of good output, accept, fixtures";
+        readonly directory: "outbound-management";
+        readonly entrypoint: "outbound.method";
+        readonly lessonFiles: readonly ["TASK.md", "outbound.method", "read_crm.py", "crm.py", "check_sources.py", "check_plan.py", "save_day.py", "starter/crm.json", "inputs.json", "fixtures/crm.json", "fixtures/observations.json", "fixtures/plan.json", "fixtures/tasks.md", "fixtures/receipt.json", "fixtures/state.json", "README.md"];
+    } | {
+        readonly id: "social-briefing";
+        readonly description: "Researches a topic through Grok, alphaXiv, and LinkedIn in the browser, then writes a briefing with quotes and source links.";
+        readonly teaches: "browser agent, call, no_effect_reason, accept";
+        readonly directory: "social-briefing";
+        readonly entrypoint: "social-briefing.method";
+        readonly lessonFiles: readonly ["TASK.md", "social-briefing.method", "inputs.json", "result.fixture.json", "README.md"];
+    } | {
+        readonly id: "daily-briefing";
+        readonly description: "Turns prepared records of one fictional day into a cited briefing website, using an approved writing example, a source check, and rendering scripts.";
+        readonly teaches: "approved example as an input, script tool, source check, website result";
+        readonly directory: "daily-briefing";
+        readonly entrypoint: "daily-briefing.method";
+        readonly lessonFiles: readonly ["TASK.md", "daily-briefing.method", "approved-report.md", "briefing_check_inputs.py", "briefing_files.py", "briefing_artifacts.py", "briefing_times.py", "briefing_sessions.py", "briefing_validation.py", "briefing_render.py", "briefing_manifest.py", "briefing_markdown.py", "briefing_website.py", "briefing_progress.py", "reader/reader.css", "reader/reader.js", "inputs.json", "sample-report.md", "README.md"];
+    };
+    directory: string;
+};
+export declare function exampleCatalog(): string;
+export declare function renderExample(id: string, installedPaths?: boolean): string;

package/dist/packages/sdk/src/authoring-example.js

@@ -0,0 +1,50 @@
+import { exampleSelection } from "./authoring-instructions.js";
+import { readFileSync, existsSync } from 'node:fs';
+import { fileURLToPath } from 'node:url';
+export const authoringExamples = [
+    { id: 'notes-summary', description: 'The smallest complete Method: reads a folder of meeting notes, finds decisions and action items with one model call that shows two good items, and saves a summary file. A recorded case keeps one correction.', teaches: 'files connection, call with examples of good output, a recorded case in cases/', directory: 'notes-summary', entrypoint: 'notes-summary.method', lessonFiles: [
+            'TASK.md', 'notes-summary.method', 'read-notes.mjs', 'save.mjs', 'cases/dates-in-decisions/case.json', 'README.md',
+        ] },
+    { id: 'message-routing', description: "Classifies a customer message with Method's classifier, then a script rule chooses a support destination. ticket.method adds one ticket write that a retry does not repeat.", teaches: 'classify with an unclear option, a threshold in a script, an effect that reads the ticket back, retry without a duplicate write', directory: 'message-routing', entrypoint: 'message-routing.method', lessonFiles: [
+            'TASK.md', 'message-routing.method', 'routing.mjs', 'choose-destination.mjs', 'inputs.json', 'result.fixture.json', 'ticket.method', 'create-ticket.mjs', 'README.md',
+        ] },
+    { id: 'support-triage', description: 'Reads a help desk ticket, classifies its team, refund request, and urgency, drafts a first reply, updates the ticket, and asks a person when the team is unclear.', teaches: 'models and secrets, classify with options, yes_no and levels, an unclear path, ask, effects with an http observer, a committed case, run_data: device, method connect', directory: 'support-triage', entrypoint: 'support-triage.method', lessonFiles: [
+            'TASK.md', 'support-triage.method', 'triage.mjs', 'helpdesk.mjs', 'read-ticket.mjs', 'route.mjs', 'set-ticket.mjs', 'triage.test.mjs', 'inputs.json', 'cases/double-charge-to-billing/case.json', 'README.md',
+        ] },
+    { id: 'outbound-management', description: 'Reads email and prospect sources, updates persistent CRM state, and saves daily tasks and outreach drafts for review.', teaches: 'state across runs, script checks, examples of good output, accept, fixtures', directory: 'outbound-management', entrypoint: 'outbound.method', lessonFiles: [
+            'TASK.md', 'outbound.method', 'read_crm.py', 'crm.py', 'check_sources.py', 'check_plan.py', 'save_day.py', 'starter/crm.json', 'inputs.json', 'fixtures/crm.json', 'fixtures/observations.json', 'fixtures/plan.json', 'fixtures/tasks.md', 'fixtures/receipt.json', 'fixtures/state.json', 'README.md',
+        ] },
+    { id: 'social-briefing', description: 'Researches a topic through Grok, alphaXiv, and LinkedIn in the browser, then writes a briefing with quotes and source links.', teaches: 'browser agent, call, no_effect_reason, accept', directory: 'social-briefing', entrypoint: 'social-briefing.method', lessonFiles: [
+            'TASK.md', 'social-briefing.method', 'inputs.json', 'result.fixture.json', 'README.md',
+        ] },
+    { id: 'daily-briefing', description: 'Turns prepared records of one fictional day into a cited briefing website, using an approved writing example, a source check, and rendering scripts.', teaches: 'approved example as an input, script tool, source check, website result', directory: 'daily-briefing', entrypoint: 'daily-briefing.method', lessonFiles: [
+            'TASK.md', 'daily-briefing.method', 'approved-report.md', 'briefing_check_inputs.py', 'briefing_files.py', 'briefing_artifacts.py', 'briefing_times.py', 'briefing_sessions.py', 'briefing_validation.py', 'briefing_render.py', 'briefing_manifest.py', 'briefing_markdown.py', 'briefing_website.py', 'briefing_progress.py', 'reader/reader.css', 'reader/reader.js', 'inputs.json', 'sample-report.md', 'README.md',
+        ] },
+];
+export function exampleDirectory(id) {
+    const example = authoringExamples.find(example => example.id === id);
+    if (!example)
+        throw Error(`Unknown example '${id}'. Choose ${authoringExamples.map(example => example.id).join(', ')}.\n\n${exampleCatalog()}`);
+    return { example, directory: fileURLToPath(new URL(`../examples/${example.directory}/`, import.meta.url)) };
+}
+export function exampleCatalog() {
+    return '# Example catalog\n\n' + authoringExamples.map(example => `- \`method authoring example ${example.id}\`: ${example.description} Teaches: ${example.teaches}.`).join('\n') + '\n\n' + exampleSelection + '\n';
+}
+export function renderExample(id, installedPaths = true) {
+    const { example, directory } = exampleDirectory(id);
+    const files = JSON.parse(readFileSync(new URL('../examples/files.json', import.meta.url), 'utf8'));
+    const location = (name) => installedPaths ? directory + name : `${example.directory}/${name}`;
+    let result = `# Worked example: ${example.id}\n\n${example.description}\n\n`;
+    // The sample inputs show how the example runs.
+    const lessons = [...example.lessonFiles];
+    for (const name of [...lessons, ...['inputs.json'].filter(name => !lessons.includes(name) && existsSync(directory + name))]) {
+        const content = readFileSync(directory + name, 'utf8');
+        const language = name.endsWith('.method') ? 'yaml' : name.endsWith('.json') ? 'json' : name.endsWith('.py') ? 'python' : /\.(mjs|js)$/.test(name) ? 'javascript' : name.endsWith('.css') ? 'css' : 'markdown';
+        const runs = content.match(/`+/g) ?? [];
+        const fence = '`'.repeat(Math.max(3, ...runs.map(run => run.length + 1)));
+        result += `## ${name}\n\n${fence}${language}\n${content.trimEnd()}\n${fence}\n\n`;
+    }
+    result += '## Installed files\n\n';
+    result += files.filter(name => name.startsWith(example.directory + '/')).map(name => `- ${location(name.slice(example.directory.length + 1))}`).join('\n') + '\n';
+    return result;
+}

package/dist/packages/sdk/src/authoring-instructions.d.ts

@@ -0,0 +1,20 @@
+/** Shared authoring text; safe to import in the dashboard and public site. */
+export declare const authoringEntryRule = "Before creating, editing, or proposing a Method, run `method authoring` and read its guidance. Do this before choosing an existing Method as a reference.";
+export declare const checkEditingRule = "Existing checks and tests are implementation choices, not user requirements. Remove a check that is unnecessary, repeats other validation, or enforces a requirement that nobody asked for. Delete the tests and instructions that exist only for it, and do not replace it. Do not change useful output only to satisfy a check.";
+export declare const designProcedure = "# Choose the design\n\n| Requirement | Step type |\n| --- | --- |\n| Fixed rules, calculations, file changes, or an API that is not a model | run |\n| A structured model answer from supplied information | call |\n| Model-directed investigation or tool use | agent |\n| A choice from named options, a yes/no, or a score on ordered levels, with probabilities | classify |\n| An answer or decision that must come from the user | ask |\n\nFor browser work, declare a browser environment and select it with do.browser: environment.NAME; see method authoring example social-briefing.\n\nAdd a check only when it catches a failure that matters to the result. A change to a service, an API, email, or a browser that sends needs an effect that reads the result back; local file writes need neither. When you convert existing code, do not keep its checks and tests only because they exist. The rules are in method authoring concepts.\n\nUse when for conditions, each for collections, repeat for bounded iteration, and after for order without a data dependency. Split steps for a check, a retry, a human decision, or an external change.\n";
+/** The full check rules; in concepts. */
+export declare const checkRules = "# Checks\n\nAdd a check only when it catches a concrete failure that matters to the result. Output types and the runtime already validate shapes; do not repeat them. Do not check wording, headings, keywords, lengths, or counts unless the task requires them: \"write accurate prose\" is not a reason to match strings.\n\nUse the simplest check that proves the fact: a built-in equals, count, present, or file check, a script, or an agent check. Local file writes need no check: the runtime observes files connections itself. A change to a service, an API, email, or a browser that sends needs an effect that reads the result back, because a receipt or a 200 status shows only that the request was accepted. Use a built-in observer (http, sqlite, file) when one fits. When a change cannot or need not be observed, such as a browser step that only reads, write no_effect_reason instead.\n\nExisting checks and tests are implementation choices, not user requirements. Remove a check that is unnecessary, repeats other validation, or enforces a requirement that nobody asked for. Delete the tests and instructions that exist only for it, and do not replace it. Do not change useful output only to satisfy a check.\n";
+/** The rules that make a first Method work quickly. They come before every other part of the guide. */
+export declare const firstMethodRules = "# Build a Method\n\n1. **Sign in first.** Run `method status`. If it is not signed in, run `method login` and let the user approve in the browser. Signed in, model and classification steps need no keys, each run saves a version when the file changed, and runs appear on the dashboard.\n2. **Each model or classifier request is its own step**: `call`, `agent`, or `classify`, with its prompt in the Method, so the user can change one prompt, run again, and compare. A script never calls a model API. When the user already has code that does the work, keep its fixed logic as `run` steps and move each prompt and rubric into its own step; do not wrap the code. \"The same thing\" means the same behavior in steps. If a request cannot become a step because Method lacks a feature, tell the user what is missing.\n3. **Show the design, then build it in the same turn.** Show each step with its type, purpose, and output, and a table of the prompts and rubrics in the user's existing work, each with the step that holds it. Do not wait for approval unless the user asked to approve first. Ask only for information that you cannot find and that would change the design.\n4. **Run early and often.** Write the first steps, validate, run, then add the next steps. Fix errors. Fix each warning, or accept it with the user's reason. Never add a check only to remove a warning. A new run reuses every step whose definition and inputs did not change, so each run executes only what changed. `--rerun STEP` runs a step again anyway; `--fresh` runs every step.\n5. **Keep the inputs of the existing code.** If the code takes an ID and looks up the record, the Method takes the same ID and looks it up the same way.\n6. **Use the defaults without asking.** Model steps use the account's hosted models and `classify` uses Method's classifier, so no model or classifier keys are needed. To keep the model that existing code uses, add `models: {writer: provider/model}` to the Method and use `model: writer` in the steps (or `model: provider/model` on the step); it needs no key. Keep the models that the Method or the existing code names: when a model step fails, show the error and ask before you change its model. Run records go to the user's account. When the user asks that run data stay on this computer or not be uploaded, set `run_data: device`: the run's inputs, outputs, and files stay here, and the account keeps only each step's status and timing. Model steps still send each step's input to the model to answer it; nothing is kept. Tell the user that in one line, then run again.\n7. **Keys stay out of chat.** Declare each key that a script needs under `secrets:` with its purpose; every script of the Method receives all of its declared secrets. Run `method secret find` in the Method's folder: it lists the key files nearby and the names in each, never the values, and prints the import command. Run that command and tell the user which file each key came from: the key stays on this computer, so there is nothing to ask. If it finds nothing, ask the user to run `method secret set NAME`, which opens a private form in their browser. Never open, print, or search a key file (`cat`, `grep`, an editor), including Method's own secret store, and never ask for a value in chat: the values would go into the chat. When a run says Method's model credit is used up, run `method config model-key` yourself: it takes the user's own OpenRouter key from the one nearby key file that holds it, or opens a private form for it. Then run again.\n8. **Choose a sample yourself** from the user's data, and check that it has the sources the Method needs. Ask only when there is no good sample.\n9. **Iterate.** After a good run, show the result and the dashboard link, and ask what to change. Change the step and run again. Show only results that a run made: never write or edit a result by hand, and fix a wrong result in the Method, not in the data it reads. If you cannot run, say so.\n10. **Publish** with `method publish FILE --reason TEXT` when the user wants to share or schedule a version. It runs the Method's cases first.\n\nWhen a run fails, read its `fix` and `diagnostics`, change the step, and run again.\n";
+/** How to write the prompt inside a call, agent, or classify step. */
+export declare const promptRules = "# Write each prompt\n\n- **One task per prompt.** If a prompt says \"then\" or has several jobs, make several steps.\n- **Say what to do.** Leave out background that does not change the output.\n- **Show 1 to 3 examples of good output.** Take them from the user's work: examples in an existing prompt, a past output that the user approved, or the first run that the user accepts. Pass a long example as an input, not as text in the prompt.\n- **Put the output shape in `out`**, not in the prompt.\n- **Say what to do when the input does not have the answer**, for example \"leave due empty\". For classify, add an option such as `unclear`.\n\nBefore:\n\n```text\nYou are an expert support analyst with years of experience. Our company values clear\ncommunication. Read the tickets, decide which ones are urgent, write a summary, and\nreturn JSON with a \"summary\" key. Make it good.\n```\n\nAfter (urgency is a classify step before this one; the shape is in `out`):\n\n```text\nWrite a five-sentence summary of this week's support tickets for the team.\nStart with the high-urgency tickets. Quote no customer names.\nWrite it in the style of this summary from an earlier week:\n\n{{example}}\n```\n";
+/** Enough of the format to write a Method without reading the JSON schema. */
+export declare const fieldReference = "# Field reference\n\n```text\nformat: method/3.4\nname, goal          text\ninputs              {NAME: DATA}           values the run receives (--inputs FILE)\nsecrets             {NAME: purpose}        keys that scripts receive as environment variables\nenvironment         {NAME: {type: files | service | browser | desktop | tool, description}}\nfiles               [PATH]                 helper files that scripts import or read\nsteps               {ID: STEP}\nresult              REF, or {NAME: REF}\nrun_data            account (default) | device\n\nDATA   {type: text | number | boolean | record | list | file, description,\n        fields: {NAME: TYPE}   (a record, or a list of records)\n        items: TYPE            (a list of one type)\n        default: VALUE}        A bare type such as text works inside fields and items.\nREF    inputs.NAME | an output NAME | NAME.field | state.NAME | environment.NAME\n\nSTEP   name, purpose          give a run step both; purpose states its rules, result, and external changes\n       in: {ALIAS: REF}       the values that the step receives\n       each: {ITEM: LIST_REF} run once per item; ITEM is given to the step, so do not repeat it in in\n       concurrency: 1-32      items at once, for an each step that changes nothing\n       when: BOOLEAN_REF      after: ID or [ID]      repeat: {max_iterations, until: BOOLEAN_OUTPUT}\n       do: one of\n         {kind: run, runtime: python | node, entrypoint: FILE, args: [...]}\n             reads one JSON object (its in) on stdin, prints one JSON object (its out); files go under $METHOD_OUTPUT_DIR\n         {kind: call, model: NAME, prompt: TEXT}\n             the step's in go to the model as JSON; {{ALIAS}} puts a text, number, or boolean value into the prompt\n         {kind: agent, model: NAME, prompt: TEXT, tools: [TOOL]}\n         {kind: classify, question: TEXT, options: {ID: description}}   value: {choice, probabilities}\n         {kind: classify, question: TEXT, answer: yes_no}                value: {answer, probability} (of yes)\n         {kind: classify, question: TEXT, levels: [LOW, ..., HIGH]}      value: {level, score, probabilities}; 2-10 levels\n             Do counting, math, and date comparisons in a run step; the classifier reads the question literally. Choose thresholds from a few labeled samples.\n       ask: TEXT              in place of do: a question for the user\n       out: {NAME: DATA}      (classify: out: NAME)\n       changes: [state.NAME | environment.NAME]; a service change needs effects or no_effect_reason\n       check, limits: {timeout_ms, max_model_requests, max_agent_turns}\n       accept: {CODE: reason}   keep a warning or note with the user's reason\n\nmodels: {NAME: provider/model | {model, max_output_tokens, reasoning_effort}}   hosted models; no key. A step without model uses the account default.\n        NAME: {agent: codex | claude, model, reasoning_effort}   a step with model: NAME runs on that local agent (it must be installed); --agent still overrides.\nlimits: {timeout_ms, max_model_requests, max_invocations, max_tool_calls, max_concurrency, ..., step: {timeout_ms, max_agent_turns, max_model_requests}}\ntools:  {NAME: {description, in, out, run, effects}}   script tools that agent steps list in tools\nid: wf_...   written by the CLI at the first signed-in save; keep it. method new-id FILE makes a copy a new Method.\nConnections: a files connection uses the folder NAME beside the Method, or method bind FILE NAME --file PATH (this computer only).\nIssues: errors block; warnings and notes do not.\n```\n\n`method schema method` prints the complete JSON schema.\n";
+export declare const designExamples = "# Contrasting design outlines\n\nThese are design outlines, not runnable Method files.\n\n| Request | Design | Explanation |\n| --- | --- | --- |\n| Summarize supplied text | call \u2192 return summary | The model receives all source text. Add a save step only if a saved file is requested. Use an agent if it must find or inspect additional sources. |\n| Investigate a claim | agent to research and assess \u2192 return findings | Add a separate planning, checking, or saving step only when the task needs that boundary or result. When the user requires that the findings say only what the sources say, add an agent check on the assess step (method authoring recipes). |\n| Route a message with human review for low confidence | classify \u2192 threshold run \u2192 conditional ask | Classification returns probabilities. Code applies the threshold. Human input resolves cases below the threshold. Add a separate action with an effect if the Method must send or change anything. |\n| Send a daily summary email | call to write \u2192 run to send, with an effect | The send script puts METHOD_OPERATION_ID in the Message-ID. A mail.delivery effect searches the bounce mailbox through its own read-only connection until a 5-day horizon. A bounce fails the run; no bounce by the horizon is unrefuted, not proven. |\n";
+/** Cost rules for a design; in concepts, not in the start of the guide. */
+export declare const costRules = "Before describing execution cost, check how the model steps run. With hosted models, a call is one request without tools, and an agent step can make several requests and use tools. With --agent, each model step starts a local agent process. State the expected model requests and agent processes when they are known; mark unknown counts as unknown.";
+/** What to watch after a Method works. */
+export declare const watchRules = "# Watch it\n\n- Look at failed and unconfirmed runs on the dashboard. A run that needs attention says which step failed and why.\n- For classify, watch how often the choice is `unclear` or below your threshold. A rise means the inputs changed.\n- For slow effects such as email delivery, schedule `method observe --pending`.\n";
+/** What to do after a Method works: production, improvement, and script cards. */
+export declare const afterRules = "# After it works\n\n- **Put it in an app:** `method connect APP_FOLDER` publishes it and prints the code to add.\n- **Improve the results:** when the user wants the results changed, `method improve FILE --note TEXT` makes a proposal from the recent runs; `method apply FILE` merges it.\n- **Explain the scripts:** `method explain FILE` writes a card for each script step.\n";
+export declare const exampleSelection = "After choosing the step types, read the examples that fit the design. Use their syntax; choose the steps for this task yourself.";

package/dist/packages/sdk/src/authoring-instructions.js

@@ -0,0 +1,151 @@
+/** Shared authoring text; safe to import in the dashboard and public site. */
+export const authoringEntryRule = "Before creating, editing, or proposing a Method, run `method authoring` and read its guidance. Do this before choosing an existing Method as a reference.";
+export const checkEditingRule = "Existing checks and tests are implementation choices, not user requirements. Remove a check that is unnecessary, repeats other validation, or enforces a requirement that nobody asked for. Delete the tests and instructions that exist only for it, and do not replace it. Do not change useful output only to satisfy a check.";
+export const designProcedure = `# Choose the design
+
+| Requirement | Step type |
+| --- | --- |
+| Fixed rules, calculations, file changes, or an API that is not a model | run |
+| A structured model answer from supplied information | call |
+| Model-directed investigation or tool use | agent |
+| A choice from named options, a yes/no, or a score on ordered levels, with probabilities | classify |
+| An answer or decision that must come from the user | ask |
+
+For browser work, declare a browser environment and select it with do.browser: environment.NAME; see method authoring example social-briefing.
+
+Add a check only when it catches a failure that matters to the result. A change to a service, an API, email, or a browser that sends needs an effect that reads the result back; local file writes need neither. When you convert existing code, do not keep its checks and tests only because they exist. The rules are in method authoring concepts.
+
+Use when for conditions, each for collections, repeat for bounded iteration, and after for order without a data dependency. Split steps for a check, a retry, a human decision, or an external change.
+`;
+/** The full check rules; in concepts. */
+export const checkRules = `# Checks
+
+Add a check only when it catches a concrete failure that matters to the result. Output types and the runtime already validate shapes; do not repeat them. Do not check wording, headings, keywords, lengths, or counts unless the task requires them: "write accurate prose" is not a reason to match strings.
+
+Use the simplest check that proves the fact: a built-in equals, count, present, or file check, a script, or an agent check. Local file writes need no check: the runtime observes files connections itself. A change to a service, an API, email, or a browser that sends needs an effect that reads the result back, because a receipt or a 200 status shows only that the request was accepted. Use a built-in observer (http, sqlite, file) when one fits. When a change cannot or need not be observed, such as a browser step that only reads, write no_effect_reason instead.
+
+${checkEditingRule}
+`;
+/** The rules that make a first Method work quickly. They come before every other part of the guide. */
+export const firstMethodRules = `# Build a Method
+
+1. **Sign in first.** Run \`method status\`. If it is not signed in, run \`method login\` and let the user approve in the browser. Signed in, model and classification steps need no keys, each run saves a version when the file changed, and runs appear on the dashboard.
+2. **Each model or classifier request is its own step**: \`call\`, \`agent\`, or \`classify\`, with its prompt in the Method, so the user can change one prompt, run again, and compare. A script never calls a model API. When the user already has code that does the work, keep its fixed logic as \`run\` steps and move each prompt and rubric into its own step; do not wrap the code. "The same thing" means the same behavior in steps. If a request cannot become a step because Method lacks a feature, tell the user what is missing.
+3. **Show the design, then build it in the same turn.** Show each step with its type, purpose, and output, and a table of the prompts and rubrics in the user's existing work, each with the step that holds it. Do not wait for approval unless the user asked to approve first. Ask only for information that you cannot find and that would change the design.
+4. **Run early and often.** Write the first steps, validate, run, then add the next steps. Fix errors. Fix each warning, or accept it with the user's reason. Never add a check only to remove a warning. A new run reuses every step whose definition and inputs did not change, so each run executes only what changed. \`--rerun STEP\` runs a step again anyway; \`--fresh\` runs every step.
+5. **Keep the inputs of the existing code.** If the code takes an ID and looks up the record, the Method takes the same ID and looks it up the same way.
+6. **Use the defaults without asking.** Model steps use the account's hosted models and \`classify\` uses Method's classifier, so no model or classifier keys are needed. To keep the model that existing code uses, add \`models: {writer: provider/model}\` to the Method and use \`model: writer\` in the steps (or \`model: provider/model\` on the step); it needs no key. Keep the models that the Method or the existing code names: when a model step fails, show the error and ask before you change its model. Run records go to the user's account. When the user asks that run data stay on this computer or not be uploaded, set \`run_data: device\`: the run's inputs, outputs, and files stay here, and the account keeps only each step's status and timing. Model steps still send each step's input to the model to answer it; nothing is kept. Tell the user that in one line, then run again.
+7. **Keys stay out of chat.** Declare each key that a script needs under \`secrets:\` with its purpose; every script of the Method receives all of its declared secrets. Run \`method secret find\` in the Method's folder: it lists the key files nearby and the names in each, never the values, and prints the import command. Run that command and tell the user which file each key came from: the key stays on this computer, so there is nothing to ask. If it finds nothing, ask the user to run \`method secret set NAME\`, which opens a private form in their browser. Never open, print, or search a key file (\`cat\`, \`grep\`, an editor), including Method's own secret store, and never ask for a value in chat: the values would go into the chat. When a run says Method's model credit is used up, run \`method config model-key\` yourself: it takes the user's own OpenRouter key from the one nearby key file that holds it, or opens a private form for it. Then run again.
+8. **Choose a sample yourself** from the user's data, and check that it has the sources the Method needs. Ask only when there is no good sample.
+9. **Iterate.** After a good run, show the result and the dashboard link, and ask what to change. Change the step and run again. Show only results that a run made: never write or edit a result by hand, and fix a wrong result in the Method, not in the data it reads. If you cannot run, say so.
+10. **Publish** with \`method publish FILE --reason TEXT\` when the user wants to share or schedule a version. It runs the Method's cases first.
+
+When a run fails, read its \`fix\` and \`diagnostics\`, change the step, and run again.
+`;
+/** How to write the prompt inside a call, agent, or classify step. */
+export const promptRules = `# Write each prompt
+
+- **One task per prompt.** If a prompt says "then" or has several jobs, make several steps.
+- **Say what to do.** Leave out background that does not change the output.
+- **Show 1 to 3 examples of good output.** Take them from the user's work: examples in an existing prompt, a past output that the user approved, or the first run that the user accepts. Pass a long example as an input, not as text in the prompt.
+- **Put the output shape in \`out\`**, not in the prompt.
+- **Say what to do when the input does not have the answer**, for example "leave due empty". For classify, add an option such as \`unclear\`.
+
+Before:
+
+\`\`\`text
+You are an expert support analyst with years of experience. Our company values clear
+communication. Read the tickets, decide which ones are urgent, write a summary, and
+return JSON with a "summary" key. Make it good.
+\`\`\`
+
+After (urgency is a classify step before this one; the shape is in \`out\`):
+
+\`\`\`text
+Write a five-sentence summary of this week's support tickets for the team.
+Start with the high-urgency tickets. Quote no customer names.
+Write it in the style of this summary from an earlier week:
+
+{{example}}
+\`\`\`
+`;
+/** Enough of the format to write a Method without reading the JSON schema. */
+export const fieldReference = `# Field reference
+
+\`\`\`text
+format: method/3.4
+name, goal          text
+inputs              {NAME: DATA}           values the run receives (--inputs FILE)
+secrets             {NAME: purpose}        keys that scripts receive as environment variables
+environment         {NAME: {type: files | service | browser | desktop | tool, description}}
+files               [PATH]                 helper files that scripts import or read
+steps               {ID: STEP}
+result              REF, or {NAME: REF}
+run_data            account (default) | device
+
+DATA   {type: text | number | boolean | record | list | file, description,
+        fields: {NAME: TYPE}   (a record, or a list of records)
+        items: TYPE            (a list of one type)
+        default: VALUE}        A bare type such as text works inside fields and items.
+REF    inputs.NAME | an output NAME | NAME.field | state.NAME | environment.NAME
+
+STEP   name, purpose          give a run step both; purpose states its rules, result, and external changes
+       in: {ALIAS: REF}       the values that the step receives
+       each: {ITEM: LIST_REF} run once per item; ITEM is given to the step, so do not repeat it in in
+       concurrency: 1-32      items at once, for an each step that changes nothing
+       when: BOOLEAN_REF      after: ID or [ID]      repeat: {max_iterations, until: BOOLEAN_OUTPUT}
+       do: one of
+         {kind: run, runtime: python | node, entrypoint: FILE, args: [...]}
+             reads one JSON object (its in) on stdin, prints one JSON object (its out); files go under $METHOD_OUTPUT_DIR
+         {kind: call, model: NAME, prompt: TEXT}
+             the step's in go to the model as JSON; {{ALIAS}} puts a text, number, or boolean value into the prompt
+         {kind: agent, model: NAME, prompt: TEXT, tools: [TOOL]}
+         {kind: classify, question: TEXT, options: {ID: description}}   value: {choice, probabilities}
+         {kind: classify, question: TEXT, answer: yes_no}                value: {answer, probability} (of yes)
+         {kind: classify, question: TEXT, levels: [LOW, ..., HIGH]}      value: {level, score, probabilities}; 2-10 levels
+             Do counting, math, and date comparisons in a run step; the classifier reads the question literally. Choose thresholds from a few labeled samples.
+       ask: TEXT              in place of do: a question for the user
+       out: {NAME: DATA}      (classify: out: NAME)
+       changes: [state.NAME | environment.NAME]; a service change needs effects or no_effect_reason
+       check, limits: {timeout_ms, max_model_requests, max_agent_turns}
+       accept: {CODE: reason}   keep a warning or note with the user's reason
+
+models: {NAME: provider/model | {model, max_output_tokens, reasoning_effort}}   hosted models; no key. A step without model uses the account default.
+        NAME: {agent: codex | claude, model, reasoning_effort}   a step with model: NAME runs on that local agent (it must be installed); --agent still overrides.
+limits: {timeout_ms, max_model_requests, max_invocations, max_tool_calls, max_concurrency, ..., step: {timeout_ms, max_agent_turns, max_model_requests}}
+tools:  {NAME: {description, in, out, run, effects}}   script tools that agent steps list in tools
+id: wf_...   written by the CLI at the first signed-in save; keep it. method new-id FILE makes a copy a new Method.
+Connections: a files connection uses the folder NAME beside the Method, or method bind FILE NAME --file PATH (this computer only).
+Issues: errors block; warnings and notes do not.
+\`\`\`
+
+\`method schema method\` prints the complete JSON schema.
+`;
+export const designExamples = `# Contrasting design outlines
+
+These are design outlines, not runnable Method files.
+
+| Request | Design | Explanation |
+| --- | --- | --- |
+| Summarize supplied text | call → return summary | The model receives all source text. Add a save step only if a saved file is requested. Use an agent if it must find or inspect additional sources. |
+| Investigate a claim | agent to research and assess → return findings | Add a separate planning, checking, or saving step only when the task needs that boundary or result. When the user requires that the findings say only what the sources say, add an agent check on the assess step (method authoring recipes). |
+| Route a message with human review for low confidence | classify → threshold run → conditional ask | Classification returns probabilities. Code applies the threshold. Human input resolves cases below the threshold. Add a separate action with an effect if the Method must send or change anything. |
+| Send a daily summary email | call to write → run to send, with an effect | The send script puts METHOD_OPERATION_ID in the Message-ID. A mail.delivery effect searches the bounce mailbox through its own read-only connection until a 5-day horizon. A bounce fails the run; no bounce by the horizon is unrefuted, not proven. |
+`;
+/** Cost rules for a design; in concepts, not in the start of the guide. */
+export const costRules = "Before describing execution cost, check how the model steps run. With hosted models, a call is one request without tools, and an agent step can make several requests and use tools. With --agent, each model step starts a local agent process. State the expected model requests and agent processes when they are known; mark unknown counts as unknown.";
+/** What to watch after a Method works. */
+export const watchRules = `# Watch it
+
+- Look at failed and unconfirmed runs on the dashboard. A run that needs attention says which step failed and why.
+- For classify, watch how often the choice is \`unclear\` or below your threshold. A rise means the inputs changed.
+- For slow effects such as email delivery, schedule \`method observe --pending\`.
+`;
+/** What to do after a Method works: production, improvement, and script cards. */
+export const afterRules = `# After it works
+
+- **Put it in an app:** \`method connect APP_FOLDER\` publishes it and prints the code to add.
+- **Improve the results:** when the user wants the results changed, \`method improve FILE --note TEXT\` makes a proposal from the recent runs; \`method apply FILE\` merges it.
+- **Explain the scripts:** \`method explain FILE\` writes a card for each script step.
+`;
+export const exampleSelection = "After choosing the step types, read the examples that fit the design. Use their syntax; choose the steps for this task yourself.";

package/dist/packages/sdk/src/authoring-prompt.d.ts

@@ -0,0 +1,2 @@
+/** The prompt for agents without the Method plugin. The installed guide holds the rules; this prompt only starts them. */
+export declare const authoringPrompt = "Help me turn repeated work into a Method with the Method CLI. Do the setup first, without asking me:\n\n1. If `which method` finds nothing, install Method now with `curl -fsSL https://app.withmethod.ai/install.sh | sh`. I approve this installer.\n2. Run `method login` and wait while I approve the sign-in in my browser.\n3. Run `method authoring` and follow it.\n\nThen ask me what work to turn into a Method. Make each prompt its own step, so that I can improve it. Run it on a sample, show me the result and the dashboard link, and ask me what to change.";

package/dist/packages/sdk/src/authoring-prompt.js

@@ -0,0 +1,8 @@
+/** The prompt for agents without the Method plugin. The installed guide holds the rules; this prompt only starts them. */
+export const authoringPrompt = `Help me turn repeated work into a Method with the Method CLI. Do the setup first, without asking me:
+
+1. If \`which method\` finds nothing, install Method now with \`curl -fsSL https://app.withmethod.ai/install.sh | sh\`. I approve this installer.
+2. Run \`method login\` and wait while I approve the sign-in in my browser.
+3. Run \`method authoring\` and follow it.
+
+Then ask me what work to turn into a Method. Make each prompt its own step, so that I can improve it. Run it on a sample, show me the result and the dashboard link, and ask me what to change.`;

package/dist/packages/sdk/src/authoring.d.ts

@@ -0,0 +1,10 @@
+export declare function writeDocument(path: string, value: unknown): void;
+export declare const authoringHelp: string;
+export declare function authoringPath(path: string): string;
+export declare const readDocument: (file: string) => any;
+export declare function at(document: any, path: string): any;
+export declare function change(document: any, path: string, value: any, remove?: boolean): any;
+/** Read, change, and replace the file in one rename. */
+export declare function editDocument(file: string, edit: (doc: any) => any): any;
+export declare function differences(a: any, b: any, path?: string): any[];
+export declare function localAuthoring(args: string[]): Promise<boolean>;