# Changelog

> **This is the PUBLIC form of this artifact. Findings are listed in full, but the details of SECURITY findings — which rule fired, in which file, on which line, and how to fix it — are deliberately withheld, and any secret-scanner results are excluded entirely. Where detail is absent here it was REMOVED FOR PUBLICATION; it is not missing from the analysis. The complete artifact is available from the repository owner.**

## Score

- CAI 58 → 58 (+0.0)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 93 → 92 (-0.9)
- Architecture 89 → 89 (-0.3)
- Maturity 47 → 51 (+3.5)
- Readiness 74 → 68 (-6.3)
- Security 48 → 48 (-0.0)
- Performance 100 → 100 (+0.0)

## Resolved (5)

- Inconsistent factory method naming and parameter ordering. The Bigtable adapter exposes multiple 'open' variants that differ by optional parameters (token_source, hooks) but lack a unified builder pattern or consistent overloading strategy. Some methods take serializers, others take hooks, some take both, some take neither. This forces users to memorize specific method names for different configuration combinations rather than using a single fluent API.
- Inconsistent factory method naming compared to Bigtable. While similar to Bigtable, the SQLite adapter also suffers from multiple 'open' variants. However, the inconsistency is more pronounced because the Bigtable adapter has 5 open variants while SQLite has 3, and they don't map 1:1 (e.g., Bigtable has 'open_with_token_source' but SQLite does not have an equivalent 'open_with_token_source' method, instead relying on the connection object). This creates confusion when switching between storage backends.
- Inconsistent factory method naming. DynamoDB has 'open_with_serializers' and 'open', but lacks the 'open_with_hooks' variant that Bigtable and SQLite have. This asymmetry makes it difficult to write generic code that works across different storage backends, as the method to inject test hooks or custom serializers varies by implementation.
- Inconsistent factory method naming. Memory adapter uses 'with_serializers' (setter-style) and 'new' (constructor-style), while other adapters use 'open' or 'open_with_*'. This breaks the pattern of using 'open' for initialization across the library.
- Inconsistent method location. 'history_view' is a method on the EventStore implementations (Bigtable, SQLite) but is a method on the underlying Storage (MemoryStorage) rather than the EventStore wrapper. This inconsistency makes it unclear whether history_view is a high-level event store operation or a low-level storage operation, complicating the abstraction layer.

## New (22)

- Duplicated block (11 lines × 2) (conformance-runner/src/target_bigtable/scene.rs)
- Duplicated block (12 lines × 2) (lib/src/bigtable/backend.rs)
- Duplicated block (13 lines × 2) (conformance-runner/src/target_bigtable/execute.rs)
- Duplicated block (13 lines × 2) (conformance-runner/src/target_dynamodb/check_requests.rs)
- Duplicated block (21–22 lines × 2) (conformance-runner/src/target_bigtable/execute.rs)
- Duplicated block (22 lines × 2) (conformance-runner/src/target_bigtable/execute.rs)
- Duplicated block (4–7 lines × 3) (conformance-runner/src/target_bigtable/execute.rs)
- Duplicated block (5 lines × 2) (conformance-runner/src/target_bigtable/execute.rs)
- Duplicated block (5 lines × 2) (conformance-runner/src/target_bigtable/execute.rs)
- Duplicated block (5 lines × 2) (lib/src/bigtable/backend.rs)
- Duplicated block (5 lines × 2) (lib/src/spanner/configuration.rs)
- Duplicated block (6 lines × 2) (conformance-runner/src/target_bigtable/emulator.rs)
- Duplicated block (9 lines × 2) (lib/src/bigtable/backend.rs)
- Duplicated block (9–10 lines × 2) (lib/src/spanner/backend.rs)
- FaultPlan::register (cognitive 16) (conformance-runner/src/fault.rs)
- High: security finding (details withheld)
- Hotspot: conformance-runner/src/target_bigtable/execute.rs (conformance-runner/src/target_bigtable/execute.rs)
- event_store_adapter_conformance_rs::target_spanner::execute::run_in_scene (cognitive 33) (conformance-runner/src/target_spanner/execute.rs)
- event_store_adapter_conformance_rs::target_spanner::execute::run_in_scene (cyclomatic 19) (conformance-runner/src/target_spanner/execute.rs)
- event_store_adapter_rs::spanner::configuration::reconcile (cognitive 23) (lib/src/spanner/configuration.rs)
- …and 2 more

## Changes since last survey

- 16 commits — 14 feature/other, 2 fixes

## By area

- (root) — 7 commits
- lib/Cargo.toml — 4 commits
- conformance-runner/src — 1 commit
- conformance-runner/tests — 1 commit
- lib/src — 1 commit
- lib/tests — 1 commit
- test-utils/Cargo.toml — 1 commit

## Notable commits

- fix: fix(deps): testcontainers を astral-tokio-tar 除去後の上流修正に一時固定 (#350)
- fix: fix(test-utils): remove the direct bollard dependency and use the Docker CLI
- change: Disable Renovate bot by setting enabled to false
- change: chore(deny): allow the MIT-0 and Zlib licenses of jsonschema 0.60's dependencies (#347)
- change: chore(deps): Update Rust crate base64 to 0.23.0 (#345)
- change: chore(deps): Update Rust crate jsonschema to v0.58.6 (#266)
- change: chore(deps): Update Rust crate rusqlite to 0.41.0 (#340)
- change: chore: unify the README badges and license as MIT OR Apache-2.0 (#346)
- change: docs: add Rust contributor guide and bilingual design history
- change: docs: align the user documentation with the hub template and check it in CI (#339)
- change: feat: add Spanner storage with v5 conformance (#344)
- change: refactor(test): migrate Docker fixtures from testcontainers to dockertest
- change: test(conformance): run the FNV-1a 64 value cases on the Bigtable leg (#337)
- change: version up to v5.1.0
- change: version up to v5.1.1
- change: version up to v5.2.0

## Architecture

- Containers 0 added · 0 removed · contexts 1 added · 0 removed · edges 0 added · 0 removed

## Added bounded contexts (1)

- python
