@timurproko/a1 0.1.1-dev.8 → 0.1.1-dev.9

package/README.md

@@ -4,19 +4,12 @@ A1 is a terminal-native agent launcher for Windows, Linux, and macOS. Bare `a1`
 
 ## Install
 
-Requirements:
-
-- Node.js 22.19 through 24.x
-- npm 11
-
-Published packages include the integrity-verified process guardian for supported platforms. Building A1 from source additionally requires Rust/Cargo 1.85 or newer.
+Requires Node.js 22.19 through 24.x and npm 11.
 
 ```sh
 npm install --global @timurproko/a1@latest
 ```
 
-The package installs only the `a1` command.
-
 ## Commands
 
 ```sh
@@ -28,79 +21,23 @@ a1 update       # update to npm latest
 a1 update:next  # update to npm next
 ```
 
-Bare `a1` owns its Pi-compatible TUI composition and uses the public Pi engine, components, and terminal APIs. It does not insert a PTY or terminal-byte relay. Default visuals and workflows track the pinned vanilla Pi baseline; A1-specific visual customization and structured tabs remain disabled.
-
-`a1 pi` is the untouched upstream fallback and comparison oracle. Use it to distinguish A1-owned UI problems from upstream Pi, profile, provider, or terminal problems. The `a1 ui` subcommand was removed and is not a compatibility alias; run bare `a1` for the owned UI.
+The `a1 ui` subcommand was removed; run bare `a1` for the owned UI.
 
-`a1 sandbox` is unchanged: it launches vanilla Pi with isolated Pi configuration and resources. “Sandbox” does not mean operating-system, filesystem, process, network, or credential security isolation. See [`docs/features/launch-profiles.md`](docs/features/launch-profiles.md) for first-run directories, independent `/login`, trust behavior, extension placement, and recovery.
-
-Every interactive command creates an independent, non-detachable launch instance. Any number of `a1`, `a1 pi`, and `a1 sandbox` commands may run in separate terminals at the same time. Closing one command closes only its owned UI/Pi process and all agents, extensions, tools, daemons, and descendants created by that invocation; it never requires finding PIDs, deleting control state, or restarting the supervisor. The idle supervisor may remain available for release coordination after all interactive instances close, but it owns no surviving instance runtime.
+Any number of `a1`, `a1 pi`, and `a1 sandbox` commands may run in separate terminals at the same time. Closing one command closes only its own UI/Pi process and everything it spawned.
 
 ## Develop
 
 ```sh
-npm ci
-npm run build
-npm start
-```
-
-`npm start` gives each invocation isolated A1 development state and an isolated development Pi profile. Use `npm start -- --print-environment` to inspect the selected paths without launching the UI.
-
-A1 control state uses `%APPDATA%\\A1` and `%LOCALAPPDATA%\\A1` on Windows, and the `a1` directory under XDG config/data/runtime roots on Unix. Override it only with declared `A1_*` variables such as `A1_CONFIG_DIR`, `A1_DATA_DIR`, `A1_RUNTIME_DIR`, `A1_DATABASE_PATH`, and `A1_ENDPOINT`. Pi profile roots remain `~/.a1/agent`, `~/.pi/agent`, and `~/.a1/sandbox`. This is a no-migration identity hard cut; see [`docs/architecture/toolchain.md`](docs/architecture/toolchain.md#identity-hard-cut-and-cleanup) before removing obsolete control state.
-
-### Worktree lifecycle
-
-The primary worktree stays on `develop` and is integration-only. Each task uses a detached worktree under the repository's ignored `.worktrees/` directory, based on current `origin/develop` unless another base is selected.
-
-```sh
-git fetch origin --prune
-git worktree add --detach .worktrees/<task-id> origin/develop
-cd .worktrees/<task-id>
+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 instance
+npm run test:fast   # typecheck + fast suite, no build needed
+npm test            # same as test:fast
+npm run test:full   # complete non-physical suite
 ```
 
-Commit and validate coherent work there. Because `develop` is protected, push the detached commit to one temporary remote branch and merge one pull request for the requested change. After merge, update the primary worktree and remove the task worktree only when its commits are reachable from `develop`:
+## Release
 
 ```sh
-git push origin HEAD:refs/heads/<task-id>
-gh pr create --base develop --head <task-id>
-# After the pull request is merged:
-cd <repository-root>
-git fetch origin --prune
-git merge --ff-only origin/develop
-git worktree remove .worktrees/<task-id>
-git worktree prune
+npm run release:next   # publish current develop tip to npm next via trusted CI workflows
 ```
-
-Manual acceptance does not leave a permanent validation checkout. Once acceptance is recorded, archive the completed OpenSpec change, integrate the archive commit into `develop`, then remove and prune every task or acceptance worktree retained for that change. Never remove a worktree before all of its implementation, acceptance, and archive commits are reachable from `develop`.
-
-Local package archives and ad hoc test builds belong under `.builds/`, never in the repository root. For manual package tests, use:
-
-```sh
-mkdir -p .builds
-npm pack --ignore-scripts --pack-destination .builds
-```
-
-Run the non-desktop gates with:
-
-```sh
-npm run typecheck
-npm run check:architecture
-npm run check:deprecated
-npm test
-npm run test:release
-```
-
-Automated physical-terminal interaction must never run on an active workstation. Future physical certification may run only on dedicated disposable workers or VMs with exclusive test desktops.
-
-## Releases
-
-An exact manually accepted `-dev.N` candidate may publish under npm tag `next` after applicable non-desktop gates pass. Such a preview is explicitly uncertified, cannot move `latest`, and cannot claim stable terminal parity or platform support. Stable claims require deferred physical and cross-platform certification against the exact package.
-
-Trusted preview publication uses `.github/workflows/publish-next.yml` and npm provenance. Local release mechanics are documented in [`docs/architecture/toolchain.md`](docs/architecture/toolchain.md).
-
-## Architecture
-
-- [`docs/architecture/boundaries.md`](docs/architecture/boundaries.md)
-- [`docs/architecture/toolchain.md`](docs/architecture/toolchain.md)
-- [`docs/manual-transparent-checkpoint.md`](docs/manual-transparent-checkpoint.md)
-- [`docs/features/launch-profiles.md`](docs/features/launch-profiles.md)

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

@@ -5,7 +5,7 @@
   "platform": "darwin",
   "architecture": "arm64",
   "capability": "unsupported",
-  "builtAt": "2026-08-22T17:52:01.473Z",
+  "builtAt": "2026-08-23T08:07:45.115Z",
   "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-22T17:52:01.995Z",
+  "builtAt": "2026-08-23T08:07:37.399Z",
   "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-22T17:52:47.054Z",
+  "builtAt": "2026-08-23T08:08:17.265Z",
   "artifact": {
     "filename": "process-guardian.exe",
-    "sha256": "ed14b51aeb577ecd86df4a8a9ca3ea33c27885da8d3d196b26b0d705d70a0b71",
+    "sha256": "a803cf8cc8bb6143d2adb7378183d4366a6bb880e110786ebeb7e778b64b6c59",
     "size": 172544
   },
   "provenance": {

package/docs/architecture/toolchain.md

@@ -73,7 +73,7 @@ Presentation acceptance is the reader comparing `a1 pi` with pinned Pi. `node sc
 
 A preview candidate must use a unique `-dev.N` version and exact manually accepted bytes. Publication packs once, binds evidence to source commit/version/integrity, runs applicable non-desktop gates, publishes under npm `next`, and verifies registry identity. It must keep `latest` unchanged and record physical/cross-platform certification as deferred.
 
-The GitHub trusted-publishing workflow is `.github/workflows/publish-next.yml`. Stable publication remains a separate release process from a clean tagged `master` commit after all mandatory platform gates pass.
+The GitHub trusted-publishing workflow is `.github/workflows/npm-publish.yml`. Stable publication remains a separate release process from a clean tagged `master` commit after all mandatory platform gates pass.
 
 ## A1 state paths
 

package/docs/ci-release-runbook.md

@@ -22,10 +22,18 @@ Need more coverage for a risky preview? Dispatch the candidate with `full: true`
 
 ## Publish a preview to npm `next`
 
+One command from a clean `develop` checkout runs the whole chain — candidate build, publish, registry verification:
+
+```sh
+npm run release:next
+```
+
+It dispatches the same trusted workflows below and never publishes local bytes. The manual steps remain the reference path:
+
 1. Make sure `Development validation required` is green on the `develop` tip.
 2. Dispatch **Build npm next candidate** with the exact commit and `confirm_candidate=build-uncertified-next-candidate`.
 3. Check the resulting `candidate-evidence.json`: gates passed, package integrity matches.
-4. Approve the `npm-next` environment and dispatch **Publish npm next** with the candidate run id.
+4. Approve the `npm-publish` environment and dispatch **Publish npm next** with the candidate run id.
 
 The publisher uploads the exact validated tarball — it never rebuilds. Candidates expire after 14 days; an expired or mismatched artifact means building a new candidate, not patching the old one.
 
@@ -35,7 +43,7 @@ The publisher uploads the exact validated tarball — it never rebuilds. Candida
 2. Dispatch **Build stable candidate** — it packs once and validates the same bytes on all three platforms.
 3. Dispatch **Certify stable physical platforms** on the dedicated isolated workers (they set `PHYSICAL_WORKER_ISOLATED=true` and run under the `stable-physical` environment). Never run physical host probes on a developer workstation.
 4. Dispatch **Certify stable candidate** with both run ids. `Stable candidate required` passes only when every verdict binds the same commit, version, and digest.
-5. Merge that exact commit to `master`, tag it `v<version>`, and dispatch **Publish npm stable**, then approve `npm-stable`.
+5. Merge that exact commit to `master`, tag it `v<version>`, and dispatch **Publish npm stable**, then approve `npm-publish`.
 
 Stable artifacts expire after 30 days. The same rule as previews applies: publication still requires exact certified bytes. Never upload locally rebuilt bytes, and never route around certification by rebuilding inside a publisher.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@timurproko/a1",
-  "version": "0.1.1-dev.8",
+  "version": "0.1.1-dev.9",
   "description": "Standalone terminal workspace for supervised native and managed agents",
   "type": "module",
   "packageManager": "npm@11.13.0",
@@ -21,13 +21,14 @@
     "clean": "node scripts/clean.mjs",
     "build": "npm run clean && tsc -p tsconfig.build.json && node scripts/build-process-guardian.mjs",
     "build:process-guardian": "node scripts/build-process-guardian.mjs",
-    "typecheck": "tsc -p tsconfig.json --noEmit",
+    "typecheck": "tsgo -p tsconfig.json --noEmit",
     "check:architecture": "node scripts/check-architecture.mjs && node scripts/product-identifier-policy.mjs --check && node scripts/check-product-identity-boundaries.mjs && node scripts/check-package-identity.mjs && node scripts/check-pinned-pi-source-ledger.mjs && node scripts/check-terminal-host-provenance.mjs",
     "check:customization-ready": "node scripts/check-owned-ui-customization-prerequisites.mjs",
     "check:deprecated": "node scripts/check-deprecated-dependencies.mjs",
     "branches:prune": "node scripts/prune-merged-branches.mjs",
     "check": "npm run test:fast",
     "publish:next": "tsx scripts/publish-next.ts",
+    "release:next": "node scripts/release-next.mjs",
     "test": "npm run test:fast",
     "test:fast": "node scripts/run-validation-tier.mjs typecheck fast",
     "test:scope": "node scripts/run-validation-tier.mjs",
@@ -59,6 +60,7 @@
     "@types/cross-spawn": "6.0.6",
     "@types/node": "24.2.1",
     "@types/semver": "7.8.0",
+    "@typescript/native-preview": "7.0.0-dev.20260707.2",
     "@xterm/headless": "6.0.0",
     "node-pty": "1.1.0",
     "tsx": "4.20.3",