@aryacode/dsh-aryacode-polish 0.3.4 → 0.3.6

package/CHANGELOG.md

@@ -1,5 +1,33 @@
 # Changelog
 
+## [0.3.6] - 2026-10-27
+
+### Fixed
+
+- **The README's status line no longer carries a version.** The packaged README is
+  the card's page body, so any version written into its prose is stale as soon as
+  the next release ships — 0.3.5 was published with a page still describing
+  "0.3.4". The status now says what shipped; the version comes from the manifest
+  and the page header. `test/docs.spec.mjs` fails if a version returns.
+
+## [0.3.5] - 2026-10-27
+
+### Fixed
+
+- **The card's own page described an older plugin.** The README that ships in the
+  tarball *is* the page body in the Plugins market, and it still said "0.2.0, one
+  feature shipped" and listed a layout directory that does not exist. Status,
+  layout, and requirements now match the package.
+
+### Changed
+
+- `HANDOFF.md` was rewritten for the shipped bundle: the contracts that cost time
+  (a row's config namespace is the row id, not the slot key; no bundler for the
+  face; the client session contract exposes no events), the slot geography around
+  the account row, the development loop, and the release order that keeps the
+  catalogue record. `test/docs.spec.mjs` now fails if the briefing drifts back to
+  the stale claims it once made.
+
 ## [0.3.4] - 2026-10-27
 
 ### Added

package/README.md

@@ -7,7 +7,8 @@ installed into and patches nothing. It is one package, one Plugins row, and one
 switch per feature, so a refinement that turns out to be wrong for a machine can
 be turned off without uninstalling anything.
 
-Status: **0.2.0.** One feature shipped: the estimated session cost pill.
+Status: **two features shipped.** The version is the package's, and the card
+header already shows it.
 
 ## What it is
 
@@ -116,10 +117,11 @@ entries/polish.js    the row: Config derived from the registry, apply()
 entries/registry.js  the feature list — the one place a feature is declared
 entries/usage.js     the fold: model-attributed usage out of the session log
 entries/cost.js      the polishCost projection: rates, pricing, host mount
-entries/features/    one module per feature
 entries/config.js    volatile-reference accessors (resolve/flag/list/text)
 lib/index.js         mount point re-exporting the row
 client/face.js       browser face source: the Configure page and every surface
+client/money.js      which wallet is shown, and how the amount is rendered
+client/account.js    the granted, timeout-bounded balance read
 client/switches.json the browser half of the seam — one entry per switch
 scripts/build-client.mjs  wraps client/face.js into lib/client.js
 lib/client.js        generated: the bundle the Shell loads

package/lib/client.js

@@ -23,7 +23,7 @@ window.__ModuleLoader__.load({
     ]
     const ROW_ID = "polish"
     const ROW_KEY = "@aryacode/dsh-aryacode-polish" + '#' + ROW_ID
-    const CLIENT_VERSION = "0.3.4"
+    const CLIENT_VERSION = "0.3.6"
 
     /**
      * The two pure decisions behind the balance line: which wallet to show, and how

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aryacode/dsh-aryacode-polish",
-  "version": "0.3.4",
+  "version": "0.3.6",
   "description": "AryaCode Polish: one install for the small things that make AryaCode feel finished. One Plugins row, one switch per quality-of-life feature.",
   "keywords": [
     "dsh",