thursday-agent 0.22.0 → 0.23.0

package/guide/bots.md

@@ -23,17 +23,23 @@ bots. A ready-made bot differs only in its role, and some carry a skill of their
 
 - **Analyst** finds things out and answers with sources: what something costs, how a number moved
   and why, which one to pick, whether to buy now or wait.
-- **Curator** keeps the user up to date: a morning brief on the topics they follow, and anything
-  long — a video, a podcast, a talk, an article, a PDF — handed back short, each point linked to
-  where it is said.
-- **Concierge** takes trips and errands up to the step that pays: a trip laid out day by day,
-  flights and stays found and compared, a booking, an order or a form filled in. With the kiwi
+- **Curator** keeps the user up to date: a morning brief on the topics they follow — what changed
+  since the last one, why each story is theirs, the stories they are following as a line through
+  the days, the rest as headlines — and anything long — a video, a podcast, a talk, an article, a
+  PDF — handed back short, each point linked to where it is said.
+- **Concierge** takes trips and errands up to the step that pays: a trip laid out day by day —
+  pictures of every place that open large, what to do and watch for there, the cost and what is
+  still to price always in view, what to book by when — flights and stays found and compared, a
+  booking, an order or a form filled in. With the kiwi
   connector on (**Settings › Connectors**) it searches flights without opening a window.
 - **Designer** makes what gets looked at: two to four ways a screen or page could look side by
-  side, a deck, a post or poster at its real size.
-- **Tutor** explains anything as a picture book.
-- **Marketer** keeps one brief per product and works from it: positioning, page copy, a launch
-  plan, social posts, emails, an SEO audit.
+  side, a deck, a post or poster at its real size, a short film for a birthday or a thank-you.
+- **Tutor** explains anything simply, a picture at a time: slides that read like a picture book,
+  read aloud when asked, or a one-page guide to study from.
+- **Writer** writes what goes out in the user's name, the way they write: their mail read and
+  answered as drafts, letters, posts, page copy, and a product's marketing — positioning, a launch
+  plan, emails, an SEO audit — from one brief per product. It sends only what they asked to have
+  sent, such as a finished page mailed to them.
 - **Jarvis** takes whatever nobody else is for — the web, files, this computer.
 
 A bot keeps its own memory — what a job taught it, how the user asked it to work — listed on its
@@ -54,16 +60,38 @@ or waiting on an answer never is, and what a job made stays in **Settings › Fi
 Pressing the pill opens the corner as a list; pressing a row opens the thread. **Esc** or the back
 arrow steps back one level, and the ✕ folds the room away.
 
-While a thread is at work, the cube button at the top of it shows it as an office, nearly the whole
-window: each bot at its desk, the work walked from desk to desk as it happens, a hand-off that
-waits for another bot's answer held in a tray under an hourglass, and questions and the final
-report brought to your counter. A bot's tag opens a card with what it is doing and why; pressing
-the tag keeps it open. The clock on the wall is how long the job has run, and the job's name lies
-on the floor. **Chat** beside it is the thread's own conversation, and **At a glance** puts the
-request, what is asked of you, each bot's state and what came back on one list; under either is
-the thread's box, and a file dropped on the office goes into it. The office shows where the thread
-stands now and walks what happens while it is open, so a thread that has ended has none. It pans
-by dragging and zooms with the wheel or the buttons at its bottom left, and **Esc** closes it.
+An open thread is also drawn as an office where her face stands, beside the room, when the window
+is wide enough: each bot at its desk, the work walked from desk to desk as it happens, a hand-off
+that waits for another bot's answer held in its tray, with a dashed line on the floor from the bot
+it waits for, and questions and the final report brought to your counter. A bot at work bobs over
+its desk as if typing. A bot flips as it first comes in to its desk, hops when more work lands
+there, and now and then leaps on its own; when the report reaches your counter, every bot leaps
+and throws its papers in the air, and they flutter down and lie on the floor a moment. Opening a
+job that finished while you were away does the same once the office stands, the first time only.
+A computer set to reduce motion gets the walking without the leaps. A bot that was stopped, or
+paused waiting on **Continue**, has its eyes crossed out, in the office and on its tab in the room.
+Only a bot with something to say has a plate over its head: the one at work (**working**), the one
+that wants you (**needs you**, in orange, for a question or **Continue**), and the thread's bot once
+its report is ready (**report ready**). Every other bot just stands there; pointing at it shows its
+name. Once the report is ready its words stand open over the thread's bot, scrolling when they are
+long. Pressing another bot opens its last answer there instead, or the question it asks, and its
+tab in the room; pressing it again, or tapping the floor, puts it away. The office's top left
+names the job, and once the job is done, says how many bots worked on it and
+lists the files it handed over; pressing one opens it. Past three, the rest fold under **+N
+more**, which opens them in place. The clock on the wall says how long the job has run, and how it
+stands is written in large letters on the ground beside the building: at work, your turn, paused,
+stopped or done, with how long it took under a finished or stopped one. While the app has stopped
+the job and waits on **Continue**, the ground around the building goes faintly red. Once the job
+is done, the report is brought to your counter; writing on after it, the bot carries the report
+back to its desk. A file dropped on the office goes to the
+thread, as one dropped on the room does. The office opens a little zoomed out, pans by dragging
+and zooms with the wheel or the buttons at its bottom left, from 30% to 400%; the frame button
+brings it back. Her face fades out as the office comes and back in as it goes,
+and a call that is on shows her last words at the top; the corner of finished jobs stays quiet
+while a thread is open. **Office** and **Chat**, beside the ✕ of an open thread, pick how every
+thread is shown: beside its office, or as the conversation alone with her face kept. The choice
+is kept on this computer. In the conversation, what you wrote yourself — a job from the write
+line, a step-in — is under **You**; what she handed over or passed on from a call is under her name.
 
 A long thread summarizes itself when it fills up. The small bar at the top right of an open thread
 shows how full it is; pressing it has the bot summarize at its next step, which makes every later
@@ -86,11 +114,11 @@ on a step right now.
 
 ## Handing a bot work without a call
 
-The **+** at the left end of the pill, or the `/` key, opens the line at the foot of the screen
-(`calls.md`, writing to her). It opens on Thursday; pick a bot with the chip at its left, or type
-`@` and a name at the start. That pick lasts for one message. Files can go with the words (at most
-8 at a time, 25 MB each). The bot cannot hear the call, so the message has to say the whole job.
-Enter sends it, and the room opens on the thread it started.
+The **@** at the left end of the pill, or the `@` key, opens the line at the foot of the screen
+(`calls.md`, writing to her) on the list of who to write to, Thursday first: pick a bot there, type
+its name after the `@`, or later with the chip at the line's left. That pick lasts for one message.
+Files can go with the words (at most 8 at a time, 25 MB each). The bot cannot hear the call, so the
+message has to say the whole job. Enter sends it, and the room opens on the thread it started.
 
 An open thread's own message box takes files the same way. Once more than one bot is in a thread,
 the box says who it is addressed to and can be changed. Only the bot the job went to brings other
@@ -124,7 +152,9 @@ it when it is in.
   pill says how many need a reply, and each can be answered right there (or just above the line at
   the foot, while that is open).
 - **A pause** — a model that broke twice, a provider that refused, the app restarting, a job that
-  reached its step limit — shows as *Paused*, and **Continue** picks it up where it left off.
+  reached its step limit — shows as *Paused*, and **Continue** picks it up where it left off. When
+  the provider turned down the key or sign-in the bot runs on, it says so, and **Open Settings**
+  beside **Continue** opens **Settings › API keys**; Continue once a key works.
 - **Signing in** is always the user's: the bot opens the page and waits.
 - **Paying** is the user's too: a bot fills a checkout in and stops at the button.
 
@@ -159,15 +189,11 @@ an open file, it is shown fresh with **Reloaded at** and the time; a sound or vi
 file, a spreadsheet or anything else the app cannot show has **Open it**, which opens it in the
 computer's own program.
 
-## Books, canvases, decks, videos and pages
+## Canvases, decks, videos and pages
 
 A page, canvas or deck opened inside the app takes the keyboard once clicked; opened in its own tab
-(↗) it has the whole window. Its top bar names the bot that made it.
-
-**Tutor**'s picture book is a picture and a line or two a page, turned by swiping, the arrow keys or
-tapping either side; it may end on a quiz. It can also be a PDF, or a video that reads itself aloud,
-when asked; otherwise it is a book to swipe through. Pictures need an image model and the video a
-speech model in **Settings › Models**.
+(↗) it has the whole window. Its top bar names the bot that made it, with its face; a page that is
+read — a report, a brief, a trip — ends with the same, and its one colour is that bot's.
 
 **Designer**'s canvas lays two to four options side by side, each with a note on what it is for and
 what it costs, the one it recommends marked. Drag to move, pinch or hold ⌘ and scroll to zoom, the
@@ -178,12 +204,18 @@ note pin on the rail (**N**) pins a note of the user's own; a bot asked to chang
 the notes. It designs from what exists — a codebase, a brand, a page — so give it a screenshot of a
 screen it cannot open.
 
-A **deck** is for presenting. Any bot can make one; the app lays out every slide, in one of four
-palettes: **Forest**, **Sea**, **Clay** or **Ink**. The top bar has the arrows, Notes (**n**), full
-screen (**f**), Present, a theme button and **Export** (**Print · one slide a page**, **This slide
-as a picture**, **Download this file**). Presenting shows the slide alone, never the notes. There is
-no PowerPoint file; a handout prints to PDF. **Edit** changes words and notes in place, moves,
-duplicates or deletes the open slide, or changes the palette; ⌘Z undoes.
+A **deck** is for presenting, or for explaining one thing simply. Any bot can make one; the app
+lays out every slide, in one of six palettes: **Forest**, **Sea**, **Clay**, **Ink**, **Paper** or
+**Night**.
+**Tutor**'s decks explain the way a picture book does — a picture and a line or two a slide, a new
+word marked where it is first named — and may end on a quiz: tapping a pick marks it and shows the
+answer. The top bar has the arrows, Notes (**n**), full screen (**f**), Present, a theme button and
+**Export** (**Print · one slide a page**, **This slide as a picture**, **Download this file**).
+Presenting shows the slide alone, never the notes. There is no PowerPoint file; a handout prints to
+PDF. **Edit** changes words and notes in place, moves, duplicates or deletes the open slide, or
+changes the palette; ⌘Z undoes. Asked for one, a bot also makes the deck a PDF, a slide a sheet, or
+a video that reads each slide's notes aloud over it. A picture a bot generates needs an image model,
+and the video a speech model, in **Settings › Models**.
 
 A **motion video** is a short hand-drawn film with music — a birthday or anniversary gift, a
 thank-you to a parent, a farewell, a small story. Any bot can make one: tell it who it is for and
@@ -205,12 +237,25 @@ A bot also reads an Excel file handed to it; an old .xls has to be saved as .xls
 
 A **page** is for reading — a report, a memo, a plan, meeting notes — with its contents beside it,
 tables, checklists, and numbered sources at the end. It prints as a document, and **Export › Word
-file** saves a .docx. **Edit** makes it editable in place: `/` on an empty line picks a block, and
-lines started with `#`, `-`, `1.`, `[]` or `>` become headings, lists, checklists or notes. Changes
-are saved as typed. A bot asked to change it starts from the page as edited.
-
-When a deck, sheet or page is changed elsewhere (by its bot, in Excel, or from another window)
-while it is being edited, nothing more is saved over it: the top bar says **Changed since it opened · not kept** and shows **Reload**.
+file** saves a .docx. Click anywhere in its words and type: there is no Edit button. While typing, a
+handle beside the block moves, copies or deletes it, selected words get bold, italic, a heading or a
+link, `/` on an empty line picks a block, and lines started with `#`, `-`, `1.`, `[]` or `>` become
+headings, lists, checklists or notes. Clicking a link shows where it goes, with **Open**, **Edit**
+and **Remove**; ⌘-click or Ctrl-click opens it straight away. In the app, changes are saved a moment
+after you stop typing, and the top bar says **Saving…** then **Saved**. A bot asked to change it
+starts from the page as edited.
+
+A page opened outside the app, as a file, is not saved into that file: the top bar says **Kept in
+this browser only**, your edits come back when the file is opened again in the same browser,
+**Discard edits** throws them away, and **Export › Download this file** saves a copy with them.
+
+When a page is changed elsewhere (by its bot, or from another window) while you have unsaved edits,
+they are not saved over it: the top bar says **Not saved: changed elsewhere** and shows **Load new
+version**. Your edits stay on the page and are kept aside; the new version then opens with them in a
+box above it, to **Copy** back, **Download** as a file of their own, or **Dismiss**.
+
+When a deck or sheet is changed elsewhere (by its bot, in Excel, or from another window) while it
+is being edited, nothing more is saved over it: the top bar says **Changed since it opened · not kept** and shows **Reload**.
 
 ## Routines: jobs that start by themselves
 

package/guide/calls.md

@@ -5,7 +5,8 @@
 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. It keeps
+- Say the wake phrase, "hey thursday" unless they changed it. It comes on with the microphone on
+  the first run's microphone step, and is otherwise off until switched on. It keeps
   the microphone open while the tab is, uses the browser's own speech recognition (Chrome sends
   what it hears to Google), and listens in English only.
 - Press the shortcut, Alt + Shift + T (⌥⇧T on a Mac) unless they changed it. It is off to begin
@@ -22,8 +23,10 @@ memory (`memory.md`). A call she places herself opens on why she called.
 The first call started from the page — spoken or in writing — has the browser ask to know the
 user's location. Allowed, she knows on every call which town they are in and the weather there:
 the page asks BigDataCloud for the town's name and Open-Meteo for the weather, and only those two
-reach her. What was found is used for half an hour before it is looked up again. Refused, or not
-known within three seconds, the call goes on without it and nothing is sent. The browser keeps
+reach her. What was found is used for half an hour before it is looked up again. Once it is
+allowed, the page asks the device for its position as it opens, so a call does not wait on the
+device; the position stays in the page until a call starts. Refused, or not known within three
+seconds, the call goes on without it and nothing is sent. The browser keeps
 the answer; it is changed in the browser's site settings for this app (the icon left of the
 address). A phone chat has no browser, so she does not know it there.
 
@@ -32,7 +35,7 @@ with her turning into a globe: it spins to where they are, dives until their cou
 screen, and shows the sky over it as it is there now — the sun or the moon where it really is,
 and the weather, lightly — while she greets them with that weather. At night the country is
 dark. After about eight seconds she is back; tapping the globe brings her back sooner and does
-not hang up. It waits for the next call on a call she placed herself and on the very first
+not hang up, and opening a job's office over her ends it. It waits for the next call on a call she placed herself and on the very first
 call, and does not play when the system is set to reduce motion or the app's page is not the
 one in front. The day counts only once it has played, in this browser only. The map is drawn
 in the browser, so the position still goes nowhere.
@@ -46,13 +49,13 @@ several steps — goes to a bot while the call carries on. She picks the bot and
 While she is working, the line under her face says so. The microphone stays open: anything said
 meanwhile is heard and answered once she is done, so there is no need to repeat it.
 
-**Share screen**, on that line during a spoken call, shows her a screen, a window or a tab; the
-browser asks which. **Camera** shows her your camera instead — one or the other, not both. A small
-copy stands at the top right while it is on. Nothing of it is sent while it is only on: she looks
-when what they ask needs it — "what does this error say?", "what am I holding?" — and then a
-picture of it as it is at that moment goes to the model behind her, nowhere else. **Stop** on the line, the browser's own bar, or the end of the call
-stops it. When the browser refuses — on a Mac, the browser needs Screen Recording, or Camera, in
-System Settings › Privacy & Security — its reason shows, and nothing is shown.
+**Draw**, on that line during a spoken call, opens a pad over the call: pick a colour, draw, and
+**Show her** gives her the drawing the moment it is pressed. She looks at it and says what she makes
+of it, and you can go on from there — "what do you think of this logo?" It goes to her alone, not
+onto the write line.
+**Esc** closes the pad and keeps what is on it for next time; **Clear** wipes it. **Undo** and
+**Redo** beside it (⌘Z and ⇧⌘Z, or Ctrl+Z and Ctrl+Shift+Z) take back or bring back one stroke at a
+time, a Clear too.
 
 ## Ending it
 
@@ -64,18 +67,25 @@ 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. Sending her a message there starts a call in writing: her answers show
-beside her face, and the line stays open for writing back. She has the same memory, tools and bots
-as on a spoken call, with no voice and no per-minute billing.
+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 with the list of who to write to up, her first: **Enter** takes her, a name
+typed after the `@` narrows the list, and **Esc** puts it away. Sending her a message there starts
+a call in writing: her answers show beside her face, and the line stays open for writing back. She
+has the same memory, tools and bots as on a spoken call, with no voice and no per-minute billing.
 
 - **Her answers** keep their shape (lists, tables), and what she names is a link: a file opens over
   the call, a web page in a new tab.
-- **Files**: the paperclip, a paste, or a drop anywhere on the window — at most 8 at a time, 25 MB
-  each. She can look at a picture herself, 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 (**Tab** or
-  **Enter** takes the highlighted one). A bot picked there gets that one message, then the line goes
-  back to her; **Esc** with a bot picked also goes back to her.
+- **Files**: the paperclip's **A file from this computer**, a paste, or a drop anywhere on the
+  window — at most 8 at a time, 25 MB each. A picture (png, jpg, webp, gif) goes to her with the
+  words, so "what does this say?" is answered on the spot. One over 4 MB, or one sent while she
+  runs on a model that cannot see pictures, does not go with them, and she says so. Later
+  messages carry the call's pictures again, the newest up to 12 MB in all; an older one she
+  looks at again by its name.
+- **A drawing**: the paperclip's **Draw something** opens a pad over the screen. **Add to the
+  message** puts it on the line as a picture, sent with the words like any other.
+- **Who it goes to**: the list it opens on, the chip at the left of the line, or `@` and a name at
+  the start (**Tab** or **Enter** takes the highlighted one). A bot picked there gets that one
+  message, then the line goes back to her; **Esc** with a bot picked also 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 shows which, and can pick another model, from any provider with
   a key, for writing only. With nothing to run on it says so; keys are in **Settings › API keys**.
@@ -84,9 +94,11 @@ as on a spoken call, with no voice and no per-minute billing.
   when the plan resets. Every turn tries the plan first, so it goes back to the plan by itself once
   the plan resets. Turns on the key are billed to it. With no key, the turn fails as below.
 - **When a turn fails** — a refused key, a plan's limit with no key to go on — her face says ERROR
-  and the provider's reason shows in red under the line, with **Send it again** and a link to
-  **API keys**. When an OpenAI key is set and was not the problem, the button reads **Send it again
-  on your OpenAI key**.
+  and the provider's reason shows in red under the line, with **Send it again**. When the provider
+  turned down the key or sign-in itself, the line says so in a sentence with the provider's own
+  words small under it, and **Open Settings** opens **Settings › API keys**, where the GPT
+  Subscription and every key are; send it again once one works. When an OpenAI key is set and was
+  not the problem, the button reads **Send it again on your OpenAI key**.
 - **Ending it**: **Esc** ends it (saying goodbye does not), and so does starting a spoken call.
   Opening a thread in the corner does not: the corner says *Thursday is still on the line*, with
   **Back to her** to return.
@@ -94,8 +106,9 @@ as on a spoken call, with no voice and no per-minute billing.
 It is kept with the other calls, marked *in writing*.
 
 During a spoken call the line writes to bots only. A file put down then is one she is told about —
-its chip says *she knows it is here* — and what to do with it can simply be said; she hands it to a
-bot.
+its chip says *she knows it is here* — and what to do with it can simply be said. A picture goes to
+the model behind her as it lands, as a smaller copy that fits the call's connection, so she can say
+what is in it; anything else she hands to a bot.
 
 ## Seeing the words
 
@@ -162,6 +175,9 @@ the wake phrase picks up; **Esc** is "not now". A missed ring stays on screen wi
 until called back or cleared with Esc. She cannot switch this on herself: when asked to call back,
 say where it is.
 
+Nothing rings while a thread is open in the corner: what that thread asks is answered there, and
+what another job asked or finished meanwhile rings once the thread is closed.
+
 ## History
 
 **Settings › Thursday › History** has two tiles. **Call history** lists every kept call, each with

package/guide/index.md

@@ -37,8 +37,11 @@ three of these that fit them rather than a list:
   on one page."
 - An errand on a website: a booking, an order, a form. The bot fills it in and stops at the
   pay button.
-- Their mail: what arrived, what needs an answer, a reply written and ready.
-- Something to make: a report with charts, a page, slides, a short video, a post with images.
+- Their mail: what arrived, what needs an answer, a reply written and ready; or something
+  finished sent by mail, to them or to someone they name.
+- Something to make: a report with charts, a page, slides, a short film for a birthday, a post
+  with images.
+- Something to understand: explained simply, a picture at a time, read aloud if they like.
 - Something on this computer: what is in a folder, a file converted, a script that runs again
   tomorrow.
 - Something that should happen by itself: "every weekday at nine, go through my mail and

package/guide/phone.md

@@ -94,16 +94,19 @@ back.
 
 - **Writing again while she works** joins what she is doing, so "no, the other one" changes course
   at once.
-- **Pictures and files** sent to her are kept in the workspace's `inbox` folder. She can look at a
-  picture herself or hand any file to a bot. Voice messages and videos are not read. Telegram hands
+- **Pictures and files** sent to her are kept in the workspace's `inbox` folder. A picture reaches
+  her as a picture with what was written with it, as in a call in writing; any other file she can
+  hand to a bot. Voice messages and videos are not read. Telegram hands
   over files up to 20 MB, and the app takes up to 45 MB from any chat app; a file that does not come
   through is named in the chat.
 - **Files she names in an answer** are sent with it, the newest three. What does not go — a fourth,
   or one too big (Telegram 50 MB, Discord 20 MB, any app 45 MB) — is listed under *Not sent — still
   on this computer*. Asking her to show what a bot made works the same way.
 - **A page** — a report, a deck, a design — arrives as up to nine pictures of it, since no chat app
-  opens one; the page itself stays on the computer. If the pictures cannot be drawn, the page file
-  is sent instead.
+  opens one. A page made to be read — a document, a deck, a brief, a trip, a digest — comes with a
+  PDF of the whole of it too, to keep or pass on; a design comes as its pictures alone. A page made
+  before this update comes without its PDF until its bot makes it again. If the pictures cannot be
+  drawn, the page file is sent instead.
 - **A bot's question, or finished work**, arrives as the bot wrote it, under a line naming the bot
   and the thread, with its files. Work started from the phone always comes back to the phone.
   Anything else — a routine, work started on the computer — comes only while no browser has the app

package/guide/setup.md

@@ -15,8 +15,14 @@ the plan it is on, so the plan can still be signed in to. The call screen's **Se
 **Settings › Thursday** ask the same way.
 
 Every step can be skipped and done later in Settings. On the microphone step the main button turns
-the microphone on (the browser asks first, by its address bar); the line under it goes on without
-one. The bots picked there are set up when it ends; they work once there is a model to run on.
+the microphone on (the browser asks first, by its address bar), and with it the wake phrase, and
+goes on to the next step; the line under it goes on without either. On the bots step her face gives
+way to their office, one desk for each bot switched on, with a job already under way that ends a
+few seconds in: each bot hands its part back and the report comes in. The bots picked
+there are set up when it ends; they work once there is a model to run on.
+The models step ends on **Exa**, a key for web search: without it a bot searches only when its own
+model can. The style step shows one of her four characters at a time, with a line on how she talks;
+**Previous** and **Next** move between them, and the one showing is the one set.
 With a sign-in or a key the last button is **Call her**; without either it is **Look around**.
 
 Once it has been left, by any of its buttons, it does not show again, and **Reset history** does not
@@ -29,7 +35,7 @@ The buttons at the top right of the call screen open **Thursday**, **Memory** an
 list is Thursday, Memory, Bots, Threads, Routines, Files, Skills, Connectors, Sign-ins, Models,
 API keys and Phone. ⌘K (Ctrl+K) jumps to a section's filter, and ⌘ (Ctrl) with a number from 1 to 9
 opens one of the first nine sections. Under community are **Ask on Discord** and **GitHub**. The
-theme — **System**, **Light** or **Dark** — is at the foot of the list.
+theme — **System**, **Light** or **Dark**, Light until one is picked — is at the foot of the list.
 
 ## Keys
 
@@ -86,11 +92,11 @@ A skill is a written-down way of doing something that a bot reads before it star
 ship with the app are shared by every bot: using the browser; using this Mac's apps (on a Mac only);
 making documents, slides, pages and small apps with charts; reading videos, podcasts, articles and
 PDFs; reports built on published numbers; a daily news brief; finding more skills; and writing a new
-one. **Marketer** and **Concierge** also carry skills of their own, for marketing and for trips,
-that no other bot sees.
+one. **Writer** and **Concierge** also carry skills of their own, for marketing a product and for
+trips, that no other bot sees.
 
 **Settings › Skills** lists them in groups: **Custom** (the user's own), one group for each bot that
-has its own (such as **Marketer's own**), and **Default** (the ones that ship, read-only). There a
+has its own (such as **Writer's own**), and **Default** (the ones that ship, read-only). There a
 skill can be switched off, uploaded (a `.md`, `.zip` or `.skill` file up to 20 MB), written from
 scratch, or deleted when it is the user's own. In one of the user's own, **Edit** on a file
 changes it in place.

package/guide/trouble.md

@@ -23,8 +23,9 @@ Say what happened and the one thing that fixes it; most problems are a setting o
 
 ## "Hey thursday" does nothing
 
-The wake phrase is off until it is switched on in **Settings › Thursday › Starting a call**, where
-the phrase can also be changed. It needs a browser with speech recognition, the microphone, and the
+The wake phrase comes on when the microphone is turned on in the first run; skipped there, it is
+off until it is switched on in **Settings › Thursday › Starting a call**, where the phrase can also
+be changed. It needs a browser with speech recognition, the microphone, and the
 app's tab open. When it cannot start, the screen says "Wake word off" with the reason. Tapping her
 face always works.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "thursday-agent",
-  "version": "0.22.0",
+  "version": "0.23.0",
   "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/SKILL.md

@@ -13,7 +13,8 @@ call. `S=<this skill's dir>/scripts`, `D=$THURSDAY_SKILLS/data-report/scripts`.
 |---|---|
 | `node $D/weather.mjs "<place>[, <CC>]" <from> [<to>] [--f]` | The forecast a line a day, or past the 16 days it reaches, what the same days were like the last five years. `--f` prints °F |
 | `node $D/fx.mjs <amount> <FROM> <TO[,TO…]>` | The amount at today's rate, with the rate's date and where it came from |
-| `node $S/itinerary.mjs <trip.json> [--name <file>]` | The trip as one page in your `artifacts/` folder: a photo and a map link per stop, costs added up. Uses the browser only for a `"photo"` page url |
+| `node $S/itinerary.mjs <trip.json> [--name <file>]` | The trip as one page in your `artifacts/` folder: a gallery of each place, what to do and watch for there, the money and what is left to book in view, the way, the days, costs added up. Uses the browser only for a `"photo"` page url |
+| `node $THURSDAY_SKILLS/artifact/scripts/document.mjs pdf <page path>` | The page as a PDF beside it, when they ask for one; a page sent to their phone goes with its PDF already |
 
 **The search is yours.** Flights, stays and their prices are this skill's work, not a question to
 hand to another bot: a hand-off pays for a second bot's prompt, skills and browser, and for the