@timurproko/a1 0.1.8-dev.127 → 0.1.8-dev.132

package/README.md

@@ -6,11 +6,25 @@
 npm install --global @timurproko/a1@latest
 ```
 
+Any channel can also be installed or updated directly with npm, without the
+`a1 update` commands:
+
+```sh
+# dev channel (next tag)
+npm install -g @timurproko/a1@next
+
+# stable release
+npm install -g @timurproko/a1@latest
+
+# exact version
+npm install -g @timurproko/a1@0.1.8-dev.107
+```
+
 ## Use
 
 ```sh
 a1                      # launch A1 (profile: ~/.a1/agent)
-a1 version              # show Installed, Release, and Develop versions
+a1 version              # show Current, Develop, and Release versions
 a1 update               # install the newest stable release
 a1 update:develop       # install the current development preview
 a1 update:107           # install numbered preview 107

package/bin/module-identity.js

@@ -14,18 +14,20 @@
  * chrome silently disappears and routed input dead-ends, with no error.
  *
  * A1 therefore does not import the specifier at all. Its package declares the
- * subpath import `#pi-tui`, resolving to pinned Pi's copy first and to the
- * hoisted one only when that is absent — which is exactly the case where there
- * is one copy and both sides agree anyway. Every A1 module imports `#pi-tui`,
- * so which copy A1 uses is stated in package.json and enforced by Node at
- * resolution, rather than arranged by rewriting an installed tree.
+ * subpath import `#pi-tui`, resolving to bin/pi-tui.js — a proxy that
+ * re-exports pinned Pi's nested copy. The hop through the proxy is load-bearing:
+ * Node rejects package-imports targets containing a `node_modules` path segment
+ * (Invalid Package Target) and silently falls through to any fallback, which is
+ * exactly how an earlier alias that named the nested path directly reintroduced
+ * the split while appearing to declare the opposite. A plain import specifier
+ * inside a module carries no such restriction.
  *
- * What remains here is the check that it worked. The alias names one path
- * inside pinned Pi; if a future layout moved that copy, resolution would fall
- * back to A1's own and the split would return — silently, which is what made
- * this expensive the first time. So launch compares the two resolutions and
- * says so when they differ, loudly and once, instead of leaving a user to
- * discover it as missing extension UI.
+ * What remains here is the check that it worked. The alias is resolved by
+ * asking Node itself — never by reimplementing resolution, which is how the
+ * earlier check reported "unified" for a target Node had rejected — and the
+ * proxy hop is followed to the module it re-exports. When that disagrees with
+ * what pinned Pi resolves, launch says so, loudly and once, instead of leaving
+ * a user to discover it as missing extension UI.
  *
  * This lives in bin/ (shipped, plain JS) because it inspects dependency
  * resolution, which the Pi API boundary policy rightly forbids ordinary
@@ -39,32 +41,41 @@ import { pathToFileURL } from "node:url";
 /**
  * What A1's own modules resolve `#pi-tui` to, as a real path.
  *
- * The alias is read from the manifest and its entries tried in order, which is
- * what Node does for a subpath import: a relative target is a file within the
- * package, and a bare one goes through ordinary resolution. Asking Node
- * directly is not an option here — `import.meta.resolve` ignores the parent it
- * is given unless an experimental flag is set, so it would always answer for
- * the running process rather than for the installation being inspected.
+ * Node answers for the alias itself (require.resolve honors package imports for
+ * the package the parent belongs to). When the answer is A1's proxy file, the
+ * module it re-exports is what A1 actually renders with, so the proxy's one
+ * static `export * from` specifier is followed to its target.
  */
 function resolveOwnPiTui(packageRoot) {
-  const manifest = JSON.parse(readFileSync(join(packageRoot, "package.json"), "utf8"));
-  const alias = manifest.imports?.["#pi-tui"];
-  const targets = Array.isArray(alias) ? alias : alias === undefined ? [] : [alias];
-  if (targets.length === 0) throw new Error("package.json declares no #pi-tui alias");
-  for (const target of targets) {
-    if (typeof target !== "string") continue;
-    if (target.startsWith("./") || target.startsWith("../")) {
-      const candidate = join(packageRoot, target);
-      if (existsSync(candidate)) return canonical(candidate);
-      continue;
-    }
-    try {
-      return canonical(createRequire(pathToFileURL(join(packageRoot, "package.json")).href).resolve(target));
-    } catch {
-      continue;
-    }
+  const requireFromRoot = createRequire(pathToFileURL(join(packageRoot, "package.json")).href);
+  let resolved;
+  try {
+    resolved = requireFromRoot.resolve("#pi-tui");
+  } catch (error) {
+    throw new Error(`#pi-tui does not resolve: ${message(error)}`);
+  }
+  return canonical(followProxyReExport(resolved));
+}
+
+/**
+ * Follow A1's proxy hop: one relative `export * from "..."` per file, at most
+ * one hop. A resolution that is not the proxy (or any file without such a
+ * re-export) is returned as-is.
+ */
+function followProxyReExport(resolvedPath) {
+  let source;
+  try {
+    source = readFileSync(resolvedPath, "utf8");
+  } catch {
+    return resolvedPath;
+  }
+  const reExport = source.match(/^export \* from "(\.\.?\/[^"]+)";?$/m);
+  if (!reExport) return resolvedPath;
+  const target = join(dirname(resolvedPath), reExport[1]);
+  if (!existsSync(target)) {
+    throw new Error(`#pi-tui proxy ${resolvedPath} re-exports a missing file: ${target}`);
   }
-  throw new Error(`no #pi-tui target resolves: ${targets.join(", ")}`);
+  return target;
 }
 
 /**

package/bin/pi-tui.d.ts

@@ -0,0 +1,6 @@
+/**
+ * Types for the `#pi-tui` proxy (see ./pi-tui.js): the alias resolves to that
+ * file, so TypeScript reads this declaration and follows it to pinned Pi's
+ * nested pi-tui copy — the same module the proxy re-exports at runtime.
+ */
+export * from "../node_modules/@earendil-works/pi-coding-agent/node_modules/@earendil-works/pi-tui/dist/index.js";

package/bin/pi-tui.js

@@ -0,0 +1,24 @@
+/**
+ * The one pi-tui module A1 uses: pinned Pi's own copy.
+ *
+ * A1's `#pi-tui` alias resolves here, and this file re-exports the copy nested
+ * inside pinned Pi — the same one Pi's extension loader hands to extensions, so
+ * prototype patches and `instanceof` checks land on the classes A1 renders with.
+ *
+ * The alias cannot name that copy directly: Node rejects any package-imports
+ * target containing a `node_modules` path segment (Invalid Package Target) and
+ * silently falls through to the next entry, which resolves the hoisted root
+ * copy and reintroduces the two-identity split this file exists to prevent. A
+ * plain import specifier in a module carries no such restriction, so the hop
+ * through this file is what makes the nested copy nameable from the manifest.
+ *
+ * When the nested copy is missing (a layout pinned Pi's shrinkwrap does not
+ * produce), this import fails loudly at launch instead of silently rendering
+ * without extension chrome. bin/module-identity.js reports the same condition
+ * before the composition loads.
+ *
+ * This lives in bin/ (shipped, plain JS) because it names a path inside
+ * node_modules, which the Pi API boundary policy rightly forbids ordinary
+ * production code from doing.
+ */
+export * from "../node_modules/@earendil-works/pi-coding-agent/node_modules/@earendil-works/pi-tui/dist/index.js";

package/dist/cli/version-stats.js

@@ -21,7 +21,7 @@ export async function runVersionStats(options) {
         return 1;
     }
     const remote = await queryDistTags(runner);
-    output.stdout(`Installed: ${installed}\nRelease:   ${remote.release ?? "unavailable"}\nDevelop:   ${remote.develop ?? "unavailable"}\n`);
+    output.stdout(`Current: ${installed}\nDevelop: ${remote.develop ?? "unavailable"}\nRelease: ${remote.release ?? "unavailable"}\n`);
     if (remote.error)
         output.stderr(`${PRODUCT_TEXT.diagnostic(`could not resolve npm dist-tags: ${remote.error}`)}\n`);
     return 0;
@@ -37,7 +37,9 @@ async function queryDistTags(runner) {
     if (result.code !== 0)
         return unavailable(`npm exited with status ${result.code ?? "unknown"}`);
     try {
-        const metadata = JSON.parse(result.stdout);
+        const parsed = JSON.parse(result.stdout);
+        // npm 12 wraps `npm view <pkg> dist-tags --json` output in a one-element array; older npm returns the bare object.
+        const metadata = Array.isArray(parsed) && parsed.length === 1 ? parsed[0] : parsed;
         if (typeof metadata !== "object" || metadata === null || Array.isArray(metadata))
             throw new TypeError("npm returned a non-object dist-tags value");
         const tags = metadata;

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

@@ -5,7 +5,7 @@
   "platform": "darwin",
   "architecture": "arm64",
   "capability": "unsupported",
-  "builtAt": "2026-08-25T16:32:02.507Z",
+  "builtAt": "2026-08-25T17:36:44.842Z",
   "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-25T16:32:02.752Z",
+  "builtAt": "2026-08-25T17:37:08.874Z",
   "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-25T16:33:25.671Z",
+  "builtAt": "2026-08-25T17:37:16.993Z",
   "artifact": {
     "filename": "process-guardian.exe",
-    "sha256": "eeceadd71235bbb8b39caec42a55216b6b48f3822b8cc9ac94fe4932d74bb5de",
+    "sha256": "b9edc03a251b1c0e851ff55227385f016241fc4f33aa0f5ee5f0415443d6a927",
     "size": 172544
   },
   "provenance": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@timurproko/a1",
-  "version": "0.1.8-dev.127",
+  "version": "0.1.8-dev.132",
   "description": "Standalone terminal workspace for supervised native and managed agents",
   "type": "module",
   "packageManager": "npm@11.13.0",
@@ -8,10 +8,7 @@
     "a1": "bin/cli.js"
   },
   "imports": {
-    "#pi-tui": [
-      "./node_modules/@earendil-works/pi-coding-agent/node_modules/@earendil-works/pi-tui/dist/index.js",
-      "@earendil-works/pi-tui"
-    ]
+    "#pi-tui": "./bin/pi-tui.js"
   },
   "files": [
     "bin",