@zerotal/arch 1.8.0 → 1.8.1

package/docs/changelog.md

@@ -27,9 +27,42 @@ the section for every version you cross and apply its migration notes, not only
 majors. [Releases and versioning](/docs/support-policy#releases-and-versioning) explains
 when that carve-out ends.
 
+## 1.8.1 — 2026-08-26
+
+DevTools showed you the wrong request, accurately.
+
+### Fixed
+
+- **A page keeps the DevTools panel while its own assets load.** Opening `/login` selected
+  `/login`, then `/favicon.ico` a few milliseconds later, then `/css/app.css`. Live mode
+  selected every trace as it arrived and a page's sub-resources arrive right behind it, so the
+  bar named a request nobody asked about, the detail below described that request's headers
+  and its empty session, and the page you were inspecting had scrolled into the list. Nothing
+  shown was wrong; it was all about the wrong request.
+
+  Traces are now classified into three kinds rather than two, because "not the document" would
+  have suppressed the form post and the Inertia visit — the requests most worth watching. What
+  gets skipped over is narrower: a sub-resource the browser fetched on its own initiative. The
+  browser is asked rather than the URL, since an app may serve an API from a `.js` route and a
+  build that hashes its asset names has no extension to read; what was actually served is the
+  fallback, so a page fetched by `curl` still reads as a page. Anything unclassifiable counts
+  as app traffic, never as an asset — being wrong there decides whether a request is skipped,
+  and skipping the wrong one is how the panel stops showing what you came to see.
+
+  An asset still takes the selection when nothing else has it, so a panel opened mid-load
+  shows a request rather than an empty pane. A paused panel still counts assets toward its
+  pending badge.
+
+### Added
+
+- **A `kind` facet on the DevTools All tab**, beside method and status. Assets were never the
+  problem, only their claim on the selection, so they are not hidden: pick `page` and `api`
+  for a list without fifty stylesheet fetches in it, or `asset` alone for what the browser
+  pulled in, what it cost and which of it 404'd — which was not visible anywhere before.
+
 ## 1.8.0 — 2026-08-24
 
-The first render mode, the codemod runner 2.0 depends on, and four failures that
+The first render mode, the codemod runner 2.0 depends on, and five failures that
 each looked like something other than what they were.
 
 ### Added

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zerotal/arch",
-  "version": "1.8.0",
+  "version": "1.8.1",
   "license": "MIT",
   "maturity": "stable",
   "private": false,
@@ -35,11 +35,11 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@zerotal/core": "1.8.0"
+    "@zerotal/core": "1.8.1"
   },
   "devDependencies": {
     "typescript": "^5.8.0",
-    "@zerotal/orm": "1.8.0"
+    "@zerotal/orm": "1.8.1"
   },
   "description": "The Zerotal agent surface — an MCP server that hands coding agents the framework's machine-readable truth: exact API signatures, live routes and schema, version-matched docs, and `zt doctor`.",
   "keywords": [

package/src/install/ArchInstallCommand.ts

@@ -16,7 +16,7 @@ import type { Application } from "@zerotal/core";
 import { ArchConfig } from "../config.ts";
 import type { ArchConfigShape } from "../config.ts";
 import { NoProjectRootError } from "../errors.ts";
-import { installedPackages } from "../probe/topics.ts";
+import { declaredPackages } from "../probe/topics.ts";
 import { detectAgents } from "./detect.ts";
 import { agentsPreamble, buildGuidelines, claudeShim } from "./guidelines.ts";
 import { detectShape } from "./shape.ts";
@@ -54,7 +54,9 @@ export class ArchInstallCommand extends Command {
     const config = this._config();
 
     const detected = await detectAgents(root);
-    const packages = (await installedPackages(root)).map((pkg) => pkg.name);
+    // Declared, not installed: what an install layout hoists into node_modules
+    // differs between machines, and the guidance must not.
+    const packages = (await declaredPackages(root)).map((pkg) => pkg.name);
     // Read off disk rather than from a booted app: a project that will not boot is
     // often exactly why someone is installing the agent surface.
     const shape = await detectShape(root);

package/src/probe/topics.ts

@@ -304,3 +304,43 @@ export async function installedPackages(root = process.cwd()): Promise<Installed
 function controllerLabel(rawName: string): string {
   return rawName.startsWith("FileRoute<") ? "file" : rawName;
 }
+
+/**
+ * The `@zerotal/*` packages this app *declares*, with their installed versions.
+ *
+ * {@link installedPackages} answers "what is on disk here", which is the right
+ * answer for a version report and the wrong one for guidance. Two things get into
+ * `node_modules/@zerotal` besides an app's own dependencies: transitive ones, and
+ * whatever an install layout decides to hoist — and layouts disagree. The same
+ * commit of one app resolved seventeen packages on a developer's machine and
+ * eleven on its server, because the server hoisted the shared ones to the
+ * workspace root instead.
+ *
+ * That is not a cosmetic difference when the list decides what an agent is told.
+ * `@zerotal/queue` arriving as a transitive dependency does not mean the app runs
+ * jobs, and a block explaining where jobs live is confidently wrong for an app
+ * that has none. It also made the generated file unstable between machines, so a
+ * check comparing it against the project could not tell drift from a difference
+ * of layout.
+ *
+ * Direct dependencies only, which is both deterministic and the honest reading of
+ * "what this app has": you import what you declare.
+ */
+export async function declaredPackages(root = process.cwd()): Promise<InstalledPackage[]> {
+  let declared: Set<string>;
+  try {
+    const manifest = (await Bun.file(`${root}/package.json`).json()) as {
+      dependencies?: Record<string, string>;
+      devDependencies?: Record<string, string>;
+    };
+    declared = new Set([
+      ...Object.keys(manifest.dependencies ?? {}),
+      ...Object.keys(manifest.devDependencies ?? {}),
+    ]);
+  } catch {
+    // No manifest to read — every installed package is as good a guess as any.
+    return installedPackages(root);
+  }
+
+  return (await installedPackages(root)).filter((pkg) => declared.has(pkg.name));
+}

package/src/provider/ArchProvider.ts

@@ -142,7 +142,7 @@ export async function agentsFileCheck(
     };
   }
 
-  const [{ buildGuidelines }, { detectShape }, { installedPackages }, markers] = await Promise.all([
+  const [{ buildGuidelines }, { detectShape }, { declaredPackages }, markers] = await Promise.all([
     import("../install/guidelines.ts"),
     import("../install/shape.ts"),
     import("../probe/topics.ts"),
@@ -160,7 +160,7 @@ export async function agentsFileCheck(
     };
   }
 
-  const packages = (await installedPackages(root)).map((pkg) => pkg.name);
+  const packages = (await declaredPackages(root)).map((pkg) => pkg.name);
   const shape = await detectShape(root);
   const expected = buildGuidelines({
     packages,