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

package/dist/packages/sdk/examples/message-routing/message-routing.method

@@ -0,0 +1,45 @@
+format: method/3.4
+name: Classify and route a customer message
+goal: Choose a support destination and show the rule used.
+inputs:
+  message:
+    type: text
+    description: The complete customer message to classify.
+steps:
+  classify_message:
+    name: Classify the customer message
+    in:
+      message: inputs.message
+    do:
+      kind: classify
+      question: Which team should handle the main request in this message?
+      options:
+        billing: Billing — invoices, charges, refunds, and payments.
+        technical: Technical support — errors and problems using the product.
+        unclear: Unclear — the message does not say enough to choose, or no listed team fits.
+    out: message_category
+  choose_destination:
+    name: Choose the destination
+    purpose: |
+      Chooses Billing or Technical support when that category is selected
+      and its probability is at least 90%. Otherwise chooses Manual review.
+      Returns the destination, the rule used, and the probability and threshold.
+    in:
+      category: message_category
+    do:
+      kind: run
+      runtime: node
+      entrypoint: choose-destination.mjs
+    out:
+      routing:
+        type: record
+        description: The selected destination and the values used to choose it.
+        fields:
+          destination: text
+          rule_applied: text
+          selected_probability: number
+          required_probability: number
+result: routing
+files:
+  - routing.mjs
+run_prompt: Run this Method with the customer message, then show the destination and the rule used.

package/dist/packages/sdk/examples/message-routing/result.fixture.json

@@ -0,0 +1,6 @@
+{
+  "destination": "billing",
+  "rule_applied": "selected_category_meets_threshold",
+  "selected_probability": 0.94,
+  "required_probability": 0.9
+}

package/dist/packages/sdk/examples/message-routing/routing.mjs

@@ -0,0 +1,29 @@
+export function chooseDestination(category) {
+  const ids = ['billing', 'technical', 'unclear'];
+  if (!category || !ids.includes(category.choice)) {
+    throw new Error('Expected a declared category.');
+  }
+  const probabilities = category.probabilities;
+  if (!probabilities || Object.keys(probabilities).length !== ids.length ||
+      ids.some(id => !Object.hasOwn(probabilities, id) ||
+        !Number.isFinite(probabilities[id]) ||
+        probabilities[id] < 0 || probabilities[id] > 1)) {
+    throw new Error('Expected one valid probability per category.');
+  }
+  if (Math.abs(ids.reduce((sum, id) => sum + probabilities[id], 0) - 1) > 1e-6 ||
+      probabilities[category.choice] + 1e-6 < Math.max(...ids.map(id => probabilities[id]))) {
+    throw new Error('Expected a valid distribution and a maximum-probability choice.');
+  }
+  const required = 0.90;
+  const observed = probabilities[category.choice];
+  const automatic = category.choice !== 'unclear' && observed >= required;
+  return {
+    routing: {
+      destination: automatic ? category.choice : 'manual_review',
+      rule_applied: category.choice === 'unclear' ? 'unclear_requires_review' :
+        automatic ? 'selected_category_meets_threshold' : 'below_threshold',
+      selected_probability: observed,
+      required_probability: required
+    }
+  };
+}

package/dist/packages/sdk/examples/message-routing/routing.test.mjs

@@ -0,0 +1,27 @@
+import test from 'node:test';
+import assert from 'node:assert/strict';
+import { chooseDestination } from './routing.mjs';
+const classify = (choice, billing, technical, unclear) =>
+  ({choice, probabilities: {billing, technical, unclear}});
+test('accepts the exact threshold', () => {
+  const r = chooseDestination(classify('billing', .90, .08, .02)).routing;
+  assert.equal(r.destination, 'billing');
+  assert.equal(r.rule_applied, 'selected_category_meets_threshold');
+});
+test('routes below the threshold to manual review', () => {
+  const r = chooseDestination(classify('billing', .899, .081, .02)).routing;
+  assert.equal(r.destination, 'manual_review');
+  assert.equal(r.rule_applied, 'below_threshold');
+});
+test('unclear always requires review', () => {
+  const r = chooseDestination(classify('unclear', 0, 0, 1)).routing;
+  assert.equal(r.destination, 'manual_review');
+  assert.equal(r.rule_applied, 'unclear_requires_review');
+});
+test('routes technical support independently', () => {
+  assert.equal(chooseDestination(classify('technical', .03, .95, .02)).routing.destination, 'technical');
+});
+test('rejects missing or invalid input', () => {
+  assert.throws(() => chooseDestination(null));
+  assert.throws(() => chooseDestination(classify('billing', .9, .9, 0)));
+});

package/dist/packages/sdk/examples/message-routing/ticket.method

@@ -0,0 +1,88 @@
+format: method/3.4
+name: Route a message and create one ticket
+goal: Create a ticket and recover an interrupted response without a duplicate write.
+inputs:
+  message:
+    type: text
+    description: The complete customer message to classify.
+steps:
+  classify_message:
+    name: Classify the customer message
+    in:
+      message: inputs.message
+    do:
+      kind: classify
+      question: Which team should handle the main request in this message?
+      options:
+        billing: Billing — invoices, charges, refunds, and payments.
+        technical: Technical support — errors and problems using the product.
+        unclear: Unclear — the message does not say enough to choose, or no listed team fits.
+    out: message_category
+  choose_destination:
+    name: Choose the destination
+    purpose: |
+      Chooses Billing or Technical support when that category is selected
+      and its probability is at least 90%. Otherwise chooses Manual review.
+      Returns the destination, the rule used, and the probability and threshold.
+    in:
+      category: message_category
+    do:
+      kind: run
+      runtime: node
+      entrypoint: choose-destination.mjs
+    out:
+      routing:
+        type: record
+        description: The selected destination and the values used to choose it.
+        fields:
+          destination: text
+          rule_applied: text
+          selected_probability: number
+          required_probability: number
+  create_ticket:
+    name: Create the support ticket
+    purpose: Creates a ticket for the selected destination and returns its receipt.
+      Sends the operation ID as the Idempotency-Key, so a retry returns the same
+      ticket. The saved effect reads the ticket back by the operation ID.
+    in:
+      message: inputs.message
+      routing: routing
+      service: environment.ticket_service
+    do:
+      kind: run
+      runtime: node
+      entrypoint: create-ticket.mjs
+    changes:
+      - environment.ticket_service
+    out:
+      ticket:
+        type: record
+        description: The service receipt for this operation.
+        fields:
+          ticket_id: text
+          operation_id: text
+    effects:
+      saved:
+        intent: The ticket service stores one ticket for this operation with the
+          submitted message and destination.
+        in:
+          message: inputs.message
+          destination: routing.destination
+        observe:
+          kind: http
+          path: /tickets/by-operation/{token}
+          expect:
+            fields:
+              operation_id: "{token}"
+              message: "{inputs.message}"
+              destination: "{inputs.destination}"
+        blocking: true
+result: ticket
+files:
+  - routing.mjs
+run_prompt: Run this Method with the customer message, then show the destination
+  and the rule used.
+environment:
+  ticket_service:
+    type: service
+    description: Ticket service with idempotent writes and operation lookup.

package/dist/packages/sdk/examples/message-routing/ticket.test.mjs

@@ -0,0 +1,64 @@
+import test from 'node:test';
+import assert from 'node:assert/strict';
+import {createServer} from 'node:http';
+import {mkdtemp,cp,readFile,writeFile,rm} from 'node:fs/promises';
+import {tmpdir} from 'node:os';
+import {join} from 'node:path';
+import {fileURLToPath} from 'node:url';
+import {parse,stringify} from 'yaml';
+import {runMethod} from '@withmethod/runtime';
+
+test('retry reuses the operation ID after the service commits and before stdout returns', async t => {
+  const root=await mkdtemp(join(tmpdir(),'method-ticket-retry-'));
+  t.after(()=>rm(root,{recursive:true,force:true}));
+  const records=new Map(), writes=[];
+  let committed;
+  const saved=new Promise(resolve=>committed=resolve);
+  let first=true;
+  const server=createServer(async(req,res)=>{
+    let body='';for await(const chunk of req)body+=chunk;
+    res.setHeader('content-type','application/json');
+    if(req.url==='/committed') {
+      if(first){first=false;committed();return;}
+      res.end('{}');return;
+    }
+    if(req.method==='POST'&&req.url==='/tickets') {
+      const key=req.headers['idempotency-key'],payload=JSON.parse(body),prior=records.get(key);
+      writes.push(key);
+      if(prior&&(prior.message!==payload.message||prior.destination!==payload.destination)){res.statusCode=409;res.end('{}');return;}
+      const record=prior??{ticket_id:'ticket-'+(records.size+1),operation_id:key,...payload};
+      records.set(key,record);res.end(JSON.stringify({ticket_id:record.ticket_id,operation_id:key}));return;
+    }
+    const record=records.get(decodeURIComponent(req.url.split('/').at(-1)));
+    res.statusCode=record?200:404;res.end(JSON.stringify(record??{}));
+  });
+  await new Promise(resolve=>server.listen(0,'127.0.0.1',resolve));
+  t.after(()=>{server.closeAllConnections();server.close();});
+  const url=`http://127.0.0.1:${server.address().port}`;
+  await cp(fileURLToPath(new URL('./',import.meta.url)),root,{recursive:true});
+  const method=parse(await readFile(join(root,'ticket.method'),'utf8'));
+  // The handshake exists only in this test wrapper. The real action has no test hooks.
+  method.steps.create_ticket.do.entrypoint='fixture-action.mjs';
+  method.files.push('create-ticket.mjs');
+  await writeFile(join(root,'fixture-action.mjs'),`const write=process.stdout.write.bind(process.stdout);process.stdout.write=data=>{void fetch(${JSON.stringify(url+'/committed')},{method:'POST'}).then(()=>write(data));return true;};await import('./create-ticket.mjs');`);
+  const file=join(root,'task.method');await writeFile(file,stringify(method));
+  const config={allow_local_processes:true,runtimes:{node:{command:process.execPath,version:process.version}},environment:{ticket_service:url},classification:{provider:'typesafe',model:'jev-fixture'}};
+  let classifications=0;
+  const classification={resolve:async()=>config.classification,evaluate:async()=>{classifications++;return {...config.classification,choice:'billing',probabilities:{billing:.94,technical:.04,unclear:.02},confidence:.8,usage:null};}};
+  const runDir=join(root,'run'),controller=new AbortController();
+  const running=runMethod(file,config,{runDir,classification,inputs:{message:'Please send my invoice.'},signal:controller.signal});
+  await saved;
+  controller.abort(Object.assign(Error('Test interruption after service commit'),{code:'interrupted'}));
+  assert.notEqual((await running).status,'completed');
+  assert.equal(records.size,1);
+  const resumed=await runMethod(file,config,{runDir,classification,resume:true,retry:['create_ticket:0']});
+  assert.equal(resumed.status,'completed');assert.equal(records.size,1);assert.equal(classifications,1);
+  assert.equal(writes.length,2);assert.equal(writes[0],writes[1]);
+  assert.equal(resumed.result.operation_id,writes[0]);
+  // The effect read the ticket back through the lookup connection; the receipt did not confirm it.
+  assert.equal(resumed.effects.confirmed,1);
+  const ledger=(await readFile(join(runDir,'effects.jsonl'),'utf8')).trim().split('\n').map(line=>JSON.parse(line));
+  assert.equal(ledger.at(-1).verdict,'confirmed');assert.equal(ledger.at(-1).token,writes[0]);
+  const conflict=await fetch(url+'/tickets',{method:'POST',headers:{'Idempotency-Key':writes[0]},body:JSON.stringify({message:'Different',destination:'billing'})});
+  assert.equal(conflict.status,409);
+});

package/dist/packages/sdk/examples/notes-summary/README.md

@@ -0,0 +1,23 @@
+# Weekly summary from meeting notes
+
+The smallest complete Method: a script reads a folder, one model call finds the items, and a script saves a file.
+
+- The folders `notes/` and `out/` beside the Method are its two files connections, so they need no binding. `out/` is empty until the first run.
+- The save step declares `changes: [environment.out]`. Nothing else is needed: the runtime reads the folder before and after the step, and the run fails if the step returns `out/weekly.md` but that file did not change.
+- The prompt shows two items written the way they should be. They come from other notes, so the model copies their form, not their content.
+- Run it: `method run notes-summary.method`.
+
+## The case in cases/
+
+The first version of the prompt asked for due dates as YYYY-MM-DD but said nothing about other dates. Its run wrote the decision "Move the client demo to 14 Oct." The correction was: write dates in decisions as YYYY-MM-DD too. The prompt now says so, and it shows an example decision with a date. The run after the change wrote "Move the client demo to 2026-10-14."
+
+That correction is kept as a case. It was made from the two runs:
+
+```sh
+method case new notes-summary.method --id dates-in-decisions \
+  --run BAD_RUN --passing-run FIXED_RUN \
+  --note "The demo date in the decision says 14 Oct. Write dates in decisions as YYYY-MM-DD too, like the due dates." \
+  --rubric "Every date in a decision is written as YYYY-MM-DD."
+```
+
+`method test notes-summary.method` runs it again: the summarize step changed since the bad run, so it runs live, and a model judges the saved summary against the rubric. `method publish` runs the cases first. Add a case in the same way for each correction that a later version must keep.

package/dist/packages/sdk/examples/notes-summary/TASK.md

@@ -0,0 +1,3 @@
+# Request
+
+Every Friday, read this week's meeting notes and save a summary with the decisions and the action items. Each item names its owner, its due date when the notes give one, and the note it came from.

package/dist/packages/sdk/examples/notes-summary/cases/dates-in-decisions/case.json

@@ -0,0 +1,36 @@
+{
+  "format": "method-case/1",
+  "id": "dates-in-decisions",
+  "status": "active",
+  "method_file": "notes-summary.method",
+  "note": "The demo date in the decision says 14 Oct. Write dates in decisions as YYYY-MM-DD too, like the due dates.",
+  "author": null,
+  "created": "2026-10-10T02:18:15.490Z",
+  "source": {
+    "run_dir": "/work/notes-summary/run2",
+    "execution_id": "e8348baa-6be6-421e-b50d-0f86e4df765f",
+    "method_sha256": "a444edf4f50b1263e1a0b1037a26ba2db91a95f3508e2e6f11747f44d468fa7d",
+    "passing_run_dir": "/work/notes-summary/run3"
+  },
+  "expect": [
+    {
+      "kind": "rubric",
+      "ref": "outputs.path",
+      "criteria": [
+        {
+          "id": "c1",
+          "text": "Every date in a decision is written as YYYY-MM-DD."
+        }
+      ]
+    }
+  ],
+  "runs": null,
+  "min_pass": null,
+  "supersedes": [],
+  "superseded_by": null,
+  "files": {
+    "/work/notes-summary/out/weekly.md": "files/0"
+  },
+  "retention_until": "2027-10-10",
+  "redacted": true
+}

package/dist/packages/sdk/examples/notes-summary/cases/dates-in-decisions/examples.json

@@ -0,0 +1,16 @@
+[
+  {
+    "run": "failing",
+    "labels": {
+      "c1": false
+    },
+    "value": "/work/notes-summary/out/weekly.md"
+  },
+  {
+    "run": "passing",
+    "labels": {
+      "c1": true
+    },
+    "value": "/work/notes-summary/out/weekly.md"
+  }
+]

package/dist/packages/sdk/examples/notes-summary/cases/dates-in-decisions/files/0

@@ -0,0 +1,10 @@
+# Weekly summary
+
+## Decisions
+- Move the client demo to 14 Oct. (2026-10-05-standup.md)
+- Drop the PDF export from this release. (2026-10-07-planning.md)
+
+## Action items
+- Finish the invoice export. — Dana, due 2026-10-08 (2026-10-05-standup.md)
+- Ask legal about the new NDA template. — Sam (2026-10-05-standup.md)
+- Rewrite the onboarding email. — Priya, due 2026-10-10 (2026-10-07-planning.md)

package/dist/packages/sdk/examples/notes-summary/cases/dates-in-decisions/recording.json

@@ -0,0 +1,195 @@
+{
+  "format": "method-recording/1",
+  "method_sha256": "a444edf4f50b1263e1a0b1037a26ba2db91a95f3508e2e6f11747f44d468fa7d",
+  "execution_id": "e8348baa-6be6-421e-b50d-0f86e4df765f",
+  "inputs": {},
+  "initial_state": {},
+  "environment": {
+    "notes": "/work/notes-summary/notes",
+    "out": "/work/notes-summary/out"
+  },
+  "keys": {
+    "read": "1fd58db074013c4e48e962c51903c64713d8ec03deee94801a84b5efe34297d9",
+    "summarize": "0639fb3e5ebc18181b7b7dc63d11cea0cc23238540c3b7953ec4b53ff16e51d7",
+    "save": "92f29d344b66c6e90a7af14ead1f3942b3a2bb93e2d7553b863c27e8e419307c"
+  },
+  "iterations": {
+    "summarize": [
+      {
+        "inputs": {
+          "material": "## 2026-10-05-standup.md\n# Standup 5 Oct\n- Dana: the invoice export is late; she will finish it by 8 Oct.\n- Decision: move the client demo to 14 Oct.\n- Sam will ask legal about the new NDA template.\n\n\n## 2026-10-07-planning.md\n# Planning 7 Oct\n- Decision: drop the PDF export from this release.\n- Priya owns the onboarding email rewrite, due 10 Oct.\n"
+        },
+        "candidate": {
+          "summary": {
+            "decisions": [
+              {
+                "text": "Move the client demo to 14 Oct.",
+                "source": "2026-10-05-standup.md"
+              },
+              {
+                "text": "Drop the PDF export from this release.",
+                "source": "2026-10-07-planning.md"
+              }
+            ],
+            "actions": [
+              {
+                "action": "Finish the invoice export.",
+                "owner": "Dana",
+                "due": "2026-10-08",
+                "source": "2026-10-05-standup.md"
+              },
+              {
+                "action": "Ask legal about the new NDA template.",
+                "owner": "Sam",
+                "due": "",
+                "source": "2026-10-05-standup.md"
+              },
+              {
+                "action": "Rewrite the onboarding email.",
+                "owner": "Priya",
+                "due": "2026-10-10",
+                "source": "2026-10-07-planning.md"
+              }
+            ]
+          }
+        }
+      }
+    ],
+    "save": [
+      {
+        "inputs": {
+          "summary": {
+            "decisions": [
+              {
+                "text": "Move the client demo to 14 Oct.",
+                "source": "2026-10-05-standup.md"
+              },
+              {
+                "text": "Drop the PDF export from this release.",
+                "source": "2026-10-07-planning.md"
+              }
+            ],
+            "actions": [
+              {
+                "action": "Finish the invoice export.",
+                "owner": "Dana",
+                "due": "2026-10-08",
+                "source": "2026-10-05-standup.md"
+              },
+              {
+                "action": "Ask legal about the new NDA template.",
+                "owner": "Sam",
+                "due": "",
+                "source": "2026-10-05-standup.md"
+              },
+              {
+                "action": "Rewrite the onboarding email.",
+                "owner": "Priya",
+                "due": "2026-10-10",
+                "source": "2026-10-07-planning.md"
+              }
+            ]
+          },
+          "out": "/work/notes-summary/out"
+        },
+        "candidate": {
+          "path": "/work/notes-summary/out/weekly.md"
+        }
+      }
+    ]
+  },
+  "observations": {},
+  "method": {
+    "format": "method/3.4",
+    "id": "wf_e1a98901bb45007eba9d8653bf08c98f",
+    "name": "Weekly summary from meeting notes",
+    "goal": "Read this week's meeting notes and save a summary with the decisions and the action items, each with its owner, due date and source note.",
+    "environment": {
+      "notes": {
+        "type": "files",
+        "description": "Folder of Markdown meeting notes."
+      },
+      "out": {
+        "type": "files",
+        "description": "Folder where the summary is saved."
+      }
+    },
+    "steps": {
+      "read": {
+        "name": "Read the notes",
+        "purpose": "Reads every Markdown file in the notes folder, oldest name first, and returns their text headed by the file name.",
+        "in": {
+          "notes": "environment.notes"
+        },
+        "do": {
+          "kind": "run",
+          "runtime": "node",
+          "entrypoint": "read-notes.mjs"
+        },
+        "out": {
+          "material": {
+            "type": "text",
+            "description": "All notes, each headed by its file name."
+          }
+        }
+      },
+      "summarize": {
+        "name": "Find decisions and action items",
+        "in": {
+          "material": "material"
+        },
+        "do": {
+          "kind": "call",
+          "model": "default",
+          "prompt": "From these meeting notes, list every decision and every action item.\nFor each item, give the note file it comes from. For an action item,\ngive the owner, and the due date as YYYY-MM-DD when the notes give one;\notherwise use an empty due. Do not add anything that the notes do not say.\n\n{{material}}\n"
+        },
+        "out": {
+          "summary": {
+            "type": "record",
+            "fields": {
+              "decisions": {
+                "type": "list",
+                "fields": {
+                  "text": "text",
+                  "source": "text"
+                }
+              },
+              "actions": {
+                "type": "list",
+                "fields": {
+                  "action": "text",
+                  "owner": "text",
+                  "due": "text",
+                  "source": "text"
+                }
+              }
+            }
+          }
+        }
+      },
+      "save": {
+        "name": "Save the summary",
+        "purpose": "Writes the decisions and action items to out/weekly.md as Markdown and returns the file path.",
+        "in": {
+          "summary": "summary",
+          "out": "environment.out"
+        },
+        "do": {
+          "kind": "run",
+          "runtime": "node",
+          "entrypoint": "save.mjs"
+        },
+        "changes": [
+          "environment.out"
+        ],
+        "out": {
+          "path": {
+            "type": "text",
+            "description": "Path of the saved summary."
+          }
+        }
+      }
+    },
+    "result": "path"
+  }
+}

package/dist/packages/sdk/examples/notes-summary/notes/2026-10-05-standup.md

@@ -0,0 +1,4 @@
+# Standup 5 Oct
+- Dana: the invoice export is late; she will finish it by 8 Oct.
+- Decision: move the client demo to 14 Oct.
+- Sam will ask legal about the new NDA template.

package/dist/packages/sdk/examples/notes-summary/notes/2026-10-07-planning.md

@@ -0,0 +1,3 @@
+# Planning 7 Oct
+- Decision: drop the PDF export from this release.
+- Priya owns the onboarding email rewrite, due 10 Oct.

package/dist/packages/sdk/examples/notes-summary/notes-summary.method

@@ -0,0 +1,54 @@
+format: method/3.4
+name: Weekly summary from meeting notes
+goal: Read this week's meeting notes and save a summary with the decisions and the action items, each with its owner, due date and source note.
+environment:
+  notes:
+    type: files
+    description: Folder of Markdown meeting notes.
+  out:
+    type: files
+    description: Folder where the summary is saved.
+steps:
+  read:
+    name: Read the notes
+    purpose: Reads every Markdown file in the notes folder, oldest name first, and returns their text headed by the file name.
+    in: {notes: environment.notes}
+    do: {kind: run, runtime: node, entrypoint: read-notes.mjs}
+    out:
+      material: {type: text, description: "All notes, each headed by its file name."}
+  summarize:
+    name: Find decisions and action items
+    in: {material: material}
+    do:
+      kind: call
+      model: default
+      prompt: |
+        From these meeting notes, list every decision and every action item.
+        For each item, give the note file it comes from. For an action item,
+        give the owner and the due date. Write every date as YYYY-MM-DD, also
+        inside a decision; take the year from the note's file name. When the
+        notes give no due date, leave due empty. Do not add anything that the
+        notes do not say.
+
+        Two items from other notes, written the way they should be:
+        - "Decision: ship the beta on 3 Nov." in 2026-10-28-review.md is the decision
+          text "Ship the beta on 2026-11-03.", source "2026-10-28-review.md".
+        - "Lee will book the venue." in 2026-10-28-review.md is the action
+          "Book the venue.", owner "Lee", due "", source "2026-10-28-review.md".
+
+        {{material}}
+    out:
+      summary:
+        type: record
+        fields:
+          decisions: {type: list, fields: {text: text, source: text}}
+          actions: {type: list, fields: {action: text, owner: text, due: text, source: text}}
+  save:
+    name: Save the summary
+    purpose: Writes the decisions and action items to out/weekly.md as Markdown and returns the file path.
+    in: {summary: summary, out: environment.out}
+    do: {kind: run, runtime: node, entrypoint: save.mjs}
+    changes: [environment.out]
+    out:
+      path: {type: text, description: Path of the saved summary.}
+result: path

package/dist/packages/sdk/examples/notes-summary/read-notes.mjs

@@ -0,0 +1,4 @@
+import {readFileSync, readdirSync} from 'node:fs';
+const {notes} = JSON.parse(readFileSync(0, 'utf8'));
+const files = readdirSync(notes).filter(name => name.endsWith('.md')).sort();
+console.log(JSON.stringify({material: files.map(name => `## ${name}\n${readFileSync(`${notes}/${name}`, 'utf8')}`).join('\n\n')}));

package/dist/packages/sdk/examples/notes-summary/save.mjs

@@ -0,0 +1,7 @@
+import {readFileSync, writeFileSync} from 'node:fs';
+const {summary, out} = JSON.parse(readFileSync(0, 'utf8'));
+const lines = ['# Weekly summary', '', '## Decisions', ...summary.decisions.map(d => `- ${d.text} (${d.source})`), '', '## Action items',
+  ...summary.actions.map(a => `- ${a.action} — ${a.owner}${a.due ? `, due ${a.due}` : ''} (${a.source})`), ''];
+const path = `${out}/weekly.md`;
+writeFileSync(path, lines.join('\n'));
+console.log(JSON.stringify({path}));