Merge pull request #1511 from Hellblazer/release/v7.34.0

release: conexus 7.34.0

Author: Hellblazer

.claude-plugin/marketplace.json

@@ -11,21 +11,21 @@
         "source": "git-subdir",
         "url": "https://github.com/Hellblazer/nexus.git",
         "path": "conexus",
-        "ref": "v7.33.0"
+        "ref": "v7.34.0"
       },
       "description": "Self-hosted three-tier knowledge management with 13 specialized agents, plan-centric retrieval via nx_answer, semantic search, and RDR decision tracking for Claude Code.",
-      "version": "7.33.0"
+      "version": "7.34.0"
     },
     {
       "name": "sn",
       "source": {
         "source": "git-subdir",
         "url": "https://github.com/Hellblazer/nexus.git",
         "path": "sn",
-        "ref": "v7.33.0"
+        "ref": "v7.34.0"
       },
       "description": "Injects Serena and Context7 MCP tool usage guidance into subagents via SubagentStart hook.",
-      "version": "7.33.0"
+      "version": "7.34.0"
     }
   ]
 }

CHANGELOG.md

@@ -6,6 +6,54 @@ Versioning follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
 
+## [7.34.0] - 2026-09-06
+
+Paired with engine-service-v0.1.106 (`REQUIRED_ENGINE_VERSION` 0.1.106).
+
+### Fixed
+
+- Engine (nexus-hxrcm): `POST /v1/catalog/manifest/write_many` no longer
+  fails with `deadlock detected` when two calls on one collection overlap.
+  The metadata-only UPDATE batch orders its row locks by chash, the same
+  fix class as the multi-row INSERT, and the combined-write refresh retries
+  on SQLSTATE 40P01. The metadata-only UPDATE on both write paths now takes
+  the shared sweep gate first, so it waits for a running superseded-chunk
+  sweep or orphan quarantine instead of racing it on a different lock
+  order. Six cloud 500s since the v0.1.104 flip; the client-side symptom
+  was `superseded-chunk sweep skipped ... (sweep_failed)`.
+- Storage-service supervisor (nexus-59bah): the heartbeat takes the
+  per-scope election flock with a budget of one third of the lease TTL
+  instead of blocking on it. A held flock costs one skipped stamp, logged
+  as `service_supervisor_heartbeat_election_busy`, and the next tick
+  retries; a wedged holder can no longer keep the heartbeat loop blocked
+  past the TTL. `publish`, `relinquish`, and the shutdown marker still
+  block, so concurrent first claims serialize into increasing generations.
+- `nx_answer` (nexus-wj12p, nexus-90gyo, nexus-zy0kj): a grown plan whose
+  stored question names different identifiers (RDR ids, bead ids, engine
+  tags, client versions, issue numbers) than the incoming question is no
+  longer matched; the call falls through to the inline planner. A
+  retrieval-only or reduce-less result is classified as a non-answer,
+  recorded `success=False`, never grown, and returned as a
+  `[non-answer: <shape>]` notice carrying the retrieved chunk refs; the
+  envelope gains `answer_shape`. `nx answer-runs` reports the same shapes
+  as `degenerate/non_answer/<shape>` for pre-fix runs too.
+
+### Removed
+
+- `nx index repo --force-stale` and the collection pipeline-version stamp
+  (nexus-ebu0c). Since RDR-155 every collection handle is a service stub
+  with no metadata, so the stamp had been a silent no-op; since
+  nexus-4jj40 the engine skips embedding for unchanged chunk text, so
+  `--force` after a chunker change re-embeds only what the chunker
+  changed. `--force` is the one lever. The `nx doctor` "pipeline versions"
+  row is gone with it.
+
+### Documentation
+
+- README § Updating and Getting Started § Upgrading are cut to the two
+  commands, the do-not-reinstall-with-uv rule, and a pointer for pre-PG
+  installs.
+
 ## [7.33.0] - 2026-09-06
 
 Paired with engine-service-v0.1.105 (`REQUIRED_ENGINE_VERSION` 0.1.105).

README.md

@@ -72,17 +72,24 @@ The `nx` CLI provides direct access to all storage tiers, indexing, search, the
 ## Updating
 
 ```bash
-nx self install                          # 1. update the code — PRESERVES your extras (e.g. [local])
+nx self install                          # 1. update the code (keeps your extras, e.g. [local])
 nx upgrade                               # 2. converge the data
 ```
 
-Upgrading nexus is: update the code, then run `nx upgrade`. That single trigger converges everything else — it brings the package, engine, and process preconditions current, then walks one ordered ladder. The T2-schema and ChromaDB→Postgres+pgvector substrate-move rungs (and the chunk-identity / embedder-era migrations that were co-resident inside the substrate move) retired with the Chroma + client-SQLite migration machinery at RDR-155 P4b; the RDR-180 chash rekey is the ladder's sole remaining data rung today, detecting, converging, and verifying before it records completion, resumable and idempotent, with your existing store left byte-untouched as a rollback target. There is nothing to sequence by hand and no era to know for any install that has already reached the PG substrate (6.0+): `nx doctor` reports the pending rung read-only, `nx upgrade` walks it, and a dormant-but-migrated install converges the same way a current one no-ops. A **pre-PG install** (5.x, or 6.x that never migrated off ChromaDB) is a separate two-hop — the Chroma-era migration machinery retired at RDR-155 P4b, so hop through `conexus==6.18.1` first (`nx upgrade` there migrates ChromaDB → Postgres+pgvector, copy-not-move), then upgrade forward to current; see [Getting Started § Upgrading an existing install](docs/getting-started.md#upgrading-an-existing-install-skip-this-if-this-is-your-first-install) for the exact commands. Rollback is always yours to invoke and never automatic.
+Both steps, every time. Step 1 installs a new generation beside the one you
+are running and repoints `current`; nothing is swapped under a live process,
+so it is safe with Claude Code sessions open and the service up. Step 2
+converges the package, engine, and service, then walks any pending data
+rung. `nx doctor` shows what is pending; `nx upgrade --dry-run` previews.
 
-**Step 1 installs a new generation; it does not replace the one you are running.** `nx self install` builds a fresh tree beside the existing ones under `~/.local/share/nexus/tools/`, repoints the `current` symlink and rewrites the `~/.local/bin` shims. Nothing is swapped underneath a live process, so it always succeeds with Claude Code sessions open, the storage service up, and an `nx index` in flight — those holders keep running from their own tree and converge at their next spawn. The install source and your extras travel in the generation's own receipt, so a `[local]` install stays a `[local]` install. Older generations are reaped once nothing is bound to them (the last three are kept by default; `--keep N` to change that).
+Do not upgrade with `uv tool install conexus` or `--force`: that resets the
+environment and drops `[local]`, which downgrades the embedder and makes
+search return nothing. If you did, `nx self install` repairs it.
 
-**On a box still using the older uv-tool layout, `nx self install` now CONVERGES it** (7.20.0, nexus-gu9zo). It builds a generation beside the existing uv tree, flips `current`, takes over the `~/.local/bin` shims, and registers the old tree so live holders keep running from it until nothing is bound to it. Your extras bridge across from the uv receipt, so a `[local]` install stays `[local]`. Before 7.20.0 the command refused here and pointed at a repo script most users do not have — no packaged install could reach the generation layout at all. `nx doctor`'s *Generation layout* row tells you which layout you are on. On either layout, **do not** upgrade with `uv tool install conexus --force` / `uv tool install conexus`: that *resets* the install and **drops `[local]`**, silently downgrading your embedder from 768-dim to 384-dim, which dimension-mismatches existing 768-dim collections and makes search return nothing. On a uv-tool box, recover with `uv tool install --reinstall "conexus[local]"`. On a generation box, that same command rebuilds a `[local]`-less uv tree beside your install (a plain `uv tool install` leaves the nexus shims alone — "Executable already exists"; `--force` takes them, and then every spawn resolves through uv's tree instead of `current`). Since 7.21.0 this is self-repairing: the next `nx upgrade` (the SessionStart hook runs it) or `nx self install` rewrites the shims back to `current`, registers uv's tree for reap, and — if uv's tree is the newer version, i.e. you meant to upgrade — builds a generation at that version from your own receipt, so `[local]` survives. Never run `uv tool uninstall conexus` on a generation box: it deletes the nexus shims at those paths; a reaped tree is what makes uv refuse to rebuild.
+After `/plugin update`, run both steps so the CLI matches the plugin.
 
-When you update the **Claude Code plugin** (`/plugin update`), run **both** upgrade steps above (`nx self install` then `nx upgrade`) so the CLI stays in lockstep with the plugin version.
+Installs that never left ChromaDB (5.x, or 6.x never migrated) take a
+different path: [Getting Started § Upgrading from a pre-PG install](docs/getting-started.md#upgrading-from-a-pre-pg-install).
 
 ### Something broken?
 

conexus/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "conexus",
-  "version": "7.33.0",
+  "version": "7.34.0",
   "description": "Self-hosted three-tier knowledge management with plan-centric retrieval (nx_answer), specialized agents, semantic search, and RDR decision tracking for Claude Code.",
   "author": {
     "name": "Hal Hildebrand",

conexus/CHANGELOG.md

@@ -4,6 +4,10 @@ All notable changes to the conexus plugin are documented here.
 Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 Versioning follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [7.34.0] - 2026-09-06
+
+- Plugin version aligned with conexus 7.34.0. No plugin-side changes.
+
 ## [7.33.0] - 2026-09-06
 
 - Plugin version aligned with conexus 7.33.0.

conexus/PENDING_RELEASE.md

@@ -29,6 +29,6 @@ mechanize, it matters enough to ship.
 ---
 
 
-## Awaiting the next release or plugin cut (pinned: v7.33.0)
+## Awaiting the next release or plugin cut (pinned: v7.34.0)
 
 (none)

docs/cli-reference.md

@@ -86,8 +86,7 @@ nx index repo ./my-project
 |------|-------------|
 | `--frecency-only` | Update frecency scores only; skip re-embedding (faster, for re-ranking refresh). Mutually exclusive with `--force` |
 | `--re-embed` | Requires `--force`. Also forces a Voyage re-embed of every chunk, even one whose text is unchanged (the pre-nexus-4jj40 `--force` behaviour). Without it, `--force` alone re-chunks and re-sends every file; the server's own existence-partition still skips the billed embed call for a chunk whose text is byte-identical to what is already stored, refreshing only its metadata (e.g. a chunker classification change). Reserve `--re-embed` for a genuine embedding-model change |
-| `--force-stale` | Re-index only if collection pipeline version is outdated (smart force — skips current collections) |
-| `--since-head` | Index only the git delta since the last indexed commit (`owners.head_hash`): changed files re-index, deleted files' docs prune, full-tree passes (staleness pulls, housekeeping, misclassified/orphan prunes, rg cache rebuild) are skipped. Worktree-inclusive. Falls back to a full index when no usable base exists; ignored with `--force`/`--force-stale`. The per-commit hook's fast path |
+| `--since-head` | Index only the git delta since the last indexed commit (`owners.head_hash`): changed files re-index, deleted files' docs prune, full-tree passes (staleness pulls, housekeeping, misclassified/orphan prunes, rg cache rebuild) are skipped. Worktree-inclusive. Falls back to a full index when no usable base exists; ignored with `--force`. The per-commit hook's fast path |
 | `--corpus [docs\|knowledge]` | Corpus routing for auto-classified prose/PDF files (default: `docs`). `docs` routes to `docs__` collections; `knowledge` routes to `knowledge__` collections instead |
 | `--on-locked {skip,wait}` | Behavior under contention (default: `wait`). Per-repo advisory lock (two `nx index repo` on the same repo): `skip` exits immediately, `wait` blocks. Catalog-write fairness (RDR-146): when a foreground interactive catalog write is pending, `skip` defers this run's catalog writes to the next idempotent pass, `wait` proceeds after a bounded yield. `NX_WRITE_PRIORITY=interactive|batch` overrides the tty-based priority of a run's catalog writes. |
 
@@ -3607,6 +3606,20 @@ every row is split three ways:
   - `error` — a plan-execution or binding error before/without any
     completed step.
   - `other` — anything else (harness probes, unclassified rows).
+  - `non_answer/<shape>` (nexus-90gyo / nexus-zy0kj) — reachable at ANY
+    `step_count`, like the nexus-x79ne well-formed shapes: the run
+    retrieved evidence but never reduced it. `<shape>` is one of
+    `hydration_dump` (the body is a `store_get_many` payload),
+    `extractions_only` (a bare `operator_extract` payload),
+    `ranking_only`, `operator_payload` (filter, check, verify or groupby
+    payload), `retrieval_only` (a search/query/traverse result payload),
+    `listing`, `empty`. A row
+    written by a post-fix client carries the `[non-answer: <shape>]`
+    notice as its `final_text` and is named by that prefix; a pre-fix row
+    (the 2026-09-06 run 706 / plan 488 class) is named from its body by
+    the same classifier `nx_answer` uses (`nexus.plans.answer_shape`).
+    Before this class existed these rows counted as executed-ok and the
+    plan-grow path saved them as successes.
 
 `--json` carries `executed_ok_count`, `executed_failed_count`,
 `degenerate_count`, `degenerate_breakdown: {class: count}`, plus a
@@ -3678,6 +3691,22 @@ predicted `usd`/`ms`/`basis`, and which one was chosen are written to
 predicted_cost_usd, basis}`; `None` on any path that never reaches Step
 1's hit branch — force_dynamic, a plan-miss, or an error before Step 1).
 
+The envelope also carries `answer_shape` (nexus-90gyo): `"answered"` when
+`final_text` is a synthesized answer, otherwise one of `hydration_dump`,
+`extractions_only`, `ranking_only`, `operator_payload`, `retrieval_only`, `listing`, `empty`.
+On a non-answer `final_text` is a one-line `[non-answer: <shape>]` notice
+(the raw payload is never returned as prose), the `chunks` list still
+carries what was retrieved, the run is recorded as a failure, and no plan
+is grown from it (nexus-zy0kj). `None` on paths that never classified:
+errors, misses, the single-step fast path, a continuation handoff.
+Grown plans are additionally gated on identifier agreement at match time
+(nexus-wj12p): a grown plan whose originating question named identifiers
+(RDR/JDR ids, bead ids, engine tags, client versions, GH/PR numbers) is
+offered only to an intent naming exactly the same set, so a question
+about RDR-197 can no longer be answered by a plan grown for RDR-176; the
+drop is logged as `plan_match_grown_literal_disagreement_dropped` and
+the call falls through to the inline planner.
+
 ### `--derive-budget` (RDR-196 .p3a, nexus-nyry9.19)
 
 Derives the default `budget_usd` from recorded **post-flip** history and