@michaelmagan/dnumb 0.1.0 → 0.1.1

package/AGENTS.md

@@ -165,8 +165,9 @@ does not.
 
 ## Status
 
-**Pre-release, not yet on npm.** The library surface above is built and tested. The CLI has a
-stable verb set — `capture`, `look`, `diff`, and `q describe|find|at|within|distance|nearest|facts|color`
+**Published.** `npm install --save-dev @michaelmagan/dnumb` — MIT, zero dependencies. The library
+surface above is built and tested. The CLI has a stable verb set — `capture`, `look`, `diff`, and
+`q describe|find|at|within|distance|nearest|facts|color`
 — documented with worked examples in
 [README § From the CLI](https://github.com/michaelmagan/dnumb/blob/main/README.md#from-the-cli) and
 [§ Reading a diff](https://github.com/michaelmagan/dnumb/blob/main/README.md#reading-a-diff). This
@@ -174,6 +175,18 @@ file still does not restate flags, on purpose: run `dnumb --help` for the exhaus
 list of what your installed copy actually supports, and treat it as authoritative over any prose
 here or there.
 
+**Invoking it — three forms, not one.** Nothing installed yet, any package manager: `npx
+@michaelmagan/dnumb --help` (or `bunx @michaelmagan/dnumb --help`) — the zero-install form, works
+everywhere. Already a dependency — installed via `npm install`, `pnpm add`, or `bun add`, all of
+which populate `node_modules/.bin/dnumb` the same way: `npx dnumb --help` or `bunx dnumb --help`,
+either resolves the local bin regardless of which tool installed it (verified: `npx` correctly
+resolves a bun-installed bin, including under bun's isolated linker). **If a bare `npx dnumb ...` or
+`bunx dnumb ...` 404s, that means nothing is installed locally, not that the package doesn't
+exist** — both tools then resolve `dnumb` as a *package* name against the registry, and there is no
+unscoped `dnumb` package on npm (permanently blocked by npm's similarity filter); retry with the
+scoped form above, or install first: `npm install --save-dev @michaelmagan/dnumb` / `bun add -d
+@michaelmagan/dnumb`.
+
 The digest format is specified in
 [`docs/digest.md`](https://github.com/michaelmagan/dnumb/blob/main/docs/digest.md). Build progress,
 including what was tried and what was wrong, is in

package/README.md

@@ -20,7 +20,7 @@ e0 body @0,0 1024x181
   e1 h1.heading "Account settings" @24,24 976x25
   e2 div @24,65 976x44 [row] ↓16 [overflow-y +105px; clip]
     e3 button.button "Actions" @39,77 60x21
-    e4 span "3 selected" @111,77 68x20 →12
+    e4 span "3 selected" @111,75 90x24 →12
     e5 nav.menu "Actions" @39,104 182x109 →-110 [clipped by e2 div; overflow:hidden, not scrollable; 103.8px below, 182x5 visible]
       e6 a.menuitem "Rename" @40,105 180x36 [clipped by e2 div; overflow:hidden, not scrollable; 31.6px below, 180x4 visible]
       e7 a.menuitem "Duplicate" @40,141 180x36 ↓0 [clipped by e2 div; overflow:hidden, not scrollable; 67.2px below, nothing visible]
@@ -41,12 +41,13 @@ other four are, only in this one header line and the `q color` verb — naming e
 pair on the page with a WCAG contrast ratio beside it, and never a pass/fail. See
 [`docs/digest.md`](docs/digest.md#color) for the full grammar.
 
-> **Status: pre-release.** Not published to npm. The library — capture, digest, facts, clip
-> analysis, bundles, the Playwright integration — is built and tested. The CLI (`capture`, `look`,
-> `diff`, `q`) has a stable verb set, worked below in [From the CLI](#from-the-cli) and
-> [Reading a diff](#reading-a-diff); `dnumb --help` stays the exhaustive, versioned option list.
-> Build journal in [`LOG.md`](LOG.md); the plan is
-> [`docs/00-PLAN-OF-RECORD.md`](docs/00-PLAN-OF-RECORD.md).
+> **Status: published.** `npm install --save-dev @michaelmagan/dnumb` — MIT, zero dependencies. The
+> library — capture, digest, facts, clip analysis, bundles, the Playwright integration — is built
+> and tested. The CLI (`capture`, `look`, `diff`, `q`) has a stable verb set, worked below in
+> [From the CLI](#from-the-cli) and [Reading a diff](#reading-a-diff); `dnumb --help` stays the
+> exhaustive, versioned option list. Build journal in [`LOG.md`](LOG.md); the plan is
+> [`docs/00-PLAN-OF-RECORD.md`](docs/00-PLAN-OF-RECORD.md); the release history is
+> [`docs/06-RELEASE.md`](docs/06-RELEASE.md).
 
 ## The idea
 
@@ -174,8 +175,23 @@ No test suite yet, or just want a bundle right now? The shortest path from a URL
 two commands:
 
 ```bash
-dnumb capture https://example.com/settings --name settings-desktop
-dnumb --from .dnumb/settings-desktop.json look
+npx @michaelmagan/dnumb capture https://example.com/settings --name settings-desktop  # no install
+npx @michaelmagan/dnumb --from .dnumb/settings-desktop.json look
+```
+
+On a bun project, `bunx` is the equivalent zero-install form: `bunx @michaelmagan/dnumb --help`.
+
+Already installed it (`npm install --save-dev @michaelmagan/dnumb`, or `bun add -d
+@michaelmagan/dnumb`)? Drop the scope — `npx dnumb` and `bunx dnumb` both resolve the local `dnumb`
+bin the same way, since npm, pnpm, and bun all populate `node_modules/.bin/dnumb` identically.
+Without a local install, either tool takes `dnumb` as a *package* name, not a bin name, and there is
+no unscoped `dnumb` package on npm (see [`docs/06-RELEASE.md` §0](docs/06-RELEASE.md)) — so a bare
+`npx dnumb` or `bunx dnumb` with nothing installed 404s.
+
+```bash
+npx dnumb capture https://example.com/settings --name settings-desktop  # after install
+npx dnumb --from .dnumb/settings-desktop.json look
+# or, in a bun project: bunx dnumb capture ...  /  bunx dnumb --from ... look
 ```
 
 `capture` launches a browser, navigates, captures, and writes `.dnumb/settings-desktop.json` —

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@michaelmagan/dnumb",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Turns a rendered page into measurements an agent can read: element geometry, overflow, clipping, and a text diff of what changed between two states.",
   "keywords": [
     "agent",
@@ -36,9 +36,9 @@
     "AGENTS.md"
   ],
   "publishConfig": {
-    "access": "public"
+    "access": "public",
+    "provenance": true
   },
-  "packageManager": "pnpm@11.24.0",
   "intent": {
     "version": 1,
     "repo": "michaelmagan/dnumb",
@@ -55,21 +55,6 @@
       "dnumb": "./src/cli.ts"
     }
   },
-  "scripts": {
-    "build": "zshy --project tsconfig.build.json && node scripts/exports-map.mjs",
-    "postbuild": "node scripts/exports-map.mjs",
-    "typecheck": "tsc --noEmit",
-    "lint": "biome check --error-on-warnings .",
-    "format": "biome check --write .",
-    "test": "vitest run --project unit",
-    "test:browser": "vitest run --project browser",
-    "test:all": "vitest run",
-    "test:travel": "bash scripts/travel-test.sh",
-    "check:package": "publint --strict && attw --pack .",
-    "prepack": "pnpm run build",
-    "prepublishOnly": "pnpm run typecheck && pnpm run lint && pnpm run test && pnpm run test:browser && pnpm run check:package",
-    "release": "changeset publish"
-  },
   "peerDependencies": {
     "playwright-core": ">=1.17.0"
   },
@@ -137,5 +122,18 @@
         "./dist/spec/index.d.cts"
       ]
     }
+  },
+  "scripts": {
+    "build": "zshy --project tsconfig.build.json && node scripts/exports-map.mjs",
+    "postbuild": "node scripts/exports-map.mjs",
+    "typecheck": "tsc --noEmit",
+    "lint": "biome check --error-on-warnings .",
+    "format": "biome check --write .",
+    "test": "vitest run --project unit",
+    "test:browser": "vitest run --project browser",
+    "test:all": "vitest run",
+    "test:travel": "bash scripts/travel-test.sh",
+    "check:package": "publint --strict && attw --pack .",
+    "release": "changeset publish"
   }
-}
+}

package/skills/dnumb/SKILL.md

@@ -27,10 +27,11 @@ e5 nav.menu "Actions" @39,104 182x109 →-110 [clipped by e2 div; overflow:hidde
 A menu overlapping the sibling before it — negative gap — clipped by its own parent's
 `overflow: hidden` with only a 5px sliver surviving. Neither line says "bug". You decide that.
 
-## Status: pre-release
+## Status: published
 
-Not yet published to npm. The library surface below is built and tested. The CLI has a stable verb
-set — `capture`, `look`, `diff`, and `q describe|find|at|within|distance|nearest|facts|color` — worked in
+`npm install --save-dev @michaelmagan/dnumb` — MIT, zero dependencies. The library surface below is
+built and tested. The CLI has a stable verb set — `capture`, `look`, `diff`, and
+`q describe|find|at|within|distance|nearest|facts|color` — worked in
 [README § From the CLI](https://github.com/michaelmagan/dnumb/blob/main/README.md#from-the-cli) and
 [§ Reading a diff](https://github.com/michaelmagan/dnumb/blob/main/README.md#reading-a-diff). This
 file does not restate flags: run `dnumb --help` for the exhaustive, versioned list of what your
@@ -70,6 +71,15 @@ npm install --save-dev @michaelmagan/dnumb
 everything — dnumb reuses your browsers and never downloads its own. If it does not, everything
 downstream of a saved bundle still works with no browser at all.
 
+**No install, just try the CLI:** `npx @michaelmagan/dnumb --help` (or, on a bun project, `bunx
+@michaelmagan/dnumb --help`). **After installing — via npm, pnpm, or `bun add -d
+@michaelmagan/dnumb` — the shorter `npx dnumb --help` / `bunx dnumb --help` also works**, either
+one, since all three package managers populate `node_modules/.bin/dnumb` the same way and both
+`npx` and `bunx` resolve a local bin from it before ever touching the registry. **A bare `npx dnumb
+...` or `bunx dnumb ...` with nothing installed 404s against the registry**, because the tool is
+then resolving `dnumb` as a package name, not a bin name, and no unscoped `dnumb` package exists. A
+404 there means "install it," not "the tool doesn't exist."
+
 ## Read this before you use the output
 
 **Facts come with counter-facts, and a fact is not a verdict.** The same number means different