fix(tui): execute store wizard plans

Author: flyingrobots

BEARING.md

@@ -14,9 +14,10 @@ timeline
 
 ## Current State
 
-The encryption surface has been simplified and the dedup-with-encryption gap is
-closed. The 20-card backlog from Phase 5 remains clear; recent work focused on
-collapsing scheme complexity and shipping convergent encryption.
+`v6.0.0` shipped on `2026-05-09`. The encryption surface has been simplified,
+the dedup-with-encryption gap is closed, and npm plus GitHub Releases are the
+active publication surfaces while JSR remains deferred behind the upstream
+toolchain blocker.
 
 What exists now:
 
@@ -91,10 +92,10 @@ These were the active tensions from the previous bearing. All resolved.
 
 ## Open Tensions
 
-- **CasService size.** At ~2100 lines, `CasService` is still the largest single
-  module. The published decomposition order (store coordination, then manifest
-  publication, then recipient flows, then restore pipeline) has not yet been
-  executed. The service works, but it concentrates too many responsibilities.
+- **TUI modernization.** The cockpit is useful and the Store Wizard now executes
+  the encryption, compression, and chunking plan it presents. The remaining TUI
+  work is broader operator ergonomics, discoverability, and long-lived workflow
+  polish rather than a store-plan correctness blocker.
 - **No browser/edge runtime.** The architecture is now fully hexagonal and
   platform-agnostic at the port level, but no browser or edge adapter exists.
   `@git-stunts/plumbing` shells out to the `git` CLI, which is fundamentally
@@ -110,14 +111,11 @@ These were the active tensions from the previous bearing. All resolved.
 
 ## Next Horizon
 
-With schemes simplified and convergent encryption shipped, these are candidate
-directions — not commitments.
+With v6.0.0 shipped, these are candidate directions — not commitments.
 
-- **CasService decomposition.** Execute the published extraction order: pull
-  store write coordination into `StoreCoordinator`, manifest/tree publication
-  into `PublicationService`, recipient mutation into `RecipientService`, and
-  restore pipeline into `RestoreService`. Each extraction should preserve the
-  public facade contract.
+- **TUI modernization.** Keep dashboard and wizard actions sharing executable
+  option-building truth while improving operator ergonomics around long-lived
+  store, restore, vault, and diagnostics workflows.
 - **Browser/edge persistence adapter.** A `FetchPersistenceAdapter` or
   `IsomorphicGitAdapter` could enable browser-side restore (read path) without
   the `git` CLI. Write path is harder — it needs ref updates and tree creation.

CHANGELOG.md

@@ -7,6 +7,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [6.0.1] — 2026-05-09
+
+### Added
+
+- **Per-operation chunking overrides** — `ContentAddressableStore.store()` and
+  `storeFile()` now accept a `chunking` option for a single operation, allowing
+  CDC or fixed chunking without mutating the facade's default chunker.
+- **Active release-doc drift guard** — active release documents now have a unit
+  guard against stale pre-v6.0.0 claims resurfacing after publication.
+
 ### Changed
 
 - **Release workflow future-runtime hardening** — The GitHub Release job now
@@ -17,6 +27,22 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   navigation. Dense restore streaming detail moved to `GUIDE.md`, while the
   security hardening table in `ADVANCED_GUIDE.md` now carries the detailed
   limits previously summarized in the README.
+- **Post-v6 planning truth** — `STATUS.md`, `ROADMAP.md`, `BEARING.md`, and the
+  METHOD backlog now describe `v6.0.x` maintenance rather than the completed
+  `v6.0.0` pre-tag state.
+- **6.0.1 release verification** — `npm run release:verify -- --skip-jsr`
+  passed 12/12 steps with 5,383 observed tests. JSR remains intentionally
+  skipped for this patch line.
+
+### Fixed
+
+- **TUI Store Wizard execution** — the Operations workspace Store Wizard now
+  threads passphrase encryption, forced convergent encryption, gzip
+  compression, and fixed/CDC chunking into the actual `storeFile()` call before
+  publishing the manifest tree to the vault.
+- **Store Wizard state flow** — passphrase and convergent selections collect a
+  passphrase before the compression step, and the wizard step count remains
+  contiguous when encryption is skipped.
 
 ## [6.0.0] — 2026-05-09
 

GUIDE.md

@@ -174,6 +174,21 @@ const manifest = await cas.storeFile({
 
 The filename defaults to the basename of `filePath`. Override it with the optional `filename` parameter.
 
+Use `chunking` on a single store call when one asset needs a different strategy
+from the facade default:
+
+```js
+const manifest = await cas.storeFile({
+  filePath: './large-archive.tar',
+  slug: 'archives/large',
+  chunking: { strategy: 'cdc' },
+});
+```
+
+This override is scoped to that operation. The next `store()` or `storeFile()`
+call returns to the facade's configured chunker unless it also supplies
+`chunking`.
+
 ---
 
 ## Encryption
@@ -848,13 +863,17 @@ This table describes the high-level `ContentAddressableStore` facade. The facade
 
 ### Chunking Config Object
 
+Constructor `chunking` sets the facade default. `store()` and `storeFile()` can
+also receive the same object as a per-operation override.
+
 | Key               | Type               | Description                            |
 | ----------------- | ------------------ | -------------------------------------- |
 | `strategy`        | `'fixed' \| 'cdc'` | Chunking strategy                      |
 | `chunkSize`       | `number`           | Fixed chunk size (fixed strategy only) |
 | `targetChunkSize` | `number`           | CDC target chunk size                  |
 | `minChunkSize`    | `number`           | CDC minimum chunk size                 |
 | `maxChunkSize`    | `number`           | CDC maximum chunk size                 |
+| `normalized`      | `boolean`          | Use FastCDC-style dual-mask boundaries |
 
 ### `.casrc` Project Config
 

ROADMAP.md

@@ -12,26 +12,26 @@ Fresh planning now follows the METHOD:
 
 ## Current Reality
 
-- **Last tagged release:** `v5.3.2` (`2026-03-15`)
-- **Current release candidate:** `v6.0.0` on `release/v6.0.0`
+- **Last tagged release:** `v6.0.0` (`2026-05-09`)
+- **Current release line:** `v6.x` maintenance on `main`
 - **Supported runtimes:** Node.js 22.x, Bun, Deno
 - **Human surface reality:** the human CLI and TUI are substantial and already
   ahead of some older planning docs.
 - **Agent surface reality:** a first-class `git cas agent` contract now exists
   for shipped Relay flows, but breadth and portability are still incomplete.
 - **Planning reality:** fresh work is now chosen from METHOD backlog lanes, not
   milestone fiction.
-- **Release posture:** JSR publication is deferred from the v6.0.0 tag path
-  until the upstream `jsr`/Deno dry-run blocker is fixed.
+- **Release posture:** npm and GitHub Releases are the active v6.0.x
+  publication surfaces. JSR publication is deferred until the upstream
+  `jsr`/Deno dry-run blocker is fixed.
 
 ## Current Queue Snapshot
 
 See the live backlog for exact lane placement:
 
-- [REL — Version Bump](./docs/method/backlog/v6.0.0/REL_version-bump.md)
 - [TUI — v6.x TUI Modernization](./docs/method/backlog/v6.x-tui/TUI_store-wizard.md)
-- [TUI — Store Wizard Execution Gap](./docs/method/backlog/bad-code/TUI_store-wizard-execution-gap.md)
-- [SEC — Vault Passphrase Verifier Gap](./docs/method/backlog/bad-code/SEC_vault-passphrase-verifier-gap.md)
+- [Vault Tree Memory Loading](./docs/method/backlog/bad-code/vault-tree-memory-loading.md)
+- [TR — GitPersistenceAdapter Full Materialization](./docs/method/backlog/bad-code/TR_persistence-adapter-materialization.md)
 
 ## How To Read This File
 

STATUS.md

@@ -1,7 +1,8 @@
 # STATUS
 
 **Last tagged release:** `v6.0.0` (`2026-05-09`)
-**Current release state:** `v6.0.0` is published to npm and GitHub Releases; JSR publication is deferred for the v6.0.0 line.
+**Current release state:** `v6.0.1` patch candidate on `main`; `v6.0.0` is published to npm and GitHub Releases, and JSR publication is deferred for the v6.0.x line.
+**Latest verification:** `npm run release:verify -- --skip-jsr` passed 12/12 steps with 5,383 observed tests.
 **Playback truth:** `main`
 **Runtimes:** Node.js 22.x, Bun, Deno
 **Current planning method:** [WORKFLOW.md](./WORKFLOW.md)
@@ -56,6 +57,13 @@
   orchestrates use cases while dedicated collaborators own persistence, tree-OID
   cache state, metadata/tree codecs, privacy indexing, key verification, and retry
   policy.
+- Store Wizard execution now uses the same `storeFile()` option payload it
+  presents in the UI: passphrase/convergent encryption, gzip compression, and
+  fixed/CDC chunking choices are threaded into the CAS facade before the
+  manifest is published to the vault.
+- `ContentAddressableStore.store()` and `storeFile()` accept per-operation
+  `chunking` overrides, so one store can use CDC or fixed chunking without
+  mutating the facade's default chunker.
 - Manifest parsing now rejects unsupported encryption schemes,
   `encrypted: false`, malformed AES-GCM nonce/tag values, and framed manifests
   that omit `frameBytes`, across both JSON and CBOR manifest codecs.
@@ -72,7 +80,8 @@
 
 ## Active Queue Snapshot
 
-- [TUI — Store Wizard Execution Gap](./docs/method/backlog/bad-code/TUI_store-wizard-execution-gap.md)
+- [Vault Tree Memory Loading](./docs/method/backlog/bad-code/vault-tree-memory-loading.md)
+- [TR — GitPersistenceAdapter Full Materialization](./docs/method/backlog/bad-code/TR_persistence-adapter-materialization.md)
 
 ## Read Next