ciris-server 0.5.181__tar.gz → 0.5.182__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Potentially problematic release.
This version of ciris-server might be problematic. Click here for more details.
- {ciris_server-0.5.181 → ciris_server-0.5.182}/.github/workflows/bench.yml +20 -1
- {ciris_server-0.5.181 → ciris_server-0.5.182}/.github/workflows/build-wheels.yml +9 -1
- {ciris_server-0.5.181 → ciris_server-0.5.182}/.github/workflows/ci.yml +32 -2
- {ciris_server-0.5.181 → ciris_server-0.5.182}/.github/workflows/conformance.yml +20 -1
- {ciris_server-0.5.181 → ciris_server-0.5.182}/.github/workflows/mesh-harness.yml +12 -1
- {ciris_server-0.5.181 → ciris_server-0.5.182}/.github/workflows/release.yml +20 -1
- {ciris_server-0.5.181 → ciris_server-0.5.182}/Cargo.lock +20 -19
- {ciris_server-0.5.181 → ciris_server-0.5.182}/Cargo.toml +14 -14
- {ciris_server-0.5.181 → ciris_server-0.5.182}/PKG-INFO +2 -2
- {ciris_server-0.5.181 → ciris_server-0.5.182}/README.md +1 -1
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/Cargo.toml +5 -5
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/role/ret_relay.rs +47 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/evidence/CIRISServer.cc_impl.tsv +8 -8
- {ciris_server-0.5.181 → ciris_server-0.5.182}/scripts/verify_release_surface.sh +31 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/oauth.rs +49 -5
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/oauth_link.rs +115 -3
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/store.rs +110 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/compose.rs +48 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/federation_delivery.rs +34 -2
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/operator_surface.rs +99 -3
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/capacity_scorer.rs +14 -14
- ciris_server-0.5.182/tests/egress_scrub_is_not_at_rest.rs +314 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/nat_traversal.rs +16 -0
- ciris_server-0.5.182/tests/oauth_state_matrix.rs +781 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/one_author_per_row.rs +18 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/release_gates/substrate.rs +9 -4
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/substrate_contract_gate.rs +9 -3
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/support/log_capture.rs +25 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/.cargo/config.toml +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/.claude/workflows/localize-ui.js +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/.github/workflows/client-artifacts.yml +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/.github/workflows/export-pipeline-pubkeys.yml +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/.github/workflows/ios-asset.yml +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/.github/workflows/localization.yml +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/.github/workflows/publish-pypi.yml +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/.gitignore +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/BUILDING_A_LOCAL_WHEEL.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/CHANGELOG.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/CONTRIBUTING.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/GOVERNANCE.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/LICENSE +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/MISSION.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/SECURITY.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/WIRE_VOCABULARY_KINDS.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/bench-site/bench_results.json +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/bench-site/index.html +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/bench_results.json +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/benches/alm_chain.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/benches/erasure_survival.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/benches/n_eff_scoring.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/benches/pqc_av_streaming.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/benches/replication_ingest.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/benches/sig_overhead.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/benches/stream_fanout.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/.github/workflows/bench.yml +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/.github/workflows/ci.yml +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/.gitignore +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/.pre-commit-config.yaml +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/FSD/CIRIS_LENS_CORE.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/FSD/LENS_CORE_V0_5.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/FSD/OPEN_QUESTIONS.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/LICENSE +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/MISSION.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/README.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/benches/aggregate.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/benches/canonicalize.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/benches/project.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/deny.toml +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/docs/BENCHMARKS.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/docs/COHABITATION.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/docs/PRE_COMMIT.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/docs/PUBLIC_SCHEMA_CONTRACT.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/docs/PYPI_PUBLISH.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/docs/RELEASE_NOTES.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/docs/STANDARDS_COMPARISON.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/docs/THREAT_MODEL.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/patterns_from_cirislens_core/extraction/json_path.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/patterns_from_cirislens_core/extraction/metadata.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/patterns_from_cirislens_core/extraction/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/patterns_from_cirislens_core/scrubber/distilbert_loader.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/patterns_from_cirislens_core/scrubber/fields.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/patterns_from_cirislens_core/scrubber/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/patterns_from_cirislens_core/scrubber/ner.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/patterns_from_cirislens_core/scrubber/ort_loader.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/patterns_from_cirislens_core/scrubber/proptests.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/patterns_from_cirislens_core/scrubber/regex.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/patterns_from_cirislens_core/scrubber/walker.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/patterns_from_cirislens_core/scrubber/xlm_r_loader.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/pyproject.toml +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/python/ciris_lens_core/__init__.py +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/audit/api.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/audit/delegate.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/audit/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/audit/pyo3.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/canonical/ceg_egress.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/canonical/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/capacity/attestation.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/capacity/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/capacity/score.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/capture/batch.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/capture/client.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/capture/consent.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/capture/correlation.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/capture/event.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/capture/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/capture/partial.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/capture/py_engine.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/capture/seal.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/cohort/declared.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/cohort/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/cohort/resourcing.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/config/egress.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/config/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/config/node.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/config/retention.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/config/upstream.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/detector/axis_metrics.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/detector/coherence_ratchet.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/detector/correlated_action.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/detector/distributive_access.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/detector/manifold.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/detector/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/extract/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/extract/projection.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/ffi/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/ffi/pyo3.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/key_id.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/lib.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/observability/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/pipeline/lifecycle.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/pipeline/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/retention/eviction.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/retention/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/retention/summary.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/role/handler.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/role/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/role/node.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/role/relay.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/scores/aggregate.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/scores/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/scores/oracle.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/scoring/assembly.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/scoring/axis_calibration.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/scoring/calibration.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/scoring/capacity.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/scoring/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/scoring/n_eff.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/scoring/result.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/signing/event.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/signing/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/wire/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/src/wire/signer.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/tests/parity/README.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/tests/parity/canonical_fixtures.json +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/tests/parity/generate_canonical_fixtures.py +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/crates/ciris-lens-core/tests/sovereign_rlib.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/data/live_mesh_2026-06-22.json +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/docs/SCOPE_PRIVACY.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/evidence/README.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/evidence/blocked_upstream.tsv +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/evidence/cc_compliance_map.tsv +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/evidence/cc_impl.tsv +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/examples/mesh_propagation/main.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/examples/qa_runner/accord.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/examples/qa_runner/canonical.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/examples/qa_runner/common.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/examples/qa_runner/family.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/examples/qa_runner/main.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/examples/qa_runner/verify.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/examples/test_anchor_env.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/.gitignore +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/Dockerfile +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/README.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/agent_boot.py +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/docker-compose.353.yml +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/docker-compose.configured.yml +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/docker-compose.field.yml +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/docker-compose.genesis.yml +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/docker-compose.load.yml +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/docker-compose.traceflow.yml +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/docker-compose.unblessed.yml +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/docker-compose.yml +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/lib/harness.sh +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/pack_wheel.py +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/probe.sh +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/run.sh +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/run_353.sh +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/run_configured.sh +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/run_embedded.sh +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/run_field_sweep.sh +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/run_lifecycle.sh +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/run_load_repro.sh +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/run_scenario.sh +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/run_traceflow.sh +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/run_traceflow2.sh +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/scenarios/genesis_seed.sh +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/harness/mesh-repro/scenarios/traceflow.sh +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/installers/windows/README.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/installers/windows/bundle-jre.ps1 +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/installers/windows/ciris-server-entry.py +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/installers/windows/ciris-server-installer.iss +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/installers/windows/ciris-server.spec +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/pyproject.toml +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/python/ciris_server/__init__.py +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/python/ciris_server/__main__.py +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/python/ciris_server/cli.py +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/python/ciris_server/desktop_launcher.py +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/rust-toolchain.toml +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/scripts/bench_report.py +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/scripts/preflight.sh +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/scripts/sync-client-version.sh +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/scripts/with_test_postgres.sh +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/accord.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/accord_custody.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/accord_duty.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/accord_halt.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/accord_pki/yubico_attestation_root_1.der +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/accord_pki/yubico_attestation_root_1.pem +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/accord_provision.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/accord_reactivate.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/accord_release.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/adapter.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/admin_ops.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/attest.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/ABSORPTION.md +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/api_keys.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/attestation.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/bootstrap.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/consent.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/device_auth.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/device_grant.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/erasure.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/gate.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/loopback.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/occurrence.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/ownership.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/portable_occurrence.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/refusal.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/roles.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/self_login.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/session.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/auth/verify.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/backend.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/benchmarks/bench_results.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/benchmarks/mesh.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/benchmarks/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/benchmarks/scoreboard.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/claim_remote.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/commons_surface.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/compliance.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/compose_policy.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/compose_status.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/config.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/config_api.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/config_reconcile.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/conformance.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/delegation_transparency.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/deployment.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/equivocation.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/family.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/federation_admin.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/federation_nodecode.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/federation_peers.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/federation_surface.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/field_conformance.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/graph_config.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/hardware_attestation.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/health.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/holonomic.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/http_log.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/identity.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/identity_gate.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/ids.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/import.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/ingest_http.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/key_standing.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/lib.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/location.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/main.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/memory_api.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/mesh_config_effect.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/mesh_config_surface.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/mesh_genesis.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/mesh_relay.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/node_control.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/node_identity.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/nodecode.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/operations_catalogue.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/peer.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/proxy.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/py_adapter.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/quorum.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/radio.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/receive_axis.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/replication_reconcile.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/retention_loop.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/safety/age.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/safety/infohazard.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/safety/mod.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/safety/moderation.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/safety/named.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/safety/watchlist.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/scorer/n_eff.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/scorer.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/scrub.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/self_identity.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/sign_object.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/system_data.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/telemetry_logs.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/test_bless.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/trace_plane_watch.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/trust_root_api.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/vocabulary_surface.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/withdraws_arbitrage.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/src/yubico_attestation_ca.pem +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/abuse_surface.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/accord.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/accord_admit_node.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/accord_duty_grant.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/admin_ops.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/alm_chain.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/audit_chain.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/auth_backend_is_not_sqlite_only.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/authorization_digest_is_stable_under_co_scrub.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/av_spine_e2e.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/backend_parity.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/blocked_upstream_gate.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/capacity_self_revocation_pin.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/ceg_graph_projection.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/ceremony_preflight.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/chaos_mesh.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/claim_pin_file_is_declared.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/claim_remote.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/commons_surface.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/compliance_map.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/compose_policy.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/compose_policy_manifest_arms.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/config_cohort_scope.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/config_reconcile.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/conformance_gate.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/coscrub_binds_its_subject.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/cross_target_deps.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/delivery_round_diagnostics.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/device_grant.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/duty_scopes_match_the_substrate.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/egress_scrub.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/egress_scrub_python_door.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/envelope_vocabulary_single_source.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/equivocation.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/federation_admin.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/federation_key_id.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/federation_peers_announced.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/federation_peers_sideband.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/federation_session_kex.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/federation_tier_admission_witness.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/field_conformance.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/first_run_to_moderation_e2e.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/fold_consent_surface.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/folded_health.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/genesis_bundle_validate.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/genesis_seed_save.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/graph_config.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/hardware_class_admission.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/health_contract_hashes.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/health_names_the_node.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/ingest_http.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/keyset_inspection.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/localization_bundle_shape.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/localization_gate.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/login_identifier.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/login_name_is_not_a_choice.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/logout_ends_the_session_not_the_owner.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/mesh_config_consumers.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/mesh_config_surface.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/mesh_seed_e2e.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/mesh_seed_keyplane_e2e.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/no_key_material_is_copied.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/nodecode.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/noise_floor.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/noise_floor_verdicts.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/oauth_redirect_uri_is_served.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/oauth_surface_shapes.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/occurrence.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/occurrence_kex_e2e.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/operator_surface.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/owner_is_the_identity.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/owner_lockout_recovery.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/ownership.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/peer_replication.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/piv_preflight_fails_open.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/portable_occurrence.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/pqc_is_not_optional.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/release_gates/boundary.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/release_gates/ffi_symbols.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/release_gates/ladder.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/release_gates/planes.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/release_gates/surfaces.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/release_gates/trust_root.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/release_gates.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/replication.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/replication_policy_gate.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/replication_reconcile.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/resolve_bearer_binding.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/retention_loop.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/revoked_after_enforcement.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/root_bootstrap.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/safety.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/seed_digest_probe.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/seed_vocabulary.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/self_identity_fold.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/session_token_is_verified.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/stream_sth_consistency.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/support/accord_batch.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/support/accord_trust.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/support/localization.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/support/revocation.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/trace_plane_release_gate.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/trace_round_e2e.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/tracing_reinit.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/tracing_sink.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/trust_root_qa.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/wire_vocabulary_gate.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tests/withdraws_arbitrage.rs +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tools/audit_cohort_scope_callers.py +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tools/build-android-wheel.sh +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tools/check_blocked_upstream.sh +0 -0
- {ciris_server-0.5.181 → ciris_server-0.5.182}/tools/check_evidence.py +0 -0
|
@@ -52,7 +52,26 @@ jobs:
|
|
|
52
52
|
# Drop the preinstalled Microsoft/azure-cli apt repo: it intermittently
|
|
53
53
|
# 403s and tanks apt-get update (its packages are not needed here).
|
|
54
54
|
sudo rm -f /etc/apt/sources.list.d/microsoft-prod.list /etc/apt/sources.list.d/azure-cli.list /etc/apt/sources.list.d/azure-cli.sources
|
|
55
|
-
|
|
55
|
+
# AND drop the AZURE UBUNTU MIRROR itself (CIRISServer#449). Removing
|
|
56
|
+
# the Microsoft repos above was not enough: the runner image makes
|
|
57
|
+
# `azure.archive.ubuntu.com` the PRIMARY Ubuntu mirror via
|
|
58
|
+
# /etc/apt/apt-mirrors.txt, and when it stops answering, apt retries it
|
|
59
|
+
# for the InRelease of every suite before falling back. Observed three
|
|
60
|
+
# times on one PR: `clippy + test` wedged 68 min, `traceflow ladder`
|
|
61
|
+
# 75 min to a timeout-failure, and the retry of the first wedged again
|
|
62
|
+
# at the identical `Ign:` lines. A job that hangs for an hour reads as
|
|
63
|
+
# a slow test suite, which is why it cost a day before anyone looked.
|
|
64
|
+
sudo sed -i 's|azure\.archive\.ubuntu\.com|archive.ubuntu.com|g' \
|
|
65
|
+
/etc/apt/apt-mirrors.txt /etc/apt/sources.list 2>/dev/null || true
|
|
66
|
+
sudo find /etc/apt/sources.list.d -type f -exec \
|
|
67
|
+
sed -i 's|azure\.archive\.ubuntu\.com|archive.ubuntu.com|g' {} + 2>/dev/null || true
|
|
68
|
+
# Bounded: retry a few times, cap each connection, and cap the whole
|
|
69
|
+
# step. Without the outer `timeout` a stalled mirror consumes the job's
|
|
70
|
+
# entire budget and the failure names the job, never the cause.
|
|
71
|
+
sudo timeout 300 apt-get update \
|
|
72
|
+
-o Acquire::Retries=3 \
|
|
73
|
+
-o Acquire::http::Timeout=20 \
|
|
74
|
+
-o Acquire::https::Timeout=20
|
|
56
75
|
sudo apt-get install -y libtss2-dev libsqlite3-dev libudev-dev
|
|
57
76
|
# CIRISCache (CIRISServer#99) — 4-layer centipede over the Swatinem GHA L1.
|
|
58
77
|
# Single leg: PLAT=linux-x86_64. Restore verify→persist→edge→server; SAVE
|
|
@@ -136,8 +136,16 @@ jobs:
|
|
|
136
136
|
# 403s and tanks apt-get update (its packages are not needed here).
|
|
137
137
|
sudo rm -f /etc/apt/sources.list.d/microsoft-prod.list /etc/apt/sources.list.d/azure-cli.list /etc/apt/sources.list.d/azure-cli.sources # CIRISServer#99 — retry apt (ports.ubuntu.com intermittently network-times-out
|
|
138
138
|
# on the arm64 runners; a bare failure tanked 0.5.117's linux-aarch64 wheel).
|
|
139
|
+
# Also drop the AZURE UBUNTU MIRROR (CIRISServer#449): the runner image
|
|
140
|
+
# makes it primary via /etc/apt/apt-mirrors.txt, and a stalled azure
|
|
141
|
+
# mirror wedges a job for over an hour rather than failing it.
|
|
142
|
+
sudo sed -i 's|azure\.archive\.ubuntu\.com|archive.ubuntu.com|g' \
|
|
143
|
+
/etc/apt/apt-mirrors.txt /etc/apt/sources.list 2>/dev/null || true
|
|
144
|
+
sudo find /etc/apt/sources.list.d -type f -exec \
|
|
145
|
+
sed -i 's|azure\.archive\.ubuntu\.com|archive.ubuntu.com|g' {} + 2>/dev/null || true
|
|
139
146
|
for i in 1 2 3; do
|
|
140
|
-
sudo apt-get update
|
|
147
|
+
sudo timeout 300 apt-get update -o Acquire::Retries=3 -o Acquire::http::Timeout=20 -o Acquire::https::Timeout=20 \
|
|
148
|
+
&& sudo apt-get install -y libsqlite3-dev libudev-dev patchelf && break
|
|
141
149
|
echo "apt attempt $i failed; retrying in $((i*20))s"; sleep $((i*20))
|
|
142
150
|
done
|
|
143
151
|
- uses: actions/setup-python@v5
|
|
@@ -95,7 +95,26 @@ jobs:
|
|
|
95
95
|
# Drop the preinstalled Microsoft/azure-cli apt repo: it intermittently
|
|
96
96
|
# 403s and tanks apt-get update (its packages are not needed here).
|
|
97
97
|
sudo rm -f /etc/apt/sources.list.d/microsoft-prod.list /etc/apt/sources.list.d/azure-cli.list /etc/apt/sources.list.d/azure-cli.sources
|
|
98
|
-
|
|
98
|
+
# AND drop the AZURE UBUNTU MIRROR itself (CIRISServer#449). Removing
|
|
99
|
+
# the Microsoft repos above was not enough: the runner image makes
|
|
100
|
+
# `azure.archive.ubuntu.com` the PRIMARY Ubuntu mirror via
|
|
101
|
+
# /etc/apt/apt-mirrors.txt, and when it stops answering, apt retries it
|
|
102
|
+
# for the InRelease of every suite before falling back. Observed three
|
|
103
|
+
# times on one PR: `clippy + test` wedged 68 min, `traceflow ladder`
|
|
104
|
+
# 75 min to a timeout-failure, and the retry of the first wedged again
|
|
105
|
+
# at the identical `Ign:` lines. A job that hangs for an hour reads as
|
|
106
|
+
# a slow test suite, which is why it cost a day before anyone looked.
|
|
107
|
+
sudo sed -i 's|azure\.archive\.ubuntu\.com|archive.ubuntu.com|g' \
|
|
108
|
+
/etc/apt/apt-mirrors.txt /etc/apt/sources.list 2>/dev/null || true
|
|
109
|
+
sudo find /etc/apt/sources.list.d -type f -exec \
|
|
110
|
+
sed -i 's|azure\.archive\.ubuntu\.com|archive.ubuntu.com|g' {} + 2>/dev/null || true
|
|
111
|
+
# Bounded: retry a few times, cap each connection, and cap the whole
|
|
112
|
+
# step. Without the outer `timeout` a stalled mirror consumes the job's
|
|
113
|
+
# entire budget and the failure names the job, never the cause.
|
|
114
|
+
sudo timeout 300 apt-get update \
|
|
115
|
+
-o Acquire::Retries=3 \
|
|
116
|
+
-o Acquire::http::Timeout=20 \
|
|
117
|
+
-o Acquire::https::Timeout=20
|
|
99
118
|
sudo apt-get install -y libtss2-dev libsqlite3-dev libudev-dev
|
|
100
119
|
# CIRISCache (CIRISServer#99) — 4-layer centipede over the Swatinem GHA L1.
|
|
101
120
|
# PLAT from the NATIVE target of each runner (macos-latest = arm64). Restore
|
|
@@ -384,7 +403,18 @@ jobs:
|
|
|
384
403
|
sudo rm -f /etc/apt/sources.list.d/microsoft-prod.list \
|
|
385
404
|
/etc/apt/sources.list.d/azure-cli.list \
|
|
386
405
|
/etc/apt/sources.list.d/azure-cli.sources
|
|
387
|
-
|
|
406
|
+
# Drop the AZURE UBUNTU MIRROR (CIRISServer#449) — the runner image makes
|
|
407
|
+
# it the PRIMARY mirror via /etc/apt/apt-mirrors.txt, and a stalled
|
|
408
|
+
# azure mirror wedges the whole job (68 min, 75 min, and a re-run that
|
|
409
|
+
# hung again, all on one PR).
|
|
410
|
+
sudo sed -i 's|azure\.archive\.ubuntu\.com|archive.ubuntu.com|g' \
|
|
411
|
+
/etc/apt/apt-mirrors.txt /etc/apt/sources.list 2>/dev/null || true
|
|
412
|
+
sudo find /etc/apt/sources.list.d -type f -exec \
|
|
413
|
+
sed -i 's|azure\.archive\.ubuntu\.com|archive.ubuntu.com|g' {} + 2>/dev/null || true
|
|
414
|
+
sudo timeout 300 apt-get update \
|
|
415
|
+
-o Acquire::Retries=3 \
|
|
416
|
+
-o Acquire::http::Timeout=20 \
|
|
417
|
+
-o Acquire::https::Timeout=20
|
|
388
418
|
sudo apt-get install -y libtss2-dev libsqlite3-dev libudev-dev
|
|
389
419
|
- name: Compute CIRISCache keys (4-layer centipede, CIRISServer#99)
|
|
390
420
|
id: cachekey
|
|
@@ -96,7 +96,26 @@ jobs:
|
|
|
96
96
|
# Drop the preinstalled Microsoft/azure-cli apt repo: it intermittently
|
|
97
97
|
# 403s and tanks apt-get update (its packages are not needed here).
|
|
98
98
|
sudo rm -f /etc/apt/sources.list.d/microsoft-prod.list /etc/apt/sources.list.d/azure-cli.list /etc/apt/sources.list.d/azure-cli.sources
|
|
99
|
-
|
|
99
|
+
# AND drop the AZURE UBUNTU MIRROR itself (CIRISServer#449). Removing
|
|
100
|
+
# the Microsoft repos above was not enough: the runner image makes
|
|
101
|
+
# `azure.archive.ubuntu.com` the PRIMARY Ubuntu mirror via
|
|
102
|
+
# /etc/apt/apt-mirrors.txt, and when it stops answering, apt retries it
|
|
103
|
+
# for the InRelease of every suite before falling back. Observed three
|
|
104
|
+
# times on one PR: `clippy + test` wedged 68 min, `traceflow ladder`
|
|
105
|
+
# 75 min to a timeout-failure, and the retry of the first wedged again
|
|
106
|
+
# at the identical `Ign:` lines. A job that hangs for an hour reads as
|
|
107
|
+
# a slow test suite, which is why it cost a day before anyone looked.
|
|
108
|
+
sudo sed -i 's|azure\.archive\.ubuntu\.com|archive.ubuntu.com|g' \
|
|
109
|
+
/etc/apt/apt-mirrors.txt /etc/apt/sources.list 2>/dev/null || true
|
|
110
|
+
sudo find /etc/apt/sources.list.d -type f -exec \
|
|
111
|
+
sed -i 's|azure\.archive\.ubuntu\.com|archive.ubuntu.com|g' {} + 2>/dev/null || true
|
|
112
|
+
# Bounded: retry a few times, cap each connection, and cap the whole
|
|
113
|
+
# step. Without the outer `timeout` a stalled mirror consumes the job's
|
|
114
|
+
# entire budget and the failure names the job, never the cause.
|
|
115
|
+
sudo timeout 300 apt-get update \
|
|
116
|
+
-o Acquire::Retries=3 \
|
|
117
|
+
-o Acquire::http::Timeout=20 \
|
|
118
|
+
-o Acquire::https::Timeout=20
|
|
100
119
|
sudo apt-get install -y libsqlite3-dev libudev-dev patchelf
|
|
101
120
|
- uses: actions/setup-python@v5
|
|
102
121
|
with:
|
|
@@ -90,7 +90,18 @@ jobs:
|
|
|
90
90
|
sudo rm -f /etc/apt/sources.list.d/microsoft-prod.list \
|
|
91
91
|
/etc/apt/sources.list.d/azure-cli.list \
|
|
92
92
|
/etc/apt/sources.list.d/azure-cli.sources
|
|
93
|
-
|
|
93
|
+
# Drop the AZURE UBUNTU MIRROR (CIRISServer#449) — the runner image makes
|
|
94
|
+
# it the PRIMARY mirror via /etc/apt/apt-mirrors.txt, and a stalled
|
|
95
|
+
# azure mirror wedges the whole job (68 min, 75 min, and a re-run that
|
|
96
|
+
# hung again, all on one PR).
|
|
97
|
+
sudo sed -i 's|azure\.archive\.ubuntu\.com|archive.ubuntu.com|g' \
|
|
98
|
+
/etc/apt/apt-mirrors.txt /etc/apt/sources.list 2>/dev/null || true
|
|
99
|
+
sudo find /etc/apt/sources.list.d -type f -exec \
|
|
100
|
+
sed -i 's|azure\.archive\.ubuntu\.com|archive.ubuntu.com|g' {} + 2>/dev/null || true
|
|
101
|
+
sudo timeout 300 apt-get update \
|
|
102
|
+
-o Acquire::Retries=3 \
|
|
103
|
+
-o Acquire::http::Timeout=20 \
|
|
104
|
+
-o Acquire::https::Timeout=20
|
|
94
105
|
sudo apt-get install -y libtss2-dev libsqlite3-dev libudev-dev
|
|
95
106
|
|
|
96
107
|
- uses: dtolnay/rust-toolchain@1.97.0
|
|
@@ -112,7 +112,26 @@ jobs:
|
|
|
112
112
|
# Drop the preinstalled Microsoft/azure-cli apt repo: it intermittently
|
|
113
113
|
# 403s and tanks apt-get update (its packages are not needed here).
|
|
114
114
|
sudo rm -f /etc/apt/sources.list.d/microsoft-prod.list /etc/apt/sources.list.d/azure-cli.list /etc/apt/sources.list.d/azure-cli.sources
|
|
115
|
-
|
|
115
|
+
# AND drop the AZURE UBUNTU MIRROR itself (CIRISServer#449). Removing
|
|
116
|
+
# the Microsoft repos above was not enough: the runner image makes
|
|
117
|
+
# `azure.archive.ubuntu.com` the PRIMARY Ubuntu mirror via
|
|
118
|
+
# /etc/apt/apt-mirrors.txt, and when it stops answering, apt retries it
|
|
119
|
+
# for the InRelease of every suite before falling back. Observed three
|
|
120
|
+
# times on one PR: `clippy + test` wedged 68 min, `traceflow ladder`
|
|
121
|
+
# 75 min to a timeout-failure, and the retry of the first wedged again
|
|
122
|
+
# at the identical `Ign:` lines. A job that hangs for an hour reads as
|
|
123
|
+
# a slow test suite, which is why it cost a day before anyone looked.
|
|
124
|
+
sudo sed -i 's|azure\.archive\.ubuntu\.com|archive.ubuntu.com|g' \
|
|
125
|
+
/etc/apt/apt-mirrors.txt /etc/apt/sources.list 2>/dev/null || true
|
|
126
|
+
sudo find /etc/apt/sources.list.d -type f -exec \
|
|
127
|
+
sed -i 's|azure\.archive\.ubuntu\.com|archive.ubuntu.com|g' {} + 2>/dev/null || true
|
|
128
|
+
# Bounded: retry a few times, cap each connection, and cap the whole
|
|
129
|
+
# step. Without the outer `timeout` a stalled mirror consumes the job's
|
|
130
|
+
# entire budget and the failure names the job, never the cause.
|
|
131
|
+
sudo timeout 300 apt-get update \
|
|
132
|
+
-o Acquire::Retries=3 \
|
|
133
|
+
-o Acquire::http::Timeout=20 \
|
|
134
|
+
-o Acquire::https::Timeout=20
|
|
116
135
|
sudo apt-get install -y libsqlite3-dev libudev-dev
|
|
117
136
|
|
|
118
137
|
# CIRISCache (CIRISServer#99) — 4-layer centipede over the Swatinem GHA L1.
|
|
@@ -908,8 +908,8 @@ dependencies = [
|
|
|
908
908
|
|
|
909
909
|
[[package]]
|
|
910
910
|
name = "ciris-crypto"
|
|
911
|
-
version = "13.
|
|
912
|
-
source = "git+https://github.com/CIRISAI/CIRISVerify?tag=v13.
|
|
911
|
+
version = "13.6.1"
|
|
912
|
+
source = "git+https://github.com/CIRISAI/CIRISVerify?tag=v13.6.1#281f486074f80b7f13030bf471a66b18cd773c61"
|
|
913
913
|
dependencies = [
|
|
914
914
|
"chacha20poly1305",
|
|
915
915
|
"ed25519-dalek",
|
|
@@ -935,8 +935,8 @@ dependencies = [
|
|
|
935
935
|
|
|
936
936
|
[[package]]
|
|
937
937
|
name = "ciris-edge"
|
|
938
|
-
version = "
|
|
939
|
-
source = "git+https://github.com/CIRISAI/CIRISEdge?tag=
|
|
938
|
+
version = "18.0.2"
|
|
939
|
+
source = "git+https://github.com/CIRISAI/CIRISEdge?tag=v18.0.2#2fd0c95c2d21fa6b375f1ea534b7f2f22392ba7c"
|
|
940
940
|
dependencies = [
|
|
941
941
|
"async-trait",
|
|
942
942
|
"axum",
|
|
@@ -990,8 +990,8 @@ dependencies = [
|
|
|
990
990
|
|
|
991
991
|
[[package]]
|
|
992
992
|
name = "ciris-keyring"
|
|
993
|
-
version = "13.
|
|
994
|
-
source = "git+https://github.com/CIRISAI/CIRISVerify?tag=v13.
|
|
993
|
+
version = "13.6.1"
|
|
994
|
+
source = "git+https://github.com/CIRISAI/CIRISVerify?tag=v13.6.1#281f486074f80b7f13030bf471a66b18cd773c61"
|
|
995
995
|
dependencies = [
|
|
996
996
|
"aes-gcm",
|
|
997
997
|
"async-trait",
|
|
@@ -1056,8 +1056,8 @@ dependencies = [
|
|
|
1056
1056
|
|
|
1057
1057
|
[[package]]
|
|
1058
1058
|
name = "ciris-persist"
|
|
1059
|
-
version = "
|
|
1060
|
-
source = "git+https://github.com/CIRISAI/CIRISPersist?tag=
|
|
1059
|
+
version = "37.1.0"
|
|
1060
|
+
source = "git+https://github.com/CIRISAI/CIRISPersist?tag=v37.1.0#9c17a9f2012813c2baf7247050763592cb6bc417"
|
|
1061
1061
|
dependencies = [
|
|
1062
1062
|
"anyhow",
|
|
1063
1063
|
"async-trait",
|
|
@@ -1102,7 +1102,7 @@ dependencies = [
|
|
|
1102
1102
|
|
|
1103
1103
|
[[package]]
|
|
1104
1104
|
name = "ciris-server"
|
|
1105
|
-
version = "0.5.
|
|
1105
|
+
version = "0.5.182"
|
|
1106
1106
|
dependencies = [
|
|
1107
1107
|
"anyhow",
|
|
1108
1108
|
"async-trait",
|
|
@@ -1149,8 +1149,8 @@ dependencies = [
|
|
|
1149
1149
|
|
|
1150
1150
|
[[package]]
|
|
1151
1151
|
name = "ciris-verify-core"
|
|
1152
|
-
version = "13.
|
|
1153
|
-
source = "git+https://github.com/CIRISAI/CIRISVerify?tag=v13.
|
|
1152
|
+
version = "13.6.1"
|
|
1153
|
+
source = "git+https://github.com/CIRISAI/CIRISVerify?tag=v13.6.1#281f486074f80b7f13030bf471a66b18cd773c61"
|
|
1154
1154
|
dependencies = [
|
|
1155
1155
|
"android_system_properties",
|
|
1156
1156
|
"async-trait",
|
|
@@ -1191,8 +1191,8 @@ dependencies = [
|
|
|
1191
1191
|
|
|
1192
1192
|
[[package]]
|
|
1193
1193
|
name = "ciris-verify-ffi"
|
|
1194
|
-
version = "13.
|
|
1195
|
-
source = "git+https://github.com/CIRISAI/CIRISVerify?tag=v13.
|
|
1194
|
+
version = "13.6.1"
|
|
1195
|
+
source = "git+https://github.com/CIRISAI/CIRISVerify?tag=v13.6.1#281f486074f80b7f13030bf471a66b18cd773c61"
|
|
1196
1196
|
dependencies = [
|
|
1197
1197
|
"aes-gcm",
|
|
1198
1198
|
"android_logger",
|
|
@@ -3584,8 +3584,8 @@ checksum = "bbd2bcb4c963f2ddae06a2efc7e9f3591312473c50c6685e1f298068316e66fe"
|
|
|
3584
3584
|
|
|
3585
3585
|
[[package]]
|
|
3586
3586
|
name = "leviculum-core"
|
|
3587
|
-
version = "0.
|
|
3588
|
-
source = "git+https://github.com/CIRISAI/leviculum?tag=v0.
|
|
3587
|
+
version = "0.20.0+ciris.1"
|
|
3588
|
+
source = "git+https://github.com/CIRISAI/leviculum?tag=v0.20.0%2Bciris.1#8775f1f838d7b47886193599884a859633363c1a"
|
|
3589
3589
|
dependencies = [
|
|
3590
3590
|
"aes",
|
|
3591
3591
|
"cbc",
|
|
@@ -3602,8 +3602,8 @@ dependencies = [
|
|
|
3602
3602
|
|
|
3603
3603
|
[[package]]
|
|
3604
3604
|
name = "leviculum-lxmf"
|
|
3605
|
-
version = "0.
|
|
3606
|
-
source = "git+https://github.com/CIRISAI/leviculum?tag=v0.
|
|
3605
|
+
version = "0.20.0+ciris.1"
|
|
3606
|
+
source = "git+https://github.com/CIRISAI/leviculum?tag=v0.20.0%2Bciris.1#8775f1f838d7b47886193599884a859633363c1a"
|
|
3607
3607
|
dependencies = [
|
|
3608
3608
|
"leviculum-core",
|
|
3609
3609
|
"rand_core 0.6.4",
|
|
@@ -3613,10 +3613,11 @@ dependencies = [
|
|
|
3613
3613
|
|
|
3614
3614
|
[[package]]
|
|
3615
3615
|
name = "leviculum-std"
|
|
3616
|
-
version = "0.
|
|
3617
|
-
source = "git+https://github.com/CIRISAI/leviculum?tag=v0.
|
|
3616
|
+
version = "0.20.0+ciris.1"
|
|
3617
|
+
source = "git+https://github.com/CIRISAI/leviculum?tag=v0.20.0%2Bciris.1#8775f1f838d7b47886193599884a859633363c1a"
|
|
3618
3618
|
dependencies = [
|
|
3619
3619
|
"clap 4.6.6",
|
|
3620
|
+
"futures",
|
|
3620
3621
|
"hmac 0.12.1",
|
|
3621
3622
|
"if-addrs",
|
|
3622
3623
|
"leviculum-core",
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
[package]
|
|
2
2
|
name = "ciris-server"
|
|
3
|
-
version = "0.5.181" # 0.5.181 = A CHECK THAT CANNOT FAIL READS AS CONFIRMATION. Four changes, one theme. (1) #445 A BROWSER SIGN-IN COULD STILL NOT COMPLETE, and the cause was ONE LINE in /login: `Some(redirect_uri).filter(|r| r != "/")` collapsed TWO states onto None — "no redirect_uri given" and "the destination IS the site root" — and the callback reads None as "serve the desktop hand-off page", which is LOOPBACK-ONLY. A plain /login is the front door of every managed deployment, so the arm that broke was the NORMAL case, not the stray one: authentication succeeded every time, the session was parked where the browser could not reach it, and ZERO redemption codes were minted in six hours on a node answering web_signin:true. Now collapsed only when app_nonce is present (a desktop app polls the loopback hand-off; a redirect to / would be noise). Deliberately NOT keyed on ConnectInfo: a managed node behind a reverse proxy sees the PROXY's loopback address, so "is this caller local" is unanswerable at the callback — it is answerable at /v1/auth/signin-state, where the caller connects directly, which is why session_delivery lives there. Every existing test drove the flow with an explicit redirect_uri; there was a D3 case for /dashboard and NONE for the front door. (2) #445 THE LOG LINE THAT SENT THE REPORT UPSTREAM. "NO app_nonce: … a stray tab … claimable only via the loopback-gated recent slot" diagnosed the CALLER instead of describing the flow, and led a careful reader to the wrong branch entirely — the callback never branched on app_nonce at all. It now says what actually happens. (3) #352 THE EVIDENCE MANIFEST PARSED AS ZERO COVERAGE — the same defect class, in the compliance layer. The Constitution's check_claims.py strips # lines and hands the rest to csv.DictReader, which took our first DATA row as the header; every later row then lacked a decimal_id and was SILENTLY skipped. Vendoring the file added a manifest that resolved nothing and reported nothing. Now emits the canonical header row, spelled EXACTLY as CIRISPersist spells it (decimal_id, not our comment's older cc_section) because the consumer keys on those names and two spellings is how two files drift. 0 usable rows -> 12, all with decimal_id. (4) THE RELEASE GATE NOW DRIVES THE FRONT DOOR, because #445 WOULD HAVE PASSED IT AS WRITTEN — it asserted the surface SHAPE (web_signin is present) and never that a browser can actually sign in. Two of its own drafts failed before it worked, both recorded because they are the same disease: under set -euo pipefail a grep matching nothing killed the script mid-assignment so it printed NOTHING and read as a pass; and the first working draft reported a 200 from /login as "skip — no provider configured" and exited 0, which would have passed the very release it was written for. It now asks the providers list to tell an unconfigured node from a broken one. All four branches exercised: healthy redirect passes, the #445 shape FAILS, nothing-listening FAILS, genuinely-unconfigured SKIPS loudly. Substrate unmoved: persist v32.3.0 / edge v17.4.1 / verify v13.3.1. PRIOR CUT (0.5.180) FOLLOWS: THE GATE THAT BROKE A RELEASE, FIXED. THE 0.5.179 GITHUB RELEASE IS INCOMPLETE (27/30 assets, zero linux-x86_64) AND THIS CUT REPLACES IT. Its PyPI wheels published fine (9 files), so pip users were never affected; anyone pulling the linux binary from the GitHub release was. CAUSE: the release-surface gate I added in 0.5.179 failed the linux lane on a bug of its OWN. It discovered the port by grepping the boot log for listen_addr. That was wrong TWICE: (1) the node's stderr is BLOCK-buffered into a file, so while the process LIVES the log is EMPTY — the gate only ever "worked" locally because the node CRASHED there, and exiting flushed the buffer; its happy path had NEVER ONCE EXECUTED and it was wired to fail the build regardless. (2) net.listen_addr (:4242) is the RETICULUM transport; the node's entire HTTP interface is :4243 (compose.rs — "this one listener also carries /v1/identity, auth, setup/claim, config, ingest"). FIX: no discovery step remains — readiness IS the endpoint under test answering, with stdbuf keeping the diagnostic log usable while the process lives (0.5.179 reported an EMPTY log, which is why nothing could be diagnosed from it). WHILE TESTING THE FIX THE GATE CAUGHT ITSELF COMMITTING #410: a fake binary that died instantly still "verified", because an UNRELATED node was already serving :4243 and answered the readiness probe. A 200 from a port is not proof it is YOUR node — in CI that silently greenlights a broken artifact against someone else's healthy one, the worst possible failure for a gate whose whole job is proving what THIS build serves. Now nothing may already answer before boot, and our PID must still be alive when it does. ALL FOUR BRANCHES ARE NOW EXERCISED: happy path (exit 0), assertions bite (exit 1 against a live 0.5.173 node lacking the fields), stranger-on-port (exit 1, 0s), boot-death (exit 1, 1s, log actually dumped). ONE branch still cannot be tested off-CI — a real binary booting and serving — because the dev host holds 4242/4243. So the step is REPORT-ONLY this release: blocking on a branch that has never run is precisely what produced 0.5.179. Its job now is to ANSWER whether the shipped artifact serves web_signin and managed, which the release log answers either way. Flip continue-on-error off once it comes up green on a real boot. Substrate unmoved: persist v32.3.0 / edge v17.4.1 / verify v13.3.1. PRIOR CUT (0.5.179) FOLLOWS: THE SIGN-IN STATE CUT. (A) #439 A NODE CAN NOW BE ASKED WHAT WILL HAPPEN BEFORE YOU WALK INTO IT. GET /v1/auth/signin-state returns claimed / managed / web_signin / callback_base / providers plus new_identity{outcome, reason_id, remedy}. Sign-in has TEN distinct outcomes across desktop, browser, mobile, managed and personal nodes and no client could ask which one it was in, so every surface guessed and guessed DIFFERENTLY: the GUI pattern-matched a hostname, the desktop client asked the BRAIN about a fact only the node holds, a refused user saw a JSON wall or a spinner. The refusals were all CORRECT; what was missing was any way to see the state first. outcome is computed from the SAME two predicates resolve_oauth_user gates on, so it cannot drift from the behaviour it describes. The remedy is asserted PERFORMABLE — the gate fails if it says "link"/"settings", because #432 leaves both link surfaces dead and printing an impossible remedy is the ProviderUnavailable mistake this tree already paid for. (B) ANSWERED FOR THE CALLER, NOT IN THE ABSTRACT. The same node truthfully tells a loopback desktop app and a remote browser different things about how a session reaches them (loopback_handoff vs exchange_code) — collapsing those is HOW the loopback-only parking became invisible to browsers. caller_is_loopback() is extracted from require_loopback so the gate and the thing REPORTING the gate read one predicate. The node-wide facts (claimed/managed/web_signin) are asserted NOT to vary by caller: splitting the axis without that would invite the opposite bug. (C) THE RELEASE NOW ASKS ITS OWN ARTIFACT WHAT IT SERVES. 0.5.178 published and an afternoon went into arguing whether the binary contained web_signin — both sides running `strings`, a PROXY, because nothing could answer the only question that mattered. release.yml built, stripped, signed, uploaded and published without ever asking its output to respond. scripts/verify_release_surface.sh boots the STAGED STRIPPED binary (the exact uploaded bytes) and asserts every documented key on /v1/auth/oauth/providers and /v1/auth/signin-state; a release that cannot serve its own documented surface FAILS before publishing. It earned its place immediately: run against the shipped 0.5.178 binary it correctly reported a boot failure rather than passing silently. (D) CORRECTED: 0.5.178's own note described `managed` as PATH-derived while the code in the same tag used deployment::is_managed(). The note was written before the correction and never revisited — the second consecutive release whose note lagged its code. Substrate unmoved: persist v32.3.0 / edge v17.4.1 / verify v13.3.1. PRIOR CUT (0.5.178) FOLLOWS: THE SIGN-IN CUT. No substrate change (persist v32.3.0 / edge v17.4.1 / verify v13.3.1 unmoved) — every item is ours. (1) #439 A WEB SIGN-IN COULD NOT COMPLETE. The callback redirected the browser to its destination carrying NOTHING: the sign-in had succeeded, the session was parked on a loopback-only route a remote browser cannot reach, and the page could not tell "no session came back" from "the provider refused" — so CIRISGUI reported oauth_failed on a SUCCESSFUL sign-in. The destination now carries a SINGLE-USE redemption code redeemed at POST /v1/auth/oauth/exchange, session in the response BODY. The old contract is NOT restored: a live 24h bearer in a URL lands in history, in Referer, and in every proxy log on the path. A code authenticates nothing alone, dies on first redemption, expires in 60s — the OAuth authorization-code pattern applied to our own issuance. The exchange route is deliberately NOT loopback-gated and the reason is recorded AT the route: the desktop hand-off gives a bearer to anyone who asks so the network boundary protects it; this gives nothing without a 256-bit single-use code, so the code IS the authorisation. Unknown and spent codes share ONE refusal — distinguishing them confirms a real code to a prober. (2) #439 THE NODE STATES ITS DEPLOYMENT SHAPE. CIRISGUI decided managed-ness with hostname === "agents.ciris.ai", so every other hosted node was classified unmanaged and built its API base wrong. A client cannot derive this; the node knows it at boot. /v1/auth/oauth/providers now returns callback_base / managed / web_signin / exchange_query_key, with managed being deployment::is_managed() — an AUTH-POLICY fact (does this deployment admit MULTIPLE logins) and NOT a URL shape. A first draft derived it from whether the callback base carried a PATH; that was a routing question wearing the name of a policy one, and a client-visible LIE, since a path-prefixed personal node would have told CIRISGUI it admits strangers while refusing them. It is the SAME predicate resolve_oauth_user gates admission on, so what a client is told cannot drift from what the node does. Its gate is an INDEPENDENCE, not a value: four callback bases of different shapes must report the SAME posture. (3) #439 FIRST-RUN STOPPED LYING ABOUT A CLAIMED NODE. "Is this a first run?" depends on TWO stores and the client read one — the brain answers from its own config while the NODE knows whether it has been claimed. Observed live: brain setup_required=true beside node setup_required=false with a standing owner binding. The user got the first-run login, a Google sign-in there was correctly REFUSED (auth.oauth.no_local_identity, the owner being a local credential with no OAuth identity), and the node looked broken while being right every time. nodeHasOwner() and its reasoning were ALREADY in the file, in the degrade branches — the happy path was the one place the rule was missing. It now also SAYS so, in all 29 languages. ALSO RECORDED HERE, because 0.5.177 shipped them after its own comment was written: #434 the provider ID TOKEN now reaches the desktop app (Google returns it in the SAME response the node already parsed for access_token; desktop CIRIS_PROXY was configured with an EMPTY api_key via googleIdToken ?: ""), and #435 a deployment can DECLARE its callback base before boot (writing the config key needs an owner session, which needs a sign-in, which is what the key configures — precedence is one-directional: stored config -> environment -> loopback default).
|
|
3
|
+
version = "0.5.182" # 0.5.182 = THE SUBSTRATE JUMP AND THE SIGN-IN MATRIX. (A) SUBSTRATE: persist v32.3.0->v37.1.0, edge v17.4.1->v18.0.2, verify v13.3.1->v13.6.1, carrying leviculum v0.16->v0.20 (where the completion-mirror + lock-contention work behind the live-canonical wedge lands, CIRISEdge#508 / leviculum#56-#59). NO RE-GENESIS: both re-genesis mentions in persist v37 are GUARDS not triggers, accord_root is write-door-only, no signature preimage moved — and genesis_bundle_validate passes 7/7 on the new triple. Persist independently re-validated on BOTH backends and FALSIFIED it (one flipped base64 char in the charter signature reds the install gate), and established the span is v31.2->v37.1, correcting our own recalled estimate. 30 new WithholdReason variants classified across Policy/Fault/Integrity from edge's documented semantics — the load-bearing line being "I cannot judge" (Fault) vs "the signer is not seated" (Policy), which CIRISPersist#713 wrote a mutation to protect. --lib was GREEN while --all-targets was RED on the NAT fixture, exactly the trap v37's changelog documents. (B) #448 A PRE-PROVISIONED HUMAN IS NOT A STRANGER. resolve_oauth_user matched only (provider, external_id), so a person an owner ADDED IN USERS was refused on the node they were added to — the node ignoring its own operator. An owner knows an ADDRESS and can never know a Google `sub`. An active cert carrying that email with no pair yet is now a provisioning slot: the verified pair is stamped on first sign-in and the weaker handle stops being load-bearing. THE SECURITY LINE DID NOT MOVE — this matches an email an OWNER WROTE onto a cert, never one a caller asserts; an unprovisioned address still matches nothing, a cert already naming an identity can never be rebound by address, and two slots for one address refuse rather than pick. (C) #432 CLOSED FROM THE DIRECTION THAT WORKS. POST /v1/self/oauth-link was not merely uncalled, it was UNCALLABLE: it demanded an external_id no human can look up. It now accepts an EMAIL and has a real client caller (preprovisionOAuthEmail). The generated UsersApi path /v1/users/{id}/oauth-links is the AGENT's spec surface and was never ours to route. (D) THE REMEDY SENTENCE IS BACK, and ONLY because the action now works — it came out at 0.5.177 because naming an impossible remedy is the #387 lesson. If that path is removed, the sentence comes out in the same commit. (E) tests/oauth_state_matrix.rs — 15 rows over a SYNTHETIC provider driving the real router, real resolve path, real store. MANAGED NODES ADMIT ANYONE AS AN OBSERVER and that is now pinned by ROLE, not just by admission: mutating determine_role to Authority reds both managed rows. The managed logic is CORRECT in code, so a managed deployment that refuses is an is_managed() DETECTION fault — it is a majority-of-five needing TWO indicators, and a container setting only CIRIS_MANAGED=true is still classified personal while looking configured. Two of my own defects are recorded in the file: CIRIS_MANAGED is process-global and leaked across rows (three refusals red, the email row GREEN — the pass being the dangerous half), and two adjacent &str params in authorize_url were swapped, which compiled perfectly and put the redirect_uri where the state belonged. PRIOR CUT (0.5.181) FOLLOWS: A CHECK THAT CANNOT FAIL READS AS CONFIRMATION. Four changes, one theme. (1) #445 A BROWSER SIGN-IN COULD STILL NOT COMPLETE, and the cause was ONE LINE in /login: `Some(redirect_uri).filter(|r| r != "/")` collapsed TWO states onto None — "no redirect_uri given" and "the destination IS the site root" — and the callback reads None as "serve the desktop hand-off page", which is LOOPBACK-ONLY. A plain /login is the front door of every managed deployment, so the arm that broke was the NORMAL case, not the stray one: authentication succeeded every time, the session was parked where the browser could not reach it, and ZERO redemption codes were minted in six hours on a node answering web_signin:true. Now collapsed only when app_nonce is present (a desktop app polls the loopback hand-off; a redirect to / would be noise). Deliberately NOT keyed on ConnectInfo: a managed node behind a reverse proxy sees the PROXY's loopback address, so "is this caller local" is unanswerable at the callback — it is answerable at /v1/auth/signin-state, where the caller connects directly, which is why session_delivery lives there. Every existing test drove the flow with an explicit redirect_uri; there was a D3 case for /dashboard and NONE for the front door. (2) #445 THE LOG LINE THAT SENT THE REPORT UPSTREAM. "NO app_nonce: … a stray tab … claimable only via the loopback-gated recent slot" diagnosed the CALLER instead of describing the flow, and led a careful reader to the wrong branch entirely — the callback never branched on app_nonce at all. It now says what actually happens. (3) #352 THE EVIDENCE MANIFEST PARSED AS ZERO COVERAGE — the same defect class, in the compliance layer. The Constitution's check_claims.py strips # lines and hands the rest to csv.DictReader, which took our first DATA row as the header; every later row then lacked a decimal_id and was SILENTLY skipped. Vendoring the file added a manifest that resolved nothing and reported nothing. Now emits the canonical header row, spelled EXACTLY as CIRISPersist spells it (decimal_id, not our comment's older cc_section) because the consumer keys on those names and two spellings is how two files drift. 0 usable rows -> 12, all with decimal_id. (4) THE RELEASE GATE NOW DRIVES THE FRONT DOOR, because #445 WOULD HAVE PASSED IT AS WRITTEN — it asserted the surface SHAPE (web_signin is present) and never that a browser can actually sign in. Two of its own drafts failed before it worked, both recorded because they are the same disease: under set -euo pipefail a grep matching nothing killed the script mid-assignment so it printed NOTHING and read as a pass; and the first working draft reported a 200 from /login as "skip — no provider configured" and exited 0, which would have passed the very release it was written for. It now asks the providers list to tell an unconfigured node from a broken one. All four branches exercised: healthy redirect passes, the #445 shape FAILS, nothing-listening FAILS, genuinely-unconfigured SKIPS loudly. Substrate unmoved: persist v32.3.0 / edge v17.4.1 / verify v13.3.1. PRIOR CUT (0.5.180) FOLLOWS: THE GATE THAT BROKE A RELEASE, FIXED. THE 0.5.179 GITHUB RELEASE IS INCOMPLETE (27/30 assets, zero linux-x86_64) AND THIS CUT REPLACES IT. Its PyPI wheels published fine (9 files), so pip users were never affected; anyone pulling the linux binary from the GitHub release was. CAUSE: the release-surface gate I added in 0.5.179 failed the linux lane on a bug of its OWN. It discovered the port by grepping the boot log for listen_addr. That was wrong TWICE: (1) the node's stderr is BLOCK-buffered into a file, so while the process LIVES the log is EMPTY — the gate only ever "worked" locally because the node CRASHED there, and exiting flushed the buffer; its happy path had NEVER ONCE EXECUTED and it was wired to fail the build regardless. (2) net.listen_addr (:4242) is the RETICULUM transport; the node's entire HTTP interface is :4243 (compose.rs — "this one listener also carries /v1/identity, auth, setup/claim, config, ingest"). FIX: no discovery step remains — readiness IS the endpoint under test answering, with stdbuf keeping the diagnostic log usable while the process lives (0.5.179 reported an EMPTY log, which is why nothing could be diagnosed from it). WHILE TESTING THE FIX THE GATE CAUGHT ITSELF COMMITTING #410: a fake binary that died instantly still "verified", because an UNRELATED node was already serving :4243 and answered the readiness probe. A 200 from a port is not proof it is YOUR node — in CI that silently greenlights a broken artifact against someone else's healthy one, the worst possible failure for a gate whose whole job is proving what THIS build serves. Now nothing may already answer before boot, and our PID must still be alive when it does. ALL FOUR BRANCHES ARE NOW EXERCISED: happy path (exit 0), assertions bite (exit 1 against a live 0.5.173 node lacking the fields), stranger-on-port (exit 1, 0s), boot-death (exit 1, 1s, log actually dumped). ONE branch still cannot be tested off-CI — a real binary booting and serving — because the dev host holds 4242/4243. So the step is REPORT-ONLY this release: blocking on a branch that has never run is precisely what produced 0.5.179. Its job now is to ANSWER whether the shipped artifact serves web_signin and managed, which the release log answers either way. Flip continue-on-error off once it comes up green on a real boot. Substrate unmoved: persist v32.3.0 / edge v17.4.1 / verify v13.3.1. PRIOR CUT (0.5.179) FOLLOWS: THE SIGN-IN STATE CUT. (A) #439 A NODE CAN NOW BE ASKED WHAT WILL HAPPEN BEFORE YOU WALK INTO IT. GET /v1/auth/signin-state returns claimed / managed / web_signin / callback_base / providers plus new_identity{outcome, reason_id, remedy}. Sign-in has TEN distinct outcomes across desktop, browser, mobile, managed and personal nodes and no client could ask which one it was in, so every surface guessed and guessed DIFFERENTLY: the GUI pattern-matched a hostname, the desktop client asked the BRAIN about a fact only the node holds, a refused user saw a JSON wall or a spinner. The refusals were all CORRECT; what was missing was any way to see the state first. outcome is computed from the SAME two predicates resolve_oauth_user gates on, so it cannot drift from the behaviour it describes. The remedy is asserted PERFORMABLE — the gate fails if it says "link"/"settings", because #432 leaves both link surfaces dead and printing an impossible remedy is the ProviderUnavailable mistake this tree already paid for. (B) ANSWERED FOR THE CALLER, NOT IN THE ABSTRACT. The same node truthfully tells a loopback desktop app and a remote browser different things about how a session reaches them (loopback_handoff vs exchange_code) — collapsing those is HOW the loopback-only parking became invisible to browsers. caller_is_loopback() is extracted from require_loopback so the gate and the thing REPORTING the gate read one predicate. The node-wide facts (claimed/managed/web_signin) are asserted NOT to vary by caller: splitting the axis without that would invite the opposite bug. (C) THE RELEASE NOW ASKS ITS OWN ARTIFACT WHAT IT SERVES. 0.5.178 published and an afternoon went into arguing whether the binary contained web_signin — both sides running `strings`, a PROXY, because nothing could answer the only question that mattered. release.yml built, stripped, signed, uploaded and published without ever asking its output to respond. scripts/verify_release_surface.sh boots the STAGED STRIPPED binary (the exact uploaded bytes) and asserts every documented key on /v1/auth/oauth/providers and /v1/auth/signin-state; a release that cannot serve its own documented surface FAILS before publishing. It earned its place immediately: run against the shipped 0.5.178 binary it correctly reported a boot failure rather than passing silently. (D) CORRECTED: 0.5.178's own note described `managed` as PATH-derived while the code in the same tag used deployment::is_managed(). The note was written before the correction and never revisited — the second consecutive release whose note lagged its code. Substrate unmoved: persist v32.3.0 / edge v17.4.1 / verify v13.3.1. PRIOR CUT (0.5.178) FOLLOWS: THE SIGN-IN CUT. No substrate change (persist v32.3.0 / edge v17.4.1 / verify v13.3.1 unmoved) — every item is ours. (1) #439 A WEB SIGN-IN COULD NOT COMPLETE. The callback redirected the browser to its destination carrying NOTHING: the sign-in had succeeded, the session was parked on a loopback-only route a remote browser cannot reach, and the page could not tell "no session came back" from "the provider refused" — so CIRISGUI reported oauth_failed on a SUCCESSFUL sign-in. The destination now carries a SINGLE-USE redemption code redeemed at POST /v1/auth/oauth/exchange, session in the response BODY. The old contract is NOT restored: a live 24h bearer in a URL lands in history, in Referer, and in every proxy log on the path. A code authenticates nothing alone, dies on first redemption, expires in 60s — the OAuth authorization-code pattern applied to our own issuance. The exchange route is deliberately NOT loopback-gated and the reason is recorded AT the route: the desktop hand-off gives a bearer to anyone who asks so the network boundary protects it; this gives nothing without a 256-bit single-use code, so the code IS the authorisation. Unknown and spent codes share ONE refusal — distinguishing them confirms a real code to a prober. (2) #439 THE NODE STATES ITS DEPLOYMENT SHAPE. CIRISGUI decided managed-ness with hostname === "agents.ciris.ai", so every other hosted node was classified unmanaged and built its API base wrong. A client cannot derive this; the node knows it at boot. /v1/auth/oauth/providers now returns callback_base / managed / web_signin / exchange_query_key, with managed being deployment::is_managed() — an AUTH-POLICY fact (does this deployment admit MULTIPLE logins) and NOT a URL shape. A first draft derived it from whether the callback base carried a PATH; that was a routing question wearing the name of a policy one, and a client-visible LIE, since a path-prefixed personal node would have told CIRISGUI it admits strangers while refusing them. It is the SAME predicate resolve_oauth_user gates admission on, so what a client is told cannot drift from what the node does. Its gate is an INDEPENDENCE, not a value: four callback bases of different shapes must report the SAME posture. (3) #439 FIRST-RUN STOPPED LYING ABOUT A CLAIMED NODE. "Is this a first run?" depends on TWO stores and the client read one — the brain answers from its own config while the NODE knows whether it has been claimed. Observed live: brain setup_required=true beside node setup_required=false with a standing owner binding. The user got the first-run login, a Google sign-in there was correctly REFUSED (auth.oauth.no_local_identity, the owner being a local credential with no OAuth identity), and the node looked broken while being right every time. nodeHasOwner() and its reasoning were ALREADY in the file, in the degrade branches — the happy path was the one place the rule was missing. It now also SAYS so, in all 29 languages. ALSO RECORDED HERE, because 0.5.177 shipped them after its own comment was written: #434 the provider ID TOKEN now reaches the desktop app (Google returns it in the SAME response the node already parsed for access_token; desktop CIRIS_PROXY was configured with an EMPTY api_key via googleIdToken ?: ""), and #435 a deployment can DECLARE its callback base before boot (writing the config key needs an owner session, which needs a sign-in, which is what the key configures — precedence is one-directional: stored config -> environment -> loopback default).
|
|
4
4
|
edition = "2021"
|
|
5
5
|
# MSRV floor is set by the substrate: ciris-verify v5.2.0 requires 1.86
|
|
6
6
|
# (persist v6.0.1 is 1.83). Build with the higher of the two.
|
|
@@ -135,8 +135,8 @@ ciris-lens-core = { path = "crates/ciris-lens-core" } # ABSORBED in-tree (wo
|
|
|
135
135
|
# `cirislens_wa_cert` + `cirislens_service_token_revocation` expose the auth
|
|
136
136
|
# substrate the fabric absorbs (CIRISServer#9, src/auth): the agent's `wa_cert`
|
|
137
137
|
# table (users/WA/OAuth/api-keys) + the `revoked_service_tokens` table.
|
|
138
|
-
ciris-persist = { git = "https://github.com/CIRISAI/CIRISPersist", tag = "
|
|
139
|
-
ciris-edge = { git = "https://github.com/CIRISAI/CIRISEdge", tag = "
|
|
138
|
+
ciris-persist = { git = "https://github.com/CIRISAI/CIRISPersist", tag = "v37.1.0", features = ["sqlite", "scrub", "cirisgraph", "cirislens_wa_cert", "cirislens_service_token_revocation", "cirisaudit", "cirislens_tasks", "cirislens_thoughts", "cirislens_tickets", "cirislens_correlations", "cirislens_deferral_reports", "cirislens_maintenance_locks", "cirislens_creation_ceremonies", "cirislens_legacy_migration", "cirisincident", "telemetry", "secrets"] }
|
|
139
|
+
ciris-edge = { git = "https://github.com/CIRISAI/CIRISEdge", tag = "v18.0.2", features = ["transport-reticulum", "transport-http", "transport-packet-radio", "ffi-uniffi"] }
|
|
140
140
|
# Founder-quorum verification + key-id fingerprint at the composition root
|
|
141
141
|
# (threshold:: module path — NOT re-exported at the crate root).
|
|
142
142
|
# LOCKSTEP: persist v9.4.0 transitively pins verify-core v6.6.x — the whole
|
|
@@ -168,16 +168,16 @@ ciris-edge = { git = "https://github.com/CIRISAI/CIRISEdge", tag = "v17.4
|
|
|
168
168
|
#
|
|
169
169
|
# What that ceiling costs us is recorded where it bites, not here:
|
|
170
170
|
# src/hardware_attestation.rs (CIRISServer#339 / CIRISVerify#199).
|
|
171
|
-
ciris-verify-core = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.
|
|
171
|
+
ciris-verify-core = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.6.1" }
|
|
172
172
|
# The hybrid crypto primitives (Ed25519 + ML-DSA-65 software signers) — used by
|
|
173
173
|
# the portable software identity occurrence to build a `HybridSigningIdentity`
|
|
174
174
|
# over two software seeds. Same tag as the rest of the verify family.
|
|
175
|
-
ciris-crypto = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.
|
|
175
|
+
ciris-crypto = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.6.1", version = "13", features = ["pqc-ml-dsa", "self-enc"] }
|
|
176
176
|
# Hardware-backed transport-identity keystore (verify v5.2.0 #68 / edge #99).
|
|
177
177
|
# Base = software keystore + byte-identical migration of an existing .rid (works
|
|
178
178
|
# everywhere, no libtss2). The real TPM-2.0 / SE / StrongBox backend rides the
|
|
179
179
|
# `tpm` feature; runtime auto-detects hardware and falls back to software.
|
|
180
|
-
ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.
|
|
180
|
+
ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.6.1", version = "13", features = ["software", "pqc-ml-dsa"] }
|
|
181
181
|
# The verify FFI (C ABI) — folded into `ciris_server._native.so` (CIRISServer#232)
|
|
182
182
|
# so the agent drops its standalone `ciris-verify` wheel and rides us for verify
|
|
183
183
|
# too (kills the v9.0.0-vs-v5.1.3 wire/canonical-hash skew, CIRISAgent#917). v9.0.1
|
|
@@ -188,7 +188,7 @@ ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.3.1
|
|
|
188
188
|
# FFI version == the bundled substrate version by construction (no skew possible).
|
|
189
189
|
# Default features (secp256k1, key-grant, hybrid-kex) + the crypto features unify
|
|
190
190
|
# with ciris-crypto's above (self-enc, pqc-ml-dsa) across the graph.
|
|
191
|
-
ciris-verify-ffi = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.
|
|
191
|
+
ciris-verify-ffi = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.6.1", version = "13", optional = true }
|
|
192
192
|
|
|
193
193
|
# PyO3 bindings for the abi3 wheel — optional, gated behind the `python` feature
|
|
194
194
|
# so the binary never links them. 0.29 matches the persist/edge family floor.
|
|
@@ -262,16 +262,16 @@ tracing-appender = "0.2"
|
|
|
262
262
|
# - keyring `tpm` (tss-esapi / TPM 2.0) — the real hardware backend; needs
|
|
263
263
|
# libtss2 (Linux build dep). Other targets keep the software keystore.
|
|
264
264
|
[target.'cfg(target_os = "linux")'.dependencies]
|
|
265
|
-
ciris-persist = { git = "https://github.com/CIRISAI/CIRISPersist", tag = "
|
|
265
|
+
ciris-persist = { git = "https://github.com/CIRISAI/CIRISPersist", tag = "v37.1.0", features = ["postgres", "scrub", "cirisgraph", "cirislens_wa_cert", "cirislens_service_token_revocation", "cirisaudit", "cirislens_tasks", "cirislens_thoughts", "cirislens_tickets", "cirislens_correlations", "cirislens_deferral_reports", "cirislens_maintenance_locks", "cirislens_creation_ceremonies", "cirislens_legacy_migration", "cirisincident", "telemetry", "secrets"] }
|
|
266
266
|
# keyring `tpm` (TPM-at-rest, Linux-only via tss-esapi). `pkcs11` is no longer
|
|
267
267
|
# per-target — it rides the global `pkcs11` feature now that cryptoki builds on all
|
|
268
268
|
# targets (CIRISVerify v6.12.0).
|
|
269
|
-
ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.
|
|
269
|
+
ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.6.1", version = "13", features = ["tpm-plugin"] }
|
|
270
270
|
|
|
271
271
|
# Android (arm64/arm32/x86_64): the keyring `android` backend (JNI → Android
|
|
272
272
|
# Keystore/StrongBox); sqlite bundles, no postgres/tpm. Mirrors persist/edge.
|
|
273
273
|
[target.'cfg(target_os = "android")'.dependencies]
|
|
274
|
-
ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.
|
|
274
|
+
ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.6.1", version = "13", features = ["android"] }
|
|
275
275
|
|
|
276
276
|
# serialport (the RNode LoRa driver dep, src/radio.rs) pulls libudev-sys on Linux,
|
|
277
277
|
# which only resolves where libudev exists: desktop/server Linux (gnu, x86_64 or
|
|
@@ -291,7 +291,7 @@ ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.3.1
|
|
|
291
291
|
# `full_traces` at Detailed and RELABELS the trace `detailed`, loudly. A mobile
|
|
292
292
|
# node therefore never ships content claiming a scrub it did not receive; it
|
|
293
293
|
# simply cannot offer the NER tier.
|
|
294
|
-
ciris-persist = { git = "https://github.com/CIRISAI/CIRISPersist", tag = "
|
|
294
|
+
ciris-persist = { git = "https://github.com/CIRISAI/CIRISPersist", tag = "v37.1.0", features = ["scrub-ner"] }
|
|
295
295
|
serialport = "4"
|
|
296
296
|
|
|
297
297
|
# libsqlite3-sys (pulled by persist's `sqlite` feature) links the SYSTEM libsqlite3
|
|
@@ -342,14 +342,14 @@ http-body-util = "0.1"
|
|
|
342
342
|
# The PQC primitives the realtime-A/V E2E bench drives directly: hybrid KEX
|
|
343
343
|
# (X25519 + ML-KEM-768) for the per-Link transit key, AES-256-GCM for the
|
|
344
344
|
# two-layer chunk seal. Same pin/features edge composes (tag parity).
|
|
345
|
-
ciris-crypto = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.
|
|
345
|
+
ciris-crypto = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.6.1", version = "13", features = ["hybrid-kex", "aes-gcm", "pqc-ml-dsa", "self-enc"] }
|
|
346
346
|
# Enable edge's OWN fountain codec (`codec-fountain`, L1-A) for the survival-floor
|
|
347
347
|
# proof — dev/test ONLY (feature unification applies to test/bench builds; the
|
|
348
348
|
# shipped wheel stays codec-free, since a relay forwards sealed symbols opaquely
|
|
349
349
|
# and never encodes/decodes). This lets tests/chaos_mesh.rs exercise the SUBSTRATE
|
|
350
350
|
# codec (`fountain_encode`/`fountain_decode`) directly — a real MEASURED proof,
|
|
351
351
|
# not a reference stand-in.
|
|
352
|
-
ciris-edge = { git = "https://github.com/CIRISAI/CIRISEdge", tag = "
|
|
352
|
+
ciris-edge = { git = "https://github.com/CIRISAI/CIRISEdge", tag = "v18.0.2", features = ["codec-fountain"] }
|
|
353
353
|
# Enable persist's TEST-ONLY genesis-seam (`test-genesis-seam`, CIRISPersist#387) for the
|
|
354
354
|
# accord ceremony tests (tests/accord.rs): `Engine::with_signer_pre_genesis` yields a clean
|
|
355
355
|
# engine with the HUMANITY_ACCORD genesis seed SKIPPED, so those tests can stand up their OWN
|
|
@@ -361,7 +361,7 @@ ciris-edge = { git = "https://github.com/CIRISAI/CIRISEdge", tag = "v17.4.1",
|
|
|
361
361
|
# without one. Pre-genesis is now a supported boot mode, not a test seam, and an Engine built
|
|
362
362
|
# that way reports `GenesisPosture::PreGenesis` while every ROOT_REQUIRING_GATES gate refuses
|
|
363
363
|
# with `NoConstitutionalRootYet`. A node that trusts nothing is not a node that checks nothing.
|
|
364
|
-
ciris-persist = { git = "https://github.com/CIRISAI/CIRISPersist", tag = "
|
|
364
|
+
ciris-persist = { git = "https://github.com/CIRISAI/CIRISPersist", tag = "v37.1.0" }
|
|
365
365
|
|
|
366
366
|
# The QA runner exercises the family/accord ceremony surfaces against a
|
|
367
367
|
# CONTROLLABLE roster — holders it can sign as. persist v31.0.0 made roster growth
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: ciris-server
|
|
3
|
-
Version: 0.5.
|
|
3
|
+
Version: 0.5.182
|
|
4
4
|
License-File: LICENSE
|
|
5
5
|
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.
|
|
6
6
|
Author-email: Eric Moore <eric@ciris.ai>
|
|
@@ -350,7 +350,7 @@ itself, while a quorum roots to `humanity-accord`. The charter is 2-of-2 over a
|
|
|
350
350
|
— a replicated row proves its own m-of-n rather than deferring to the bundle it
|
|
351
351
|
arrived in. Two humans to halt, two to legitimize.
|
|
352
352
|
|
|
353
|
-
Substrate pins: **persist
|
|
353
|
+
Substrate pins: **persist v37.1.0 / edge v18.0.2 / verify v13.6.1** — hybrid PQ
|
|
354
354
|
throughout, Registry-of-Record admission, drift-witnessed policy hashes. Edge
|
|
355
355
|
v15.7.x adds the realtime A/V spine (MLS X-Wing epoch keys, signed Welcome,
|
|
356
356
|
fragment ARQ); the server exercises publisher → relay → subscriber
|
|
@@ -339,7 +339,7 @@ itself, while a quorum roots to `humanity-accord`. The charter is 2-of-2 over a
|
|
|
339
339
|
— a replicated row proves its own m-of-n rather than deferring to the bundle it
|
|
340
340
|
arrived in. Two humans to halt, two to legitimize.
|
|
341
341
|
|
|
342
|
-
Substrate pins: **persist
|
|
342
|
+
Substrate pins: **persist v37.1.0 / edge v18.0.2 / verify v13.6.1** — hybrid PQ
|
|
343
343
|
throughout, Registry-of-Record admission, drift-witnessed policy hashes. Edge
|
|
344
344
|
v15.7.x adds the realtime A/V spine (MLS X-Wing epoch keys, signed Welcome,
|
|
345
345
|
fragment ARQ); the server exercises publisher → relay → subscriber
|
|
@@ -26,8 +26,8 @@ crate-type = ["cdylib", "rlib"]
|
|
|
26
26
|
#
|
|
27
27
|
# OQ-01 closure 2026-05-03: rlib primary, PyO3 cdylib via `python`
|
|
28
28
|
# feature for the deployed-lens cutover.
|
|
29
|
-
ciris-persist = { git = "https://github.com/CIRISAI/CIRISPersist", tag = "
|
|
30
|
-
ciris-edge = { git = "https://github.com/CIRISAI/CIRISEdge", tag = "
|
|
29
|
+
ciris-persist = { git = "https://github.com/CIRISAI/CIRISPersist", tag = "v37.1.0", version = "37", features = ["extract", "sqlite"] }
|
|
30
|
+
ciris-edge = { git = "https://github.com/CIRISAI/CIRISEdge", tag = "v18.0.2", version = "18", features = ["transport-http", "transport-reticulum"] }
|
|
31
31
|
|
|
32
32
|
# Keyring — relay mode (CIRISLensCore#10) loads its Edge transport-
|
|
33
33
|
# signing identity via `ciris_keyring::load_local_seed`. Edge's
|
|
@@ -37,16 +37,16 @@ ciris-edge = { git = "https://github.com/CIRISAI/CIRISEdge", tag = "v17.4.
|
|
|
37
37
|
# CIRISVerify tag persist + edge pin (v5.0.0 — CEG 1.0 / Agent 3.0 substrate
|
|
38
38
|
# release; MAJOR 4→5 but additive for lens-core) — single verify version.
|
|
39
39
|
# features mirror edge's keyring pin exactly.
|
|
40
|
-
ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.
|
|
40
|
+
ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.6.1", version = "13", features = ["software", "pqc-ml-dsa"] }
|
|
41
41
|
# verify-core for `fedcode::derive_key_id` — the lens seal path must stamp the
|
|
42
42
|
# DERIVED federation key_id (`derive_key_id(<alias>, <ed25519 pubkey>)`), the id
|
|
43
43
|
# `receive_and_persist` verifies against, NOT the bare `local_key_id` alias
|
|
44
44
|
# (CIRISServer#118; same class as the closed CIRISEdge#203). Single verify version.
|
|
45
|
-
ciris-verify-core = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.
|
|
45
|
+
ciris-verify-core = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.6.1", version = "13" }
|
|
46
46
|
# Crypto-DRY (CIRISServer#283 findings 3+5): route the hand-composed hybrid rule
|
|
47
47
|
# (event.rs) + the test-only trace verify (seal.rs) through the one crypto facade
|
|
48
48
|
# instead of a direct ed25519-dalek dep and a replicated binding.
|
|
49
|
-
ciris-crypto = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.
|
|
49
|
+
ciris-crypto = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v13.6.1", version = "13", features = ["pqc-ml-dsa"] }
|
|
50
50
|
|
|
51
51
|
# persist's `sqlite` feature: relay mode persists inbound batches via
|
|
52
52
|
# `Engine::receive_and_persist` + reads `Engine::sqlite_backend()` for
|
|
@@ -143,6 +143,53 @@ impl LensCore {
|
|
|
143
143
|
// CIRISEdge#363: 30s bootstrap link keepalive so links survive the
|
|
144
144
|
// Key/IdentityOccurrence anti-entropy exchange (clamped edge-side).
|
|
145
145
|
link_keepalive: Some(std::time::Duration::from_secs(30)),
|
|
146
|
+
// CIRISEdge#508 item (d). A lens relay is not the canonical that
|
|
147
|
+
// wedged, but it carries the same replication planes, and
|
|
148
|
+
// leviculum's 256 default is documented as sized for "small std
|
|
149
|
+
// platforms" with servers expected to override. Edge clamps this
|
|
150
|
+
// into 16..=65_536, so the value cannot escape its DoS bound.
|
|
151
|
+
//
|
|
152
|
+
// Capacity is HEADROOM, not a cure: #508's own priority order puts
|
|
153
|
+
// it LAST, behind the completion-mirror eviction and the single
|
|
154
|
+
// mutex that actually stall the consumer (leviculum#56-#59). It
|
|
155
|
+
// buys time in front of a stall; it does not prevent one.
|
|
156
|
+
control_channel_capacity: Some(4096),
|
|
157
|
+
// CIRISEdge#499 — a lens relay must stay reachable. `false` would
|
|
158
|
+
// make it point-to-point only, and a silent reachability change on
|
|
159
|
+
// upgrade is precisely what edge warns this flag can cause.
|
|
160
|
+
federation_visible: true,
|
|
161
|
+
// CIRISEdge#492 (v17.5.0) — the two legacy-path posture knobs. This
|
|
162
|
+
// relay uses the legacy path (`interfaces` is empty), so both apply.
|
|
163
|
+
//
|
|
164
|
+
// `None` on each reproduces pre-v17.5.0 behaviour EXACTLY, which is
|
|
165
|
+
// what an adopt should do: a substrate re-pin must not silently move
|
|
166
|
+
// a node's network posture. Both are deliberate opt-ins.
|
|
167
|
+
//
|
|
168
|
+
// `ifac: None` = an OPEN port. Not an oversight — turning IFAC on
|
|
169
|
+
// means a member-only port, and the passphrase for it is supposed to
|
|
170
|
+
// arrive through persist's `key_grant` TransitMembership scope. This
|
|
171
|
+
// repo has ZERO call sites for that surface, so enabling IFAC today
|
|
172
|
+
// would mean an operator distributing a shared secret by hand — the
|
|
173
|
+
// stopgap #492 exists to REPLACE. It becomes correct once we consume
|
|
174
|
+
// the grant surface, and that is its own cut.
|
|
175
|
+
ifac: None,
|
|
176
|
+
// `transit: Some(false)` — a DECLARED leaf port. Relay transport is
|
|
177
|
+
// limited to CIRIS peers as of this release, and a lens relay is not
|
|
178
|
+
// the CIRIS fabric node: it terminates traffic for its own role and
|
|
179
|
+
// relays for nobody.
|
|
180
|
+
//
|
|
181
|
+
// This is a posture decision made deliberately alongside the adopt,
|
|
182
|
+
// not a mechanical consequence of it. Before v17.5.0 the legacy path
|
|
183
|
+
// took leviculum's relay-by-default, so `enable_transport: false`
|
|
184
|
+
// above declared a leaf node whose port would still carry transit for
|
|
185
|
+
// strangers — the declaration and the behaviour disagreed, and only
|
|
186
|
+
// the arrival of this field made the gap expressible.
|
|
187
|
+
//
|
|
188
|
+
// `Some(false)` is not the same as the `None` default: a declared
|
|
189
|
+
// non-transit port never rebroadcasts announces and DROPS any relay
|
|
190
|
+
// crossing it, so peers stop building paths that expect transit here
|
|
191
|
+
// rather than building them and having them fail.
|
|
192
|
+
transit: Some(false),
|
|
146
193
|
};
|
|
147
194
|
|
|
148
195
|
// Auth bundle — wire the federation signer into the authenticated
|
|
@@ -10,14 +10,14 @@
|
|
|
10
10
|
#
|
|
11
11
|
# ─── RESOLVED ──────────────────────────────────────────────────────────────────
|
|
12
12
|
decimal_id claim_id repo path#symbol crate@version
|
|
13
|
-
3.1 CLM-nsproc-dimension CIRISServer src/compose_policy.rs#polarity_for ciris-server@v0.5.
|
|
14
|
-
4.4.2 CLM-nsproc-aggregation-policy CIRISServer src/compose_policy.rs#polarity_for ciris-server@v0.5.
|
|
15
|
-
4.4.3.4.3 CLM-nsproc-cohort-scope CIRISServer src/graph_config.rs#set_config ciris-server@v0.5.
|
|
16
|
-
4.2.2.1 CLM-nsproc-attestation-evidence CIRISServer src/hardware_attestation.rs#admit_hardware_class_against_root ciris-server@v0.5.
|
|
17
|
-
2.6.6.1 CLM-location CIRISServer src/location.rs#mint_location_proof ciris-server@v0.5.
|
|
18
|
-
2.6.6 CLM-canonicalization-cell CIRISServer src/location.rs#mint_location_proof ciris-server@v0.5.
|
|
19
|
-
3.4.5 CLM-capacity-score CIRISServer src/scorer.rs#score_and_emit ciris-server@v0.5.
|
|
20
|
-
3.3.7 CLM-consent-directed CIRISServer src/peer.rs#emit_replication_consent ciris-server@v0.5.
|
|
13
|
+
3.1 CLM-nsproc-dimension CIRISServer src/compose_policy.rs#polarity_for ciris-server@v0.5.182
|
|
14
|
+
4.4.2 CLM-nsproc-aggregation-policy CIRISServer src/compose_policy.rs#polarity_for ciris-server@v0.5.182
|
|
15
|
+
4.4.3.4.3 CLM-nsproc-cohort-scope CIRISServer src/graph_config.rs#set_config ciris-server@v0.5.182
|
|
16
|
+
4.2.2.1 CLM-nsproc-attestation-evidence CIRISServer src/hardware_attestation.rs#admit_hardware_class_against_root ciris-server@v0.5.182
|
|
17
|
+
2.6.6.1 CLM-location CIRISServer src/location.rs#mint_location_proof ciris-server@v0.5.182
|
|
18
|
+
2.6.6 CLM-canonicalization-cell CIRISServer src/location.rs#mint_location_proof ciris-server@v0.5.182
|
|
19
|
+
3.4.5 CLM-capacity-score CIRISServer src/scorer.rs#score_and_emit ciris-server@v0.5.182
|
|
20
|
+
3.3.7 CLM-consent-directed CIRISServer src/peer.rs#emit_replication_consent ciris-server@v0.5.182
|
|
21
21
|
#
|
|
22
22
|
# ─── DECLARED GAPS ─────────────────────────────────────────────────────────────
|
|
23
23
|
# Controls the Constitution attributes to this repo that are NOT enforced here.
|