heyquilt 0.3.109 → 0.3.116

package/README.md

@@ -238,6 +238,7 @@ See [Claims](#claims).
 | `quilt_project_rules` | The project's rules for AI, the same for every tool: AGENTS.md (root and folders, else CLAUDE.md), Cursor rules that always apply, and the design system (DESIGN.md, or the file AGENTS.md names with `Design system: <path>`) |
 | `quilt_inbox` | What is waiting for you: mentions (`@yourname`), direct messages and tasks handed to you since you last looked |
 | `quilt_webhook_subscribe` / `quilt_webhook_unsubscribe` | Have each mention, direct message and handed-over task POSTed to a URL of yours as it happens, signed; or stop that |
+| `quilt_webhook_test` | POST a signed `webhook.test` event to your webhook now, and say what the receiver answered |
 | `quilt_check_update` | Whether the Quilt you run (your image) is current; an old one is told to update the app |
 | `quilt_send_file` | Send a project file through chat (secrets and paths outside the project are refused) |
 | `quilt_get_file` | Download a shared file (again) |
@@ -412,11 +413,39 @@ A receiver that is down or answers 5xx is tried again a few times; whatever was
 POSTed is still in `quilt_inbox`. `events` narrows the subscription; calling
 again replaces it; `quilt_webhook_unsubscribe` ends it.
 
-For a hosted agent the relay delivers, so the webhook works even when the agent
-itself is asleep, and the subscription carries over when it joins another
-session. For an agent joined from a computer, its Quilt delivers and keeps the
-subscription in that folder's `.quilt/webhook.json`. URLs must be `https` and
-public (an agent on a computer may also use `http` on that computer).
+`quilt_webhook_test` POSTs a `webhook.test` event now (signed like any other) and
+says what the receiver answered. With `coalesce: true` a burst wakes the agent once:
+events are gathered for 2 s, and any that follow within 30 s of a POST go together in
+one more POST; a POST with several carries the first one's fields on top (the shape
+above) and all of them, oldest first, in `events` (with `count`). Without it, one POST
+per event.
+
+The relay keeps and sends every agent's webhook, hosted or joined from a computer
+(`quilt join`), so it works while the agent, or its computer, is asleep; it is one
+webhook per agent, and it covers each session the agent is in (a hosted agent's, and
+each one an agent on a computer connects to). So an agent that only has an invite
+link joins, subscribes once, and is woken from then on with nothing else set up. URLs
+must be `https`, without credentials, and every address the host resolves to must be
+public, checked when it is set and again before each POST; redirects are not followed.
+An agent on a computer may also use `http` to that computer (a receiver running next
+to it): that one its own Quilt sends, while it is awake.
+
+From a shell, the same webhook:
+
+```
+quilt join <invite> --webhook-url https://example.com/hook --webhook-bearer-env MY_HOOK_KEY
+quilt webhook set https://example.com/hook --bearer-env MY_HOOK_KEY [--coalesce]
+quilt webhook            # status: URL, events, who sends it, the last POST
+quilt webhook test
+quilt webhook clear
+```
+
+Keys are given by environment variable name (`--bearer-env`, `--secret-env`), never on
+the command line, and are never shown again. A folder that subscribed with an older
+Quilt (which sent the webhook from the computer, kept in `.quilt/webhook.json`) hands
+it to the relay, same URL and secret, the next time it is let in; from then on only
+the relay sends it, so the agent is not woken twice. A relay too old to keep it leaves
+it with the computer, as before.
 
 ### Agents in workspaces
 

package/RELEASES.md

@@ -11,6 +11,96 @@ Format: `## <version> — <YYYY-MM-DD>`, an optional one-line summary, then bull
 Lead each bullet with a short bold phrase. Inline `code` and **bold** are rendered;
 nothing else is.
 
+## 0.3.116 — 2026-10-25
+
+- **Source control has its own command, `seam`.** Quilt Source's git verbs (`seam log`, `seam merge`, `seam checkout`…) now come from their own package, `@heyquilt/seam`, with their own sign-in (`seam login`) and their own MCP server (`seam mcp`, tools named `seam_*`). The Quilt app's `quilt` command and Quilt's MCP no longer carry source control: Quilt sessions and Quilt Source are separate products. Block folders now hold `.seam/block.json`, and agents give seam their key with `SEAM_TOKEN`. The docs at frame.heyquilt.com say the same.
+
+## 0.3.115 — 2026-10-25
+
+0.3.114 did not finish publishing, so this release carries it.
+
+- **Quilt Source has its own site.** frame.heyquilt.com now opens on a page that says what Quilt's source control is (quilts, squares, patches and blocks, how a square gets to main, what happens to a conflict, how agents use it), with docs: getting started, git commands side by side, squares and merging, agents, and the HTTP API. Your repos are under Your repos, and old repo links still work.
+- **A repo's home page.** A repo opens on its numbers (patches on main, patches this week, open squares, conflicts, how long squares take to merge, each with its trend), its files with the last patch that changed each one, patches a day for the last month, its README, what it's written in, its open squares, and who works on it.
+- **A fresh import takes merges at once.** Right after `quilt import git`, merging into main was refused for an hour because the imported history counted against main's hourly merge limit. Imported patches no longer count.
+- **Your cloud AI runs the newest Quilt on its machine.** When your cloud AI updated Quilt on its machine (by running the install script), its AI tool's Quilt tools and hooks kept running the version the machine was made with, and the AI could not fix that by itself. Now the machine's `quilt` command, and the Quilt tools and hooks of every AI tool on it, run whichever installed Quilt is newest, and a machine with a newer one installed starts on it the next time it goes idle.
+
+## 0.3.114 — 2026-10-25
+
+- **Quilt Source has its own site.** frame.heyquilt.com now opens on a page that says what Quilt's source control is (quilts, squares, patches and blocks, how a square gets to main, what happens to a conflict, how agents use it), with docs: getting started, git commands side by side, squares and merging, agents, and the HTTP API. Your repos are under Your repos, and old repo links still work.
+- **A repo's home page.** A repo opens on its numbers (patches on main, patches this week, open squares, conflicts, how long squares take to merge, each with its trend), its files with the last patch that changed each one, patches a day for the last month, its README, what it's written in, its open squares, and who works on it.
+- **A fresh import takes merges at once.** Right after `quilt import git`, merging into main was refused for an hour because the imported history counted against main's hourly merge limit. Imported patches no longer count.
+- **Your cloud AI runs the newest Quilt on its machine.** When your cloud AI updated Quilt on its machine (by running the install script), its AI tool's Quilt tools and hooks kept running the version the machine was made with, and the AI could not fix that by itself. Now the machine's `quilt` command, and the Quilt tools and hooks of every AI tool on it, run whichever installed Quilt is newest, and a machine with a newer one installed starts on it the next time it goes idle.
+
+## 0.3.113 — 2026-10-24
+
+- **@you is for you, @you's AI is for your cloud AI.** The AI sessions on your computer (Claude Code, Cursor, Codex…) no longer read, get woken by or have to answer @mentions of you, direct messages to you or tasks for you: those are yours, and you see them in the app as before. Your AI on your computer only does what you ask it at the keyboard. "@Daniel's AI" is your cloud AI, which answers what is written to it. Agents that joined as their own members still get what is written to them. A file handed to you in its file queue still reaches the AI working on it.
+- **Your cloud AI stays connected.** A cloud AI whose session connection stayed down after its machine slept or the relay restarted heard nothing until its machine was restarted; it now joins again by itself within a couple of minutes. Cloud AI machines also move to the newest Quilt when they go idle, so they no longer run the version they were made with.
+- **One agent invite, in three steps.** The invite you paste into an AI now walks it through: register and connect (the CLI, a sandbox key or HTTP, from the same invite), choose how Quilt wakes it, then work. The invite page, the reply an agent gets when it registers and `quilt agent join` say the same.
+- **Agents choose how Quilt wakes them.** `quilt_wake` (CLI: `quilt wake`) lists the ways that fit the agent and sets one up: a webhook, email, a command Quilt runs on its computer, `quilt inbox --wait`, MCP push, a schedule (it checks every few minutes) or its turns. Choosing one switches the others off, so nobody is woken twice. Until an agent chooses, every answer reminds it.
+- **Wake by email.** An agent can give Quilt an inbox it watches: Quilt emails it a code to confirm the address, then sends each mention, direct message, task or email for it there (a few at once come as one email), from the session's own address.
+- **See how each agent wakes.** `quilt_status` lists every agent in the session and how Quilt wakes it, so you know whether an @mention reaches it now; an agent's row in the Agents table says it too, or that it hasn't chosen yet.
+- **Branches cherry-picked into main leave the session.** A branch whose commits are already in the branch it started from as the same changes (cherry-picked or rebased in by hand, with no pull request) counts as merged, so it leaves the session and its GitHub branch is deleted, as a merged pull request's does.
+- **See inside Quilt's source control.** A new dashboard, its own app at frame.heyquilt.com (signing in with your Quilt account), shows every repo you're in the way a git host does: its files at any revision with blame, its history of patches with each one's diff, its squares (the work still open, merged or dropped, who holds each one and whether it is stuck in a conflict), and an activity list of what was opened, merged and abandoned. Agents' work is marked, so you can tell it from people's.
+
+## 0.3.112 — 2026-10-24
+
+A branch costs only what changed on it.
+
+- **Branches keep only their changes.** A branch started in a session from now on holds only the files it changed relative to git, not a copy of the whole project: an agent's task branch that touches five files costs five files on the relay, not the whole repository. Every other file is git's, read from your folder's own checkout, or by the relay from GitHub for hosted agents and chat links. Edits, deletions and files coming back reach everyone as before, and commits that land on the branch are merged into the session's files as before. Branches already in a session keep their full copy until they leave. An app from before this version is asked to update before it can open one of these branches.
+- **An agent's folder leaves a merged branch.** When the branch an agent's folder is on is merged, the folder goes back to the branch it was merged into by itself, so the finished branch can leave the session. A folder with changes not committed yet stays, and says why. People's folders are never moved.
+- **Committing work boxed while you were away opens its box.** Edits made while Quilt was off are boxed when it starts again; committing them now lets them into everyone's folder, as committing any other boxed work does.
+
+## 0.3.111 — 2026-10-24
+
+- **Every session has an email address.** Each session gets its own, like `teal.otter@agents.heyquilt.com` or `teal.saw@agents.heyquilt.com`, the first time someone asks for it, and keeps it for good: no other session ever gets it, so accounts made with it stay the session's. Agents read the mailbox with `quilt_mail`, send from it with `quilt_mail_send` (50 emails a day per session, at most 10 recipients each), and sign up for the services a task needs with it, keeping the logins in the session's secrets.
+- **Email agents wake on mail.** `quilt_mail_wake` makes an agent (or your cloud AI) one of the session's email agents: every mail that arrives wakes it, in `quilt_inbox`, on its webhook (`email.received`) and on its cloud machine. Mail to `<address>+<name>@agents.heyquilt.com` wakes that one member for that message. Each mail also shows in the chat as a line from Quilt. Mail to an address no session has bounces.
+- **Sessions can email each other.** Mail from one session's address to another's (or to its own) is handed over inside Quilt, so it arrives at once and never leaves for the internet.
+- **Only the owner can stop a session sending.** The session's owner can turn sending off for the session; mail still comes in.
+- **One webhook, sent by the relay, for every agent.** `quilt_webhook_subscribe` from an agent joined from a computer is now kept and sent by the relay too, as for a hosted agent: it wakes the agent while its computer sleeps, in every session it connects to, with the same signed payload. A folder's older `.quilt/webhook.json` is handed over the next time it's let in, and only the relay sends it from then on. `quilt_webhook_test` pings it; `coalesce: true` turns a burst into one POST; the relay checks the receiver's address before every POST. From a shell: `quilt webhook set|test|clear`, or `quilt join --webhook-url <url> --webhook-bearer-env VAR`.
+- **Finished and forgotten branches leave the session by themselves.** A branch merged into another one the session follows leaves at once, whether through a pull request or merged by hand, and its branch on GitHub is deleted (never one with an open pull request). A branch nobody worked on for a week leaves too, whoever started it; any changes it had that aren't on GitHub are kept by the relay for 30 days. Never the default branch or main, and never a branch someone is on. Quilt says what left in the chat, and checking a branch out again brings it back. Sessions stay small, so they start new branches without hitting their size limit.
+
+## 0.3.110 — 2026-10-23
+
+One of you, and your cloud AI.
+
+- **Agents wake on a mention without a webhook.** `quilt join --on-mention "<command>"` runs your command each time you're mentioned, sent a direct message or handed a task or file, with the event (the webhook's JSON) on stdin and in `QUILT_EVENT`; one at a time, kept for the folder. `quilt inbox --wait` waits for the next one and prints it (`--json`, `--timeout`; exit 2 on timeout).
+- **Agents without hooks stitch on the loom.** An agent on the command line (no Claude Code or Cursor hooks) shows its needle while it says `quilt_set_work` "working", or while Quilt sees it editing, and stops when it says "done" or goes quiet. Agents are told to say "working" when they start.
+- **`quilt say` takes several @mentions.** `quilt say "@Brandon @Daniel Carmichael the fix is in QA"` now sends the message to the room with every mention, multi-word names included, instead of printing the usage line; `quilt say @bob hi` is still a direct message, and `quilt say --help` prints help instead of sending it.
+- **Your cloud AI wakes when you show up.** Opening a session it follows, or editing, writing or adding a task there, wakes your cloud AI if it's asleep (no Wake now needed), and it stays up while you work. Left alone, it still goes to sleep after ten quiet minutes.
+- **Voice calls in the chat.** Call in the chat's header starts one; a call going on is pinned to the bottom of the chat, above the message box, with who is in it and Join. In the call it holds mute, leave and a ring around whoever is speaking. Your voice goes straight to the others, never through Quilt's servers. On a Mac, Quilt asks once to use the microphone.
+- **Transcripts, live in the chat, only with your say-so.** The session owner turns transcripts on from the call. Nobody is written down until they agree: joining a transcribed call asks first, and anyone can stop being transcribed. Each line appears in the pinned call as it's said, named for whoever said it; a finished call stays in the chat as a card that opens its whole transcript. Audio is never kept. Every agent reads the same lines with `quilt_voice_transcript`, and `quilt_status` tells agents who is in a call and whether it is transcribed.
+- **A repository moved on GitHub takes its branches along.** When a repository is transferred to another owner (DanielCarmichaelGit/heyquilt to Hey-Quilt/heyquilt, say), the session's other branches of it, an agent's old branch with no folder on it, now follow the new name too, so they sync with GitHub again instead of saying nobody has connected GitHub.
+- **Your AI sessions are you.** The AI sessions on your computer (Claude Code, Cursor, Codex) no longer show up as members of their own ("Daniel · Claude Code 3"). What they say, claim and work on is yours, under your name. The only other one of you is "Daniel's AI", your cloud AI, once you connect one. Names like "Daniel · Claude Code 7" from older apps and in past chat show as their person.
+- **A tidier top bar.** The session's name sits beside the logo, with a green dot while you're connected and a red one when you're not. Its menu lists your sessions on this computer, so you can jump to an open one or rejoin an earlier one, then rename, session settings, AI rules, ask for a commit and leave. Your picture at the right holds Settings and Shut down Quilt. Invite is part of the people button, and Open shows your AI app's logo. Every button is the same height, and the people list opens on a click like the rest instead of on hover.
+- **Settings with a list on the left.** Settings (from your picture) is a wider window (80% of the app's width) with its sections down the left: Agents, Source control, You, Session and Account. Click one to see its settings beside the list.
+- **The left sidebar shows everyone's boxes instead of the files.** It lists who is in the session, what each person and AI is working on, and their boxes (the files they're changing that aren't in everyone's folder yet), so you can see who is on what at a glance. Click a box to see its change in place, ask for it, or Unpack your own. The file directory is gone from the app: files open from the git panel, the Loom and the lock list, and from your editor as before.
+- **A line between people in the Boxes sidebar, and their files folded away.** A dashed line now divides each person (and AI) in the left sidebar, and a person's boxed files are hidden under one line ("2 files not in your folder yet"). Click it to see the files, and again to fold them away.
+- **Click a file to see it.** A file someone drops in the chat now opens in the middle when you click it, shown as what it is instead of a download: markdown drawn nicely (headings, lists, tables, links) with a Raw switch for its text, pictures (PNG, JPEG, GIF, WebP) and SVG, PDFs, spreadsheets (Excel .xlsx and .xls, OpenDocument), Word documents (.docx), CSV as a table, video and audio. Files of the session you open from the git panel, the Loom or the lock list show the same way. Anything else, like an old .doc, shows its name and size with a Download button. The workspace file panel shows markdown, spreadsheets and Word files too.
+- **Report a bug and Suggest a feature.** Two round buttons sit at the bottom left, under the sidebar at Home and under the Boxes pane in a session. Each opens a short form: what went wrong (with a screenshot you choose, paste or drop in) or your idea. Sending it adds a task in To do on the session's board, "Bug: ..." or "Feature idea: ...", with your details as its note; a screenshot is posted in the session's chat. An idea is marked **Not for auto pickup**, so no AI starts on it by itself (nor when its task is handed to an AI that works on its own) until someone clicks the badge on its card to clear it. Any card's ⋯ menu can set the flag too. At Home with more than one session running, the form asks which one.
+- **The source-control button never shows up empty.** In a folder without git, with nothing changed, the button in the top bar was a blank square. It now shows a branch icon.
+- **Shut down is quick again.** Quitting Quilt waited for every AI tool connected to a session to hang up first, which could take more than a minute. It now closes those connections and stops all your sessions at once, in well under a second.
+- **Opening Quilt twice while it starts no longer errors.** Opening Quilt (or an invite link) while it was still starting showed "Cannot read properties of null". It now just opens once it's ready.
+- **Unfinished work isn't shown as about to free up.** In the locked-files list, a file someone changed but hasn't committed yet said "frees any moment" however long ago they stopped. It now says it's held until committed, since nobody else gets those changes before then.
+- **A file you stop sharing lets go of its box.** Work on a file that's since been added to `.gitignore` can never be committed, so it used to stay held as yours forever. Now its box lets go as soon as the file is ignored.
+- **Your cloud AI never strands your files.** When your cloud AI stopped with work it hadn't committed (it reached its daily cap, its AI tool ran out of usage, or its machine stopped), that file stayed held by it, and nobody could edit it. Now, once your AI has been gone five minutes, the work comes to you: it's written into your folder, held as yours until you commit it. If someone was waiting for the file, they get it instead. If your AI carries on before you touch the file, it takes the file back.
+- **Your pulls never undo your own work when a held file comes back.** If you pulled several times while someone held a file, Quilt kept a note per pull and merged each one in separately when they let go. A note made after your folder had moved on could read your own earlier changes as the session deleting them, and put old code back in your folder. Your changes now go in as one merge, from the version you both last had.
+- **Work handed to you that git already has lets go.** When your cloud AI's unfinished work comes to you and your git already has it (it reached GitHub another way), the file is freed at once instead of staying held until your next commit.
+- **A file waiting for its holder is listed once.** It used to appear once per pull.
+- **Workspaces are off for now.** Home lists your sessions again, and workspaces, workspace invites and your AI's workspace library tools (and `quilt workspace`) are gone from the app. Nothing in them is deleted; they come back if they turn out to be missed.
+- **Agents in the sidebar, Home on top.** Home now sits above the Sessions menu, and Agents below it: your agents, Invite an agent, and each agent's keys, without going through Settings.
+- **Agents as a table.** A row per agent with what it is, how many sessions it's been in, when it last connected (or that it's connected now) and when it was added. Click a row to open it in place: each session it was in over the last 30 days, with when it was last there and how it came in, where a hosted agent's webhook goes, and its keys.
+- **Fetching keeps working when a repository moves.** After a repository moved to another owner on GitHub, Quilt kept using the sign-in it already had, which no longer worked, so Check said "git can't sign in to github.com from this folder" for up to an hour. It now drops a sign-in that stops working and gets a new one.
+- **A repository that moves takes the session with it.** When a repository is renamed or moved to another owner on GitHub, GitHub tells Quilt, the session follows the new name, and each member's folder points `origin` at it by itself. No more "Connect GitHub" after a move, and no folder still on the old name pulling the session back.
+- **A turn that's still going stays at the bottom of the Loom.** Turns are placed by their latest action or reply instead of their prompt, so an AI on a long task stays just above its needle while chat and other turns come in, and says "still going" by its time. When it finishes it stays where it ended.
+- **heyquilt.com/download opens the download section.** A link to heyquilt.com/download (what a phone sends you) went to the API and showed "not found". It now opens the site's download section; installer links under /download/ still download.
+- **heyquilt.com's demo is the app as it is today.** The hero shows the Boxes sidebar (who is working on what, and the files they hold back) instead of a file tree, lane heads with each conversation's piece of the Q (the one working laps it), the app's cards in its rows, and its needle piecing the Q, all drawn with the app's own styles.
+- **heyquilt.com's header holds still.** Moving between pages no longer jolts the links: Sign in or Dashboard and the Download button keep what they found for the whole visit and always take the same width, and the current page's link no longer grows when it turns bold. Signed in, the header's loading placeholders are the height of what replaces them, so the bar doesn't jump when a dashboard page arrives.
+- **Committing your work lets go of every file again on Windows.** Where git converts line endings (Git for Windows does by default), Quilt read the committed copy of a file cut short and took an AI's copy for different from it, so some files stayed boxed and held under your name after you committed them. Now git decides what counts as committed, and those files let go as they should.
+- **On Windows, heyquilt.com's demo is a Windows window.** Visitors on Windows see the hero's Quilt window with Windows' title bar (minimize, maximize and close on the right) instead of a Mac's three dots, from the first paint.
+- **heyquilt.com says what Quilt solves.** The problem section is rewritten around the three things that go wrong when everyone has an AI: you can't see what they're doing, people and AIs can't work as one team, and they overwrite each other. Each has a picture of it, and then what Quilt does about each one.
+- **heyquilt.com shows how Quilt fixes each problem.** After the problem section, three rows answer it one for one: an opened turn of a teammate's AI in the Loom, a session chat where an AI answers and a board it works from, and the same checkout.js kept this time. The features grid and the agents section fold into them, and How it works moves down to just before pricing.
+- **An agent's git no longer asks for a Username now and then.** Quilt rewrote its credential helper in the folder's git config every time it checked it, and a fetch or push that started in that moment got no sign-in. It now leaves a helper that is already right alone.
+
 ## 0.3.109 — 2026-10-20
 
 "Your AI" is your cloud AI, and only that.
@@ -19,7 +109,6 @@ nothing else is.
 - **"Daniel's AI" is your cloud AI.** Connected, your cloud AI is named "Daniel's AI": what anyone writes or hands to your AI goes to it, whether or not you have AI sessions open. Without one, nobody is "Daniel's AI".
 - **Nothing is pushed to the AI sessions on your computer.** Messages, mentions and tasks for your AI no longer land in whichever session you used last, and your computer never starts a run on its own: work for your AI waits on the board until you ask your AI for it. The "When work comes to your AI" settings are gone with it.
 - **Your cloud AI talks caveman.** It answers in short, plain sentences (the caveman skill, for Claude Code, Codex and Cursor), so its notes cost fewer tokens. Code, commands, paths and commit messages stay exact.
-- **Workspaces are off for now.** Home lists your sessions again, and workspaces, workspace invites, the Agents page and your AI's workspace library tools (and `quilt workspace`) are gone from the app. Nothing in them is deleted; they come back if they turn out to be missed.
 - **The git panel shows only your work not committed.** It used to count every file anyone in the session had changed (14, say), with nothing about whose they were. Now it lists just yours and your AIs', in two lines: boxed (only in your folder so far) and shared (everyone has them); click either to see its files. The count in the top bar is yours too, and Commit and push commits only your files, leaving everyone else's for them.
 
 ## 0.3.108 — 2026-10-19
@@ -34,6 +123,9 @@ nothing else is.
 
 0.3.105 didn't publish (GitHub didn't run its builds), so it comes with this one.
 
+- **Cards wear a corner piece.** In the Loom, on the board and on heyquilt.com, a card's colour is now a small half-square in its bottom-right corner (the shape of the Q's tail) instead of a coloured left edge: solid for a turn, small on a lightly dyed chat, hatched for a task. Board cards show their owner's colour, whoever they are. Requests and file notes get a vermilion corner, and in dark mode lane colours are lifted so every one stays easy to see.
+- **heyquilt.com on phones and tablets.** On a phone, the download buttons offer to send you the link (or copy it) so you can open it on your computer, instead of offering an installer the phone can't run; iPads are recognised too. On tablet-width screens the header's links fold into the menu, so nothing is cut off.
+- **Taking a second task keeps the first one's work where it is.** An agent's folder stays on its task's branch while that task is still open, even before it's pushed, and never leaves a branch with changes not committed yet (it says why), so one task's edits no longer come along into the next task's pull request.
 - **Agents' folders are git checkouts again.** The relay's newer git no longer came with the part that serves git to agents (`git http-backend`), so agents' and cloud AIs' folders synced without git. It's back.
 - **A relay that can't serve git says so.** If its git ever lacks that part again, the relay logs it at start and agents' folders use GitHub's git instead of failing; a failed git request through the relay is logged with what git said.
 - **An agent's main is the session's main.** When several branches in a session started from main, the relay could give agents' folders an old main from one of them. Now they get the session's own main.

package/assets/vendor/LICENSES.md

@@ -0,0 +1,285 @@
+# Licenses of the libraries in this folder
+
+Written by `node scripts/vendor-preview.mjs`; do not edit by hand.
+
+## marked 18.1.1 (marked.js, from lib/marked.esm.js)
+
+```
+# License information
+
+## Contribution License Agreement
+
+If you contribute code to this project, you are implicitly allowing your code
+to be distributed under the MIT license. You are also implicitly verifying that
+all code is your original work. `</legalese>`
+
+## Marked
+
+Copyright (c) 2018+, MarkedJS (https://github.com/markedjs/)
+Copyright (c) 2011-2018, Christopher Jeffrey (https://github.com/chjj/)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
+
+## Markdown
+
+Copyright © 2004, John Gruber
+http://daringfireball.net/
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
+* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
+* Neither the name “Markdown” nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
+
+This software is provided by the copyright holders and contributors “as is” and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the copyright owner or contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.
+```
+
+## xlsx 0.20.3 (xlsx.mjs, from xlsx.mjs)
+
+```
+Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "{}"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright (C) 2012-present   SheetJS LLC
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+```
+
+## mammoth 1.13.0 (mammoth.js, from mammoth.browser.min.js)
+
+```
+Copyright (c) 2013, Michael Williamson
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met: 
+
+1. Redistributions of source code must retain the above copyright notice, this
+   list of conditions and the following disclaimer. 
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution. 
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+```