@bowmark/web 1.0.0 → 1.2.0

package/README.md

@@ -1,11 +1,12 @@
 # @bowmark/web
 
-> **Status:** publishable, 2026-08-05 · `private` is gone and the two-hop release is
-> wired (Phase 6 of
-> [`docs/plans/public-types-package.md`](../../../docs/plans/public-types-package.md)).
-> Nothing above `0.0.0` is on npm until release-please bumps `package.json` and the
-> mirror's `publish.yml` sees the change. **What would make this doc wrong:** a build
-> step appearing, or the declarations moving out into a second package.
+> **Status:** PUBLISHED · `@bowmark/web@1.0.0` on npm, 2026-08-06, alongside
+> `bowmark-web` and `bowmark-web-stubs` on PyPI at the same version. The plan that built it
+> is deleted; the reasoning is in the four
+> [`docs/decisions/2026-08-06-*`](../../../docs/decisions/) records and the enforceable half
+> is [`.claude/rules/public-types.md`](../../../.claude/rules/public-types.md).
+> **What would make this doc wrong:** a build step appearing, the declarations moving out
+> into a second package, or a runtime dependency landing in `package.json`.
 
 ```sh
 npm i @bowmark/web
@@ -186,13 +187,20 @@ message.
 
 **What it fails CLOSED on, and the two things it must not.** A known unit with an
 unknown FUNCTION is refused — the table is authoritative about a unit it carries. An
-unknown UNIT passes straight through, because a Shopify family MEMBER
-(`providers.gymshark`) is absent from every manifest **by design** — `listProviders()`
-excludes members and always will — so refusing an unknown unit would refuse the largest
-part of the library. A function with no readable argument shape is an EXPLICIT `null` in
-the table rather than an absence, and passes through; that distinction is what makes the
+unknown UNIT passes straight through, because a family MEMBER (`providers.gymshark`) is
+absent from the RUNTIME validator table **by design** — `listProviders()` excludes
+members and always will — so refusing an unknown unit would refuse the largest part of
+the library. A function with no readable argument shape is an EXPLICIT `null` in the
+table rather than an absence, and passes through; that distinction is what makes the
 first rule safe at all.
 
+Note the deliberate asymmetry with the TYPES: since 2026-08-06 a member IS declared in
+`library.d.ts`, so `providers.gymshark.search(…)` completes and type-checks. The two
+answer different questions. Types are a build-time artifact and can afford one line per
+member; the validator table is loaded into every client process at runtime, where 51,711
+entries would be a cost paid on every call to buy nothing — the family's arguments are
+already checked by the shared interface the compiler saw.
+
 **A parameter may not offer a type the wire cannot carry.** Every argument crosses as
 JSON on every surface, so `requestedTime?: string | Date` has an arm refused 100% of the
 time while the library says otherwise. `gate:public-types`' `wire-impossible-param`
@@ -203,10 +211,16 @@ for all 253 typed parameters.
 ## Regenerating
 
 ```bash
-pnpm run gen:public-types   # writes src/generated/{library.d.ts,validators.ts}
-pnpm run gate:public-types  # fails if either committed file is stale, or leaks
+pnpm run gen:public-types         # writes src/generated/{library.d.ts,validators.ts}
+pnpm run gate:public-types        # fails on a leak, a new refusal, a wire-impossible type
+pnpm run gate:public-types:drift  # …and on the committed copy being stale
 ```
 
+**Only the middle one runs on your PR, and staleness is deliberately not fatal there.**
+The committed copy goes stale every time any unit anywhere lands a function, which is not
+something your branch can keep true — `regen-public-types.yml` repairs it on `main`. See
+`.claude/rules/public-types.md` § The gate is SPLIT.
+
 **`skipLibCheck: false` in this package's `tsconfig.json` is load-bearing**, and the base
 config sets the opposite. That flag skips type checking of every `.d.ts`, and this
 package's whole deliverable IS a `.d.ts` — with the inherited default, `pnpm typecheck`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bowmark/web",
-  "version": "1.0.0",
+  "version": "1.2.0",
   "type": "module",
   "description": "The public client for the Bowmark capability library — real TypeScript for the whole bowmark.* surface, with no Bowmark source on the caller's disk. ZERO runtime dependencies, deliberately and permanently.",
   "license": "MIT",