@timurproko/a1 0.1.8-dev.121 → 0.1.8-dev.126

package/README.md

@@ -6,117 +6,95 @@
 npm install --global @timurproko/a1@latest
 ```
 
-## Commands
+## Use
 
 ```sh
-a1                      # A1-owned UI and profile: ~/.a1/agent
+a1                      # launch A1 (profile: ~/.a1/agent)
 a1 version              # show Installed, Release, and Develop versions
-a1 update               # update to the current release
-a1 update:develop       # update to the current development preview
-a1 update:107           # install numbered development preview 107
+a1 update               # install the newest stable release
+a1 update:develop       # install the current development preview
+a1 update:107           # install numbered preview 107
 a1 update --models      # refresh A1's model catalogs
 ```
 
-Prerelease builds — what `a1 update:develop` installs — add two development profiles
-for comparing against pinned Pi and for experimenting against an isolated profile.
-A release build does not carry them.
+Development previews add two extra profiles; release builds do not carry them.
 
 ```sh
-a1 pi           # untouched vanilla Pi oracle: ~/.pi/agent
-a1 sandbox      # unchanged isolated vanilla Pi profile: ~/.a1/sandbox
+a1 pi           # vanilla Pi oracle: ~/.pi/agent
+a1 sandbox      # isolated vanilla Pi profile: ~/.a1/sandbox
 ```
 
 ## Extensions
 
-Pi extension packages install into A1's own profile, so bare `a1` loads them and
-`a1 pi` and `a1 sandbox` do not. Sources are Pi's: `npm:`, git, or a local path.
+Pi extension packages install into A1's own profile (`~/.a1/agent`), so bare `a1`
+loads them and `a1 pi` / `a1 sandbox` do not. Sources are Pi's: `npm:`, git, or a
+local path.
 
 ```sh
-a1 pi install npm:pi-mcp-adapter   # install a package into ~/.a1/agent
-a1 pi remove npm:pi-mcp-adapter    # remove it again (alias: a1 pi uninstall)
-a1 pi list                         # list packages installed for a1
+a1 pi install npm:pi-mcp-adapter   # install a package
+a1 pi remove npm:pi-mcp-adapter    # remove it (alias: a1 pi uninstall)
+a1 pi list                         # list installed packages
 a1 pi update --extensions          # update every installed package
-a1 pi update npm:pi-mcp-adapter    # update one of them
+a1 pi update npm:pi-mcp-adapter    # update one
 ```
 
-A running session loads a newly installed package after a restart. Pi's own
-profile at `~/.pi/agent` is managed by Pi itself. Extension configuration is
-isolated too: for example, MCP configuration for bare `a1` belongs under
-`~/.a1/agent` (or the project), so `~/.pi/agent/mcp.json` is not read. Run
-`/mcp setup` inside bare `a1` to configure it; the MCP footer status appears
-when that A1 configuration contains a server.
+A running session picks up a newly installed package after a restart.
+Configuration is isolated the same way: bare `a1` reads `~/.a1/agent` (or the
+project), never `~/.pi/agent`. Configure MCP with `/mcp setup` inside bare `a1`.
 
 ## Develop
 
 ```sh
 npm ci                  # install exact locked dependencies
 npm run build           # compile TypeScript and the process guardian into dist
-npm start               # build and launch an isolated development `a1`
-npm run start:pi        # build and launch an isolated development `a1 pi`
-npm run start:sandbox   # build and launch an isolated development `a1 sandbox`
-npm run test:fast       # typecheck + fast suite, no build needed
-npm test                # same as test:fast
+npm start               # build and launch a development `a1`
+npm run start:pi        # build and launch a development `a1 pi`
+npm run start:sandbox   # build and launch a development `a1 sandbox`
+npm run test:fast       # typecheck + fast suite (alias: npm test)
 npm run test:full       # complete non-physical suite
 ```
 
 ## Release
 
-Two channels, both published by CI from the exact bytes it validated. Nothing is
-ever published from a workstation.
+Two channels, both published by CI from the exact bytes it validated — never from
+a workstation.
 
 ### Development previews
 
-Ordinary pushes to `develop` do not publish. The nightly run at `03:17 UTC` always
-performs complete verification of current `origin/develop`; it publishes only when
-that source's preview is absent. A maintainer can request the same authoritative
-GitHub Actions path and wait for its result:
+A preview is `<major.minor.patch>-dev.<pull-request number>`, e.g. `0.1.8-dev.107`.
+The nightly run (`03:17 UTC`) verifies current `origin/develop` and publishes only
+when that source's preview is absent. `npm run develop` requests the same GitHub
+Actions run and waits for it. The published version list is authoritative: an
+unpublished number is refused.
 
-```sh
-npm run develop
-```
-
-A preview is `<major.minor.patch>-dev.<pull-request number>`, stamped only into the
-package. For example, the source GitHub presents as `develop (#107)` produces
-`0.1.8-dev.107`. Repeating a request for immutable version 107 succeeds without
-building or publishing again.
+Publish:
 
 ```sh
-a1 update:develop       # install the current development preview
-a1 update:107           # install preview 107
-a1 update:0.1.8-dev.107 # install that exact full preview version
+npm run develop             # request the preview publish run and wait for it
 ```
 
-The published version list is authoritative: an unpublished number is refused
-rather than guessed. npm's `next` dist-tag remains an internal registry detail.
-
-### Stable — npm `latest`
-
-One command, from a clean `develop` that matches its remote:
+Install:
 
 ```sh
-npm run release -- patch     # 0.1.1        -> 0.1.2
-npm run release -- minor     # 0.1.1        -> 0.2.0
-npm run release -- major     # 0.1.1        -> 1.0.0
-npm run release -- 0.4.0     # an exact version
+a1 update:107               # install preview 107
+a1 update:0.1.8-dev.107     # install that exact full preview version
 ```
 
-It lands the version on `develop` through a pull request that merges itself, then
-explicitly dispatches publication for that exact commit. GitHub Actions builds,
-validates the packed release on Windows, Linux, and macOS, publishes to npm
-`latest` with provenance, and only then writes the `v<version>` tag and records the
-GitHub Release. The command waits for success before opening the next `-dev` line.
+### Stable
 
 ```sh
-a1 update        # install the newest stable release
+npm run release -- patch     # 0.1.1 -> 0.1.2
+npm run release -- minor     # 0.1.1 -> 0.2.0
+npm run release -- major     # 0.1.1 -> 1.0.0
+npm run release -- 0.4.0     # an exact version
 ```
 
-After a stable publish, `master` fast-forwards to the released commit, so `master`
-always points at what npm `latest` serves while `develop` carries the work.
-
-A release that fails leaves nothing behind: no tag, no GitHub Release, no moved
-branch. Every version you can see somewhere is a version the registry actually
-serves. Release tags are protected from deletion and movement; a wrong tag is
-superseded by the next version, never repointed.
+The command lands the version on `develop` through a self-merging pull request,
+dispatches publication for that exact commit, and waits for success. CI validates
+the packed release on Windows, Linux, and macOS, publishes to npm `latest` with
+provenance, then writes the `v<version>` tag and the GitHub Release. `master`
+fast-forwards to the released commit, so it always points at what npm `latest`
+serves. A failed release leaves nothing behind: no tag, no GitHub Release, no
+moved branch.
 
-`docs/ci-release-runbook.md` has the full picture, including what happens when a
-publish fails partway.
+`docs/ci-release-runbook.md` has the full picture.

package/dist/foundation/release/update.js

@@ -14,13 +14,6 @@ import { materializeRelease, readMaterializedRelease } from "./release-store.js"
 import { UpdateTransactionStore } from "./update-transaction.js";
 export const PRODUCT_PACKAGE = PRODUCT_TEXT.packageName;
 const UPDATE_DIST_TAGS = { stable: "latest", next: "next" };
-/**
- * What each channel is called when A1 says it out loud. The internal name stays
- * `stable` because that is what the channel is, but what a reader is moving to is
- * a release, and that is the word the repository, its tags, and its GitHub
- * releases all use.
- */
-const UPDATE_CHANNEL_LABELS = { stable: "release", next: "develop" };
 const defaultFileSystem = {
     async readFile(path) { return await readFile(path, "utf8"); },
     realpath,
@@ -103,13 +96,10 @@ export function createUpdateLifecycleCoordinator(environment = process.env, file
                 await removeEndpointArtifacts(owner.paths.endpointMetadataPath, owner.paths.endpoint);
                 return { priorActiveVersion };
             }
-            if (plan === "leave-running") {
-                const running = endpoint.ownership.liveInstanceIds.length;
-                if (running > 0) {
-                    output.stdout(`${PRODUCT_TEXT.commandName} update: leaving ${running === 1 ? "one session" : `${running} sessions`} running on ${endpoint.releaseId}\n`);
-                }
+            // Leaving sessions alone is the expected outcome, and saying so mid-update tears
+            // the progress bar; only ending a session (below) is worth interrupting it for.
+            if (plan === "leave-running")
                 return { priorActiveVersion };
-            }
             // Say whose work is ending before it ends.
             const live = endpoint.ownership.liveInstanceIds.length;
             if (live > 0) {
@@ -348,7 +338,7 @@ export async function runSelfUpdate(options) {
     const targetVersion = resolved.version;
     // No full stop after a version: it already ends in a dot-separated identifier,
     // and a trailing one reads as part of the version rather than as punctuation.
-    output.stdout(`${PRODUCT_TEXT.commandName} update (${UPDATE_CHANNEL_LABELS[channel]}): ${runningVersion} → ${targetVersion}\n`);
+    output.stdout(`${PRODUCT_TEXT.commandName} update: ${runningVersion} → ${targetVersion}\n`);
     const progress = createUpdateProgress(output, options.progress ?? (options.output === undefined && process.stdout.isTTY === true));
     const rootLookup = await measure("global-root", async () => await runNpm(runner, ["root", "--global"], true, output, "resolve npm's global package root"));
     if (rootLookup.result === null)

package/dist/native/darwin-arm64/manifest.json

@@ -5,7 +5,7 @@
   "platform": "darwin",
   "architecture": "arm64",
   "capability": "unsupported",
-  "builtAt": "2026-08-25T14:20:04.982Z",
+  "builtAt": "2026-08-25T16:05:21.345Z",
   "artifact": {
     "filename": "process-guardian",
     "sha256": "7524bf568992517f50ed53196c861c5edeba0d7275633bb4735ab45bd5963a28",

package/dist/native/linux-x64/manifest.json

@@ -5,7 +5,7 @@
   "platform": "linux",
   "architecture": "x64",
   "capability": "supported",
-  "builtAt": "2026-08-25T14:20:15.954Z",
+  "builtAt": "2026-08-25T16:05:37.568Z",
   "artifact": {
     "filename": "process-guardian",
     "sha256": "29e22fe29de2828982bc67ef418c4adcaab1490281477b7bea592ec6fe621bcd",

package/dist/native/win32-x64/manifest.json

@@ -5,10 +5,10 @@
   "platform": "win32",
   "architecture": "x64",
   "capability": "supported",
-  "builtAt": "2026-08-25T14:20:44.310Z",
+  "builtAt": "2026-08-25T16:06:01.104Z",
   "artifact": {
     "filename": "process-guardian.exe",
-    "sha256": "2505aec15562e251023ec6aca4b1946536cf2ab44e4139da6066b2aa03d4dd92",
+    "sha256": "b6d74c0b5b0a9977001c9e9bf175ccda5676da8668575a092d621a12ccda74b6",
     "size": 172544
   },
   "provenance": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@timurproko/a1",
-  "version": "0.1.8-dev.121",
+  "version": "0.1.8-dev.126",
   "description": "Standalone terminal workspace for supervised native and managed agents",
   "type": "module",
   "packageManager": "npm@11.13.0",