@loompad/cli 0.1.0 → 1.1.1

package/docs/release-notes/v1.1.0.md

@@ -0,0 +1,71 @@
+## Loom 1.1.0: can you trust what your agents did?
+
+Agents say "all tests pass" when three of fourteen ran. They hit the same red
+test eight times while you're away. They force-push. 1.1 is about the gap
+between what an agent says it did and what it did, and about leaving your
+agents to work when you're not watching.
+
+### Proof: is "done" true?
+
+When a reply claims the tests, build, typecheck or lint pass, Loom checks the
+claim three ways:
+- what the reply said, numbers included;
+- what the turn actually ran, and the exit codes;
+- a **clean re-run** of your tests in a fresh worktree holding exactly the
+  agent's uncommitted changes. Your working tree is never touched.
+
+The thread gets a card: **Verified**, **Didn't hold** (with why: "said 14
+pass; 11 did"), or **Unverified**. A "done" that didn't hold pushes to your
+phone. Every turn card has **Check it**, and `loom proof` works from a
+terminal.
+
+### Night Shift: run the list while you sleep
+
+Type the tasks one per line, then choose **⋯ → Night shift** (🌙 on the phone,
+or `loom shift`). They run one after another, a chat each:
+- Proof checks every "done".
+- An agent going in circles is nudged.
+- A command that can't be taken back stops the turn.
+- An agent out of quota hands its work on.
+- A question stays open in its chat, and the next task goes.
+
+The shift stops starting new tasks at your stop-by time or budget. In the
+morning, one report says how each task went: verified, done, didn't hold,
+failed, needs you, or not started.
+
+### Watching the agents for you
+
+- **Loop watch**: the same command failing three times gets a card (Stop,
+  Nudge it, Hand it off) and a push.
+- **Blast-Radius Shield**: a force-push, `reset --hard`, an `rm -rf` outside
+  the project, `DROP TABLE`, `terraform destroy`, `npm publish`, `sudo` or
+  `curl | sh` is named the moment it runs, and it can stop the turn.
+- **Quota Relay**: hit Claude's 5-hour window mid-task and the work moves to
+  your next agent with a briefing, then comes back when the window resets.
+- **Review Triage**: every turn card says which files to read first, and why.
+- **Scorecards**: how often each agent's "done" held up, its circles and
+  shield trips, and what a verified result costs from it (`loom scorecard`).
+- **Pre-flight forecast**: what a turn usually costs and takes, before you
+  send it.
+- **Replay**: any chat as one self-contained HTML page you can send anyone
+  (`loom replay`).
+- **Design Mode**: a picked element brings its styles and its own picture.
+
+### Agent Teams, Windows, and a lighter daemon
+
+Crews now have persistent teammates with their own memory, parallel builders,
+races, and coordination across teammates' daemons and runners. Windows gets
+Job Object containment and native continuity. The daemon starts lighter and
+no longer leaks memory over long sessions.
+
+The full list is in [CHANGELOG.md](https://github.com/nickthelegend/loom/blob/main/CHANGELOG.md).
+
+### Install
+
+- **macOS**: download the `arm64` (Apple silicon) or `x64` dmg below. The app
+  is ad-hoc signed, so the first time, right-click it, choose Open, then Open.
+  Or use Homebrew: `brew tap nickthelegend/loom https://github.com/nickthelegend/loom && brew install --cask loom-desktop`.
+- **Windows / Linux**: the installer for your platform below.
+- **Android**: `loompad-1.1.0-android.apk` below installs over earlier versions.
+- **CLI**: `npm install -g github:nickthelegend/loom#v1.1.0`, then
+  `loom up --restart`.

package/docs/release-notes/v1.1.1.md

@@ -0,0 +1,38 @@
+## Loom 1.1.1: a smooth first launch
+
+Fixes found installing 1.1.0 on a Mac whose projects live on an external drive.
+
+**Loom Desktop explains a slow start.** The first time Loom reads projects on
+an external drive (or in Documents or Desktop), macOS asks whether Loom
+Desktop may access those files, and Loom's background service waits for the
+answer. 1.1.0 sat on a blank window meanwhile. 1.1.1 says *Starting Loom…*
+straight away, and after a few seconds that macOS may be asking, and to
+choose **Allow**.
+
+**No second background service.** While the first one was waiting on that
+prompt, 1.1.0 tried to start another onto the same port. 1.1.1 waits for the
+first one instead.
+
+**An installed app's error page.** If the service can't be reached, the page
+now says to quit and reopen, where the permission lives in System Settings
+(Privacy & Security → Files and Folders), and where the log is. It no longer
+says "run npm run build". The pairing request also times out instead of
+hanging.
+
+**One build, one fingerprint.** Builds now remove compiled files whose source
+is gone. Leftovers in an old checkout made the same release look like two
+different builds to the desktop app and the CLI, and each would restart the
+other's background service.
+
+Everything new in 1.1 (Proof, Night Shift, Loop watch, Blast-Radius Shield,
+Quota Relay, Review Triage, Scorecards, Replay, and more) is in the
+[1.1.0 notes](https://github.com/nickthelegend/loom/releases/tag/v1.1.0).
+
+### Install
+
+- **macOS**: the `arm64` (Apple silicon) or `x64` dmg below. The app is
+  ad-hoc signed, so the first time, right-click it, choose Open, then Open.
+  Or use Homebrew: `brew upgrade --cask loom-desktop`.
+- **Windows / Linux**: the installer for your platform below.
+- **Android**: `loompad-1.1.1-android.apk` below installs over earlier versions.
+- **CLI**: `npm install -g @loompad/cli`, then `loom up --restart`.