thursday-agent 0.17.0 → 0.17.2

package/bin/lock.mjs

@@ -0,0 +1,59 @@
+// One server to a data folder. A second one started on the same folder took the next port
+// and, at its boot, parked the first one's running jobs, closed its open calls and joined
+// the phone a second time, so every message was answered twice. The second is refused, and
+// told where the first one is.
+
+import { mkdirSync, readFileSync, rmSync, writeFileSync } from "node:fs";
+import { join } from "node:path";
+
+/** Beside the database, and named so a checkout never commits it (`*.local.*`). */
+const LOCK_FILE = "server.local.lock";
+
+/** The server already serving this data folder: where it is. Null when none is alive. */
+export function runningOn(home) {
+  let held;
+  try {
+    held = JSON.parse(readFileSync(join(home, LOCK_FILE), "utf8"));
+  } catch {
+    return null;
+  }
+  if (!Number.isInteger(held?.pid) || held.pid === process.pid) return null;
+  try {
+    // Signal 0 asks whether the process exists and sends nothing
+    process.kill(held.pid, 0);
+  } catch (error) {
+    // Someone else's process by that id is still a live one
+    if (error?.code !== "EPERM") return null;
+  }
+  return { pid: held.pid, url: String(held.url ?? "") };
+}
+
+/** Exits with where the running one is, when this folder already has a server. */
+export function refuseSecond(home) {
+  const running = runningOn(home);
+  if (!running) return;
+  console.error(
+    `\n  Thursday is already running on this data folder${running.url ? `: ${running.url}` : ""}\n  Open that one, or stop it first (Ctrl+C where it runs; one that starts with the\n  computer stops with: thursday autostart --off).\n`,
+  );
+  process.exit(1);
+}
+
+/** Marks this folder as served from here until this process ends. */
+export function holdFolder(home, url) {
+  const file = join(home, LOCK_FILE);
+  try {
+    mkdirSync(home, { recursive: true });
+    writeFileSync(file, `${JSON.stringify({ pid: process.pid, url })}\n`);
+  } catch {
+    // A folder that cannot be written is not a reason not to serve
+    return;
+  }
+  process.on("exit", () => {
+    try {
+      if (JSON.parse(readFileSync(file, "utf8")).pid === process.pid)
+        rmSync(file, { force: true });
+    } catch {
+      // Gone already
+    }
+  });
+}

package/bin/node-check.mjs

@@ -0,0 +1,21 @@
+// The first import of thursday.mjs, so it runs before the rest of bin/ is evaluated: that
+// reads what an older Node does not have (`import.meta.dirname`) while loading, and on
+// Ubuntu's and Debian's own Node 18 it died with a stack trace instead of saying why.
+// Plain JavaScript an old Node runs; the version it asks for is package.json's `engines`.
+
+import { readFileSync } from "node:fs";
+
+const { engines } = JSON.parse(
+  readFileSync(new URL("../package.json", import.meta.url), "utf8"),
+);
+const wanted = /(\d+)\.(\d+)/.exec(engines?.node ?? "");
+if (wanted) {
+  const [major, minor] = process.versions.node.split(".").map(Number);
+  const [needMajor, needMinor] = [Number(wanted[1]), Number(wanted[2])];
+  if (major < needMajor || (major === needMajor && minor < needMinor)) {
+    console.error(
+      `\n  Thursday needs Node ${needMajor}.${needMinor} or newer, and this is ${process.versions.node}.\n  Install a newer one from https://nodejs.org, or with your version manager, and run it again.\n`,
+    );
+    process.exit(1);
+  }
+}

package/bin/thursday.mjs

@@ -3,6 +3,8 @@
 // the build and at the user's home (config.ts APP_DIR / DATA_DIR), then boots
 // the standalone server. Plain JavaScript: this runs before anything is built.
 
+// First, so an older Node is told what it needs before anything else is evaluated
+import "./node-check.mjs";
 import { spawn } from "node:child_process";
 import {
   existsSync,
@@ -15,6 +17,7 @@ import { readFile } from "node:fs/promises";
 import { homedir } from "node:os";
 import { join, resolve } from "node:path";
 import { askToSetDatabaseAside, MIGRATION_FAILED_EXIT } from "./database.mjs";
+import { holdFolder, refuseSecond } from "./lock.mjs";
 import { freePort } from "./port.mjs";
 import { ROOT, toolPath } from "./tools.mjs";
 
@@ -87,8 +90,11 @@ if (argv[0] === "autostart") {
   process.exit(0);
 }
 
+// Before a port is picked: a second server on this folder would take the next one
+refuseSecond(home);
 const port = String(await freePort(asked, home));
 const url = `http://localhost:${port}`;
+holdFolder(home, url);
 /** Where config.ts DB_PATH puts the database under the home. */
 const database = join(home, "local.db");
 
@@ -179,7 +185,8 @@ start();
  * request to try again.
  */
 let stopping = false;
-for (const signal of ["SIGINT", "SIGTERM"]) {
+// A terminal closed under it is a stop too (SIGHUP), and the server parks its work for it
+for (const signal of ["SIGINT", "SIGTERM", "SIGHUP"]) {
   process.on(signal, () => {
     if (stopping) {
       child.kill("SIGKILL");

package/guide/bots.md

@@ -7,7 +7,8 @@ how a job finds its bot. The roster is **Settings › Bots**. **New bot** makes
 a description and a model, and a name cannot be changed later — and a bot's page holds what it
 **Runs on** and its **Effort**, when it **Compacts at**, its **Tools**, its own **Prompt**, its
 recent threads and its own memory. A bot can be switched off without being deleted. Deleting one keeps what it finished: **Settings ›
-Files** still shows it under that bot's name. The first run
+Files** still shows it under that bot's name. What it kept for itself — its memory and the skills it
+installed — is deleted with it, so a bot made later under the same name starts fresh. The first run
 offers the ready-made ones, all switched on; **Ready-made bots**, beside New bot, adds one later.
 There can be at most 14 bots, switched-off ones included: at 14 the roster says "14 is the most" in
 place of New bot, and one has to be deleted before another is made. When fewer places are left than
@@ -326,7 +327,8 @@ time, and at most twelve routines exist:
   run, and picking a new day and time sets it again. A time already gone is refused.
 - **On set days**: a time of day on the days picked. Every day, Weekdays and Weekends fill the days
   in one press.
-- **Every few hours**: 1, 2, 3, 6, 12 or 24 in one press, or any number from 1 to 168.
+- **Every few hours**: 1, 2, 3, 6, 12 or 24 in one press. Another number up to 168 is set by asking
+  Thursday for it, and then shows beside them.
 
 The line under the field says it back in words, with when it first starts. A routine's name and job
 are saved with **Save**.

package/guide/calls.md

@@ -6,8 +6,10 @@ Three ways in, and any of them also answers a call she placed:
 
 - Tap her face.
 - Say the wake phrase, "hey thursday" unless they changed it. It is off to begin with, because it
-  keeps the microphone open for as long as the tab is. It is heard loosely, in English, so it is
-  written in English words; a phrase in another language is not saved.
+  keeps the microphone open for as long as the tab is, and the listening is the browser's own
+  speech recognition: Chrome's sends what the microphone hears to Google, which is not this app's
+  to change. It is heard loosely, in English, so it is written in English words; a phrase in
+  another language is not saved.
 - Press the shortcut, Alt + Shift + T (⌥⇧T on a Mac) unless they changed it. It is off to begin
   with too, and works only while the app's tab has focus and nothing is being typed.
 
@@ -42,8 +44,8 @@ while it is open, silence included. Work already handed to a bot carries on.
 ## Writing to her instead
 
 The **+** at the left end of the pill in the bottom right corner — or the `/` key — opens a line at
-the foot of the screen. It opens on whoever it was last addressed to: her, the first time. What is
-sent to her there starts a call in writing: her answers come up beside her face as on a spoken
+the foot of the screen. It opens on her, always. What is sent to her there starts a call in
+writing: her answers come up beside her face as on a spoken
 call, what she is doing shows with them, and the line stays as the way to write back. She has the
 same memory, tools and bots as on a spoken call; there is no voice and no microphone, and nothing is
 billed by the minute.
@@ -53,9 +55,9 @@ billed by the minute.
 - **Files** go with the words: the paperclip, a paste, or a drop anywhere on the window — at most 8
   at a time, 25 MB each. A picture handed over in writing is one she can look at herself — a
   receipt, a screenshot, a chart — so "what does this say?" is answered on the spot.
-- **Who it goes to**: the chip at the left of the line, or `@` and a name at the start. During a
-  written call a bot picked there gets that one message; after it the line is hers again, and
-  **Esc** with a bot picked goes back to her.
+- **Who it goes to**: the chip at the left of the line, or `@` and a name at the start. A bot
+  picked there gets that one message; after it the line is hers again, and **Esc** with a bot
+  picked goes back to her.
 - **What it runs on**: the GPT Subscription when one is signed in, else the OpenAI key. The small
   **runs on** button under the line says which before anything is sent, and picks another model
   for writing to her — any provider with a key. The pick is remembered by this browser and is only
@@ -122,7 +124,7 @@ Everything here but her face is in **Settings › Thursday**, and changes apply
   circling.
 - **Voice**: the voice runs on GPT-Live 1, with 22 voices to pick from; clicking a name plays it.
   It is the one setting here a written call or a phone does not use.
-- **Style**: who she is to them — ten of them, and the only difference is how she talks. The row
+- **Style**: who she is to them — Bright, Calm, Straight or Rough, and the only difference is how she talks. The row
   shows the one she is on; opening it lists the rest with a line each. It never changes what she
   can do. Last in the list, **Your own** opens a box for saying it in their own words on top of
   the one picked — how she talks, how much she says — which wins wherever the two differ. What to
@@ -176,4 +178,4 @@ sound on a page nobody has clicked yet, so right after a reload it rings on the
 after another, oldest at the top, each with the jobs it opened and where they stand; a single call
 can be deleted, or all of them with **Delete all**. A call is kept for three months and then goes
 by itself. **Reset history** deletes every call, every job and everything she remembers, for good;
-keys, bots and connectors stay.
+keys, bots and connectors stay, and so does what each bot keeps for itself.

package/guide/memory.md

@@ -32,5 +32,6 @@ of her earlier calls (`calls.md`). Asking her to forget something removes the li
 
 Memory holds up to 400 facts, and 50 in one note. When it grows past that she says so once on a
 call and goes through what looks out of date with the user, the heaviest notes first, deleting
-only what they name. **Reset history** in Settings › Thursday deletes all of memory along with
-every call and job.
+only what they name. Forgetting a fact takes it out of everything she reads; the earlier wordings it
+replaced stay in the database until its note is deleted. **Reset history** in Settings › Thursday
+deletes all of her memory along with every call and job; what each bot keeps for itself stays.

package/guide/phone.md

@@ -126,10 +126,13 @@ starts a new one, and she reads the last one back like any earlier call.
   in the chat.
 - **A page** — a report, a deck, a design — arrives as pictures of it, since no chat app opens
   one: a deck slide by slide, a design board by board, anything else a phone's screen at a time
-  from the top, nine at most. The page itself comes with them, to open on a computer.
-  Drawing them takes a few seconds and needs the browser bots use; without it the page comes alone.
-- **What she did** — noted something down, started work, looked something up — is one short line
-  under her answer, in the words the call screen uses.
+  from the top, nine at most. The page itself stays on the computer, and the chat says so under
+  *Not sent — still on this computer*; sent along, it showed as code in a chat and its own pictures
+  never opened on a phone. Drawing them takes a few seconds and needs the browser bots use; without
+  it the page comes alone.
+- **What she did** — noted something down, started work, looked something up — is said in one short
+  line, in the words the call screen uses, only when she ended a turn without writing anything;
+  under an answer she wrote, the line read as part of her reply.
 - **How her words look**: bold, lists, links and code arrive the way each chat app draws them. A
   table arrives as rows and a heading as a bold line, since a chat has neither, and a long answer
   comes as several messages, each cut where a paragraph or a code block ends.

package/guide/setup.md

@@ -10,8 +10,10 @@ through six steps on the call screen itself: a voice key, the microphone, which
 they think with, her style, and the first call. She talks
 through it in a recorded voice, in English, and says so first; her real voice starts with the first
 call. The speaker button at the top right mutes the recording, and stays muted the next time, the opening's sounds with it. Every
-step can be passed and done later from the screens below. With a key the last button is **Call
-her**; without one it is **Look around**. It stops showing once a call has been placed, and adding
+step can be passed and done later from the screens below. The bots picked there are set up when
+it ends, key or no key; they run once there is a model to run on. With a key the last button is
+**Call her**; without one it is **Look around**, and she says whether the bots can already work or
+still need a key or a ChatGPT sign-in. It stops showing once a call has been placed, and adding
 `?intro` to the address brings it back.
 
 ## Around the screen
@@ -19,7 +21,8 @@ her**; without one it is **Look around**. It stops showing once a call has been
 The buttons at the top right of the call screen open **Thursday**, **Memory** and **Bots** directly,
 and **Settings** opens everything; each carries a dot when something there wants the user. The
 Settings list is Thursday, Memory, Bots, Threads, Routines, Files, Skills, Connectors, Sign-ins,
-Models, API keys and Phone. ⌘K (Ctrl+K) jumps to its filter, and ⌘ with a number opens that section.
+Models, API keys and Phone. ⌘K (Ctrl+K) jumps to its filter, and ⌘ with a number opens one of the
+first nine.
 Under Phone, as a group of their own named community, **Ask on Discord** opens the app's community,
 where people who use and build it answer questions, and **GitHub** opens its code, bug reports and
 releases. The theme — **System**, **Light** or **Dark** — is picked at the foot of the list.
@@ -35,21 +38,27 @@ The screen puts the two easy ways next: **GPT Subscription**, a sign-in with Cha
 ChatGPT plan, no key; the row shows how much of the plan is used and when it resets), and the
 **Vercel AI Gateway**, one key for every model and the one the app recommends (its row shows what is
 left). Under them every other provider is a mark to tap and paste a key into — Claude, Gemini, xAI
-and more behind **More**. The box a key goes in shows how that provider's keys begin where it is
+and the rest; the first run shows four of them and keeps the others behind **More**. The box a key goes in shows how that provider's keys begin where it is
 known, with a link to the page that makes one; **Remove**, on a key already set, is the red word at
 the far left.
 
 A search key (Exa) is optional. With it, calls and bots both search through Exa, which is cheaper
 per search and comes with free credits every month. Without it, a call uses OpenAI's own search and
-a bot its model's own — which only OpenAI, Claude, Gemini and xAI have, and only on their own keys.
-A bot running through the GPT Subscription, the Gateway or any other provider has no search of its
-own, so it opens pages in its browser instead.
+a bot its model's own — which the GPT Subscription has, and OpenAI, Claude, Gemini and xAI on their
+own keys. A bot running through the Gateway or any other provider has no search of its own, so it
+opens pages in its browser instead.
 
 ## Models
 
 **Settings › Models** has two groups. **Bots** holds the **Default model** — the one a bot uses when
 its own page says nothing; a small one is quick and costs little, and is the place to start — and
-its **Default effort**. Left unset it shows *auto* and runs on the first provider with a key. The
+its **Default effort**. Left unset it shows *auto* and names the model bots run on now: the GPT
+Subscription's when you are signed in, since the plan is already paid for, else OpenAI's, else xAI's,
+else the first provider with a key — the **small** model on OpenAI, the one the call's backend starts
+on too, and the **mid** one on the GPT Subscription, which is paid for either way (a Free plan opens
+only the small one and runs that), and elsewhere. A default picked here whose key is
+later removed is not swapped for another provider: bots stop and say so until it is back or another
+is picked. The
 first run's model step sets this same one, and **App default** at the top of a bot's model list puts
 that bot back on it. **Studio** holds the **Image model**, **Video model**, **Speech model** and
 **Transcription model**. A kind with no model picked simply is not there — a bot that needs it says
@@ -157,6 +166,12 @@ settings, because a browser keeps settings per address. Starting it once with `-
 moves it to that address for good; if that port is taken, it says so and stops. `thursday --help`
 lists the rest: `--home` for another data folder, `--no-open` to start without opening a browser.
 
+One data folder is served by one app at a time: started again while it runs — a second `npx`, or
+one beside the one that starts at login — it says the address of the one running and stops, rather
+than serving the same calls, jobs and phone twice. It needs Node 22.18 or newer and says so on an
+older one. Closing the terminal it runs in stops it the way Ctrl+C does: jobs that were running
+are paused, to be picked up again.
+
 ## Where the files are
 
 Everything is on this computer, in one folder: `.thursday` in their home folder when the app was
@@ -178,7 +193,9 @@ can be missing the last thing that was said; stopping the app folds that file ba
 another computer is the same folder put in the same place there. If the app ever cannot open the
 database, the terminal it was started in asks whether to set it aside and start over; yes moves it
 next to the new one with `.corrupt-` and a number in its name, and nothing is thrown away. Started by
-autostart it cannot ask, so it does not come up until it is started once from a terminal.
+autostart it cannot ask, so it does not come up until it is started once from a terminal. Data a
+newer version of the app has opened is not offered to be set aside: an older one — an autostart left
+behind while `npx` runs the latest — says so and stops, and the newer one opens it as it was.
 
 ## What it costs
 

package/guide/trouble.md

@@ -7,15 +7,21 @@ has already said which: a provider's own words are shown as they came, never hid
 
 - **"Call failed"** shows the provider's reason. A refused key or no credit left is fixed in
   **Settings › API keys**; a model the key cannot use is changed in **Settings › Thursday › Models**.
+- **"One call at a time"**: another tab of the app has a spoken call on. Hang up there, or go on
+  there; two lines at once were billed twice and said every update twice. A tab closed mid-call
+  ends its call as it goes.
 - **She cannot be heard** on a call that opened by itself (she called back): the browser holds the
   sound until the page is touched. A tap anywhere lets it through.
 - **She does not hear them**: the browser asks for the microphone on the first call. If that was
   refused, it is allowed again from the site's settings in the address bar. The first run's
   microphone step says which it was: not allowed, no microphone found, one that would not start
   (another app may be using it), or the browser's own words for anything else.
-- **The call ended by itself**: the line under her face says why — *40s of quiet* (nothing was said
-  for 40 seconds; the last 10 count down on screen), *Thursday hung up*, *Live closed the call*, or
-  *the connection dropped*. Work already handed to a bot is not affected.
+- **The call ended by itself**: the line under her face says why — *25s of quiet* (nothing was said
+  for 25 seconds; the last 10 count down on screen, and an update she is reading is let finish
+  first), *Thursday hung up*, *the call ran to Live's time limit*, *Live closed the call*, or *the
+  connection dropped*. Only a dropped connection or a close Live gives no reason for shows as a
+  failure; when Live's safety filter stops a call, a note says so. Work already handed to a bot is
+  not affected.
 
 ## "Hey thursday" does nothing
 
@@ -71,7 +77,8 @@ A job never fails for good; it pauses and waits.
 
 Deleting a single call, thread or note is on its own screen. **Settings › Thursday › History ›
 Reset history** deletes every call, every job and everything she remembers, for good; keys, bots and
-connectors stay. Wiping everything, keys included, is removing the data folder (`setup.md` says
+connectors stay, and so does what each bot keeps for itself (its own memory and the skills it
+installed, which go only when that bot is deleted). Wiping everything, keys included, is removing the data folder (`setup.md` says
 where).
 
 ## Still stuck

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "thursday-agent",
-  "version": "0.17.0",
+  "version": "0.17.2",
   "description": "A voice agent that runs on your own machine — talk to her, she hands the slow work to bots with a shell, a browser and skills.",
   "license": "MIT",
   "keywords": [

package/seed-skills/concierge/travel/scripts/itinerary.mjs

@@ -97,6 +97,12 @@ const out = join(
 
 const cur = trip.currency ? String(trip.currency).toUpperCase() : null;
 const lang = String(trip.lang ?? "en");
+// Built without them, a page in Korean came out with "Day by day" and "Before you go" on it,
+// and the warning printed after the build was passed over
+if (!lang.startsWith("en") && !trip.labels)
+  fail(
+    `The page is in "${lang}" but its own headings would be English: add "labels" in that language (references/itinerary.md) and build again.`,
+  );
 const place = String(trip.place ?? "");
 const L = {
   flights: "Getting there",
@@ -509,7 +515,3 @@ if (missing.length)
   console.log(
     `No photo for: ${missing.join("; ")}. Give those a "wiki" title that exists — a place abroad often has one only in its own language's Wikipedia ("pt:Mosteiro dos Jerónimos", "de:Kölner Dom") — or a "photo" page url, or leave them without one.`,
   );
-if (!lang.startsWith("en") && !trip.labels)
-  console.log(
-    `The page is in "${lang}" but its own headings are English: add "labels" in that language (references/itinerary.md) and build again.`,
-  );

package/skills/artifact/references/book.md

@@ -47,7 +47,8 @@ first is the cover, asking the question the book answers.
    node <skill dir>/scripts/book.mjs put <name> <scratch>/pages.html --lang <the book's language, e.g. ko>
    ```
 
-   It checks each page and puts them all into the book, in place of what it held; a
+   A book is named by its folder under your artifacts, or given by its path — the way
+   to reach one another job made. It checks each page and puts them all into the book, in place of what it held; a
    page it cannot take stops it, named, and nothing is written: fix that page in
    your file and put again. To change the book later, change your file and put it again.
 4. Look at it once when a page carries a picture you did not draw — a photo you

package/skills/artifact/references/sheet.md

@@ -84,14 +84,19 @@ Both land in `artifacts/<name>/`: hand back the page and the `.xlsx`.
   and the file's name. Look at each one: a photo with `look_at`, a PDF's text with
   `node $THURSDAY_SKILLS/media-digest/scripts/text.mjs <file.pdf> --out <scratch>/<n>.txt`. A
   figure you cannot read is an empty cell, named in your answer, never a guess. `totals` sums
-  the amounts; a second sheet by category is `SUMIF` over them, by month `SUMIFS`. Their files
-  stay where they are, as they are named.
+  the amounts; a second sheet by category is `SUMIF` over them, by month `SUMIFS`. Amounts in
+  more than one currency get a currency column and are summed a currency at a time (`SUMIFS` by
+  currency, no `totals` across them) — won and dollars are never added. Their files stay where
+  they are, as they are named.
 - **A bank's or a card's export** is the CSV they downloaded; never sign in to their bank for it.
-  `read <file.csv>` prints its lines numbered — when it says the file is not UTF-8, run it again
-  with the `--encoding` it names. Then `read <file.csv> --header <the line naming the columns>
-  --json <scratch>/<name>.json` writes the table under that line, dates as dates and amounts as
-  numbers. Add a column there — a category for each row — and `put <name>` that file; a budget by
-  month and category is a second sheet of `SUMIFS` over it.
+  `read <file.csv>` prints its lines numbered and says which line it takes as the columns. When
+  it says the file is not UTF-8, give the likeliest `--encoding` for where the bank is; if its
+  words then do not read right, try the next. It also says what it could not take: a total under
+  the table (leave it out with `--until <the table's last line>`), or dates written day or month
+  first (`--dates dmy` for 03.07.2026, `--dates mdy` for 07/03/2026 — as the bank's country
+  writes them). Then add `--json <scratch>/<name>.json`: the table as put takes it, dates as
+  dates, amounts as numbers. Add a column there — a category for each row — and `put <name>`
+  that file; a budget by month and category is a second sheet of `SUMIFS` over it.
 
 ## Their own .xlsx, and changes
 

package/skills/artifact/runtime/sheet/format.mjs

@@ -305,16 +305,23 @@ export function formatColor(value, code) {
   return sectionFor(parts, value).section.color ?? null;
 }
 
-/** A date written YYYY-MM-DD, with hh:mm or hh:mm:ss after it, as Excel's day number; else null. */
-export function serialOf(text) {
-  const m =
-    /^(\d{4})[-/.](\d{1,2})[-/.](\d{1,2})(?:[ T](\d{1,2}):(\d{2})(?::(\d{2}))?)?$/.exec(
-      String(text).trim(),
-    );
+/**
+ * A date as Excel's day number, or null. Written year first (2026-07-03, 2026.07.03,
+ * 2026/07/03) unless `order` says the day or the month comes first (`dmy`: 03.07.2026,
+ * `mdy`: 07/03/2026) — which of those a file means is for whoever knows the file to say,
+ * never guessed here. A time may follow: hh:mm or hh:mm:ss.
+ */
+export function serialOf(text, order = "ymd") {
+  const time = String.raw`(?:[ T](\d{1,2}):(\d{2})(?::(\d{2}))?)?$`;
+  const m = new RegExp(
+    order === "ymd"
+      ? String.raw`^(\d{4})[-/.](\d{1,2})[-/.](\d{1,2})` + time
+      : String.raw`^(\d{1,2})[-/.](\d{1,2})[-/.](\d{4})` + time,
+  ).exec(String(text).trim());
   if (!m) return null;
-  const [y, mo, d, h = 0, mi = 0, s = 0] = m
-    .slice(1)
-    .map((x) => Number(x ?? 0));
+  const [a, b, c, h = 0, mi = 0, s = 0] = m.slice(1).map((x) => Number(x ?? 0));
+  const [y, mo, d] =
+    order === "ymd" ? [a, b, c] : order === "dmy" ? [c, b, a] : [c, a, b];
   const at = Date.UTC(y, mo - 1, d, h, mi, s);
   const check = new Date(at);
   if (check.getUTCMonth() !== mo - 1 || check.getUTCDate() !== d || h > 23)

package/skills/artifact/scripts/book.mjs

@@ -2,10 +2,11 @@
 // A picture book: one HTML file in a folder of its own, printed and read aloud.
 //
 //   node book.mjs new <name>                               the book, styled, to write pages into
+//   (a book after `new` is its name — its folder under your artifacts — or its path)
 //   node book.mjs put <name> <pages.html> [--lang ko]      the pages written in <pages.html> put
 //                                                          into the book, checked first
-//   node book.mjs shots <name>                             every page as a picture, and all on one, in scratch/
-//   node book.mjs pdf <name>                               the book as a PDF, one page a sheet
+//   node book.mjs shots <name | path>                      every page as a picture, and all on one, in scratch/
+//   node book.mjs pdf <name | path>                        the book as a PDF, one page a sheet
 //   node book.mjs video <name> <audio>... [--size WxH]     the book as an mp4, one audio file per page
 import { spawnSync } from "node:child_process";
 import {
@@ -15,7 +16,7 @@ import {
   rmSync,
   writeFileSync,
 } from "node:fs";
-import { dirname, join, resolve } from "node:path";
+import { basename, dirname, join, resolve } from "node:path";
 import { fileURLToPath } from "node:url";
 import { markSvg } from "../runtime/shell/wear.mjs";
 import {
@@ -44,12 +45,24 @@ function bookFile(name) {
   return join(ARTIFACTS, name, `${name}.html`);
 }
 
+/**
+ * A book named, or pointed at by its folder or its file — a book another job made, or one
+ * the path names as it was handed back. A path is taken as given; a name is looked for in
+ * your own folder.
+ */
+function bookAt(arg) {
+  if (!arg || !/[/\\]|\.html$/i.test(arg)) return bookFile(arg);
+  const path = resolve(arg);
+  if (/\.html$/i.test(path)) return path;
+  return join(path, `${basename(path)}.html`);
+}
+
 /** An existing book, or how to start one. */
 function openBook(name) {
-  const book = bookFile(name);
+  const book = bookAt(name);
   if (!existsSync(book))
     throw new Stop(
-      `No book ${shown(book)}. Start it with: node ${SCRIPT} new ${name}`,
+      `No book ${shown(book)}. A book is given by its name (its folder under your artifacts) or by its path; to start one: node ${SCRIPT} new <name>`,
     );
   return book;
 }
@@ -212,7 +225,7 @@ function putPages(name, from, args) {
  */
 function shotBook(name) {
   const book = writtenBook(name);
-  const out = join(WORKSPACE, "scratch", `${name}-shots`);
+  const out = join(WORKSPACE, "scratch", `${basename(book, ".html")}-shots`);
   const sheet = join(out, "book.png");
   rmSync(out, { recursive: true, force: true });
   const done = spawnSync(