# 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 43 → 41 (-1.9)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 67 → 65 (-2.4)
- Architecture 55 → 66 (+10.8)
- Maturity 49 → 76 (+27.4)
- Readiness 43 → 38 (-4.6)
- Security 33 → 24 (-9.0)
- Domain Modelling 100 → 100 (+0.0)
- Performance 100 → 100 (+0.0)

## Resolved (32)

- Critical CVE: [GHSA redacted] (pnpm-lock.yaml)
- Critical CVE: [GHSA redacted] (pnpm-lock.yaml)
- Documentation: no project overview (README.md)
- FileTooLong: group-chat/group-chat-events.ts (packages/command/domain/src/group-chat/group-chat-events.ts)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High: security finding (details withheld)
- High: security finding (details withheld)
- Inconsistent return type for delete operations. Deleting a GroupChat returns a GroupChatOutput (likely the deleted entity or status), but deleting a Message also returns a GroupChatOutput. This is semantically incorrect; deleting a message should return a MessageOutput or a generic void/success indicator, not a GroupChat output.
- Low CVE: [GHSA redacted] (pnpm-lock.yaml)
- Low CVE: [GHSA redacted] (pnpm-lock.yaml)
- Low coverage: packages/command/domain/src/group-chat/group-chat-errors.ts (packages/command/domain/src/group-chat/group-chat-errors.ts)
- Medium CVE: [GHSA redacted] (pnpm-lock.yaml)
- Medium CVE: [GHSA redacted] (pnpm-lock.yaml)
- Medium CVE: [GHSA redacted] (pnpm-lock.yaml)
- No assertions: test (packages/query/interface-adaptor/src/index.test.ts)
- Outdated (npm): @aws-sdk/client-dynamodb
- Outdated (npm): @aws-sdk/client-dynamodb-streams
- …and 12 more

## New (18)

- Dependency hygiene PARTLY measured — npm pinning read, dependency currency not (registry.npmjs.org unreachable)
- Deprecated: @google-cloud/opentelemetry-resource-util (pnpm-lock.yaml)
- Deprecated: @smithy/core (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High CVE: [GHSA redacted] (pnpm-lock.yaml)
- High IaC: WD-COMPOSE-0002 (tools/docker-compose/docker-compose-applications.yml)
- High: security finding (details withheld)
- Low CVE: [GHSA redacted] (pnpm-lock.yaml)
- Medium CVE: [GHSA redacted] (pnpm-lock.yaml)
- Medium CVE: [GHSA redacted] (pnpm-lock.yaml)
- Medium CVE: [GHSA redacted] (pnpm-lock.yaml)
- Medium CVE: [GHSA redacted] (pnpm-lock.yaml)
- Medium CVE: [GHSA redacted] (pnpm-lock.yaml)
- No dependency advisory monitoring
- stream-recovery.processStream (cognitive 47) (packages/rmu/src/stream-recovery.ts)
- stream-recovery.processStream (cyclomatic 18) (packages/rmu/src/stream-recovery.ts)

## Changes since last survey

- 14 commits — 14 feature/other, 0 fixes

## By area

- (root) — 5 commits
- packages/rmu — 4 commits
- packages/command — 2 commits
- packages/bootstrap — 1 commit
- packages/query — 1 commit
- tools/e2e-test — 1 commit

## Notable commits

- change: Disable Renovate bot by setting enabled to false
- change: [codex] Renovate PRでフォーマット補正を走らせる (#823)
- change: chore(deps): Update dependency @google-cloud/functions-framework to v5 (#819)
- change: chore(deps): Update dependency @types/aws-lambda to v8.10.162 (#824)
- change: chore(deps): Update dependency ts-jest to v29.4.12 (#815)
- change: feat: adapt the read api to the ESA v5 read model
- change: feat: adapt write api to ESA v5 envelope api (#832)
- change: feat: add DLQ for payload decrypt failures and SQS notify transport (#839)
- change: feat: add Lambda RMU startup resync and SQS recovery worker (#841)
- change: feat: expand last_processed_sequence_number to BIGINT (T-9) (#843)
- change: feat: implement rmu recovery with retry, dlq and resync (#837)
- change: feat: switch js rmu to aggregate head streams (#834)
- change: feat: update ESA to v5.2.0 and adapt 3-table layout
- change: test: align localstack e2e with ESA v5 three-table setup (#835)
