create-pmos 0.516.0 → 0.518.0

package/workspace/guide/briefing.md

@@ -1,159 +0,0 @@
----
-type: Guide
-title: "The Briefing: today's brief"
-description: "The Briefing page of the console (/): The brief, the headline cards, Today, Needs you and how it is ranked, Mentions, Portfolio pulse, and what Done, Not yet and Drop do to an item."
-timestamp: 2026-10-15
----
-
-# The Briefing: today's brief
-
-The Briefing is the first page of the console at `/`. It has two columns. The left column holds the greeting, The brief, the headline cards, Needs you and Mentions. The right column holds Today and Portfolio pulse. It holds no calendar. The full calendar is the Calendar tab.
-
-Review is in the Work page, in its Review lens. Handled, What I could stop and Data you can lean on are in Reports, under Drafts.
-
-The Briefing shows only what PMOS already holds. When PMOS holds nothing for a section, the section says so.
-
-## What loads when you open the console
-
-When you open the console, it loads only what the Briefing needs. The other pages load the first time you open them: Calendar, Initiatives, Reports, Settings and the calendar popup. The first opening of a page can take a moment longer than the next ones. When a page cannot load, it says so. Open it again to try again.
-
-The dock is folded when the console opens. While it is folded, PMOS reads only how many agent runs need you, for the badge on the agent button. When you open the dock (Ctrl J), PMOS reads the sessions and the branches. The counts on the Work and Initiatives tabs come after the Briefing has its own data.
-
-## Headline cards
-
-The cards at the top are the signals that pass the relevance bar. Turn a card over to read its case.
-
-The cards come from two places:
-
-- **Your own data.** PMOS makes a card from each of these records:
-  - A Jira ticket or a plan (WBS) item assigned to you that is overdue, due today or blocked. "Blocked" means that the item is flagged, or that its status says blocked or on hold. The tickets come from the last My work read.
-  - An item in your Work list that is overdue or due today. An item that you parked, put on Waiting or moved to Later does not get a card.
-  - An item of today's morning brief that is worth asking, and an item of today's brief that is for you.
-- **The signal engine.** It reads the initiative records of the repository, for example a spec written after the build.
-
-The cards take the same order as Needs you (see Needs you, The order): a pinned Critical card first, then the cards that cannot wait, then the rest by score. PMOS adds at most 5 cards from your own data. A card shows only the values that its record holds. When the record has a link, for example a Jira ticket, the case of the card has a link to it. The link opens in a new tab. When no record gives a card, the deck says that nothing needs you.
-
-Above the cards, the greeting names the part of the day, for example "Good morning, Wawan". The name is the first word of the git user name on the computer where PMOS runs. When git holds no name, the greeting has none. The part of the day follows the clock. There is no button to change it. When the clock moves to a new part, the line under the greeting and the order of the cards change after you stop using the page for a minute.
-
-## The brief
-
-The brief is one paragraph under the greeting, above the headline cards. Read it to know the day in a few seconds. It says, in this order:
-
-1. The one decision that the day turns on. When no row is a decision that only you can make, it names the first row of Needs you.
-2. How many things need you, how many are overdue, and the oldest overdue item.
-3. Who waits for your reply to a mention.
-4. How many meetings are left today, and the next meeting that still has a to-do before it.
-5. Which initiatives are off track or at risk, and how many are on track.
-
-Each number and each title comes from a row on the page. The count of things that need you is the same as the count of Needs you. Press a title to go to its row. The line at the right of the title says when PMOS wrote the paragraph and which sections it read. When a section changes, for example when you mark an item done, the paragraph changes too. In the evening the paragraph says what is still open and how many meetings you held.
-
-PMOS writes the paragraph from the rows on the page. It does not call a model and it does not write a record.
-
-## Today
-
-Today starts with one line: the meeting that is on now or next, how many meetings are left, and how many of them are prepped, with a small ring. **Open calendar** opens the calendar. Under it, Today lists the meetings of the day, in time order. Each row shows:
-
-- The start time and the length.
-- The people and the initiative of the meeting.
-- **Prepared**, as chips: what PMOS holds for the meeting. This is the agent's prep note, your notes on the event, the notes you started for it, and the last notes of the same meeting. When PMOS holds none, the row says "Nothing prepared yet".
-- **Before you go**, as chips: your open items that name the meeting. A meeting with nothing held says "nothing prepared". A meeting with everything done says "prep ready".
-
-A meeting that is over is dimmed. The meeting under way is marked **Now**. The next one is marked **Next**. When the calendar holds no meeting for today, Today says so.
-
-A Today row is a reference. It has no button that changes anything.
-
-## Needs you
-
-Needs you lists what only you can do. Its header says how many decisions, how many items are yours, how many come from the agent, and how many are overdue. A decision row has a **decision** tag. When it cannot be undone it also says **hard to undo**. An item of yours has a **Work** chip: Work is where the item lives.
-
-### The order
-
-Every source goes into one list, and PMOS puts the rows in one order. PMOS does not call a model to do this. The same rows always give the same order.
-
-**Do these first** shows the three rows to do first. A row can be here for one of two reasons:
-
-- It cannot wait. A signal engine card that is Critical, and a promise to someone outside PMOS that is due or overdue, always come first. Every such row shows, even when there are more than three. The header says how many cannot wait.
-- It scores highest of the rest.
-
-**Next up** shows the other rows in score order. It shows five rows. The others are in the fold "below the line".
-
-Each row has a line of reasons under its title, for example "Frees 3 agent runs · 2 days old · about 2 min". Every reason is a part of that row's score. A reason that is not true for the row does not show. The last reason is the effort. PMOS estimates the effort from the kind of row, so it always says "about". An agent draft takes about 2 minutes. An item outside PMOS or a card with a suggested move takes about 15 minutes. A title that names a review, a spec or a PRD takes an hour or more.
-
-The score uses:
-
-- How much the item matters. This is its priority, or the signal engine's number for a card. An initiative that is off track adds to it.
-- How soon it is due. An overdue item is the most urgent.
-- Whether you can undo it.
-- How many agent runs and people wait for it. An agent that waits on your drafts counts here.
-- How long it has waited. After a week the item counts 1.5 times as much, so no row waits for ever.
-- Your flag. A flagged item counts 1.5 times as much.
-- The effort. A short task ranks above a long task of the same score.
-
-Three or more rows of one kind on one initiative show as one row that opens to its members.
-
-### What is not on the list
-
-PMOS does not rank an item that you cannot act on now. A line above the list counts them: "Not on this list: 4 waiting on others · 3 later · 2 someday". The items are not deleted. Press the line to open Work. A flagged item and a Critical card stay on the list when they are waiting or set to later. An item you finished, and a mention you marked read, are gone.
-
-A line also says when items have been untouched for a week. Press it to open the Work page, where you can review them.
-
-### The rows
-
-The rows come from these sources:
-
-1. Your own items that are overdue or due today.
-2. Items outside PMOS that wait for you to confirm: talk to someone, meet, call, ask.
-3. Decisions that only you can make.
-4. Drafts and blocks from the agent.
-
-The decisions come from these records:
-
-- A Jira ticket or a plan item assigned to you that is overdue, blocked, due today, or marked as your decision. Its row has the ticket key, and its case has a link to the ticket.
-- A signal engine card that has a suggested move, or is Critical.
-- An item of today's morning brief that is worth asking. The brief was not sure enough to act, so ask first.
-
-An item that is in your own items does not show again as a decision. **Done** and **Later** on a ticket row change the item in your Work list. They do not change Jira.
-
-An agent row says how old its oldest draft is and how many runs it holds. When the agent states how sure it is, whether you can undo the move, or how long it takes, the ranking uses that. A fact the agent did not state reads "Not known yet" and counts as neutral.
-
-Press a row to open it in place. A row of your own item has three actions. Each one writes to the item itself, the same record the Work page shows.
-
-- **Done** marks the item done. For an item outside PMOS you can first type one line about what happened. The line is optional.
-- **Not yet** asks again later. Choose **Later today**, **Tomorrow** or **Next week**. The item leaves Needs you and comes back on that day.
-- **Drop** removes the item. Press **Undo** in the notice to bring it back.
-
-PMOS can see evidence that an outside item is done. For example, a meeting with the person is on the calendar. Then the row says "Looks done: a meeting with Ana is booked Tue 10:00. Confirm?" PMOS never marks the item done itself. The item changes only when you press **Done** or **Yes, it is done**.
-
-The headline cards, the Mentions list and the Today view of the Work page use the same order.
-
-## Mentions
-
-Mentions lists the places where someone mentioned you today: Slack, Jira, Confluence and mail. The list comes from today's morning brief. A mention that needs your reply comes before one for your information. Among the replies, the one that has waited longest comes first. When there is no morning brief for today, Mentions says so.
-
-The section is quiet. It shows one line that names who waits for your reply, for example "Priya in Slack and Dara in Jira are waiting on your reply." The header says how many need a reply. Press **Show all** to open the list. A tab for each source filters the list. Each row shows the person, the text they wrote, the source and the place, the time, and **needs your reply** or **for your information**. Each row has these actions:
-
-- **Open in Slack** (or Jira, Confluence, Mail) opens the mention in a new tab. A mention with no link has no such button.
-- **Add to Work** adds an item to your Work list, for example "Reply to Dara (Jira) by today".
-- **Mark read** removes the row from the list. Press **Undo** in the notice to bring it back.
-
-A mention that is already a row of Needs you does not show again in Mentions. That row in Needs you has a **mentioned you** tag.
-
-PMOS does not reply, react or post in Slack, Jira, Confluence or mail.
-
-## Portfolio pulse
-
-Portfolio pulse says how many initiatives need attention, then shows one bar for the status of the initiatives and one row for each initiative. An initiative shows when it has a promised date, or when PMOS holds a read of its Jira epic. A row from a Jira epic shows "3 of 8 done" and a bar. "Done" counts the tickets under the epic that are done in Jira. A row with blocked tickets says **Blocked**. The Jira read is the last Jira status check; the opened row says its date. When no initiative has a promised date or a Jira read, the pulse says so. **All initiatives** at the bottom opens the Initiatives page. Press a row to open it in place. It shows why the initiative has that status, the promised date against the forecast, and the Jira progress when PMOS holds it. The page does not change.
-
-To go to the initiative, press **Open initiative** inside the opened row.
-
-## Where each action lives
-
-An item has its actions in one place only. On the Briefing, Today and Portfolio pulse show items, and do not change them. Needs you is where you decide and where you confirm your own overdue items.
-
-## On a phone
-
-At 400 pixels wide the Briefing is one column (greeting, The brief, cards, Needs you, Mentions, Today, Portfolio pulse) with no sideways scroll. Each button in an opened row is 44 pixels high.
-
-On a screen wider than 600 pixels, the top bar stays at the top of the window when you scroll a page. The top bar holds the five tabs, the date and the tool buttons. Cards that also stay in place as you scroll, such as the right column, stop under the top bar.
-
-On a phone, every console page has the same top. The page title has Record at its right. The sunrise line is under it, then the tool buttons in one row. The five tabs share the width, and each tab shows an icon over its name, so Initiatives and Reports are always on screen. A count shows at the top right of its tab's icon. A person in a row shows as a small round letter, and you can tap anywhere in the 44-pixel square around it. A line that has a sentence and a due date wraps like normal text.

package/workspace/guide/calendar-popup.md

@@ -1,46 +0,0 @@
----
-type: Guide
-title: "Calendar popup"
-description: "How to open the full calendar over any page of the console with the calendar button or the C key, how to close it, and how it remembers the zoom."
-timestamp: 2026-10-11
----
-
-# Calendar popup
-
-The calendar popup shows the Calendar tab's grid in a drawer over any page of the console (`/`). You do not leave the page you are on.
-
-## Open it
-
-Press the **calendar button** in the top bar. It is next to the search button. Or press **C**.
-
-The popup is never open when the page loads.
-
-The key **C** does nothing in these cases:
-
-- You are typing in a field, for example the search box.
-- You hold Ctrl, ⌘ or Alt.
-- A sheet or the search palette is open.
-
-## Use it
-
-The popup has the same grid as the Calendar tab, with the same five zoom levels, the layer chips, the detail, the Free time list and the lanes. It has no headline deck. It opens on the Week the first time. Press **+** or **-** to zoom. The popup opens at the zoom you used last, and with the layers you hid left hidden. The console keeps that zoom until you change it.
-
-The popup and the Calendar tab are two separate views. A zoom or a date you choose in one view does not change the other.
-
-## Close it
-
-Close the popup in one of three ways:
-
-1. Press **Esc**.
-2. Press the dark area around the popup.
-3. Press the close button (×) at the top right.
-
-The focus goes back to the control that was in use before the popup opened. When you used the button, the focus goes back to the calendar button.
-
-## On a phone
-
-On a phone the popup fills the screen. The page does not scroll sideways. Every button is at least 44 pixels high and wide.
-
-## Related
-
-- [Layout](layout.md) lists all the keys.

package/workspace/guide/command-palette.md

@@ -1,77 +0,0 @@
----
-type: Guide
-title: "Command palette"
-description: "How to use the ⌘K palette: run a command, see its command-line form, keep a note, ask the bound session, search Knowledge, Memory and the Guide, and use the compose line on a phone."
-timestamp: 2026-10-07
----
-
-# Command palette
-
-The command palette is one box for three jobs: open something, run a command, or keep a note. Press **⌘K** (Ctrl+K on Windows and Linux) to open it. Press **Esc** to close it.
-
-On a desktop, the palette is a dialog in the middle of the screen. The search box is at the top with a search icon, the scope switch is under it, and a footer at the bottom shows a hint and the keys. On a phone it is a sheet (see "On a phone").
-
-## Rows
-
-Type in the box. The rows change as you type. Rows of one kind sit under one small label, for example Commands or Initiatives, and each row has an icon for its kind. The selected row has a ring and an arrow. The rows come in this order:
-
-1. **Matched rows.** A command, an initiative, a repository, a session, a tab or a view whose name matches what you typed. A command shows its command-line form next to its name, for example `pmos item`. You can run the same command from a terminal.
-2. **Capture as note.** Keeps what you typed as a note.
-3. **Ask the session.** "Ask" and the name of a session. The session is the terminal tab you are in. When you are not in a terminal tab, it is the terminal of the selected initiative, or else the latest terminal of this repository. It shows only when a terminal tab is open.
-
-When nothing matches, **Capture as note** is the top row and is already selected. Press **Enter** to keep the note.
-
-Press **Up** and **Down** to move the selection. Press **Enter** to choose the selected row. You can also press a row.
-
-## Capture as note
-
-Capture as note keeps your words in one file and changes nothing else.
-
-- The file is `requirements/capture-YYYY-MM-DD-<n>.md` in the state folder of the selected repository. That folder is `pmos/state/` in a kit repository (one with `pmos/state/initiatives/` and no `planning/initiatives/`), and `planning/` in any other repository. It is the folder that holds the initiatives, so a later step finds the note there. `<n>` counts from 1 for each day.
-- The file has `type: Reference`, a title, a timestamp, `source: capture` and `by`. The text is the body, unchanged.
-- A file is never overwritten. When two notes race for one number, the second takes the next number.
-- A toast shows the name of the note. The palette closes.
-- When the note cannot be saved, the palette stays open, shows the reason, and keeps your text. Press **Enter** to try again.
-- Select a repository first. A note is kept in one repository, and is never kept in another one.
-
-The note is not a decision and not a requirement yet. A later step reads new notes and files each as a proposal for you to keep or drop.
-
-## Ask the session
-
-**Ask** sends what you typed to the session named on the row, then presses Enter. It works as if you had typed the text in that terminal. When the session is not connected, nothing is sent and the palette says so.
-
-## Portfolio reports
-
-Three commands write a report across every repository into the hub repository:
-
-| Command | What it writes |
-|---|---|
-| Portfolio report: weekly | The weekly report. |
-| Portfolio report: OKR | The OKR report. |
-| Portfolio report: matching… | The report on the initiatives whose names match words you type. A sheet asks for the words. |
-
-Nothing is written until you run one. When the report is written, the workspace says the path and opens the file as a tab. If a repository could not be read, the message names it. If no hub repository is set up, the message says so and nothing is written.
-
-## Search scopes
-
-The tabs under the box set where the search looks.
-
-| Scope | What it searches |
-|---|---|
-| All | Commands, initiatives, repositories, sessions, tabs and views. Strategy documents and decision records are also found here. |
-| Knowledge | Strategy documents, decision records, notes and governance files of the selected repository. Choose a row to open the document in a tab. |
-| Memory | The entries in Memory. Choose a row to read the entry in a sheet. |
-| Guide | The pages of this Guide. Choose a row to open the page in a tab. |
-
-The palette reads the lists of all three scopes when it opens. When a list cannot be read, the palette says which scope failed and why. The other scopes still work.
-
-## On a phone
-
-The palette opens as a sheet from the bottom edge. Each row is at least 48 pixels high, and the rows are reached by touch.
-
-On a phone, the scratchpad is the **compose line** at the bottom of a terminal tab. (On a desktop, open it with **Scratchpad** in the bar at the bottom of the dock.) Type a message there and press **Send**. The text is typed into the session and the line clears. The line keeps your text for each session until you send it, so a message you did not finish is still there when you come back.
-
-## Related
-
-- [Live notes](live-notes.md) keeps a note for each day.
-- [Initiatives](initiatives-and-next-steps.md) explains what an initiative shows.

package/workspace/guide/console3-sessions.md

@@ -1,147 +0,0 @@
----
-type: Guide
-title: "Sessions in console3: start, open, message, read and end your sessions"
-description: "How the Sessions panel in console3 groups your sessions, how to start a session, how to open a session as a conversation or as its terminal without leaving console3, how to send a message to a session, and how to end a session."
-timestamp: 2026-10-14
----
-
-# Sessions in console3: start, open, message, read and end your sessions
-
-Press the **Sessions** button in the console3 header to open the panel. It is the bolt icon with no label. Point at it to see its name. When a session needs you, a count shows on it. It shows your sessions in four groups: **On a card**, **Started by me**, **Past (7 days)** and **Automatic**.
-
-When the session that you opened last is still running, the **Sessions** button opens that session directly, on its conversation. To see all your sessions, press **All sessions** at the top of the session sheet. If that session has ended, the button opens the panel.
-
-The panel opens on the session that you opened last. Its row is open, so you can read the conversation and send a message without searching for it. A session counts as opened when you open its row or its terminal.
-
-## The dock
-
-The dock is folded when you first open the console. To open it, press Ctrl J (⌘J on a Mac), or use **Open the dock** in the **More** menu. The browser keeps your choice: when you leave the dock open, it opens on the Briefing next time. On the other tabs it is folded away, and no rail of buttons is left at the right edge.
-
-## Start a session
-
-You start a session in console3. You do not need the classic app.
-
-1. Do one of these steps:
-   - Press **+** in the header of the dock.
-   - Press **+ session** on a branch that has no session.
-   - Press **New** next to **Started by me** in the Sessions panel.
-2. The **New session** sheet opens. Type a name, or leave it empty to use `Shell` or `Claude`.
-3. Select the **Agent**: Shell or Claude. A Claude session uses the profile, the launch flags and the tier from Settings.
-4. Select the **Board**: the repository that the session works in. The repository that is selected in the dock is the default.
-5. Select where the session runs in **Runs on**. The list shows the working trees of the board that you selected:
-   - **Automatic**: the server selects the tree.
-   - A listed tree: the session runs in that working tree.
-   - **New branch**: type the branch name. The session runs in its own working copy of the new branch.
-6. Press **Start**. The session starts, and it opens in a sheet on the same page. If you selected a different board, the dock changes to that board.
-
-If the server cannot start the session, the sheet shows the reason.
-
-## Read a row
-
-Each row under **Started by me** shows the state of the session, how long ago it started, and its tree. The state comes from the workspace server, for example `working` or `quiet`.
-
-If the server finds that the process of a session stopped (for example, after a restart), the session moves to **Past**.
-
-## Open a session
-
-1. Press the row to open it.
-2. Press **Open the session**.
-
-The session opens in a sheet on the same page, on its conversation. To close the sheet, press its close button. The session continues to run.
-
-Two buttons at the top of the sheet change the view:
-
-- **Conversation**: your messages and the replies of Claude, with a box to send a message. This is the view that opens first.
-- **Terminal**: the live terminal of the session. You can type in it. When the terminal has focus, Esc and Tab go to the terminal. Use it for the things that the conversation does not show, for example a menu of Claude Code or the full output of a command.
-
-Press **Conversation** to go back. The terminal stays connected while the sheet is open, so nothing restarts when you change the view.
-
-### The conversation
-
-The conversation comes from the transcript that Claude Code writes on this computer. It shows the words of Claude as Claude wrote them. Nothing is summarised, and nothing is sent to a different place.
-
-- Your messages are on the right. The replies of Claude are on the left. Lists, bold text and code show as formatted text.
-- A grey line, for example "Used Bash, Read ×2", shows a run of tool calls. Press it to see each call and its target, for example the file or the command.
-- While Claude works, a line says so. Press the stop button next to the message box to stop Claude. It types Esc into the session.
-- When Claude asks before it uses a tool, a card shows the question and its options, for example **Yes** and **No**. Press an option to answer. You can also press **Answer in the terminal**.
-- Type a message in the box and press Enter to send it. Shift Enter starts a new line. **/compact** and **/clear** put that command in the box.
-- The tag above the conversation shows the state: **Working**, **Needs you**, **Your turn**, **Shell** or **Ended**.
-
-A shell where Claude has not started says "No Claude in this shell yet". Press **Start Claude here** to start Claude in that shell. Its conversation then shows in this view.
-
-If PMOS cannot find the transcript of a Claude session, the view says so, and it does not show the transcript of a different session. Read the session in the terminal. PMOS looks for transcripts in `~/.claude`, in each `~/.claude-*` profile folder, and in the folder that `CLAUDE_CONFIG_DIR` names.
-
-At **2/3** and **Whole**, the sheet also shows a list of your running sessions at the left. Each row shows the session name and, below it, the agent and its state. Press a session to open it. The conversation starts next to the list.
-
-### The scratchpad
-
-Below the terminal is a scratchpad. It keeps text for this session only. The text is saved on this machine as you type, and it is there when you open the terminal again.
-
-- To send the text to the session, press **Send to terminal**. The text is typed into the terminal. Enter is not pressed, so you can read it and press Enter yourself.
-- To hide the pad, press **Scratchpad** above it. The text is kept. The terminal gets the room back. The page remembers if the pad was hidden.
-- To make the pad taller or shorter, drag the grip on the line above it. Or select the grip and press the up arrow or the down arrow. The terminal gets the remaining room. The page remembers the height. To go back to the default height, double-click the grip.
-- Esc in the pad closes the panel. Esc in the terminal goes to the terminal.
-
-### The size of the sheet
-
-Four buttons in the header of the sheet set its width: **Normal**, **Half**, **2/3** and **Whole**. Half is half of the window. 2/3 is two thirds of the window. Whole is the full window. The terminal fits the new size. The page remembers your choice for the next session you open. On a phone the panel is already full width, so the buttons are not shown.
-
-The **Open the session** link in the sessions dock opens the same sheet.
-
-## Send a message to a session
-
-1. Press the row to open it.
-2. Type your message in the message box.
-3. Press Enter.
-
-Your message is typed into the session, and Enter is pressed. The message shows in the panel at once.
-
-## Read the conversation
-
-The panel shows the conversation of a Claude session:
-
-- Your messages are on the right.
-- The replies of Claude are on the left. Lists, bold text and code show as formatted text.
-- A grey line, for example "Used Bash, Read ×2", shows the tools that Claude used. The session sheet also shows the target of each call.
-- While Claude works, a grey line says so.
-
-The panel reads the conversation from the transcript that Claude Code writes on this computer. Nothing is sent to a different place. The panel updates while it is open.
-
-A session that is not a Claude session, or a shell where Claude has not started, has no conversation. The panel shows what you sent, and the output is in the terminal. To read it, press **Open the session**.
-
-The **Message** box in the dock and the reply line below a card do the same.
-
-If the connection to the workspace server is down, the message is not sent. The message stays in the box, and a notice tells you.
-
-**Try again** on a session that has not started is not available. The session can wait for a question, for example whether to trust the folder. Open the session and read the question first.
-
-## Background runs
-
-Some jobs run in the background, with no terminal: the Initiative Driver, a refresh of Jira status or My work, and the other jobs PMOS starts by itself. They are listed under **Automatic**.
-
-- While a background run works, open it to see each step: the tool it uses and what it does (for example `› Bash pmos driver propose …`), the words of the agent, and a step that failed.
-- When a background run ends well, its row and its card show the first line of the agent's last message, for example "Filed 3 proposals".
-- When a background run does not end well, its row and its card give the reason: you stopped it, it ran past the time limit, the process was ended, it exited with an error code, it reported an error, or it used a tool that is not allowed in a background run.
-- If PMOS restarts while a background run works, its result cannot be read. The row and the card say "Interrupted: PMOS restarted while this run was working". Run the job again.
-
-A background run does not send replies to its card as a terminal session does. It files its work with its own commands, for example the Driver's proposals on the initiative.
-
-## End a session
-
-1. Press the row to open it.
-2. Press **End the session**.
-3. Press **End** to confirm, or press **Keep it** to cancel.
-
-When you end a session, its process stops and the session is removed. Any pending change stays a proposal. If the process does not stop immediately, press **End** again to remove it.
-
-A session that is on a card has the same **End the session** control below its card.
-
-## Remove a past session
-
-A session under **Past (7 days)** has ended. To remove it from the list:
-
-1. Press the row to open it.
-2. Press **Remove**.
-3. Press **Remove** to confirm, or press **Keep it** to cancel.
-
-The record of the session is deleted. Its commits and its branch stay.

package/workspace/guide/document-sheet.md

@@ -1,89 +0,0 @@
----
-type: Guide
-title: "The document sheet"
-description: "How to read a document as rich text with its outline, edit it, review the agent's proposals section by section, read the edit log, keep its Confluence and Google Doc copies in step, see the documents around it, and clear a stale document."
-timestamp: 2026-10-14
----
-
-# The document sheet
-
-Open a document in Initiatives › Documents, in an initiative's Docs, or from Reports. The document opens in a sheet on the right. On a phone, it opens from the bottom. The segment under the title has six modes.
-
-To make the sheet wider, select **Half**, **3/4** or **Whole** beside Close; **Normal** goes back to the standard width. The sheet keeps your choice in this browser and opens at that size next time. On a phone the sheet always fills the screen, so the sizes do not show.
-
-## Read
-
-Read shows the document as formatted text: headings, bold, links, tables, checklists and callouts. The front matter shows as properties at the top.
-
-- Each section shows who changed it last: a person, or the agent and the person who accepted it, with the revision and the day. Select the name to open that revision in the edit log.
-- **Show who wrote what** colours each section: blue for a person, purple for the agent.
-- **Markdown source** shows the file as text. **Copy the markdown** copies it.
-- The **outline** beside the text lists the headings, nested by level. The section you read is marked as you scroll. Select a heading to go to it, or the arrow beside a heading to fold the headings under it. A document with more than 12 headings has a **Find a heading** box. An orange dot marks a section that cites a source that changed. A purple dot marks a section that an open proposal changes.
-- **Hide the outline** hides it, and the sheet keeps that choice in this browser. On a narrow screen the outline is a button, **Outline**, that names the section you read and opens the list over the text.
-- When an open proposal changes a section, a note shows above that section. Select **Show change** to see the difference in place.
-
-## Edit
-
-Edit opens the whole document as rich text. Use the toolbar for the paragraph style, bold, italic, code, links, lists, checklists, tables and dividers. Use **Markdown** to edit the same draft as text, and **Rich** to go back. The front matter shows as fields.
-
-1. Change the text. A changed section shows **Edited** next to its heading.
-2. Write why you change it. The sheet does not save a change without a reason.
-3. Select **Save**.
-
-A section that you did not change is saved exactly as it was. The reason goes to the edit log with your name.
-
-## Proposals
-
-Proposals lists what the agent drafted and you did not accept or reject yet. To ask for a change, see [Ask the agent from the page](ask-the-agent.md).
-
-1. Read the difference of each section. Added words are green. Removed words are struck through.
-2. Clear the tick of each section that you do not want.
-3. Slide to accept. Only the ticked sections are written, as one revision.
-
-If a section changed after the agent drafted it, you cannot tick it. Ask the agent again. To reject a proposal, select **Reject** and write why.
-
-## Edit log
-
-The edit log lists every change, newest first: who wrote the text, how it came in, the reason, the sections and the words added and removed. It also lists rejected proposals, requests to the agent, and documents marked as still current. Use **All**, **People**, **Agent** and **Outside PMOS** to filter it.
-
-- A change made outside the sheet (in an editor, or by a commit) shows **outside PMOS**, with its commit when git knows it. When it has no reason, select **Add a reason**. The reason is added to the log; the revision itself does not change.
-- Select **Show the change** to see the difference.
-
-## Stale documents
-
-A document is stale when a document that it links to changed after it. The sheet shows a banner that lists those sources and the sections that cite them.
-
-- Edit the sections, or ask the agent for an update.
-- If the document is still right, select **Mark as still current** and write why. The mark counts as a change, so the banner clears.
-
-## Copies in Confluence and Google Docs
-
-The header shows one chip for each copy of the document in Confluence or Google Docs, with its state: in step, behind (the copy has changes), PMOS ahead (PMOS has changes), both changed, or not checked. Select a chip to open **Copies in other tools**. Each copy shows its state, who changed it last and when, and when it was last checked.
-
-- **Check now** starts an agent session that reads the copies with your connectors. The states change when it finishes.
-- **Open in Confluence** or **Open in Google Doc** opens the copy.
-- When the copy is behind or both changed, **Bring their change in as a proposal** asks the agent to read the copy and draft its changes as a proposal. Review it in Proposals, section by section. PMOS keeps a fingerprint of the copy, not its text, so the proposal is where you see the difference.
-- When PMOS is ahead, **Update the Google Doc to this version** (or the Confluence page) starts an agent session that writes the copy. You have five seconds to select **Undo**.
-- **Link a copy** takes the address of a Confluence page or a Google Doc. The sheet finds the tool from the address.
-
-PMOS never overwrites the document from a copy.
-
-## Health and Relations
-
-Health shows the checks of the document and how many pass.
-
-Relations shows a graph of the documents around this one: the documents it uses on the left, its initiative and goals on top, and the documents that use it and its copies on the right. A dashed orange line shows a document that is out of step. Select a document to open it. The lists under the graph name the same documents. From Initiatives › Documents, **Open the full graph in Docs** shows the whole graph.
-
-## Report documents
-
-A report that you set up opens in the same sheet. Each cycle of a report is one document. The sheet adds these parts for a report.
-
-- **The head.** A chip says **Draft** or **Issued**. A second chip names the report. A third chip names the format: Google Slides, Google Doc, Google Sheets, Confluence or PDF.
-- **Read.** The text is drawn in the format of the report. A Slides report shows slides. A Sheets report shows grids. A Google Doc or a Confluence report shows a page. A PDF report shows A4 pages. The words come from the markdown file. Edit the file, or ask for a change, and the format changes with it.
-- **Issue.** Press **Issue** on a draft when you have sent it. PMOS sends nothing. Issue records that you did.
-- **Download.** Open the menu with the three dots. A Slides report offers PDF and PowerPoint. A Sheets report offers Excel and CSV. A Google Doc report offers PDF and Word. A Confluence report offers PDF and Word. A PDF report offers PDF. For PDF, the sheet opens the print dialog. Choose "Save as PDF" in it.
-- **Copies.** A report has one live copy, in the tool of its format. A PDF has none. Before the copy exists, the panel says "Not created" and offers **Create the Google Slides copy** (or the name of the tool of the report). PMOS waits five seconds before it starts, and **Undo** stops it. When PMOS is ahead of the copy, the button is **Update the copy**. PMOS writes to Google or to Confluence only when you press one of these buttons.
-
-## Issued reports are frozen
-
-An issued report cannot be edited. **Edit** says so, and offers **Start the next cycle**. The next cycle is a new draft. If the next draft already exists, **Start the next cycle** opens it. If it does not exist, PMOS drafts it on the day of the schedule.