ciris-server 0.2.6__tar.gz → 0.4.0__tar.gz

{ciris_server-0.2.6 → ciris_server-0.4.0}/.github/workflows/bench.yml

@@ -52,9 +52,13 @@ jobs:
         with:
           python-version: "3.12"
       - name: Run benches (criterion)
-        run: cargo bench --bench pqc_av_streaming --bench replication_ingest --bench alm_chain
+        run: cargo bench --bench pqc_av_streaming --bench replication_ingest --bench alm_chain --bench stream_fanout
       - name: Generate holonomic scoreboard (CIRISServer#12/#13)
-        run: cargo run --release --quiet -- scoreboard > scoreboard.json
+        # Pass the criterion dir so the substrate tier is promoted to MEASURED from
+        # the real bench numbers above ("numbers through the fabric"); metrics with
+        # no bench (mls_commit/cold-join, the holonomic tier) stay honestly gated.
+        # Publish-only — not a pass/fail gate (shared runners are noisy).
+        run: cargo run --release --quiet -- scoreboard --criterion-dir target/criterion > scoreboard.json
       - name: Generate interpreted page
         run: |
           BENCH_DATE="$(date -u +%Y-%m-%d)" \

{ciris_server-0.2.6 → ciris_server-0.4.0}/.github/workflows/ci.yml

@@ -46,6 +46,16 @@ jobs:
       # `extension-module` (libpython-no-link) into the test binary.
       - run: cargo clippy --all-targets -- -D warnings
       - run: cargo test
+      # The NOISE FLOOR proof (CIRISServer#14, CEG §19.7 / §19.3 N5) — provable
+      # individual-unrecoverability for erasure compliance, run explicitly so the
+      # MEASURED residual-fidelity numbers land in the CI log (Linux only — one
+      # canonical record; the test also runs on every OS via `cargo test` above).
+      # The three gated cases: (a) revocation ⇒ EjectHardDelete leaves NO
+      # recoverable tier, (b) the measured noise floor below n_source symbols,
+      # (c) N→1 aggregation erases the individual below the 1/N gist bound.
+      - name: Noise floor proof (MEASURED, Linux)
+        if: runner.os == 'Linux'
+        run: cargo test --test noise_floor -- --nocapture
       # The PyO3 wheel surface (Linux only; libpython linked, no extension-module).
       - name: clippy (python surface, Linux)
         if: runner.os == 'Linux'

{ciris_server-0.2.6 → ciris_server-0.4.0}/.github/workflows/publish-pypi.yml

@@ -243,3 +243,7 @@ jobs:
           packages-dir: dist/
           # Trusted Publishing: no `password:` — the OIDC identity is verified
           # against the publisher registered on PyPI.
+          # Idempotent re-cuts: if a tag is re-cut onto a new commit, the wheels
+          # for any platform already on PyPI are skipped instead of 400-ing the
+          # whole upload — a clean re-cut publishes only the newly-built files.
+          skip-existing: true

{ciris_server-0.2.6 → ciris_server-0.4.0}/.github/workflows/release.yml

@@ -38,19 +38,26 @@ jobs:
   build-native:
     name: Build (${{ matrix.target }})
     runs-on: ${{ matrix.os }}
+    # Allowed-to-fail lanes (the TPM backend can't cross-compile) never block the
+    # release; see the armv7 entry + the build-musl job.
+    continue-on-error: ${{ matrix.allow_fail || false }}
     strategy:
       fail-fast: false
       matrix:
         include:
           - os: ubuntu-latest
             target: x86_64-unknown-linux-gnu
-          - os: ubuntu-latest
+          # ARM64 builds NATIVELY on an ARM runner (apt libtss2-dev applies) —
+          # cross-compiling tss-esapi from x86 has no target libtss2.
+          - os: ubuntu-24.04-arm
             target: aarch64-unknown-linux-gnu
-            cross: true
-          # ARM32 — Raspberry Pi / embedded mesh nodes.
+          # ARM32 — Raspberry Pi / embedded mesh nodes. Cross-builds the TPM
+          # backend with no target libtss2 → allowed-to-fail (CIRISServer#7);
+          # never blocks the release.
           - os: ubuntu-latest
             target: armv7-unknown-linux-gnueabihf
             cross: true
+            allow_fail: true
           - os: macos-latest
             target: x86_64-apple-darwin
           - os: macos-latest
@@ -134,6 +141,9 @@ jobs:
   build-musl:
     name: Build (aarch64 musl)
     runs-on: ubuntu-latest
+    # zigbuild cross can't satisfy the TPM backend's target libtss2 — allowed to
+    # fail so it never blocks the release (aarch64-gnu native covers ARM64 Linux).
+    continue-on-error: true
     steps:
       - uses: actions/checkout@v4
       - uses: dtolnay/rust-toolchain@stable
@@ -170,6 +180,10 @@ jobs:
   create-release:
     name: Create Release
     needs: [build-native, build-musl]
+    # Run as long as the build stage finished (not cancelled) — the allowed-to-fail
+    # ARM lanes (armv7 cross, aarch64 musl) must not skip the release; it ships
+    # whatever built (x86_64 linux/mac/win + aarch64-linux-gnu native).
+    if: ${{ !cancelled() }}
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4

{ciris_server-0.2.6 → ciris_server-0.4.0}/CHANGELOG.md

@@ -4,6 +4,75 @@ All notable changes to CIRISServer. Format follows [Keep a Changelog](https://ke
 this project uses [Semantic Versioning](https://semver.org/). The minor line tracks
 the fabric-node scope (0.1 lens · 0.5 +registry · 1.0 +node), paced by the CIRISAgent train.
 
+## [0.3.1] — 2026-06-17
+
+Substrate floor → **persist v8.6.0 / edge v4.5.0 / verify-family v5.11.0** —
+the §19.7 forever-memory cross-impl loop closed: `EjectAggregatedTierOnly`
+tier-granular eviction + the unified `EjectionVerdict` surface (edge v4.5.0 ↔
+verify v5.11.0 ↔ persist v8.6.0). Additive; build + full test suite green
+(25 lib + lens-core 352 + integration), no composition-root change.
+
+## [0.3.0] — 2026-06-16
+
+The integrated fabric node: the **auth subsystem** absorbed, the **one-wheel**
+re-export surface, and the substrate on the **v8.4.0 / v4.3.0 / v5.10.0** floor.
+This is the node we replace the deployed CIRISLens with (and the wheel CIRISAgent
+adopts to drop its lens-core + its own auth).
+
+### Added
+- **Auth subsystem (`src/auth/`, CIRISServer#9) — the fabric is the single auth
+  authority.** The agent's entire user/WA/OAuth/api-key/service-token surface
+  already lived in one persist table (`wa_cert`), so this is a Python→Rust port
+  over the same rows — **no schema fork, 0 conflicts** (`src/auth/ABSORPTION.md`:
+  33 capabilities mapped). One `x-ciris-*` hybrid request verifier (accepts the
+  identity **or** any admitted occurrence — the consenting user *and* the
+  generating agent are both valid signers); **self-at-login** (§8.1.12.7) as the
+  login ceremony; OAuth front-door (providers/login/callback + native
+  google/apple); sessions/token issuer (replaces OAuth→WA→JWT); the CEG role-set
+  **plus** the agent's `UserRole`/`Permission` model verbatim; api-keys +
+  service-token revocation; attestation; user-signed **consent**; and CEG-native
+  **erasure** (GDPR Art. 17 in-app path → `Engine::evict_actor`). Password KDF,
+  native-token JWKS, and root-signature verification are byte-compatible with the
+  agent's own crypto (verified against agent-produced vectors).
+- **One-wheel re-export (CIRISServer#4):** `ciris_server` re-hosts the persist /
+  edge / lens Python surfaces under one `.so` (one PyO3 type registry —
+  `ciris_server.Engine is ciris_server.persist.Engine`), so CIRISAgent consumes a
+  single wheel and the cross-wheel type-identity bug class (CIRISPersist#109)
+  cannot occur. (`reset_engine` / `init_edge_runtime` re-export hooks pending
+  upstream: CIRISPersist#231, CIRISEdge#156; `ciris-verify` stays a standalone
+  ctypes wheel.)
+- **Noise-floor compliance bench (CIRISServer#14, `tests/noise_floor.rs`):**
+  measured individual-unrecoverability — revocation → hard-delete, the
+  reconstruction cliff at the fountain floor, aggregation-is-erasure.
+- **The fabric app (`app/`, CIRISServer#15):** the CIRISAgent KMP mesh app minus
+  agent cards (identity slice proven; governance/safety surfaces).
+
+### Changed
+- Substrate floor → **persist v8.4.0 / edge v4.3.0 / verify-family v5.10.0** (the
+  §19.7 erasure primitives + `wa_cert` auth substrate).
+
+### Validated
+- **Behavior-correct drop-in proof (`qa/`, `FSD/QA_AGAINST_RUST.md`).** The agent's
+  own Python QA-runner module definitions are run unmodified against a live Rust
+  `ciris-server`: **12/12 fabric-route tests pass, 0 gaps** — including the
+  load-bearing byte-compat proof that a password hash produced by the agent's own
+  `cryptography.PBKDF2HMAC` authenticates against the Rust `verify_password`. The
+  ~30 agent-brain modules are correctly N/A on a headless fabric node. The QA
+  runner stays Python (it is HTTP-driving conformance, not ported).
+
+### Fixed
+- **api-keys / service-token routes are now authz-gated.** `POST/GET/DELETE
+  /v1/auth/api-keys*` and `/v1/auth/service-token/revoke` now require a live
+  session bearer whose role carries `manage_user_permissions` (matching the
+  agent's gate) — the one residual the conformance run surfaced.
+
+### Notes
+- Companion: **CIRISStatus** becomes a fabric monitoring node (Flows A/B +
+  `health:liveness` `scores` + website sockets).
+- GDPR erasure is **both** entry points: the DSAR endpoint on the monitor node
+  **and** the in-app CEG-native `withdraws`. Full lens decommission stays gated on
+  the DSAR-via-status endpoint landing (keep the Python DSAR reachable until then).
+
 ## [0.2.6] — 2026-06-16
 
 Substrate floor → **v4.2.0 family** + the **multi-tier ALM relay chain** test