provident-storeroom 1.6.0 → 1.6.1

package/README.guide.md

@@ -30,7 +30,7 @@ preflight REFUSES when these two lines do not read what it computed** (`scripts/
 one check, read-only). **THE TWO LINES ARE THIS GUIDE'S OPERATIVE FIGURES; every dated paragraph below is the
 reading of its own date and is read through them.**
 
-PUBLISH-GUIDE-VERSION-LINE: THE VERSION THIS GUIDE DESCRIBES IS `1.6.0`.
+PUBLISH-GUIDE-VERSION-LINE: THE VERSION THIS GUIDE DESCRIBES IS `1.6.1`.
 PUBLISH-GUIDE-CUT-STATE: NOT STATED -- this document describes the behaviour at the version line above, and the cut-state is the release's to state, not a shipped document's (`D-57`).
 
 **⟶ AND THE CUT-STATE SENTENCE ABOVE IS WITHDRAWN, 2026-10-28 — THE CUT-STATE IS NOT A DOCUMENT'S TO STATE.** `RCA-8(g)` ANNOTATE-BESIDE, and the architect's ruling verbatim (`strata/decisions.md` · `D-57`): *"Drop the cut-state."* **The two marked lines above stand BYTE-FOR-BYTE as the reading of their own date and are read THROUGH this clause — not one byte of either is deleted — and the sentence this clause withdraws is the SECOND of them, the one that claims to say whether the release this guide travels in is cut.** **THE REASON IS MEASURED, THREE TIMES OVER, AND IT IS STRUCTURAL RATHER THAN A MISTAKE: A SHIPPED DOCUMENT IS SEALED BEFORE THE TAG THAT MAKES ITS CUT-STATE TRUE**, so every release packed before its tag ships a document denying itself, and a guard running in that release's own preflight can only ever confirm *"not cut"* — `1.2.0` shipped *"NOT CUT"*, `1.3.0` shipped *"`v1.3.0` DOES NOT EXIST"*, and the change list's head was stale within minutes of the tag that falsified it. **SO THE CUT-STATE SENTENCE IS DROPPED AS A CLAIM AND THE VERSION LINE STAYS**, because the version line is the ONE figure a tarball can be right about: the manifest knows it and travels beside it. **`scripts/publish.sh --figures` GENERATES AND ASSERTS THE VERSION LINE AND NOTHING ELSE** — the cut-state generation and its assertion are removed in the same act, so a tag set that moves can no longer redden this guide — **and the same one line is asserted in THREE shipped documents: this guide, `README.md` beside it, and the change list** (`DEF-AC`'s remaining demand, *"guard the release notes too"* and *"`README.md` still declares no version at all"*). **THE TAG SET IS NOT DELETED AND NOT DENIED: it is a RECORD OF RELEASES held in the change list, PAST TENSE — a list of what has been cut — and never a claim about the current one.** **AND WHAT THIS CLAUSE DOES NOT SAY, SAID PLAINLY BECAUSE A READER WILL LOOK FOR IT: it does not say whether the version this guide prints is cut.** That is not a document's to state; the record of what has been cut is in `RELEASE-NOTES.md`, and the registry is the registry.
@@ -74,6 +74,7 @@ measurements on a locally packed, installed artefact, and is still not witnessed
 **⟶ AND THE ELEVEN VERSION SITES READ `1.5.0`, 2026-10-29 — THE PREPARED FIGURE, AND EVERY `1.3.0` THIS GUIDE PRINTS READS `1.5.0` FROM HERE ON.** `RCA-8(g)` ANNOTATE-BESIDE: **the nine dated paragraphs above stand BYTE-FOR-BYTE and are read THROUGH this clause — so do their readings of `0.5.0`, `1.0.0`, `1.0.1`, `1.1.0`, `1.2.0` and `1.3.0`; each was true of the tree it was read on.** **THE MANIFEST AT ITS OWN BYTES THIS DATE: `bindings/js/package.json`'s `version` is `"1.5.0"`, all five `optionalDependencies` pins are `1.5.0` with it, and the five `bindings/js/platforms/*/package.json` `version` fields read `1.5.0` with them — ELEVEN CELLS, ONE VERSION, moved TOGETHER in this act and never singly (§0 item 1; `PUB-DD-10`) — and `npm run build` stamps the artefact from that manifest, so `version()` answers `1.5.0` at the built artefact and at a package installed from it.** **AND THE RELEASE THIS CHAIN SKIPPED IS NAMED RATHER THAN SILENTLY ABSORBED: `1.4.0` read `1.4.0` at those same eleven cells and was cut from them — the tag `v1.4.0` names a tree whose `bindings/js/package.json` reads `"version": "1.4.0"` at its own bytes.** **SO THE SITES ARE RE-READ, NOT RE-SPELLED:** this section's version line, §2.2's five exact pins, §8.1's *"an installed `0.5.0`"* — itself already corrected to `1.0.0`, `1.0.1`, `1.1.0`, `1.2.0` and `1.3.0` — and §11's manifest table all read `1.5.0`.
 
 **⟶ AND THE ELEVEN SITES READ `1.6.0` FROM THIS PREPARATION, 2026-10-29 — THE BUMP IS MADE HERE AND EVERY `1.5.0` ABOVE IS READ THROUGH THIS CLAUSE.** `RCA-8(g)` ANNOTATE-BESIDE: **every dated paragraph above stands BYTE-FOR-BYTE and is read THROUGH this clause — including its `1.5.0` — because each was true of the tree it was read on.** **THE MANIFEST AT ITS OWN BYTES THIS DATE: `bindings/js/package.json`'s `version` is `"1.6.0"`, all five `optionalDependencies` pins are `1.6.0` with it, and the five `bindings/js/platforms/*/package.json` `version` fields read `1.6.0` with them — ELEVEN CELLS, ONE VERSION, moved TOGETHER in this act and never singly (§0 item 1; `PUB-DD-10`)** — and **`npm run build` stamps the artefact from that manifest, so `version()` answers `1.6.0` at the built artefact and at a package installed from it** (measured this date at `bindings/js/build/Release/storeroom_js_binding.node`, and again at a package installed into a `/tmp` consumer with no repository in its ancestry). **SO THE SITES ARE RE-READ AGAIN, NOT RE-SPELLED:** this section's version line above, §2.2's five exact pins, §8.1's *"an installed …"* clause and §11's manifest table each read `1.6.0`, **and the one figure this guide can be right about is generated from that manifest and asserted in three shipped documents by `scripts/publish.sh --figures`.** **AND THE TAG SET IS A RECORD OF RELEASES AND NOT A CLAIM ABOUT THIS TREE:** `git tag --list` answers `v1.0.0` · `v1.0.1` · `v1.1.0` · `v1.2.0` · `v1.3.0` · `v1.4.0` · `v1.5.0`, `git describe` reads `v1.5.0-11-g8f5454f`, and **no `v1.6.0` is among them** — **so this clause states the version and NOT whether it is cut, because the cut-state is not a document's to state** (`D-57`; the clause above). **AND THE TAG SET IS A RECORD OF RELEASES AND NOT A CLAIM ABOUT THIS TREE:** `git tag --list` answers `v1.0.0` · `v1.0.1` · `v1.1.0` · `v1.2.0` · `v1.3.0` · `v1.4.0`, and `git describe` reads `v1.4.0-27-ga3312b7` — **so this clause states the version and NOT whether it is cut, because the cut-state is not a document's to state** (`D-57`; the clause above).
+**⟶ AND THE ELEVEN SITES READ `1.6.1` FROM THE DOCUMENTATION RELEASE, 2026-10-30 — EVERY `1.6.0` ABOVE IS READ THROUGH THIS CLAUSE.** `RCA-8(g)` ANNOTATE-BESIDE: **every dated paragraph above stands BYTE-FOR-BYTE and is read THROUGH this clause, because each was true of the tree it was read on.** **THE MANIFEST AT ITS OWN BYTES THIS DATE: `bindings/js/package.json`'s `version` is `"1.6.1"`, all five `optionalDependencies` pins are `1.6.1` with it, and the five `bindings/js/platforms/*/package.json` `version` fields read `1.6.1` with them — ELEVEN CELLS, ONE VERSION, moved TOGETHER in this act and never singly (§0 item 1; `PUB-DD-10`) — and `npm run build` stamps the artefact from that manifest, so `version()` answers `1.6.1` at the built artefact and at a package installed from it.** **SO THE SITES ARE RE-READ AGAIN, NOT RE-SPELLED:** this section's version line above, §2.2's five exact pins, §8.1's *"an installed …"* clause and §11's manifest table each read `1.6.1`. **AND WHAT THIS RELEASE CHANGES FOR YOU IS NO ARM OF THE PACKAGE: the failure form stays four members, a log entry stays five, the status set stays twenty and the kernel's token set stays nine** — the change list's `§1.6.1` states it with its arithmetic. **AND THE TAG SET IS A RECORD OF RELEASES AND NOT A CLAIM ABOUT THIS TREE:** `git tag --list` answers `v1.0.0` · `v1.0.1` · `v1.1.0` · `v1.2.0` · `v1.3.0` · `v1.4.0` · `v1.5.0` · `v1.6.0`, and `git describe` reads `v1.6.0-4-g674b79e`. (`D-57`; the change list's `§1.6.1`; `scripts/publish.sh --figures`, which asserts the one figure in three shipped documents.)
 
 **AND ONE THING A READER OF THE INSTALLED PACKAGE SHOULD KNOW BEFORE THE CITATIONS: WHEN THIS DOCUMENT IS AT
 `node_modules/provident-storeroom/README.guide.md`, IT IS THIS GUIDE.** **Its ONE authored home is

package/README.md

@@ -31,7 +31,7 @@ an edit belongs.
 
 **⟶ AND THE ONE FIGURE THIS PAGE CAN BE RIGHT ABOUT IS GENERATED AND ASSERTED, 2026-10-28 — `DEF-AC`'s third part, and `D-57`'s one surviving figure.** `RCA-8(g)` ANNOTATE-BESIDE: **every clause above stands BYTE-FOR-BYTE and is read THROUGH this one; nothing above moves.** **THE DEFECT THIS CLOSES: THIS PAGE DECLARED NO VERSION AT ALL** — a shipped document a consumer reads first, saying nothing about which release it describes — **so `scripts/publish.sh --figures` now GENERATES the line below from `bindings/js/package.json`'s `version` and REFUSES when it disagrees, exactly as it does at the guide's and the change list's own marked lines: three shipped documents, three version lines, one generator, one assertion.** **AND THE CUT-STATE IS NOT STATED HERE, OR ANYWHERE ELSE IN THIS PACKAGE'S DOCUMENTS** (`D-57`, the architect verbatim: *"Drop the cut-state"*): a document is sealed before the tag that would make its cut-state true, so **the cut-state is not a document's to state**; the record of what has been cut is the change list's, and it is past tense. **EVERY OTHER CLAIM OF THIS PAGE STANDS EXACTLY AS IT STOOD.**
 
-PUBLISH-README-VERSION-LINE: THE VERSION THIS README DESCRIBES IS `1.6.0`.
+PUBLISH-README-VERSION-LINE: THE VERSION THIS README DESCRIBES IS `1.6.1`.
 
 ## The one entry
 

package/RELEASE-NOTES.md

@@ -16,10 +16,12 @@ claims to be installable.**
 
 **⟶ AND THE CUT-STATE IS DROPPED FROM THIS FILE, 2026-10-28 — `D-57`, THE ARCHITECT VERBATIM: *"Drop the cut-state."*** `RCA-8(g)` ANNOTATE-BESIDE: **the title line and every dated paragraph of this file stand BYTE-FOR-BYTE as the reading of their own date, THIS clause is the one that reads them, and not one byte is deleted.** **THE REASON IS STRUCTURAL AND IT WAS MEASURED THREE TIMES: A SHIPPED DOCUMENT IS SEALED BEFORE THE TAG THAT MAKES ITS CUT-STATE TRUE**, so every release packed before its tag ships a document denying itself, and a guard running in that release's own preflight can only ever confirm *"not cut"* — `1.2.0` shipped *"NOT CUT"*, `1.3.0` shipped *"`v1.3.0` DOES NOT EXIST"*, and this file's own head was stale within minutes of the tag that falsified it. **SO EVERY SENTENCE BELOW THAT CLAIMS WHETHER SOME VERSION IS OR IS NOT CUT — *"PREPARED — NOT CUT"*, *"no `v1.3.0`"*, *"nothing in this section is cut"*, *"the release is not cut"*, *"what is installed today is still `1.1.0`"*, and each reading printed beside them — IS READ THROUGH THIS CLAUSE: the cut-state is not a document's to state.** **WHAT SURVIVES IS THE ONE FIGURE A SHIPPED DOCUMENT CAN BE RIGHT ABOUT, AND IT IS GENERATED FROM THE MANIFEST AND ASSERTED BY THE PREFLIGHT:**
 
-PUBLISH-NOTES-VERSION-LINE: THE VERSION THIS CHANGE LIST DESCRIBES IS `1.6.0`.
+PUBLISH-NOTES-VERSION-LINE: THE VERSION THIS CHANGE LIST DESCRIBES IS `1.6.1`.
 
 **AND THE TAG SET SURVIVES AS A RECORD OF RELEASES — PAST TENSE, A LIST OF WHAT HAS BEEN CUT, NEVER A CLAIM ABOUT THE CURRENT ONE** (the record stands in `§1.4.0` below — the section this file's head called `§main` until it was re-cut to name the version it prepares, 2026-10-28 — beside the section for the tree this file describes). (`D-57`; `DEF-AC` (b) — `scripts/publish.sh --figures` generates that line from `bindings/js/package.json`'s `version` and refuses on any disagreement, in this file, in `bindings/js/README.md` and in the shipped guide: three documents, three version lines, one generator, one assertion.)
 
+**⟶ AND THE CUT-STATE'S ONE AUTHORITY IS THE TAG SET, 2026-10-29 — `D-79` ITEM 2, KEPT BY `D-81` ITEM 2.** `RCA-8(g)` ANNOTATE-BESIDE: **no byte above or below moves; this clause is added beside the record paragraph above, and every dated paragraph of this file stands BYTE-FOR-BYTE as the reading of its own date.** **THE AUTHORITY IS `git tag --list` AND IT IS THE WHOLE OF IT: what has been released is what the tag set answers, and NO PROSE PARAGRAPH OF THIS FILE — or of the consumer guide, or of `bindings/js/README.md`, or of either landed copy — MAY ASSERT OR DENY THAT IN THE PRESENT TENSE.** **EVERY SENTENCE BELOW THAT DOES IS THE READING OF ITS OWN DATE AND IS READ THROUGH THIS CLAUSE**: the change lists of `§1.2.0` through `§1.5.0` describe releases the tag set answers for, and each one's sentence about what had or had not been released belongs to the date that wrote it. **AND WHAT THIS CLAUSE DOES NOT DO, SAID SO IT IS NOT READ AS DONE: it corrects none of them and deletes no byte of them** — `D-81` item `2`'s sweep is a REPORT of where each stands, and the catalogue at `docs/guides/backup/D81-2026-10-29-notes-move-out.md` §3 is that report, entry by entry, so a reader can check a scan by eye. (`D-79`; `D-81`; `git tag --list`.)
+
 **THE ONE THING THIS DOCUMENT IS FOR: `1.1.0` IS A MINOR, AND THIS IS WHERE ITS BREAKING CHANGES ARE
 DECLARED.** `1.0.1` was published as a PATCH and it carried behaviour changes a patch may not carry. The
 architect ruled the remedy a MINOR — *"the next release is `1.1.0`"* (`strata/decisions.md` · `D-42` item `1`)
@@ -73,7 +75,21 @@ the value to assert against, not the crate's own `Cargo.toml` version.
 
 **4 · AND A SHIPPED SENTENCE WAS FALSIFIED BY ALL OF IT, AND IS CORRECTED AT ITS OWN HOME.** **The package's `README.md` said a `delete` and a `rollback` both perform no file I/O at any tier scope.** **A `delete` SAVES NOW** — a `file`-tier delete left the bytes standing and a fresh boot read the old value; the terminal arm saves the delete's own op, and a failed save is the write's arm with `KC-9`. **A `rollback` still performs no file I/O, because it has no op of its own to save at** — and that half of the sentence was never in doubt. (`1090e1e`; `bindings/js/README.md`'s own 2026-10-28 clause.)
 
-## §1.6.0 · **PREPARED** — what `1.6.0` carries: the eleven commits on `main` past `v1.5.0`, derived from the tree
+---
+
+## §1.6.1 · **PREPARED** — a DOCUMENTATION release: what `1.6.1` carries, and the arithmetic that says how many commits
+
+**⟶ THIS SECTION IS NEW, 2026-10-30, AND IT STATES THE VERSION AND NOT THE CUT-STATE.** `RCA-8(g)` ANNOTATE-BESIDE: **no byte of the sections below moves; this section is added above `§1.6.0`, and that section's heading is corrected at its own line in the same act.** **AND THIS SECTION DOES NOT STATE WHETHER `1.6.1` HAS BEEN CUT: the cut-state is the tag set's to carry and not a document's to state** (`D-57`; the head clause of 2026-10-28 above, which governs every sentence here).
+
+**THE VERSION: `1.6.1` AT ELEVEN CELLS THAT MOVE TOGETHER AND NEVER SINGLY** — `bindings/js/package.json`'s `version`, its five exact `optionalDependencies` pins, and the five `bindings/js/platforms/*/package.json` `version` fields, read at their own bytes this date — **and `npm run build` stamps the artefact from that manifest, so `version()` answers `1.6.1` at the built artefact and at a package installed from it** (measured this date at `bindings/js/build/Release/storeroom_js_binding.node`, and again at a package installed into a `/tmp` consumer with no repository in its ancestry). **AND `scripts/publish.sh --figures` REPORTS THE SAME FIGURE IN THREE SHIPPED DOCUMENTS** — this change list's marked line, the guide's and `bindings/js/README.md`'s are each generated from that manifest, and the three agree: one generator, one assertion. (`DEF-AC` (b); `D-57`; `scripts/publish.sh --figures`.)
+
+**THE ARITHMETIC, RE-MEASURED AT THIS TREE: `git rev-list --count v1.6.0..HEAD` READS `4` AND `git describe` READS `v1.6.0-4-g674b79e`.** **The four — `636e69f`, `9ac7e0e`, `93682f3` and `674b79e` — each write `strata/decisions.md` and no other path: they are the rulings `D-79`, `D-80`, `D-81` and `D-82`, recorded beside the tree they measured, and not one of them changes a line the package ships.** **SO THE FOUR COMMITS MOVE NO BEHAVIOUR, AND THE RELEASE'S CONTENT IS THE WORKING TREE THIS PASS CARRIES BESIDE THEM — named here because a consumer must be able to read it before the cut:** **the TWO MOVE-OUTS** (`D-81` item `1`: the `§1.3.0` paragraph that claimed a cut-state and the clause that preserved it, each moved out byte-exactly into `docs/guides/backup/D81-2026-10-29-notes-move-out.md`, each leaving a one-line pointer at this file's lines `267` and `269`); **the SCANNER** (`D-81` item `3`: `scripts/publish.sh --cut-claims`, four documents and nine phrase spellings, NOT section-scoped); and **the RATCHET** (`D-82`: the catalogue is the exemption set — a cut claim at a catalogued site is accepted, a claim anywhere else is refused, and an entry whose site no longer carries one is a stale entry); **and beside them this version's bump, this section, the guide's and the README's generated lines, and the heading correction above.** **AND WHAT THAT ADDS UP TO FOR YOU, SAID INSTEAD OF LEFT TO INFERENCE: four record commits past `v1.6.0`, four documents touched on the working tree, and `4 + 4` is the whole of it — no line of `bindings/js/src/`, `bindings/js/index.mjs` or `bindings/js/index.d.ts` moved.**
+
+**NO BEHAVIOUR CHANGE — the failure form stays four members, `LogEntry` stays five, the status set stays twenty, the `KC` set stays nine, and not one call a consumer makes changes its answer.** **THIS IS A DOCUMENTATION RELEASE AND IT SAYS SO PLAINLY:** what `1.6.1` carries is the record of a guard's design and of a document's honesty — a scanner, a baseline, two moved-out passages and the arithmetic above — and **a consumer who installs `1.6.1` meets the behaviour of `1.6.0` at every arm the suite measures**, because no arm moved. (`D-74`; `D-75`; `D-77`; `D-78`; `§1.6.0`'s items `1` through `8`, which are the behaviour `1.6.0` carries; `npm test`'s reading on this tree.)
+
+## §1.6.0 · **CUT AND PUBLISHED — tag `v1.6.0`** — what that release carries: the eleven commits on `main` past `v1.5.0`, derived from the tree
+
+**⟶ `RCA-8(g)` MOVE-OUT OF THE HEADING THAT STOOD AT THIS LINE, AUTHORED 2026-10-30 BY THE `1.6.1` PASS (`D-82` · `DEF-AC`): THE HEADING THAT STOOD HERE CLAIMED A PREPARATION STATE OVER `1.6.0`, THE VERSION THE TAG `v1.6.0` NAMES — ITS BYTE-EXACT TEXT, WITH THE `sha256` OF ITS ONE LINE, STANDS AT `docs/guides/backup/D81-2026-10-29-notes-move-out.md` `§5`.** **`git tag --list` answers `v1.6.0`, so a heading over that version is a PAST-TENSE RECORD OF A RELEASE and not a preparation, which is the spelling `§1.4.0` and `§1.5.0` above already carry.** **AND WHAT THIS ACT DOES NOT DO: it moves no other byte of this section, its body and its items below stand BYTE-FOR-BYTE as the reading of their own date, and the `1.6.1` bump is stated in the section above and in no line of this one.** (`D-57`; `D-79`; `D-82`; `git tag --list`.)
 
 **⟶ THE HEADING THAT STOOD HERE WAS *"`## §1.6.0 · **PREPARED** — what `1.6.0` carries: the six commits on `main` past `v1.5.0`, derived from the tree`"*, AND ITS COUNT IS CORRECTED AT ITS OWN LINE, 2026-10-29.** `RCA-8(g)` ANNOTATE-BESIDE: **the withdrawn bytes are quoted above, every paragraph of this section below stands BYTE-FOR-BYTE as the reading of its own date, and nothing is deleted.** **THE COUNT MOVED BECAUSE THE TREE DID**: the section was written when `git describe` read `v1.5.0-6-g9e7a766`, and **the five commits after that reading — `74d871e` through `8f5454f` — carry `D-77`'s member and `D-78`'s clause, which this preparation declares.** **A HEADING THAT UNDERCOUNTS THE COMMITS IT PREPARES IS THE `DEF-AC` CLASS AT ITS MILDLEST AND IS CORRECTED RATHER THAN ANNOTATED AROUND, because the count is the one figure this section's own arithmetic prints.** (`D-57`; `git describe` at `v1.5.0-11-g8f5454f`; the arithmetic clause below, which is the re-sort.)
 
@@ -262,11 +278,9 @@ travelled in.** **Now `scripts/publish.sh` GENERATES both from `bindings/js/pack
 beside a generated *"IS CUT"* fails, and the generated line passes; `--figures` runs that one check read-only. **A
 hand-written line that contradicts the manifest can no longer travel.**
 
-**NOTHING IN THIS SECTION IS CUT, NO TAG NAMES IT, NO VERSION BUMP IS PROPOSED, AND THE ELEVEN VERSION SITES STAY AT
-`1.2.0`.** **The two behaviour changes are declared here because a consumer must be able to read them BEFORE the cut and
-must not be told they are in a tarball that does not carry them** — the same honesty the corrected head above owes.
+**⟶ `RCA-8(g)` MOVE-OUT, AUTHORED 2026-10-29 BY `D-81` ITEM 1 (`D-79` · `DEF-AC`): THE PARAGRAPH THAT STOOD HERE — the `§1.3.0` clause that asserted the cut-state of the version this section prepares, denied the tag set beside it, and named the figure the version cells then read — IS NO LONGER AT THESE LINES.** **Its byte-exact text stands at `docs/guides/backup/D81-2026-10-29-notes-move-out.md §1`, whose head names this source path, the pre-move lines `265`–`267` and the `sha256` of the region.** **The cut-state's ONE authority is `git tag --list`, stated at this file's head clause of 2026-10-29: no paragraph here asserts or denies it.** **AND WHAT DID NOT MOVE: the two behaviour changes the paragraph preceded travelled in `1.3.0`'s tarball and are declared at this section's items `1` and `2` above, unmoved.** (`D-79`; `D-81`; `git tag --list`.)
 
-**⟶ AND WHAT THE PARAGRAPH ABOVE SAYS ABOUT THE FIGURES IS SUPERSEDED BY THIS PREPARATION, 2026-10-28 — WHAT IT SAYS ABOUT THE CUT IS NOT.** `RCA-8(g)` ANNOTATE-BESIDE: **the paragraph above stands BYTE-FOR-BYTE as the reading of its own date and is read THROUGH this clause.** **UNMOVED: *"NOTHING IN THIS SECTION IS CUT, NO TAG NAMES IT"* — `git tag --list` carries no `v1.3.0`, the registry carries no `1.3.0`, and a consumer cannot install any of this.** **SUPERSEDED: *"NO VERSION BUMP IS PROPOSED, AND THE ELEVEN VERSION SITES STAY AT `1.2.0`"* — the bump IS this preparation's, and the eleven sites read `1.3.0`** (the clause at this section's head states the manifest, the pins, the five platform manifests and the rebuilt artefact's `version()`). **The two behaviour changes are unchanged, and they are `1.3.0`'s content: what a consumer installing `1.2.0` gets is `1.2.0`'s bytes, and this section is the change list of the version being prepared, not of a released one.**
+**⟶ `RCA-8(g)` MOVE-OUT, AUTHORED 2026-10-29 BY `D-81` ITEM 1 (`D-79` · `DEF-AC`): THE CLAUSE THAT STOOD HERE — the `2026-10-28` annotate-beside that preserved the paragraph above's cut-state while superseding its figures — IS NO LONGER AT THIS LINE.** **Its byte-exact text stands at `docs/guides/backup/D81-2026-10-29-notes-move-out.md §2`, whose head names this source path, the pre-move line `269` and the `sha256` of the region.** **The distinction that clause drew is kept where it belongs: `§1.3.0`'s own head records the release the tag set answers for, and its half about the figures is the reading of its own date.** **The cut-state's ONE authority is `git tag --list`, stated at this file's head clause of 2026-10-29: no paragraph here asserts or denies it.** (`D-79`; `D-81`; `git tag --list`.)
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "provident-storeroom",
-  "version": "1.6.0",
+  "version": "1.6.1",
   "description": "U-STOREROOM-PUBLISH: the published Node ESM binding for the native Rust store of Provident-Storeroom — the entry resolves the scoped per-target platform package first, the checkout's own module-relative addon second, and answers the store's single declared absent-addon form when neither loads",
   "type": "module",
   "license": "AGPL-3.0",
@@ -41,11 +41,11 @@
     "src/constraint-kernel.mjs"
   ],
   "optionalDependencies": {
-    "@auspicion/provident-storeroom-js-linux-x64-gnu": "1.6.0",
-    "@auspicion/provident-storeroom-js-linux-arm64-gnu": "1.6.0",
-    "@auspicion/provident-storeroom-js-darwin-x64": "1.6.0",
-    "@auspicion/provident-storeroom-js-darwin-arm64": "1.6.0",
-    "@auspicion/provident-storeroom-js-win32-x64-msvc": "1.6.0"
+    "@auspicion/provident-storeroom-js-linux-x64-gnu": "1.6.1",
+    "@auspicion/provident-storeroom-js-linux-arm64-gnu": "1.6.1",
+    "@auspicion/provident-storeroom-js-darwin-x64": "1.6.1",
+    "@auspicion/provident-storeroom-js-darwin-arm64": "1.6.1",
+    "@auspicion/provident-storeroom-js-win32-x64-msvc": "1.6.1"
   },
   "publishConfig": {
     "access": "public"