ciris-server 0.4.4__tar.gz → 0.4.6__tar.gz

{ciris_server-0.4.4 → ciris_server-0.4.6}/Cargo.lock

@@ -530,9 +530,9 @@ checksum = "5e764a1d40d510daf35e07be9eb06e75770908c27d411ee6c92109c9840eaaf7"
 
 [[package]]
 name = "bitcoin_hashes"
-version = "0.14.100"
+version = "0.14.2"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "0c9901a56e133a1fc86eeb1113e2591f45f4682451ca893bff494d2f88918e3f"
+checksum = "4ed83caece3afc59919481b33b472e1432d1abc4641ed9100be142ef5110b406"
 dependencies = [
  "hex-conservative",
 ]
@@ -644,15 +644,15 @@ checksum = "1fd0f2584146f6f2ef48085050886acf353beff7305ebd1ae69500e27c67f64b"
 
 [[package]]
 name = "bytes"
-version = "1.11.1"
+version = "1.12.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "1e748733b7cbc798e1434b6ac524f0c1ff2ab456fe201501e6497c8417a4fc33"
+checksum = "8ae3f5d315924270530207e2a68396c3cc547f6dca3fbdca317cfb1a51edb593"
 
 [[package]]
 name = "camino"
-version = "1.2.2"
+version = "1.2.3"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "e629a66d692cb9ff1a1c664e41771b3dcaf961985a9774c0eb0bd1b51cf60a48"
+checksum = "b4ce8d3bd5823c7504d3f579f13e7b2f3da252fcb938c594d5680ee508bf846f"
 dependencies = [
  "serde_core",
 ]
@@ -812,8 +812,8 @@ dependencies = [
 
 [[package]]
 name = "ciris-crypto"
-version = "5.11.0"
-source = "git+https://github.com/CIRISAI/CIRISVerify?tag=v5.11.0#4495706b4d7d1c28c7143df6e571b95f38512251"
+version = "6.0.0"
+source = "git+https://github.com/CIRISAI/CIRISVerify?tag=v6.0.0#1e894008352a480594adc53c21e6d4a0290862a3"
 dependencies = [
  "ed25519-dalek",
  "hex",
@@ -838,8 +838,8 @@ dependencies = [
 
 [[package]]
 name = "ciris-edge"
-version = "4.5.1"
-source = "git+https://github.com/CIRISAI/CIRISEdge?tag=v4.5.1#0a5db46da97b07a3b41b483f9793eff16bb72ce7"
+version = "4.6.0"
+source = "git+https://github.com/CIRISAI/CIRISEdge?tag=v4.6.0#630d2c7330716927979a4400fc19d86607ecd2f5"
 dependencies = [
  "async-trait",
  "axum",
@@ -890,8 +890,8 @@ dependencies = [
 
 [[package]]
 name = "ciris-keyring"
-version = "5.11.0"
-source = "git+https://github.com/CIRISAI/CIRISVerify?tag=v5.11.0#4495706b4d7d1c28c7143df6e571b95f38512251"
+version = "6.0.0"
+source = "git+https://github.com/CIRISAI/CIRISVerify?tag=v6.0.0#1e894008352a480594adc53c21e6d4a0290862a3"
 dependencies = [
  "aes-gcm",
  "async-trait",
@@ -899,6 +899,7 @@ dependencies = [
  "ciris-crypto",
  "core-foundation 0.9.4",
  "core-foundation-sys",
+ "cryptoki",
  "dirs",
  "ed25519-dalek",
  "hex",
@@ -954,8 +955,8 @@ dependencies = [
 
 [[package]]
 name = "ciris-persist"
-version = "8.8.0"
-source = "git+https://github.com/CIRISAI/CIRISPersist?tag=v8.8.0#7af98862097bd4efc79e67af1991ec52c464db46"
+version = "9.0.0"
+source = "git+https://github.com/CIRISAI/CIRISPersist?tag=v9.0.0#c2ee16518698aeccea6c13b622b5aae22b8967ec"
 dependencies = [
  "async-trait",
  "base64 0.22.1",
@@ -994,7 +995,7 @@ dependencies = [
 
 [[package]]
 name = "ciris-server"
-version = "0.4.4"
+version = "0.4.6"
 dependencies = [
  "anyhow",
  "async-trait",
@@ -1031,8 +1032,8 @@ dependencies = [
 
 [[package]]
 name = "ciris-verify-core"
-version = "5.11.0"
-source = "git+https://github.com/CIRISAI/CIRISVerify?tag=v5.11.0#4495706b4d7d1c28c7143df6e571b95f38512251"
+version = "6.0.0"
+source = "git+https://github.com/CIRISAI/CIRISVerify?tag=v6.0.0#1e894008352a480594adc53c21e6d4a0290862a3"
 dependencies = [
  "android_system_properties",
  "anyhow",
@@ -1052,8 +1053,10 @@ dependencies = [
  "libc",
  "prost",
  "prost-build",
+ "qrcode",
  "rand 0.8.6",
  "reqwest",
+ "rpassword",
  "rusqlite",
  "rustls 0.21.12",
  "rustls 0.23.40",
@@ -1342,6 +1345,28 @@ dependencies = [
  "rand_core 0.10.1",
 ]
 
+[[package]]
+name = "cryptoki"
+version = "0.12.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "ff765b99fc49f3116c9a908484486a2b92fd73c48da45c3a69716471c6cc56c6"
+dependencies = [
+ "bitflags 2.13.0",
+ "cryptoki-sys",
+ "libloading",
+ "log",
+ "secrecy",
+]
+
+[[package]]
+name = "cryptoki-sys"
+version = "0.5.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "f1fd850498411e4057f1cba79e6e2bc7cbe960544c1046ab46d4685c403a1121"
+dependencies = [
+ "libloading",
+]
+
 [[package]]
 name = "ctr"
 version = "0.9.2"
@@ -3261,6 +3286,16 @@ dependencies = [
  "rand 0.9.4",
 ]
 
+[[package]]
+name = "libloading"
+version = "0.8.9"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "d7c4b02199fee7c5d21a5ae7d8cfa79a6ef5bb2fc834d6e9058e89c825efdc55"
+dependencies = [
+ "cfg-if",
+ "windows-link",
+]
+
 [[package]]
 name = "libm"
 version = "0.2.16"
@@ -4481,6 +4516,12 @@ dependencies = [
  "syn 2.0.118",
 ]
 
+[[package]]
+name = "qrcode"
+version = "0.14.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "d68782463e408eb1e668cf6152704bd856c78c5b6417adaee3203d8f4c1fc9ec"
+
 [[package]]
 name = "qrcodegen"
 version = "1.8.0"
@@ -4984,6 +5025,27 @@ dependencies = [
  "rmp",
 ]
 
+[[package]]
+name = "rpassword"
+version = "7.5.4"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "2da316a15f47e3d053de9cb2c439650bd8fa4aaeb9365f2e5f27f492ff73c196"
+dependencies = [
+ "libc",
+ "rtoolbox",
+ "windows-sys 0.61.2",
+]
+
+[[package]]
+name = "rtoolbox"
+version = "0.0.5"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "50a0e551c1e27e1731aba276dbeaeac73f53c7cd34d1bda485d02bd1e0f36844"
+dependencies = [
+ "libc",
+ "windows-sys 0.59.0",
+]
+
 [[package]]
 name = "rusqlite"
 version = "0.31.0"
@@ -5250,6 +5312,15 @@ dependencies = [
  "zeroize",
 ]
 
+[[package]]
+name = "secrecy"
+version = "0.10.3"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "e891af845473308773346dc847b2c23ee78fe442e0472ac50e22a18a93d3ae5a"
+dependencies = [
+ "zeroize",
+]
+
 [[package]]
 name = "secret-service"
 version = "3.1.0"

{ciris_server-0.4.4 → ciris_server-0.4.6}/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "ciris-server"
-version = "0.4.4"   # 0.1 = lens-only (agent ~2.9.7); 0.3 = +auth subsystem / one-wheel; 0.4 = +federation peering/identity (capacity scoring, consent:replication, register_federation_key gate, root-bootstrap, NodeCode); 0.4.1 = self-attested first-run root claim (#887); 0.4.2 = one-time claim PIN; 0.4.3 = CC-compliant ownership (infra:* responsible-party owner-binding, no agency, serve-only-until-owned); 0.4.4 = substrate-native user-signed owner-binding — 1-phase /v1/setup/root + the local node's /v1/setup/claim-remote (client is a node; crypto only in the substrate); 0.5 = +registry (~2.9.8); 1.0 = +node (~2.9.10). Patch forward on breakage.
+version = "0.4.6"   # 0.1 = lens-only (agent ~2.9.7); 0.3 = +auth subsystem / one-wheel; 0.4 = +federation peering/identity (capacity scoring, consent:replication, register_federation_key gate, root-bootstrap, NodeCode); 0.4.1 = self-attested first-run root claim (#887); 0.4.2 = one-time claim PIN; 0.4.3 = CC-compliant ownership (infra:* responsible-party owner-binding, no agency, serve-only-until-owned); 0.4.4 = substrate-native user-signed owner-binding — 1-phase /v1/setup/root + the local node's /v1/setup/claim-remote (client is a node; crypto only in the substrate); 0.5 = +registry (~2.9.8); 1.0 = +node (~2.9.10). Patch forward on breakage.
 edition = "2021"
 # MSRV floor is set by the substrate: ciris-verify v5.2.0 requires 1.86
 # (persist v6.0.1 is 1.83). Build with the higher of the two.
@@ -63,6 +63,15 @@ extension-module = [
     "ciris-persist/extension-module",
     "ciris-edge/extension-module",
 ]
+# `pkcs11` turns on the YubiKey (PKCS#11 / PIV) custody backend for the USER
+# federation identity (`ciris-server identity create --backend pkcs11`). OFF by
+# default: a plain `cargo build` never links `cryptoki`, and the Pkcs11 backend
+# honestly returns NotSupported without it. It flips `ciris-keyring/pkcs11` on
+# (operator hardware; Linux). The YubiKey path is hardware-validated by the
+# operator — there is no token in CI, so it is gated + flagged, not unit-tested.
+# Like the per-target `tpm` posture, it is NOT in `default`; build it explicitly
+# (`--features pkcs11`) on a Linux box with a token attached.
+pkcs11 = ["ciris-keyring/pkcs11"]
 # NOTE: hardware key custody (TPM/SE/StrongBox) is wired per-TARGET below, not as
 # a cargo feature — TPM (tss-esapi) is Linux-only, so a top-level `tpm` feature
 # made `--all-features` drag tss-esapi onto Windows/macOS (where it can't build).
@@ -101,16 +110,18 @@ ciris-lens-core     = { path = "crates/ciris-lens-core" } # ABSORBED in-tree (wo
 # `cirislens_wa_cert` + `cirislens_service_token_revocation` expose the auth
 # substrate the fabric absorbs (CIRISServer#9, src/auth): the agent's `wa_cert`
 # table (users/WA/OAuth/api-keys) + the `revoked_service_tokens` table.
-ciris-persist     = { git = "https://github.com/CIRISAI/CIRISPersist", tag = "v8.8.0", features = ["sqlite", "cirislens_wa_cert", "cirislens_service_token_revocation"] }
-ciris-edge        = { git = "https://github.com/CIRISAI/CIRISEdge", tag = "v4.5.1", features = ["transport-reticulum", "transport-http"] }
+ciris-persist     = { git = "https://github.com/CIRISAI/CIRISPersist", tag = "v9.0.0", features = ["sqlite", "cirislens_wa_cert", "cirislens_service_token_revocation"] }
+ciris-edge        = { git = "https://github.com/CIRISAI/CIRISEdge", tag = "v4.6.0", features = ["transport-reticulum", "transport-http"] }
 # Founder-quorum verification + key-id fingerprint at the composition root
 # (threshold:: module path — NOT re-exported at the crate root).
-ciris-verify-core = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v5.11.0" }
+# v6.0.0 (NOT v6.1.0): persist v9.0.0 transitively pins verify v6.0.0; pinning
+# v6.1.0 produces two ciris_verify_core crates with incompatible ThresholdMember.
+ciris-verify-core = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v6.0.0" }
 # Hardware-backed transport-identity keystore (verify v5.2.0 #68 / edge #99).
 # Base = software keystore + byte-identical migration of an existing .rid (works
 # everywhere, no libtss2). The real TPM-2.0 / SE / StrongBox backend rides the
 # `tpm` feature; runtime auto-detects hardware and falls back to software.
-ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v5.11.0", version = "5", features = ["software", "pqc-ml-dsa"] }
+ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v6.0.0", version = "6", features = ["software", "pqc-ml-dsa"] }
 
 # PyO3 bindings for the abi3 wheel — optional, gated behind the `python` feature
 # so the binary never links them. 0.29 matches the persist/edge family floor.
@@ -162,13 +173,13 @@ tracing-subscriber = { version = "0.3", features = ["env-filter", "json"] }
 # - keyring `tpm` (tss-esapi / TPM 2.0) — the real hardware backend; needs
 #   libtss2 (Linux build dep). Other targets keep the software keystore.
 [target.'cfg(target_os = "linux")'.dependencies]
-ciris-persist = { git = "https://github.com/CIRISAI/CIRISPersist", tag = "v8.8.0", features = ["postgres", "cirislens_wa_cert", "cirislens_service_token_revocation"] }
-ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v5.11.0", version = "5", features = ["tpm"] }
+ciris-persist = { git = "https://github.com/CIRISAI/CIRISPersist", tag = "v9.0.0", features = ["postgres", "cirislens_wa_cert", "cirislens_service_token_revocation"] }
+ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v6.0.0", version = "6", features = ["tpm"] }
 
 # Android (arm64/arm32/x86_64): the keyring `android` backend (JNI → Android
 # Keystore/StrongBox); sqlite bundles, no postgres/tpm. Mirrors persist/edge.
 [target.'cfg(target_os = "android")'.dependencies]
-ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v5.11.0", version = "5", features = ["android"] }
+ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v6.0.0", version = "6", features = ["android"] }
 
 # Test-only — the two-node replication integration test (tests/replication.rs)
 # builds + signs CEG batches with the same primitives persist verifies against.
@@ -183,14 +194,14 @@ criterion     = { version = "0.5", features = ["async_tokio"] }
 # The PQC primitives the realtime-A/V E2E bench drives directly: hybrid KEX
 # (X25519 + ML-KEM-768) for the per-Link transit key, AES-256-GCM for the
 # two-layer chunk seal. Same pin/features edge composes (tag parity).
-ciris-crypto  = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v5.11.0", version = "5", features = ["hybrid-kex", "aes-gcm", "pqc-ml-dsa"] }
+ciris-crypto  = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v6.0.0", version = "6", features = ["hybrid-kex", "aes-gcm", "pqc-ml-dsa"] }
 # Enable edge's OWN fountain codec (`codec-fountain`, L1-A) for the survival-floor
 # proof — dev/test ONLY (feature unification applies to test/bench builds; the
 # shipped wheel stays codec-free, since a relay forwards sealed symbols opaquely
 # and never encodes/decodes). This lets tests/chaos_mesh.rs exercise the SUBSTRATE
 # codec (`fountain_encode`/`fountain_decode`) directly — a real MEASURED proof,
 # not a reference stand-in.
-ciris-edge    = { git = "https://github.com/CIRISAI/CIRISEdge", tag = "v4.5.1", features = ["codec-fountain"] }
+ciris-edge    = { git = "https://github.com/CIRISAI/CIRISEdge", tag = "v4.6.0", features = ["codec-fountain"] }
 
 # PQC realtime-A/V streaming E2E benchmark (CIRISEdge#62 realtime_av profile).
 [[bench]]

{ciris_server-0.4.4 → ciris_server-0.4.6}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ciris-server
-Version: 0.4.4
+Version: 0.4.6
 License-File: LICENSE
 Summary: The fabric node — the federation's headless cohabitation runtime (registry + lens [+ node] over one shared substrate), as the abi3 wheel CIRISAgent consumes. agent = fabric node + brain.
 Author-email: Eric Moore <eric@ciris.ai>
@@ -57,18 +57,28 @@ them. The handles (MISSION §3.4):
 
 - **Substrate handles** — the node's federation identity (`/v1/identity`),
   federation-directory reads, content fetch, replication / health.
-- **Fabric handles** — the per-role × per-axis **trust/consent toggles**,
+- **Fabric handles** — **federation-identity minting** (a hardware-rooted, YubiKey-
+  or TPM/SE-sealed user identity → a `CIRIS-V2-` *fedcode*), **node ownership**
+  (claim a node with its **NodeCode** + one-time PIN; the responsible owner-binding
+  is `infra:*`, never agency), the per-role × per-axis **trust/consent toggles**,
   **trust-graph management** (untrust, re-root, create/join groups),
-  **canonical-group membership + voting**, **self/family occurrence
-  attachment**, and the **NodeCode** QR-able peer-bootstrap shorthand.
-
-Those handles are consumed by **rich clients** — [CIRISPortal](https://github.com/CIRISAI/CIRISPortal)
-and [CIRISNode](https://github.com/CIRISAI/CIRISNode), and **chiefly the
-[CIRISAgent](https://github.com/CIRISAI/CIRISAgent) client**, the Kotlin
-Multiplatform (KMP) UI through which most people meet the fabric. The
-infrastructure that *holds* the audit corpus is the surface that *publishes* it
-(redacted PDMA logs / WBD tickets / attestation reads, per the Accord's
-transparency requirement).
+  **canonical-group membership + voting**, **self/family occurrence attachment**,
+  and **consent-object** setup between peers (`consent:replication`).
+
+Those handles are consumed by **rich clients**. Just like CIRISAgent, CIRISServer
+can run **fully headless** (the `ciris-server` binary + a CLI: e.g. `ciris-server
+identity create --backend pkcs11` mints a YubiKey-backed federation ID) **and** it
+exposes a **rich client** — **the same [CIRISAgent](https://github.com/CIRISAI/CIRISAgent)
+Kotlin-Multiplatform app, minus the agent (brain) cards.** The app *is a node*: it
+runs a local fabric node and drives it (all crypto stays in the substrate, never
+in the UI). It surfaces the **fabric cards** — create-your-federation-ID (mint the
+hardware-rooted ID from the desktop app), claim-a-node (NodeCode + PIN), the
+consent-objects card, the node switcher, and the holonomic scoreboard — **without**
+the reasoning/chat cards an agent adds. (Other rich clients:
+[CIRISPortal](https://github.com/CIRISAI/CIRISPortal),
+[CIRISNode](https://github.com/CIRISAI/CIRISNode).) The infrastructure that *holds*
+the audit corpus is the surface that *publishes* it (redacted PDMA logs / WBD
+tickets / attestation reads, per the Accord's transparency requirement).
 
 ## What it replaces
 
@@ -93,6 +103,11 @@ CIRISAgent.
 ```sh
 pip install ciris-server      # the PyO3 abi3 wheel (or build the binary: cargo build --release)
 ciris-server                  # boots a zero-setup node — mode=server, trusts ciris-canonical, no wizard
+                              # on a fresh (unclaimed) node it prints its NodeCode + one-time claim PIN
+
+# Headless: mint a hardware-rooted federation ID (or do it from the desktop app)
+ciris-server identity create --backend pkcs11   # YubiKey-backed; --backend platform-sealed (TPM/SE) | software (dev)
+                                                # prints your CIRIS-V2- fedcode + key_id
 ```
 
 Defaults need no setup: data under `$CIRIS_HOME`, SQLite corpus (Postgres via

{ciris_server-0.4.4 → ciris_server-0.4.6}/README.md

@@ -46,18 +46,28 @@ them. The handles (MISSION §3.4):
 
 - **Substrate handles** — the node's federation identity (`/v1/identity`),
   federation-directory reads, content fetch, replication / health.
-- **Fabric handles** — the per-role × per-axis **trust/consent toggles**,
+- **Fabric handles** — **federation-identity minting** (a hardware-rooted, YubiKey-
+  or TPM/SE-sealed user identity → a `CIRIS-V2-` *fedcode*), **node ownership**
+  (claim a node with its **NodeCode** + one-time PIN; the responsible owner-binding
+  is `infra:*`, never agency), the per-role × per-axis **trust/consent toggles**,
   **trust-graph management** (untrust, re-root, create/join groups),
-  **canonical-group membership + voting**, **self/family occurrence
-  attachment**, and the **NodeCode** QR-able peer-bootstrap shorthand.
-
-Those handles are consumed by **rich clients** — [CIRISPortal](https://github.com/CIRISAI/CIRISPortal)
-and [CIRISNode](https://github.com/CIRISAI/CIRISNode), and **chiefly the
-[CIRISAgent](https://github.com/CIRISAI/CIRISAgent) client**, the Kotlin
-Multiplatform (KMP) UI through which most people meet the fabric. The
-infrastructure that *holds* the audit corpus is the surface that *publishes* it
-(redacted PDMA logs / WBD tickets / attestation reads, per the Accord's
-transparency requirement).
+  **canonical-group membership + voting**, **self/family occurrence attachment**,
+  and **consent-object** setup between peers (`consent:replication`).
+
+Those handles are consumed by **rich clients**. Just like CIRISAgent, CIRISServer
+can run **fully headless** (the `ciris-server` binary + a CLI: e.g. `ciris-server
+identity create --backend pkcs11` mints a YubiKey-backed federation ID) **and** it
+exposes a **rich client** — **the same [CIRISAgent](https://github.com/CIRISAI/CIRISAgent)
+Kotlin-Multiplatform app, minus the agent (brain) cards.** The app *is a node*: it
+runs a local fabric node and drives it (all crypto stays in the substrate, never
+in the UI). It surfaces the **fabric cards** — create-your-federation-ID (mint the
+hardware-rooted ID from the desktop app), claim-a-node (NodeCode + PIN), the
+consent-objects card, the node switcher, and the holonomic scoreboard — **without**
+the reasoning/chat cards an agent adds. (Other rich clients:
+[CIRISPortal](https://github.com/CIRISAI/CIRISPortal),
+[CIRISNode](https://github.com/CIRISAI/CIRISNode).) The infrastructure that *holds*
+the audit corpus is the surface that *publishes* it (redacted PDMA logs / WBD
+tickets / attestation reads, per the Accord's transparency requirement).
 
 ## What it replaces
 
@@ -82,6 +92,11 @@ CIRISAgent.
 ```sh
 pip install ciris-server      # the PyO3 abi3 wheel (or build the binary: cargo build --release)
 ciris-server                  # boots a zero-setup node — mode=server, trusts ciris-canonical, no wizard
+                              # on a fresh (unclaimed) node it prints its NodeCode + one-time claim PIN
+
+# Headless: mint a hardware-rooted federation ID (or do it from the desktop app)
+ciris-server identity create --backend pkcs11   # YubiKey-backed; --backend platform-sealed (TPM/SE) | software (dev)
+                                                # prints your CIRIS-V2- fedcode + key_id
 ```
 
 Defaults need no setup: data under `$CIRIS_HOME`, SQLite corpus (Postgres via

{ciris_server-0.4.4 → ciris_server-0.4.6}/crates/ciris-lens-core/Cargo.toml

@@ -26,8 +26,8 @@ crate-type = ["cdylib", "rlib"]
 #
 # OQ-01 closure 2026-05-03: rlib primary, PyO3 cdylib via `python`
 # feature for the deployed-lens cutover.
-ciris-persist = { git = "https://github.com/CIRISAI/CIRISPersist", tag = "v8.8.0", version = "8", features = ["extract", "sqlite"] }
-ciris-edge    = { git = "https://github.com/CIRISAI/CIRISEdge",    tag = "v4.5.1", version = "4", features = ["transport-http", "transport-reticulum"] }
+ciris-persist = { git = "https://github.com/CIRISAI/CIRISPersist", tag = "v9.0.0", version = "9", features = ["extract", "sqlite"] }
+ciris-edge    = { git = "https://github.com/CIRISAI/CIRISEdge",    tag = "v4.6.0", version = "4", features = ["transport-http", "transport-reticulum"] }
 
 # Keyring — relay mode (CIRISLensCore#10) loads its Edge transport-
 # signing identity via `ciris_keyring::load_local_seed`. Edge's
@@ -37,7 +37,7 @@ ciris-edge    = { git = "https://github.com/CIRISAI/CIRISEdge",    tag = "v4.5.1
 # CIRISVerify tag persist + edge pin (v5.0.0 — CEG 1.0 / Agent 3.0 substrate
 # release; MAJOR 4→5 but additive for lens-core) — single verify version.
 # features mirror edge's keyring pin exactly.
-ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v5.11.0", version = "5", features = ["software", "pqc-ml-dsa"] }
+ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v6.0.0", version = "6", features = ["software", "pqc-ml-dsa"] }
 
 # persist's `sqlite` feature: relay mode persists inbound batches via
 # `Engine::receive_and_persist` + reads `Engine::sqlite_backend()` for