Merge branch 'refactor/review-followup': 리뷰 후속 Wave 1–3(보안·정합성·구조)

2026-09-24 리뷰 두 건의 후속 반영. Wave 1(보안·데이터), Wave 2(정합성), Wave 2.5, Wave 3(구조) 완료.
현황표 docs/reviews/2026-09-25-review-followup-status.md: 완료 606 · 해당 없음 133 · 보류 5 · 남음 173(W4 테스트 규칙 63 · W5 문서 110).
Wave 3 종료 검증 전부 통과(check · ci · mainCheck · integrationCheck · build-logic · optional-platforms · releaseCheck).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
donghyeon-ka
2026-09-29 17:02:03 +09:00
co-authored by Claude Opus 5.5
5247 changed files with 101418 additions and 245917 deletions
-63
View File
@@ -1,63 +0,0 @@
name: reusable-gradle
# One place that knows how a Gradle job starts.
#
# Every job in this repository opened with the same preamble: checkout, a three-line pinned
# wrapper-validation step, then the JDK/cache action. The wrapper step is gone (setup-gradle
# validates wrappers itself), and this workflow removes the rest of the repetition for the jobs whose
# only variation is the Gradle command they run.
#
# Jobs that need service containers, a matrix, artifact uploads or per-job env stay written out with
# `./.github/actions/setup-gradle-java`, because expressing those through `workflow_call` inputs
# means encoding YAML inside strings — which is how a "shared" workflow becomes less readable than
# the duplication it replaced.
on:
workflow_call:
inputs:
tasks:
description: The Gradle task list, whitespace-separated.
required: true
type: string
gradle-args:
description: Flags appended after the task list.
required: false
type: string
default: "--stacktrace"
working-directory:
description: Directory the wrapper is invoked from.
required: false
type: string
default: src
timeout-minutes:
required: false
type: number
default: 30
continue-on-error:
description: Run the job as an advisory signal rather than a gate.
required: false
type: boolean
default: false
permissions:
contents: read
jobs:
gradle:
runs-on: ubuntu-latest
timeout-minutes: ${{ inputs.timeout-minutes }}
continue-on-error: ${{ inputs.continue-on-error }}
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Run ${{ inputs.tasks }}
working-directory: ${{ inputs.working-directory }}
env:
GRADLE_TASKS: ${{ inputs.tasks }}
GRADLE_ARGS: ${{ inputs.gradle-args }}
run: |
set -euo pipefail
# Word-split on purpose: both inputs are task/flag lists. They come from this repository's
# own workflow files, never from a pull request.
# shellcheck disable=SC2086
./gradlew ${GRADLE_TASKS} ${GRADLE_ARGS}
+37
View File
@@ -0,0 +1,37 @@
name: build-logic
# The included build's own tests (TestKit for the convention plugins, unit tests for the verifiers).
# The main task graph does not reach them, so they run here — and only when a pull request touches
# the included build or the catalog it reads. build-tools was folded into build-logic (review
# 2026-09-24 BUILD-O3-6).
on:
pull_request:
paths:
- "src/build-logic/**"
- "src/gradle/**"
- ".github/workflows/build-logic.yml"
push:
branches: ["main"]
paths:
- "src/build-logic/**"
- "src/gradle/**"
- ".github/workflows/build-logic.yml"
workflow_dispatch:
permissions:
contents: read
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
jobs:
included-builds:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Test the build-logic convention plugins
working-directory: src
run: ./gradlew -p build-logic test --stacktrace
+37 -159
View File
@@ -30,18 +30,6 @@ jobs:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- name: Require the committed public-path security baseline
run: |
set -euo pipefail
readonly snapshot='docs/security/public-paths-snapshot.txt'
if [[ ! -s "${snapshot}" ]]; then
echo "::error::${snapshot} is missing or empty. CI must not let verifyPublicPathSnapshot create its own first-run baseline."
exit 1
fi
if ! git ls-files --error-unmatch "${snapshot}" >/dev/null 2>&1; then
echo "::error::${snapshot} exists locally but is not committed."
exit 1
fi
- uses: ./.github/actions/setup-gradle-java
- name: Export the live Gradle verification task map
working-directory: src
@@ -54,47 +42,16 @@ jobs:
if-no-files-found: error
# `ci`, not `check`. A leaf's `check` is that leaf's — compile, its tests, Spotless, Checkstyle
# and Error Prone — and the repository-wide gates are named tasks of their own:
# ci = every leaf check + architectureCheck + qualityCheck + configContractCheck + qualificationCheck
# so CI runs strictly more than it used to while `./gradlew :domain-core:check` runs strictly
# less.
# ci = every leaf check + architectureCheck + qualityCheck
# A leaf's `check` includes its API surface verification (owner decision 20). The main-branch
# stage (`mainCheck`: environment contract, full-boot qualification, public-path baseline,
# transport and messaging lanes, document-contract lanes) runs in integration-main.yml.
- name: Run the pull-request gate
working-directory: src
run: ./gradlew :ci :verifyPublicPathSnapshot :verifyDependencyLocks --warning-mode=fail --stacktrace
# Named as its own step because nothing else runs it: `check` does not depend on
# graphqlStableTest, so the lane's required-class guard — the check that its module-boundary
# suite has not silently stopped being discovered — would protect nothing in CI.
- name: Qualify the GraphQL Stable lane
working-directory: src
run: ./gradlew :adapter:inbound:graphql:graphqlStableTest --stacktrace
- name: Qualify opt-in inbound transports without skips
working-directory: src
run: ./gradlew :conditionalTransportQualification --stacktrace
run: ./gradlew :ci :verifyDependencyLocks --warning-mode=fail --stacktrace
- name: Verify Compose profile contracts render exactly as declared
run: bash scripts/verify-compose-profile-contracts.sh
build-logic:
# Included-build tests are independent of the main project task graph. Running them as a
# separate blocking job keeps plugin TestKit work off the quality-gates critical path.
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Test the build-logic convention plugins
working-directory: src
run: ./gradlew -p build-logic test --stacktrace
build-tools:
# build-tools is an included build, so its verifier tests are not reached by the main :ci task.
# These tests protect env/JPA/messaging/Mongo/notification evidence parsers; a broken verifier
# must fail the pull-request gate rather than silently bless bad evidence.
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Test the build-time verifier plugins
working-directory: src
run: ./gradlew -p build-tools test --stacktrace
sample-portfolio:
# The sample is excluded from production architecture/runtime membership policy, but it is still
# the reference implementation adopters copy. Compile/test/OpenAPI drift must therefore block PRs.
@@ -106,19 +63,6 @@ jobs:
working-directory: src
run: ./gradlew :sample-portfolio:check --stacktrace
redis-sdk:
# Milestone A of the Redis wrapper/typed API plan: policy catalog, typed API parity, permit
# provenance, connection isolation, and the executor guard. There is no real-server lane yet.
#
# `verifyConfigurationPropertiesProcessor` used to be in this list. It is deleted: the parity it
# enforced — a leaf declares Spring's configuration processor exactly when it owns
# @ConfigurationProperties — is now what applying `ca.spring-config` means.
# `verifyEnvKeys` is no longer named here either; it belongs to :app-bootstrap and runs through
# `configContractCheck`, which the quality-gates job covers.
uses: ./.github/workflows/_reusable-gradle.yml
with:
tasks: ":shared-contract:test --tests '*EdgeRateLimitProviderNeutralContractTest'"
optional-platforms:
runs-on: ubuntu-latest
steps:
@@ -128,104 +72,46 @@ jobs:
working-directory: src
run: ./gradlew -p optional-platforms ci --stacktrace
configuration-cache:
# Two questions, and they are not the same question.
#
# The first is whether every task in the repository-wide gates can be *stored*. That is a
# property of the task graph, so `--dry-run` answers it for the whole of `ci`,
# `integrationCheck` and `releaseCheck` in seconds, and it is the question this job used to
# duck: it checked two leaves, because four tasks elsewhere held a live `Configuration` in
# their state and could not be serialised at all. They hold resolved root components now, so
# the honest scope is all three gates rather than two leaves.
#
# The second is whether a stored entry is actually *reused* and the build still executes its
# work. `--dry-run` cannot answer that, so the executing check stays — on the two core leaves,
# because doubling a full `ci` run to prove reuse would cost more than the guarantee is worth.
# gRPC schema policy (owner decision 18). protoc compiles src/grpc/grpc-contract inside the
# optional-platforms build above; lint and breaking-change policy belong to Buf, configured by
# buf.yaml next to the schema. Buf is a native binary rather than a Maven artifact, so it runs here
# and not inside Gradle — and nothing in the repository re-implements its rules.
grpc-proto-buf:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Require every repository-wide gate to be storable
working-directory: src
shell: bash
run: |
set -euo pipefail
for gate in ci integrationCheck releaseCheck; do
echo "::group::${gate}"
./gradlew "${gate}" --dry-run \
--configuration-cache --configuration-cache-problems=fail --stacktrace
output="$({ ./gradlew "${gate}" --dry-run \
--configuration-cache --configuration-cache-problems=fail --stacktrace; } 2>&1)"
printf '%s\n' "${output}"
echo '::endgroup::'
grep -Fq 'Reusing configuration cache.' <<<"${output}" || {
echo "::error::Gradle did not reuse the configuration cache for ${gate}."
exit 1
}
done
- name: Store configuration cache for the everyday core build
working-directory: src
run: >-
./gradlew
:domain-core:check
:application-core:check
--configuration-cache
--configuration-cache-problems=fail
--stacktrace
- name: Require configuration-cache reuse
working-directory: src
shell: bash
run: |
set -euo pipefail
output="$({ ./gradlew :domain-core:check :application-core:check \
--configuration-cache --configuration-cache-problems=fail --stacktrace; } 2>&1)"
printf '%s\n' "${output}"
grep -Fq 'Reusing configuration cache.' <<<"${output}" || {
echo '::error::Gradle did not reuse the configuration cache on the second identical build.'
exit 1
}
jpa-candidate-evidence:
runs-on: ubuntu-latest
timeout-minutes: 20
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Produce zero-skip JPA candidate manifests
working-directory: src
run: >-
./gradlew
:adapter:outbound:persistence-jpa:verifyJpaCandidateEvidence
--stacktrace
- name: Retain content-addressed JPA candidate manifests
uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # actions/upload-artifact@v7.0.1
with:
name: jpa-candidate-evidence-${{ github.sha }}
path: src/adapter/outbound/persistence-jpa/build/jpa-evidence/manifests
if-no-files-found: error
retention-days: 14
# Advisory. The quarantine bucket runs so a flaky test is still executed and reported; it never
# blocks. The 14-day sunset registry that used to make an expired quarantine entry a build failure
# is gone — it was a 250-line YAML-and-Java parser guarding a registry with zero entries.
quarantine:
uses: ./.github/workflows/_reusable-gradle.yml
with:
tasks: ":quarantineTest"
gradle-args: "--stacktrace"
continue-on-error: true
# buf breaking reads the baseline schema from Git history.
fetch-depth: 0
- uses: bufbuild/buf-action@85aebf73123b5c15fd5528aaecbf9129cddf7fa7 # bufbuild/buf-action@v1.6.0
with:
version: 1.73.0
setup_only: true
- name: Lint the gRPC schema
working-directory: src/grpc/grpc-contract
run: buf lint
- name: Refuse a breaking change to the gRPC schema
working-directory: src/grpc/grpc-contract
env:
# Pull request: the target branch. Push: the commit this push replaced.
BASELINE: ${{ github.event_name == 'pull_request' && format('origin/{0}', github.base_ref) || github.event.before }}
run: |
set -euo pipefail
baseline_commit="$(git rev-parse --verify --quiet "${BASELINE}^{commit}" || true)"
if [[ -z "${baseline_commit}" ]] \
|| ! git cat-file -e "${baseline_commit}:src/grpc/grpc-contract/buf.yaml" 2>/dev/null; then
# The first change that introduces the module has nothing to be compatible with.
echo "::notice::grpc-proto-buf: baseline ${BASELINE} has no src/grpc/grpc-contract/buf.yaml; breaking check skipped."
exit 0
fi
buf breaking --against "../../../.git#ref=${baseline_commit},subdir=src/grpc/grpc-contract"
release-gate:
needs:
- quality-gates
- build-logic
- build-tools
- sample-portfolio
- redis-sdk
- jpa-candidate-evidence
- optional-platforms
- configuration-cache
- grpc-proto-buf
if: always()
runs-on: ubuntu-latest
permissions:
@@ -234,24 +120,16 @@ jobs:
- name: Require every current blocking job to succeed
env:
QUALITY_RESULT: ${{ needs.quality-gates.result }}
BUILD_LOGIC_RESULT: ${{ needs.build-logic.result }}
BUILD_TOOLS_RESULT: ${{ needs.build-tools.result }}
SAMPLE_RESULT: ${{ needs.sample-portfolio.result }}
REDIS_RESULT: ${{ needs.redis-sdk.result }}
JPA_CANDIDATE_RESULT: ${{ needs.jpa-candidate-evidence.result }}
OPTIONAL_PLATFORMS_RESULT: ${{ needs.optional-platforms.result }}
CONFIGURATION_CACHE_RESULT: ${{ needs.configuration-cache.result }}
GRPC_PROTO_BUF_RESULT: ${{ needs.grpc-proto-buf.result }}
run: |
set -euo pipefail
for result in \
"${QUALITY_RESULT}" \
"${BUILD_LOGIC_RESULT}" \
"${BUILD_TOOLS_RESULT}" \
"${SAMPLE_RESULT}" \
"${REDIS_RESULT}" \
"${JPA_CANDIDATE_RESULT}" \
"${OPTIONAL_PLATFORMS_RESULT}" \
"${CONFIGURATION_CACHE_RESULT}"; do
"${GRPC_PROTO_BUF_RESULT}"; do
if [[ "${result}" != "success" ]]; then
echo "::error::release-gate: required job result was ${result}"
exit 1
@@ -1,122 +0,0 @@
name: fileserver-certification
# The certification a release must clear. Its job list is deliberately the same shape as the support
# matrix: nothing may be advertised at a support level whose evidence job is absent here.
#
# Named "certification", not "release", and the name is the point. This workflow proves a storage
# topology, a support matrix and a telemetry redaction claim. It deploys nothing and holds no cluster
# credential. Calling it `fileserver-release.yml` read as if GitHub Actions released the fileserver,
# which is the CI/CD boundary this repository has now fixed in docs/ci-cd/boundary.md: GitHub Actions
# tests, scans and publishes artifacts; Argo CD deploys.
#
# It used to be workflow_dispatch only, which made that sentence false: the four jobs below are the
# only place the fileserver support matrix, the PVC manifest and the telemetry redaction proof are
# checked, and a release tag reached none of them unless somebody remembered to press a button.
#
# `v*` is the only release tag. The adapter-scoped `fileserver-v*` pattern is gone: this repository
# has one deployable unit (app-bootstrap), so an adapter-scoped tag could only ever run a subset of
# the release gates and call the result a release — the tag-namespace split that release.yml exists
# to end.
#
# These four jobs stay in their own file, and not in release.yml, for one mechanical reason:
# FileserverDocumentationCoverageTest reads job ids out of `.github/workflows/fileserver-*.yml` and
# requires every `fileserver-...` job docs/fileserver/support-matrix.md names to be defined in one
# of them. Renaming the file or moving these jobs needs that document changed in the same change.
on:
push:
tags:
- "v*"
workflow_dispatch:
permissions:
contents: read
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: false
jobs:
fileserver-full-verification:
runs-on: ubuntu-latest
timeout-minutes: 60
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Run the architecture-wide dependency and module verification
working-directory: src
run: >-
./gradlew
:verifyCleanArchitectureDependencies
--stacktrace
- name: Run the complete fileserver suite across every leaf
working-directory: src
run: >-
./gradlew
:application-core:check
:adapter:inbound:web:check
:adapter:outbound:fileserver:check
--stacktrace
fileserver-documentation-gate:
runs-on: ubuntu-latest
timeout-minutes: 20
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Prove every support claim maps to a job and every endpoint is documented
working-directory: src
run: >-
./gradlew
:app-bootstrap:test --tests '*FileserverDocumentationCoverageTest'
--stacktrace
fileserver-pvc-certification:
runs-on: ubuntu-latest
timeout-minutes: 45
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
# This job checks the manifest, and only the manifest. It deliberately does not apply anything
# to a cluster.
#
# There used to be a second step here that applied the job to a release cluster when
# secrets.FILESERVER_PVC_KUBECONFIG was set and `exit 0`-ed with a ::warning:: when it was
# not. With no secret configured — which is every fork of this template and was this
# repository — the step printed a warning and the job went green under the name
# "fileserver-pvc-certification", so a release read as ReadWriteOnce-certified against a
# cluster nothing had ever touched. It also wrote a `certified` output that no job, step or
# script in this repository read.
#
# The cluster result comes from an operator running infra/fileserver/kubernetes/
# pvc-certification-job.yaml against a real cluster and recording it in
# docs/fileserver/storage-certification.md. That is registered as
# docs/fileserver/storage-certification.md, and the absence of a cluster result is stated
# there rather than hidden behind a green check.
- name: Check the certification manifest still says what the claim depends on
run: |
set -euo pipefail
manifest=infra/fileserver/kubernetes/pvc-certification-job.yaml
test -f "$manifest"
grep -q 'kind: PersistentVolumeClaim' "$manifest"
grep -q 'kind: Job' "$manifest"
# ReadWriteMany is explicitly not claimed; a manifest that quietly widened the access
# mode would certify a topology the support matrix says is uncertified.
grep -q 'ReadWriteOnce' "$manifest"
! grep -q 'ReadWriteMany' "$manifest"
fileserver-sensitive-telemetry-scan:
runs-on: ubuntu-latest
timeout-minutes: 20
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Prove telemetry carries no filename, path, or raw identifier
working-directory: src
run: >-
./gradlew
:application-core:test --tests '*FileserverObservabilityTest'
--stacktrace
+2 -2
View File
@@ -49,7 +49,7 @@ jobs:
run: >-
./gradlew
:adapter:outbound:fileserver:test --tests '*CrashRecoveryMatrixTest'
:application-core:test --tests '*FileReconciliationServiceTest'
:application-fileserver:test --tests '*FileReconciliationServiceTest'
--rerun-tasks
--stacktrace
@@ -82,7 +82,7 @@ jobs:
working-directory: src
run: >-
./gradlew
:application-core:test --tests '*MultiInstanceWriterLeaseTest'
:application-fileserver:test --tests '*MultiInstanceWriterLeaseTest'
--rerun-tasks
--stacktrace
+13 -9
View File
@@ -8,9 +8,11 @@ on:
workflow_dispatch:
pull_request:
paths:
- 'src/application-core/src/**/fileserver/**'
- 'src/adapter/inbound/web/src/**/fileserver/**'
- 'src/application-fileserver/**'
- 'src/adapter/inbound/web-fileserver/**'
- 'src/adapter/outbound/fileserver/**'
- 'src/adapter/outbound/persistence-fileserver/**'
- 'src/composition/fileserver-platform/**'
- 'src/adapter/outbound/persistence-jpa/src/**/fileserver/**'
- 'src/app-bootstrap/src/**/fileserver/**'
- 'docs/fileserver/**'
@@ -45,12 +47,15 @@ jobs:
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Run the fileserver application and architecture suites
# The architecture half of this claim is ci-quality-gates.yml's `architectureCheck`, which runs
# the whole ArchUnit suite on the same pull request; a filtered second run here was the repeat
# review BUILD-중복-6 removed.
- name: Run the fileserver application and assembly suites
working-directory: src
run: >-
./gradlew
:application-core:test
:app-bootstrap:architectureTest --tests '*Fileserver*'
:application-fileserver:test
:composition:fileserver-platform:test
--stacktrace
@@ -74,11 +79,11 @@ jobs:
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Run the servlet and reactive transport contracts
- name: Run the servlet transport contracts
working-directory: src
run: >-
./gradlew
:adapter:inbound:web:test
:adapter:inbound:web-fileserver:test
--stacktrace
@@ -92,7 +97,7 @@ jobs:
working-directory: src
run: >-
./gradlew
:adapter:inbound:web:test --tests '*FileserverHardeningContractTest'
:adapter:inbound:web-fileserver:test --tests '*FileserverHardeningContractTest'
:adapter:outbound:fileserver:test --tests '*PhysicalPathResolverTest'
--stacktrace
@@ -108,6 +113,5 @@ jobs:
run: >-
./gradlew
:adapter:outbound:fileserver:test --tests '*LargeFileBoundedMemoryTest'
:adapter:inbound:web:test --tests '*DataBufferReleaseTest'
--stacktrace
+94 -65
View File
@@ -15,21 +15,20 @@ name: integration-main
# shared. They now run on every push to main as well as nightly, which is strictly more often
# than before.
#
# 2. Lanes that were registered in Gradle and invoked by nothing. Ten Gradle tasks — six MongoDB
# container lanes, app-bootstrap's Testcontainers `integrationTest`, and the three messaging
# evidence tasks that `verifyMessagingContracts` reaches — existed, failed closed, and executed
# in no workflow. A lane nobody runs is not coverage; it is a file that looks like coverage. They
# 2. Lanes that were registered in Gradle and invoked by nothing — the MongoDB container lanes and
# app-bootstrap's Testcontainers `integrationTest` — existed, failed closed, and executed in no
# workflow. A lane nobody runs is not coverage; it is a file that looks like coverage. They
# are here rather than in stage 1 because every one of them either starts containers or re-runs
# suites the PR gate already covers, and the pull-request budget is minutes for the whole gate.
#
# What is deliberately NOT here: the web and WebSocket "Advanced capability" nightly lanes that used
# to exist as web-advanced-nightly.yml and websocket-advanced-nightly.yml. Both leaves' build files
# say it outright — "They also run inside `test`, deliberately ... excluding them from the PR gate to
# make this lane look meaningful would mean the PR gate stopped covering a fifth of the leaf" — so
# `webAdvancedTest` and `websocketAdvancedTest` select tagged tests that `:<leaf>:test` already runs,
# and `:<leaf>:test` runs inside the root `check` on every pull request and every push to main. The
# strict lanes themselves survive in release.yml, where their fail-on-nothing-discovered guard is
# worth a job.
# What is deliberately NOT here: the web "Advanced capability" nightly lane that used to exist as
# web-advanced-nightly.yml (websocket-advanced-nightly.yml went with the websocket Advanced code,
# deleted 2026-09-25). The web leaf's build file says it outright — "They also run inside `test`,
# deliberately ... excluding them from the PR gate to make this lane look meaningful would mean the
# PR gate stopped covering a fifth of the leaf" — so `webAdvancedTest` selects tagged tests that
# `:<leaf>:test` already runs, and `:<leaf>:test` runs inside the root `check` on every pull request
# and every push to main. The strict lane itself survives in release.yml, where its
# fail-on-nothing-discovered guard is worth a job.
on:
push:
@@ -58,6 +57,77 @@ concurrency:
# answer: does this link resolve.
jobs:
# The main-branch stage of the Gradle gates (`:mainCheck`): the environment contract, full-boot
# qualification, the sample web contract, the public-path baseline, the conditional transport
# lanes, the messaging contract lanes and each leaf's document-contract lanes. API surfaces are
# in the pull-request `check` (owner decision 20). The rest left the pull-request gate (review
# 2026-09-24 BUILD, item 12); none of them is deleted.
main-check:
runs-on: ubuntu-latest
timeout-minutes: 60
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- name: Require the committed public-path security baseline
run: |
set -euo pipefail
readonly snapshot='docs/security/public-paths-snapshot.txt'
if [[ ! -s "${snapshot}" ]] || ! git ls-files --error-unmatch "${snapshot}" >/dev/null 2>&1; then
echo "::error::${snapshot} is missing, empty or not committed; verifyPublicPathSnapshot must not create its own baseline."
exit 1
fi
- uses: ./.github/actions/setup-gradle-java
- name: Run the main-branch stage
working-directory: src
run: ./gradlew :mainCheck --warning-mode=fail --stacktrace
# Two questions. Can every task in the repository-wide gates be *stored* (a property of the task
# graph, so `--dry-run` answers it for all of them in seconds)? And is a stored entry *reused* while
# the build still executes its work (checked on the two core leaves)?
configuration-cache:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Require every repository-wide gate to be storable
working-directory: src
shell: bash
run: |
set -euo pipefail
for gate in ci mainCheck integrationCheck releaseCheck; do
echo "::group::${gate}"
./gradlew "${gate}" --dry-run \
--configuration-cache --configuration-cache-problems=fail --stacktrace
output="$({ ./gradlew "${gate}" --dry-run \
--configuration-cache --configuration-cache-problems=fail --stacktrace; } 2>&1)"
printf '%s\n' "${output}"
echo '::endgroup::'
grep -Fq 'Reusing configuration cache.' <<<"${output}" || {
echo "::error::Gradle did not reuse the configuration cache for ${gate}."
exit 1
}
done
- name: Store configuration cache for the everyday core build
working-directory: src
run: >-
./gradlew
:domain-core:check
:application-core:check
--configuration-cache
--configuration-cache-problems=fail
--stacktrace
- name: Require configuration-cache reuse
working-directory: src
shell: bash
run: |
set -euo pipefail
output="$({ ./gradlew :domain-core:check :application-core:check \
--configuration-cache --configuration-cache-problems=fail --stacktrace; } 2>&1)"
printf '%s\n' "${output}"
grep -Fq 'Reusing configuration cache.' <<<"${output}" || {
echo '::error::Gradle did not reuse the configuration cache on the second identical build.'
exit 1
}
# Load, abuse and graceful shutdown measure behaviour that degrades gradually rather than breaking
# outright — which is exactly the kind of regression a per-PR gate never catches.
web-load-abuse-and-shutdown:
@@ -72,7 +142,6 @@ jobs:
./gradlew
:adapter:inbound:web:test
:adapter:inbound:web:webJettyCompatTest
:adapter:inbound:web:webFluxContractTest
--stacktrace
- name: Publish the test reports
@@ -181,40 +250,6 @@ jobs:
path: src/adapter/outbound/persistence-mongo/build/reports/tests/
if-no-files-found: warn
# The messaging contract evidence DAG. `verifyMessagingContracts` is the root of a chain that ran
# nowhere: it depends on four production qualification tasks (application-core,
# shared-contract and two in adapter:outbound:messaging), each of which depends on
# `prepareMessagingContractEvidence`; it is finalizedBy
# `validateMessagingContractsEvidenceManifestSchema`; and it depends on
# `validateMessagingJsonSchemaV1EvidenceManifestSchema`, which depends on
# `verifyMessagingJsonSchemaV1`. Strict qualification tasks are registered outside `check` by
# design (ca.strict-qualification.gradle), so none of the seven was reachable from any workflow.
#
# The schema validators are the part that matters. They re-read the manifest bytes the run just
# wrote and validate them against config/messaging/evidence/build-evidence-manifest-v1.schema.json
# — a manifest that claims a qualification nobody executed is exactly the failure they exist to
# catch, and until now nothing executed them either.
#
# Stage 2 rather than stage 1: no containers, but it runs four qualification suites across three
# leaves plus two JavaExec validators, and the tests it re-runs are already inside the PR gate's
# `check`. What this job adds is the evidence manifest, which is a main-branch artifact.
messaging-contract-evidence:
runs-on: ubuntu-latest
timeout-minutes: 30
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Qualify the messaging contract, catalog, binding and schema evidence
working-directory: src
run: ./gradlew :verifyMessagingContracts --stacktrace
- name: Publish the messaging evidence manifest
if: always()
uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # actions/upload-artifact@v4.6.2
with:
name: messaging-contract-evidence
path: src/build/messaging-evidence/
if-no-files-found: warn
# app-bootstrap's Testcontainers lane. The leaf gave it a source set of its own precisely so that
# `./gradlew :app-bootstrap:test` would not require a Docker daemon — and the consequence nobody
# closed is that a source set outside `test` is also outside `check`, so the real-PostgreSQL
@@ -241,15 +276,9 @@ jobs:
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: RabbitMQ transport contract
- name: Messaging outbox, inbox and admin-journal PostgreSQL contracts
working-directory: src
run: ./gradlew :messaging:messaging-rabbit:integrationTest --stacktrace
- name: Inbox PostgreSQL contract
working-directory: src
run: ./gradlew :messaging:messaging-inbox-jdbc-postgresql:integrationTest --stacktrace
- name: Outbox PostgreSQL contract
working-directory: src
run: ./gradlew :messaging:messaging-outbox-jdbc-postgresql:integrationTest --stacktrace
run: ./gradlew :messaging:messaging-reliability-jdbc-postgresql:integrationTest --stacktrace
- name: Messaging starter Kafka round trip
working-directory: src
run: ./gradlew :messaging:messaging-spring-boot-starter:integrationTest --stacktrace
@@ -258,7 +287,7 @@ jobs:
run: ./gradlew :adapter:outbound:objectstorage:integrationTest --stacktrace
- name: Standalone sample PostgreSQL contract
working-directory: src
run: ./gradlew :sample-portfolio:integrationTest --stacktrace
run: ./gradlew :sample-portfolio:integrationTestLaneCheck --stacktrace
# These six PostgreSQL contracts moved from app-bootstrap into persistence-jpa. They are named
# directly instead of relying on readiness-card membership: provider ownership and evidence
@@ -274,21 +303,18 @@ jobs:
- name: Distributed lock contract
working-directory: src
run: ./gradlew :adapter:outbound:persistence-jpa:postgresqlDistributedLockIntegrationTest --stacktrace
- name: Idempotency unique-scope contract
working-directory: src
run: ./gradlew :adapter:outbound:persistence-jpa:postgresqlIdempotencyUniqueScopeIntegrationTest --stacktrace
- name: Integer lock migration compatibility
working-directory: src
run: ./gradlew :adapter:outbound:persistence-jpa:postgresqlIntLockMigrationCompatibilityIntegrationTest --stacktrace
- name: Legacy outbox transactional append
- name: Outbox transactional append
working-directory: src
run: ./gradlew :adapter:outbound:persistence-jpa:postgresqlLegacyOutboxAppendTransactionalIntegrationTest --stacktrace
- name: Legacy outbox concurrent relay
run: ./gradlew :adapter:outbound:persistence-jpa:postgresqlOutboxAppendTransactionalIntegrationTest --stacktrace
- name: Outbox concurrent relay
working-directory: src
run: ./gradlew :adapter:outbound:persistence-jpa:postgresqlLegacyOutboxConcurrentRelayIntegrationTest --stacktrace
- name: Legacy outbox row lifecycle
run: ./gradlew :adapter:outbound:persistence-jpa:postgresqlOutboxConcurrentRelayIntegrationTest --stacktrace
- name: Outbox row lifecycle
working-directory: src
run: ./gradlew :adapter:outbound:persistence-jpa:postgresqlLegacyOutboxRowLifecycleIntegrationTest --stacktrace
run: ./gradlew :adapter:outbound:persistence-jpa:postgresqlOutboxRowLifecycleIntegrationTest --stacktrace
# The optional gRPC platform build declares one strict INTEGRATION lane —
# `grpc-operation-ledger-jpa:integrationTest`, which certifies the atomic
@@ -323,6 +349,9 @@ jobs:
# main and nightly; a partial lane run is reproduction only and cannot satisfy this job. The count
# is not written here on purpose — a number in prose drifts the moment a lane is added, and the
# matrix file is the thing this job reads.
#
# The lanes boot the qualification image (src/Dockerfile COMPOSITION=qualification: every
# capability module present). The script selects it; release.yml builds the default image.
compose-runtime-smoke:
runs-on: ubuntu-latest
timeout-minutes: 180
+4 -4
View File
@@ -21,17 +21,17 @@ jobs:
- id: jakarta-persistence-4
target: Jakarta Persistence 4
coordinate: jakarta.persistence:jakarta.persistence-api:4.x
test: "*CompatibilityLaneDefinitionTest"
test: "*Jpa4CompatibilityTest"
reason: the JPA 4 API is not on any configuration this build resolves, so nothing has been compiled against it
- id: hibernate-8
target: Hibernate 8
coordinate: org.hibernate.orm:hibernate-core:8.x
test: "*HibernateCompatibilityPolicyTest"
test: "*Hibernate8CompatibilityTest"
reason: Hibernate 8 is not resolvable from this build, so nothing has been compiled or run against it
- id: postgresql-19
target: PostgreSQL 19
coordinate: postgres:19-alpine
test: "*ExperimentalPromotionGateTest"
test: "*PostgreSql19CompatibilityTest"
reason: no PostgreSQL 19 image is published yet, so no container of that major has ever been started by this lane
runs-on: ubuntu-latest
timeout-minutes: 60
@@ -61,7 +61,7 @@ jobs:
echo "status=NOT_EXECUTABLE"
echo "probe-result=${PROBE_OUTCOME}"
echo "reason=${REASON}"
echo "what-ran=the current runtime's own policy and lane-definition tests"
echo "what-ran=the current runtime's own version canary for this target"
echo "sha=${{ github.sha }}"
} > compatibility-evidence/status.properties
echo "::notice::${TARGET} compatibility is NOT_EXECUTABLE: ${REASON}"
-45
View File
@@ -1,45 +0,0 @@
name: jpa-r2-evidence
on:
workflow_dispatch:
permissions:
contents: read
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
env:
TESTCONTAINERS_REUSE_ENABLE: "false"
jobs:
jpa-r2-evidence:
runs-on: ubuntu-latest
timeout-minutes: 30
env:
JPA_EVIDENCE_PROFILE: r2
JPA_EVIDENCE_CI_JOB: >-
actions:${{ github.workflow }}:${{ github.run_id }}:${{ github.job }}
JPA_EVIDENCE_ARTIFACT_LOCATION: >-
${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
JPA_EVIDENCE_TOPOLOGY: postgresql-16-testcontainers-tls-and-fault-matrix
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Verify the production-profile JPA R2 manifest DAG
working-directory: src
run: >-
./gradlew
:adapter:outbound:persistence-jpa:verifyJpaPrimaryFoundationEvidence
-PjpaEvidenceProfile=r2
--stacktrace
- name: Retain JPA R2 attempt manifests
if: always()
uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # actions/upload-artifact@v7.0.1
with:
name: jpa-r2-evidence-${{ github.sha }}-${{ github.run_id }}
path: src/adapter/outbound/persistence-jpa/build/jpa-evidence/manifests
if-no-files-found: error
retention-days: 30
-128
View File
@@ -1,128 +0,0 @@
name: jpa-release
# The release registry is the gate-task source: jpaReleaseQualification reads its blocking gates,
# while JpaReleaseRenderingTest holds this file's matrix and promotion lists to the registry's Stable
# majors and verifyJpaReleaseGateTasks resolves each declared task against the real Gradle graph.
# CI therefore owns release scheduling, not a second JPA gate-task inventory.
#
# The matrix below is therefore not free to drift: editing it without editing the registry fails the
# unit lane.
on:
workflow_dispatch:
push:
tags:
- 'v*'
permissions:
contents: read
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: false
jobs:
# One job per PostgreSQL major, because one job for three majors was one job for one major.
#
# `-Pjpa.matrix.versions=16,17,18` reached JpaPlatformContractSupport.start(), which started
# selectedVersions().get(0) — so twenty-eight integration classes ran against PG16 and nothing
# ran against 17 or 18, while docs/jpa/support-matrix.md recorded all three as "full contract
# suite, release lane". A JSONB mapping, a Hibernate dialect difference or a Flyway upgrade that
# only breaks on 18 shipped with a green release.
#
# start() now fails closed on a multi-version selection, so the fan-out is not optional: the
# matrix is the only way the three majors get covered, and removing a major from it removes the
# evidence rather than quietly reusing another major's.
jpa-release-gate:
runs-on: ubuntu-latest
timeout-minutes: 90
strategy:
fail-fast: false
matrix:
postgresql: ["16", "17", "18"]
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Run the JPA database qualification set on PostgreSQL ${{ matrix.postgresql }}
working-directory: src
run: >-
./gradlew
jpaReleaseQualification
-Pjpa.matrix.versions=${{ matrix.postgresql }}
--stacktrace
- name: Record which major this evidence covers
if: always()
working-directory: src
run: |
mkdir -p build/jpa-release-evidence
{
echo "sha=${{ github.sha }}"
echo "ref=${{ github.ref }}"
echo "postgresql-major=${{ matrix.postgresql }}"
echo "task-set=jpa-database-qualification"
} > "build/jpa-release-evidence/manifest-${{ matrix.postgresql }}.properties"
- name: Upload the release evidence
if: always()
uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # actions/upload-artifact@v4.6.2
with:
name: jpa-release-evidence-pg${{ matrix.postgresql }}
path: |
src/build/jpa-release-evidence/manifest-${{ matrix.postgresql }}.properties
src/adapter/outbound/persistence-jpa/build/test-results/**/*.xml
retention-days: 30
if-no-files-found: error
# The promotion decision. Three majors' evidence, and all three must come from this SHA — an
# aggregate that accepted a re-run artifact from another commit would promote a release on
# evidence produced by different code.
jpa-release-promotion:
runs-on: ubuntu-latest
timeout-minutes: 15
needs: jpa-release-gate
steps:
- name: Download every major's evidence
uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # actions/download-artifact@v4.3.0
with:
pattern: jpa-release-evidence-pg*
path: evidence
- name: Require all three majors, all from this SHA
run: |
set -euo pipefail
missing=0
for major in 16 17 18; do
manifest=$(find evidence -name "manifest-${major}.properties" -print -quit)
if [ -z "${manifest}" ]; then
echo "::error::no release evidence for PostgreSQL ${major}"
missing=1
continue
fi
sha=$(sed -n 's/^sha=//p' "${manifest}")
if [ "${sha}" != "${{ github.sha }}" ]; then
echo "::error::PostgreSQL ${major} evidence is from ${sha}, not ${{ github.sha }}"
missing=1
fi
done
if [ "${missing}" -ne 0 ]; then
echo "::error::the release gate covers three PostgreSQL majors; promotion needs all three"
exit 1
fi
echo "PostgreSQL 16, 17 and 18 evidence all present and all from ${{ github.sha }}."
jpa-architecture-and-docs:
runs-on: ubuntu-latest
timeout-minutes: 30
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Verify architecture boundaries and the support matrix
working-directory: src
run: >-
./gradlew
:verifyJpaReleaseGateTasks
:verifyJpaReadinessRegistry
:verifyCleanArchitectureDependencies
checkstyleMain
:app-bootstrap:architectureTest
:adapter:outbound:persistence-jpa:test --tests '*JpaReleaseManifestTest'
--stacktrace
+15 -24
View File
@@ -20,10 +20,11 @@ on:
# assembles, binds and migrates at all.
- 'src/application-core/src/**/notification/**'
- 'src/adapter/outbound/notification/**'
- 'src/adapter/outbound/persistence-notification/**'
# The notification real-PostgreSQL qualifications still run in the JPA leaf's lane.
- 'src/adapter/outbound/persistence-jpa/src/**/notification/**'
- 'src/adapter/outbound/persistence-jpa/src/main/resources/db/migration/jpa/notification-platform/**'
- 'src/adapter/inbound/web/src/**/notification/**'
- 'src/app-bootstrap/src/**/notification/**'
- 'src/adapter/inbound/web-notification/**'
- 'src/composition/notification-platform/**'
- 'src/app-bootstrap/src/main/resources/application*.yml'
- 'src/gradle/notification-*.gradle'
- 'src/config/architecture/modules.json'
@@ -67,7 +68,7 @@ jobs:
run: ./gradlew :adapter:outbound:notification:test --console=plain
- name: Persistence and web
working-directory: src
run: ./gradlew :adapter:outbound:persistence-jpa:test :adapter:inbound:web:test --console=plain
run: ./gradlew :adapter:outbound:persistence-jpa:test :adapter:inbound:web-notification:test :composition:notification-platform:test --console=plain
# The PR tier never touched a database, so every claim about migrations, claim atomicity and
# lease fencing rested on a fake. Docker is available on this runner; the lane fails closed
# when the container cannot start, because a skipped contract reports success for a database
@@ -78,23 +79,12 @@ jobs:
- name: Notification migration upgrade (real PostgreSQL)
working-directory: src
run: ./gradlew :adapter:outbound:persistence-jpa:jpaPlatformMigrationTest --console=plain
- name: Architecture gates
working-directory: src
run: |
./gradlew :verifyCleanArchitectureDependencies --console=plain
./gradlew :app-bootstrap:architectureTest --console=plain
- name: Configuration surface
working-directory: src
run: |
./gradlew :app-bootstrap:verifyEnvKeys :verifyPublicPathSnapshot --console=plain
./gradlew :verifyNotificationApiSurface :verifyNotificationConfiguration --console=plain
# A support grade is a promise about production behaviour. This refuses one the pipeline
# cannot back — the check that would have caught five channels reading "Stable" while no
# request had ever left the process.
- name: Evidence manifest
working-directory: src
run: ./gradlew :verifyNotificationEvidence --console=plain
- name: Static analysis
# The architecture gates run in ci-quality-gates.yml on the same pull request; the evidence
# manifest (NotificationEvidenceVerifierTest) and the environment registry
# (NotificationEnvironmentRegistryTest) are leaf tests the steps above already ran.
# verifyNotificationApiSurface is part of the leaf's `check` (owner decision 20), so the step
# below runs it; a separate API surface step would run it twice.
- name: Static analysis and API surface
working-directory: src
run: ./gradlew :adapter:outbound:notification:check -x test --console=plain
@@ -125,7 +115,8 @@ jobs:
:application-core:test
:adapter:outbound:notification:test
:adapter:outbound:persistence-jpa:test
:adapter:inbound:web:test
:adapter:inbound:web-notification:test
:composition:notification-platform:test
--console=plain
# A filter that matches nothing passes. Each --tests filter above names a class that exists
# today; if one is renamed the job must fail rather than quietly stop covering it.
@@ -149,5 +140,5 @@ jobs:
#
# The unimplemented state is still stated in two places that do not depend on a workflow:
# ProviderSandboxSmokeTest itself, and the unsatisfied provider-wire-qualified claim in
# docs/notification/evidence-manifest.json, which verifyNotificationEvidence enforces inside
# check. When a real sandbox call is implemented, the job comes back with it.
# docs/notification/evidence-manifest.json, which NotificationEvidenceVerifierTest enforces in
# the notification leaf's tests. When a real sandbox call is implemented, the job comes back with it.
@@ -1,7 +1,14 @@
name: object-storage-qualification
# Only pull requests that touch object storage start the MinIO container (review BUILD-계획-B3). The
# MinIO lanes left the object storage leaf's `check`; they run in its `mainCheck` on main and here.
on:
pull_request:
paths:
- "src/application-objectstorage/**"
- "src/adapter/outbound/objectstorage/**"
- "src/gradle/**"
- ".github/workflows/object-storage-qualification.yml"
schedule:
- cron: "23 3 * * 2"
workflow_dispatch:
@@ -11,17 +18,6 @@ on:
required: true
default: false
type: boolean
# AwsS3DirectTransferQualificationTest requires a second, separate authority
# (OBJECT_STORAGE_AWS_DIRECT_MUTATION_ENABLED) before the direct-transfer lane may run, and
# the job never supplied it. objectStorageAwsQualificationTest is a strict qualification task
# that requires both of its classes, so the lane could not be run to a pass from any input:
# dispatching it always failed on the missing variable. The authority now exists as its own
# input rather than as a constant, which is what "separate" was supposed to mean.
run_protected_aws_direct_mutation:
description: Also authorize the direct-transfer mutation lane against the sandbox bucket
required: true
default: false
type: boolean
permissions:
contents: read
@@ -53,12 +49,10 @@ jobs:
if: >-
github.event_name == 'workflow_dispatch'
&& inputs.run_protected_aws
&& inputs.run_protected_aws_direct_mutation
environment: object-storage-aws-qualification
runs-on: ubuntu-latest
env:
OBJECT_STORAGE_AWS_QUALIFICATION_ENABLED: "true"
OBJECT_STORAGE_AWS_DIRECT_MUTATION_ENABLED: ${{ inputs.run_protected_aws_direct_mutation }}
OBJECT_STORAGE_AWS_BUCKET: ${{ secrets.OBJECT_STORAGE_AWS_BUCKET }}
OBJECT_STORAGE_AWS_REGION: ${{ secrets.OBJECT_STORAGE_AWS_REGION }}
OBJECT_STORAGE_AWS_EXPECTED_OWNER: ${{ secrets.OBJECT_STORAGE_AWS_EXPECTED_OWNER }}
+15 -34
View File
@@ -12,8 +12,8 @@ name: pr-adapters
# here is only what `check` does not run.
#
# What `check` does not run, and therefore what this file is for:
# * lanes with their own source set — a second servlet container, a real Nginx, Reactor Netty;
# * lanes selected by a tag that `test` excludes — the cross-stack parity recording comparison;
# * lanes with their own source set — the servlet system contract, a second servlet container,
# a real Nginx;
# * lanes parameterised per run — one PostgreSQL major per job, one HTTP transport per job.
# Each of those genuinely cannot run inside `check`, which is the test for whether a job belongs
# here at all.
@@ -126,10 +126,9 @@ jobs:
'^infra/jpa/' \
"${common}"
# The parity gate depends on all three recording lanes and fails when one is missing, so it runs
# them itself rather than trusting a previous job to have left the recordings behind. Its tag is
# excluded from `test`, which is why `check` cannot cover it.
web-cross-stack-parity:
# The servlet system contract on both containers the template supports (Tomcat, Jetty). Real
# sockets, so neither lane is part of `check`.
web-servlet-containers:
needs: changes
if: needs.changes.outputs.web == 'true'
runs-on: ubuntu-latest
@@ -137,39 +136,21 @@ jobs:
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Compare the wire contract across Tomcat, Jetty and Reactor Netty
- name: Run the servlet system contract on Tomcat and Jetty
working-directory: src
run: >-
./gradlew
:adapter:inbound:web:webCrossStackParityTest
:adapter:inbound:web:systemTest
:adapter:inbound:web:webJettyCompatTest
--stacktrace
- name: Publish the parity recordings
- name: Publish the test reports
if: always()
uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # actions/upload-artifact@v4.6.2
with:
name: web-contract-parity
path: src/adapter/inbound/web/build/web-contract-parity/
if-no-files-found: error
# Docker-gated, and the lane fails rather than skipping when the runtime is missing. A proxy
# contract that quietly passes without a proxy has been certifying nothing since whenever the
# container runtime last broke.
web-nginx-proxy-contract:
needs: changes
if: needs.changes.outputs.web == 'true'
runs-on: ubuntu-latest
timeout-minutes: 30
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Run the proxy, prefix and spoofing contract behind a real Nginx
working-directory: src
run: >-
./gradlew
:adapter:inbound:web:webNginxProxyTest
--stacktrace
name: web-servlet-containers-reports
path: src/adapter/inbound/web/build/reports/tests/
if-no-files-found: warn
websocket-container-matrix:
needs: changes
@@ -215,7 +196,7 @@ jobs:
strategy:
fail-fast: false
matrix:
transport: [apache, jdk, reactor]
transport: [apache, jdk]
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
@@ -228,8 +209,8 @@ jobs:
--stacktrace
# Only the Spring 7.0 lane. httpClientSecurityTest, httpClientBlockHoundTest and
# spring62ApiSurfaceScan used to run here too; all three are `dependsOn` of this leaf's `check`
# Only the Spring 7.0 lane. httpClientSecurityTest and spring62ApiSurfaceScan used to run here
# too; both are `dependsOn` of this leaf's `check`
# (src/adapter/outbound/httpclient/build.gradle), so ci-quality-gates.yml already ran them on the
# same pull request. spring70CompatibilityTest is deliberately outside `check` and is what is left.
httpclient-security-and-compatibility:
+16 -7
View File
@@ -31,6 +31,8 @@ name: redis-sdk-topology
on:
pull_request:
paths:
- "src/adapter/outbound/redis-runtime/**"
- "src/adapter/outbound/redis-sdk/**"
- "src/adapter/outbound/cache-redis/**"
- "infra/redis-sdk/**"
- ".github/workflows/redis-sdk-topology.yml"
@@ -145,10 +147,15 @@ jobs:
working-directory: src
run: |
set -euo pipefail
# Each leaf declares the lanes its tests qualify; a mode a leaf does not declare fails
# closed, so each topology names exactly the leaves that have classes for it.
runtime=:adapter:outbound:redis-runtime:redisTopologyTest
sdk=:adapter:outbound:redis-sdk:redisTopologyTest
semantic=:adapter:outbound:cache-redis:redisTopologyTest
case '${{ matrix.topology }}' in
standalone) port=6379; extra='' ;;
sentinel) port=27010; extra='-Predis.topology.master=skeleton' ;;
cluster) port=7100; extra='' ;;
standalone) port=6379; extra=''; tasks="$runtime $sdk $semantic" ;;
sentinel) port=27010; extra='-Predis.topology.master=skeleton'; tasks="$runtime $sdk" ;;
cluster) port=7100; extra=''; tasks="$runtime $sdk $semantic" ;;
# The TLS lane's CA is generated at start-up, so the trust material is extracted from
# the lane rather than checked in. A checked-in key is a secret in the repository
# however loudly the file is named "test".
@@ -156,10 +163,11 @@ jobs:
port=6390
docker compose -f ../infra/redis-sdk/tls/compose.yml cp redis:/tls/ca.crt "$RUNNER_TEMP/redis-lane-ca.pem"
extra="-Predis.topology.trust-material=$RUNNER_TEMP/redis-lane-ca.pem"
tasks="$runtime"
;;
*) echo "unknown topology"; exit 1 ;;
esac
./gradlew :adapter:outbound:cache-redis:redisTopologyTest --console=plain \
./gradlew $tasks --continue --console=plain \
-Predis.topology.host=localhost \
-Predis.topology.port="$port" \
-Predis.topology.mode='${{ matrix.topology }}' \
@@ -168,7 +176,7 @@ jobs:
if: always()
run: |
set -euo pipefail
out=src/adapter/outbound/cache-redis/build/test-results/redisTopologyTest
out=src/build/redis-topology-evidence
mkdir -p "$out"
cat > "$out/evidence-manifest.txt" <<MANIFEST
commit=${{ github.sha }}
@@ -184,8 +192,9 @@ jobs:
with:
name: redis-topology-${{ matrix.topology }}-${{ matrix.redis_version }}
path: |
src/adapter/outbound/cache-redis/build/test-results/redisTopologyTest/**
src/adapter/outbound/cache-redis/build/reports/tests/redisTopologyTest/**
src/build/redis-topology-evidence/**
src/adapter/outbound/*/build/test-results/redisTopologyTest/**
src/adapter/outbound/*/build/reports/tests/redisTopologyTest/**
if-no-files-found: error
retention-days: 90
- name: Stop the topology
+317 -34
View File
@@ -5,31 +5,24 @@ name: release
# One workflow, because there is one deployable unit. `app-bootstrap` is the composition root and
# the only thing a cluster runs; the adapters are leaves of that artifact, not independently
# shippable services. Eight files used to answer a release tag — web-release, web-advanced-release,
# websocket-release, httpclient-release, container-release, and the three that still have to live
# apart (see below) — and between them they ran `verifyCleanArchitectureDependencies` six times and
# `:app-bootstrap:test` four times for one release, on separate runners, with no job in any of them
# able to wait on a job in another.
# websocket-release, httpclient-release, container-release, jpa-release, fileserver-certification
# and one more — and between them they ran `verifyCleanArchitectureDependencies` six times and the
# composition root's unit tests four times for one release, on separate runners, with no job in any
# of them able to wait on a job in another.
#
# Tag scheme: `v*` only. The adapter-scoped patterns (`web-v*`, `websocket-v*`, `fileserver-v*`) are
# gone. They were the namespace-split bug: tagging `v1.2.3` and tagging `web-v1.2.3` ran different
# sets of gates, so a release could choose which gate it cleared, and the adapter-scoped half could
# not build an image because there is no per-adapter image to build.
#
# Two release workflows still stand outside this file, both for a mechanical reason rather than a
# design one:
# * jpa-release.yml — JpaReleaseRenderingTest reads that exact path and holds its PostgreSQL
# matrix and promotion list to src/config/jpa/release-registry.json.
# * fileserver-certification.yml — FileserverDocumentationCoverageTest requires every job id named
# in docs/fileserver/support-matrix.md to be defined in a `.github/workflows/fileserver-*.yml`.
# It is named "certification" rather than "release" on purpose: it certifies a storage topology
# and a support matrix, it deploys nothing, and the CI/CD boundary in docs/ci-cd/boundary.md
# says GitHub Actions does not deploy.
# Folding either one in needs its src-side test (and, for fileserver, the support document) changed
# in the same commit. Until then the image job below cannot wait on them — a stated gap.
# The JPA release gates and the fileserver certification used to stand outside this file
# (jpa-release.yml, fileserver-certification.yml), so the image job could not wait on them. They are
# jobs here now (review 2026-09-24 BUILD-계획-B2): JpaReleaseRenderingTest reads this file's JPA
# matrix and promotion list, and FileserverDocumentationCoverageTest reads its fileserver job ids.
#
# The image job DOES now wait on the evidence jobs in this file, which is new: while the image build
# lived in its own workflow it could publish while a sibling suite was still running or already red,
# because `needs:` does not reach across workflows.
# The image job waits on every evidence job in this file: `needs:` does not reach across
# workflows, so a gate in another file could still be running, or already red, when the image
# published.
on:
push:
@@ -46,9 +39,10 @@ concurrency:
cancel-in-progress: false
jobs:
# The repository release contract, once. releaseCheck contains the PR gate plus provenance,
# stale-archive hygiene and the public path snapshot, so those tasks are no longer merely
# registered/documented — the tag workflow executes them before any image can publish.
# The tag-only checks. releaseCheck no longer re-runs `ci`: a release tag is cut from a main
# commit that ci-quality-gates.yml (the pull-request gate) and integration-main.yml (`mainCheck`)
# already ran on, and running the whole PR gate a third time was the repeat review BUILD-중복-6
# asked to remove.
architecture-and-surface:
runs-on: ubuntu-latest
timeout-minutes: 90
@@ -59,12 +53,11 @@ jobs:
working-directory: src
run: ./gradlew :releaseCheck --stacktrace
# Every web lane that `check` cannot reach. webCrossStackParityTest depends on `test`,
# webJettyCompatTest and webFluxContractTest, so naming it runs all four — which is what
# web-advanced-release.yml spent a separate 90-minute job doing by naming the three by hand.
# Every web lane that `check` cannot reach: the servlet system contract on Tomcat (systemTest)
# and Jetty (webJettyCompatTest), and the Advanced lane.
#
# webAdvancedTest is here rather than in a nightly of its own. Its tests run inside
# `:adapter:inbound:web:test` by design, so the lane adds exactly one thing: it fails closed when
# `:adapter:inbound:web-advanced:test` by design, so the lane adds exactly one thing: it fails closed when
# the `web-advanced` tag selects nothing. That is worth asserting at a release and is not worth a
# workflow file and a runner every night.
web-stable-release-gate:
@@ -77,9 +70,9 @@ jobs:
working-directory: src
run: >-
./gradlew
:adapter:inbound:web:webCrossStackParityTest
:adapter:inbound:web:webNginxProxyTest
:adapter:inbound:web:webAdvancedTest
:adapter:inbound:web:systemTest
:adapter:inbound:web:webJettyCompatTest
:adapter:inbound:web-advanced:webAdvancedTest
--stacktrace
- name: Publish the release evidence
@@ -88,8 +81,8 @@ jobs:
with:
name: web-release-evidence
path: |
src/adapter/inbound/web/build/web-contract-parity/
src/adapter/inbound/web/build/reports/tests/
src/adapter/inbound/web-advanced/build/reports/tests/
if-no-files-found: error
websocket-stable-release-gate:
@@ -98,15 +91,15 @@ jobs:
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Run every websocket lane, Stable and Advanced
- name: Run every websocket lane
working-directory: src
run: >-
./gradlew
:adapter:inbound:websocket:test
:adapter:inbound:websocket:systemTest
:adapter:inbound:websocket:websocketJettyTest
:adapter:inbound:websocket:websocketNginxTest
:adapter:inbound:websocket:websocketTransportQualificationTest
:adapter:inbound:websocket:websocketAdvancedTest
--stacktrace
- name: Publish the release evidence
@@ -120,7 +113,7 @@ jobs:
# The three gRPC certification lanes. Their tests already run on every pull request — the
# `grpc-inprocess`, `grpc-netty` and `grpc-fault` tags are NOT excluded from
# `:grpc:grpc-testkit:test` (only `grpc-performance` is), and that task runs inside the root
# `check`. So this job adds exactly what the web and WebSocket Advanced lanes above add: the lane
# `check`. So this job adds exactly what the web Advanced lane above adds: the lane
# fails closed when its tag selects nothing, which is the one thing a tag-filtered suite inside
# `test` cannot tell you. A renamed or deleted @Tag would otherwise leave the in-process,
# transport and fault evidence grades claiming coverage that stopped existing.
@@ -178,7 +171,6 @@ jobs:
:adapter:outbound:httpclient:spring70CompatibilityTest
:adapter:outbound:httpclient:httpClientStableContractTest
:adapter:outbound:httpclient:httpClientSecurityTest
:adapter:outbound:httpclient:httpClientBlockHoundTest
:adapter:outbound:httpclient:httpClientFailureInjectionTest
:adapter:outbound:httpclient:httpClientPerformanceTest
--stacktrace
@@ -195,6 +187,179 @@ jobs:
- name: Verify documentation matches the code
run: python3 scripts/verify-httpclient-docs.py
# ---------------------------------------------------------------------------------------------
# JPA release gates (were jpa-release.yml). One job per PostgreSQL major, because one job for
# three majors was one job for one major: `-Pjpa.matrix.versions=16,17,18` reached
# JpaPlatformContractSupport.start(), which started only the first selected version, while
# docs/jpa/support-matrix.md recorded all three as covered. start() now fails closed on a
# multi-version selection, so this matrix is the only way the Stable majors get covered.
#
# config/jpa/release-registry.json is the gate-task source: jpaReleaseQualification (persistence-jpa
# build.gradle) depends on its blocking gates, so a gate naming a missing task fails when the task
# graph is built, and JpaReleaseRenderingTest holds this matrix and the promotion list below to the
# registry's Stable majors. Editing one without the other fails the persistence-jpa unit lane.
jpa-release-gate:
runs-on: ubuntu-latest
timeout-minutes: 90
strategy:
fail-fast: false
matrix:
postgresql: ["16", "17", "18"]
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Run the JPA database qualification set on PostgreSQL ${{ matrix.postgresql }}
working-directory: src
run: >-
./gradlew
jpaReleaseQualification
-Pjpa.matrix.versions=${{ matrix.postgresql }}
--stacktrace
- name: Record which major this evidence covers
if: always()
working-directory: src
run: |
mkdir -p build/jpa-release-evidence
{
echo "sha=${{ github.sha }}"
echo "ref=${{ github.ref }}"
echo "postgresql-major=${{ matrix.postgresql }}"
echo "task-set=jpa-database-qualification"
} > "build/jpa-release-evidence/manifest-${{ matrix.postgresql }}.properties"
- name: Upload the release evidence
if: always()
uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # actions/upload-artifact@v4.6.2
with:
name: jpa-release-evidence-pg${{ matrix.postgresql }}
path: |
src/build/jpa-release-evidence/manifest-${{ matrix.postgresql }}.properties
src/adapter/outbound/persistence-jpa/build/test-results/**/*.xml
retention-days: 30
if-no-files-found: error
# The promotion decision. Every Stable major's evidence, all from this SHA — an aggregate that
# accepted a re-run artifact from another commit would promote a release on evidence produced by
# different code.
jpa-release-promotion:
runs-on: ubuntu-latest
timeout-minutes: 15
needs: jpa-release-gate
steps:
- name: Download every major's evidence
uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # actions/download-artifact@v4.3.0
with:
pattern: jpa-release-evidence-pg*
path: evidence
- name: Require every Stable major, all from this SHA
run: |
set -euo pipefail
missing=0
for major in 16 17 18; do
manifest=$(find evidence -name "manifest-${major}.properties" -print -quit)
if [ -z "${manifest}" ]; then
echo "::error::no release evidence for PostgreSQL ${major}"
missing=1
continue
fi
sha=$(sed -n 's/^sha=//p' "${manifest}")
if [ "${sha}" != "${{ github.sha }}" ]; then
echo "::error::PostgreSQL ${major} evidence is from ${sha}, not ${{ github.sha }}"
missing=1
fi
done
if [ "${missing}" -ne 0 ]; then
echo "::error::the release gate covers every Stable PostgreSQL major; promotion needs all of them"
exit 1
fi
echo "Every Stable PostgreSQL major's evidence is present and from ${{ github.sha }}."
jpa-registry-and-docs:
runs-on: ubuntu-latest
timeout-minutes: 30
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Verify the release registry, the readiness cards and the support matrix
working-directory: src
run: >-
./gradlew
:adapter:outbound:persistence-jpa:test
--tests '*JpaReleaseManifestTest'
--tests '*JpaReleaseRenderingTest'
--tests '*JpaReadinessRegistryTest'
--stacktrace
# ---------------------------------------------------------------------------------------------
# Fileserver certification (was fileserver-certification.yml). Its job list is the same shape as
# docs/fileserver/support-matrix.md: nothing is advertised at a support level whose evidence job
# is absent. FileserverDocumentationCoverageTest reads the job ids from this file and from
# `.github/workflows/fileserver-*.yml`. "Certification" rather than "release" on purpose: these
# jobs prove a storage topology, a support matrix and a telemetry redaction claim, and deploy
# nothing (docs/ci-cd/boundary.md).
fileserver-full-verification:
runs-on: ubuntu-latest
timeout-minutes: 60
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Run the complete fileserver suite across every leaf
working-directory: src
run: >-
./gradlew
:application-fileserver:check
:adapter:inbound:web-fileserver:check
:adapter:outbound:fileserver:check
:adapter:outbound:persistence-fileserver:check
:composition:fileserver-platform:check
--stacktrace
fileserver-documentation-gate:
runs-on: ubuntu-latest
timeout-minutes: 20
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Prove every support claim maps to a job and every endpoint is documented
working-directory: src
run: >-
./gradlew
:composition:fileserver-platform:test --tests '*FileserverDocumentationCoverageTest'
--stacktrace
fileserver-pvc-certification:
runs-on: ubuntu-latest
timeout-minutes: 45
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
# This job checks the manifest, and only the manifest; it applies nothing to a cluster. The
# cluster result comes from an operator running infra/fileserver/kubernetes/
# pvc-certification-job.yaml and recording it in docs/fileserver/storage-certification.md,
# where the absence of a cluster result is stated rather than hidden behind a green check.
- name: Check the certification manifest still says what the claim depends on
run: |
set -euo pipefail
manifest=infra/fileserver/kubernetes/pvc-certification-job.yaml
test -f "$manifest"
grep -q 'kind: PersistentVolumeClaim' "$manifest"
grep -q 'kind: Job' "$manifest"
# ReadWriteMany is explicitly not claimed; a manifest that quietly widened the access
# mode would certify a topology the support matrix says is uncertified.
grep -q 'ReadWriteOnce' "$manifest"
! grep -q 'ReadWriteMany' "$manifest"
fileserver-sensitive-telemetry-scan:
runs-on: ubuntu-latest
timeout-minutes: 20
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # actions/checkout@v4.2.2
- uses: ./.github/actions/setup-gradle-java
- name: Prove telemetry carries no filename, path, or raw identifier
working-directory: src
run: >-
./gradlew
:application-fileserver:test --tests '*FileserverObservabilityTest'
--stacktrace
app-image-release:
needs:
- architecture-and-surface
@@ -203,11 +368,22 @@ jobs:
- grpc-stable-release-gate
- httpclient-release-gate
- httpclient-documentation
- jpa-release-promotion
- jpa-registry-and-docs
- fileserver-full-verification
- fileserver-documentation-gate
- fileserver-pvc-certification
- fileserver-sensitive-telemetry-scan
# Job-level, because a job that declares `permissions:` replaces the workflow set entirely: this
# is the only job that writes anything anywhere, and `packages: write` stops at its boundary.
# job and app-image-signing are the only ones that write anything anywhere, and
# `packages: write` stops at their boundary. No OIDC token here: this job runs the repository's
# Gradle build inside the Dockerfile, and the signing identity stays out of that.
permissions:
contents: read
packages: write
# The signing job below reads the digest from here. It is the digest, not a tag, that is signed.
outputs:
pinned_reference: ${{ steps.push.outputs.pinned_reference }}
runs-on: ubuntu-latest
timeout-minutes: 90
steps:
@@ -404,6 +580,7 @@ jobs:
# digest recorded below is immutable by construction, and it is the field the GitOps repository
# pins — the tags exist so a person can find the digest, not so a cluster can resolve one.
- name: Push the release and revision tags
id: push
run: |
set -euo pipefail
docker push "${IMAGE_REPOSITORY}:${IMAGE_VERSION_TAG}"
@@ -424,6 +601,7 @@ jobs:
exit 1
fi
printf 'PINNED_REFERENCE=%s\n' "${pinned_reference}" >> "${GITHUB_ENV}"
printf 'pinned_reference=%s\n' "${pinned_reference}" >> "${GITHUB_OUTPUT}"
printf 'container-release: pushed %s\n' "${pinned_reference}"
# The handoff to the GitOps repository, in a form a person and a script can both read. It is
# written to the job summary as well as to an artifact because the summary is where somebody
@@ -457,3 +635,108 @@ jobs:
path: image-release.txt
if-no-files-found: error
retention-days: 90
# Keyless signature of the pushed digest (owner decision 31). A job of its own so that
# `id-token: write` — the GitHub OIDC token Fulcio turns into a short-lived signing certificate
# naming this workflow and tag — exists only here, in a job that checks nothing out and builds
# nothing. The signature goes to the registry beside the image (hence `packages: write`) and the
# transparency-log entry to Rekor; there is no key to store or rotate.
#
# The digest is signed, never a tag: a tag can be moved to other content, a digest cannot.
# Verification runs right after signing with the identity a deployment should require, so a
# release whose signature a cluster would reject fails here instead of at admission.
#
# Local limit: signing needs the tag run's OIDC token and a pushed GHCR image, so it is exercised
# only by a real release. DeveloperExperienceContractTest pins the structure of this job.
app-image-signing:
needs:
- app-image-release
permissions:
contents: read
packages: write
id-token: write
runs-on: ubuntu-latest
timeout-minutes: 30
env:
PINNED_REFERENCE: ${{ needs.app-image-release.outputs.pinned_reference }}
steps:
# Same policy as Trivy above: a pinned release binary with an asserted SHA-256, no action.
# The two hashes are the cosign-linux-{amd64,arm64} lines of the official v3.1.3
# cosign_checksums.txt, which was itself verified against its Sigstore bundle
# (identity keyless@projectsigstore.iam.gserviceaccount.com, issuer https://accounts.google.com)
# when they were pinned. The checksum file is fetched again here and must still carry the
# pinned line, so a re-published release asset fails the job instead of passing silently.
- name: Install pinned cosign under RUNNER_TEMP
run: |
set -euo pipefail
readonly COSIGN_VERSION='3.1.3'
readonly COSIGN_SHA256_AMD64='4629c757b7618056f8ddd7e2625ae9fdd94c0372a65049520bc7d9df9efc7f71'
readonly COSIGN_SHA256_ARM64='c5d324e091826b0d7a78eb16fef316450b4eb9aaec045611c08ba06f5e73220a'
readonly DOWNLOAD_BASE_URL="https://github.com/sigstore/cosign/releases/download/v${COSIGN_VERSION}"
case "${RUNNER_ARCH:-X64}" in
X64)
asset='cosign-linux-amd64'
expected_sha256="${COSIGN_SHA256_AMD64}"
;;
ARM64)
asset='cosign-linux-arm64'
expected_sha256="${COSIGN_SHA256_ARM64}"
;;
*)
echo "::error::unsupported runner architecture: ${RUNNER_ARCH:-unknown}"
exit 1
;;
esac
install_dir="${RUNNER_TEMP}/cosign-${COSIGN_VERSION}"
mkdir -p "${install_dir}"
curl --fail --show-error --silent --location --retry 3 \
--proto '=https' --tlsv1.2 \
"${DOWNLOAD_BASE_URL}/cosign_checksums.txt" \
--output "${RUNNER_TEMP}/cosign_checksums.txt"
if ! grep -qxF "${expected_sha256} ${asset}" "${RUNNER_TEMP}/cosign_checksums.txt"; then
echo "::error::cosign_checksums.txt no longer lists the pinned ${asset} hash"
exit 1
fi
curl --fail --show-error --silent --location --retry 3 \
--proto '=https' --tlsv1.2 \
"${DOWNLOAD_BASE_URL}/${asset}" \
--output "${install_dir}/cosign"
printf '%s %s\n' "${expected_sha256}" "${install_dir}/cosign" | sha256sum -c -
chmod 0755 "${install_dir}/cosign"
printf '%s\n' "${install_dir}" >> "${GITHUB_PATH}"
- name: Check the reference to sign
run: |
set -euo pipefail
if [[ ! "${PINNED_REFERENCE}" =~ ^ghcr\.io/[a-z0-9._/-]+@sha256:[0-9a-f]{64}$ ]]; then
echo "::error::app-image-release handed over no digest reference; got '${PINNED_REFERENCE}'"
exit 1
fi
printf 'CERTIFICATE_IDENTITY=%s/%s\n' "${GITHUB_SERVER_URL}" "${GITHUB_WORKFLOW_REF}" \
>> "${GITHUB_ENV}"
- name: Sign in to the container registry
env:
REGISTRY_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
set -euo pipefail
printf '%s' "${REGISTRY_TOKEN}" \
| docker login ghcr.io --username "${GITHUB_ACTOR}" --password-stdin
- name: Sign the image digest (keyless)
run: |
set -euo pipefail
cosign sign --yes "${PINNED_REFERENCE}"
# The identity a deployment admission policy should require: this workflow file at this tag,
# issued by GitHub's OIDC provider. Anything else — another workflow, another repository, a
# branch run — does not verify.
- name: Verify the signature with the release identity
run: |
set -euo pipefail
cosign verify \
--certificate-identity "${CERTIFICATE_IDENTITY}" \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
"${PINNED_REFERENCE}" > cosign-verify.json
{
printf '### container-release signature\n\n'
printf -- '- signed: `%s`\n' "${PINNED_REFERENCE}"
printf -- '- certificate identity: `%s`\n' "${CERTIFICATE_IDENTITY}"
printf -- '- issuer: `https://token.actions.githubusercontent.com`\n'
} >> "${GITHUB_STEP_SUMMARY}"
+5
View File
@@ -10,3 +10,8 @@ src/.env*
# Written per run by the runtime-smoke wrapper; never committed.
src/.env.lane
# Local tool output (graphify knowledge graph, Playwright MCP snapshots).
graphify-out/
src/graphify-out/
.playwright-mcp/
+72 -9
View File
@@ -49,8 +49,8 @@ root `CLAUDE.md`는 이 목록의 동기화된 요약이다. 두 문서가 어
## Gradle 정책 권위
- `src/config/architecture/modules.json`: 등록된 모든 leaf의 ID, repository-relative 소스 경로,
Gradle path, 허용 production project dependency edge. runtime membership은 실제 resolved
runtimeClasspath에서 검증하며 registry에 별도 membership 목록을 복제하지 않는다. leaf 목록과 그 개수의 SSOT는 registry다. 문서는 개수를 복제하지 않는다 —
Gradle path, 허용 production project dependency edge. runtime membership 목록은 없다: 조립 루트가
받을 수 있는 모듈은 `allowed_dependencies`가 정하고, 방향 게이트가 그 밖의 edge를 막는다. leaf 목록과 그 개수의 SSOT는 registry다. 문서는 개수를 복제하지 않는다 —
산문에 적힌 숫자는 leaf가 추가되는 순간 drift하기 때문이다. 이제 이걸 강제하는 태스크는 없다:
`verifyDocumentedLeafCount`는 삭제됐다. 문서에 적힌 수가 틀린 것은 결함이지만 빌드를 실패시킬
사유는 아니고, 그 태스크는 모든 `CLAUDE.md`와 `build.gradle`을 정규식으로 훑는 파서였다.
@@ -59,10 +59,16 @@ root `CLAUDE.md`는 이 목록의 동기화된 요약이다. 두 문서가 어
경로, 없는 디렉터리)만 여기서 실패한다. 허용되지 않는 edge 같은 아키텍처 규칙은
`verifyCleanArchitectureDependencies`가 답한다 — settings에서 죽으면 실행할 수 있는 태스크가
하나도 없다.
- `src/build-logic/`: convention plugin. leaf는 `ca.java-library` / `ca.spring-library` /
`ca.platform-module` 중 자기 성격을 선언하고, 그 플러그인이 toolchain·락·정적분석·테스트
기본값을 준다. `ca.architecture`가 아키텍처 검증 태스크를 소유한다.
- `src/build.gradle`: 루트 라이프사이클(`ci`, `releaseCheck`, `qualityCheck`,
- `src/build-logic/`: 아키텍처 코어(registry, 방향·순수성 task), 컨벤션, 테스트 레인 하나
(`strictTestLanes`). leaf는 `ca.java-library` / `ca.spring-library` / `ca.platform-module` 중
자기 성격을 선언하고, 그 플러그인이 toolchain·락·정적분석·테스트 기본값을 준다.
`ca.architecture`가 아키텍처 검증 태스크를 소유한다. 기능별 검사(notification·mongo·messaging·
graphql·JPA readiness 등)는 build-logic이 아니라 소유 leaf의 테스트다. 테스트가 저장소 파일을 읽으면
그 파일을 그 leaf의 test task `inputs`로 선언한다. 저장소 문서와 대조하는 테스트는 `mainStage()`
레인(`document-contract` 태그)으로 leaf `mainCheck`에서 돈다.
- `verifyEnvKeys`는 app-bootstrap 태스크로 유지한다(소유자 결정 4). 구현은 build-logic의
`ca.config-contract`다. `src/build-tools/` included build는 비워서 삭제했다.
- `src/build.gradle`: 루트 라이프사이클(`ci`, `mainCheck`, `releaseCheck`, `qualityCheck`,
`configContractCheck`, `integrationCheck`)과 버전/리비전
작업 파일의 소유 leaf는 registry의 `source_path`로 판단하고 가장 가까운 `src/**/CLAUDE.md`를
@@ -86,7 +92,7 @@ commit 정책은 모든 플랫폼에서 `human-only`이며 agent는 stage/commit
## 모듈 책임
모든 leaf 모듈의 ID, 실제 소스 경로, Gradle path, 허용 production 의존성, runtime membership은
모든 leaf 모듈의 ID, 실제 소스 경로, Gradle path, 허용 production 의존성은
`src/config/architecture/modules.json`이 SSOT다. focused test는 소유 leaf의 `gradle_path`에서
파생한다. 이 문서는 leaf 목록을 복제하지 않고 family 책임만 정의한다. 작업 파일에서는 가장 가까운
`src/**/CLAUDE.md`를 함께 읽는다.
@@ -145,6 +151,27 @@ Gradle 의존성 검증도 같은 registry를 읽는다. root 문서나 기억
- 그 밖의 `adapter:outbound:*`: external capability adapter contract를 검증한다.
- `app-bootstrap/settings`: configuration binding, validation, logging 설정을 검증한다.
테스트 작성 규칙 (새로 쓰거나 고치는 테스트에 적용):
1. 이름은 lowerCamelCase 행동 문장(`<상황/주체><결과>`)이다. 이름에 적은 성질은 반드시 단언한다.
2. `@DisplayName`은 메서드 이름으로 못 쓰는 내용(숫자, 기호, 이유)이 있을 때만 쓰고, 언어는 영어로
통일한다.
3. 본문 문장이 3개 이상이면 `// given` `// when` `// then` 주석과 구역 사이 빈 줄을 둔다. 준비할
것이 없으면 `// given`은 생략한다. `// when`은 정확히 하나다. 두 번 필요하면 테스트를 나눈다.
예외 테스트는 `catchThrowable`로 when을 분리한다(기존 `assertThatThrownBy`는 손댈 때
`// when & then`까지 허용). 한 줄 테스트와 ArchUnit `.check()`는 주석 없이 쓴다.
4. `@Nested`는 테스트 10개 이상이고 대상 연산이 2개 이상인 클래스에서만, 연산 단위로 한 단계만 쓴다.
5. then은 when의 결과 하나만 단언한다. 여러 필드는 `usingRecursiveComparison()` 또는
`extracting(..).containsExactly(..)`로 한 번에 비교한다. `isNotNull`/`isPresent`/
`doesNotThrowAnyException`만으로 끝내지 않는다(이름이 "예외 없음" 자체를 말할 때만 예외).
예외는 타입과 reason/message를 함께 단언한다. 표 형태 입력은 `@ParameterizedTest`로 쓴다.
6. 포트 대역은 hand-rolled fake를 포트당 하나, 포트 소유 모듈 testFixtures에 둔다. adapter가 있는
포트는 fake와 adapter가 같은 추상 계약 테스트(`XxxContract`)를 통과한다. Mockito는 프레임워크
경계(Spring Data repository, SDK client)와 장애 주입에만 쓴다.
GWT 주석을 검사하는 자동 게이트는 만들지 않는다. 주석은 bytecode에 없어 ArchUnit이 볼 수 없고,
실질적인 강제 수단은 fake와 adapter가 같은 계약 테스트를 상속하는 구조다.
검증 원칙:
- 완료를 주장하기 전에 `superpowers:verification-before-completion`을 사용한다.
@@ -157,9 +184,10 @@ Gradle 의존성 검증도 같은 registry를 읽는다. root 문서나 기억
cd src
./gradlew <owner-gradle-path>:check --console=plain # 그 leaf만: 컴파일·테스트·포맷·스타일·ErrorProne
./gradlew check # 모든 leaf의 check
./gradlew architectureCheck # 의존 방향·런타임 멤버십·application-core 순수성
./gradlew architectureCheck # 의존 방향·domain-core/shared-contract/application-* 순수성·ArchUnit
./gradlew qualityCheck # SpotBugs + FindSecBugs (leaf check에는 없다)
./gradlew ci # PR 게이트 = leaf check + architecture + quality + config + qualification
./gradlew ci # PR 게이트 = leaf check + architecture + quality
./gradlew mainCheck # main 단계 = env 계약·전체 기동·public path·전송/메시징 레인·leaf 문서 대조 레인
./gradlew verifyPublicPathSnapshot
./gradlew :app-bootstrap:verifyEnvKeys
```
@@ -169,6 +197,39 @@ leaf의 `check`는 그 leaf만 검사한다. 저장소 전체 질문은 이름
소유 leaf의 정확한 Gradle path는 `src/config/architecture/modules.json`에서 읽고 focused test
명령을 파생한다. root 문서에 leaf별 명령 목록을 복제하지 않는다.
## 부가 기능(capability) 모듈 규칙
Redis, Kafka, JPA 같은 부가 기능은 "의존성을 붙이면 켜지고, 떼면 사라지는 모듈"로 제공한다.
각 서비스는 `app-bootstrap/build.gradle`에 필요한 모듈만 `runtimeOnly` 한 줄로 고른다.
설계 근거는 `docs/superpowers/specs/2026-09-25-capability-module-packaging-design.md`.
템플릿 기본 조립은 web에서 쓰는 부분뿐이다: `adapter:inbound:web`, 운영 관측(actuator·metrics·
tracing·로그), `domain-core`·`application-core`·`shared-contract`, `adapter:outbound:support`·
`adapter:outbound:identifier`. 그 밖의 기능(JPA 포함)은 한 줄을 추가해서 켠다.
capability 모듈 완료 기준 (7개 모두 충족해야 "포장 완료"):
1. 서비스 코드는 application-core의 포트만 호출한다. 그래서 모듈을 `runtimeOnly`로 받을 수 있다.
2. 모듈이 자기 `AutoConfiguration.imports`를 가진다. 모듈이 있으면 켜지고, 필요하면 `enabled`
설정으로 끌 수 있다. 다른 자동 설정에 기대면 순서를 명시한다(`afterName`).
3. 켜면 완전히 동작한다. 문서에 적은 옵션은 전부 실제로 동작하고, 동작하지 않는 옵션은 설정 키
자체를 두지 않는다.
4. 설정 prefix는 하나만 쓴다. 바인딩은 `StrictSettingsBinder`, 값 검증은 설정 record의 compact
constructor에서 한다.
5. 포트 소유 모듈 testFixtures의 포트 계약 테스트(추상 클래스)를 fake와 실제 어댑터가 모두
통과한다. 실제 벤더(Testcontainers)로 도는 테스트가 1개 이상 있다.
6. 모듈 README에 세 가지를 적는다: 제공하는 것, 추가할 한 줄, 필요한 env 키.
7. 이 모듈을 아는 곳은 모듈 자신뿐이다. bootstrap의 scan 정규식이나 스위치 목록에 등록하지
않고, 한 줄을 지우면 기능이 완전히 사라진다.
모듈 설정 기본값은 `config/module-defaults/<모듈>.yml`에 두고 `adapter:outbound:support`의
`ModuleDefaultsEnvironmentPostProcessor` 하나가 읽는다. 의존성 closure에 support가 없는 leaf
(persistence-mongo, graphql)만 자기 EPP가 `config/<이름>.yml`을 읽는다.
서비스 코드가 모듈 타입을 직접 호출해야 하는 라이브러리형 기능은 `runtimeOnly`로 컴파일되지
않는다. 그런 기능은 가능한 한 포트 뒤로 옮기고, 불가피하면 서비스의 어댑터 leaf에서
`implementation`으로 받는다.
## 설정과 런타임
설정 규칙:
@@ -192,6 +253,8 @@ Docker/runtime 규칙:
1. `src/settings.gradle`의 `rootProject.name`을 새 프로젝트명으로 바꾼다.
2. Java package `dev.caskeleton`을 새 organization/project package로 바꾼다.
gRPC 플랫폼을 쓰면 proto 조직 이름 `caskeleton`(`src/grpc/grpc-contract/src/main/proto/caskeleton/`의
디렉터리, 각 `.proto`의 `package`·`java_package`)도 함께 바꾸고 `buf lint`로 확인한다.
3. `CaSkeletonApplication` 이름을 새 애플리케이션 이름으로 바꾼다.
4. production 모듈에는 목표 도메인의 entity, repository port, use case, adapter만 추가하고, 예시 코드는 `sample-portfolio`에 격리한다.
5. 모듈 이름과 경계는 유지한다.
+36 -12
View File
@@ -21,12 +21,20 @@ If this summary drifts from `AGENTS.md`, `AGENTS.md` wins and this summary must
## Gradle policy authorities
- `src/config/architecture/modules.json`: every registered leaf identity, repository-relative source
paths, Gradle paths, allowed production project dependency edges, and the exact runtime
memberships of both composition roots. The registry owns the leaf list and its size; no document
restates the count, because a number written in prose drifts the moment a leaf is added.
paths, Gradle paths and allowed production project dependency edges. There is no runtime
membership list: what a composition root may take is its `allowed_dependencies`, and the direction
gate refuses any other edge. The registry owns the leaf list and its size; no document restates
the count, because a number written in prose drifts the moment a leaf is added.
- `src/settings.gradle`: fail-closed registry validation, project inclusion, and directory mapping.
- `src/build.gradle`: `verifyCleanArchitectureDependencies` and the other architecture-wide
verification tasks.
- `src/build-logic/`: the architecture core (registry, direction and purity tasks), the conventions,
and one test-lane mechanism (`strictTestLanes`). Feature-specific checks are the owning leaf's
tests; a test that reads repository files declares them as that leaf's test `inputs`, and a test
that compares a leaf with repository documents is a `mainStage()` lane (tag `document-contract`)
in that leaf's `mainCheck`.
- `verifyEnvKeys` stays an app-bootstrap task (owner decision 4); its implementation is build-logic's
`ca.config-contract`. The `src/build-tools/` included build was emptied and removed.
- `src/build.gradle`: the root lifecycle (`ci`, `mainCheck`, `releaseCheck` and the named
repository-wide gates).
Commit policy is `human-only`: agents do not stage, commit, amend, or push implementation changes.
@@ -66,8 +74,8 @@ own `*-api` leaves are its ports, its broker leaves are its adapters, its starte
root — and the messaging module review (`docs/reviews/2026-08-14-messaging-module-code-review.md`
MSG-023 §6.2) chose that layout deliberately over folding it into `adapter:outbound:*`. This
application reaches it through the application-owned anti-corruption bridge in
`adapter:outbound:messaging` (MSG-015). The canonical bridge exists; legacy outbox/realtime cutover
still has explicitly documented seams in `src/messaging/CLAUDE.md`.
`adapter:outbound:messaging` (MSG-015). The canonical bridge is the only path: the legacy outbox
append port and the legacy Kafka publishing seam were deleted (owner decision 7).
Never infer an individual leaf's Gradle path, allowed dependency, or test command from this table.
Read its `gradle_path` and `allowed_dependencies` from `src/config/architecture/modules.json`; runtime
@@ -112,15 +120,31 @@ Architecture-wide commands:
```
A leaf's `check` covers that leaf only — compile, its tests, Spotless, Checkstyle, Error Prone.
Repository-wide questions have their own names: `architectureCheck` (dependency direction, runtime
membership, application-core purity, Git-carryable sources), `qualityCheck` (SpotBugs, FindSecBugs),
`configContractCheck` (the environment contract), `integrationCheck` (the declared strict test
lanes). `ci` is leaf checks + architectureCheck + qualityCheck + configContractCheck + qualificationCheck; `releaseCheck` adds
provenance, archive hygiene and the public-path snapshot.
Repository-wide questions have their own names: `architectureCheck` (dependency direction, purity
of domain-core/shared-contract/application-*, Git-carryable sources, ArchUnit), `qualityCheck`
(SpotBugs, FindSecBugs), `configContractCheck` (the environment contract), `integrationCheck` (the
declared strict integration lanes; a lane that needs an input the build was not given is left out
and named). `ci` (pull request) is leaf checks (API surfaces included, owner decision 20) +
architectureCheck + qualityCheck; `mainCheck` (main branch) is configContractCheck +
qualificationCheck + the sample web contract + the public-path snapshot + the transport and
messaging qualification lanes + every leaf's `mainCheck` (document-contract lanes, MinIO lanes);
`releaseCheck` is the tag-only checks: release provenance and the public-path snapshot.
Test-writing rules (behavior-sentence names that assert what they promise, given/when/then comments,
one `// when`, one fake per port in the port owner's testFixtures, fake and adapter sharing one
abstract contract test) are canonical in `AGENTS.md`.
Use public-path and env-key checks only when their surfaces changed. Full `test`, `check` or `ci`
requires the controller's workflow authorization.
## Capability modules
Optional features (JPA, Redis, Kafka, notification, Mongo, object storage, HTTP client, GraphQL,
WebSocket, gRPC, file server) are modules that turn on when present and disappear when removed. A
service selects them with one `runtimeOnly` line each in `app-bootstrap/build.gradle`; the template's
default composition is the web inbound adapter, observability, the cores, and support/identifier. The
seven completion criteria for a capability module are canonical in `AGENTS.md`.
## Advisory and reporting
Use dependency-DAG/topological reasoning and 3–5 materially distinct alternatives when that many
+13 -9
View File
@@ -23,7 +23,7 @@ family 수준의 책임은 다음과 같습니다.
| `application-core` | command·유스케이스·application 정책·트랜잭션 port. inbound DTO·persistence entity 금지 |
| `adapter:inbound:*` | HTTP·gRPC·GraphQL·WebSocket transport 경계, DTO·validation·인증·에러 매핑 |
| `adapter:outbound:persistence-*` | JPA/PostgreSQL·MongoDB 영속 구현과 매핑·migration |
| `adapter:outbound:*` | support(공유 베이스)·messaging·cache·notification·object storage·file·HTTP client·identifier 능력을 port 뒤에서 구현. 외부 연동 어댑터(messaging·cache·notification·HTTP client)는 기본 비활성 |
| `adapter:outbound:*` | support(공유 베이스)·messaging·cache·notification·object storage·file·HTTP client·identifier 능력을 port 뒤에서 구현. 기본 조립에는 support·identifier만 들어 있고, 나머지는 `app-bootstrap/build.gradle`의 `runtimeOnly` 한 줄로 고릅니다 |
| `shared-contract` | skeleton 전역 운영 계약. business/domain 개념 저장 금지 |
| `app-bootstrap` | Spring Boot entrypoint와 composition root |
| `sample-portfolio` | WorkLog 예시 도메인(fixture/reference). production이 의존하지 않음 |
@@ -38,11 +38,10 @@ test는 해당 Gradle path에서 `./gradlew <gradle-path>:test --console=plain`
전제조건은 Temurin 21(루트 [.tool-versions](.tool-versions)에 고정)과 Docker Engine 또는 Docker Desktop입니다. Gradle은 저장소 wrapper를 씁니다. 첫 실행 진입점은 하나입니다.
```bash
cd src
./gradlew bootstrap
scripts/bootstrap-local.sh # 다른 Compose overlay는 scripts/bootstrap-local.sh <profile>
```
`bootstrap`은 compile 검사, PostgreSQL Compose 기동, 애플리케이션 이미지 build·기동(startup Flyway 포함), sample 격리 검증, `GET /api/healthcheck` HTTP smoke를 순서대로 실행합니다. 각 단계가 별도 Gradle task라 실패 단계가 task 이름으로 드러납니다. 기동을 확인하려면 health endpoint를 호출합니다.
`scripts/bootstrap-local.sh`는 compile 검사, PostgreSQL Compose 기동, 애플리케이션 이미지 build·기동, `GET /api/healthcheck` HTTP smoke를 순서대로 실행합니다. 각 단계가 `bootstrap N/4` 줄을 찍고 실패하면 그 단계에서 멈추므로 실패 단계가 드러납니다. 기동을 확인하려면 health endpoint를 호출합니다.
```bash
curl -fsS http://localhost:8080/api/healthcheck
@@ -56,22 +55,27 @@ docker compose -f docker-compose.yml -f docker-compose.local.yml down
`src/.env.example`은 배포 환경 변수의 추적 가능한 복사/검증 계약이고 `src/.env`는 로컬 실행 입력입니다. 전체 환경 변수 목록과 조정 시점은 [src/README.md](src/README.md)와 [docs/registries/env-keys.yaml](docs/registries/env-keys.yaml)에 있습니다.
### 프로파일별 데이터스토어
### 기본 조립과 부가 기능
`bootstrap`은 컨테이너 경로(PostgreSQL)를 검증하는 첫 실행 진입점입니다. 일상 개발은 Docker 없이 돌리는 `local` 프로파일이며, 이때 데이터스토어는 H2 in-memory입니다.
기본 조립(`bootJar`)은 web, 관측, `domain-core`·`application-core`·`shared-contract`, support,
identifier뿐이라 DB·Redis·Kafka 없이 기동합니다.
```bash
cd src
./gradlew :app-bootstrap:bootRun
```
| 프로파일 | 데이터스토어 | 스키마 소유자 |
DB, Redis, Kafka, 알림, 파일 서버 같은 부가 기능은 `app-bootstrap/build.gradle`에 주석 처리된
`runtimeOnly` 한 줄씩으로 있습니다. 줄의 주석을 풀고 필요한 env를 넣으면 켜지고, 줄을 지우면 사라집니다.
줄마다 필요한 env와 끄는 키는 [src/README.md](src/README.md)의 "기능 추가 = 한 줄 + env" 표에 있습니다.
| 프로파일 | 데이터스토어 (persistence-jpa 줄을 넣었을 때) | 스키마 소유자 |
| --- | --- | --- |
| `local` (bootRun 기본) | H2 in-memory | Hibernate `create-drop` |
| `local` | Compose PostgreSQL (`./gradlew :app-bootstrap:bootRunH2`는 줄 없이도 모듈을 자기 classpath에 올려 H2 in-memory로 실행) | Flyway (H2는 Hibernate `create-drop`) |
| `dev` | PostgreSQL | Flyway |
| `prod` | PostgreSQL | Flyway |
`local`은 wiring과 애플리케이션 동작을 검증하고, migration과 vendor 동작은 검증하지 않습니다. 프로파일별 설정은 [src/app-bootstrap/src/main/resources/](src/app-bootstrap/src/main/resources/)의 `application-{local,dev,prod}.yml`이, 상세 설명은 [src/README.md](src/README.md)가 소유합니다.
H2 실행은 wiring과 애플리케이션 동작만 검증하고, migration과 vendor 동작은 검증하지 않습니다. 프로파일별 설정은 [src/app-bootstrap/src/main/resources/](src/app-bootstrap/src/main/resources/)의 `application-{local,dev,prod}.yml`이, 상세 설명은 [src/README.md](src/README.md)가 소유합니다.
## 새 프로젝트로 시작하기
+6 -1
View File
@@ -33,7 +33,12 @@ services:
BUILD_VERSION: "${BUILD_VERSION:-0.0.1+0000000}"
GIT_SHA: "${GIT_SHA:-0000000}"
SOURCE_URL: "${SOURCE_URL:-https://example.invalid/ca-tmpl}"
image: caskeleton:${BUILD_VERSION:-0.0.1_local_0000000}
# default = the composition a service ships. scripts/run-compose-runtime-smoke.sh sets
# qualification: every capability module present, each lane switching on what it tests.
COMPOSITION: "${COMPOSITION:-default}"
# The composition is in the tag, so a lane's qualification image is never reused as the
# default one (Compose reuses a matching tag instead of building).
image: caskeleton:${BUILD_VERSION:-0.0.1_local_0000000}-${COMPOSITION:-default}
# Generated per run by scripts/run-compose-runtime-smoke.sh and removed on teardown. Seven values
# have no inline default on purpose — the datasource address and credential, the application
# name, and the JWT issuer and audience — so a lane has to supply them, and a lane that borrowed
@@ -1,8 +1,17 @@
# ADR-GRPC-002: Schema governance runs without protoc and without the Buf CLI
- Status: accepted
- Status: **superseded (2026-09-28)** by owner decision 18 of the 2026-09-25 review follow-up
- Date: 2026-08-30
- Scope: `:grpc:grpc-proto-contract`, `:grpc:grpc-codegen`
- Scope: `:grpc:grpc-proto-contract`, `:grpc:grpc-codegen` (both removed)
> **Superseded.** The regex `.proto` validator and the Java re-implementation of Buf's rules were
> deleted. The schema now lives in `:grpc:grpc-contract` (`src/grpc/grpc-contract/src/main/proto`),
> compiled by the Gradle protobuf plugin (`com.google.protobuf`, version pinned in
> `src/gradle/libs.versions.toml`; protoc and the protobuf-java runtime are both `protobufGrpc`).
> Generated sources are excluded from Spotless, Checkstyle and Error Prone in that leaf only.
> `buf lint` and `buf breaking` (`src/grpc/grpc-contract/buf.yaml`, STANDARD lint, FILE breaking)
> run in CI, job `grpc-proto-buf` in `.github/workflows/ci-quality-gates.yml`. The proto organization
> is `caskeleton` (was `hyeonworks`). The text below is kept as the record of the original decision.
## Context
@@ -2,7 +2,7 @@
- Status: accepted
- Date: 2026-08-30
- Scope: `:grpc:grpc-core-api`, `:grpc:grpc-policy`, `:grpc:grpc-testkit`
- Scope: `:grpc:grpc-core-api`, `:grpc:grpc-runtime` (was `grpc-policy`), `:grpc:grpc-testkit`
## Context
@@ -2,7 +2,7 @@
- Status: accepted
- Date: 2026-08-30
- Scope: `:grpc:grpc-policy`, `:grpc:grpc-operation-ledger-jpa`, `:grpc:grpc-core-api`
- Scope: `:grpc:grpc-runtime` (was `grpc-policy`), `:grpc:grpc-operation-ledger-jpa`, `:grpc:grpc-core-api`
## Context
@@ -2,7 +2,7 @@
- Status: accepted
- Date: 2026-08-30
- Scope: `:grpc:grpc-policy`
- Scope: `:grpc:grpc-runtime` (was `grpc-policy`)
## Context
@@ -2,7 +2,7 @@
- Status: accepted
- Date: 2026-08-31
- Scope: `:grpc:grpc-discovery`, `:grpc:grpc-client`
- Scope: `:grpc:grpc-runtime` (was `grpc-discovery`, `grpc-client`)
## Context
@@ -63,6 +63,6 @@ declaration is a wrong statement somebody wrote down, and a missing one is a que
`GrpcChannelProfileValidator` takes resolved counts where they are known at startup and skips the
check where they are not, rather than guessing and failing on a name that cannot be resolved yet.
**xDS is reachable, and not by this route.** It lives in `grpc-advanced-resilience` behind its
**xDS is reachable, and not by this route.** It lives in `grpc-advanced` (package `resilience`/`xds`) behind its
capability flag and its production approval, and `GrpcXdsStartupGuard.advertisableAsStableSupport()`
returns false so the Stable support statement cannot widen quietly. See ADR-GRPC-ADV-001.
@@ -29,7 +29,9 @@ production unapproved — because the remedy differs in each case.
**Promotion evidence is per capability.** `GrpcAdvancedPromotionEvidence` is one record per
capability, so no promotion can drag another along;
`GrpcAdvancedPromotionGate.capabilitiesDraggedAlong` returns an empty list, and that is a tested
property rather than a claim. Two thresholds: seven days of soak plus complete evidence for
property rather than a claim. (2026-09-28: the gate classes were removed because nothing outside
their own tests called them — review 2026-09-24 S5-lead-4. The per-capability rule stands as a
review rule in `docs/runbooks/grpc-advanced-capabilities.md`.) Two thresholds: seven days of soak plus complete evidence for
`ADVANCED_STABLE`, thirty for a Stable default, because the second means every deployment gets the
capability's dependencies and its failure modes.
@@ -1,6 +1,9 @@
# ADR-JPA-002 — Retry re-runs the whole use case
- Status: Accepted
- Status: Superseded (2026-09-25) — the retry engine this ADR describes
(`FullTransactionRetryCoordinator`, `JpaTransactionExecutor`) was removed. `SpringTransactionPort`
retries nothing; a caller that retries still re-runs the whole use case, which is the part of this
decision that stands. The last commit is in `docs/capability-status.md`.
- Date: 2026-08-11
- Design: §19.2
+7 -4
View File
@@ -1,6 +1,8 @@
# ADR-JPA-003 — Completion unknown is never retried
- Status: Accepted
- Status: Accepted; amended 2026-09-25 — `TransactionCompletionResolver`, `CommitFailureClassifier`
and the retry engine were removed. The invariant holds because `SpringTransactionPort`, the only
transaction engine, retries nothing; enforcement below is updated accordingly.
- Date: 2026-08-11
- Design: §17
@@ -14,7 +16,7 @@ acknowledgement may simply have been lost. The driver cannot tell the two apart.
`TransactionCompletionUnknownException` is never retried, automatically or otherwise. It is
produced only by a failure observed while the transaction phase is `COMMITTING`, and only for
SQLSTATE `40003`, a connection-class (`08*`) state, or a transport break. Recovery is
domain-specific reconciliation through `TransactionCompletionResolver`.
domain-specific reconciliation.
## Consequences
@@ -37,5 +39,6 @@ which idempotency record, business row, or outbox entry proves the write happene
## Enforcement
`JpaFailureContextTest`; `DefaultJpaRetryPolicyTest`; `CommitFailureClassifierTest`; release gate
`completion-unknown-no-retry`.
`JpaFailureContextTest`;
`PostgreSqlTransactionIntegrationTest#connectionLossDuringCommitSurfacesAsAFailureAndIsNeverRetried`
(also the `jpa-failure` lane, i.e. release gate `completion-unknown-no-retry`).
@@ -33,5 +33,6 @@ intended cost: it makes schema change reviewable and reversible.
## Enforcement
`JpaDangerousConfigurationGuard`; `FlywaySchemaPolicy`; `FlywayValidationGate`;
`PostgreSqlRuntimeRoleVerifier`; release gates `flyway-validate` and `runtime-role-no-ddl`.
`JpaDangerousConfigurationGuard`; `FlywaySchemaPolicy`; `FlywayValidationGate` (testkit, used by the
migration contract tests); `PostgreSqlRuntimeRoleVerifier`; release gates `flyway-validate` and
`runtime-role-no-ddl`.
@@ -3,6 +3,13 @@
- **Status:** Accepted
- **Date:** 2026-08-13
- **Design source:** design §2 (D-15), §3.2–§3.3; Advanced expansion plan Task 15
- **Amended 2026-09-25:** the `ca-skeleton.persistence-mongo.advanced.*.enabled` binding
(`MongoAdvancedConfiguration`/`MongoAdvancedSettings`) was imported by nothing, so no deployment
property ever reached the flags; it was removed together with `propertyFor`. The flags are now
built in code by the adapter that constructs an entry point. `MongoAdvancedPromotionGate`,
`MongoAdvancedPromotionEvidence`, `MongoVectorSearchBenchmarkGate` and the search, vector, time
series and GridFS packages (interfaces with no implementation) were removed. The evidence
categories below remain a review obligation; no class checks them.
## Context
@@ -19,15 +19,16 @@ retention, its own eviction and its own opinion about ordering.
## Decision
**Three outcomes, expressed in the stream rather than in the status.** `WebStreamEnvelope` is sealed
over `Item`, `Failure` and `Complete`. A client that sees neither terminal envelope has been cut off,
and that third case is recorded as `ABRUPT_CLOSE` rather than counted as a completion — which is
where a rising rate of mid-stream failures would otherwise hide.
**Three outcomes, expressed in the stream rather than in the status.** The wire record (for NDJSON,
`NdjsonRecord`) is an item, a failure or a completion. A client that sees neither terminal record
has been cut off, and that third case is recorded as `ABRUPT_CLOSE` rather than counted as a
completion — which is where a rising rate of mid-stream failures would otherwise hide.
**Nothing writes a problem document onto a committed response.** `WebStreamTerminationMapper`
branches on whether any byte has been written. Before commit, an RFC 9457 problem with a real
status; after, a terminal record. Attempting both produces a body that is half stream and half JSON,
which no client parses and every proxy caches as a success.
**Nothing writes an error body onto a committed response.** Before commit, a failure is an ordinary
HTTP error (the `Envelope`) with a real status; after, a terminal record. Attempting both produces a
body that is half stream and half JSON, which no client parses and every proxy caches as a success.
(The mapper that encoded this, `WebStreamTerminationMapper`, was removed on 2026-09-25 with the
problem-document vocabulary it returned; the rule stands.)
**Positions are monotonic, and it is enforced.** `WebStreamEvidence.recordDelivered` refuses a
repeated or regressing position. A client deduplicating on position would silently drop the second
@@ -6,8 +6,9 @@
## Context
Advanced Task 2 offers a virtual-thread executor for MVC; Task 3 offers a bounded blocking bridge
for WebFlux.
Advanced Task 2 offers a virtual-thread executor for MVC; Task 3 offered a bounded blocking bridge
for WebFlux. (The WebFlux adapter for it was removed on 2026-09-25 — the template is servlet only;
`advanced.blockingbridge` remains as library code.)
A platform-thread MVC deployment has an implicit concurrency limit — the thread pool — and that
limit is usually what has been protecting the database pool, the outbound HTTP bulkhead and every
@@ -40,6 +41,9 @@ offload; `BlockingBridgeBudget` bounds the concurrency and refuses a caller that
in time, because otherwise a slow dependency's callers accumulate until the heap does and the fast
dependencies starve behind them.
> 2026-09-25: `advanced.blockingbridge` was removed. Its WebFlux adapter went with the WebFlux twin
> (D4), and a budget for a bridge that no longer exists bounded nothing.
**Pinning is observed, not assumed away.** `VirtualThreadProfile.requiredObservations()` lists what
has to be watched — `jdk.VirtualThreadPinned` above all. A synchronized block held across a blocking
call pins the carrier thread, the carrier pool is bounded by CPU count, and enough pinned carriers is
@@ -23,6 +23,10 @@ contributor that mutates it on the way to 3.2 changes the artifact that is actua
silently, and only when the experimental lane runs. `OpenApi32CompatibilityReport` compares the
snapshot hash before and after and makes a difference a promotion blocker.
> 2026-09-25: `OpenApi32CompatibilityReport` and `OpenApiToolchainMatrix` were removed — promotion
> checks kept in production code, called only by their own tests. `WebOpenApi32Generator` remains
> as library code in `adapter:inbound:web-advanced`; the decision below is unchanged.
**Four kinds of tool are checked separately.** A parser reports structural errors; a linter applies
style rules and accepts documents a parser rejects; a generator produces client code, and this is
where an unsupported construct surfaces — not as an error but as a method with the wrong signature;
@@ -1,6 +1,9 @@
# ADR-WS-001: The WebSocket platform ships as packages in one leaf, with machine-checked boundaries
- Status: accepted
- Status: Superseded 2026-09-25 — the eighteen-package platform was cut to the parts a Spring
configuration or a real-container lane reaches: the `stomp` channel and the servlet handler
library (`servlet`, `outbound`, `budget`). The Advanced packages, the reactive runtime and the
`WebSocketArchitectureRules` pack went with the rest (see `docs/capability-status.md`).
- Date: 2026-08-25
- Scope: `:adapter:inbound:websocket`
+2 -1
View File
@@ -1,6 +1,7 @@
# ADR-WS-002: Resume and cluster state are caches, and are treated as caches
- Status: Accepted
- Status: Superseded 2026-09-25 — `advanced.resume`, `advanced.cluster` and `advanced.presence`
were removed: nothing assembled them (see `docs/capability-status.md`).
- Date: 2026-08-25
- Scope: `adapter:inbound:websocket` — `advanced.resume`, `advanced.cluster`, `advanced.presence`
@@ -1,6 +1,7 @@
# ADR-WS-003: STOMP is an Advanced adapter with a declared destination catalog
- Status: Accepted
- Status: Superseded 2026-09-25 — `advanced.stomp` and `advanced.stomp.rabbit` were removed; the
`stomp` package is the only STOMP channel (see `docs/capability-status.md`).
- Date: 2026-08-25
- Scope: `adapter:inbound:websocket` — `advanced.stomp`, `advanced.stomp.rabbit`
+4 -244
View File
@@ -5,180 +5,21 @@
# split into capability artifacts.
# Update only after review with:
# ./gradlew :adapter:inbound:graphql:updateGraphQlApiSurface -PapproveGraphQlApiSurfaceChange
# types: 401
# types: 161
dev.caskeleton.adapter.inbound.graphql.HealthGraphqlController
dev.caskeleton.adapter.inbound.graphql.advanced.admin.GraphQlAdminPrincipal
dev.caskeleton.adapter.inbound.graphql.advanced.admin.GraphQlPersistedOperationAdminAuthorization
dev.caskeleton.adapter.inbound.graphql.advanced.admin.GraphQlPersistedOperationAdminDeniedException
dev.caskeleton.adapter.inbound.graphql.advanced.admin.GraphQlPersistedOperationAdminPort
dev.caskeleton.adapter.inbound.graphql.advanced.admin.GraphQlPersistedOperationAdminService
dev.caskeleton.adapter.inbound.graphql.advanced.admin.GraphQlPersistedOperationAudit
dev.caskeleton.adapter.inbound.graphql.advanced.admin.GraphQlPersistedOperationBlockCommand
dev.caskeleton.adapter.inbound.graphql.advanced.admin.GraphQlPersistedOperationRemovalGate
dev.caskeleton.adapter.inbound.graphql.advanced.admin.GraphQlPersistedOperationRemovalRejectedException
dev.caskeleton.adapter.inbound.graphql.advanced.admin.GraphQlPersistedOperationUsage
dev.caskeleton.adapter.inbound.graphql.advanced.bootstrap.GraphQlAdvancedCapability
dev.caskeleton.adapter.inbound.graphql.advanced.bootstrap.GraphQlAdvancedCapabilityDisabledException
dev.caskeleton.adapter.inbound.graphql.advanced.bootstrap.GraphQlAdvancedCapabilityGrade
dev.caskeleton.adapter.inbound.graphql.advanced.bootstrap.GraphQlAdvancedDependencyRules
dev.caskeleton.adapter.inbound.graphql.advanced.bootstrap.GraphQlAdvancedFeatureFlags
dev.caskeleton.adapter.inbound.graphql.advanced.bootstrap.GraphQlAdvancedModuleGuard
dev.caskeleton.adapter.inbound.graphql.advanced.chaining.GraphQlChainedDataLoaderPolicy
dev.caskeleton.adapter.inbound.graphql.advanced.chaining.GraphQlChainedDispatchConfigurer
dev.caskeleton.adapter.inbound.graphql.advanced.chaining.GraphQlChainedLoaderMetrics
dev.caskeleton.adapter.inbound.graphql.advanced.chaining.GraphQlDataLoaderCycleDetector
dev.caskeleton.adapter.inbound.graphql.advanced.chaining.GraphQlDataLoaderDependencyCycleException
dev.caskeleton.adapter.inbound.graphql.advanced.chaining.GraphQlDataLoaderDependencyGraph
dev.caskeleton.adapter.inbound.graphql.advanced.codegen.GraphQlClientOperationGenerator
dev.caskeleton.adapter.inbound.graphql.advanced.codegen.GraphQlCodegenBoundaryException
dev.caskeleton.adapter.inbound.graphql.advanced.codegen.GraphQlCodegenProfile
dev.caskeleton.adapter.inbound.graphql.advanced.codegen.GraphQlGeneratedCompatibilityGate
dev.caskeleton.adapter.inbound.graphql.advanced.codegen.GraphQlGeneratedSourceBoundary
dev.caskeleton.adapter.inbound.graphql.advanced.codegen.GraphQlOperationValidator
dev.caskeleton.adapter.inbound.graphql.advanced.codegen.GraphQlScalarMapping
dev.caskeleton.adapter.inbound.graphql.advanced.codegen.GraphQlTransportTypeGenerator
dev.caskeleton.adapter.inbound.graphql.advanced.composition.GraphQlFederationCompositionGate
dev.caskeleton.adapter.inbound.graphql.advanced.composition.GraphQlFederationCompositionResult
dev.caskeleton.adapter.inbound.graphql.advanced.composition.GraphQlFederationDeploymentOrder
dev.caskeleton.adapter.inbound.graphql.advanced.composition.GraphQlFederationLatencyBudget
dev.caskeleton.adapter.inbound.graphql.advanced.composition.GraphQlFederationReleaseEvidence
dev.caskeleton.adapter.inbound.graphql.advanced.composition.GraphQlFederationReleaseRejectedException
dev.caskeleton.adapter.inbound.graphql.advanced.composition.GraphQlFederationUsageReport
dev.caskeleton.adapter.inbound.graphql.advanced.composition.GraphQlSubgraphContract
dev.caskeleton.adapter.inbound.graphql.advanced.federation.GraphQlFederationBatchResolver
dev.caskeleton.adapter.inbound.graphql.advanced.federation.GraphQlFederationCapability
dev.caskeleton.adapter.inbound.graphql.advanced.federation.GraphQlFederationEntityKey
dev.caskeleton.adapter.inbound.graphql.advanced.federation.GraphQlFederationEntityResolver
dev.caskeleton.adapter.inbound.graphql.advanced.federation.GraphQlFederationProperties
dev.caskeleton.adapter.inbound.graphql.advanced.federation.GraphQlFederationRepresentationException
dev.caskeleton.adapter.inbound.graphql.advanced.federation.GraphQlFederationSchemaFactory
dev.caskeleton.adapter.inbound.graphql.advanced.get.GraphQlHttpDraftCompatibilityReport
dev.caskeleton.adapter.inbound.graphql.advanced.get.GraphQlHttpGetCachePolicy
dev.caskeleton.adapter.inbound.graphql.advanced.get.GraphQlHttpGetCsrfPolicy
dev.caskeleton.adapter.inbound.graphql.advanced.get.GraphQlHttpGetOperationPolicy
dev.caskeleton.adapter.inbound.graphql.advanced.get.GraphQlHttpGetProfile
dev.caskeleton.adapter.inbound.graphql.advanced.get.GraphQlHttpGetRejectedException
dev.caskeleton.adapter.inbound.graphql.advanced.get.GraphQlHttpGetRequestParser
dev.caskeleton.adapter.inbound.graphql.advanced.incremental.GraphQlIncrementalCancellation
dev.caskeleton.adapter.inbound.graphql.advanced.incremental.GraphQlIncrementalCompatibilityGate
dev.caskeleton.adapter.inbound.graphql.advanced.incremental.GraphQlIncrementalDeliveryCapability
dev.caskeleton.adapter.inbound.graphql.advanced.incremental.GraphQlIncrementalDeliveryProfile
dev.caskeleton.adapter.inbound.graphql.advanced.incremental.GraphQlIncrementalDeliveryRejectedException
dev.caskeleton.adapter.inbound.graphql.advanced.incremental.GraphQlIncrementalPatch
dev.caskeleton.adapter.inbound.graphql.advanced.incremental.GraphQlIncrementalTransportPolicy
dev.caskeleton.adapter.inbound.graphql.advanced.persisted.GraphQlPersistedOperation
dev.caskeleton.adapter.inbound.graphql.advanced.persisted.GraphQlPersistedOperationConflictException
dev.caskeleton.adapter.inbound.graphql.advanced.persisted.GraphQlPersistedOperationId
dev.caskeleton.adapter.inbound.graphql.advanced.persisted.GraphQlPersistedOperationInterceptor
dev.caskeleton.adapter.inbound.graphql.advanced.persisted.GraphQlPersistedOperationLookup
dev.caskeleton.adapter.inbound.graphql.advanced.persisted.GraphQlPersistedOperationNotFoundException
dev.caskeleton.adapter.inbound.graphql.advanced.persisted.GraphQlPersistedOperationPolicy
dev.caskeleton.adapter.inbound.graphql.advanced.persisted.GraphQlPersistedOperationRecordMapping
dev.caskeleton.adapter.inbound.graphql.advanced.persisted.GraphQlPersistedOperationRegistry
dev.caskeleton.adapter.inbound.graphql.advanced.persisted.GraphQlPersistedOperationRejectedException
dev.caskeleton.adapter.inbound.graphql.advanced.persisted.GraphQlPersistedOperationRequest
dev.caskeleton.adapter.inbound.graphql.advanced.persisted.GraphQlPersistedOperationStatus
dev.caskeleton.adapter.inbound.graphql.advanced.persisted.GraphQlPersistedOperationTransition
dev.caskeleton.adapter.inbound.graphql.advanced.persisted.GraphQlPersistedPreparsedBridge
dev.caskeleton.adapter.inbound.graphql.advanced.persisted.OperationalStoreGraphQlPersistedOperationRegistry
dev.caskeleton.adapter.inbound.graphql.advanced.release.GraphQlAdvancedCompatibilityMatrix
dev.caskeleton.adapter.inbound.graphql.advanced.release.GraphQlAdvancedPromotionDecision
dev.caskeleton.adapter.inbound.graphql.advanced.release.GraphQlAdvancedReleaseEvidence
dev.caskeleton.adapter.inbound.graphql.advanced.release.GraphQlAdvancedReleaseException
dev.caskeleton.adapter.inbound.graphql.advanced.release.GraphQlAdvancedReleaseGate
dev.caskeleton.adapter.inbound.graphql.advanced.release.GraphQlAdvancedRunbookIndex
dev.caskeleton.adapter.inbound.graphql.advanced.release.GraphQlAdvancedSoakScenario
dev.caskeleton.adapter.inbound.graphql.advanced.replay.GraphQlReplayAuthorization
dev.caskeleton.adapter.inbound.graphql.advanced.replay.GraphQlReplayAuthorizationException
dev.caskeleton.adapter.inbound.graphql.advanced.replay.GraphQlReplayGapException
dev.caskeleton.adapter.inbound.graphql.advanced.replay.GraphQlReplayHistoryLostException
dev.caskeleton.adapter.inbound.graphql.advanced.replay.GraphQlReplayPosition
dev.caskeleton.adapter.inbound.graphql.advanced.replay.GraphQlReplaySource
dev.caskeleton.adapter.inbound.graphql.advanced.replay.GraphQlSnapshotLiveHandoff
dev.caskeleton.adapter.inbound.graphql.advanced.replay.GraphQlSubscriptionCursor
dev.caskeleton.adapter.inbound.graphql.advanced.rsocket.GraphQlRSocketAdmission
dev.caskeleton.adapter.inbound.graphql.advanced.rsocket.GraphQlRSocketAuthentication
dev.caskeleton.adapter.inbound.graphql.advanced.rsocket.GraphQlRSocketCapability
dev.caskeleton.adapter.inbound.graphql.advanced.rsocket.GraphQlRSocketErrorMapper
dev.caskeleton.adapter.inbound.graphql.advanced.rsocket.GraphQlRSocketHandlerFactory
dev.caskeleton.adapter.inbound.graphql.advanced.rsocket.GraphQlRSocketProperties
dev.caskeleton.adapter.inbound.graphql.advanced.rsocket.GraphQlRSocketRoutePolicy
dev.caskeleton.adapter.inbound.graphql.advanced.rsocket.GraphQlRSocketRouteRejectedException
dev.caskeleton.adapter.inbound.graphql.advanced.security.GraphQlSubscriptionAuthorizationPolicy
dev.caskeleton.adapter.inbound.graphql.advanced.security.GraphQlWebSocketAuthenticationException
dev.caskeleton.adapter.inbound.graphql.advanced.security.GraphQlWebSocketAuthenticationInterceptor
dev.caskeleton.adapter.inbound.graphql.advanced.security.GraphQlWebSocketCloseReason
dev.caskeleton.adapter.inbound.graphql.advanced.security.GraphQlWebSocketCredentialExpiry
dev.caskeleton.adapter.inbound.graphql.advanced.security.GraphQlWebSocketPrincipal
dev.caskeleton.adapter.inbound.graphql.advanced.security.GraphQlWebSocketRevocationSignal
dev.caskeleton.adapter.inbound.graphql.advanced.springdata.GraphQlRepositoryAllowlist
dev.caskeleton.adapter.inbound.graphql.advanced.springdata.GraphQlRepositoryArgumentPolicy
dev.caskeleton.adapter.inbound.graphql.advanced.springdata.GraphQlRepositoryExposure
dev.caskeleton.adapter.inbound.graphql.advanced.springdata.GraphQlRepositoryExposureRejectedException
dev.caskeleton.adapter.inbound.graphql.advanced.springdata.GraphQlRepositoryExposureValidator
dev.caskeleton.adapter.inbound.graphql.advanced.springdata.GraphQlRepositoryPaginationPolicy
dev.caskeleton.adapter.inbound.graphql.advanced.springdata.GraphQlRepositoryProjectionPolicy
dev.caskeleton.adapter.inbound.graphql.advanced.sse.GraphQlSseAdmission
dev.caskeleton.adapter.inbound.graphql.advanced.sse.GraphQlSseConnectionPolicy
dev.caskeleton.adapter.inbound.graphql.advanced.sse.GraphQlSseHandlerFactory
dev.caskeleton.adapter.inbound.graphql.advanced.sse.GraphQlSseHeartbeat
dev.caskeleton.adapter.inbound.graphql.advanced.sse.GraphQlSseProperties
dev.caskeleton.adapter.inbound.graphql.advanced.sse.GraphQlSseRejectedException
dev.caskeleton.adapter.inbound.graphql.advanced.sse.GraphQlSseTermination
dev.caskeleton.adapter.inbound.graphql.advanced.subscription.GraphQlSlowConsumerPolicy
dev.caskeleton.adapter.inbound.graphql.advanced.subscription.GraphQlSubscriptionBufferPolicy
dev.caskeleton.adapter.inbound.graphql.advanced.subscription.GraphQlSubscriptionCancellation
dev.caskeleton.adapter.inbound.graphql.advanced.subscription.GraphQlSubscriptionContext
dev.caskeleton.adapter.inbound.graphql.advanced.subscription.GraphQlSubscriptionDispatcher
dev.caskeleton.adapter.inbound.graphql.advanced.subscription.GraphQlSubscriptionDrainCoordinator
dev.caskeleton.adapter.inbound.graphql.advanced.subscription.GraphQlSubscriptionDrainPhase
dev.caskeleton.adapter.inbound.graphql.advanced.subscription.GraphQlSubscriptionDrainingException
dev.caskeleton.adapter.inbound.graphql.advanced.subscription.GraphQlSubscriptionEvent
dev.caskeleton.adapter.inbound.graphql.advanced.subscription.GraphQlSubscriptionExecutionPolicy
dev.caskeleton.adapter.inbound.graphql.advanced.subscription.GraphQlSubscriptionLease
dev.caskeleton.adapter.inbound.graphql.advanced.subscription.GraphQlSubscriptionMetrics
dev.caskeleton.adapter.inbound.graphql.advanced.subscription.GraphQlSubscriptionOrderingProfile
dev.caskeleton.adapter.inbound.graphql.advanced.subscription.GraphQlSubscriptionSource
dev.caskeleton.adapter.inbound.graphql.advanced.subscription.GraphQlSubscriptionState
dev.caskeleton.adapter.inbound.graphql.advanced.subscription.GraphQlSubscriptionTermination
dev.caskeleton.adapter.inbound.graphql.api.GraphQlClientProfile
dev.caskeleton.adapter.inbound.graphql.api.GraphQlClientProfileName
dev.caskeleton.adapter.inbound.graphql.api.GraphQlOperationId
dev.caskeleton.adapter.inbound.graphql.api.GraphQlOperationName
dev.caskeleton.adapter.inbound.graphql.api.GraphQlSchemaCoordinate
dev.caskeleton.adapter.inbound.graphql.architecture.GraphQlAsyncReturnShape
dev.caskeleton.adapter.inbound.graphql.architecture.GraphQlControllerContractException
dev.caskeleton.adapter.inbound.graphql.architecture.GraphQlControllerInspector
dev.caskeleton.adapter.inbound.graphql.architecture.GraphQlControllerTransactionRule
dev.caskeleton.adapter.inbound.graphql.architecture.GraphQlInputTypePolicy
dev.caskeleton.adapter.inbound.graphql.architecture.GraphQlResolverBoundaryRules
dev.caskeleton.adapter.inbound.graphql.architecture.GraphQlReturnTypePolicy
dev.caskeleton.adapter.inbound.graphql.architecture.GraphQlTransportTypeRules
dev.caskeleton.adapter.inbound.graphql.architecture.GraphQlTypeGraph
dev.caskeleton.adapter.inbound.graphql.autoconfigure.GraphQlActivationEnvironmentPostProcessor
dev.caskeleton.adapter.inbound.graphql.autoconfigure.GraphQlDeploymentMode
dev.caskeleton.adapter.inbound.graphql.autoconfigure.GraphQlOffAutoConfigurationImportFilter
dev.caskeleton.adapter.inbound.graphql.autoconfigure.GraphQlPlatformActuatorEndpoint
dev.caskeleton.adapter.inbound.graphql.autoconfigure.GraphQlPlatformAutoConfiguration
dev.caskeleton.adapter.inbound.graphql.autoconfigure.GraphQlPlatformConfigurationException
dev.caskeleton.adapter.inbound.graphql.autoconfigure.GraphQlPlatformConfigurationReport
dev.caskeleton.adapter.inbound.graphql.autoconfigure.GraphQlPlatformRuntime
dev.caskeleton.adapter.inbound.graphql.autoconfigure.GraphQlPlatformSettings
dev.caskeleton.adapter.inbound.graphql.autoconfigure.GraphQlPlatformStartupValidator
dev.caskeleton.adapter.inbound.graphql.autoconfigure.GraphQlRetiredSafetyAxis
dev.caskeleton.adapter.inbound.graphql.autoconfigure.GraphQlRootAutoConfiguration
dev.caskeleton.adapter.inbound.graphql.autoconfigure.GraphQlRuntimeTransport
dev.caskeleton.adapter.inbound.graphql.compat.GraphQlChangeKind
dev.caskeleton.adapter.inbound.graphql.compat.GraphQlClientOwnerApproval
dev.caskeleton.adapter.inbound.graphql.compat.GraphQlCompatibilityImpact
dev.caskeleton.adapter.inbound.graphql.compat.GraphQlCompatibilityPolicy
dev.caskeleton.adapter.inbound.graphql.compat.GraphQlCompatibilityReport
dev.caskeleton.adapter.inbound.graphql.compat.GraphQlDeprecationGate
dev.caskeleton.adapter.inbound.graphql.compat.GraphQlRemovalDecision
dev.caskeleton.adapter.inbound.graphql.compat.GraphQlRemovalRequest
dev.caskeleton.adapter.inbound.graphql.compat.GraphQlSchemaChange
dev.caskeleton.adapter.inbound.graphql.compat.GraphQlSchemaComparator
dev.caskeleton.adapter.inbound.graphql.compat.GraphQlSchemaUsage
dev.caskeleton.adapter.inbound.graphql.context.ActorRef
dev.caskeleton.adapter.inbound.graphql.context.GraphQlCommandAttribution
dev.caskeleton.adapter.inbound.graphql.context.GraphQlDeadline
@@ -193,16 +34,7 @@ dev.caskeleton.adapter.inbound.graphql.cost.GraphQlDocumentComplexityScorer
dev.caskeleton.adapter.inbound.graphql.cost.GraphQlDocumentShape
dev.caskeleton.adapter.inbound.graphql.cost.GraphQlDocumentShapeAnalyzer
dev.caskeleton.adapter.inbound.graphql.cost.GraphQlFieldCostDescriptor
dev.caskeleton.adapter.inbound.graphql.cost.GraphQlParserLimitPolicy
dev.caskeleton.adapter.inbound.graphql.cost.GraphQlParserLimits
dev.caskeleton.adapter.inbound.graphql.cost.GraphQlParserOptionsFactory
dev.caskeleton.adapter.inbound.graphql.cost.GraphQlParserRejectedException
dev.caskeleton.adapter.inbound.graphql.cost.GraphQlResolverWeight
dev.caskeleton.adapter.inbound.graphql.cost.GraphQlResponseByteLimiter
dev.caskeleton.adapter.inbound.graphql.cost.GraphQlResponseNodeCounter
dev.caskeleton.adapter.inbound.graphql.cost.GraphQlRuntimeBudget
dev.caskeleton.adapter.inbound.graphql.cost.GraphQlRuntimeBudgetExceededException
dev.caskeleton.adapter.inbound.graphql.cost.GraphQlRuntimeBudgetTracker
dev.caskeleton.adapter.inbound.graphql.cost.GraphQlStructuralLimitException
dev.caskeleton.adapter.inbound.graphql.cost.GraphQlStructuralLimitPolicy
dev.caskeleton.adapter.inbound.graphql.cost.GraphQlStructuralLimits
@@ -227,33 +59,22 @@ dev.caskeleton.adapter.inbound.graphql.error.GraphQlErrorCategory
dev.caskeleton.adapter.inbound.graphql.error.GraphQlErrorCode
dev.caskeleton.adapter.inbound.graphql.error.GraphQlErrorContext
dev.caskeleton.adapter.inbound.graphql.error.GraphQlExceptionResolver
dev.caskeleton.adapter.inbound.graphql.error.GraphQlFailureBoundary
dev.caskeleton.adapter.inbound.graphql.error.GraphQlInternalErrorMasker
dev.caskeleton.adapter.inbound.graphql.error.GraphQlNullabilityContract
dev.caskeleton.adapter.inbound.graphql.error.GraphQlRequestErrorMapper
dev.caskeleton.adapter.inbound.graphql.error.GraphQlSubscriptionExceptionResolver
dev.caskeleton.adapter.inbound.graphql.error.GraphQlPlatformRejection
dev.caskeleton.adapter.inbound.graphql.error.GraphQlWireError
dev.caskeleton.adapter.inbound.graphql.error.GraphQlWireErrorMapper
dev.caskeleton.adapter.inbound.graphql.error.GraphQlWireErrors
dev.caskeleton.adapter.inbound.graphql.execution.BoundedPreparsedDocumentProvider
dev.caskeleton.adapter.inbound.graphql.execution.GraphQlAnonymousOperationException
dev.caskeleton.adapter.inbound.graphql.execution.GraphQlCancellation
dev.caskeleton.adapter.inbound.graphql.execution.GraphQlDeadlinePropagator
dev.caskeleton.adapter.inbound.graphql.execution.GraphQlExecutionPipeline
dev.caskeleton.adapter.inbound.graphql.execution.GraphQlExecutionPipelineException
dev.caskeleton.adapter.inbound.graphql.execution.GraphQlExecutionPipelineValidator
dev.caskeleton.adapter.inbound.graphql.execution.GraphQlExecutionProfile
dev.caskeleton.adapter.inbound.graphql.execution.GraphQlExecutionProfileException
dev.caskeleton.adapter.inbound.graphql.execution.GraphQlExecutionProfileValidator
dev.caskeleton.adapter.inbound.graphql.execution.GraphQlExecutionStage
dev.caskeleton.adapter.inbound.graphql.execution.GraphQlOperationNameInterceptor
dev.caskeleton.adapter.inbound.graphql.execution.GraphQlOperationNamePolicy
dev.caskeleton.adapter.inbound.graphql.execution.GraphQlOperationSelection
dev.caskeleton.adapter.inbound.graphql.execution.GraphQlPreparsedCacheKey
dev.caskeleton.adapter.inbound.graphql.execution.GraphQlPreparsedCacheMetrics
dev.caskeleton.adapter.inbound.graphql.execution.GraphQlPreparsedCachePolicy
dev.caskeleton.adapter.inbound.graphql.execution.GraphQlRequestCancelledException
dev.caskeleton.adapter.inbound.graphql.execution.GraphQlResolverBudget
dev.caskeleton.adapter.inbound.graphql.execution.GraphQlResolverCatalog
dev.caskeleton.adapter.inbound.graphql.execution.GraphQlResolverDescriptor
dev.caskeleton.adapter.inbound.graphql.execution.GraphQlTimeoutPolicy
dev.caskeleton.adapter.inbound.graphql.fetch.GraphQlFetchProfile
dev.caskeleton.adapter.inbound.graphql.fetch.GraphQlFetchProfileClassifier
@@ -265,41 +86,20 @@ dev.caskeleton.adapter.inbound.graphql.fetch.GraphQlSelectionCoordinate
dev.caskeleton.adapter.inbound.graphql.fetch.GraphQlSelectionSetView
dev.caskeleton.adapter.inbound.graphql.fetch.GraphQlSelectionSignature
dev.caskeleton.adapter.inbound.graphql.fetch.GraphQlUnmappedSelectionException
dev.caskeleton.adapter.inbound.graphql.http.GraphQlAcceptHeader
dev.caskeleton.adapter.inbound.graphql.http.GraphQlExecutionOutcome
dev.caskeleton.adapter.inbound.graphql.http.GraphQlExtensionsPolicy
dev.caskeleton.adapter.inbound.graphql.http.GraphQlHttpContractException
dev.caskeleton.adapter.inbound.graphql.http.GraphQlHttpExecutor
dev.caskeleton.adapter.inbound.graphql.http.GraphQlHttpOutcome
dev.caskeleton.adapter.inbound.graphql.http.GraphQlHttpProfile
dev.caskeleton.adapter.inbound.graphql.http.GraphQlHttpRequestEnvelope
dev.caskeleton.adapter.inbound.graphql.http.GraphQlHttpResponse
dev.caskeleton.adapter.inbound.graphql.http.GraphQlHttpResponseFactory
dev.caskeleton.adapter.inbound.graphql.http.GraphQlHttpResponsePolicy
dev.caskeleton.adapter.inbound.graphql.http.GraphQlHttpStatusMapper
dev.caskeleton.adapter.inbound.graphql.http.GraphQlJsonStructurePolicy
dev.caskeleton.adapter.inbound.graphql.http.GraphQlJsonValues
dev.caskeleton.adapter.inbound.graphql.http.GraphQlMediaTypes
dev.caskeleton.adapter.inbound.graphql.http.GraphQlRequestEnvelopeValidator
dev.caskeleton.adapter.inbound.graphql.http.GraphQlRequestFormatException
dev.caskeleton.adapter.inbound.graphql.http.GraphQlRequestSize
dev.caskeleton.adapter.inbound.graphql.http.GraphQlRequestTooLargeException
dev.caskeleton.adapter.inbound.graphql.moduleboundary.GraphQlAdvancedModule
dev.caskeleton.adapter.inbound.graphql.moduleboundary.GraphQlModuleBoundary
dev.caskeleton.adapter.inbound.graphql.moduleboundary.GraphQlModulePurity
dev.caskeleton.adapter.inbound.graphql.moduleboundary.GraphQlStableModule
dev.caskeleton.adapter.inbound.graphql.mutation.GraphQlBatchMutationItemResult
dev.caskeleton.adapter.inbound.graphql.mutation.GraphQlBusinessResult
dev.caskeleton.adapter.inbound.graphql.mutation.GraphQlCanonicalInput
dev.caskeleton.adapter.inbound.graphql.mutation.GraphQlExpectedVersion
dev.caskeleton.adapter.inbound.graphql.mutation.GraphQlIdempotencyConflictException
dev.caskeleton.adapter.inbound.graphql.mutation.GraphQlIdempotencyKey
dev.caskeleton.adapter.inbound.graphql.mutation.GraphQlMutationContractException
dev.caskeleton.adapter.inbound.graphql.mutation.GraphQlMutationContractValidator
dev.caskeleton.adapter.inbound.graphql.mutation.GraphQlMutationCoordinate
dev.caskeleton.adapter.inbound.graphql.mutation.GraphQlMutationFingerprint
dev.caskeleton.adapter.inbound.graphql.mutation.GraphQlMutationIdempotencyContext
dev.caskeleton.adapter.inbound.graphql.mutation.GraphQlMutationIdempotencyInterceptor
dev.caskeleton.adapter.inbound.graphql.mutation.GraphQlMutationPayload
dev.caskeleton.adapter.inbound.graphql.mutation.GraphQlMutationResultMapper
dev.caskeleton.adapter.inbound.graphql.observation.GraphQlDataLoaderObservationConvention
@@ -307,7 +107,6 @@ dev.caskeleton.adapter.inbound.graphql.observation.GraphQlMetricCardinalityPolic
dev.caskeleton.adapter.inbound.graphql.observation.GraphQlObservationContractException
dev.caskeleton.adapter.inbound.graphql.observation.GraphQlObservationNames
dev.caskeleton.adapter.inbound.graphql.observation.GraphQlOperationNameCardinality
dev.caskeleton.adapter.inbound.graphql.observation.GraphQlProfilerAccessPolicy
dev.caskeleton.adapter.inbound.graphql.observation.GraphQlRequestObservationConvention
dev.caskeleton.adapter.inbound.graphql.observation.GraphQlResolverObservationConvention
dev.caskeleton.adapter.inbound.graphql.observation.GraphQlSensitiveAttributeFilter
@@ -329,26 +128,8 @@ dev.caskeleton.adapter.inbound.graphql.pagination.GraphQlKeysetWindow
dev.caskeleton.adapter.inbound.graphql.pagination.GraphQlPageInfo
dev.caskeleton.adapter.inbound.graphql.pagination.HmacGraphQlCursorCodec
dev.caskeleton.adapter.inbound.graphql.policy.GraphQlClientPolicy
dev.caskeleton.adapter.inbound.graphql.policy.GraphQlClientPolicyManifest
dev.caskeleton.adapter.inbound.graphql.policy.GraphQlOperationCatalog
dev.caskeleton.adapter.inbound.graphql.policy.GraphQlOperationPolicy
dev.caskeleton.adapter.inbound.graphql.policy.GraphQlOperationType
dev.caskeleton.adapter.inbound.graphql.policy.GraphQlPolicyViolation
dev.caskeleton.adapter.inbound.graphql.policy.GraphQlUnknownClientProfileException
dev.caskeleton.adapter.inbound.graphql.policy.GraphQlUnknownOperationException
dev.caskeleton.adapter.inbound.graphql.policy.ResolverExecutionType
dev.caskeleton.adapter.inbound.graphql.release.GraphQlCompatibilityMatrix
dev.caskeleton.adapter.inbound.graphql.release.GraphQlFaultScenario
dev.caskeleton.adapter.inbound.graphql.release.GraphQlPerformanceScenario
dev.caskeleton.adapter.inbound.graphql.release.GraphQlReleaseEvidence
dev.caskeleton.adapter.inbound.graphql.release.GraphQlReleaseException
dev.caskeleton.adapter.inbound.graphql.release.GraphQlReleaseGate
dev.caskeleton.adapter.inbound.graphql.release.GraphQlReleaseOverride
dev.caskeleton.adapter.inbound.graphql.release.GraphQlReleaseReportWriter
dev.caskeleton.adapter.inbound.graphql.release.GraphQlStableCapabilityManifest
dev.caskeleton.adapter.inbound.graphql.runtime.GraphQlBatchLoaderRegistrar
dev.caskeleton.adapter.inbound.graphql.runtime.GraphQlBlockingBridge
dev.caskeleton.adapter.inbound.graphql.runtime.GraphQlBlockingBridgeFullException
dev.caskeleton.adapter.inbound.graphql.runtime.GraphQlCostBudgetHandler
dev.caskeleton.adapter.inbound.graphql.runtime.GraphQlDataFetcherExceptionResolver
dev.caskeleton.adapter.inbound.graphql.runtime.GraphQlDocumentAuthorizationHandler
@@ -358,13 +139,10 @@ dev.caskeleton.adapter.inbound.graphql.runtime.GraphQlExecutionHandler
dev.caskeleton.adapter.inbound.graphql.runtime.GraphQlExecutionRequest
dev.caskeleton.adapter.inbound.graphql.runtime.GraphQlOperationSelectionHandler
dev.caskeleton.adapter.inbound.graphql.runtime.GraphQlPlatformInstrumentation
dev.caskeleton.adapter.inbound.graphql.runtime.GraphQlPlatformRejectionMapper
dev.caskeleton.adapter.inbound.graphql.runtime.GraphQlPlatformWebInterceptor
dev.caskeleton.adapter.inbound.graphql.runtime.GraphQlPreparsedDocumentAdapter
dev.caskeleton.adapter.inbound.graphql.runtime.GraphQlPrincipalResolver
dev.caskeleton.adapter.inbound.graphql.runtime.GraphQlRequestObservationConventionAdapter
dev.caskeleton.adapter.inbound.graphql.runtime.GraphQlWireErrorMapper
dev.caskeleton.adapter.inbound.graphql.runtime.GraphQlWireErrors
dev.caskeleton.adapter.inbound.graphql.runtime.servlet.GraphQlRequestBodyLimitFilter
dev.caskeleton.adapter.inbound.graphql.scalar.BigDecimalScalar
dev.caskeleton.adapter.inbound.graphql.scalar.DateScalar
@@ -373,25 +151,9 @@ dev.caskeleton.adapter.inbound.graphql.scalar.GraphQlScalarWiringConfigurer
dev.caskeleton.adapter.inbound.graphql.scalar.InstantScalar
dev.caskeleton.adapter.inbound.graphql.scalar.LongScalar
dev.caskeleton.adapter.inbound.graphql.scalar.UuidScalar
dev.caskeleton.adapter.inbound.graphql.schema.GraphQlContractVersion
dev.caskeleton.adapter.inbound.graphql.schema.GraphQlMappingInspectionGate
dev.caskeleton.adapter.inbound.graphql.schema.GraphQlMappingIssue
dev.caskeleton.adapter.inbound.graphql.schema.GraphQlMappingPolicy
dev.caskeleton.adapter.inbound.graphql.schema.GraphQlOneOfInputValidator
dev.caskeleton.adapter.inbound.graphql.schema.GraphQlOneOfPolicy
dev.caskeleton.adapter.inbound.graphql.schema.GraphQlOneOfSchemaGate
dev.caskeleton.adapter.inbound.graphql.schema.GraphQlOneOfViolationException
dev.caskeleton.adapter.inbound.graphql.schema.GraphQlScalarDefinition
dev.caskeleton.adapter.inbound.graphql.schema.GraphQlScalarManifest
dev.caskeleton.adapter.inbound.graphql.schema.GraphQlScalarPolicy
dev.caskeleton.adapter.inbound.graphql.schema.GraphQlSchemaAssembler
dev.caskeleton.adapter.inbound.graphql.schema.GraphQlSchemaAssemblyException
dev.caskeleton.adapter.inbound.graphql.schema.GraphQlSchemaAssemblyResult
dev.caskeleton.adapter.inbound.graphql.schema.GraphQlSchemaContract
dev.caskeleton.adapter.inbound.graphql.schema.GraphQlSchemaHash
dev.caskeleton.adapter.inbound.graphql.schema.GraphQlSchemaMappingException
dev.caskeleton.adapter.inbound.graphql.schema.GraphQlSchemaOwnership
dev.caskeleton.adapter.inbound.graphql.schema.GraphQlSchemaResource
dev.caskeleton.adapter.inbound.graphql.security.ApplicationObjectAuthorization
dev.caskeleton.adapter.inbound.graphql.security.GraphQlAuthenticatedPrincipal
dev.caskeleton.adapter.inbound.graphql.security.GraphQlAuthenticationContextFactory
@@ -401,8 +163,6 @@ dev.caskeleton.adapter.inbound.graphql.security.GraphQlAuthorizationDeniedExcept
dev.caskeleton.adapter.inbound.graphql.security.GraphQlAuthorizationInterceptor
dev.caskeleton.adapter.inbound.graphql.security.GraphQlAuthorizationPolicy
dev.caskeleton.adapter.inbound.graphql.security.GraphQlBatchContext
dev.caskeleton.adapter.inbound.graphql.security.GraphQlClientProfileResolver
dev.caskeleton.adapter.inbound.graphql.security.GraphQlContextCleanup
dev.caskeleton.adapter.inbound.graphql.security.GraphQlContextPropagator
dev.caskeleton.adapter.inbound.graphql.security.GraphQlObjectAuthorizationPort
dev.caskeleton.adapter.inbound.graphql.security.GraphQlTenantIsolationException
@@ -1,6 +1,8 @@
# Supported production adopter surface for the JPA persistence leaf.
# Language-level public implementation types are not compatibility promises.
# Adding an import outside this list requires an explicit review of the adopter contract.
# Checked by verifyJpaApiSurface (ca.api-surface adopterBaseline); every entry must be in
# jpa-api-surface.txt. persistence-fileserver types are that leaf's own surface, not listed here.
dev.caskeleton.adapter.outbound.persistence.api.capability.CapabilitySupport
dev.caskeleton.adapter.outbound.persistence.api.capability.JpaCapability
dev.caskeleton.adapter.outbound.persistence.audit.AuditContextPort
@@ -8,16 +10,11 @@ dev.caskeleton.adapter.outbound.persistence.audit.AuditableEntity
dev.caskeleton.adapter.outbound.persistence.config.PersistenceJpaConfig
dev.caskeleton.adapter.outbound.persistence.config.PersistenceVendorSettings
dev.caskeleton.adapter.outbound.persistence.failure.SqlStateErrorMapping
dev.caskeleton.adapter.outbound.persistence.fileserver.FileserverSchemaActivation
dev.caskeleton.adapter.outbound.persistence.hibernate.HibernateProviderPolicy
dev.caskeleton.adapter.outbound.persistence.idempotency.IdempotencyClaimRepository
dev.caskeleton.adapter.outbound.persistence.migration.FlywaySchemaPolicy
dev.caskeleton.adapter.outbound.persistence.outbox.OutboxClaimRepository
dev.caskeleton.adapter.outbound.persistence.postgresql.PostgreSqlIdempotencyClaimRepository
dev.caskeleton.adapter.outbound.persistence.postgresql.PostgreSqlLocalTimeoutConfigurer
dev.caskeleton.adapter.outbound.persistence.postgresql.PostgreSqlOutboxClaimRepository
dev.caskeleton.adapter.outbound.persistence.outbox.jpa.OutboxClaimRepository
dev.caskeleton.adapter.outbound.persistence.outbox.postgresql.PostgreSqlOutboxClaimRepository
dev.caskeleton.adapter.outbound.persistence.postgresql.PostgreSqlPersistenceConfig
dev.caskeleton.adapter.outbound.persistence.postgresql.PostgreSqlSqlStateErrorMapping
dev.caskeleton.adapter.outbound.persistence.security.DatabasePrivilegeReport
dev.caskeleton.adapter.outbound.persistence.security.PostgreSqlRuntimeRoleVerifier
dev.caskeleton.adapter.outbound.persistence.transaction.TransactionLocalTimeoutConfigurer
+19 -164
View File
@@ -5,7 +5,7 @@
# root yet.
# Update only after review with:
# ./gradlew :adapter:outbound:persistence-jpa:updateJpaApiSurface -PapproveJpaApiSurfaceChange
# types: 311
# types: 166
dev.caskeleton.adapter.outbound.persistence.api.PersistenceOperationName
dev.caskeleton.adapter.outbound.persistence.api.capability.CapabilitySupport
dev.caskeleton.adapter.outbound.persistence.api.capability.JpaCapability
@@ -28,12 +28,9 @@ dev.caskeleton.adapter.outbound.persistence.api.error.QueryTimeoutException
dev.caskeleton.adapter.outbound.persistence.api.error.SchemaMismatchException
dev.caskeleton.adapter.outbound.persistence.api.error.SerializationFailureException
dev.caskeleton.adapter.outbound.persistence.api.error.SqlExceptionSqlStateResolver
dev.caskeleton.adapter.outbound.persistence.api.error.SqlStateResolver
dev.caskeleton.adapter.outbound.persistence.api.error.TransactionCompletionUnknownException
dev.caskeleton.adapter.outbound.persistence.api.error.TransactionTimeoutException
dev.caskeleton.adapter.outbound.persistence.api.error.UniqueConstraintViolationException
dev.caskeleton.adapter.outbound.persistence.api.error.VendorFailureTranslator
dev.caskeleton.adapter.outbound.persistence.api.query.CursorCodec
dev.caskeleton.adapter.outbound.persistence.api.query.CursorPayloadCodec
dev.caskeleton.adapter.outbound.persistence.api.query.KeysetPageRequest
dev.caskeleton.adapter.outbound.persistence.api.query.KeysetSlice
@@ -43,46 +40,25 @@ dev.caskeleton.adapter.outbound.persistence.api.query.QueryObservation
dev.caskeleton.adapter.outbound.persistence.api.query.QueryScope
dev.caskeleton.adapter.outbound.persistence.api.query.SignedJsonCursorCodec
dev.caskeleton.adapter.outbound.persistence.api.query.SortDirection
dev.caskeleton.adapter.outbound.persistence.api.transaction.IsolationLevel
dev.caskeleton.adapter.outbound.persistence.api.transaction.JitterMode
dev.caskeleton.adapter.outbound.persistence.api.transaction.JpaRetryPolicy
dev.caskeleton.adapter.outbound.persistence.api.transaction.JpaTransactionExecutor
dev.caskeleton.adapter.outbound.persistence.api.transaction.PropagationMode
dev.caskeleton.adapter.outbound.persistence.api.transaction.RetryDecision
dev.caskeleton.adapter.outbound.persistence.api.transaction.RetryDisposition
dev.caskeleton.adapter.outbound.persistence.api.transaction.RetryEventListener
dev.caskeleton.adapter.outbound.persistence.api.transaction.RetryProfile
dev.caskeleton.adapter.outbound.persistence.api.transaction.TransactionAttempt
dev.caskeleton.adapter.outbound.persistence.api.transaction.TransactionCompletionEvidence
dev.caskeleton.adapter.outbound.persistence.api.transaction.TransactionProfile
dev.caskeleton.adapter.outbound.persistence.audit.AuditContextPort
dev.caskeleton.adapter.outbound.persistence.audit.AuditableEntity
dev.caskeleton.adapter.outbound.persistence.audit.DomainContextAuditContextPort
dev.caskeleton.adapter.outbound.persistence.audit.DomainContextAuditContext
dev.caskeleton.adapter.outbound.persistence.cache.CacheConcurrencyStrategy
dev.caskeleton.adapter.outbound.persistence.cache.CacheRegionCatalog
dev.caskeleton.adapter.outbound.persistence.cache.HibernateCacheGuard
dev.caskeleton.adapter.outbound.persistence.cache.HibernateCachePolicy
dev.caskeleton.adapter.outbound.persistence.cache.HibernateCacheSettings
dev.caskeleton.adapter.outbound.persistence.config.JpaAdapterComponentsConfig
dev.caskeleton.adapter.outbound.persistence.config.PersistenceJpaConfig
dev.caskeleton.adapter.outbound.persistence.config.PersistenceVendorSettings
dev.caskeleton.adapter.outbound.persistence.envers.EntityRevision
dev.caskeleton.adapter.outbound.persistence.envers.EnversConfigurationGuard
dev.caskeleton.adapter.outbound.persistence.envers.EnversHistoryPolicy
dev.caskeleton.adapter.outbound.persistence.envers.EnversHistoryReader
dev.caskeleton.adapter.outbound.persistence.envers.EnversRevisionMetadata
dev.caskeleton.adapter.outbound.persistence.envers.HibernateEnversHistoryReader
dev.caskeleton.adapter.outbound.persistence.experimental.ExperimentalFeature
dev.caskeleton.adapter.outbound.persistence.experimental.ExperimentalFeatureGate
dev.caskeleton.adapter.outbound.persistence.experimental.database.TenantDataSourceLifecycle
dev.caskeleton.adapter.outbound.persistence.experimental.database.TenantDataSourceRegistry
dev.caskeleton.adapter.outbound.persistence.experimental.database.TenantEntityManagerFactoryRegistry
dev.caskeleton.adapter.outbound.persistence.experimental.database.TenantPoolBudget
dev.caskeleton.adapter.outbound.persistence.experimental.next.CompatibilityLane
dev.caskeleton.adapter.outbound.persistence.experimental.next.ExperimentalPromotionGate
dev.caskeleton.adapter.outbound.persistence.experimental.next.HibernateCompatibilityPolicy
dev.caskeleton.adapter.outbound.persistence.experimental.next.PromotionDecision
dev.caskeleton.adapter.outbound.persistence.experimental.next.PromotionEvidence
dev.caskeleton.adapter.outbound.persistence.experimental.replica.ConsistencyAwareDataSourceRouter
dev.caskeleton.adapter.outbound.persistence.experimental.replica.ConsistencyToken
dev.caskeleton.adapter.outbound.persistence.experimental.replica.ReadConsistency
@@ -90,7 +66,6 @@ dev.caskeleton.adapter.outbound.persistence.experimental.replica.ReplicaLagMonit
dev.caskeleton.adapter.outbound.persistence.experimental.replica.ReplicaRoutingDecision
dev.caskeleton.adapter.outbound.persistence.experimental.replica.ReplicaTarget
dev.caskeleton.adapter.outbound.persistence.experimental.replica.TransactionContext
dev.caskeleton.adapter.outbound.persistence.experimental.rls.RlsAdminBypassToken
dev.caskeleton.adapter.outbound.persistence.experimental.rls.RlsPolicyVerifier
dev.caskeleton.adapter.outbound.persistence.experimental.rls.RlsTenantSessionBinder
dev.caskeleton.adapter.outbound.persistence.experimental.schema.SchemaMultiTenantConnectionProvider
@@ -99,14 +74,10 @@ dev.caskeleton.adapter.outbound.persistence.experimental.schema.SchemaTenantRegi
dev.caskeleton.adapter.outbound.persistence.experimental.schema.TenantMigrationStatus
dev.caskeleton.adapter.outbound.persistence.experimental.tenant.TenantAwareRepositoryGuard
dev.caskeleton.adapter.outbound.persistence.experimental.tenant.TenantContext
dev.caskeleton.adapter.outbound.persistence.experimental.tenant.TenantEntityListenerGuard
dev.caskeleton.adapter.outbound.persistence.experimental.tenant.TenantId
dev.caskeleton.adapter.outbound.persistence.failure.PersistenceExceptionTranslator
dev.caskeleton.adapter.outbound.persistence.failure.SqlStateErrorMapping
dev.caskeleton.adapter.outbound.persistence.failure.StandardSqlStateErrorMapping
dev.caskeleton.adapter.outbound.persistence.h2.H2IdempotencyClaimRepository
dev.caskeleton.adapter.outbound.persistence.h2.H2LocalTimeoutConfigurer
dev.caskeleton.adapter.outbound.persistence.h2.H2OutboxClaimRepository
dev.caskeleton.adapter.outbound.persistence.h2.H2PersistenceConfig
dev.caskeleton.adapter.outbound.persistence.h2.H2SqlStateErrorMapping
dev.caskeleton.adapter.outbound.persistence.hibernate.HibernateProviderPolicy
@@ -118,110 +89,42 @@ dev.caskeleton.adapter.outbound.persistence.hibernate.QueryNameContext
dev.caskeleton.adapter.outbound.persistence.hibernate.batch.BatchExecutionResult
dev.caskeleton.adapter.outbound.persistence.hibernate.batch.HibernateBatchConfigurationGuard
dev.caskeleton.adapter.outbound.persistence.hibernate.batch.HibernateJpaBatchExecutor
dev.caskeleton.adapter.outbound.persistence.hibernate.batch.JpaBatchExecutor
dev.caskeleton.adapter.outbound.persistence.hibernate.batch.JpaBatchProfile
dev.caskeleton.adapter.outbound.persistence.hibernate.batch.JpaBatchProfileRegistry
dev.caskeleton.adapter.outbound.persistence.hibernate.bulk.AffectedRowsExpectation
dev.caskeleton.adapter.outbound.persistence.hibernate.bulk.BulkDmlExecutor
dev.caskeleton.adapter.outbound.persistence.hibernate.bulk.BulkDmlResult
dev.caskeleton.adapter.outbound.persistence.hibernate.bulk.BulkOperationName
dev.caskeleton.adapter.outbound.persistence.hibernate.bulk.HibernateBulkDmlExecutor
dev.caskeleton.adapter.outbound.persistence.hibernate.stateless.HibernateStatelessSessionRunner
dev.caskeleton.adapter.outbound.persistence.hibernate.stateless.StatelessRowCapExceededException
dev.caskeleton.adapter.outbound.persistence.hibernate.stateless.StatelessSessionRunner
dev.caskeleton.adapter.outbound.persistence.hibernate.stateless.StatelessWorkName
dev.caskeleton.adapter.outbound.persistence.hibernate.stateless.StatelessWorkResult
dev.caskeleton.adapter.outbound.persistence.idempotency.IdempotencyClaimRepository
dev.caskeleton.adapter.outbound.persistence.idempotency.IdempotencyReaper
dev.caskeleton.adapter.outbound.persistence.idempotency.IdempotencyRecordJpaRepository
dev.caskeleton.adapter.outbound.persistence.idempotency.IdempotencyResponseObjectStore
dev.caskeleton.adapter.outbound.persistence.idempotency.IdempotencyStoreAdapter
dev.caskeleton.adapter.outbound.persistence.idempotency.entity.IdempotencyRecordEntity
dev.caskeleton.adapter.outbound.persistence.idempotency.mapper.IdempotencyRecordEntityMapper
dev.caskeleton.adapter.outbound.persistence.liveevent.JpaLiveEventReplayAdapter
dev.caskeleton.adapter.outbound.persistence.idempotency.jpa.IdempotencyReaper
dev.caskeleton.adapter.outbound.persistence.idempotency.jpa.IdempotencyRecordJpaRepository
dev.caskeleton.adapter.outbound.persistence.idempotency.jpa.entity.IdempotencyRecordEntity
dev.caskeleton.adapter.outbound.persistence.idempotency.postgresql.IdempotencySchemaStream
dev.caskeleton.adapter.outbound.persistence.idempotency.postgresql.PostgreSqlIdempotencyStore
dev.caskeleton.adapter.outbound.persistence.liveevent.JpaLiveEventReplay
dev.caskeleton.adapter.outbound.persistence.liveevent.LiveEventJpaRepository
dev.caskeleton.adapter.outbound.persistence.liveevent.entity.LiveEventEntity
dev.caskeleton.adapter.outbound.persistence.lock.DistributedLockPersistenceConfig
dev.caskeleton.adapter.outbound.persistence.lock.LockRegistryDistributedLockAdapter
dev.caskeleton.adapter.outbound.persistence.lock.LockRegistryDistributedLock
dev.caskeleton.adapter.outbound.persistence.lock.LockSettings
dev.caskeleton.adapter.outbound.persistence.migration.ConcurrentIndexMigrationInspector
dev.caskeleton.adapter.outbound.persistence.migration.FailedConcurrentIndexRecovery
dev.caskeleton.adapter.outbound.persistence.migration.FlywaySchemaPolicy
dev.caskeleton.adapter.outbound.persistence.migration.FlywayValidationGate
dev.caskeleton.adapter.outbound.persistence.migration.MigrationResource
dev.caskeleton.adapter.outbound.persistence.migration.NonTransactionalMigrationPolicy
dev.caskeleton.adapter.outbound.persistence.migration.SchemaManagementMode
dev.caskeleton.adapter.outbound.persistence.migration.SchemaVersionSnapshot
dev.caskeleton.adapter.outbound.persistence.notification.NotificationJpaPersistenceConfig
dev.caskeleton.adapter.outbound.persistence.notification.NotificationSchemaActivation
dev.caskeleton.adapter.outbound.persistence.notification.NotificationSchemaStream
dev.caskeleton.adapter.outbound.persistence.notification.configuration.NotificationJpaPersistenceFacade
dev.caskeleton.adapter.outbound.persistence.notification.crypto.DirectAeadNotificationPayloadCrypto
dev.caskeleton.adapter.outbound.persistence.notification.crypto.NotificationCiphertext
dev.caskeleton.adapter.outbound.persistence.notification.crypto.NotificationCryptoException
dev.caskeleton.adapter.outbound.persistence.notification.crypto.NotificationHmacDigester
dev.caskeleton.adapter.outbound.persistence.notification.crypto.NotificationKeyMaterialHandle
dev.caskeleton.adapter.outbound.persistence.notification.crypto.NotificationKeyMaterialProvider
dev.caskeleton.adapter.outbound.persistence.notification.platform.AdminAuditEntity
dev.caskeleton.adapter.outbound.persistence.notification.platform.AdminAuditJpaRepository
dev.caskeleton.adapter.outbound.persistence.notification.platform.ConsentEntity
dev.caskeleton.adapter.outbound.persistence.notification.platform.ConsentJpaRepository
dev.caskeleton.adapter.outbound.persistence.notification.platform.ContactPointEntity
dev.caskeleton.adapter.outbound.persistence.notification.platform.ContactPointJpaRepository
dev.caskeleton.adapter.outbound.persistence.notification.platform.DeduplicationClaimEntity
dev.caskeleton.adapter.outbound.persistence.notification.platform.DeduplicationClaimJpaRepository
dev.caskeleton.adapter.outbound.persistence.notification.platform.DeliveryAttemptEntity
dev.caskeleton.adapter.outbound.persistence.notification.platform.DeliveryAttemptJpaRepository
dev.caskeleton.adapter.outbound.persistence.notification.platform.JdbcNotificationServingState
dev.caskeleton.adapter.outbound.persistence.notification.platform.JdbcReconciliationJobStore
dev.caskeleton.adapter.outbound.persistence.notification.platform.JpaAdminOperationStore
dev.caskeleton.adapter.outbound.persistence.notification.platform.JpaContactPointStore
dev.caskeleton.adapter.outbound.persistence.notification.platform.JpaDeliveryAttemptStore
dev.caskeleton.adapter.outbound.persistence.notification.platform.JpaNotificationRequestStore
dev.caskeleton.adapter.outbound.persistence.notification.platform.JpaNotificationSideEffectStore
dev.caskeleton.adapter.outbound.persistence.notification.platform.JpaPolicyStores
dev.caskeleton.adapter.outbound.persistence.notification.platform.JpaProviderEventLedger
dev.caskeleton.adapter.outbound.persistence.notification.platform.JpaRecipientDeliveryStore
dev.caskeleton.adapter.outbound.persistence.notification.platform.JpaRecipientLeaseStore
dev.caskeleton.adapter.outbound.persistence.notification.platform.JpaSuppressionStore
dev.caskeleton.adapter.outbound.persistence.notification.platform.JpaTemplateRegistry
dev.caskeleton.adapter.outbound.persistence.notification.platform.NotificationRecordMapper
dev.caskeleton.adapter.outbound.persistence.notification.platform.NotificationRequestEntity
dev.caskeleton.adapter.outbound.persistence.notification.platform.NotificationRequestJpaRepository
dev.caskeleton.adapter.outbound.persistence.notification.platform.PreferenceEntity
dev.caskeleton.adapter.outbound.persistence.notification.platform.PreferenceJpaRepository
dev.caskeleton.adapter.outbound.persistence.notification.platform.ProviderEventEntity
dev.caskeleton.adapter.outbound.persistence.notification.platform.ProviderEventJpaRepository
dev.caskeleton.adapter.outbound.persistence.notification.platform.RecipientClaimSql
dev.caskeleton.adapter.outbound.persistence.notification.platform.RecipientDeliveryEntity
dev.caskeleton.adapter.outbound.persistence.notification.platform.RecipientDeliveryJpaRepository
dev.caskeleton.adapter.outbound.persistence.notification.platform.SuppressionEntity
dev.caskeleton.adapter.outbound.persistence.notification.platform.SuppressionJpaRepository
dev.caskeleton.adapter.outbound.persistence.notification.platform.TemplateVersionEntity
dev.caskeleton.adapter.outbound.persistence.notification.platform.TemplateVersionJpaRepository
dev.caskeleton.adapter.outbound.persistence.notification.platform.TenantBoundRepositoryGuard
dev.caskeleton.adapter.outbound.persistence.notification.platform.inbox.InboxCommitEventPublisher
dev.caskeleton.adapter.outbound.persistence.notification.platform.inbox.InboxItemEntity
dev.caskeleton.adapter.outbound.persistence.notification.platform.inbox.InboxItemJpaRepository
dev.caskeleton.adapter.outbound.persistence.notification.platform.inbox.InboxOutboxRecordFactory
dev.caskeleton.adapter.outbound.persistence.notification.platform.inbox.JpaNotificationInbox
dev.caskeleton.adapter.outbound.persistence.observation.JpaMetricTags
dev.caskeleton.adapter.outbound.persistence.observation.JpaRetryObservation
dev.caskeleton.adapter.outbound.persistence.observation.JpaTransactionObservation
dev.caskeleton.adapter.outbound.persistence.observation.LowCardinality
dev.caskeleton.adapter.outbound.persistence.observation.MicrometerQueryObservation
dev.caskeleton.adapter.outbound.persistence.observation.SqlDiagnosticRedactor
dev.caskeleton.adapter.outbound.persistence.operation.DurableOperationJpaRepository
dev.caskeleton.adapter.outbound.persistence.operation.DurableOperationStoreAdapter
dev.caskeleton.adapter.outbound.persistence.operation.JpaDurableOperationStore
dev.caskeleton.adapter.outbound.persistence.operation.entity.DurableOperationEntity
dev.caskeleton.adapter.outbound.persistence.outbox.OutboxClaimRepository
dev.caskeleton.adapter.outbound.persistence.outbox.OutboxEventJpaRepository
dev.caskeleton.adapter.outbound.persistence.outbox.OutboxReaper
dev.caskeleton.adapter.outbound.persistence.outbox.OutboxStoreAdapter
dev.caskeleton.adapter.outbound.persistence.outbox.entity.OutboxEventEntity
dev.caskeleton.adapter.outbound.persistence.postgresql.PostgreSqlIdempotencyClaimRepository
dev.caskeleton.adapter.outbound.persistence.postgresql.PostgreSqlLocalTimeoutConfigurer
dev.caskeleton.adapter.outbound.persistence.postgresql.PostgreSqlOutboxClaimRepository
dev.caskeleton.adapter.outbound.persistence.outbox.h2.H2OutboxClaimRepository
dev.caskeleton.adapter.outbound.persistence.outbox.jpa.JpaOutboxStore
dev.caskeleton.adapter.outbound.persistence.outbox.jpa.OutboxClaimRepository
dev.caskeleton.adapter.outbound.persistence.outbox.jpa.OutboxEventJpaRepository
dev.caskeleton.adapter.outbound.persistence.outbox.jpa.OutboxReaper
dev.caskeleton.adapter.outbound.persistence.outbox.jpa.entity.OutboxEventEntity
dev.caskeleton.adapter.outbound.persistence.outbox.postgresql.PostgreSqlOutboxClaimRepository
dev.caskeleton.adapter.outbound.persistence.postgresql.PostgreSqlPersistenceConfig
dev.caskeleton.adapter.outbound.persistence.postgresql.PostgreSqlSqlStateErrorMapping
dev.caskeleton.adapter.outbound.persistence.postgresql.array.PostgreSqlArraySupport
@@ -233,56 +136,32 @@ dev.caskeleton.adapter.outbound.persistence.postgresql.copy.CopyFormat
dev.caskeleton.adapter.outbound.persistence.postgresql.copy.CopyLimits
dev.caskeleton.adapter.outbound.persistence.postgresql.copy.CopyOperationName
dev.caskeleton.adapter.outbound.persistence.postgresql.copy.CopyResult
dev.caskeleton.adapter.outbound.persistence.postgresql.copy.PostgreSqlCopyLoader
dev.caskeleton.adapter.outbound.persistence.postgresql.copy.RegisteredCopyStatement
dev.caskeleton.adapter.outbound.persistence.postgresql.copy.RegisteredPostgreSqlCopyLoader
dev.caskeleton.adapter.outbound.persistence.postgresql.error.ConstraintCatalog
dev.caskeleton.adapter.outbound.persistence.postgresql.error.PostgreSqlExceptionTranslator
dev.caskeleton.adapter.outbound.persistence.postgresql.error.PostgreSqlFailureClassifier
dev.caskeleton.adapter.outbound.persistence.postgresql.error.PostgreSqlServerErrorFields
dev.caskeleton.adapter.outbound.persistence.postgresql.error.PostgreSqlState
dev.caskeleton.adapter.outbound.persistence.postgresql.idempotency.PostgreSqlOwnerSafeIdempotencyStore
dev.caskeleton.adapter.outbound.persistence.postgresql.inbox.PostgreSqlSameStoreInboxAdapter
dev.caskeleton.adapter.outbound.persistence.postgresql.json.JsonDocument
dev.caskeleton.adapter.outbound.persistence.postgresql.json.JsonDocumentCodec
dev.caskeleton.adapter.outbound.persistence.postgresql.json.JsonPathName
dev.caskeleton.adapter.outbound.persistence.postgresql.json.PostgreSqlJsonQuerySupport
dev.caskeleton.adapter.outbound.persistence.postgresql.lock.LockWaitObservation
dev.caskeleton.adapter.outbound.persistence.postgresql.lock.PostgreSqlLockExceptionTranslator
dev.caskeleton.adapter.outbound.persistence.postgresql.lock.PostgreSqlLockOptions
dev.caskeleton.adapter.outbound.persistence.postgresql.lock.PostgreSqlWorkClaimExecutor
dev.caskeleton.adapter.outbound.persistence.postgresql.lock.WorkClaim
dev.caskeleton.adapter.outbound.persistence.postgresql.lock.WorkClaimExecutor
dev.caskeleton.adapter.outbound.persistence.postgresql.lock.WorkQueueDefinition
dev.caskeleton.adapter.outbound.persistence.postgresql.lock.WorkQueueName
dev.caskeleton.adapter.outbound.persistence.postgresql.outbox.PostgreSqlImmutableOutboxAppendAdapter
dev.caskeleton.adapter.outbound.persistence.postgresql.outbox.PostgreSqlPollingDeliveryAdapter
dev.caskeleton.adapter.outbound.persistence.postgresql.range.PgRange
dev.caskeleton.adapter.outbound.persistence.postgresql.range.PgRangeCodec
dev.caskeleton.adapter.outbound.persistence.postgresql.range.PgRangeJdbcType
dev.caskeleton.adapter.outbound.persistence.postgresql.range.PostgreSqlRangeQuerySupport
dev.caskeleton.adapter.outbound.persistence.postgresql.write.NativeWriteName
dev.caskeleton.adapter.outbound.persistence.postgresql.write.PostgreSqlUpsertExecutor
dev.caskeleton.adapter.outbound.persistence.postgresql.write.RegisteredPostgreSqlUpsertExecutor
dev.caskeleton.adapter.outbound.persistence.postgresql.write.RegisteredUpsertStatement
dev.caskeleton.adapter.outbound.persistence.postgresql.write.UpsertConflictTarget
dev.caskeleton.adapter.outbound.persistence.postgresql.write.UpsertResult
dev.caskeleton.adapter.outbound.persistence.postgresql.write.WriteDisposition
dev.caskeleton.adapter.outbound.persistence.querydsl.PredicatePolicy
dev.caskeleton.adapter.outbound.persistence.querydsl.QueryPage
dev.caskeleton.adapter.outbound.persistence.querydsl.QuerydslJpaSupport
dev.caskeleton.adapter.outbound.persistence.security.DatabasePrivilegeReport
dev.caskeleton.adapter.outbound.persistence.security.DatabaseRolePolicy
dev.caskeleton.adapter.outbound.persistence.security.PostgreSqlRuntimeRoleVerifier
dev.caskeleton.adapter.outbound.persistence.security.SearchPathPolicy
dev.caskeleton.adapter.outbound.persistence.springdata.EntityGraphCatalog
dev.caskeleton.adapter.outbound.persistence.springdata.EntityManagerAccess
dev.caskeleton.adapter.outbound.persistence.springdata.FetchPlanApplier
dev.caskeleton.adapter.outbound.persistence.springdata.FetchPlanName
dev.caskeleton.adapter.outbound.persistence.springdata.JpaKeysetQuerySupport
dev.caskeleton.adapter.outbound.persistence.springdata.JpaRepositoryFragmentSupport
dev.caskeleton.adapter.outbound.persistence.springdata.JpaStreamExecutor
dev.caskeleton.adapter.outbound.persistence.springdata.JpaStreamScope
dev.caskeleton.adapter.outbound.persistence.springdata.KeysetPredicateBuilder
dev.caskeleton.adapter.outbound.persistence.springdata.KeysetSliceAssembler
dev.caskeleton.adapter.outbound.persistence.springdata.KeysetTerm
@@ -291,29 +170,5 @@ dev.caskeleton.adapter.outbound.persistence.springdata.SafeSortField
dev.caskeleton.adapter.outbound.persistence.springdata.SafeSortMapper
dev.caskeleton.adapter.outbound.persistence.springdata.SafeSortRegistry
dev.caskeleton.adapter.outbound.persistence.springdata.ScrollPolicy
dev.caskeleton.adapter.outbound.persistence.springdata.SpecificationPolicy
dev.caskeleton.adapter.outbound.persistence.transaction.BackoffCalculator
dev.caskeleton.adapter.outbound.persistence.transaction.CommitFailureClassifier
dev.caskeleton.adapter.outbound.persistence.transaction.CompletionUnknownRecord
dev.caskeleton.adapter.outbound.persistence.transaction.CompletionUnknownRecorder
dev.caskeleton.adapter.outbound.persistence.transaction.DefaultJpaRetryPolicy
dev.caskeleton.adapter.outbound.persistence.transaction.EffectiveTransactionTimeouts
dev.caskeleton.adapter.outbound.persistence.transaction.EvidenceAwareJpaTransactionManager
dev.caskeleton.adapter.outbound.persistence.transaction.FullTransactionRetryCoordinator
dev.caskeleton.adapter.outbound.persistence.transaction.JpaTransactionConfig
dev.caskeleton.adapter.outbound.persistence.transaction.JpaTransactionSettings
dev.caskeleton.adapter.outbound.persistence.transaction.OptimisticConflictTranslator
dev.caskeleton.adapter.outbound.persistence.transaction.PersistenceFailureTranslatorChain
dev.caskeleton.adapter.outbound.persistence.transaction.RetryBudget
dev.caskeleton.adapter.outbound.persistence.transaction.RetrySleeper
dev.caskeleton.adapter.outbound.persistence.transaction.SpringJpaTransactionExecutor
dev.caskeleton.adapter.outbound.persistence.transaction.SpringTransactionPort
dev.caskeleton.adapter.outbound.persistence.transaction.ThreadRetrySleeper
dev.caskeleton.adapter.outbound.persistence.transaction.TransactionDefinitionMapper
dev.caskeleton.adapter.outbound.persistence.transaction.TransactionEvidenceContext
dev.caskeleton.adapter.outbound.persistence.transaction.TransactionEvidenceFrame
dev.caskeleton.adapter.outbound.persistence.transaction.TransactionEvidenceScope
dev.caskeleton.adapter.outbound.persistence.transaction.TransactionLocalTimeoutConfigurer
dev.caskeleton.adapter.outbound.persistence.transaction.TransactionProfileRegistry
dev.caskeleton.adapter.outbound.persistence.transaction.TransactionStartBudget
dev.caskeleton.adapter.outbound.persistence.transaction.UnknownOperation
dev.caskeleton.adapter.outbound.persistence.transaction.CallerTransaction
dev.caskeleton.adapter.outbound.persistence.transaction.SpringTransaction
+2 -77
View File
@@ -5,8 +5,8 @@
# root yet.
# Update only after review with:
# ./gradlew :adapter:outbound:persistence-mongo:updateMongoApiSurface -PapproveMongoApiSurfaceChange
# types: 346
dev.caskeleton.adapter.outbound.mongo.MongoOptInAutoConfigurationImportFilter
# types: 271
dev.caskeleton.adapter.outbound.mongo.MongoDefaultsEnvironmentPostProcessor
dev.caskeleton.adapter.outbound.mongo.MongoPersistenceConfig
dev.caskeleton.adapter.outbound.mongo.MongoPersistenceSettings
dev.caskeleton.adapter.outbound.mongo.MongoRootAutoConfiguration
@@ -14,22 +14,10 @@ dev.caskeleton.adapter.outbound.mongo.advanced.MongoAdvancedCapabilityFlags
dev.caskeleton.adapter.outbound.mongo.advanced.MongoAdvancedCapabilityGuard
dev.caskeleton.adapter.outbound.mongo.advanced.MongoAdvancedEntryPoint
dev.caskeleton.adapter.outbound.mongo.advanced.MongoAdvancedPolicy
dev.caskeleton.adapter.outbound.mongo.advanced.MongoAdvancedPromotionEvidence
dev.caskeleton.adapter.outbound.mongo.advanced.MongoAdvancedPromotionGate
dev.caskeleton.adapter.outbound.mongo.advanced.autoconfigure.MongoAdvancedConfiguration
dev.caskeleton.adapter.outbound.mongo.advanced.autoconfigure.MongoAdvancedSettings
dev.caskeleton.adapter.outbound.mongo.advanced.bridge.MongoBridgeCheckpointPolicy
dev.caskeleton.adapter.outbound.mongo.advanced.bridge.MongoBridgeOutboxPolicy
dev.caskeleton.adapter.outbound.mongo.advanced.bridge.MongoChangeMessagingBridge
dev.caskeleton.adapter.outbound.mongo.advanced.bridge.MongoChangeToIntegrationEventMapper
dev.caskeleton.adapter.outbound.mongo.advanced.bridge.MongoIntegrationEventEnvelope
dev.caskeleton.adapter.outbound.mongo.advanced.bridge.MongoIntegrationEventPublisher
dev.caskeleton.adapter.outbound.mongo.advanced.bridge.MongoPublishResult
dev.caskeleton.adapter.outbound.mongo.advanced.encryption.csfle.MongoCsfleClientFactory
dev.caskeleton.adapter.outbound.mongo.advanced.encryption.csfle.MongoCsfleFieldPolicy
dev.caskeleton.adapter.outbound.mongo.advanced.encryption.csfle.MongoCsfleMode
dev.caskeleton.adapter.outbound.mongo.advanced.encryption.csfle.MongoCsfleProfile
dev.caskeleton.adapter.outbound.mongo.advanced.encryption.csfle.MongoDataKeyResolver
dev.caskeleton.adapter.outbound.mongo.advanced.encryption.qe.MongoEncryptedFieldDescriptor
dev.caskeleton.adapter.outbound.mongo.advanced.encryption.qe.MongoEncryptionMetadataOwnership
dev.caskeleton.adapter.outbound.mongo.advanced.encryption.qe.MongoQueryShape
@@ -37,15 +25,6 @@ dev.caskeleton.adapter.outbound.mongo.advanced.encryption.qe.MongoQueryShapeSupp
dev.caskeleton.adapter.outbound.mongo.advanced.encryption.qe.MongoQueryableEncryptionCollectionManager
dev.caskeleton.adapter.outbound.mongo.advanced.encryption.qe.MongoQueryableEncryptionProfile
dev.caskeleton.adapter.outbound.mongo.advanced.encryption.qe.MongoQueryableEncryptionQueryType
dev.caskeleton.adapter.outbound.mongo.advanced.gridfs.MongoGridFsCompatibilityReader
dev.caskeleton.adapter.outbound.mongo.advanced.gridfs.MongoGridFsMigrationCheckpoint
dev.caskeleton.adapter.outbound.mongo.advanced.gridfs.MongoGridFsMigrationJob
dev.caskeleton.adapter.outbound.mongo.advanced.gridfs.MongoGridFsObjectReference
dev.caskeleton.adapter.outbound.mongo.advanced.search.MongoSearchIndexDescriptor
dev.caskeleton.adapter.outbound.mongo.advanced.search.MongoSearchIndexState
dev.caskeleton.adapter.outbound.mongo.advanced.search.MongoSearchOperations
dev.caskeleton.adapter.outbound.mongo.advanced.search.MongoSearchQuery
dev.caskeleton.adapter.outbound.mongo.advanced.search.MongoSearchReadinessGate
dev.caskeleton.adapter.outbound.mongo.advanced.sharding.MongoRoutingClassification
dev.caskeleton.adapter.outbound.mongo.advanced.sharding.ShardAwareQueryValidator
dev.caskeleton.adapter.outbound.mongo.advanced.sharding.ShardKeyDescriptor
@@ -56,25 +35,12 @@ dev.caskeleton.adapter.outbound.mongo.advanced.sharding.admin.ReshardApproval
dev.caskeleton.adapter.outbound.mongo.advanced.sharding.admin.ShardKeyAnalyzer
dev.caskeleton.adapter.outbound.mongo.advanced.sharding.admin.ShardKeyReadinessReport
dev.caskeleton.adapter.outbound.mongo.advanced.tenancy.database.MongoTenantClientRegistry
dev.caskeleton.adapter.outbound.mongo.advanced.tenancy.database.MongoTenantDatabaseResolver
dev.caskeleton.adapter.outbound.mongo.advanced.tenancy.database.MongoTenantLifecyclePolicy
dev.caskeleton.adapter.outbound.mongo.advanced.tenancy.database.MongoTenantMigrationCheckpointStore
dev.caskeleton.adapter.outbound.mongo.advanced.tenancy.database.MongoTenantMigrationCoordinator
dev.caskeleton.adapter.outbound.mongo.advanced.tenancy.shared.MongoTenantContext
dev.caskeleton.adapter.outbound.mongo.advanced.tenancy.shared.MongoTenantManifestValidator
dev.caskeleton.adapter.outbound.mongo.advanced.tenancy.shared.MongoTenantPredicateInjector
dev.caskeleton.adapter.outbound.mongo.advanced.tenancy.shared.TenantScopedMongoOperations
dev.caskeleton.adapter.outbound.mongo.advanced.timeseries.MongoTimeSeriesCapability
dev.caskeleton.adapter.outbound.mongo.advanced.timeseries.MongoTimeSeriesCapabilityValidator
dev.caskeleton.adapter.outbound.mongo.advanced.timeseries.MongoTimeSeriesDescriptor
dev.caskeleton.adapter.outbound.mongo.advanced.timeseries.MongoTimeSeriesGranularity
dev.caskeleton.adapter.outbound.mongo.advanced.timeseries.MongoTimeSeriesOperations
dev.caskeleton.adapter.outbound.mongo.advanced.timeseries.MongoTimeSeriesSupport
dev.caskeleton.adapter.outbound.mongo.advanced.vector.MongoEmbedding
dev.caskeleton.adapter.outbound.mongo.advanced.vector.MongoVectorIndexDescriptor
dev.caskeleton.adapter.outbound.mongo.advanced.vector.MongoVectorQuery
dev.caskeleton.adapter.outbound.mongo.advanced.vector.MongoVectorSearchBenchmarkGate
dev.caskeleton.adapter.outbound.mongo.advanced.vector.MongoVectorSearchOperations
dev.caskeleton.adapter.outbound.mongo.aggregation.MongoAggregationPlan
dev.caskeleton.adapter.outbound.mongo.aggregation.MongoAggregationProfile
dev.caskeleton.adapter.outbound.mongo.aggregation.MongoAggregationRisk
@@ -95,7 +61,6 @@ dev.caskeleton.adapter.outbound.mongo.api.consistency.MongoConsistencyDescriptor
dev.caskeleton.adapter.outbound.mongo.api.consistency.MongoConsistencyGuarantee
dev.caskeleton.adapter.outbound.mongo.api.consistency.MongoConsistencyProfile
dev.caskeleton.adapter.outbound.mongo.api.consistency.MongoConsistencyRegistry
dev.caskeleton.adapter.outbound.mongo.api.error.MongoBulkPartialFailureException
dev.caskeleton.adapter.outbound.mongo.api.error.MongoConnectionException
dev.caskeleton.adapter.outbound.mongo.api.error.MongoCursorException
dev.caskeleton.adapter.outbound.mongo.api.error.MongoDataSchemaUnsupportedException
@@ -124,7 +89,6 @@ dev.caskeleton.adapter.outbound.mongo.api.mapping.DomainDocumentId
dev.caskeleton.adapter.outbound.mongo.api.mapping.MongoBigIntegerRepresentation
dev.caskeleton.adapter.outbound.mongo.api.mapping.MongoDecimalRepresentation
dev.caskeleton.adapter.outbound.mongo.api.mapping.MongoEnumRepresentation
dev.caskeleton.adapter.outbound.mongo.api.mapping.MongoIdRepresentation
dev.caskeleton.adapter.outbound.mongo.api.mapping.MongoTemporalRepresentation
dev.caskeleton.adapter.outbound.mongo.api.mapping.MongoTypeMetadataPolicy
dev.caskeleton.adapter.outbound.mongo.api.mapping.MongoTypeRepresentationManifest
@@ -148,27 +112,6 @@ dev.caskeleton.adapter.outbound.mongo.autoconfigure.MongoPlatformSettings
dev.caskeleton.adapter.outbound.mongo.autoconfigure.MongoProfileProperties
dev.caskeleton.adapter.outbound.mongo.autoconfigure.MongoStartupValidator
dev.caskeleton.adapter.outbound.mongo.autoconfigure.MongoTopologyProbe
dev.caskeleton.adapter.outbound.mongo.changestream.MongoChangeEventIdentity
dev.caskeleton.adapter.outbound.mongo.changestream.MongoChangeStreamPipeline
dev.caskeleton.adapter.outbound.mongo.changestream.MongoChangeStreamState
dev.caskeleton.adapter.outbound.mongo.changestream.MongoChangeStreamSubscription
dev.caskeleton.adapter.outbound.mongo.changestream.MongoClusterTime
dev.caskeleton.adapter.outbound.mongo.changestream.MongoResumeCheckpoint
dev.caskeleton.adapter.outbound.mongo.changestream.MongoResumeCheckpointStore
dev.caskeleton.adapter.outbound.mongo.changestream.MongoResumePosition
dev.caskeleton.adapter.outbound.mongo.changestream.MongoResumeTokenCodec
dev.caskeleton.adapter.outbound.mongo.changestream.consumer.MongoChangeStreamSource
dev.caskeleton.adapter.outbound.mongo.changestream.consumer.ReactiveMongoChangeStreamConsumer
dev.caskeleton.adapter.outbound.mongo.changestream.consumer.SpringReactiveChangeStreamSource
dev.caskeleton.adapter.outbound.mongo.changestream.projector.MongoChangeClaim
dev.caskeleton.adapter.outbound.mongo.changestream.projector.MongoChangeDeduplicationStore
dev.caskeleton.adapter.outbound.mongo.changestream.projector.MongoChangeProjectionResult
dev.caskeleton.adapter.outbound.mongo.changestream.projector.MongoChangeProjector
dev.caskeleton.adapter.outbound.mongo.changestream.projector.MongoChangeStreamRunner
dev.caskeleton.adapter.outbound.mongo.changestream.recovery.MongoChangeHistoryLostException
dev.caskeleton.adapter.outbound.mongo.changestream.recovery.MongoChangeStreamRecoveryDecision
dev.caskeleton.adapter.outbound.mongo.changestream.recovery.MongoChangeStreamRecoveryPolicy
dev.caskeleton.adapter.outbound.mongo.changestream.recovery.MongoInvalidateRecovery
dev.caskeleton.adapter.outbound.mongo.client.MongoClientSettingsFactory
dev.caskeleton.adapter.outbound.mongo.failure.DefaultMongoFailureClassifier
dev.caskeleton.adapter.outbound.mongo.failure.DefaultMongoFailureTranslator
@@ -276,18 +219,6 @@ dev.caskeleton.adapter.outbound.mongo.query.pagination.MongoKeysetQueryBuilder
dev.caskeleton.adapter.outbound.mongo.query.pagination.MongoKeysetSlice
dev.caskeleton.adapter.outbound.mongo.query.pagination.MongoKeysetSort
dev.caskeleton.adapter.outbound.mongo.query.pagination.MongoNullSortOrdering
dev.caskeleton.adapter.outbound.mongo.reactive.DefaultReactiveMongoExecutor
dev.caskeleton.adapter.outbound.mongo.reactive.ReactiveMongoCallback
dev.caskeleton.adapter.outbound.mongo.reactive.ReactiveMongoCollectionAccess
dev.caskeleton.adapter.outbound.mongo.reactive.ReactiveMongoConsistencyBinder
dev.caskeleton.adapter.outbound.mongo.reactive.ReactiveMongoContextKeys
dev.caskeleton.adapter.outbound.mongo.reactive.ReactiveMongoExecutor
dev.caskeleton.adapter.outbound.mongo.reactive.ReactiveScopedMongoOperations
dev.caskeleton.adapter.outbound.mongo.reactive.cursor.MongoCursorGuard
dev.caskeleton.adapter.outbound.mongo.reactive.cursor.MongoCursorLease
dev.caskeleton.adapter.outbound.mongo.reactive.cursor.MongoCursorTermination
dev.caskeleton.adapter.outbound.mongo.reactive.cursor.MongoReactiveCursorPublisher
dev.caskeleton.adapter.outbound.mongo.reactive.cursor.MongoResultBudgetTracker
dev.caskeleton.adapter.outbound.mongo.schema.index.MongoIndexApplyPolicy
dev.caskeleton.adapter.outbound.mongo.schema.index.MongoIndexDescriptorView
dev.caskeleton.adapter.outbound.mongo.schema.index.MongoIndexDiff
@@ -337,18 +268,12 @@ dev.caskeleton.adapter.outbound.mongo.transaction.MongoTransactionProfile
dev.caskeleton.adapter.outbound.mongo.transaction.MongoTransactionScope
dev.caskeleton.adapter.outbound.mongo.transaction.MongoTransactionSession
dev.caskeleton.adapter.outbound.mongo.transaction.MongoTransactionSessionFactory
dev.caskeleton.adapter.outbound.mongo.transaction.ReactiveMongoTransactionExecutor
dev.caskeleton.adapter.outbound.mongo.transaction.ReactiveMongoTransactionSession
dev.caskeleton.adapter.outbound.mongo.transaction.ReactiveMongoTransactionSessionFactory
dev.caskeleton.adapter.outbound.mongo.transaction.SpringMongoTransactionExecutor
dev.caskeleton.adapter.outbound.mongo.transaction.SpringMongoTransactionSessionFactory
dev.caskeleton.adapter.outbound.mongo.transaction.SpringReactiveMongoTransactionExecutor
dev.caskeleton.adapter.outbound.mongo.transaction.SpringReactiveMongoTransactionSessionFactory
dev.caskeleton.adapter.outbound.mongo.transaction.retry.MongoCommitReconciler
dev.caskeleton.adapter.outbound.mongo.transaction.retry.MongoRetryBudget
dev.caskeleton.adapter.outbound.mongo.transaction.retry.MongoRetryDecision
dev.caskeleton.adapter.outbound.mongo.transaction.retry.MongoTransactionRetryCoordinator
dev.caskeleton.adapter.outbound.mongo.transaction.session.MongoCausalSessionContext
dev.caskeleton.adapter.outbound.mongo.transaction.session.MongoCausalSessionExecutor
dev.caskeleton.adapter.outbound.mongo.transaction.session.ReactiveMongoCausalSessionExecutor
dev.caskeleton.adapter.outbound.mongo.transaction.session.SpringMongoCausalSessionExecutor
@@ -0,0 +1,6 @@
# Supported production adopter surface for the fileserver persistence leaf.
# Language-level public implementation types are not compatibility promises.
# Adding an import outside this list requires an explicit review of the adopter contract.
# Checked by verifyPersistenceFileserverApiSurface (ca.api-surface adopterBaseline); every entry must
# be in persistence-fileserver-api-surface.txt.
dev.caskeleton.adapter.outbound.persistence.fileserver.FileserverSchemaActivation
@@ -0,0 +1,30 @@
# Fileserver persistence leaf public API surface — every public top-level type in src/main/java.
# Entities, Spring Data repositories and store adapters are implementation;
# the adopter baseline lists the subset other leaves' production code may import.
# Update only after review with:
# ./gradlew :adapter:outbound:persistence-fileserver:updatePersistenceFileserverApiSurface -PapprovePersistenceFileserverApiSurfaceChange
# types: 24
dev.caskeleton.adapter.outbound.persistence.fileserver.FileserverJpaPersistenceConfig
dev.caskeleton.adapter.outbound.persistence.fileserver.FileserverSchemaActivation
dev.caskeleton.adapter.outbound.persistence.fileserver.JpaCleanupQueue
dev.caskeleton.adapter.outbound.persistence.fileserver.JpaContentReferenceLedger
dev.caskeleton.adapter.outbound.persistence.fileserver.JpaFileMetadata
dev.caskeleton.adapter.outbound.persistence.fileserver.JpaFileQuota
dev.caskeleton.adapter.outbound.persistence.fileserver.JpaQuotaCommit
dev.caskeleton.adapter.outbound.persistence.fileserver.JpaQuotaReclaim
dev.caskeleton.adapter.outbound.persistence.fileserver.JpaRecoveryQueue
dev.caskeleton.adapter.outbound.persistence.fileserver.JpaStagingUploadLocator
dev.caskeleton.adapter.outbound.persistence.fileserver.JpaUploadSession
dev.caskeleton.adapter.outbound.persistence.fileserver.entity.CleanupItemEntity
dev.caskeleton.adapter.outbound.persistence.fileserver.entity.FileEntity
dev.caskeleton.adapter.outbound.persistence.fileserver.entity.QuotaReservationEntity
dev.caskeleton.adapter.outbound.persistence.fileserver.entity.RecoveryItemEntity
dev.caskeleton.adapter.outbound.persistence.fileserver.entity.UploadSessionEntity
dev.caskeleton.adapter.outbound.persistence.fileserver.entity.VerificationResultEntity
dev.caskeleton.adapter.outbound.persistence.fileserver.repository.FileTransitionRepository
dev.caskeleton.adapter.outbound.persistence.fileserver.repository.FileserverCleanupRepository
dev.caskeleton.adapter.outbound.persistence.fileserver.repository.FileserverQuotaRepository
dev.caskeleton.adapter.outbound.persistence.fileserver.repository.FileserverRecoveryRepository
dev.caskeleton.adapter.outbound.persistence.fileserver.repository.JpaFileRepository
dev.caskeleton.adapter.outbound.persistence.fileserver.repository.JpaUploadSessionRepository
dev.caskeleton.adapter.outbound.persistence.fileserver.repository.UploadLeaseRepository
+499 -22
View File
@@ -9,7 +9,7 @@ real provider."
| Column | The question | Who decides it |
| --- | --- | --- |
| **IMPLEMENTED** | Does this repository contain the capability? | `src/config/architecture/modules.json` — the leaf is registered |
| **WIRED** | Does the shipped `app-bootstrap` artifact assemble it when its switch is on? | the leaf's `META-INF/spring/...AutoConfiguration.imports`, its edge in `app-bootstrap/build.gradle`, and a composition test that boots `CaSkeletonApplication` |
| **WIRED** | Present when selected: does the module assemble itself — own `AutoConfiguration.imports`, own settings, on when present, off with `enabled=false` — once a service adds its one `runtimeOnly` line to `app-bootstrap/build.gradle`? | the leaf's `META-INF/spring/...AutoConfiguration.imports`, the commented line in `app-bootstrap/build.gradle`, and an activation test in the leaf (present = on, `enabled=false` = off) |
| **QUALIFIED** | Has it been proven against a real provider, by something CI runs? | a strict test lane against a real provider **and** a workflow that executes it |
The third column is the one that rots quietly, because a lane can exist and be invoked by nothing.
@@ -17,35 +17,512 @@ Each row below names the lane *and* the workflow, so "qualified" can be checked
## Status
| Capability | Master switch | IMPLEMENTED | WIRED | QUALIFIED | Evidence |
The default composition — what `bootJar` builds — is web, observability, `domain-core`,
`application-core`, `shared-contract`, `adapter:outbound:support` and `adapter:outbound:identifier`.
Every **yes** row in WIRED below is absent from it until a service uncomments that row's
`runtimeOnly` line in `app-bootstrap/build.gradle`. A module on the classpath is on; its enabled key
defaults to `true`, and `false` turns a present module fully off. `./gradlew
:app-bootstrap:qualificationBootJar` packages the main runtime plus every capability, for compose
lanes and CI; it is not a deployment artifact.
| Capability | Enabled key (property / env, default) | IMPLEMENTED | WIRED | QUALIFIED | Evidence |
| --- | --- | --- | --- | --- | --- |
| Relational persistence (JPA/PostgreSQL) | `APP_PERSISTENCE_JPA_ENABLED` | yes | yes | yes | six `postgresql*IntegrationTest` lanes, run by `integration-main.yml` → `jpa-provider-ownership-contracts` |
| Document persistence (MongoDB) | `APP_PERSISTENCE_MONGO_ENABLED` | yes | yes | yes | six container lanes (`mongoReplicaSetTest`, `mongoFailoverTest`, …), run by `integration-main.yml` → `mongo-container-lanes` |
| Messaging (broker-neutral core) | `APP_MESSAGING_ENABLED` | yes | yes | Kafka only | `messaging-kafka:messagingCertificationTest` behind `verifyMessagingCertificationEvidence`, run by `messaging-certification.yml`. **No broker starter ships**: a deployment composes `messaging-spring-boot-starter-kafka` or `-rabbit` itself, and selecting a broker it did not compose is refused at startup. Rabbit ships validators and no transport. |
| Redis capabilities (cache / rate-limit / lease / idempotency) | `APP_REDIS_ENABLED` | yes | yes | yes | `cache-redis:redisTopologyTest`, run by `redis-sdk-topology.yml` |
| Notification platform | `APP_NOTIFICATION_PLATFORM_ENABLED` | yes | yes | claim-scoped | `verifyNotificationEvidence` refuses a grade in `docs/notification/support-matrix.md` that no proven claim backs; run by `notification-platform.yml`. There is no real-SMTP lane, and the matrix says so rather than implying one. |
| File export publication (R2) | `APP_FILESERVER_ENABLED` | yes | yes | yes | A different capability from the platform row below, in its own namespace so the two cannot be switched on together by accident. Atomic publication and durability are proven by `adapter:outbound:fileserver`'s own lanes inside its `check`, which every PR runs. |
| File server platform | `APP_FILESERVER_PLATFORM_ENABLED` | yes | yes | yes | `app-bootstrap:integrationTest` → `FileserverCompositionIntegrationTest` (required by the strict lane, so it cannot silently disappear), run by `integration-main.yml` → `bootstrap-integration` |
| Outbound HTTP client | `APP_HTTPCLIENT_ENABLED` | yes | yes | yes | `httpclient:httpClientFailureInjectionTest` against a faulted upstream, run by `integration-main.yml` → `httpclient-fault-injection` |
| GraphQL transport | `APP_GRAPHQL_ENABLED` | yes | yes | compose-level | `local-graphql` and the three `off-*` lanes in `src/config/runtime/compose-profile-contracts.json`, run by `integration-main.yml` → `compose-runtime-smoke`. The route's absence when the switch is off is what those lanes prove. |
| Object storage | `app.object-storage.enabled` (no `MasterSwitch` entry) | yes | **no** | MinIO only | The leaf is **not** an `app-bootstrap` dependency — only `sample-portfolio` consumes it, and `app-bootstrap:integrationTest` assembles it test-only against digest-pinned MinIO. A fork that wants it adds the edge. |
| Relational persistence (JPA/PostgreSQL) | `ca-skeleton.persistence-jpa.enabled` / `APP_PERSISTENCE_JPA_ENABLED`, `true` | yes | yes (one line: `runtimeOnly project(':adapter:outbound:persistence-jpa')`) | yes | Not in the default composition. The one line brings everything — its own `AutoConfiguration.imports` (`PersistenceJpaAutoConfiguration`, `PersistenceJpaRuntimeConfig`, `JpaStartupAutoConfiguration`), its environment handling (`JpaActivationEnvironmentPostProcessor`, `spring.factories`: readiness `db` while on; with `false` it also excludes Boot's JDBC, Hibernate, Spring Data JPA and Flyway auto-configuration, so no DataSource is bound), the startup guards (Flyway strategy, datasource/OSIV/DDL/pool/TLS/vendor checks, exit codes unchanged) and its settings (`config/module-defaults/persistence-jpa.yml`). `persistence-jpa:PersistenceJpaCapabilityAssemblyTest` proves the module assembles on its own; six `postgresql*IntegrationTest` lanes, run by `integration-main.yml` → `jpa-provider-ownership-contracts`, qualify it against PostgreSQL. `sample-portfolio` selects it by its build dependency and the module's auto-configuration (no broad scan of the persistence package). `bootRunH2` adds the module to its own classpath only. |
| Document persistence (MongoDB) | `ca-skeleton.persistence-mongo.enabled` / `APP_PERSISTENCE_MONGO_ENABLED`, `true` | yes | yes (one line: `runtimeOnly project(':adapter:outbound:persistence-mongo')`) | yes | On when present; `false` also excludes Boot's Mongo auto-configuration (`MongoCapabilityActivationTest`). The connection-source rule (`SPRING_MONGODB_URI` or the selected profile's `uri-secret`) is checked by the module's own `MongoDefaultsEnvironmentPostProcessor`. Six container lanes (`mongoReplicaSetTest`, `mongoFailoverTest`, …), run by `integration-main.yml` → `mongo-container-lanes` |
| Messaging (Kafka) | `app.messaging.enabled` / `APP_MESSAGING_ENABLED`, `true` | yes | yes (one line: `runtimeOnly project(':adapter:outbound:messaging-kafka')`, which brings the application bridge, the legacy `KafkaSender` seam and the vendored platform with its Kafka transport) | Kafka only | On when present (`KafkaCapabilityActivationTest`). `messaging-kafka:messagingCertificationTest` behind `verifyMessagingCertificationEvidence`, run by `messaging-certification.yml`; the starter's `integrationTest` is the live Kafka round trip. Kafka is the only registered broker; the RabbitMQ broker keys were removed (no transport). |
| Redis capabilities (cache / rate-limit / lease / idempotency) | `app.redis.enabled` / `APP_REDIS_ENABLED`, `true` | yes | yes (one line: `runtimeOnly project(':adapter:outbound:cache-redis')`, which brings `redis-runtime`) | yes | `cache-redis:redisTopologyTest`, run by `redis-sdk-topology.yml`. Not in the default composition. On when present; `false` contributes no Redis bean — no settings, client, connection, thread or health contributor. The module owns its readiness contribution (`RedisReadinessGroupPostProcessor`, `spring.factories`) and its settings (`config/module-defaults/cache-redis.yml`: `app.redis.enabled`, `app.rate-limit.*`, the Redis `ca-skeleton.capabilities.*`). No `app-bootstrap` main source names a Redis type. |
| Request idempotency | `APP_IDEMPOTENCY_PROVIDER` (`disabled` \| `redis` \| `postgresql`; a selector, not an on/off key) | yes | yes | Redis only | One generation: the application `IdempotencyExecutor`, built once by `app-bootstrap` `IdempotencyProviderSelectionConfig` over the one store the selected provider contributes (`cache-redis` or `persistence-jpa`); startup is refused unless exactly one store exists. `sample-portfolio` cannot depend on `app-bootstrap`, so its own `SampleIdempotencyConfig` builds its one executor from the same keys. Redis is covered by the row above. PostgreSQL has `persistence-jpa:postgresqlIdempotencyIntegrationTest`, but no workflow runs it. The `postgresql` provider refuses a non-PostgreSQL data source, so `bootRunH2` uses `disabled` or `redis`.. The executor stays in the composition root on purpose — it needs only application-core and its settings — while each store comes with its module: `postgresql` needs the persistence-jpa line, `redis` the cache-redis one. |
| Transactional outbox relay | `ca-skeleton.outbox.enabled` / `APP_OUTBOX_ENABLED`, `false` (+ `APP_OUTBOX_RELAY_ENABLED`, `false`; persistence-jpa settings) | yes | yes (with the persistence-jpa line; the scheduler also needs the messaging-kafka line) | yes | The store and its settings are persistence-jpa's; the relay (`OutboxConfig`) is application composition in `app-bootstrap` because a driven adapter must not build or call a use case. It turns on only when an `OutboxStorePort` bean exists, and the scheduler only when an `OutboxMessagePublishPort` does (the messaging bridge), each ordered after its contributor by `afterName` — so an environment with no publisher keeps its PENDING rows. The bridge registers no stand-in publisher: a present-and-enabled bridge with a blank broker and no canonical transport is refused at startup. `postgresqlLegacyOutboxConcurrentRelayIntegrationTest` qualifies claim/fencing against PostgreSQL. |
| Notification platform | `ca-skeleton.notification.platform.enabled` / `APP_NOTIFICATION_PLATFORM_ENABLED`, `true` | yes | yes (one line: `runtimeOnly project(':composition:notification-platform')`, plus the persistence-jpa line) | claim-scoped | Not in the default composition. The one line brings the use-case assembly, `adapter:outbound:notification`, the HTTP surface `adapter:inbound:web-notification` and its own settings (`config/module-defaults/notification.yml`), each registered through the module's own `AutoConfiguration.imports`; `adapter:inbound:web` no longer depends on `application-notification`. `verifyNotificationEvidence` refuses a grade in `docs/notification/support-matrix.md` that no proven claim backs; run by `notification-platform.yml`. There is no real-SMTP lane, and the matrix says so rather than implying one. |
| File server platform | `app.fileserver-platform.enabled` / `APP_FILESERVER_PLATFORM_ENABLED`, `true` | yes | yes (one line: `runtimeOnly project(':composition:fileserver-platform')`, plus the persistence-jpa line) | yes | On when present; module-owned `config/module-defaults/fileserver.yml` also carries the servlet multipart ceiling. `app-bootstrap:integrationTest` → `FileserverCompositionIntegrationTest` (required by the strict lane), run by `integration-main.yml` → `bootstrap-integration` |
| Outbound HTTP client | `app.httpclient.enabled` / `APP_HTTPCLIENT_ENABLED`, `true` | yes | yes (one line: `runtimeOnly project(':adapter:outbound:httpclient')`) | yes | On when present (`HttpClientPlatformActivationTest`). `httpclient:httpClientFailureInjectionTest` against a faulted upstream, run by `integration-main.yml` → `httpclient-fault-injection` |
| GraphQL transport | `backend.graphql.enabled` / `APP_GRAPHQL_ENABLED`, `true` | yes | yes (one line: `runtimeOnly project(':adapter:inbound:graphql')`) | leaf-level | On when present; `false` also excludes Spring GraphQL's own auto-configuration, so no `/graphql` (`GraphQlCapabilityActivationTest`). `graphqlTransportQualificationTest` runs the HTTP boundary. The deployment-mode/runtime-profile rule is the module's own `GraphQlPlatformStartupValidator`. The default jar does not ship GraphQL, so a compose lane that exercises it runs the qualification jar. |
| Object storage | `app.object-storage.enabled` (no `APP_*` row), `true` | yes | yes (one line: `runtimeOnly project(':adapter:outbound:objectstorage')`) | MinIO only | Own `ObjectStorageAutoConfiguration` (was bound through bootstrap's properties scan); on when present, `false` leaves only the explicit legacy seam (`ObjectStorageAutoConfigurationTest`). `app-bootstrap:integrationTest` assembles it against digest-pinned MinIO. |
| gRPC platform | — (build-level) | yes | **no** | yes | Absent from the main build entirely: `optional-platforms` is a separate Gradle build, so the switch is the `include`, not an environment variable. `-p optional-platforms ci` runs on every PR and `integrationCheck` certifies the operation ledger against real PostgreSQL. |
| WebSocket transport | — (build-level) | yes | **no** | — | Qualification-only edge in `app-bootstrap`; `ConditionalTransportBuildContractTest` asserts it has no production edge. |
| gRPC transport (`adapter:inbound:grpc`) | `ca-skeleton.grpc.server.enabled` (no `APP_*` row), `true` | yes | yes (one line: `runtimeOnly project(':adapter:inbound:grpc')`) | leaf-level | Own `AutoConfiguration.imports` (`GrpcServerConfig`); on when present, and the loopback plaintext listener still needs `ca-skeleton.grpc.server.allow-insecure-local=true` (`GrpcSafeActivationTest`, `grpcTransportQualificationTest`). |
| WebSocket transport | `app.websocket.enabled` / `APP_WEBSOCKET_ENABLED`, `true` | yes | yes (one line: `runtimeOnly project(':adapter:inbound:websocket')`) | — | Own `AutoConfiguration.imports` (`WebSocketConfig`), on in a servlet app when present (`WebSocketAutoConfigurationTest`); `ConditionalTransportBuildContractTest` asserts it has no default production edge. |
| Web Advanced library (`adapter:inbound:web-advanced`) | — (build-level; three `backend.web.advanced.*.enabled` switches inside) | yes | **no** | — | No composition root depends on it; `app-bootstrap` takes it `testRuntimeOnly` for the ArchUnit import. No real-provider lane: `webAdvancedTest` (the `web-advanced` tag, run by `release.yml` → `web-stable-release-gate`) is unit and context-runner level. The Nginx lane went with the proxy library on 2026-09-25. |
## Reading the "no" rows
A **no** in WIRED is not a defect. It is the review's Build Composition principle working: the
repository holds more capabilities than any one derived service should ship, and a capability that
is absent from the artifact holds no beans, no connections and no threads whatever its configuration
says. The three **no** rows are the ones where that choice has been made and is enforced by a test.
A **yes** in WIRED means "present when its line is selected": uncommenting the one line is the whole
change, and deleting it removes the module's beans, settings and dependencies together. It does not
mean the default artifact ships the capability — none of the **yes** rows is in the default
composition. A capability that is absent from the artifact holds no beans, no connections and no
threads whatever its configuration says, so the missing line is the ordinary off state and
`enabled=false` is only the explicit off for a module that is present.
The rows that say **yes** are the ones where the choice is still "ship it and switch it off", which
is a weaker guarantee — correct, but it depends on the switch being honest rather than on the code
being absent. Moving more rows to **no** is what `app-bootstrap`'s composition-ownership work is for.
A **no** in WIRED is not a defect either. It marks a capability with no one-line selection: the gRPC
platform is a separate Gradle build, and the web-advanced library is taken as `implementation` by a
service's own adapter leaf, never by a composition root.
## Keeping this honest
`CapabilityStatusDocumentTest` derives the switch list from `MasterSwitch` and fails when a switch
has no row here. That is deliberately the only automated check: a table of facts that a parser
`CapabilityStatusDocumentTest` checks that the column sources above are named — the module
registry, `AutoConfiguration.imports`, and a workflow that executes the lane. The switch list it used
to derive from `MasterSwitch` went with that class (2026-09-25). That is deliberately the only
automated check: a table of facts that a parser
re-derives would be a second source of truth, and the columns above are judgements about evidence,
which is exactly the thing the review says a build must not pretend to compute.
## 제거된 코드 (2026-09-25 리팩터링)
web 경로의 `W/`는 `src/adapter/inbound/web/src/main/java/dev/caskeleton/adapter/inbound/web/`, `WF/`는 `src/adapter/inbound/web-fileserver/src/main/java/dev/caskeleton/adapter/inbound/web/fileserver/`.
복구가 필요하면 표의 커밋에서 경로를 꺼낸다(`git show <커밋>:<경로>`).
리뷰 후속 작업(2026-09-25~28, `docs/superpowers/plans/2026-09-25-review-followup.md`)에서 지운 것은 마지막으로 존재한 커밋이 `6d27356e`인 행으로 표 끝에 이어 붙였다.
| 대상 | 경로 | 마지막으로 존재한 커밋 | 이유 |
| --- | --- | --- | --- |
| 파일 publication R1/R2 어댑터(`FileserverR2Config`, `FileExportConfig`, local-persistent provider 등 31개)와 테스트 | `src/adapter/outbound/fileserver/src/main/java/dev/caskeleton/adapter/outbound/fileserver/*.java`, 같은 위치의 `src/test` 루트 파일 | `208077fd` | 조립 경로 없음(component scan 밖, 호출자 없음) |
| `FilePublicationPort`·`FileExportPort` 계약 | `src/application-core/src/main/java/dev/caskeleton/application/filepublication/`, `.../application/fileexport/` | `208077fd` | 호출자 없음 |
| `MasterSwitch.FILESERVER`, `app.fileserver.*`·`app.file-export.*` 설정, `APP_FILESERVER_ENABLED`·`APP_FILESERVER_LOCAL_*` env key | `src/shared-contract/.../activation/MasterSwitch.java`, `src/app-bootstrap/src/main/resources/config/fileserver.yml` | `208077fd` | 읽는 코드 없음 |
| websocket Advanced STOMP·RabbitMQ relay(`StompBrokerExclusivity` 포함), `APP_WEBSOCKET_ADVANCED_STOMP_*` env key | `src/adapter/inbound/websocket/src/main/java/dev/caskeleton/adapter/inbound/websocket/advanced/stomp/` | `208077fd` | 같은 기능의 중복 구현(`stomp/`가 남음) |
| websocket main의 검증용 코드(`moduleboundary`, `evidence`, `release`) | `src/adapter/inbound/websocket/src/main/java/dev/caskeleton/adapter/inbound/websocket/{moduleboundary,evidence,release}/` | `208077fd` | 호출자 없음 |
| httpclient `BoundedErrorBody` | `src/adapter/outbound/httpclient/src/main/java/dev/caskeleton/adapter/outbound/httpclient/restclient/BoundedErrorBody.java` | `208077fd` | 호출자 없음 |
| httpclient Spring 7 service group·`RestTemplate` 이행 패키지 | `src/adapter/outbound/httpclient/src/main/java/dev/caskeleton/adapter/outbound/httpclient/{spring7,migration}/` | `208077fd` | 테스트에서만 사용 |
| `UuidCodec` | `src/adapter/outbound/identifier/src/main/java/dev/caskeleton/adapter/outbound/identifier/UuidCodec.java` | `208077fd` | 호출자 없음 |
| object storage legacy adoption(`maintenance/`, `ObjectStorageLegacyMigrationConfig`, `LegacyObjectAdoptionSettings`), `storage/migration` 포트, sample `AdoptLegacyPosterImageUseCase`와 전용 타입 | `src/adapter/outbound/objectstorage/src/main/java/dev/caskeleton/adapter/outbound/objectstorage/maintenance/`, `src/application-objectstorage/src/main/java/dev/caskeleton/application/storage/migration/`, `src/sample-portfolio/.../application/poster/migration/` | `208077fd` | 켜면 기동 실패(SPI 구현 없음) |
| object storage readiness 타입(`ObjectStorageCapabilityEvidence`, `ObjectStorageCapabilityCard`, `ObjectStorageReadinessLevel`) | `src/adapter/outbound/objectstorage/src/main/java/dev/caskeleton/adapter/outbound/objectstorage/readiness/` | `208077fd` | 테스트에서만 사용(검증은 `ObjectStorageReadinessRegistryTest`로 이동) |
| `ObjectControlRecordEnvelope` | `src/adapter/outbound/objectstorage/src/main/java/dev/caskeleton/adapter/outbound/objectstorage/control/ObjectControlRecordEnvelope.java` | `208077fd` | 호출자 없음 |
| application-core 테스트 헬퍼 `CompiledPackageScanner` | `src/application-core/src/test/java/dev/caskeleton/application/testsupport/CompiledPackageScanner.java` | `208077fd` | 호출자 없음 |
| web WebFlux 플랫폼 (`WebFluxPlatformAutoConfiguration` 외) | `W/webflux/` | `208077fd` | D4: servlet + virtual threads 단일 스택, 기본 조립이 선택할 수 없음 |
| web Advanced WebFlux 스트리밍·blocking bridge 어댑터 | `W/advanced/webflux/` | `208077fd` | D4: WebFlux 쌍둥이 |
| 알림 콜백 WebFlux 핸들러 | `W/notification/platform/callback/reactive/` | `208077fd` | D4: WebFlux 쌍둥이 (MVC 컨트롤러가 유일 경로) |
| 파일 서버 WebFlux 전송 | `WF/reactive/` | `208077fd` | D4: WebFlux 쌍둥이, 조립 불가 |
| WebFlux 계약·성능 lane, cross-stack parity lane | `src/adapter/inbound/web/src/webfluxContractTest/`, `build.gradle`의 `webFluxContractTest`·`webFluxPerformanceTest`·`webCrossStackParityTest` | `208077fd` | D4: Reactor Netty 대상 lane, 비교 대상 소멸 |
| web 모듈 경계 맵 (`WebStableModule` 외) | `W/moduleboundary/`, `src/adapter/inbound/web/src/test/java/dev/caskeleton/adapter/inbound/web/moduleboundary/` | `208077fd` | main에 둔 governance 코드, 소비자 없음 |
| 서명 커서 코덱 (`CursorCodec`, `CursorException`) | `W/cursor/` | `208077fd` | 호출자 0, `GlobalExceptionHandler` 커서 처리도 함께 제거 |
| 2세대 관측 (`WebAccessLog*`, `WebAudit*`, `WebObservationConvention`, `WebMetricCardinalityPolicy`) | `W/observability/` | `208077fd` | 조립 안 된 2세대, `RequestLoggingFilter`가 정본 |
| 2세대 조건부 요청 (`EntityTag`, `ConditionalReadEvaluator`, `MutationPreconditionEvaluator` 외) | `W/conditional/` | `208077fd` | 2세대, `ETags`·`PreconditionFailedException`이 정본 |
| 2세대 페이지네이션 (`HmacWebCursorCodec`, `WebCollectionRequestParser` 외 16개) | `W/pagination/` | `208077fd` | 2세대, `PageParams`·`SortParam`이 정본 |
| 응답 계약·헤더 이름 (`WebHeaderName`, `WebResponseContract`, `WebSuccessResponse`, `DeprecationHeaderWriter`) | `W/http/`, `W/versioning/` | `208077fd` | 호출자 0 |
| 병렬 rate-limit (`WebRateLimiter`, web `RateLimitDecision`·`RateLimitFailurePolicy`·`RateLimitProfileName`, `WebMvcThrottleFilter`, `ThrottleProblemWriter`) | `W/ratelimit/`, `W/mvc/throttle/`, `W/error/` | `208077fd` | 2세대, `RateLimitInterceptor` + shared-contract `RateLimitDecision`이 정본 |
| rate-limit draft 헤더 (`RATELIMIT_DRAFT_HEADERS`) | `W/advanced/ratelimit/`, `WebAdvancedFeature` 상수 | `208077fd` | 병렬 rate-limit 세트에만 붙는 부가 기능 |
| admission 제어 | `W/admission/` | `208077fd` | 조립 안 된 2세대 |
| evidence 필터·startup check·platform snapshot | `W/evidence/`, `W/mvc/filter/WebMvcEvidenceFilter.java`, `W/mvc/autoconfigure/WebMvcPlatformStartupCheck.java`, `W/admin/platform/` | `208077fd` | 읽는 곳 없는 bean, `WebMvcPlatformAutoConfiguration`은 3개 bean만 유지 |
| 검증 예외 매퍼 | `W/validation/` | `208077fd` | 제거된 bean·problem handler에서만 도달 |
| WebProblem 어휘 (`ProblemCode`, `ProblemCatalog`, `WebProblem`, `WebProblemFactory` 외) | `W/error/`, `W/mvc/error/`, `src/adapter/inbound/web/src/main/resources/META-INF/web/problem-catalog.yaml`, `W/openapi/ProblemSchemaContributor.java`, `W/openapi/WebOpenApiReleaseGate.java` | `208077fd` | 운영 에러는 `GlobalExceptionHandler`의 Envelope, `spring.mvc.problemdetails.enabled=false` |
| 요청 budget 필터 (`WebMvcBudgetFilter`, `BudgetProblemMapper`) | `W/mvc/budget/`, `W/error/BudgetProblemMapper.java` | `208077fd` | fixture 전용, WebProblem 어휘에 의존 |
| stream 종료 어휘 (`TerminationDecision`, `WebStreamEnvelope`, `WebStreamTerminationMapper`) | `W/advanced/stream/` | `208077fd` | `ProblemCode`에 의존, 호출자 0 |
| durable operation HTTP 투영 (`OperationQueryService`, `OperationHttpController` 외) | `W/operationasync/`, `W/mvc/operation/` | `208077fd` | 운영 조립 없음(scan 제외·bean 없음), 실패를 `WebProblem`으로만 표현. application-core use case는 유지 |
| WebProblem·budget·throttle·operation fixture와 lane | `src/adapter/inbound/web/src/testFixtures/java/dev/caskeleton/adapter/inbound/web/testkit/{budget,throttle,operation,contract,webflux}/`, `webtestkit/{Budget,Throttle}FixtureApplication.java`, `systemTest`·`jettyCompatTest`의 budget/contract/operation/throttle IT | `208077fd` | 제거된 표면만 인증. Tomcat/Jetty 전송 lane은 Envelope 기준으로 유지 |
| WebFlux 전용 오버로드 (`ZeroCopyEligibility.isEligible(ServerHttpResponse…)`·`supportsZeroCopy`, `CallbackRequestFactory.create(…externalUrl…)`) | `WF/http/ZeroCopyEligibility.java`, `W/notification/platform/callback/CallbackRequestFactory.java` | `208077fd` | 제거된 reactive 핸들러만 호출 |
| graphql 부팅 시 컨트롤러 경계 검사 `architecture/` (9개, ~970줄) | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/architecture/` | `208077fd` | 부팅마다 리플렉션으로 검사하던 것. 규칙 2개(resolver 전송 타입, raw DataFetcher 위치)는 `GraphQlTransportBoundaryArchitectureTest`(ArchUnit)로 옮김 |
| `GraphQlPlatformAutoConfiguration.graphQlControllerBoundaryCheck` bean | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/autoconfigure/GraphQlPlatformAutoConfiguration.java` | `208077fd` | 위 검사를 부팅 때 돌리던 bean. 빌드 때 ArchUnit으로 대체 |
| graphql 스키마 호환성 비교기 `compat/` (11개, ~1,560줄) | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/compat/` | `208077fd` | 호출하는 production 코드 없음(테스트만) |
| graphql 모듈 경계 모델 `moduleboundary/` (main 4개 + test 스캐너 3개) | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/moduleboundary/` | `208077fd` | sub-package 경계 선언과 소스 스캐너 테스트. 런타임 소비자 없음 |
| graphql 릴리스 게이트 `release/` (9개) | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/release/` | `208077fd` | 호출하는 곳 없음. 성능·장애 증거도 없었음 |
| graphql Advanced 릴리스 게이트 `advanced/release/` (7개) | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/advanced/release/` | `208077fd` | 호출하는 곳 없음 |
| `GraphQlAdvancedDependencyRules` | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/advanced/bootstrap/GraphQlAdvancedDependencyRules.java` | `208077fd` | `moduleboundary` 전용, 테스트에서만 사용 |
| `GraphQlGeneratedCompatibilityGate` | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/advanced/codegen/GraphQlGeneratedCompatibilityGate.java` | `208077fd` | `compat` 전용, 테스트에서만 사용 |
| testFixtures `GraphQlSchemaContractSuite` | `src/adapter/inbound/graphql/src/testFixtures/java/dev/caskeleton/adapter/inbound/graphql/testkit/GraphQlSchemaContractSuite.java` | `208077fd` | `compat` 의존, 테스트에서만 사용 |
| messaging adapter R1 contract/binding 컴파일러 `contract/`·`destination/`·`config/` (MessagingCapabilityCardRegistry 포함) | `src/adapter/outbound/messaging/src/main/java/dev/caskeleton/adapter/outbound/messaging/{contract,destination,config}/` | `208077fd` | 어느 조립에도 연결되지 않은 R1 세대 |
| messaging adapter R1 JSON Schema envelope encoder `envelope/` + pin한 Draft 2020-12 meta-schema 리소스 | `src/adapter/outbound/messaging/src/main/java/dev/caskeleton/adapter/outbound/messaging/envelope/, src/adapter/outbound/messaging/src/main/resources/contracts/messaging/meta/` | `208077fd` | 조립 없음. NetworkNT가 production 의존성에서 빠짐. `IntegrationEventEncoderPort`는 adopter 확장 지점으로 유지 |
| messaging adapter `realtime/` (`MessagingDurableFanoutAdapter`, `RealtimeFanoutEnvelopeJson`) | `src/adapter/outbound/messaging/src/main/java/dev/caskeleton/adapter/outbound/messaging/realtime/` | `208077fd` | bean 없음 |
| strict lane `messagingCompiledContractsQualificationTest`·`messagingJsonSchemaV1QualificationTest`, 루트 `verifyMessagingJsonSchemaV1`·`validateMessagingJsonSchemaV1EvidenceManifestSchema` | `src/adapter/outbound/messaging/build.gradle, src/build-tools/src/main/java/dev/caskeleton/buildtools/messaging/MessagingQualificationPlugin.java` | `208077fd` | 삭제한 R1 코드만 검증하던 레인. `verifyMessagingContracts`는 application·shared 레인으로 남김 |
| `MessagingEvidenceManifestSchemaValidator`(+Test)와 루트 JavaExec `validateMessagingContractsEvidenceManifestSchema` | `src/adapter/outbound/messaging/src/test/java/dev/caskeleton/adapter/outbound/messaging/qualification/` | `208077fd` | 삭제한 `LocalJsonSchemaRegistry`에 의존했고, 다른 project의 test classpath를 루트 task가 풀어 쓰는 구조였음. 같은 검증을 build-tools `MessagingEvidenceSchemaValidator`로 옮겨 `verifyMessagingContracts`가 직접 수행 |
| `messaging-pulsar-experimental` leaf | `src/messaging/messaging-pulsar-experimental/` | `208077fd` | SDK 없는 seam, 기본 비활성, 조립 없음 |
| `messaging-nats-experimental` leaf | `src/messaging/messaging-nats-experimental/` | `208077fd` | SDK 없는 seam, 기본 비활성, 조립 없음 |
| `messaging-kafka-share-experimental` leaf | `src/messaging/messaging-kafka-share-experimental/` | `208077fd` | 기본 비활성, 조립 없음 |
| `messaging-spring-cloud-stream-bridge` leaf | `src/messaging/messaging-spring-cloud-stream-bridge/` | `208077fd` | StreamBridge 연동 없는 seam, 조립 없음 |
| `messaging-rabbit` leaf | `src/messaging/messaging-rabbit/` | `208077fd` | production transport가 없어 선택하면 기동 거부되던 상태 |
| `messaging-spring-boot-starter-rabbit` leaf | `src/messaging/messaging-spring-boot-starter-rabbit/` | `208077fd` | 위 rabbit leaf의 조립 모듈 |
| Debezium outbox 매핑 (`DebeziumOutboxEventRouter` 등 4개 + `debezium/outbox-event-router.properties`) | `src/messaging/messaging-outbox-jdbc-postgresql/src/main/java/dev/caskeleton/messaging/outbox/Debezium*.java` | `208077fd` | 조립 없음. `routing_key` 컬럼은 유지 |
| `MessagingSettings.Experimental`·`Bridge` (`app.messaging.experimental.*`, `app.messaging.bridge.*`) | `src/messaging/messaging-spring-boot-starter/src/main/java/dev/caskeleton/messaging/autoconfigure/MessagingSettings.java` | `208077fd` | 바인딩만 되고 읽는 코드 없음 |
| `MessagingProviderSelection`의 rabbit 항목 | `src/messaging/messaging-spring-boot-starter/src/main/java/dev/caskeleton/messaging/autoconfigure/MessagingProviderSelection.java` | `208077fd` | rabbit leaf 삭제에 따름 |
| starter의 `messaging-cloudevents`·`messaging-claim-check` 의존 edge (leaf는 유지) | `src/messaging/messaging-spring-boot-starter/build.gradle, src/config/architecture/modules.json` | `208077fd` | starter main이 두 leaf를 참조하지 않음 |
| RabbitMQ·Pulsar·NATS 개발용 compose | `infra/messaging/{rabbitmq,pulsar,nats}/docker-compose.yml` | `208077fd` | 해당 어댑터 삭제에 따름 |
| Notification R1 타입 96개(`NotificationPort`·`Notification`·`NotificationChannel` 제외)와 테스트 19개 | `src/application-notification/src/{main,test}/java/dev/caskeleton/application/notification/*.java` | `208077fd` | production 소비자 0건. platform이 canonical(NOTIF-ADR-005) |
| ArchUnit 규칙 `NOTIFICATION_R1_AND_PLATFORM_DO_NOT_DEPEND_ON_EACH_OTHER` | `src/app-bootstrap/src/architectureTest/java/dev/caskeleton/bootstrap/architecture/ApplicationBoundaryArchitectureTest.java` | `208077fd` | R1이 없어져 지킬 경계가 없음 |
| Notification Reactor facade와 `reactor-core`·`reactor-test`·`spring-web` 의존 | `src/adapter/outbound/notification/src/main/java/dev/caskeleton/adapter/outbound/notification/platform/reactor/` | `208077fd` | 조립 0건. `spring-web`은 import 0건 |
| `NotificationOrchestrator` | `src/application-notification/src/main/java/dev/caskeleton/application/notification/platform/api/NotificationOrchestrator.java` | `208077fd` | 호출자는 연산별 use case 포트로 이미 분리됨 |
| notification platform `sms`·`push`·`email`·`webpush` facade와 `ApplicationReceiptServiceImpl` | `src/application-notification/src/main/java/dev/caskeleton/application/notification/platform/{sms,push,email,webpush}/`, `.../platform/dispatch/ApplicationReceiptServiceImpl.java` | `208077fd` | 구현·조립 0건 |
| 던지는 곳이 없는 notification 예외 12종 | `src/application-notification/src/main/java/dev/caskeleton/application/notification/platform/api/error/` | `208077fd` | throw 0건 |
| notification redaction 5종(`NotificationRedactor`, `SafeDiagnosticContext`, `SensitiveValueClassifier`, `SensitiveValueKind`, `UnsafeDiagnosticFieldException`) | `src/application-notification/src/main/java/dev/caskeleton/application/notification/platform/security/` | `208077fd` | production 호출 0건 |
| `contract-v1` 테스트 템플릿 4개 | `src/adapter/outbound/notification/src/test/resources/notification/templates/` | `208077fd` | 읽는 테스트 없음 |
| JPA notification crypto 6종과 테스트 | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/notification/crypto/` | `208077fd` | 테스트 외 사용 0건. `ContactPointRoundTripTest`는 application-notification으로 이동 |
| JPA 두 번째 트랜잭션·재시도 엔진 19종(`SpringJpaTransactionExecutor`, `FullTransactionRetryCoordinator`, `CommitFailureClassifier`, `EvidenceAwareJpaTransactionManager`, `CompletionUnknownRecorder` 등), `JpaTransactionAutoConfiguration`, `JpaObservabilityAutoConfiguration`, `JpaRetryObservation`, `api/transaction/*`(`TransactionCompletionEvidence` 제외) | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/{transaction,autoconfigure,observation,api/transaction}/` | `208077fd` | 빈은 있었으나 호출자 0건. 트랜잭션 엔진을 `SpringTransactionPort` 하나로 |
| `VendorFailureTranslator` 빈 2개와 `H2FailureTranslator` | `.../persistence/postgresql/PostgreSqlPersistenceConfig.java`, `.../persistence/h2/` | `208077fd` | 유일한 소비자(위 엔진)가 사라짐 |
| 위 엔진 전용 테스트(`CommitAmbiguityContractTest`, `OptimisticRetryIntegrationTest`, `PostgreSqlVendorFailureTranslatorRegistrationTest` 등) | `src/adapter/outbound/persistence-jpa/src/{test,postgresqlIntegrationTest}/` | `208077fd` | 대상 코드 삭제 |
| `PolicyTransactionPort` 계열(`TransactionRequest`, `TransactionResult`, `TransactionPolicyId`, `TransactionPhase`, `TransactionOutcome`, `ReconciliationReference`, `TransactionAdmissionException`) | `src/application-core/src/main/java/dev/caskeleton/application/transaction/` | `208077fd` | 유일한 호출자(fileserver 보상)를 `TransactionPort.inNew`로 교체 |
| `SpringPolicyTransactionPort`, `TransactionRetryBackoff`, `TransactionRetryClassifier`, 타임아웃 계열(`TransactionDeadlineCalculator`, `TransactionStartBudget`, `EffectiveTransactionTimeouts`, `TransactionLocalTimeoutConfigurer`, `PostgreSqlLocalTimeoutConfigurer`, `H2LocalTimeoutConfigurer`, `JpaTransactionSettings`, `JpaTransactionConfig`)과 `ca-skeleton.jpa.transaction.*` 설정 | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/transaction/`, `src/app-bootstrap/src/main/resources/config/persistence.yml` | `208077fd` | policy 경로 전용. 교체 후 사용처 0건 |
| `FileserverCompensationTransaction` | `src/application-fileserver/src/main/java/dev/caskeleton/application/fileserver/upload/` | `208077fd` | `transactions.inNew(...)` 한 줄로 대체 |
| Mongo reactive 경로(`reactive/**`, reactive transaction/session 6종, `ReactiveExecution`, `applyTo(ReactiveMongoTemplate)`)와 reactive starter·`reactor-test` 의존 | `src/adapter/outbound/persistence-mongo/src/main/java/dev/caskeleton/adapter/outbound/mongo/{reactive,transaction}/` | `208077fd` | 기본 조립에서 exclude되어 도달 불가, 포트 없음 |
| Mongo change stream(`changestream/**`)과 change-stream→messaging bridge(`advanced/bridge/`), 문서 `change-stream-guide.md`·`runbooks/history-lost.md` | `src/adapter/outbound/persistence-mongo/src/main/java/dev/caskeleton/adapter/outbound/mongo/{changestream,advanced/bridge}/`, `docs/mongodb/` | `208077fd` | driver source가 없어 실행 불가 |
| application-core cache 20종(`CacheAsideExecutor`, `CacheAsidePolicy`, `CacheSingleFlight`, `CacheRefresh*`, `CacheObservation*` 등)과 테스트 4개 | `src/application-core/src/main/java/dev/caskeleton/application/cache/` | `208077fd` | 조립·소비자 0건. cache-redis는 `CacheRegionPort` 계열 9종만 사용 |
| `LeaseWatchdog` | `src/application-core/src/main/java/dev/caskeleton/application/lease/` | `208077fd` | main 참조 0건 |
| `TransactionCompletionResolver`, `CompletionResolution` | `src/application-core/src/main/java/dev/caskeleton/application/transaction/` | `208077fd` | 구현체 0건 |
| same-store inbox(`application/inbox/`, `PostgreSqlSameStoreInboxAdapter`, `PostgreSqlInboxIntegrationTest`, `db/migration/jpa/inbox`, readiness card `jpa-inbox-same-store-v1`) | `src/application-core/src/main/java/dev/caskeleton/application/inbox/`, `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/postgresql/inbox/` | `208077fd` | 어떤 조립도 migration 트리를 적용한 적 없음 |
| `EphemeralFanoutPort`, `RedisEphemeralFanoutAdapter` | `src/application-core/src/main/java/dev/caskeleton/application/realtime/`, `src/adapter/outbound/cache-redis/src/main/java/dev/caskeleton/adapter/outbound/cache/redis/realtime/` | `208077fd` | bean·테스트·호출자 0건 |
| PostgreSQL work-claim 실행기(`WorkClaimExecutor`, `PostgreSqlWorkClaimExecutor`, `WorkClaim`, `WorkQueueDefinition`, `WorkQueueName`) | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/postgresql/lock/` | `208077fd` | 호출자 0건 |
| PostgreSQL upsert 실행기 7종 | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/postgresql/write/` | `208077fd` | 호출자 0건 |
| Mongo `ca-skeleton.persistence-mongo.advanced.<capability>.enabled` 바인딩(`MongoAdvancedConfiguration`, `MongoAdvancedSettings`)과 `MongoAdvancedCapabilityFlags.PROPERTY_PREFIX`·`propertyFor` | `src/adapter/outbound/persistence-mongo/src/main/java/dev/caskeleton/adapter/outbound/mongo/advanced/autoconfigure/`, `src/adapter/outbound/persistence-mongo/src/main/java/dev/caskeleton/adapter/outbound/mongo/advanced/MongoAdvancedCapabilityFlags.java` | `208077fd` | import하는 main 코드 0건이라 어떤 배포 property도 flag에 닿지 않음. flag는 진입점을 만드는 어댑터 코드가 직접 만든다 |
| Mongo search·vector(`advanced/search/` 5종, `advanced/vector/` 5종, `MongoSearchReadinessGate`·`MongoVectorSearchBenchmarkGate` 포함), 문서 `docs/mongodb/advanced/search-vector.md` | `src/adapter/outbound/persistence-mongo/src/main/java/dev/caskeleton/adapter/outbound/mongo/advanced/{search,vector}/` | `208077fd` | `MongoSearchOperations`·`MongoVectorSearchOperations` 구현체 0건. 나머지는 그 인터페이스의 인자와 main에 둔 gate |
| Mongo time series(`advanced/timeseries/` 6종), 문서 `docs/mongodb/advanced/time-series.md` | `src/adapter/outbound/persistence-mongo/src/main/java/dev/caskeleton/adapter/outbound/mongo/advanced/timeseries/` | `208077fd` | `MongoTimeSeriesOperations` 구현체 0건. 나머지는 descriptor와 모든 항목이 unsupported인 표 |
| Mongo GridFS 호환(`advanced/gridfs/` 4종), 문서 `docs/mongodb/advanced/gridfs-migration.md` | `src/adapter/outbound/persistence-mongo/src/main/java/dev/caskeleton/adapter/outbound/mongo/advanced/gridfs/` | `208077fd` | `MongoGridFsCompatibilityReader` 구현체 0건이라 `MongoGridFsMigrationJob`을 실행할 수 없음 |
| `MongoDataKeyResolver`, `MongoTenantDatabaseResolver`, `TenantScopedMongoOperations` | `src/adapter/outbound/persistence-mongo/src/main/java/dev/caskeleton/adapter/outbound/mongo/advanced/{encryption/csfle,tenancy/database,tenancy/shared}/` | `208077fd` | 구현체·호출자 0건 |
| `MongoAdvancedPromotionGate`, `MongoAdvancedPromotionEvidence` | `src/adapter/outbound/persistence-mongo/src/main/java/dev/caskeleton/adapter/outbound/mongo/advanced/` | `208077fd` | production classpath의 promotion gate, 자기 테스트 외 호출자 0건. 증거 항목은 ADR-MONGO-ADV-001의 리뷰 의무로 남김 |
| testFixtures `MongoAtlasCapabilityContractSuite`, provider testkit `MongoAtlasLocalContainer`, release contract `MONGO-REL-011` | `src/adapter/outbound/persistence-mongo/src/{testFixtures,mongoProviderTestkit}/java/dev/caskeleton/adapter/outbound/mongo/testkit/atlas/`, `src/config/mongodb/release-contracts.json` | `208077fd` | 위 promotion gate 테스트만 사용. 등록된 lane 없음 |
| `MongoIdRepresentation`, `MongoBulkPartialFailureException` | `src/adapter/outbound/persistence-mongo/src/main/java/dev/caskeleton/adapter/outbound/mongo/api/mapping/`, `src/adapter/outbound/persistence-mongo/src/main/java/dev/caskeleton/adapter/outbound/mongo/api/error/` | `208077fd` | 참조 0건. 문서는 "`_id` 표현을 정한다", "부분 실패를 알린다"고 했지만 쓰거나 던지는 코드가 없음 |
| Mongo `platform.change-streams` 키(`MongoPlatformSettings.changeStreams`, `MongoStartupValidator`의 change stream 검사) | `src/adapter/outbound/persistence-mongo/src/main/java/dev/caskeleton/adapter/outbound/mongo/autoconfigure/` | `208077fd` | 켜면 기동 실패만 하는 키. change stream 기능은 이미 삭제됨 |
| Mongo profile 키 `consistency-default`, `decimal-representation`, `runtime-auto-create-indexes` | `src/adapter/outbound/persistence-mongo/src/main/java/dev/caskeleton/adapter/outbound/mongo/autoconfigure/MongoProfileProperties.java`, `src/app-bootstrap/src/main/resources/config/persistence.yml`(주석 예시), `docs/mongo/persistence-profile.example.yml` | `208077fd` | 검증만 하고 읽는 코드 0건. decimal은 허용 값이 `DECIMAL128` 하나, auto-index는 Spring Data 설정에 연결되지 않음 |
| 위 대상 전용 테스트 5개 클래스(36개)와 테스트 메서드 2개 | `src/adapter/outbound/persistence-mongo/src/test/java/dev/caskeleton/adapter/outbound/mongo/advanced/{autoconfigure,search,timeseries,gridfs}/`, `.../advanced/MongoAdvancedPromotionGateTest.java`, `MongoPlatformSettingsTest.productionRefusesRuntimeIndexCreation`, `MongoStartupValidationTest.changeStreamsCannotBeSwitchedOn` | `208077fd` | 대상 코드 삭제. guard 거부 검증은 `MongoAdvancedCapabilityGuardTest`로 옮김 |
| redis-sdk 진입 인터페이스 `RedisOperations`·`ReactiveRedisOperations` | `src/adapter/outbound/redis-sdk/src/main/java/dev/caskeleton/adapter/outbound/cache/redis/sdk/api/` | `208077fd` | 구현체 없음 |
| redis-sdk `ExpirationUpdatePolicy` | `src/adapter/outbound/redis-sdk/src/main/java/dev/caskeleton/adapter/outbound/cache/redis/sdk/api/operations/` | `208077fd` | 호출자 없음 |
| redis-sdk `RedisCommandMetadataDiff`·`RedisServerCommandMetadata`와 테스트 | `src/adapter/outbound/redis-sdk/src/main/java/dev/caskeleton/adapter/outbound/cache/redis/sdk/lettuce/command/` | `208077fd` | main에 둔 gate, 연결된 build 검사 없음(테스트에서만 사용) |
| redis-sdk `RedisConnectionRegistry`·`RedisConnectionLease`와 테스트 | `src/adapter/outbound/redis-sdk/src/main/java/dev/caskeleton/adapter/outbound/cache/redis/sdk/lettuce/connection/` | `208077fd` | 테스트에서만 사용. lane 한도는 redis-runtime `RedisRuntimeOwner`가 소유 |
| `app.redis.limits.*`·`advanced.*`·`raw.*`·`timeout.collection`·`timeout.admin`·`blocking.max-block`·`lifecycle.tls-handshake-timeout`·`capacity.maximum-in-flight-bytes`·`capacity.maximum-reply-bytes`·`pubsub.overflow-policy`, env key 23개, `RedisCredentialRole.RAW` | `src/adapter/outbound/redis-runtime/src/main/java/dev/caskeleton/adapter/outbound/cache/redis/sdk/config/RedisSdkSettings.java`, `RedisSdkAutoConfiguration.java` | `208077fd` | 검증만 하고 읽는 코드 없음. `raw.*`는 어떤 lane도 쓰지 않는 RAW 계정 클라이언트를 만들고 allowlist 파일은 존재만 확인. SDK 한도·advanced 정책·raw 승인은 코드(`RedisOperationLimits`, `ConfiguredRedisPolicyAuthority`, `RawCommandApprovals`)로 준다 |
| application-core outbox V2 포트·유스케이스 17종(`NewOutboxEventV2`, `OutboxAppendPortV2`, `OutboxPollingDeliveryPortV2`, `PublishNextOutboxDeliveryUseCase`, `OutboxV2RetryPolicy`, `OutboxPublicationAuthority` 등)과 계약 테스트 2개 | `src/application-core/src/{main,test}/java/dev/caskeleton/application/outbox/v2/` | `208077fd` | 어떤 조립도 만들지 않은 세대(D2). v1 relay 한 세대만 남기고 owner/token fencing은 v1로 이식 |
| JPA outbox V2 adapter(`PostgreSqlImmutableOutboxAppendAdapter`, `PostgreSqlPollingDeliveryAdapter`, `CanonicalOutboxEventRowMapper`)와 단위 테스트(`PostgreSqlOutboxTransitionDigestTest`, `OutboxStorageMigrationSafetyTest`) | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/postgresql/outbox/`, `.../src/test/java/.../persistence/{postgresql/outbox,migration}/` | `208077fd` | 빈 등록 0건, 위 V2 포트 전용 |
| outbox V2 migration stream `jpa/outbox-storage`(V1·V2), `jpa/outbox-polling`(V1·V2)과 `applied-migrations.sha256`의 해당 4줄 | `src/adapter/outbound/persistence-jpa/src/main/resources/db/migration/jpa/{outbox-storage,outbox-polling}/` | `208077fd` | 어떤 composition도 Flyway location으로 설정한 적 없음 |
| outbox V2 PostgreSQL 통합 테스트(`PostgreSqlOutboxStorageIntegrationTest`, `PostgreSqlOutboxPollingIntegrationTest`, `CanonicalOutboxV2TestFixture`, `LegacyOutboxDrainContractTest`), lane `postgresqlOutboxStorageIntegrationTest`·`postgresqlOutboxPollingIntegrationTest`, `PostgreSqlOptionalStreamLifecycle.outboxStorage()/outboxPolling()` | `src/adapter/outbound/persistence-jpa/src/postgresqlIntegrationTest/java/dev/caskeleton/adapter/outbound/persistence/readiness/`, `src/build-logic/src/main/java/dev/caskeleton/buildlogic/jpa/JpaTestLanesPlugin.java` | `208077fd` | 대상 코드 삭제. CI에 걸린 lane 없음 |
| readiness card `jpa-outbox-storage-v2`, `jpa-outbox-polling-delivery-v2`, `jpa-outbox-cdc-retention-v1`(storage-v2 전제)과 polling/CDC 동시 선택 금지 규칙 | `src/config/jpa/readiness-cards.yaml`, `src/build-tools/src/main/java/dev/caskeleton/buildtools/jpa/JpaReadinessRegistryValidator.java` | `208077fd` | 대상 stream·adapter 삭제 |
| web Advanced release gate (`WebAdvancedPromotionGate`, `WebAdvancedReleaseManifest`)와 기능 카탈로그 `WebAdvancedFeature`, 테스트 `WebAdvancedReleaseTest`·`WebAdvancedRollbackIT`의 gate 테스트 2개 | `W/advanced/release/`, `W/advanced/WebAdvancedFeature.java`, `src/adapter/inbound/web/src/test/java/dev/caskeleton/adapter/inbound/web/advanced/release/` | `208077fd` | main에 둔 승격 gate, 테스트에서만 호출. 카탈로그는 읽는 코드 없는 설정 키(`…json-merge-patch.enabled`, `…sse.enabled`, `…cbor.enabled` 등)를 문서에 약속 |
| OpenAPI 3.2 승격 리포트 (`OpenApi32CompatibilityReport`, `OpenApiToolchainMatrix`)와 테스트 5개 | `W/advanced/openapi/`, `src/adapter/inbound/web/src/test/java/dev/caskeleton/adapter/inbound/web/advanced/openapi/OpenApi32CompatibilityReportTest.java` | `208077fd` | main에 둔 승격 gate, 테스트에서만 호출. `OpenApiVersionLane` 테스트 1개는 `OpenApiVersionLaneTest`로 남김 |
| blocking bridge 예산 (`BlockingBridgeBudget`, `BlockingBridgeProfile`, `BlockingBridgeRejectedException`)과 테스트 | `W/advanced/blockingbridge/`, `src/adapter/inbound/web/src/test/java/dev/caskeleton/adapter/inbound/web/advanced/blockingbridge/` | `208077fd` | 예산을 거는 WebFlux bridge 어댑터가 이미 삭제됨(D4) |
| 호출자 0 타입: `SpringMvcRouteInventoryCollector`, `WebPartialResponseException`, `WebBudgetMeter`(+ `WebBudgetOutcome`·`WebBudgetExceededException`·`WebBudgetViolation`), `WebStatusContract`, `WebJsonDecodingException` | `W/admin/route/`, `W/advanced/stream/`, `W/budget/`, `W/http/`, `W/json/` | `208077fd` | main·테스트 어디서도 참조 없음 |
| 쓰지 않는 테스트 대역 `InMemoryIdempotencyStore` | `src/adapter/inbound/web/src/test/java/dev/caskeleton/adapter/inbound/web/idempotency/` | `208077fd` | 참조 0 |
| websocket Advanced 전체(resume, cluster, presence, CBOR·Protobuf codec, compression, 외부 client, GraphQL bridge, HTTP/2·3 profile, SockJS profile·`SockJsConfiguration`, `AdvancedPromotionGate`, `WebSocketAdvancedCapability`)와 테스트 16개, lane `websocketAdvancedTest`, `compileOnly` CBOR·protobuf 의존, `application-core` 의존 | `WS/advanced/`, `WST/advanced/`, `src/adapter/inbound/websocket/build.gradle` | `208077fd` | 어떤 Spring 설정도 import하지 않음(`AutoConfiguration.imports` 없음, bootstrap scan 밖). `SockJsConfiguration`은 켜면 조립되지 않는 platform bean 3개를 요구. `application-core` edge는 이 코드만 사용 |
| `app.websocket.platform.*` 설정(`WebSocketPlatformSettings`, `WebSocketPlatformSafetyConfiguration`, `WebSocketPlatformStartupValidator`, `WebSocketStackExclusivity`)과 env key 15개(`APP_WEBSOCKET_PLATFORM_*` 14개, `APP_WEBSOCKET_ADVANCED_SOCKJS_ENABLED`) | `WS/config/`, `docs/registries/env-keys.yaml`, `src/.env.example` | `208077fd` | 바인딩하는 코드 없음(`@EnableConfigurationProperties` 없음). safety config는 import하는 곳이 없고, 켜면 아무도 만들지 않는 catalog bean 6개를 요구해 기동 실패 |
| platform catalog·정책 패키지 `admin`, `authz`, `codec`, `handler`, `handshake`, `lifecycle`, `observability`, `ordering`, `security`, `session`, `protocol`(`WebSocketMessageId` 제외), `core`(`WebSocketConnectionId`와 idempotency가 쓰는 2개 제외)와 테스트 | `WS/{admin,authz,codec,handler,handshake,lifecycle,observability,ordering,security,session,protocol,core}/`, `WST/` 같은 패키지 | `208077fd` | 테스트에서만 사용. `PlatformWebSocketHandler`도 쓰지 않음. `HandshakeAdmissionPipeline`은 bearer/cookie를 헤더 존재만으로 통과시켰고(2026-09-24 모듈 리뷰 K#1), `WebSocketSessionRegistry`는 연결 수 상한 경쟁 조건이 있었음(K#7) |
| reactive runtime `webflux/`(`ReactiveFrameSink`, `WebSocketDataBufferLifecycle`, `WebSocketDataBufferPolicy`)와 `spring-webflux`·`reactor-core` 의존 | `WS/webflux/`, `WST/webflux/` | `208077fd` | 템플릿은 servlet 전용(D4). 호출자 없음. sink 버퍼가 무제한이라 budget이 동작하지 않았음(K#3) |
| `inbound/FragmentAssembler`, close-code catalog `error/`, `WebSocketConnectionBudget`의 `maxFrameBytes`·`maxFragments`·`maxInboundMessagesPerSecond`·`maxConnectionAge`·`idleTimeout` | `WS/{inbound,error}/`, `WS/budget/WebSocketConnectionBudget.java` | `208077fd` | servlet handler는 whole-message 모드라 frame·fragment를 볼 수 없어 frame/fragment 상한이 동작하지 않았음(K#2). 나머지 3개는 읽는 코드 없음. 수신 상한은 `maxMessageBytes`(UTF-8 바이트) 하나, idle timeout은 컨테이너 설정. close는 Spring `CloseStatus`(1001/1009/1013) 직접 사용 |
| testFixtures `WebSocketArchitectureRules`(WS-ARCH-1~6)와 `WebSocketArchitectureRulesTest`, ArchUnit test 의존 | `src/adapter/inbound/websocket/src/testFixtures/java/dev/caskeleton/adapter/inbound/websocket/testkit/arch/`, `WST/arch/` | `208077fd` | 규칙 대상 패키지(`handler`, `webflux`, `advanced`)가 삭제됨. 남는 WS-ARCH-4(persistence 금지)는 registry 의존 게이트가 이미 막음 |
| 문서 `docs/websocket/advanced-support-matrix.md`, `docs/websocket/repository-adaptation.md`, `docs/websocket/runbooks/resume-history-loss.md` | `docs/websocket/` | `208077fd` | 삭제한 코드와 존재하지 않는 `…advanced.*.enabled` 플래그를 설명 |
| messaging adapter `realtime/` (`MessagingDurableFanoutAdapter`, `RealtimeFanoutEnvelopeJson`) | `src/adapter/outbound/messaging/src/main/java/dev/caskeleton/adapter/outbound/messaging/realtime/` | `208077fd` | bean 없음. `DurableFanoutPort`는 websocket이 쓰므로 유지 |
| `app.jpa-platform.addons-enabled` 조건(`PersistenceJpaRuntimeConfig`, bootstrap `JpaPlatformRuntimeAutoConfiguration`)과 그 스위치 테스트 2개 | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/autoconfigure/PersistenceJpaRuntimeConfig.java`, `src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/autoconfigure/jpa/JpaPlatformRuntimeAutoConfiguration.java` | `208077fd` | 어떤 property source·env 키도 설정하지 않음(테스트만 false로 설정). JPA 마스터 스위치 `ca-skeleton.persistence-jpa.enabled` 하나로 켜고 끈다 |
| `backend.jpa.experimental.*` 플래그 8개(`ExperimentalFeature`, `ExperimentalFeatureGate`, 진입점 3개의 `enabledBy(..)` 팩토리)와 `ExperimentalEntryConsentTest` | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/experimental/` | `208077fd` | 설정에서 플래그를 읽는 코드 0건. gate는 호출자가 직접 만든 Map만 검사했고 "기동 실패" 문서 약속은 거짓. 진입점은 public 생성자로 직접 만든다 |
| `experimental/next/*`(`CompatibilityLane`, `ExperimentalPromotionGate`, `PromotionDecision`, `PromotionEvidence`, `HibernateCompatibilityPolicy`)와 테스트 `CompatibilityLaneDefinitionTest`·`ExperimentalPromotionGateTest`·`HibernateCompatibilityPolicyTest` | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/experimental/next/` | `208077fd` | main에 둔 promotion/lane gate, 자기 테스트 외 호출자 0건. `HibernateProviderPolicy` 검증은 `HibernateProviderPolicyTest`로, 버전 canary는 `Jpa4/Hibernate8/PostgreSql19CompatibilityTest`로 남김(`jpa-next.yml`이 실행) |
| `TenantEntityManagerFactoryRegistry`, `RlsAdminBypassToken`, `TenantEntityListenerGuard` | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/experimental/{database,rls,tenant}/` | `208077fd` | 테스트·호출자 0건 |
| `JpaTransactionObservation`(`jpa.transaction.*` meter)와 테스트 메서드 2개 | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/observation/JpaTransactionObservation.java` | `208077fd` | 생성하는 곳 0건이라 문서의 transaction metric은 나온 적 없음. `docs/jpa/observability.md` 정정 |
| 단일 구현 인터페이스 `JpaBatchExecutor`, `BulkDmlExecutor`, `StatelessSessionRunner`, `PostgreSqlCopyLoader`, `EnversHistoryReader`, `CursorCodec`, `VendorFailureTranslator`, `SqlStateResolver`, `ConstraintCatalog` | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/{hibernate/batch,hibernate/bulk,hibernate/stateless,postgresql/copy,envers,api/query,api/error,postgresql/error}/` | `208077fd` | 구현 1개, 인터페이스를 참조하는 테스트·외부 코드 0건. 테스트된 구현(`HibernateJpaBatchExecutor` 등)을 진입점으로 남김 |
| 구현 없는 인터페이스 `EntityManagerAccess`, `LockWaitObservation` | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/springdata/`, `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/postgresql/lock/` | `208077fd` | 구현·호출자 0건 |
| `JpaBatchProfileRegistry`, `SpecificationPolicy`, `QuerydslJpaSupport`, `PgRangeJdbcType`, `PostgreSqlRangeQuerySupport`, `FailedConcurrentIndexRecovery`, `NonTransactionalMigrationPolicy`, `SchemaVersionSnapshot` | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/{hibernate/batch,springdata,querydsl,postgresql/range,migration}/` | `208077fd` | 테스트·호출자 0건. invalid index 확인은 `docs/jpa/runbooks.md`의 SQL로 대체 |
| `FlywayValidationGate`, `ConcurrentIndexMigrationInspector`, `MigrationResource`(main에서 testkit으로 이동, 삭제 아님) | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/migration/` → `src/adapter/outbound/persistence-jpa/src/testFixtures/java/dev/caskeleton/adapter/outbound/persistence/testkit/migration/` | `208077fd` | 테스트·testkit에서만 쓰는 gate. 기동 검증은 Flyway validate-on-migrate와 `ddl-auto=validate`가 한다 |
| `JpaCapability.TRANSACTION_RETRY`·`POSTGRESQL_NATIVE_WRITE`·`POSTGRESQL_WORK_CLAIM`과 `jpaplatform` actuator 보고 항목 | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/api/capability/JpaCapability.java`, `src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/autoconfigure/jpa/JpaPlatformAutoConfiguration.java` | `208077fd` | 해당 코드(재시도 엔진, upsert·work-claim 실행기)가 이미 삭제됐는데 보고서는 Stable/Advanced로 광고함 |
| web Advanced functional routes (`FunctionalRouteRegistry`, `WebFunctionalHandlerAdapter` 외)와 테스트, web-advanced의 `spring-webflux` 의존 | `W/advanced/functional/`, `src/adapter/inbound/web/src/test/java/dev/caskeleton/adapter/inbound/web/advanced/functional/` (W3-2에서 `adapter:inbound:web-advanced`로 옮긴 뒤 삭제) | `208077fd` | D4: WebFlux `RouterFunction`을 만든다. servlet 전용 템플릿에서 서빙할 곳이 없음 |
| forwarded header 라이브러리 (`ForwardedHeaderSanitizer`, `TrustedProxyPolicy`, `NormalizedForwardedHeaders`, `UntrustedForwardedHeaderException`)와 외부 URI (`ExternalOrigin`, `ExternalPrefix`, `ExternalUriBuilder`, `ExternalUriPolicy`), 테스트 | `W/proxy/`, `W/http/External*.java` (W3-2에서 web-advanced로 옮긴 뒤 삭제) | `208077fd` | 한 기능에 한 세대: 운영은 `server.forward-headers-strategy`(`app-bootstrap/.../config/server.yml`) |
| Nginx proxy lane `webNginxProxyTest`와 CI job (`pr-adapters.yml` → `web-nginx-proxy-contract`, `release.yml`) | `src/adapter/inbound/web/src/nginxProxyTest/` | `208077fd` | 위 forwarded header 라이브러리만 인증하던 lane |
| CORS/CSRF 프로필 (`CorsProfile`, `CsrfProfile`, `WebCorsPolicyValidator`, `WebCredentialMode`, `WebCsrfPolicyResolver`)과 테스트 | `W/security/` 의 해당 5개 파일 (W3-2에서 web-advanced로 옮긴 뒤 삭제) | `208077fd` | 한 기능에 한 세대: 운영은 `CorsSettings` + `SecurityConfig`. 같은 패키지의 security-context bridge는 유지 |
| cache 정책 카탈로그 (`WebCachePolicyCatalog`, `WebCachePolicy`, `WebVaryPolicy`, `WebCacheHeaders`)와 테스트 | `W/cache/` (W3-2에서 web-advanced로 옮긴 뒤 삭제) | `208077fd` | 한 기능에 한 세대: 운영은 `CacheControlFilter` |
| JSON mapper factory (`WebObjectMapperFactory`, `WebJsonProfile`, `BoundedJsonFactory`)와 테스트 | `W/json/` (W3-2에서 web-advanced로 옮긴 뒤 삭제) | `208077fd` | 한 기능에 한 세대: 운영은 Boot `JsonMapper` + `spring.jackson.*`. 스트리밍 encoder는 Boot `JsonMapper` bean을 받도록 변경 |
| OpenAPI customizer (`WebOpenApiCustomizer`, `WebOpenApiProfile`, `CursorSchemaContributor`)와 `WebOpenApiSnapshotTest` | `W/openapi/` 의 해당 3개 파일 (W3-2에서 web-advanced로 옮긴 뒤 삭제) | `208077fd` | 한 기능에 한 세대: 운영은 springdoc + `OpenApiContractConfig`. `CursorPage` 스키마는 이미 삭제된 커서 페이지네이션을 설명 |
| realtime 포트 (`ConnectionRegistryPort`, `DurableFanoutPort` 외 7개 타입)와 Redis 연결 레지스트리 (`RedisConnectionRegistryAdapter`) | `src/application-core/src/main/java/dev/caskeleton/application/realtime/`, `src/adapter/outbound/cache-redis/src/main/java/dev/caskeleton/adapter/outbound/cache/redis/realtime/` | `208077fd` | 소비자 0 (websocket 정리 후 호출자 없음, bean 없음). `LiveEventReplayPort` 계열은 유지 |
| graphql `advanced/**` 전체 (15개 패키지, 130개, ~5,600줄) + 테스트 | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/advanced/` | `208077fd` | 모든 진입점이 `GraphQlAdvancedModuleGuard`를 거치는데 그 플래그(`GraphQlAdvancedFeatureFlags`)를 바인딩하는 코드가 없다. Spring GraphQL/graphql-java SPI를 구현한 타입이 없어 SSE·RSocket·federation·incremental·GET·chaining은 이름만 있는 모델. `GraphQlReplaySource`·`GraphQlPersistedOperationAdminPort`는 구현체 없는 인터페이스, persisted 레지스트리가 기대는 `OperationalRecordStorePort`도 구현체 0. composition/incremental/bootstrap은 gate·등급 코드 |
| `backend.graphql.unsupported.*` 6개 키 (`GraphQlPlatformSettings.Unsupported`, `withUnsupportedCapability`, 검증기 분기) | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/autoconfigure/GraphQlPlatformSettings.java`, `GraphQlPlatformStartupValidator.java` | `208077fd` | 켜면 부팅 실패만 한다. 구현하지 않은 기능에는 설정 키를 두지 않는다(AGENTS 기준 3) |
| `backend.graphql.cursor.key-ids` (`GraphQlPlatformSettings.Cursor`, `withCursorKeyIds`) | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/autoconfigure/GraphQlPlatformSettings.java` | `208077fd` | 읽는 곳이 등록되지 않은 actuator 보고서뿐. 커서 서명은 라이브러리(`HmacGraphQlCursorCodec`)를 서비스가 직접 조립한다 |
| `GraphQlPlatformActuatorEndpoint`, `GraphQlPlatformConfigurationReport` | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/autoconfigure/` | `208077fd` | 빈으로 등록하는 곳이 없어 노출되지 않는 endpoint. 테스트만 호출 |
| `GraphQlClientPolicy`의 `persistedOperationOnly`·`maxResponseNodes`·`maxResponseBytes` | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/policy/GraphQlClientPolicy.java` | `208077fd` | 아무도 읽지 않는 필드. `persistedOperationOnly=true`는 허용 목록 우회(fail-open)였다 |
| `GraphQlRequestErrorMapper`, `GraphQlSubscriptionExceptionResolver`, `GraphQlNullabilityContract`, `GraphQlFailureBoundary` | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/error/` | `208077fd` | main 참조 0 |
| `GraphQlWireErrorMapper.mapRequestRejection` | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/runtime/GraphQlWireErrorMapper.java` | `208077fd` | 호출처 0. 요청 단계는 `GraphQlPlatformRejectionMapper.map`을 직접 쓴다(Javadoc에 사실대로 적음) |
| parser 한도(`GraphQlParserLimitPolicy`, `GraphQlParserLimits`, `GraphQlParserOptionsFactory`, `GraphQlParserRejectedException`) | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/cost/` | `208077fd` | auto-configuration이 parser 기본값을 바꾸지 않는다. 테스트만 호출 |
| 응답 runtime budget(`GraphQlRuntimeBudgetTracker`, `GraphQlRuntimeBudget`, `GraphQlResponseByteLimiter`, `GraphQlResponseNodeCounter`, `GraphQlRuntimeBudgetExceededException`) | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/cost/` | `208077fd` | 유일한 소비자가 `advanced/incremental`. 요청 경로에 없음 |
| `GraphQlCancellation`, `GraphQlDeadlinePropagator`, `GraphQlResolverBudget`, `GraphQlOperationNameInterceptor`, `GraphQlOperationNamePolicy`, `GraphQlResolverCatalog`, `GraphQlResolverDescriptor`, `GraphQlExecutionProfileValidator` | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/execution/` | `208077fd` | 등록·호출하는 곳이 없는 interceptor·검증기·신호. 익명 operation 거부는 `GraphQlOperationSelectionHandler`가 이미 한다 |
| `GraphQlClientPolicyManifest`, `GraphQlOperationCatalog`, `GraphQlOperationPolicy`, `GraphQlPolicyViolation`, `GraphQlUnknownClientProfileException`, `GraphQlUnknownOperationException`, `ResolverExecutionType`, `api/GraphQlClientProfileName` | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/policy/`, `api/` | `208077fd` | 요청 경로가 참조하지 않는 카탈로그·manifest. 테스트만 호출 |
| schema gate·병렬 조립기(`GraphQlMappingInspectionGate`, `GraphQlOneOf*` 4개, `GraphQlSchemaAssembler`/`AssemblyResult`/`AssemblyException`, `GraphQlSchemaContract`, `GraphQlSchemaHash` 등 14개) | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/schema/` | `208077fd` | 스키마 조립·mapping inspection·`@oneOf` 검증은 Spring GraphQL/graphql-java가 한다. 이 gate들은 어디에도 등록되지 않았다 |
| 병렬 HTTP 전송 모델(`GraphQlHttpExecutor`, `GraphQlHttpResponseFactory`, `GraphQlHttpStatusMapper`, `GraphQlMediaTypes`, `GraphQlAcceptHeader`, `GraphQlHttpProfile` 등 9개) | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/http/` | `208077fd` | HTTP 처리는 Spring GraphQL handler가 한다. `GraphQlHttpExecutor`는 구현체 없는 인터페이스 |
| `GraphQlClientProfileResolver`, `GraphQlContextCleanup`, `GraphQlProfilerAccessPolicy` | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/security/`, `observation/` | `208077fd` | 등록·호출하는 곳 없음 |
| testFixtures testkit(계약 suite 5개, JPA/Mongo 통합 fixture, `GraphQlStorageIntegrationEvidence`, `GraphQlPartialResponseFixture`)와 `GraphQlCrossModuleContractSuiteTest` | `src/adapter/inbound/graphql/src/testFixtures/java/dev/caskeleton/adapter/inbound/graphql/testkit/` | `208077fd` | 삭제한 병렬 HTTP 모델 위에서 자기 자신만 검사하던 증거 코드. 다른 모듈이 testFixtures를 쓰지 않는다. `GraphQlRequestContexts`만 남김 |
| 요청 멱등성 v1 모델 (`IdempotencyExecutor`(v1), `IdempotencyStorePort`(v1), `IdempotencyScope`, `IdempotencyContext`, `IdempotencyRecord`, `IdempotencyStatus`, `IdempotencyScopeMissingException`, `Sleeper`)와 `IdempotencyScopeTest`, `IdempotencyV2ContractSingularityTest` | `src/application-core/src/main/java/dev/caskeleton/application/idempotency/` | `208077fd` | W2-6 한 세대: V2(owner-safe store, scope digest, 대기 없는 경합 처리)가 정본. V2 타입은 `v2` 패키지에서 상위 패키지로 옮기고 `V2` 접미사를 뗐다(`IdempotencyExecutorV2`→`IdempotencyExecutor`, `IdempotencyStorePortV2`→`IdempotencyStorePort`) |
| JPA v1 멱등성 store (`IdempotencyStoreAdapter`, `IdempotencyClaimRepository`, `IdempotencyResponseObjectStore`, `mapper/IdempotencyRecordEntityMapper`, `postgresql/PostgreSqlIdempotencyClaimRepository`, `h2/H2IdempotencyClaimRepository`)와 `IdempotencyStoreAdapterTest`, `PostgreSqlIdempotencyUniqueScopeIntegrationTest`, lane `postgresqlIdempotencyUniqueScopeIntegrationTest` | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/` (`idempotency/`, `postgresql/`, `h2/`) | `208077fd` | W2-6: v1 `jdbc` provider 구현. `postgresql` provider는 `PostgreSqlOwnerSafeIdempotencyStore`. unique-scope lane은 v1 제약 `uq_idempotency_scope`만 확인했다(마이그레이션 파일은 그대로) |
| bootstrap 멱등성 조립 (`IdempotencyConfig`, `IdempotencyComposition`, `PostgreSqlIdempotencyProviderConfig`, `IdempotencyProviderSettings`, `config/idempotency.yml`)와 `IdempotencyProviderSettingsTest`, `IdempotencyShippedAutoConfigurationTest`, `IdempotencyProviderScanCollisionTest` | `src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/autoconfigure/idempotency/` | `208077fd` | W2-6: executor를 여러 곳에서 만들고 lease/codec을 하드코딩했다. 이제 `IdempotencyProviderSelectionConfig`가 `IdempotencySettings` 하나로 한 번 만든다. 테스트는 `IdempotencyProviderCompositionTest`로 합침 |
| sample v1 멱등성 설정 (`SampleIdempotencySettings`) | `src/sample-portfolio/src/main/java/dev/caskeleton/sample/portfolio/bootstrap/idempotency/` | `208077fd` | W2-6: v1 `ca-skeleton.idempotency.ttl` 바인딩. `SampleIdempotencyConfig`가 `ca-skeleton.capabilities.idempotency`를 직접 읽는다 |
| websocket command ledger (`idempotency/CommandReconciliation`, `CommittedResultLedger`, `WebSocketCommandKey`, `WebSocketCommandOutcome`, `core/WebSocketActorReference`, `core/WebSocketEndpointName`, testFixtures `testkit/fault/WebSocketFaultInjector`, `WebSocketFaultPoint`)와 `InMemoryCommittedResultLedger`, `WebSocketCommandIdempotencyTest`, `CommandLossRecoveryTest` | `src/adapter/inbound/websocket/src/` | `208077fd` | W2-6: v1 executor 전용 ledger. `core/` 두 타입은 ledger 삭제 뒤 참조가 없다. 멱등성이 필요하면 use case 안에서 `IdempotencyExecutor`를 쓴다 |
| GraphQL mutation 멱등성 (`GraphQlMutationIdempotencyInterceptor`, `GraphQlMutationIdempotencyContext`, `GraphQlIdempotencyKey`, `GraphQlIdempotencyConflictException`, `GraphQlCanonicalInput`, `GraphQlMutationFingerprint`, `GraphQlExtensionsPolicy`의 `idempotencyKey` 허용, `GraphQlMutationContractValidator.requireIdempotency`)와 `GraphQlMutationIdempotencyContextTest` | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/` (`mutation/`, `http/`) | `208077fd` | W2-6: store에 연결된 적 없는 v1 executor 사용처. `idempotencyKey` extension은 이제 거부된다 |
| web v1 멱등성 fake (test `idempotency/InMemoryIdempotencyStore`, testFixtures `testkit/fault/FaultFixtureStore`) | `src/adapter/inbound/web/src/` | `208077fd` | W2-6: application-core testFixtures `testkit/InMemoryIdempotencyStore` 하나로 대체 |
| Import filters `MongoOptInAutoConfigurationImportFilter`, `GraphQlOffAutoConfigurationImportFilter`, `MessagingOffAutoConfigurationImportFilter` (+ `MessagingOffAutoConfigurationImportFilterParityTest`) and their `spring.factories` entries | `src/adapter/outbound/persistence-mongo/src/main/java/dev/caskeleton/adapter/outbound/mongo/`, `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/autoconfigure/`, `src/adapter/outbound/messaging/src/main/java/dev/caskeleton/adapter/outbound/messaging/autoconfigure/` | `208077fd` | W4-4: off machinery for a jar shipped switched off. A capability is now absent unless selected; an explicit `enabled=false` excludes Boot's Mongo/GraphQL auto-configuration from the module's own environment post-processor |
| bootstrap capability settings `config/messaging.yml`, `config/graphql.yml`, `config/httpclient.yml`, `config/fileserver.yml`, the Mongo block of `config/persistence.yml`, `spring.servlet.multipart` in `application.yml`, `app.messaging.broker` in `application-local.yml` | `src/app-bootstrap/src/main/resources/` | `208077fd` | W4-4: moved into the owning modules (`config/<capability>.yml`, loaded at lowest precedence by each module) |
| RabbitMQ broker settings (`BrokerSettings` `addresses`/`publisher-confirms`/`publisher-returns`/`mandatory`/`confirm-timeout`/`auto-ack`/`prefetch`/`quorum-queues`, `BrokerSettings.RABBITMQ`, the compiler and key-validator Rabbit branches) and the RabbitMQ YAML example | `src/messaging/messaging-spring-boot-starter/src/main/java/dev/caskeleton/messaging/autoconfigure/`, `docs/messaging/configuration-reference.md` | `208077fd` | W4-4 (criterion 3): the keys bound with no transport behind them; `type: rabbitmq` and Rabbit keys now fail startup naming the key |
| bootstrap tests for shipped-and-switched-off capabilities: `MongoShippedCompositionContractTest` (moved to the Mongo leaf as `MongoReactiveDriverAbsenceTest`), `MessagingMembershipQualificationTest`, systemTest `GraphQlShippedAndGatedTest`; the Mongo/GraphQL/messaging cases of `ShippedRuntimeFacadePresenceTest`, the HTTP client/Kafka cases of `OptionalAdapterBeanGatingTest` and `BootstrapCapabilityReachabilitySystemTest` | `src/app-bootstrap/src/test/`, `src/app-bootstrap/src/systemTest/` | `208077fd` | W4-4: absent from the default composition is the off state; each leaf proves present = on and `enabled=false` = off itself |
| `JpaOffAutoConfigurationImportFilter`, `DataSourceRequirement`과 `DataSourceRequirementTest` | `src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/autoconfigure/jpa/`, `src/app-bootstrap/src/test/java/dev/caskeleton/bootstrap/autoconfigure/jpa/` | `208077fd` | W4-2: JPA를 싣지 않는 조립에서는 Boot의 관계형 자동 설정이 classpath에 없어 꺼진다. 끄는 장치 불필요 |
| `JpaPlatformAutoConfiguration`(플랫폼 조립 factory), `PersistenceJpaRootAutoConfiguration`, `JpaPlatformRuntimeAutoConfiguration`, `MigrationStartupConfig`와 `JpaPlatformAddonAssemblyTest`, `PersistenceJpaRootAutoConfigurationOrderingTest` | `src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/autoconfigure/jpa/`, `src/app-bootstrap/src/test/java/dev/caskeleton/bootstrap/autoconfigure/jpa/` | `208077fd` | W4-2: persistence-jpa `startup.JpaStartupAutoConfiguration` 하나로 합침. 보고서 조립은 `JpaPlatformReport.read`/`platformCapabilities` |
| `DistributedLockConfig`와 `DistributedLockConfigTest` | `src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/autoconfigure/lock/`, `src/app-bootstrap/src/test/java/dev/caskeleton/bootstrap/autoconfigure/lock/` | `208077fd` | W4-1: `distributedLockProvider` bean을 persistence-jpa `DistributedLockPersistenceConfig`로 옮김(테스트도 그쪽에 합침) |
| `DisabledMessagingSentinelAutoConfiguration` | `src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/autoconfigure/messaging/` | `208077fd` | W4-1: relay 스케줄러가 `OutboxMessagePublishPort` bean이 있을 때만 생기므로 대역 publisher가 필요 없다 |
| `OutboxRelayBrokerRequirementValidator`와 테스트 | `src/app-bootstrap/src/{main,test}/java/dev/caskeleton/bootstrap/autoconfigure/outbox/` | `208077fd` | W4-1: 발행 포트가 없으면 스케줄러 자체가 없어 PENDING 행을 DEAD로 소진할 경로가 없다 |
| `RuntimeSafetySettings.migrationOnStartup` | `src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/settings/RuntimeSafetySettings.java` | `208077fd` | W4-2: 읽는 곳이 persistence-jpa뿐. 키 `ca-skeleton.runtime.migration-on-startup`은 그 모듈 기본 설정으로 이동 |
| systemTest H2 도달성 케이스 3개(lock/outbox/PostgreSQL 멱등성)와 `ShippedCompositionHarness.allOffWithH2`, `ShippedRuntimeFacadePresenceTest`의 JPA 케이스 | `src/app-bootstrap/src/systemTest/java/dev/caskeleton/bootstrap/activation/`, `src/app-bootstrap/src/test/java/dev/caskeleton/bootstrap/activation/ShippedRuntimeFacadePresenceTest.java` | `208077fd` | W4-2: 기본 조립이 JPA를 싣지 않는다. 같은 증명은 persistence-jpa `PersistenceJpaCapabilityAssemblyTest` |
| 모듈별 설정 로더 `HttpClientDefaultsEnvironmentPostProcessor`, `FileserverDefaultsEnvironmentPostProcessor`, `NotificationDefaultsEnvironmentPostProcessor`, `MessagingDefaultsEnvironmentPostProcessor`와 각 `spring.factories` | `src/adapter/outbound/httpclient/`, `src/composition/fileserver-platform/`, `src/composition/notification-platform/`, `src/adapter/outbound/messaging-kafka/` | `208077fd` | W4 병합: 설정 파일을 `config/module-defaults/<모듈>.yml`로 옮기고 support의 `ModuleDefaultsEnvironmentPostProcessor` 하나가 읽는다. support에 닿지 않는 persistence-mongo·graphql만 자기 EPP가 `config/<이름>.yml`을 읽는다 |
| `DisabledOutboxMessagePublisher`(outbox 대역 publisher) | `src/adapter/outbound/messaging/src/main/java/dev/caskeleton/adapter/outbound/messaging/outbox/` | `208077fd` | W4 병합: 대역이 있으면 relay 스케줄러가 켜져 모든 발행이 실패하고 PENDING 행이 DEAD로 소진된다. broker가 비어 있고 canonical transport도 없으면 기동을 거부한다 |
| bootstrap `config/persistence.yml`, `config/outbox.yml`, `config/redis.yml`, `config/ratelimit.yml`와 그 import 줄, 기본 조립의 `cache-redis`·`redis-runtime`·`adapter:outbound:messaging` 의존성 | `src/app-bootstrap/` | `208077fd` | W4 병합: 설정은 persistence-jpa·cache-redis 모듈 기본 설정으로, 의존성은 `app-bootstrap/build.gradle`의 주석 한 줄 목록으로 |
| `AutoConfigurationReachabilityParityTest.offImportFiltersReferenceCurrentBootCandidates`와 stale-target 검사 | `src/app-bootstrap/src/test/java/dev/caskeleton/bootstrap/contract/` | `208077fd` | W4 병합: 검사할 off import filter가 남아 있지 않다 |
| `MasterSwitch`, `MasterSwitchParser`, `MasterSwitchParseResult`(shared-contract `activation` 패키지 전체)와 `MasterSwitchParserTest` | `src/shared-contract/src/main/java/dev/caskeleton/shared/activation/`, `src/shared-contract/src/test/java/dev/caskeleton/shared/activation/` | `208077fd` | W4-5: 모든 capability를 한 jar에 싣고 스위치로 끄던 장치의 SSOT. 이제 capability는 `app-bootstrap/build.gradle`의 `runtimeOnly` 한 줄로 고르고, 있는 모듈은 자기 `enabled` 키(기본 `true`)로만 끈다 |
| bootstrap `activation` 패키지: `MasterSwitchEnvironmentPostProcessor`, `CapabilityDependencyValidator`, `CapabilityDependencyEnvironmentValidator`, `CapabilityDependencyStartupCheck`, `AdapterActivationAutoConfiguration`, `AdapterActivationEndpoint`(`/actuator/adapteractivation`), `AdapterActivationReport` | `src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/activation/` | `208077fd` | W4-5: 스위치 값을 정규화하고, 켠 capability가 꺼진 의존을 가리키면 기동을 거부하고, 스위치 상태를 endpoint로 보고하던 코드. capability 사이 의존은 이제 build 줄로 표현한다(알림·파일 서버는 persistence-jpa 줄도 넣는다). 무엇이 조립됐는지는 Boot의 `conditions` endpoint로 본다(기본 노출 목록에는 없으니 `management.endpoints.web.exposure.include`에 추가). 같은 패키지의 `RuntimeEnvironmentProfileValidator`는 삭제가 아니라 `dev.caskeleton.bootstrap.runtime`으로 옮김 |
| `CaSkeletonApplication.AUTO_CONFIGURED_PACKAGES`(component scan 제외 정규식) | `src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/CaSkeletonApplication.java` | `208077fd` | W4-5: scan은 이제 `dev.caskeleton.bootstrap`만 본다. web은 `WebAdapterAutoConfiguration`, support는 `OutboundSupportConfig`를 자기 `AutoConfiguration.imports`로 공개하므로 제외할 패키지가 없다 |
| `StartupOrder.MASTER_SWITCH_NORMALISATION`, `StartupOrder.CAPABILITY_DEPENDENCY` | `src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/runtime/startup/StartupOrder.java`(지금은 `adapter:outbound:support`의 `support.startup.StartupOrder`) | `208077fd` | W4-5: 순서를 정해 줄 post-processor·validator가 삭제됨 |
| `RedisActivationValidator`, `RedisActivationAutoConfiguration`과 `RedisActivationValidatorTest` | `src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/autoconfigure/redis/RedisActivationValidator.java`, `src/app-bootstrap/src/test/java/dev/caskeleton/bootstrap/autoconfigure/redis/RedisActivationValidatorTest.java`(W4 병합 중 cache-redis로 옮긴 뒤 삭제) | `208077fd` | W4-5: Redis를 기본으로 끈 채 싣던 시절의 활성화 가드. 이제 cache-redis 줄이 있으면 켜지고(`APP_REDIS_ENABLED` 기본 `true`), `false`면 `RedisCapabilityConfig`·`RedisSdkAutoConfiguration`이 bean을 하나도 만들지 않는다 |
| `DatabaseReadinessGroupPostProcessor` | `src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/autoconfigure/jpa/DatabaseReadinessGroupPostProcessor.java` | `208077fd` | W4-5: persistence-jpa `startup.JpaActivationEnvironmentPostProcessor`로 대체. 켜져 있으면 readiness에 `db`를 넣고, `APP_PERSISTENCE_JPA_ENABLED=false`면 Boot의 JDBC·Hibernate·Spring Data JPA·Flyway 자동 설정까지 빼서 완전히 끈다 |
| 끄는 장치 테스트: `AdapterActivationEndpointTest`, `AdapterActivationReportShapeTest`, `CapabilityDependencyValidatorTest`, `MasterSwitchRegistryContractTest`, `ShippedRuntimeFacadePresenceTest`, `DisabledAdapterSentinelTest`, `OptionalAdapterBeanGatingTest`, `AutoConfigurationReachabilityParityTest`, `RedisOptionalityContractTest`, persistence-jpa `OutboxMasterSwitchWiringContractTest` | `src/app-bootstrap/src/test/java/dev/caskeleton/bootstrap/{activation,contract}/`, `src/app-bootstrap/src/test/java/dev/caskeleton/adapter/outbound/`, `src/adapter/outbound/persistence-jpa/src/test/java/dev/caskeleton/adapter/outbound/persistence/outbox/` | `208077fd` | W4-5: 기본 jar에 실린 capability가 꺼져 있음을 증명하던 테스트. 이제 기본 조립에 없는 것이 꺼진 상태이고, 각 leaf가 "있으면 켜짐 / `enabled=false`면 꺼짐"을 스스로 증명한다 |
| systemTest `activation/AdapterActivationInventory`, `DependencyErrorStartupContractTest`, `FiveAdapterOffInventoryTest`, `MasterSwitchEnvironmentPostProcessorTest` | `src/app-bootstrap/src/systemTest/java/dev/caskeleton/bootstrap/activation/` | `208077fd` | W4-5: 다섯 어댑터를 모두 싣고 끈 기동과 의존 오류 메시지를 확인하던 lane. 기본 조립 기동은 systemTest `composition/DefaultCompositionBootTest`(local/dev/prod, capability bean 0개)가, capability별 켜짐/꺼짐은 각 leaf의 activation 테스트가 본다 |
| bootstrap `GraphQlDeploymentModeRegistryParityTest` | `src/app-bootstrap/src/test/java/dev/caskeleton/bootstrap/activation/GraphQlDeploymentModeRegistryParityTest.java` | `208077fd` | W4-5: 규칙(deployment mode ↔ runtime profile)이 graphql `GraphQlPlatformStartupValidator`로 옮겨 가면서 테스트도 graphql leaf의 같은 이름 테스트로 옮김 |
| `OutboxRepository.purgePublishedBefore(Instant)`, `InboxRepository.purgeProcessedBefore(Instant)`와 JDBC 구현 | `src/messaging/messaging-reliability-api/src/main/java/dev/caskeleton/messaging/reliability/{Outbox,Inbox}Repository.java`, `src/messaging/messaging-{outbox,inbox}-jdbc-postgresql/src/main/java/.../Jdbc{Outbox,Inbox}Repository.java` | `6d27356e` | M-6: 개수 제한 없는 단일 DELETE. bounded 버전만 남김 |
| JAAS 문자열에 사용자 이름·비밀번호를 넣던 코드(`jaas`, `scramJaas`, `plainJaas`, `escapeJaas`)와 그 테스트 `aSecretWithQuotesIsEscaped`, `aSecretWithAControlCharacterIsRefused` | `src/messaging/messaging-kafka/src/main/java/dev/caskeleton/messaging/kafka/KafkaSecurityConfigurer.java`, `.../KafkaSecurityConfigurerTest.java` | `6d27356e` | M-2d/M-2f: 자격 증명이 JAAS에 들어가지 않으므로 escape할 값이 없음. callback handler로 대체 |
| `CredentialRuntime` 5-인자 생성자 | `src/messaging/messaging-security/src/main/java/dev/caskeleton/messaging/security/CredentialRuntime.java` | `6d27356e` | username을 받는 생성자로 대체, 호출자는 registry 하나 |
| `BrokerCredentialProfile.MutualTls(String)` 1-인자 형태 | `src/messaging/messaging-security/src/main/java/dev/caskeleton/messaging/security/BrokerCredentialProfile.java` | `6d27356e` | key store 없는 MUTUAL_TLS는 동작할 수 없음. `(credentialId, keyStoreLocation, keyStoreType)`으로 대체 |
| 테스트 `handlerTimeoutCancelsTheOutstandingHandlerBeforeThePartitionPermitIsReleased` | `src/messaging/messaging-kafka/src/test/java/dev/caskeleton/messaging/kafka/KafkaConsumerRegistrarTest.java` | `6d27356e` | M-3: CompletableFuture cancel을 단언해 결함을 고정하던 테스트 |
| `spring.kafka.bootstrap-servers` 모듈 기본값, compose 계약의 `SPRING_KAFKA_BOOTSTRAP_SERVERS` 3곳, producer의 `Environment` 인자 | `src/adapter/outbound/messaging-kafka/src/main/resources/config/module-defaults/messaging.yml`, `src/config/runtime/compose-profile-contracts.json`, `src/messaging/messaging-spring-boot-starter-kafka/.../KafkaMessagingAutoConfiguration.java` | `6d27356e` | M-2b: broker 주소 출처를 `app.messaging.brokers.<b>` 하나로 |
| direct 전송·direct multipart 조정자와 보조 타입 14개(`DirectTransferCoordinator`, `DirectMultipartCoordinator`, `DirectGrantProvider`, `DirectMultipartProvider`, `DirectGrantReplayCache`, `DirectMultipartGrantLedger`, `DirectMultipartCompletionVerifier`, `DirectPartAcknowledgementVerifier`, `DirectPublishedObjectResolver`, `DirectTransferPolicy`, `DirectTransferCorsPolicy`, `DirectTransferSessionRecord`, `DirectGrantGeneration`, `PresignedGrantRedactor`) | `src/adapter/outbound/objectstorage/src/main/java/dev/caskeleton/adapter/outbound/objectstorage/direct/` | `6d27356e` | main 호출자 0, 조립 경로 없음(소유자 결정 D1·D-7a) |
| managed multipart 5개(`ManagedMultipartCoordinator`, `MultipartOperationResolver`, `MultipartPartLedger`, `MultipartUploadPlan`, `MultipartCompletionEvidence`) | `src/adapter/outbound/objectstorage/src/main/java/dev/caskeleton/adapter/outbound/objectstorage/multipart/` | `6d27356e` | main 호출자 0 |
| S3 direct·multipart·presigner·operation resolver 6개(`S3DirectTransferProvider`, `S3DirectMultipartProvider`, `S3ManagedMultipartProvider`, `S3DirectCompletionVerifier`, `S3PresignerFactory`, `S3ObjectOperationResolver`) | `src/adapter/outbound/objectstorage/src/main/java/dev/caskeleton/adapter/outbound/objectstorage/s3/` | `6d27356e` | 위 조정자만 쓰던 provider. contribution이 만들기만 하고 아무도 꺼내 쓰지 않았다 |
| operation 해결·epoch 커널 5개(`ObjectOperationResolutionService`, `ObjectOperationEpochRecord`, `ObjectOperationEpochState`, `DirectGrantSessionState`, `MultipartUploadState`)와 `ObjectOperationStateMachine.advanceDirectGrant/advanceMultipart`, `PendingObjectEffect.Kind`의 DIRECT_*·MULTIPART_* 값, `ObjectRequestFingerprintCodec.OperationKind`의 DIRECT_*·MULTIPART_* 값 | `src/adapter/outbound/objectstorage/src/main/java/dev/caskeleton/adapter/outbound/objectstorage/kernel/`, `.../codec/ObjectRequestFingerprintCodec.java` | `6d27356e` | 삭제된 조정자 전용. fingerprint 정규 바이트 형식(`direct-parameter` 줄 포함)은 기존 기록 호환을 위해 유지 |
| direct/multipart control record 5종(`ObjectDirectSessionRecord`, `ObjectDirectMultipartSessionRecord`, `ObjectDirectMultipartGrantRecord`, `ObjectMultipartSessionRecord`, `ObjectMultipartPartRecord`)과 codec 분기·`Family` 값, `ObjectControlKeyCodec.{multipart,directSession,multipartPart,directMultipartGrant,operationEpoch}`, `ObjectHandleCodec.{directUpload,multipart,partReceipt}` | `src/adapter/outbound/objectstorage/src/main/java/dev/caskeleton/adapter/outbound/objectstorage/control/`, `.../codec/` | `6d27356e` | 삭제된 조정자만 쓰던 영속 레코드. 이 family를 쓴 조립 경로가 없어 저장된 레코드도 없다 |
| capability 값 `DIRECT_UPLOAD`·`DIRECT_MULTIPART` | `ObjectStorageProvider.Capability`, `application-objectstorage/.../model/ObjectCapabilityRequirement.java` | `6d27356e` | 구현이 사라진 뒤에도 설정하면 조용히 무시되는 옵션이 된다(capability 규칙 3) |
| `SelectedObjectStorageProviderFactory`의 `managedMultipart/directTransfer/directMultipart` 슬롯·getter·생성자 3개 | `src/adapter/outbound/objectstorage/src/main/java/dev/caskeleton/adapter/outbound/objectstorage/config/SelectedObjectStorageProviderFactory.java` | `6d27356e` | 테스트만 호출(`S3ProviderCompositionTest`) |
| `S3ClientPolicy.{requireSdkCompatibleMpuObjectSize,requirePartCount,requirePartSize}`, `MINIMUM_NON_FINAL_PART_BYTES` | `src/adapter/outbound/objectstorage/src/main/java/dev/caskeleton/adapter/outbound/objectstorage/s3/S3ClientPolicy.java` | `6d27356e` | multipart provider 전용 |
| 포트 `DirectObjectUploadPort`·`DirectObjectDownloadGrantPort`·`DirectMultipartUploadPort` | `src/application-objectstorage/src/main/java/dev/caskeleton/application/objectstorage/port/` | `6d27356e` | 구현·소비자 0 |
| direct/multipart 요청·응답 타입 15개(`Direct{Upload,Download}Grant`, `DirectUploadCompletion{Request,Receipt}`, `Direct{Upload,Download}GrantRequest`, `Multipart{Start,Complete,Abort}Request`, `MultipartPartAcknowledgement`, `MultipartReceipt`, `MultipartSession`, `PartUploadGrant{,Request}`)과 `ObjectModelSupport.{immutableHeaders,requireExpiry}` | `src/application-objectstorage/src/main/java/dev/caskeleton/application/objectstorage/{model,request}/` | `6d27356e` | 삭제된 포트 전용 |
| 식별자 `DirectTransferSessionId`·`MultipartPartNumber`·`PartReceiptToken`, `ObjectIdentitySupport.requirePartReceipt` | `src/application-objectstorage/src/main/java/dev/caskeleton/application/objectstorage/identity/` | `6d27356e` | 삭제된 포트·레코드 전용 |
| `RoutingObjectDirectGrantAdapter` | `src/adapter/outbound/objectstorage/src/main/java/dev/caskeleton/adapter/outbound/objectstorage/config/RoutingObjectDirectGrantAdapter.java` | `6d27356e` | private 생성자만 있는 빈 클래스, 참조 0 (D-7b) |
| `ObjectStorageMaintenanceCapabilityConfig` | `src/adapter/outbound/objectstorage/src/main/java/dev/caskeleton/adapter/outbound/objectstorage/config/ObjectStorageMaintenanceCapabilityConfig.java` | `6d27356e` | 빈 `@Configuration` (D-7b) |
| `ObjectPurgeMaintenancePort`, `ObjectPurgeRequest` | `src/application-objectstorage/src/main/java/dev/caskeleton/application/objectstorage/{port,request}/` | `6d27356e` | 구현 0 (D-7c) |
| 삭제 코드 전용 테스트 17개(`direct/` 6개, `multipart/` 2개, `ObjectOperationEpochTest`, `ObjectMutationResponseLossTest`, `S3{DirectMultipart,DirectTransfer,ManagedMultipart}ProviderTest`, `S3ObjectOperationResolverTest`, `MinioDirectTransfer{Contract,Fault}Test`, `S3SdkApiCharacterizationTest.sdkMultipartIntegerPartCountAndMinimumPartBoundariesFailClosed`) | `src/adapter/outbound/objectstorage/src/test/java/dev/caskeleton/adapter/outbound/objectstorage/` | `6d27356e` | 대상 코드 삭제 |
| `AwsS3DirectMutationPreconditionsTest`와 workflow 입력 `run_protected_aws_direct_mutation`·env `OBJECT_STORAGE_AWS_DIRECT_MUTATION_ENABLED` | `src/adapter/outbound/objectstorage/src/objectStorageAwsQualificationTest/.../AwsS3DirectMutationPreconditionsTest.java`, `.github/workflows/object-storage-qualification.yml` | `6d27356e` | direct 전송 lane의 별도 권한 검사. direct 코드가 없으니 검사할 대상이 없다 |
| APNs provider adapter(4 클래스)와 테스트 | `src/adapter/outbound/notification/src/{main,test}/java/dev/caskeleton/adapter/outbound/notification/platform/provider/apns/` | `6d27356e` | assembler 없음 — 켜면 기동 실패. S4-#3a |
| FCM provider adapter(10 클래스)와 테스트 | `…/platform/provider/fcm/` | `6d27356e` | 같은 이유. S4-#3a |
| Twilio provider adapter(9 클래스)와 테스트 | `…/platform/provider/twilio/` | `6d27356e` | 같은 이유. S4-#3a |
| Web Push provider adapter(10 클래스)와 테스트 | `…/platform/provider/webpush/` | `6d27356e` | 같은 이유. S4-#3a |
| Webhook provider adapter(3 클래스)와 테스트 | `…/platform/provider/webhook/` | `6d27356e` | 같은 이유. S4-#3a |
| `SesSuppressionUpdater` | `…/platform/provider/ses/SesSuppressionUpdater.java` | `6d27356e` | main 참조 0. suppression은 projection side-effect 경로가 담당. S4-#3a |
| `ProviderType.APNS/FCM/TWILIO/WEB_PUSH/WEBHOOK` | `…/platform/autoconfigure/ProviderType.java` | `6d27356e` | 조립할 수 없는 종류. 이제 binding에서 unknown type으로 실패 |
| provider 설정 필드 `topic`, `vapid-public-key`, `callback-signing-secret-ref` | `…/platform/autoconfigure/NotificationPlatformSettings.java` (Provider) | `6d27356e` | 삭제된 5종만 읽던 키. capability 규칙 3(동작 안 하는 옵션은 키를 두지 않음) |
| `SecretPurpose.VAPID_SIGNING`, 설정 `secrets.vapid-signing-key`·`active-key-ids.VAPID_SIGNING`, env `APP_NOTIFICATION_PLATFORM_VAPID_SIGNING_KEY`·`APP_NOTIFICATION_PLATFORM_VAPID_SIGNING_KEY_ID` | `src/application-notification/…/platform/security/SecretPurpose.java`, `src/composition/notification-platform/src/main/resources/config/module-defaults/notification.yml`, `src/.env.example`, `docs/registries/env-keys.yaml`, `docs/registries/secrets-classification.yaml`, `scripts/run-compose-runtime-smoke.sh` | `6d27356e` | Web Push 삭제로 소비자 0 |
| Twilio·FCM·APNs·Web Push runbook 절, support-matrix·module-mapping 행 | `docs/notification/provider-runbooks.md`, `docs/notification/support-matrix.md`, `docs/notification/module-mapping.md`, `docs/notification/configuration-reference.md` | `6d27356e` | 설명 대상 코드 삭제 |
| tus `Upload-Defer-Length: 1` 수락 분기 | `src/adapter/inbound/web-fileserver/src/main/java/dev/caskeleton/adapter/inbound/web/fileserver/tus/TusRequestParser.java` `declaredLength` | `6d27356e` | C-5c. 길이를 나중에 확정할 PATCH가 없어 끝나지 않는 upload만 만들었다. 이제 400 |
| 테스트 `aDeferredLengthUploadIsNeverAutoFinalized` | `src/adapter/inbound/web-fileserver/src/test/java/dev/caskeleton/adapter/inbound/web/fileserver/tus/TusProtocolContractTest.java` | `6d27356e` | 위 분기를 전제로 한 테스트. `aCreateThatDefersItsLengthIsRefusedBecauseTheExtensionIsNotOffered`로 대체 |
| 테스트 `scopeSemaphoreRegistryIsBoundedAndOverflowScopesShareConservativeCapacity` | `src/application-fileserver/src/test/java/dev/caskeleton/application/fileserver/quota/TransferAdmissionControllerTest.java` | `6d27356e` | C-9b. 유휴 scope가 overflow로 몰린다는 옛 동작을 단언. `theScopeRegistryStaysBoundedAsCallersComeAndGo`로 대체 |
| lifecycle delete·admin forceDelete·cancel의 retire 복사본 | `DefaultFileLifecycleService.delete`, `DefaultFileserverAdminService.forceDelete`, `DefaultUploadApplicationService.cancel` 본문 | `6d27356e` | S1-#5. `cleanup/FileRetirement` 하나로 합침 |
| `GrpcStableModuleCatalog`(+`GrpcStableModuleCatalogTest`) | `src/grpc/grpc-core-api/src/main/java/dev/caskeleton/grpc/core/GrpcStableModuleCatalog.java` | `6d27356e` | leaf 목록을 core-api에 재기술(registry SSOT 중복), main 호출자 0 (S7-#4) |
| `GrpcStableBuildInvariant` | `src/grpc/grpc-core-api/src/main/java/dev/caskeleton/grpc/core/GrpcStableBuildInvariant.java` | `6d27356e` | 상수 반환·항상 빈 set으로만 불림. 격리는 `verifyCleanArchitectureDependencies`가 강제 (S7-#4, N-9b/c) |
| `GrpcPlatformStartupValidator.validateAdvancedIsolation` + `stableModuleDependencies` 파라미터 | `src/grpc/grpc-spring-boot-starter/src/main/java/dev/caskeleton/grpc/boot/GrpcPlatformStartupValidator.java` | `6d27356e` | 항상 `Set.of()`로 호출돼 항상 통과 (N-9b) |
| `GrpcAdvancedModuleGuard.requireStableStarterIsClean`, `advancedModules` | `src/grpc-advanced/grpc-advanced-bootstrap/src/main/java/dev/caskeleton/grpc/advanced/bootstrap/GrpcAdvancedModuleGuard.java` | `6d27356e` | 삭제된 catalog/invariant 위임, main 호출자 0 |
| `GrpcApplicationBoundaryRules`, `GrpcRawApiImportRule`, `GrpcServiceAdapterMarker`(+`GrpcApplicationBoundaryRulesTest`) | `src/grpc/grpc-server/src/main/java/dev/caskeleton/grpc/architecture/` | `6d27356e` | 문자열로 ArchUnit 흉내, 자기 테스트의 합성 입력만 검사. 경계 규칙은 app-bootstrap ArchUnit이 검사 |
| `GrpcKotlinCompatibilityGate`, `GrpcKotlinProfile` | `src/grpc-advanced/grpc-advanced-compat/src/main/java/dev/caskeleton/grpc/advanced/kotlin/` | `6d27356e` | `supportableHere()` 상수 false, main 호출자 0 |
| `GrpcWebCompatibilityGate` | `src/grpc-advanced/grpc-advanced-compat/src/main/java/dev/caskeleton/grpc/advanced/web/GrpcWebCompatibilityGate.java` | `6d27356e` | 상수 메서드 + main 호출자 0(`GrpcWebRpcSupport.require`가 같은 규칙) |
| `GrpcServletStartupValidator`, `GrpcServletCapabilityMatrix`, `GrpcServletCompatibilityProfile`(+`GrpcServletStartupValidatorTest`) | `src/grpc-advanced/grpc-advanced-compat/src/main/java/dev/caskeleton/grpc/advanced/servlet/` | `6d27356e` | Servlet 전송 코드 없이 상수 matrix·gate만 있던 패키지, main 호출자 0 |
| `GrpcEdition2024Gate`, `GrpcEdition2026Guard` | `src/grpc-advanced/grpc-advanced-edition/src/main/java/dev/caskeleton/grpc/advanced/edition/` | `6d27356e` | 상수 반환 gate·무조건 throw guard, main 호출자 0 |
| `GrpcResolverSafetyPolicy.acceptAfterClose`, `mayCarryBusinessMetadata`; `CREDENTIAL_SHAPED` 정규식 | `src/grpc-advanced/grpc-advanced-resilience/src/main/java/dev/caskeleton/grpc/advanced/discovery/GrpcResolverSafetyPolicy.java` | `6d27356e` | 상수 메서드(S7-#4) / 부분일치 정규식이 정상 키를 거부(N-4, W1 커밋) |
| `GrpcXdsStartupGuard` + 테스트 리소스 `xds/bootstrap.json` | `src/grpc-advanced/grpc-advanced-resilience/src/main/java/dev/caskeleton/grpc/advanced/xds/GrpcXdsStartupGuard.java` | `6d27356e` | 상수 메서드 포함 guard, main 호출자 0 |
| `GrpcAdvancedInfrastructureTestkit` | `src/grpc-advanced/grpc-advanced-diagnostics/src/main/java/dev/caskeleton/grpc/advanced/diagnostics/GrpcAdvancedInfrastructureTestkit.java` | `6d27356e` | capability별 인프라 목록 상수, main 호출자 0 (문서 표로 대체) |
| 설정 키 `ca-skeleton.capabilities.rate-limit.default-policy-id` (+ `RedisCapabilitySettings.RateLimit.defaultPolicyId` getter/setter) | `src/adapter/outbound/cache-redis/src/main/resources/config/module-defaults/cache-redis.yml`, `src/adapter/outbound/cache-redis/src/main/java/dev/caskeleton/adapter/outbound/cache/redis/capability/RedisCapabilitySettings.java` | `6d27356e` | S6-#6b: 같은 env 키에 두 설정 키가 묶여 있었다. `app.rate-limit.default-policy-id` 하나로 통일 |
| `SmtpProviderRuntimeAssembler.capabilities()` (SMTP capability 사본) | `src/adapter/outbound/notification/src/main/java/dev/caskeleton/adapter/outbound/notification/platform/autoconfigure/SmtpProviderRuntimeAssembler.java` | `6d27356e` | 어댑터 `capabilities()`와 값이 달랐다(S4-#4a). 이제 snapshot이 어댑터 값을 쓴다 |
| actuator `loggers` 노출과 `POST`/`DELETE /actuator/loggers/**` `denyAll` 규칙 | `src/app-bootstrap/src/main/resources/config/observability.yml`, `src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/management/security/ManagementSecurityConfig.java` | `6d27356e` | actuator 체인에 인증 수단이 없어 어떤 자격증명으로도 도달할 수 없었다(L-7a) |
| `IdempotencyExecutor.preserveUnknown` | `src/application-core/src/main/java/dev/caskeleton/application/idempotency/IdempotencyExecutor.java` | `6d27356e` | `recordFailure`로 대체했다(A-8b) |
| `GraphQlExecutionProfile`(BLOCKING_MVC·REACTIVE_WEBFLUX·MIXED_CONTROLLED), `GraphQlExecutionProfileException` | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/execution/` | `6d27356e` | D4: servlet 단일 스택이라 고를 프로파일이 없음 |
| `GraphQlRuntimeTransport`와 `GraphQlPlatformAutoConfiguration`의 `ServletRuntimeDetection`·`ReactiveRuntimeDetection`, `GraphQlPlatformRuntime.transport` | `.../graphql/autoconfigure/` | `6d27356e` | D4: 프로파일과 실행 서버 대조가 필요 없어짐 |
| `GraphQlBlockingBridge`, `GraphQlBlockingBridgeFullException`, `GraphQlBatchLoaderRegistrar`의 bridge·profile 인자, `GraphQlBlockingBridgeTest` | `.../graphql/runtime/`, `src/adapter/inbound/graphql/src/test/java/dev/caskeleton/adapter/inbound/graphql/runtime/` | `6d27356e` | D4: event loop 에서 blocking 작업을 빼내는 bridge. servlet 에서는 호출 스레드 inline 실행(J-4b 결함 경로) |
| 설정 `backend.graphql.execution-profile`(`APP_GRAPHQL_EXECUTION_PROFILE`), `backend.graphql.unbridged-blocking-resolvers`와 validator의 reactive 검사 | `GraphQlPlatformSettings.java`, `GraphQlPlatformStartupValidator.java`, `src/main/resources/config/graphql.yml`, `docs/registries/env-keys.yaml`, `src/.env.example` | `6d27356e` | D4: 동작할 수 없는 옵션은 키를 두지 않는다 |
| 테스트: `GraphQlTransportNeutralityTest`의 context 기반 프로파일 케이스 7개, `GraphQlBatchLoaderRegistrationTest` reactive·bridge 2건, `GraphQlPlatformStartupValidatorTest.aBlockingResolverWithoutABridgeCannotRunOnTheReactiveProfile` | `src/adapter/inbound/graphql/src/test/java/dev/caskeleton/adapter/inbound/graphql/` | `6d27356e` | 대상 코드 삭제 |
| `GraphQlPlatformRejectionMapper.map`(unknown → INTERNAL_ERROR 정적 메서드) | `.../graphql/runtime/GraphQlPlatformRejectionMapper.java` | `6d27356e` | 모든 경로가 `GraphQlWireErrorMapper.map`을 쓰게 되어 호출자 없음 (`mapFieldFailure`는 `map`으로 이름 변경) |
| `JpaDangerousConfigurationGuard`의 OSIV 검사 분기와 `OPEN_IN_VIEW_KEY` 상수 | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/startup/JpaDangerousConfigurationGuard.java` | `6d27356e` | S6-#3b. `OpenInViewSafetyValidator`가 모든 profile에서 먼저 거부하므로 local 예외가 도달 불가능한 죽은 코드 |
| `OutboxEventJpaRepository.deletePublishedBefore`(무제한 단일 DELETE) | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/outbox/OutboxEventJpaRepository.java` | `6d27356e` | E-8b. 배치 삭제 `deletePublishedBatch`로 교체 |
| rate-limit client IP 모드 (`RateLimitClientIpMode`, `ClientIpResolver`, `ClientIpResolverFactory`, `ForwardedHeaderClientIpResolver`, `RemoteAddrClientIpResolver`)와 설정 `app.rate-limit.client-ip-mode` / env `APP_RATE_LIMIT_CLIENT_IP_MODE` | `src/adapter/inbound/web/src/main/java/dev/caskeleton/adapter/inbound/web/ratelimit/` | `6d27356e` | I-5a·NEW-10c: `FORWARDED_HEADERS_TRUSTED`가 호출자가 쓰는 XFF 맨 왼쪽 값을 키로 씀. 운영 정본은 `server.forward-headers-strategy=native` + `server.tomcat.remoteip.internal-proxies`의 `getRemoteAddr()` 하나 |
| `RequestLoggingFilter`의 request/correlation/trace id 발급·MDC 기록·응답 헤더 | `src/adapter/inbound/web/src/main/java/dev/caskeleton/adapter/inbound/web/filter/RequestLoggingFilter.java` | `6d27356e` | I-4a·I-4b: `WebMvcRequestIdFilter`로 이동(두 필터가 trace를 따로 만들던 것 제거) |
| 알림 제출 category 기본값 `"transactional"` | `src/adapter/inbound/web-notification/.../submission/NotificationSubmissionController.java` | `6d27356e` | I-6a 결정 13 |
| `WorkLogController.requireIfMatch`(트랜잭션 밖 get 후 비교) | `src/sample-portfolio/src/main/java/dev/caskeleton/sample/portfolio/adapter/inbound/web/controller/WorkLogController.java` | `6d27356e` | S6-#11b: 비교를 update 유스케이스 트랜잭션 안으로 |
| reactive gateway·SSE·streaming·runtime 패키지 (`DefaultReactiveHttpGateway`, `ReactiveHttpGateway`, `DefaultReactiveSseGateway`, `ReactiveSseGateway`, `ReactiveStreamingGateway`, `ReactiveAttemptExecutor`, `ReactiveClientRuntime`, `WebClientRuntimeFactory`, `WebClientBodyWriter`, `WebClientResponseMapper`, `BoundedDataBufferFlux`, `FirstByteDeliveryGuard`, `MultipartReplayability`, `ReactiveBodySource`, `SseIdleTimeoutException`, `SseOperation`, `SseReconnectPolicy`) | `src/adapter/outbound/httpclient/src/main/java/dev/caskeleton/adapter/outbound/httpclient/webclient/` | `6d27356e` | 결정 9: httpclient reactive 스택 삭제, blocking 경로 하나만 유지 |
| Reactor Netty transport (`ReactorNettyTransportProvider`, `ReactorHttpClientFactory`, `ReactorConnectionProviderFactory`, `ReactorFailureClassifier`, `ReactorPoolMetricsBinder`) | `.../httpclient/reactor/` | `6d27356e` | 결정 9 |
| reactive 자격증명 (`ReactiveCredentialProviderRegistry`, `ReactiveRequestCredentialProvider`) | `.../httpclient/auth/` | `6d27356e` | 결정 9 |
| reactive 재시도·resilience (`ReactiveAttemptResiliencePipeline`, `ReactiveLogicalCall`, `ReactiveRetryCoordinator`) | `.../httpclient/resilience/` | `6d27356e` | 결정 9 |
| reactive typed client (`DefaultReactiveHttpServiceRegistry`, `ReactiveHttpServiceRegistry`, `ReactiveKernelHttpExchangeAdapter`, `ReactiveOperationContext`, `ReactiveServiceInvocationHandler`), `ServiceOperationDescriptor.reactive` 플래그와 blocking/reactive 혼합 검사 | `.../httpclient/service/` | `6d27356e` | 결정 9 |
| reactive transport SPI (`ReactiveTransportProvider`, `ReactiveTransportCapabilities`), `TransportCapabilityValidator`의 reactive overload | `.../httpclient/transport/` | `6d27356e` | 결정 9 |
| 설정 키 `app.httpclient.clients[N].api`(`APP_HTTPCLIENT_CLIENTS_N_API`)와 `ClientApiType`, `TransportType.REACTOR_NETTY`, actuator `api` 항목 | `.../httpclient/profile/ClientApiType.java`, `docs/httpclient/env-fields.yaml` | `6d27356e` | 남은 값이 하나뿐인 키(동작하지 않는 옵션은 키를 두지 않음). H2 전용 프로필은 이제 모든 transport에서 `HTTP2_REQUIRED_TRANSPORT_UNSUPPORTED` |
| 기동 위반 코드 `REACTIVE_REDIRECT_UNSUPPORTED`, `REACTIVE_AUTHENTICATION_UNSUPPORTED`, `DYNAMIC_TARGET_PROFILE_API_UNSUPPORTED` | `.../profile/ClientProfileValidator.java`, `.../autoconfigure/HttpClientStartupValidator.java` | `6d27356e` | reactive 프로필이 없어 판정 대상 없음 |
| reactive bean (`httpClientReactiveTransportProviders`, `httpClientReactiveCredentialProvider`, `ReactiveAttemptExecutor`, `reactiveHttpGateway`, `ReactiveHttpServiceRegistry`, `ReactiveStreamingGateway`, `ReactiveSseGateway`) | `.../httpclient/autoconfigure/` | `6d27356e` | 결정 9 |
| reactive 테스트 (`BlockHoundEventLoopTest`, `DefaultReactiveHttpGatewayTest`, `FirstByteRetryBoundaryTest`, `ReactiveSseGatewayTest`, `ReactiveStreamingLifecycleTest`, `ReactiveRetryCoordinatorTest`, `ReactiveHttpServiceRegistryTest`, `ReactiveAuthenticationContractTest`, `BlockingReactiveSignatureSeparationTest`), 계약·protocol 테스트의 reactor case | `src/adapter/outbound/httpclient/src/test/java/...` | `6d27356e` | 대상 코드 삭제. forward proxy 경로 테스트는 blocking(Apache)으로 옮김(`ForwardProxyContractTest.gatewayRoutesTheCallThroughTheConfiguredForwardProxy`) |
| reactive testkit (`ReactiveTestGateways`, `ReactiveTransportContract`, `ReactiveEventsClient`, `MixedSignatureClient`, `NettyLeakDetectionExtension`, `EventPayload`, `MockHttpServer.enqueueSse`, `ClientProfiles.reactor`, `HttpClientContract.blockHoundSelected`) | `src/adapter/outbound/httpclient/src/testFixtures/java/...` | `6d27356e` | 대상 코드 삭제 |
| `Http2StreamSaturationTest`(Reactor Netty 전용), `ReactiveClientBenchmark` | `.../src/httpClientPerformanceTest/...`, `.../src/jmh/...` | `6d27356e` | 대상 transport 삭제 |
| `httpClientBlockHoundTest` lane, `check` 의존, 계약 lane 기본 transport의 `reactor`, `io.netty.leakDetection.level` 시스템 속성 | `src/adapter/outbound/httpclient/build.gradle` | `6d27356e` | reactor event loop이 없어 검증 대상 없음 |
| 의존 `spring-webflux`, `reactor-core`, `reactor-netty-http`, `reactor-test`, `blockhound`, testFixtures `netty-common`·`logback-classic`·`reactor-core`, 카탈로그 `blockhound` | `src/adapter/outbound/httpclient/build.gradle`, `src/gradle/libs.versions.toml` | `6d27356e` | 결정 9 |
| CI matrix `transport: reactor`, release의 `httpClientBlockHoundTest` | `.github/workflows/pr-adapters.yml`, `.github/workflows/release.yml` | `6d27356e` | 없는 lane·transport 호출 제거 |
| `MongoBulkWritePlan.estimatedEncodedBytes` (plan 생성 시 `toJson()` 크기 추정) | `src/adapter/outbound/persistence-mongo/src/main/java/dev/caskeleton/adapter/outbound/mongo/imperative/bulk/MongoBulkWritePlan.java` | `6d27356e` | 매핑 전 값에 codec이 없어 실패(F-4b). 매핑된 문서의 실제 BSON 크기 검사(`MongoBulkExecutor.mappedWrites`)로 대체 |
| `MongoCsfleClientFactory.settingsFor`의 `encryptedFieldsMapJson` 인자 | `src/adapter/outbound/persistence-mongo/src/main/java/dev/caskeleton/adapter/outbound/mongo/advanced/encryption/csfle/MongoCsfleClientFactory.java` | `6d27356e` | 호출자 JSON을 schema로 쓰던 경로(F-5b). `profile.fields()`에서 생성 |
| 설정 키 `ca-skeleton.persistence-mongo.active-profile` | `src/adapter/outbound/persistence-mongo/src/main/resources/config/mongo.yml` | `6d27356e` | `ca-skeleton.persistence-mongo.platform.active-profile`로 이동(F-2a, `MongoPlatformSettings`에 한 번 바인딩). env 키는 그대로 |
| `GitCommandResult` record | `src/build-logic/src/main/java/dev/caskeleton/buildlogic/architecture/GitCommandResult.java` | `6d27356e` | O-3b에서 git 호출이 exit code를 직접 판정하는 `checkIgnore` 하나로 줄어 쓰는 곳이 없음 |
| `git rev-parse --show-toplevel` 호출(checkout 판정) | `VerifyNoIgnoredSourcePackagesTask.java` | `6d27356e` | 실패하면 "checkout 아님"으로 읽혀 게이트가 통과하던 원인. `.git` 존재 판정으로 대체 |
| compose 계약 필드 `expectedSwitchesOn` | `src/config/runtime/compose-profile-contracts.json` | `6d27356e` | 읽는 코드가 없던 필드. `expectedCapabilitiesOn`(info 이름)으로 재정의 |
| `grpc-policy` leaf | `src/grpc/grpc-policy` | `6d27356e` | 병합: → `grpc-runtime`(S7-#3) |
| `grpc-server` leaf | `src/grpc/grpc-server` | `6d27356e` | 병합: → `grpc-runtime`(S7-#3) |
| `grpc-client` leaf | `src/grpc/grpc-client` | `6d27356e` | 병합: → `grpc-runtime`(S7-#3) |
| `grpc-discovery` leaf | `src/grpc/grpc-discovery` | `6d27356e` | 병합: → `grpc-runtime`(S7-#3) |
| `grpc-admin` leaf | `src/grpc/grpc-admin` | `6d27356e` | 병합: → `grpc-runtime`(S7-#3) |
| `grpc-proto-contract` leaf (`.proto`는 이동) | `src/grpc/grpc-proto-contract` | `6d27356e` | 병합: → `grpc-contract`. `.proto` 두 파일은 `grpc-contract/src/main/proto/caskeleton/…`로 이동, 나머지는 삭제(S7-#13) |
| `GrpcProtoContractValidator`, `GrpcProtoStyleManifest`, `GrpcProtoRuleViolation` + 테스트 | `src/grpc/grpc-proto-contract/src/main/java/dev/caskeleton/grpc/contract/` | `6d27356e` | regex `.proto` 파서·style 규칙 재구현 — protoc + Buf lint로 대체(결정 18) |
| `buf.gen.yaml`, `buf.lock`, 구 `buf.yaml` | `src/grpc/grpc-proto-contract/src/main/resources/proto/` | `6d27356e` | 명세용 파일. 생성은 Gradle protobuf 플러그인, 설정은 `src/grpc/grpc-contract/buf.yaml` |
| `grpc-codegen` leaf 전체(`GrpcBufPolicy`, `GrpcBreakingCategory`, `GrpcCodegenManifest`, `GrpcCodegenOutput`, `GrpcGeneratedPackagePolicy`, `GrpcDescriptorArtifact`, `GrpcConsumerFixture`, `GrpcSchemaArtifactPublisher`, `GrpcSchemaBaseline` + 테스트·consumer fixture) | `src/grpc/grpc-codegen` | `6d27356e` | Buf lint/breaking·codegen 소유 규칙의 Java 재구현 — Buf(CI)·protobuf 플러그인으로 대체(결정 18) |
| `grpc-advanced-bootstrap` leaf | `src/grpc-advanced/grpc-advanced-bootstrap` | `6d27356e` | 병합: → `grpc-advanced`(S7-#3) |
| `grpc-advanced-edition` leaf | `src/grpc-advanced/grpc-advanced-edition` | `6d27356e` | 병합: → `grpc-advanced`(S7-#3); `compatibility.proto`는 test resources로 |
| `grpc-advanced-streaming` leaf | `src/grpc-advanced/grpc-advanced-streaming` | `6d27356e` | 병합: → `grpc-advanced`(S7-#3) |
| `grpc-advanced-resilience` leaf | `src/grpc-advanced/grpc-advanced-resilience` | `6d27356e` | 병합: → `grpc-advanced`(S7-#3) |
| `grpc-advanced-diagnostics` leaf | `src/grpc-advanced/grpc-advanced-diagnostics` | `6d27356e` | 병합: → `grpc-advanced`(S7-#3) |
| `GrpcStreamProfile` | `src/grpc/grpc-policy/src/main/java/dev/caskeleton/grpc/streaming/GrpcStreamProfile.java` | `6d27356e` | 테스트에서만 쓰였고 `GrpcFlowControlPolicy`의 256/8 MiB를 복제(N-10b) |
| `GrpcAuthenticationPolicy.isAuthenticated(Metadata)` | `src/adapter/inbound/grpc/src/main/java/dev/caskeleton/adapter/inbound/grpc/GrpcAuthenticationPolicy.java` | `6d27356e` | `authenticate(Metadata): Optional<Principal>`로 교체(K-10a) |
| `GrpcCredentialRotationManager.completeDrain()`(무인자) | `src/grpc/grpc-policy/src/main/java/dev/caskeleton/grpc/security/GrpcCredentialRotationManager.java` | `6d27356e` | `completeDrain(GrpcCredentialGeneration)`로 교체(P5-new-3) |
| `ClientSafeErrorMessages` (web 코드별 영어 문구 표) | `src/adapter/inbound/web/src/main/java/dev/caskeleton/adapter/inbound/web/error/ClientSafeErrorMessages.java` | `016597ac` | 결정 11: shared `ClientErrorMessages`(Category별 한국어) 하나로 |
| `PortfolioClientSafeErrorMessages` (sample 영어 문구) | `src/sample-portfolio/src/main/java/dev/caskeleton/sample/portfolio/adapter/inbound/web/error/PortfolioClientSafeErrorMessages.java` | `016597ac` | 같은 이유(`ErrorResponseFactory`가 message 인자를 받지 않음) |
| `FileserverProblem` | `src/adapter/inbound/web-fileserver/src/main/java/dev/caskeleton/adapter/inbound/web/fileserver/problem/FileserverProblem.java` | `016597ac` | 결정 2: fileserver 실패도 Envelope |
| `FileserverProblemFactory` (+ composition `fileserverProblemFactory` bean) | `src/adapter/inbound/web-fileserver/.../problem/FileserverProblemFactory.java`, `src/composition/fileserver-platform/.../FileserverWebAssemblyConfiguration.java` | `016597ac` | 같은 이유 |
| `FileserverProblemTitles` (영어 title 표) | `src/adapter/inbound/web-fileserver/.../problem/FileserverProblemTitles.java` | `016597ac` | 같은 이유 + 결정 11 |
| `BatchUploadItemProblem` | `src/adapter/inbound/web-fileserver/.../dto/BatchUploadItemProblem.java` | `016597ac` | batch 항목도 `ApiError` |
| `FileserverErrorCode.problemType()` (URN) | `src/application-fileserver/.../api/error/FileserverErrorCode.java` | `016597ac` | problem 문서가 없어져 호출자 0 |
| `GraphQlPlatformRejectionMapper` (instanceof 사슬) | `src/adapter/inbound/graphql/.../runtime/GraphQlPlatformRejectionMapper.java` | `016597ac` | S5-#6d: 예외가 `GraphQlPlatformRejection` 구현 |
| `runtime/GraphQlWireErrorMapper`, `runtime/GraphQlWireErrors` (이동) | `src/adapter/inbound/graphql/.../runtime/` → `.../error/` | `016597ac` | 삭제가 아니라 `error/` 패키지로 이동(S5-#6d). `classificationOf`·`category`·`clientMessage` switch는 `RENDERINGS` 표로 대체 |
| sample publisher별 JSON escape 사본 3개 | `PosterEventPublisher`·`PosterImagePublicationEventPublisher`·`WorkLogReservedIntegrationEventMapper`(`escape`/`field`/`jsonField`) | `016597ac` | X2-P1-6: `EventJson` 하나로 |
| `SensitiveHeaderStripper.withAdditional` | `src/adapter/outbound/httpclient/src/main/java/dev/caskeleton/adapter/outbound/httpclient/security/SensitiveHeaderStripper.java` | `c4a066df` | H-4b. main 호출자 0, executor는 `alsoStripping` 사용 |
| `SafeHttpLogEvent`, `HttpClientTagPolicyTest.safeLogEventCarriesNoSecretOrExpandedUrl` | `src/adapter/outbound/httpclient/src/main/java/dev/caskeleton/adapter/outbound/httpclient/observation/SafeHttpLogEvent.java` | `c4a066df` | S3-#8b. 테스트만 참조 |
| `HttpClientTagPolicy` bean(`httpClientTagPolicy`) | `.../httpclient/autoconfigure/HttpClientObservationAutoConfiguration.java` | `c4a066df` | S3-#6. 소비처 0, override 불가 |
| `RetryCoordinator` 인터페이스(구현 `BlockingRetryCoordinator` → `RetryCoordinator` 개명) | `.../httpclient/resilience/RetryCoordinator.java` | `c4a066df` | S3-#7. 구현 1개, fake 없음 |
| `ExecutionEvidenceClassifier` 인터페이스(구현 `DefaultExecutionEvidenceClassifier` → `ExecutionEvidenceClassifier` 개명) | `.../httpclient/resilience/ExecutionEvidenceClassifier.java` | `c4a066df` | S3-#7. 구현 1개, fake 없음 |
| `BlockingAttemptExecutor.categoryOf` (`getSimpleName()` switch) | `.../httpclient/restclient/BlockingAttemptExecutor.java` | `c4a066df` | H-7a. 예외가 자기 category를 구현 |
| `BlockingExecutionSupport`(→ `ExecutionSupport` 개명) | `.../httpclient/restclient/BlockingExecutionSupport.java` | `c4a066df` | S3-#6. blocking만 남아 접두어 무의미 |
| `JpaSchemaSafetyValidator`, `JpaSchemaSafetyValidatorTest` | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/startup/JpaSchemaSafetyValidator.java` | `93251e76` | S6-#3c. guard와 중복, guard보다 늦게 돌아 발동한 적 없음 |
| `isProdActive()` wrapper 4개 | `persistence-jpa/.../startup/{FlywayProdSafetyValidator,PersistenceVendorProdSafetyValidator,PostgreSqlTransportSecurityValidator}.java`, `app-bootstrap/.../runtime/SecretSourceValidator.java` | `93251e76` | S6-#3d. `RuntimeProfileSnapshot.isProduction()` 1줄 위임 |
| `DurableOperationJpaRepository`의 `JpaRepository` 상속(findAll/deleteAll 등) | `persistence-jpa/.../operation/DurableOperationJpaRepository.java` | `93251e76` | E-6b. tenant 범위 없는 bulk 메서드 노출 |
| build-tools included build 전체(`ca.jpa-evidence`, `ca.jpa-qualification`, `jpa/` 45파일, `junit/` 2파일과 테스트) | `src/build-tools/` | `016597ac` | 소유자 결정 4(JPA evidence manifest 폐기). `config/`는 build-logic으로 이동 |
| `jpa-r2-evidence.yml`, integration-main `jpa-candidate-evidence` job | `.github/workflows/` | `016597ac` | JPA evidence manifest 폐기 |
| `JpaAdopterApiSurfaceTest` | `src/adapter/outbound/persistence-jpa/src/test/java/dev/caskeleton/adapter/outbound/persistence/` | `016597ac` | `ca.api-surface` `adopterBaseline`으로 통합(BUILD-중복-3) |
| `GrpcStableReleaseGate`·`GrpcCompatibilityMatrix`·`GrpcReleaseDecision`·`GrpcReleaseEvidence`(+Test) | `src/grpc/grpc-testkit/src/{main,test}/java/dev/caskeleton/grpc/release/` | `016597ac` | 호출처가 자기 테스트뿐(S5-lead-4) |
| `GrpcAdvancedPromotionGate`·`…Decision`·`…Evidence`·`GrpcAdvancedSupportMatrix`(+Test) | `src/grpc-advanced/grpc-advanced-bootstrap/src/{main,test}/java/dev/caskeleton/grpc/advanced/release/` | `016597ac` | 같음 |
| `ca.public-path-snapshot`(publicpath 5파일 + renderer test) | `src/build-logic/src/main/java/dev/caskeleton/buildlogic/publicpath/` | `016597ac` | app-bootstrap `PublicPathSnapshotTest`로(BUILD-O3-5) |
| `ca.archive-hygiene`(archive 5파일 + test) | `src/build-logic/src/main/java/dev/caskeleton/buildlogic/archive/` | `016597ac` | leaf version에서 revision 제거로 stale jar가 생기지 않음 |
| `ca.developer-bootstrap`(`DeveloperBootstrapPlugin`, `BootstrapSmokeTask` + functional test) | `src/build-logic/src/main/java/dev/caskeleton/buildlogic/bootstrap/` | `016597ac` | `scripts/bootstrap-local.sh`로 |
| `BuildVerificationPurityContractTest`(archive·public-path TestKit 10개) | `src/build-logic/src/test/java/dev/caskeleton/bootstrap/contract/` | `016597ac` | 대상 플러그인 삭제; public-path 케이스는 `PublicPathSnapshotTest`로 |
| `jpa-release.yml`, `fileserver-certification.yml` | `.github/workflows/` | `016597ac` | job을 `release.yml`로 이동(B2) |
| 삭제·이동한 검사 | 지금 도는 곳 | 게이트 |
| `verifyJpaReadinessRegistry`(카드 구조·선행·task 존재·migration stream) | persistence-jpa `JpaReadinessRegistryTest` | `ci`(leaf `test`) |
| `verifyJpaCandidateEvidence`/`verifyJpaPrimaryFoundationEvidence`(JUnit XML selector·no-skip) | readiness 레인 `requires`(카드 인용 scenario 전부) + `rejectSkipped` | `integrationCheck`, `release.yml` `jpa-release-gate` |
| `verifyJpaReleaseGateTasks`(gate task 존재) | `jpaReleaseQualification` dependsOn(없는 task면 그래프 생성 실패) + `JpaReleaseRenderingTest` | release, `ci` |
| `jpaReleaseQualification`(루트) | persistence-jpa 같은 이름 태스크 | `release.yml` `jpa-release-gate` |
| `JpaAdopterApiSurfaceTest` | `:adapter:outbound:persistence-jpa:verifyJpaApiSurface` adopter 검사 | `ci`(leaf `check`) |
| `verifyEnvKeys`(build-tools) | build-logic `ca.config-contract`, 태스크 동일 | `mainCheck`(`configContractCheck`) |
| `verifyPublicPathSnapshot`/`updatePublicPathSnapshot`(플러그인) | `:app-bootstrap:publicPathSnapshotTest`(루트 별칭 `verifyPublicPathSnapshot`) + 렌더링 단위 테스트 3개(`test`) | `mainCheck`, `releaseCheck`, `ci`(단위) |
| `verifyNoStaleTraceableJars` | 해당 없음 — leaf jar 이름에 revision이 없어 stale jar가 생기지 않음 | — |
| `GrpcStableReleaseGate`/`GrpcAdvancedPromotionGate` | 게이트에 연결된 적 없음(자기 테스트만). release `grpc-stable-release-gate` job은 그대로 | — |
| notification evidence·env registry·mongo lane 계약(`test`) | `notificationDocumentContractTest`·`notificationEnvironmentContractTest`·`mongoDocumentContractTest` | `mainCheck` |
| objectstorage MinIO 레인(`check`) | objectstorage `mainCheck` + `integrationCheck` + object-storage-qualification.yml(경로 필터) | `mainCheck` |
| `releaseCheck`의 `ci` | ci-quality-gates.yml `:ci`(PR·main push) | PR |
| fileserver-pr `architectureTest --tests '*Fileserver*'` | `:ci`의 `architectureCheck`(전체 ArchUnit) | PR |
| legacy whole-`byte[]` 포트 `ObjectStoragePort`·`StoredObject` | `src/application-objectstorage/src/main/java/dev/caskeleton/application/storage/` | `c4a066df` | 한 기능에 한 세대(S1-#17b·S4-#11a). canonical semantic 포트로 대체 |
| legacy 어댑터 `FilesystemObjectStorageAdapter`·`S3ObjectStorageAdapter`와 `ObjectStorageConfig`·`ObjectStorageSettings`(`ca-skeleton.objectstorage.*`) | `src/adapter/outbound/objectstorage/src/main/java/dev/caskeleton/adapter/outbound/objectstorage/` | `c4a066df` | 같은 이유 |
| `LegacyObjectStorageActivationGuard`, `ObjectStorageCapabilitySettings.Legacy`(`app.object-storage.legacy.*`), 바인딩의 legacy namespace 겹침 검사, `docs/objectstorage/env-fields.yaml` legacy 10행 | `src/adapter/outbound/objectstorage/src/main/java/dev/caskeleton/adapter/outbound/objectstorage/config/` | `c4a066df` | 같은 이유 |
| legacy 테스트 `LegacyObjectStorageConfigTest`·`LegacyObjectStorageBehaviorTest`·`FilesystemObjectStorageAdapterTest`·`S3ObjectStorageAdapterTest`·`S3ObjectStorageAdapterIT` | `src/adapter/outbound/objectstorage/src/{test,integrationTest}/java/dev/caskeleton/adapter/outbound/objectstorage/` | `c4a066df` | 대상 코드 삭제 |
| sample legacy 업로드 `UploadPosterImageUseCase`·`LegacyPosterImageController`·`UploadPosterImageCommand`·`StoredObjectResponse`·`PosterWebMapper.toStoredObjectResponse`·`PosterImageApiSettings.Mode.LEGACY`·`LegacyPosterImageUploadCharacterizationTest` | `src/sample-portfolio/src/main/java/dev/caskeleton/sample/portfolio/` | `c4a066df` | canonical `PublishPosterImageUseCase`(mode=publication)가 대체 |
| `FileStateMachine`·`DefaultFileStateMachine`과 bean | `src/application-fileserver/src/main/java/dev/caskeleton/application/fileserver/api/` | `c4a066df` | `FileState.canTransitionTo`로 대체(S1-#13) |
| 인터페이스 `WriterLeaseCoordinator`·`TransferAdmissionController`(구현이 이름을 가짐) | `src/application-fileserver/src/main/java/dev/caskeleton/application/fileserver/{concurrency,quota}/` | `c4a066df` | 구현 1개·대역 0(S1-#6a) |
| content SPI 확장 `AsyncContentStore`·`CopyCapableContentStore`·`CapacityAwareContentStore`·`DelegatedDownloadStore`·`DelegatedDownloadDescriptor`·`StorageCapacity`·`CopyPrecondition` | `src/application-fileserver/src/main/java/dev/caskeleton/application/fileserver/api/content/` | `c4a066df` | 구현·호출 0(S1-#12) |
| `LocalDownloadContentGateway`·`LocalZeroCopyDownloadGateway` | `src/adapter/outbound/fileserver/src/main/java/dev/caskeleton/adapter/outbound/fileserver/platform/local/` | `c4a066df` | 위임만(S1-lead-4), store가 포트를 직접 구현 |
| 예외 서브클래스 17개(`AtomicPublishUnsupported`·`ConcurrentFileModification`·`FileAccessDenied`·`FileNotReady`·`FileTooLarge`·`IntegrityMismatch`·`MalformedRequest`·`MalwareDetected`·`PartialWrite`·`PathOutsideNamespace`·`QuotaExceeded`·`StorageFull`·`StorageUnavailable`·`TransferAdmissionRejected`·`TransferTimeout`·`UnsupportedMediaType`·`UploadExpired` + `Exception`) | `src/application-fileserver/src/main/java/dev/caskeleton/application/fileserver/api/error/` | `c4a066df` | 타입 분기 0, code가 같은 정보(S1-#7) |
| `FileserverWebProperties.defaultNamespace`·`uploadTtl`, `TusProperties.uploadTtl`, `Draft12Properties.uploadTtl` | `src/adapter/inbound/web-fileserver/src/main/java/dev/caskeleton/adapter/inbound/web/fileserver/` | `c4a066df` | 업로드 세션 정책이 `UploadPolicy`로(S5-#10). 설정 키 변화 없음 |
| `ObjectRequestSupport.boundedToken` | `src/application-objectstorage/src/main/java/dev/caskeleton/application/objectstorage/request/ObjectRequestSupport.java` | `c4a066df` | `ObjectModelSupport.requireBoundedToken`과 중복(S1-#17a) |
| `RedisHealthSnapshotProvider` | `src/shared-contract/src/main/java/dev/caskeleton/shared/health/RedisHealthSnapshotProvider.java` | `4fb7943b` | 구현·소비자 0 (A-5b) |
| `opstore` 패키지(`OperationalRecordStorePort`·`OperationalRecord`·`OperationalRecordConflictException`) | `src/shared-contract/src/main/java/dev/caskeleton/shared/opstore/` | `4fb7943b` | 사용처 0 (X1-#6f, S1-#15b, NEW-9b) |
| `DomainContextStrategy`·`DomainContextPropagatorFactory` + 테스트 | `src/shared-contract/src/main/java/dev/caskeleton/shared/concurrency/` | `4fb7943b` | case 하나뿐인 확장 지점 (A-10c) |
| `DomainContextSettings`(`ca-skeleton.domain-context.strategy`) | `src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/concurrency/DomainContextSettings.java` | `4fb7943b` | 선택할 전략이 하나 (A-10c) |
| `RateLimitInterceptor.disabled` + 테스트 | `src/adapter/inbound/web/src/main/java/dev/caskeleton/adapter/inbound/web/ratelimit/RateLimitInterceptor.java` | `4fb7943b` | M2 이후 dead (I-8d) |
| `GraphQlRequestEnvelopeValidator`·`GraphQlHttpRequestEnvelope` + `GraphQlRequestEnvelopeValidatorTest` | `src/adapter/inbound/graphql/src/main/java/dev/caskeleton/adapter/inbound/graphql/http/` | `4fb7943b` | 요청 경로에서 도달 불가 (J-10d) |
| `MigrationFailedException`·`ProfileMismatchException`·`RequiredAdapterDisabledException`·`StartupValidationException` | `src/adapter/outbound/support/src/main/java/dev/caskeleton/adapter/outbound/support/startup/` | `f2857840^`(= `b7187e1b`) | 역할 없는 subclass (S6-#13) |
| `ExternalRequestUrlResolver`의 forwarded 파싱 + env `APP_NOTIFICATION_PLATFORM_CALLBACK_TRUSTED_PROXIES` | `src/adapter/inbound/web-notification/src/main/java/dev/caskeleton/adapter/inbound/web/notification/platform/callback/ExternalRequestUrlResolver.java` | `d54909c4` | 컨테이너(RemoteIpValve)와 다른 두 번째 신뢰 판단 (I-5b) |
| `LegacyOutboxAppendPort` | `src/application-core/src/main/java/dev/caskeleton/application/outbox/LegacyOutboxAppendPort.java` | `6d27356e` | canonical `OutboxAppendPort`로 통일(결정 7) |
| legacy outbox 모델 `NewOutboxEvent`, `OutboxEvent`, `CanonicalClaimedOutboxEvent`, `OutboxPayloadPolicy` (+ `NewOutboxEventTest`, `OutboxPayloadPolicyTest`) | `src/application-core/src/main/java/dev/caskeleton/application/outbox/` | `6d27356e` | append 모델이 `ValidatedIntegrationEvent` 하나. `ClaimedOutboxEvent`는 sealed 합집합이 아니라 canonical record |
| `LegacyOutboxAppendContract` | `src/application-core/src/testFixtures/java/dev/caskeleton/application/outbox/testkit/LegacyOutboxAppendContract.java` | `6d27356e` | `OutboxAppendContract`로 대체 |
| `CanonicalOutboxAppendAdapter` (+ Activation·단위 테스트) | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/outbox/CanonicalOutboxAppendAdapter.java` | `6d27356e` | `OutboxStoreAdapter`가 `OutboxAppendPort`를 직접 구현(트랜잭션 guard 포함) |
| `OutboxEventEntity.payload`·`idempotencyKey` 접근자, claim SQL의 legacy CASE | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/outbox/entity/OutboxEventEntity.java`, `PostgreSqlOutboxClaimRepository`, `H2OutboxClaimRepository` | `6d27356e` | canonical 컬럼만 읽고 씀. 컬럼은 V19에서 nullable로 두고 migration은 수정하지 않음 |
| `OutboxCanonicalTransportRequirementValidator` (+ Validator/Composition 테스트) | `src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/autoconfigure/outbox/OutboxCanonicalTransportRequirementValidator.java` | `6d27356e` | 켜고 끌 canonical 플래그가 없어짐 |
| 설정 키 `ca-skeleton.outbox.canonical-transport-enabled` / env `APP_OUTBOX_CANONICAL_TRANSPORT_ENABLED` | `persistence-jpa.yml`, `docs/registries/env-keys.yaml`, `src/.env.example` | `6d27356e` | 같음 |
| messaging `core/*`: `MessageBroker`, `MessagePublisher`, `OutboundMessage`, `OutboundMessagePublisher`, `DisabledMessagePublisher` (+ `OutboundMessagePublisherTest`) | `src/adapter/outbound/messaging/src/main/java/dev/caskeleton/adapter/outbound/messaging/core/` | `6d27356e` | legacy 발행 경로 삭제. relay는 bridge(`IntegrationEventPublishPort`)만 씀 |
| `OutboxEnvelopeJson` (+ `OutboxCanonicalPublishRoutingTest`) | `src/adapter/outbound/messaging/src/main/java/dev/caskeleton/adapter/outbound/messaging/outbox/OutboxEnvelopeJson.java` | `6d27356e` | envelope은 encoder가 한 번 만들고 bytes 그대로 전달 |
| legacy Kafka seam: `KafkaSender`, `KafkaSenderAutoConfiguration`, `KafkaMessageBroker`, `KafkaAdapterConfig`, `KafkaAdapterSettings`, `BrokerAddress`, `LegacyKafkaMessagingRootAutoConfiguration`, `AutoConfiguration.imports` (+ 테스트 5개) | `src/adapter/outbound/messaging-kafka/src/main/java/dev/caskeleton/adapter/outbound/messaging/kafka/` | `6d27356e` | TLS/SASL 없는 두 번째 producer(X1-#1f, NEW-4a). leaf는 코드 없는 capability 묶음으로 유지 |
| `messaging.yml`의 `kafka.brokers` | `src/adapter/outbound/messaging-kafka/src/main/resources/config/module-defaults/messaging.yml` | `6d27356e` | seam 설정 |
| `WorkLogReservedIntegrationEvent`, `WorkLogReservedIntegrationEventMapper` (+ Mapper 테스트 2개) | `src/sample-portfolio/src/main/java/dev/caskeleton/sample/portfolio/application/event/` | `6d27356e` | `PortfolioEventOutbox` + 계약 `portfolio.worklog.reserved` v1로 대체 |
| `SampleIdempotencyConfig` (executor 복사본) | `src/sample-portfolio/src/main/java/dev/caskeleton/sample/portfolio/bootstrap/idempotency/SampleIdempotencyConfig.java` | `6d27356e` | `composition:idempotency` 사용. Clock·스케줄링만 `SampleSchedulingConfig`로 |
| app-bootstrap `config/capabilities.yml` (이동) | `src/app-bootstrap/src/main/resources/config/capabilities.yml` | `6d27356e` | `composition/idempotency/.../config/module-defaults/idempotency.yml`로 이동 |
| app-bootstrap outbox 조립 `OutboxConfig`·`OutboxSettings`·`OutboxMetrics`·`OutboxRelayScheduler`·`OutboxLeaderElectionToken` (이동) | `src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/autoconfigure/outbox/` | `6d27356e` | `composition:outbox-relay`로 이동 |
| app-bootstrap 멱등성 조립 `IdempotencyProviderSelectionConfig`·`IdempotencySettings` (이동) | `src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/autoconfigure/idempotency/` | `6d27356e` | `composition:idempotency`로 이동 |
| app-bootstrap runtime 배선 tracing 6개, metrics 3개, `DomainContextConfig/Settings`, `PseudonymizationConfig`, `PrivacySettings`, `ManagementSecurityConfig` (이동) | `src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/{autoconfigure/tracing,metrics,concurrency,logging,settings,management/security}/` | `6d27356e` | `composition:service-runtime`으로 이동 |
| sample bootstrap 복사본: `SampleTracingConfig`, `SampleTracingSettings`, `SampleTracingSampleRateResolver`(`staging` 분기), `SampleTracingSamplingEnvironmentPostProcessor`, `SampleMicrometerSpanErrorRecorder`, `SampleMetricsContractConfig`, `SampleDomainContextConfig`, `SamplePseudonymizationConfig`, `SamplePrivacySettings`, `META-INF/spring.factories` | `src/sample-portfolio/src/main/java/dev/caskeleton/sample/portfolio/bootstrap/{tracing,metrics,context,logging,settings}/` | `6d27356e` | 원본과 갈라진 복사본(S6-#7). 공용 모듈 사용 |
| messaging `OutboxRepository.leaseBatch`, 4인자 `claimBatch`, 3인자 `markAmbiguous` | `src/messaging/messaging-reliability-api/src/main/java/dev/caskeleton/messaging/reliability/OutboxRepository.java` | `6d27356e` | main 호출 0. fencing 없는 claim/쓰기 표면(S7-#8) |
| `JdbcOutboxRepository`의 LEASE SQL·`leaseBatch`·`*Unfenced` 4개·`update` helper·손 JSON(`toJson`/`fromJson`/`escape`/`unescape`) | `src/messaging/messaging-outbox-jdbc-postgresql/src/main/java/dev/caskeleton/messaging/outbox/JdbcOutboxRepository.java` | `6d27356e` | 호출 0. 손 JSON reader는 결함(P18-new-1). jsonb 함수로 대체 |
| leaf `messaging-outbox-jdbc-postgresql`, `messaging-inbox-jdbc-postgresql` (코드는 이동) | `src/messaging/messaging-outbox-jdbc-postgresql`, `src/messaging/messaging-inbox-jdbc-postgresql` | `6d27356e` | `messaging-reliability` + `messaging-reliability-jdbc-postgresql`로 재분할(S7-#5b) |
| application-core 테스트 `malformedReportData` | `src/application-core/src/test/java/dev/caskeleton/application/outbox/` (relay 테스트) | `6d27356e` | blank aggregate id를 가진 claim이 canonical 모델에서 만들어질 수 없음 |
| `EventJson`(sample 이벤트 JSON 문자열 조립, P15에서 신설) | `src/sample-portfolio/src/main/java/dev/caskeleton/sample/portfolio/application/event/EventJson.java` | `25de288a` | P18 통합: sample 발행기가 canonical `PortfolioEventOutbox` + encoder로 옮겨 호출자 0 |
| `DomainContextSettings`(`ca-skeleton.domain-context.strategy`, P18이 service-runtime으로 옮긴 사본) | `src/composition/service-runtime/src/main/java/dev/caskeleton/composition/runtime/context/DomainContextSettings.java` | `e1dafd00`(P18 worktree) | P18 통합: P25 A-10c가 전략 선택 설정을 없앰 — `DomainContextConfig`가 `ThreadLocalDomainContextPropagator`를 직접 만든다 |
| `ProviderRuntimeRotator` | `src/adapter/outbound/notification/src/main/java/dev/caskeleton/adapter/outbound/notification/platform/dispatch/ProviderRuntimeRotator.java` | `0ed7bc8d` | S4-#3c: main 참조 0, production 입력 없는 회전 경로 |
| `RuntimeDrainCoordinator` | `.../notification/platform/dispatch/RuntimeDrainCoordinator.java` | `0ed7bc8d` | S4-#3c: rotator만 사용 |
| `CredentialProbe` | `.../notification/platform/dispatch/CredentialProbe.java` | `0ed7bc8d` | S4-#3c: 구현체 0, rotator만 사용 |
| `CredentialValidationException` | `.../notification/platform/dispatch/CredentialValidationException.java` | `0ed7bc8d` | S4-#3c: rotator만 던짐 |
| `NotificationSubmissionService.submit/schedule/accept` | `src/application-notification/.../platform/dispatch/NotificationSubmissionService.java` | `0ed7bc8d` | S1-#10b: main 호출자 0, use case와 3벌 중복 |
| `NotificationPlatformSettings.Provider` 8-인자 생성자 | `.../notification/platform/autoconfigure/NotificationPlatformSettings.java` | `0ed7bc8d` | S4-#15: 테스트 호환용 오버로드 |
| `TemplateRendererRegistry` | `src/application-notification/.../platform/dispatch/TemplateRendererRegistry.java` | `ce863643` | S1-#9: 모든 channel에 같은 renderer |
| `MapTemplateRendererRegistry` | `.../notification/platform/dispatch/MapTemplateRendererRegistry.java` | `ce863643` | S1-#9 |
| `ThymeleafNotificationRenderer` | `.../notification/platform/template/ThymeleafNotificationRenderer.java` | `ce863643` | S1-#9: `CanonicalNotificationRenderer` 위임 래퍼뿐 |
| `ProviderEventProjectorRegistry` | `src/application-notification/.../platform/callback/ProviderEventProjectorRegistry.java` | `ce863643` | S1-#9: 모든 provider에 같은 projector |
| `MapProviderEventProjectorRegistry` | `.../notification/platform/callback/MapProviderEventProjectorRegistry.java` | `ce863643` | S1-#9 |
| `SesDeliveryProjector` | `.../notification/platform/provider/ses/SesDeliveryProjector.java` | `ce863643` | S1-#9: `StandardDeliveryProjector` 상속만 |
| `ProviderCallbackAssembler.projector()`, `AssembledProvider.projector`, `AssembledPlatform.projectors`, `NO_PROJECTOR` 분기 | `.../notification/platform/autoconfigure/*`, `ProviderEventProjectionService.java` | `ce863643` | S1-#9: 슬롯이 늘 같은 규칙을 가리킴 |
| `ProviderRuntime.moveTo`와 `mark*`별 조건 | `.../notification/platform/dispatch/ProviderRuntime.java` | `ce863643` | S4-#14b: 전이표 하나로 대체 |
| `JdkNotificationHttpGateway` | `.../notification/platform/provider/http/JdkNotificationHttpGateway.java` | `bff135d6` | S4-lead-3(결정 17): AWS SDK sesv2로 교체 |
| `NotificationHttpGateway`·`NotificationHttpRequest`·`NotificationHttpResponse`·`NotificationHttpTransportException` | `.../notification/platform/provider/http/` | `bff135d6` | S4-lead-3 |
| `AwsSignatureV4Signer` | `.../notification/platform/provider/ses/AwsSignatureV4Signer.java` | `bff135d6` | S4-lead-3: SDK가 서명 |
| `notificationHttpGateway` bean | `.../notification/platform/autoconfigure/NotificationPlatformCoreConfig.java` | `bff135d6` | S4-lead-3 |
| `JdkNotificationHttpGatewaySecurityTest` | `.../test/.../provider/http/JdkNotificationHttpGatewaySecurityTest.java` | `bff135d6` | 대상 gateway 삭제 |
| `PersistenceJpaConfig.OPT_IN_NOTIFICATION_PACKAGE`, coverage 테스트 opt-in 표 | `src/adapter/outbound/persistence-jpa/.../config/PersistenceJpaConfig.java`, `PersistenceEntityScanCoverageTest.java` | `90fcc8ba` | S2-#1b: 알림 패키지가 leaf 밖으로 |
| `PostgreSqlNotificationBackgroundPassIntegrationTest.replayMarksAnEventWithNoProjectorFailed` | `src/adapter/outbound/persistence-jpa/src/postgresqlIntegrationTest/.../readiness/` | `ce863643` | S1-#9: `NO_PROJECTOR` 분기 삭제 |
| `ca.release-provenance` 플러그인 | `src/build-logic/src/main/java/dev/caskeleton/buildlogic/release/` | `64a83918` | BUILD-O3-5: sourceRevision은 `ca.java-conventions`, provenance 검증은 루트 태스크 하나 |
| app-bootstrap의 `MessagingCapabilityRegistryContractTest` 위치 | `src/app-bootstrap/src/test/java/.../MessagingCapabilityRegistryContractTest.java` | `64a83918` | 결정 29: messaging leaf 테스트로 이동 |
| `BatchMessageHandler`, `BatchMessageDelivery`, `BatchDeliveryMetadata`, `PauseResumeController`, `ProcessingGuarantee` | `src/messaging/messaging-core-api/src/main/java/dev/caskeleton/messaging/api/delivery/` | `423a29c4` | 구현·사용처 0(M-9) |
| `CapabilityRegistry` | `src/messaging/messaging-core-api/src/main/java/dev/caskeleton/messaging/api/destination/CapabilityRegistry.java` | `423a29c4` | 구현·사용처 0(M-9) |
| `DelayedMessagePublisher`, `BlockingMessagePublisher`, `BatchMessagePublisher`, `BatchPublishOptions`, `BatchPublishItemResult`, `BatchPublishResult` | `src/messaging/messaging-core-api/src/main/java/dev/caskeleton/messaging/api/publish/` | `423a29c4` | 구현·사용처 0(M-9), facade 삭제로 구현 0(S7-#9c) |
| `ManualMessageHandler`, `SettlementController` | `src/messaging/messaging-core-api/src/main/java/dev/caskeleton/messaging/api/settlement/` | `423a29c4` | 구현·사용처 0(M-9) |
| 예외 13개 `Message{Authentication,BrokerUnavailable,Consumer,DeadLetter,HandlerTimeout,HeaderRejected,PublishAmbiguous,PublishRejected,Redrive,RetryExhausted,Routing,Settlement,SettlementUnknown}Exception` | `src/messaging/messaging-core-api/src/main/java/dev/caskeleton/messaging/api/error/` | `423a29c4` | 참조 0(S7-#10) |
| `MessagingLifecycle` (+ `MessagingLifecycleTest`) | `src/messaging/messaging-transport-spi/src/main/java/dev/caskeleton/messaging/transport/MessagingLifecycle.java` | `423a29c4` | 구현 0(M-9). 종료 순서는 `MessagingShutdownLifecycle`이 실제로 수행 |
| `KafkaTopologyInspector`, `KafkaBatchConsumerRegistrar` | `src/messaging/messaging-kafka/src/main/java/dev/caskeleton/messaging/kafka/` | `423a29c4` | main 참조 0(S7-#10, S7-#2: batch consume은 결정 10 범위 밖) |
| `ReliableMessagePublisher`, `InboxRecord` | `src/messaging/messaging-reliability-api/src/main/java/dev/caskeleton/messaging/reliability/` | `423a29c4` | 참조 0(S7-#10). outbox append는 canonical `OutboxAppendPort` |
| `DefaultBlockingMessagePublisher`, `DefaultReactiveMessagePublisher`, `DefaultBatchMessagePublisher`, `ReactiveMessagePublisher` (+ `BlockingFacadeTest`, `ReactiveFacadeTest`, `BatchPublisherTest`) | `src/messaging/messaging-spring-boot-starter/src/main/java/dev/caskeleton/messaging/autoconfigure/` | `423a29c4` | starter 밖 참조 0(S7-#9c) |
| `PublishResults` | `src/messaging/messaging-spring-boot-starter/src/main/java/dev/caskeleton/messaging/autoconfigure/PublishResults.java` | `423a29c4` | facade 삭제로 호출자 0(S7-#6b) |
| `MessagingCapabilities`의 읽지 않는 flag 9개(brokerAcknowledgement, replicationOrPersistenceEvidence, perMessageSettlement, batchSettlement, keyedOrdering, replay, brokerTransaction, nativeDeadLetter, topologyManagement) | `src/messaging/messaging-core-api/src/main/java/dev/caskeleton/messaging/api/destination/MessagingCapabilities.java` | `423a29c4` | main 읽기 0(S7-#11) |
| leaf `messaging-schema-api`, `messaging-admin-runtime` (코드는 이동), `messaging-admin-api`(→ `messaging-admin`으로 개명) | `src/messaging/messaging-schema-api`, `src/messaging/messaging-admin-runtime`, `src/messaging/messaging-admin-api` | `423a29c4` | S7-#12 병합 |
| `BrokerSettings`의 Kafka 필드 7개 (starter-kafka `KafkaBrokerSettings`로 이동) | `src/messaging/messaging-spring-boot-starter/src/main/java/dev/caskeleton/messaging/autoconfigure/BrokerSettings.java` | `423a29c4` | broker 중립 starter에서 broker 전용 union 제거(S7-#9b) |
| `IdempotentMessageHandler`, `TransactionalMessageAction`, `InboxResult` | `src/messaging/messaging-reliability-api/src/main/java/dev/caskeleton/messaging/reliability/` | `423a29c4` | consume 계약을 `MessageHandler<T>` 하나로(S7-#2, 결정 10). `InboxResult`는 boolean `reserve`로 만들 수 없는 값(CLAIMED_ELSEWHERE)만 남은 enum |
| `TransactionalInboxHandler` (+ starter bean `transactionalInboxHandler`, `InboxOperationsTest.anAlreadyAppliedMessageIsSafeToSettleButAClaimedOneIsNot`) | `src/messaging/messaging-reliability/src/main/java/dev/caskeleton/messaging/inbox/TransactionalInboxHandler.java` | `423a29c4` | `InboxMessageHandler`(MessageHandler 데코레이터)로 대체(S7-#2) |
| untyped `DefaultDeliveryProcessor(Function<MessageEnvelope<EncodedMessage>, HandleResult>, …)` 생성자 | `src/messaging/messaging-runtime-core/src/main/java/dev/caskeleton/messaging/runtime/DefaultDeliveryProcessor.java` | `423a29c4` | typed `MessageHandler` 목록을 받는 형태로 교체(S7-#2) |
| `CapabilityTier` (→ `ApiTier`로 개명), `CompatibilityMatrix.Tier` (→ `SupportGrade`) | `src/messaging/messaging-policy/src/main/java/dev/caskeleton/messaging/policy/CapabilityTier.java`, `src/messaging/messaging-testkit/src/main/java/dev/caskeleton/messaging/testkit/CompatibilityMatrix.java` | `423a29c4` | 등급 용어 정리(S7-#14) |
| `api 'io.projectreactor:reactor-core'`, `testImplementation 'io.projectreactor:reactor-test'` | `src/messaging/messaging-spring-boot-starter/build.gradle` | `423a29c4` | reactive facade 삭제로 노출 이유 소멸(S7-#9c) |
| SDK pub/sub 연산 표면(`RedisPubSubOperations`, `RedisShardedPubSubOperations`, `ReactiveRedisPubSubOperations`, `ReactiveRedisShardedPubSubOperations`, `PubSubChannel`, `PubSubPattern`, `ShardedPubSubChannel`, `Subscription`, `LettuceRedisPubSubOperations`, `LettuceRedisShardedPubSubOperations`, `LettuceReactiveRedisPubSubOperations`, `LettuceReactiveRedisShardedPubSubOperations`, `LiveSubscription`, `PubSubCodecs`, `PubSubOperationRequests`, `SubscriptionFlux`)과 테스트 `InMemoryRedisPubSubGateway`·`RedisPubSubOperationsContractTest` | `src/adapter/outbound/redis-sdk/src/{main,test}/java/dev/caskeleton/adapter/outbound/cache/redis/sdk/{api/operations,api/reactive,lettuce/operations}/` | `423a29c4` | 전송(`RedisPubSubGateway`) main 구현이 없어 동작 불가(G-6b) |
| `RedisPubSubGateway`, `RedisConnectionKind.PUBSUB`, `RedisCredentialRole.PUBSUB` | `src/adapter/outbound/redis-runtime/src/main/java/dev/caskeleton/adapter/outbound/cache/redis/sdk/lettuce/{operations,connection}/` | `423a29c4` | 위와 같음 |
| `RedisSdkSettings.PubSub`·`Authentication.pubsubCredentialReference`, env 키 `APP_REDIS_PUBSUB_BUFFER_CAPACITY`·`APP_REDIS_AUTHENTICATION_PUBSUB_CREDENTIAL_REFERENCE` | `src/adapter/outbound/redis-runtime/.../sdk/config/RedisSdkSettings.java`, `docs/registries/env-keys.yaml`, `src/.env.example` | `423a29c4` | 동작하지 않는 옵션은 키를 두지 않는다(G-4i) |
| `RedisCapability.SHARDED_PUBSUB`, `RedisOperationContext.PATTERN_SUBSCRIBE` | `src/adapter/outbound/redis-sdk/.../sdk/api/RedisCapability.java`, `.../sdk/lettuce/operations/RedisOperationContext.java` | `423a29c4` | 사용처(pub/sub 연산) 삭제 |
| `RedisCredentialRole`(enum) | `src/adapter/outbound/redis-runtime/.../sdk/lettuce/connection/RedisCredentialRole.java` | `423a29c4` | 열린 `RedisAccount` 값으로 대체 — runtime은 자기 계정 2개만 알고 SDK가 admin 계정을 기여(G-7c) |
| `RedisSdkSettings.Blocking`·`Transaction`·`Admin`과 env 키 `APP_REDIS_ADMIN_ENABLED`·`APP_REDIS_ADMIN_CREDENTIAL_REFERENCE`·`APP_REDIS_BLOCKING_MAX_CONNECTIONS`·`APP_REDIS_TRANSACTION_MAX_CONNECTIONS` | `src/adapter/outbound/redis-runtime/.../sdk/config/RedisSdkSettings.java`, `docs/registries/env-keys.yaml`, `src/.env.example` | `423a29c4` | SDK 전용 lane·계정. SDK `RedisSdkComposition` 코드 설정으로 이동(G-7c, S3-#3b) |
| `InMemoryGatewayAccess` | `src/adapter/outbound/redis-runtime/src/testFixtures/.../sdk/lettuce/operations/InMemoryGatewayAccess.java` | `423a29c4` | cache-redis 테스트는 runtime testFixtures `InMemorySemanticRedisCommands`를 직접 쓴다. semantic 스크립트 에뮬레이션은 그 fake로 이동(SDK의 `InMemoryRedisCommandGateway`에서는 제거) |
| `IdempotencyScriptsConcurrencyContractTest` | `src/adapter/outbound/cache-redis/src/test/java/dev/caskeleton/adapter/outbound/cache/redis/idempotency/` | `423a29c4` | reflection으로 `digests` Map 구조를 고정하던 테스트. 슬롯이 `RegisteredLuaScript` final 필드가 되어 대상이 없음; 동작은 `RegisteredLuaScriptTest`가 검증 |
| `SecretSourceValidator.REDIS_ENABLED_PROPERTY`와 Redis 역할 prefix 분기(`isRedisMaterial`, `isRedisRoleSelected`, `isRedisCacheBound`, `isSelected`), `REQUIRED_PROD_SECRETS`의 Redis 8개 | `src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/runtime/SecretSourceValidator.java` | `423a29c4` | cache-redis `RedisProductionSecrets`가 기여(S6-#2c) |
| shared `RateLimitBounds.MAXIMUM_CLEANUP_GRACE`·`MAXIMUM_CLOCK_REGRESSION`, `EdgeRateLimitProviderNeutralContractTest.allPortableAlgorithmsHaveBoundedProviderNeutralPolicies` | `src/shared-contract/src/{main,test}/java/dev/caskeleton/shared/ratelimit/` | `423a29c4` | 정책 타입이 cache-redis로 이동(S1-#15c). 정책 검증 테스트는 이동한 `RateLimitPolicyTest`에 있음 |
| `WebRequestContext` | `src/adapter/inbound/web/src/main/java/dev/caskeleton/adapter/inbound/web/core/WebRequestContext.java` | `36ba0810` | store 호출 0 → 선언한 컨트롤러는 항상 500, 소비자 0 (I-1c) |
| `ExternalRequestContext` | `src/adapter/inbound/web/src/main/java/dev/caskeleton/adapter/inbound/web/core/ExternalRequestContext.java` | `36ba0810` | `WebRequestContext` 전용 |
| `WebMvcRequestContextArgumentResolver`·`WebMvcRequestContextHolder` | `src/adapter/inbound/web/src/main/java/dev/caskeleton/adapter/inbound/web/mvc/context/` | `36ba0810` | I-1c |
| `webMvcRequestContextConfigurer` bean | `src/adapter/inbound/web/src/main/java/dev/caskeleton/adapter/inbound/web/mvc/autoconfigure/WebMvcPlatformAutoConfiguration.java` | `36ba0810` | I-1c |
| app-core `Sha256` | `src/application-core/src/main/java/dev/caskeleton/application/messaging/contract/Sha256.java` | `36ba0810` | shared-contract `digest.Sha256`로 이동 |
| `MessageDigestPort` | `src/application-notification/src/main/java/dev/caskeleton/application/notification/platform/dispatch/MessageDigestPort.java` | `36ba0810` | stdlib 포장 포트(X1-#10b) |
| `Sha256MessageDigestAdapter`·`NotificationDigest` | `src/adapter/outbound/notification/src/main/java/dev/caskeleton/adapter/outbound/notification/platform/template/` | `36ba0810` | 위 포트의 adapter·SHA-256 헬퍼 |
| `JpaStreamScope` | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/springdata/JpaStreamScope.java` | `36ba0810` | 읽기 전용 caller 트랜잭션 guard를 `transaction/CallerTransaction.requireReadOnly`로 합침(JPA API surface 순증 0) |
| web `MdcKeys` | `src/adapter/inbound/web/src/main/java/dev/caskeleton/adapter/inbound/web/observability/MdcKeys.java` | `36ba0810` | shared-contract `observability.MdcKeys`로 이동(X2-P2-5) |
| `DurableOperationJpaRepositoryShapeTest` | `src/adapter/outbound/persistence-jpa/src/test/java/dev/caskeleton/adapter/outbound/persistence/operation/DurableOperationJpaRepositoryShapeTest.java` | `36ba0810` | `ScopedRowRepositoryShapeTest`로 흡수(테스트) |
| notification `UuidV7Generator` 비트 배치 구현 | `src/adapter/outbound/notification/src/main/java/dev/caskeleton/adapter/outbound/notification/platform/dispatch/UuidV7Generator.java` | `36ba0810` | 클래스는 남기고 구현을 uuid-creator로 교체(S1-lead-2) |
| `poster.image-attached` v1 이벤트(`PosterEventPublisher.publishImageAttached`, `PosterImageAttached`, `PosterImageAttachedPayload`, `PortfolioEventContracts.POSTER_IMAGE_ATTACHED`, schema) | `src/sample-portfolio/src/main/java/dev/caskeleton/sample/portfolio/{domain/poster/PosterImageAttached.java,application/event/PosterImageAttachedPayload.java}`, `src/sample-portfolio/src/main/resources/contracts/messaging/poster.image-attached/` | `36ba0810` | legacy 업로드 삭제 뒤 호출자 0(P24-new-2·P25-new-2) |
| fileserver inbound 서비스 인터페이스 6개(`UploadApplicationService`, `FinalizeUploadService`, `SingleShotUploadService`, `DownloadApplicationService`, `FileLifecycleService`, `FileserverAdminService`)와 구현 `DefaultUploadApplicationService`·`DefaultFinalizeUploadService`·`DefaultSingleShotUploadService`·`DefaultDownloadApplicationService`·`DefaultFileLifecycleService`·`DefaultFileserverAdminService`, `download/DownloadRequest` | `src/application-fileserver/src/main/java/dev/caskeleton/application/fileserver/{upload,download,lifecycle,admin}/` | `36ba0810` | 결정 32: 연산별 `port.in` use case로 대체(S1-#6b·S1-#18b) |
| `FileserverDownloadLifecycleConfiguration`, `FileserverMaintenanceServiceConfiguration`의 admin 서비스 bean | `src/adapter/outbound/fileserver/src/main/java/dev/caskeleton/adapter/outbound/fileserver/platform/autoconfigure/` | `36ba0810` | application use case 조립을 composition root(`composition:fileserver-platform`)로 |
| `FileserverUploadServiceConfiguration`(→ `FileserverUploadSupportConfiguration`로 개명, 서비스 bean은 use case 설정으로) | `src/composition/fileserver-platform/src/main/java/dev/caskeleton/composition/fileserver/` | `36ba0810` | 같음 |
| `ca.auxiliary-source-set` 플러그인(`AuxiliarySourceSetPlugin`·`Extension`·`Spec`)과 `AuxiliarySourceSetConventionTest` | `src/build-logic/src/{main,test}/java/dev/caskeleton/buildlogic/auxiliary/` | `4f4bd1fd` | Gradle `jvm-test-suite`로 대체(BUILD-O3-5) |
| `JpaAdapterComponentsConfig` | `src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/config/JpaAdapterComponentsConfig.java` | `0ebb77b5` | 8개 패키지 `@ComponentScan` → `autoconfigure/JpaAdapterBeansConfig`의 명시적 `@Bean`(S2-#8a, `66263858`) |
| `JpaAdapterComponentsConfigTest` | `src/adapter/outbound/persistence-jpa/src/test/java/dev/caskeleton/adapter/outbound/persistence/config/JpaAdapterComponentsConfigTest.java` | `0ebb77b5` | 스캔 대상 패키지 목록을 고정하던 테스트 — 스캔 삭제로 대상 없음, `JpaAdapterBeansConfigTest`로 대체 |
| `IdempotencyActivationContractTest` | `src/adapter/outbound/persistence-jpa/src/test/java/dev/caskeleton/adapter/outbound/persistence/idempotency/jpa/IdempotencyActivationContractTest.java` | `0ebb77b5` | `IdempotencyReaper` 클래스의 `@ConditionalOnProperty`를 읽던 테스트 — 조건이 bean 설정으로 옮겨가 `IdempotencyReaperWiringTest`(실제 context)로 대체 |
| `PersistenceEntityScanCoverageTest.operationAndLiveEventAdaptersAreScanned` | `src/adapter/outbound/persistence-jpa/src/test/java/dev/caskeleton/adapter/outbound/persistence/config/PersistenceEntityScanCoverageTest.java` | `0ebb77b5` | 같은 이유(스캔 목록 고정) — `JpaAdapterBeansConfigTest.everyAdapterTheScanUsedToRegisterIsDeclaredAsABean`로 대체 |
| `MongoPlatformWiringTest.theMappingConfigurationCarriesThePlatformSwitch`·`thePlatformIsOffUnlessTheSwitchIsOn` | `src/adapter/outbound/persistence-mongo/src/test/java/dev/caskeleton/adapter/outbound/mongo/autoconfigure/MongoPlatformWiringTest.java` | `0ebb77b5` | 반복 스위치를 고정하던 테스트 — 반복 조건을 없애고 ArchUnit 두 규칙으로 대체 |
| `PortfolioEventContracts` | `src/sample-portfolio/src/main/java/dev/caskeleton/sample/portfolio/application/event/PortfolioEventContracts.java` | `0ebb77b5` | 공유 registry가 `event` → 모든 기능 역방향 의존 — `poster/PosterEventContracts`·`posterimage/PosterImageEventContracts`로 분할, `all()`은 테스트로(S6-#10a, `62a669c8`) |
| `HttpClientEnvironmentKeys`(설정 record 트리를 리플렉션으로 순회해 env 이름 역산·거부) | `src/adapter/outbound/httpclient/src/main/java/dev/caskeleton/adapter/outbound/httpclient/autoconfigure/HttpClientEnvironmentKeys.java` | `0ebb77b5` | S3-lead-2: env 오타 거부를 `StrictSettingsBinder`가 모든 capability에 대해 한다. manifest 도출은 `HttpClientPlatformEnvManifestTest`로 |
| `StrictSettingsBinder.bind(env, prefix, type, Predicate<ConfigurationPropertySource>)` overload | `src/adapter/outbound/support/.../StrictSettingsBinder.java` | `0ebb77b5` | httpclient 전용 우회였다. system env 제외가 기본 동작이 됨 |
| 설정 키 `app.httpclient.clients[N].timeout.streaming-idle`(`APP_HTTPCLIENT_CLIENTS_N_TIMEOUT_STREAMING_IDLE`)과 `TimeoutSettings.streamingIdle`·`HttpClientPlatformSettings.Timeout.streamingIdle` | `src/adapter/outbound/httpclient/.../profile/TimeoutSettings.java`, `docs/httpclient/env-fields.yaml` | `0ebb77b5` | P11-new-1: 바인딩만 되고 읽는 곳 없음(capability 규칙 3) |
| yml 키 `ca-skeleton.rate-limit.{limit,window,algorithm}` | `src/app-bootstrap/src/test/resources/application-test.yml`, `src/sample-portfolio/src/systemTest/resources/application-test.yml` | `0ebb77b5` | 읽는 코드 없음. `app.rate-limit` 아래로 옮기면 web `EdgeRateLimitTransportSettings` 트리에 섞인다 |
| `SecretSourceValidator`의 `RELATIONAL_PERSISTENCE_PROPERTY`·`isRelationalPersistenceOn()`(모듈 스위치 해석) | `src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/runtime/SecretSourceValidator.java` | `0ebb77b5` | P22-new-1: persistence-jpa가 기여 |
| 설정 키 `app.notification.platform.smtp.max-concurrency`(이름 변경 → `dispatch-concurrency`, env `APP_NOTIFICATION_PLATFORM_SMTP_DISPATCH_CONCURRENCY` 그대로) | `NotificationSmtpSettings.java`, `notification.yml` | `0ebb77b5` | P20-new-1 |
| Redis ACL `+@pubsub`·`&prod:*`(application 계정 2개) | `infra/redis-sdk/acl/*.acl` | `0ebb77b5` | P22-new-2 |
+4 -3
View File
@@ -60,11 +60,12 @@ GitHub Actions 워크플로는 `kubectl apply`, `helm upgrade`, `argocd app sync
| Argo CD Application 정의 | **없음.** GitOps 저장소에 둘 예정 |
| CI에서의 클러스터 접근 | 없음 — 유일했던 `kubectl apply`는 제거됨 |
`fileserver-certification.yml`은 예외처럼 보이지만 아니다. PVC 매니페스트가 여전히 ReadWriteOnce를
`release.yml`의 fileserver certification 잡(`fileserver-pvc-certification` 등, 예전
`fileserver-certification.yml`)은 예외처럼 보이지만 아니다. PVC 매니페스트가 여전히 ReadWriteOnce를
선언하는지 **파일만** 확인하고, 클러스터에는 아무것도 적용하지 않는다. 실제 클러스터에서의 인증은
운영자가 `infra/fileserver/kubernetes/pvc-certification-job.yaml`을 직접 실행하고
`docs/fileserver/storage-certification.md`에 기록한다. 이름을 `fileserver-release.yml`에서 바꾼 이유가
이것이다 — 이 워크플로는 릴리스하지 않는다.
`docs/fileserver/storage-certification.md`에 기록한다. 잡 이름이 "release"가 아니라 "certification"인
이유가 이것이다 — 이 잡은 릴리스하지 않는다.
## 규칙
@@ -4,7 +4,7 @@ Every capability in `:grpc-advanced:*`, its grade, and what it would take to rai
`GrpcAdvancedSupportMatrix` is the machine-readable form; `GrpcAdvancedCapability.defaultGrade`
carries the same values.
All capabilities are off by default. Flags are `ca-skeleton.grpc.advanced.<capability>.enabled`.
All capabilities are off by default. Flags are `app.grpc.advanced.<capability>.enabled`.
## Grades
@@ -29,7 +29,7 @@ All capabilities are off by default. Flags are `ca-skeleton.grpc.advanced.<capab
| Custom load balancer | `custom-load-balancer` | `EXPERIMENTAL` | — |
| Proxyless xDS | `xds` | `EXPERIMENTAL` | xDS control plane |
| gRPC-Web | `grpc-web` | `ADVANCED_STABLE` | gRPC-Web proxy |
| Servlet HTTP/2 | `servlet-compat` | `ADVANCED_STABLE` | Servlet container |
| Servlet HTTP/2 | `servlet-compat` | `ADVANCED_STABLE` (flag only; no Servlet transport code since 2026-09-25) | Servlet container |
| Spring Integration bridge | `integration-bridge` | `ADVANCED_STABLE` | — |
| Reactor adapter | `reactor` | `ADVANCED_STABLE` | — |
| Kotlin coroutine / Flow | `kotlin` | `ADVANCED_STABLE` | Kotlin toolchain |
@@ -42,14 +42,12 @@ implemented and tested in this repository. What no capability has is evidence fr
`GrpcAdvancedPromotionEvidence` for each one is empty, and no promotion has been granted.
**Four capabilities cannot produce meaningful evidence here at all**, because the infrastructure they
need is absent. `GrpcAdvancedInfrastructureTestkit.missingInfrastructure` names them, and a suite that
runs without its infrastructure passes and establishes nothing.
need is absent (gRPC-Web proxy, Servlet container, xDS control plane, Kotlin toolchain), and a suite
that runs without its infrastructure passes and establishes nothing.
**Kotlin is the sharpest case.** This repository has no Kotlin toolchain, so
`GrpcKotlinCompatibilityGate.supportableHere()` returns false and always will until one exists. The
four contract requirements — one schema source shared with Java, coroutine cancellation propagated,
Flow backpressure inside the Stable buffer bounds, platform evidence types preserved — are checkable
without a toolchain and are checked. The compile lane is not.
**Kotlin is the sharpest case.** This repository has no Kotlin toolchain, so Kotlin is not
supportable here until one exists. Only the Java-side coroutine cancellation bridge
(`GrpcCoroutineContextBridge`) is implemented and tested; there is no compile lane.
## Promotion thresholds
+10 -8
View File
@@ -4,8 +4,10 @@ What the Stable gRPC platform (`:grpc:*`) is certified against, what it is only
what is merely watched. The distinction is the point: "works with Spring Boot" is not a statement
anyone can act on.
`GrpcCompatibilityMatrix.caSkeleton()` is the machine-readable form of this table, and
`GrpcStableReleaseGate` blocks a release when a certified lane has no result or a failing one.
The release gate is the `grpc-stable-release-gate` job in `.github/workflows/release.yml`: each
certified lane is a strict test lane that fails when it runs nothing. The in-code
`GrpcCompatibilityMatrix`/`GrpcStableReleaseGate` pair was removed (review 2026-09-24 S5-lead-4):
no production or build code called it, so it gated nothing.
## Lanes
@@ -53,13 +55,13 @@ tested the adapter and not the transport.
| | Where it lives |
| --- | --- |
| Client streaming, bidirectional streaming | `grpc-advanced-streaming` |
| Manual flow control | `grpc-advanced-streaming` |
| Hedging | `grpc-advanced-resilience` |
| Custom name resolver, custom load balancer | `grpc-advanced-resilience` |
| xDS | `grpc-advanced-resilience` |
| Client streaming, bidirectional streaming | `grpc-advanced` (`streaming`) |
| Manual flow control | `grpc-advanced` (`streaming`) |
| Hedging | `grpc-advanced` (`resilience`) |
| Custom name resolver, custom load balancer | `grpc-advanced` (`resilience`) |
| xDS | `grpc-advanced` (`resilience`) |
| gRPC-Web, Servlet HTTP/2, Spring Integration, Reactor, Kotlin | `grpc-advanced-compat` |
| Channelz / CSDS diagnostics | `grpc-advanced-diagnostics` |
| Channelz / CSDS diagnostics | `grpc-advanced` (`diagnostics`) |
## Current release status
+18 -8
View File
@@ -1,9 +1,7 @@
# Fileserver configuration
Every key below lives under `app.fileserver-platform` (environment form
`APP_FILESERVER_PLATFORM_*`). That namespace is the HTTP platform's alone: `app.fileserver.*`
belongs to the R2 tabular publication capability and `app.file-export.*` to the R1 CSV export, and
the three are deliberately separate so switching one on cannot switch on another.
`APP_FILESERVER_PLATFORM_*`).
While `app.fileserver-platform.enabled` is false none of these keys is bound at all — the
auto-configuration that binds them is not processed — so a malformed value in a block nobody
@@ -16,14 +14,14 @@ exposes.
## Minimum to start
```yaml
ca-skeleton:
fileserver:
app:
fileserver-platform:
enabled: true
instance-id: ${HOSTNAME} # writer-lease owner; must be unique per node
storage:
root: /var/lib/backend/files # absolute, outside any webroot or config dir
security:
access-policy: role-based # or supply your own FileAccessPolicy bean
access-policy: role-based # or supply your own FileAccessPolicyPort bean
observability:
fingerprint-key: ${FILESERVER_FINGERPRINT_KEY}
```
@@ -32,7 +30,7 @@ Startup fails, rather than degrading, when any of these is missing or unsafe:
| Condition | Why it is fatal |
| --- | --- |
| `security.access-policy` left at `required` with no `FileAccessPolicy` bean | a file capability that authorizes by default is worse than one that refuses to start |
| `security.access-policy` left at `required` with no `FileAccessPolicyPort` bean | a file capability that authorizes by default is worse than one that refuses to start |
| `observability.fingerprint-key` unset while metrics are on | an unkeyed digest of an enumerable identifier is reversible |
| the storage root fails a mandatory capability probe | a volume that cannot create atomically, keep staging and content on one FileStore, or refuse symlinks is unsafe, not degraded |
| `storage.publish-mode: atomic-move-required` on a volume where the probe could not prove an atomic move | the configured guarantee cannot be delivered |
@@ -47,6 +45,13 @@ Startup fails, rather than degrading, when any of these is missing or unsafe:
| `write-roles` | `ROLE_FILE_WRITE` | grants create, append, finalize, delete, copy, move |
| `admin-roles` | `ROLE_FILE_ADMIN` | grants reverify and force-delete, and gates `/internal/fileserver/**` at the servlet chain |
These roles decide the tier inside each operation. In front of it, every operation's use case
carries a `file:*` permission that the web adapter's method security checks against
`app.authz.role-permissions`; `security.yml` grants `file:read` to `ROLE_FILE_READ`,
`file:upload`, `file:delete`, `file:copy` and `file:move` to `ROLE_FILE_WRITE`, and `file:admin` to
`ROLE_FILE_ADMIN`. Renaming a tier role here means mapping the new name there as well, or the
caller is refused before the tier is consulted (`docs/fileserver/design-deviations.md` §5).
There is no anonymous-read switch. Every Fileserver route is authenticated by the servlet chain
before any application policy is consulted, so such a setting could only ever have described a
permission the transport had already refused — a configuration that reads as if it grants access
@@ -119,7 +124,7 @@ Set `inline-safe-profile: true` only when downloads are never served inline from
| Key | Default | Meaning |
| --- | --- | --- |
| `instance-upload-permits` | `16` | concurrent uploads this node admits |
| `scope-upload-permits` | `4` | concurrent uploads one namespace admits |
| `scope-upload-permits` | `4` | concurrent uploads one caller (principal) admits; over it is a retryable `429` |
| `direct-download-permits` | `64` | concurrent non-delegated downloads |
| `soft-high-water` | `0.70` | storage fraction at which pressure is reported |
| `hard-high-water` | `0.85` | storage fraction at which uploads are refused |
@@ -143,6 +148,11 @@ without it still queues cleanup items; another node or an operator reclaims them
eight times is abandoned rather than retried forever — it stays visible to an operator, parked
rather than discarded.
Each pass also expires uploads whose `expiresAt` has passed (the record becomes `EXPIRED` and its
staged bytes are queued), purges orphans the admin plane retired to quarantine, and runs
reconciliation over stale `UPLOADED`/`VERIFYING`/`FAILED` records, so an ambiguous publish settles
without an operator.
## Management plane — `admin`
| Key | Default | Meaning |
+42 -38
View File
@@ -12,7 +12,7 @@ A create that fails after the record exists must end in `FAILED`, but the table
The record therefore walks `CREATED → UPLOADING → FAILED`, which is also the honest reading: the
upload had been admitted before it failed.
Pinned by `UploadApplicationServiceTest` (application-core).
Pinned by `ResumableUploadUseCasesTest` (application-fileserver).
### 2. `ContentKey`'s alphabet admits a leading separator
@@ -28,7 +28,7 @@ Deleting a file that is mid-verification has no legal transition. The lifecycle
with `409 FILE_NOT_READY` rather than inventing an edge, which matches the allowed-state list the
JPA `markDeleting` statement already enforced.
Pinned by `FileLifecycleServiceTest`.
Pinned by `FileLifecycleUseCasesTest`.
### 4. `If-Match` is specified as an ETag but the lifecycle was designed around the row version
@@ -36,7 +36,7 @@ The HTTP contract sends an entity tag; the metadata store guards on a numeric ve
takes `Optional<String> expectedEtag` and compares against the record's strong validator, so the
precondition a client sends is the precondition that is checked.
Pinned by `FileLifecycleServiceTest`.
Pinned by `FileLifecycleUseCasesTest`.
### 5. The filename policy left `:` intact
@@ -65,11 +65,11 @@ find. Added in the same migration, with a check constraint that an item names ex
Pinned by `PostgreSqlFileserverReclamationIntegrationTest`.
### 8. `ContentReferenceLedger` and `StagingUploadLocator`
### 8. `ContentReferenceLedgerPort` and `StagingUploadLocatorPort`
The orphan scan must ask whether a record still claims a physical object, and reconciliation must
map a file back to the upload that last staged it. Neither question is answerable through the
design's `FileMetadataStore` or `UploadSessionStore` as written. Rather than widen those
design's `FileMetadataPort` or `UploadSessionPort` as written. Rather than widen those
design-fixed interfaces, both are narrow single-method ports.
Pinned by `PostgreSqlFileserverReclamationIntegrationTest` and `LocalOrphanScanAdapterTest`.
@@ -80,7 +80,7 @@ Pinned by `PostgreSqlFileserverReclamationIntegrationTest` and `LocalOrphanScanA
Nothing links a reservation row to the upload that took it, and the design deliberately reclaims
stragglers by TTL and the `STALE_QUOTA_RESERVATION` cleanup type rather than threading a reservation
id through the upload session. `QuotaCommitGateway` therefore settles the oldest live reservation in
id through the upload session. `QuotaCommitPort` therefore settles the oldest live reservation in
the file's namespace.
Which row closes does not change any quota decision: enforcement sums reserved and committed bytes
@@ -97,7 +97,7 @@ Task 22 asks for zero copy on local files; §19 forbids a `Path` leaving the sto
of the plan forbids adding `Path` to the content store. WebFlux's zero-copy API takes a `Path`, so
that route is closed.
The servlet path takes the other one: `ZeroCopyDownloadGateway` receives a `WritableByteChannel` from
The servlet path takes the other one: `ZeroCopyDownloadPort` receives a `WritableByteChannel` from
the transport and the storage adapter performs `FileChannel.transferTo` into it. That is a genuine
kernel-level transfer with no filesystem concept leaving storage. The reactive path continues to
stream with bounded demand.
@@ -165,8 +165,8 @@ an extension point for a backend this template does not ship:
- `AsyncContentStore` — for a backend whose native client is non-blocking. The local platform is
blocking, and the reactive transport bridges to it on a dedicated I/O scheduler.
- `CapacityAwareContentStore` — capacity is reported through `StorageHealthPort` and
`StorageUsageProbe`, which the local platform implements.
- `CopyCapableContentStore` — server-side copy is delivered by `CopyContentGateway`; the local
`StorageUsagePort`, which the local platform implements.
- `CopyCapableContentStore` — server-side copy is delivered by `CopyContentPort`; the local
platform has no cheaper primitive than a streamed copy.
- `DelegatedDownloadStore` — delegation is delivered at the transport boundary by the nginx
`X-Accel-Redirect` strategy, which needs no store participation.
@@ -174,40 +174,44 @@ an extension point for a backend this template does not ship:
`ContentStoreCapabilities` reports what the running store actually supports, so no unimplemented SPI
is advertised as available.
## Known deviation from the repository's application-layer contract
## The repository's application-layer contract
### 5. Fileserver application services are not `CommandUseCase` / `QueryUseCase`
### 5. Fileserver operations are use cases (resolved, owner decision 32)
`src/application-core/CLAUDE.md` requires every inbound port implementation to extend
`CommandUseCase` or `QueryUseCase` and to carry `@UseCaseCapability`, which declares its transaction
mode, idempotency and repository access. The Fileserver instead exposes multi-method services —
`UploadApplicationService`, `DownloadApplicationService`, `FileLifecycleService`,
`FileserverAdminService` and their `Default*` implementations.
Every operation the transport reaches is a `CommandUseCase` or `QueryUseCase` behind a one-method
port in `application.fileserver.port.in` — create, append, status, cancel, finalize and the
single-request upload; describe, prepare, open and transfer for downloads; delete, copy and move;
and the eight management-plane operations. Each implementation (`*ApplicationUseCase`) declares its
`@UseCaseCapability`, so the ArchUnit rules that check transaction mode, repository access and
outbound calls now see the Fileserver like every other feature.
This is a real deviation, not an oversight, and it is unenforced: the ArchUnit rules
`inbound_port_implementations_end_with_use_case` and
`inbound_port_implementations_declare_capability` only match types that implement `UseCase`, so a
service that never does is silently exempt. The capability contract that every other feature in
this repository declares is therefore absent here.
Two authorities guard a write, and both stay:
Two things follow from it. The transaction mode of each operation is expressed only by which
`TransactionPort` method the body happens to call, rather than declared and checked. And the
application layer holds transport policy it would not hold if each operation were a use case with
its own command: HTTP status codes on `FileserverErrorCode`, `Range` and conditional-request
parsing in `api.transfer`, and `Content-Disposition` construction.
| Check | Where | Decides |
| --- | --- | --- |
| `@RequiresPermission("file:…")` | the use case's proxy, enforced by the web adapter's method security | whether the caller's roles grant the operation at all |
| `FileAccessPolicyPort` | inside the use case, before any side effect | the tier (read/write/admin), and that the caller owns the file in its tenant |
The status mapping in particular is a deliberate trade rather than an accident. It lives in
`application-core` so the servlet transport, the reactive transport and the Nginx delegation path
cannot answer the same failure with three different statuses. Moving it to the transport layer
resolves the layering complaint and reintroduces exactly that drift, which is why this is an
architecture decision rather than a cleanup.
The permissions are `file:read` (describe, download, upload status), `file:upload` (create,
append, finalize, cancel, the single-request upload), `file:delete`, `file:copy`, `file:move` and
`file:admin` (every management-plane operation). `security.yml` grants them to `ROLE_FILE_READ`,
`ROLE_FILE_WRITE` and `ROLE_FILE_ADMIN` — the fileserver's own default tier roles — so a caller
holding a tier holds its permissions. A deployment that renames the tier roles, or supplies its own
`FileAccessPolicyPort` under other role names, maps those names in
`app.authz.role-permissions` too; `security.access-policy: unenforced` relaxes only the
tier and ownership check, never the permission gate.
**Status: open, deliberately unresolved in this change set.** Closing it means roughly thirty
command/query use cases, a decision about where the shared status vocabulary lives, and a change to
the ArchUnit rules so a service that bypasses the contract fails the build instead of being exempt
from it. That belongs in its own ADR with its own review, and doing it inside a correctness patch
would mix a large mechanical refactor into changes that need to be readable.
The resumable transfers run on the transfer pool, and method security reads the security context
of the calling thread, so `BlockingTransferExecutor` carries the request's context onto the worker
(`BlockingTransferExecutorSecurityContextTest`). Without it an authenticated append was refused as
anonymous.
Nothing here is pinned by a test, because the deviation is the absence of a constraint. The next
step is the ADR, not another test.
What is not a use case is what no transport calls: `CleanupService` and
`FileReconciliationService` are driven by background workers with no caller identity, and a
mutating use case must declare a permission a scheduler could not hold.
`FileserverUseCaseContractDeviationTest` freezes that list.
The HTTP status vocabulary on `FileserverErrorCode` stays in the application layer, for the reason
this section used to give: the servlet transport and the Nginx delegation path must not answer the
same failure with different statuses.
+39 -11
View File
@@ -56,7 +56,7 @@ port rather than the public one.
| `401` | unauthenticated |
| `403` / `404` | denied, or hidden under the existence-hiding profile |
| `409` | state, offset, or lease conflict |
| `410` | expired upload resource |
| `410` | expired or ended (cancelled, rejected, quarantined) upload resource |
| `411` | `require-content-length` profile with no length |
| `412` | precondition failed |
| `413` | size or quota policy violation |
@@ -64,29 +64,57 @@ port rather than the public one.
| `416` | unsatisfiable Range; carries the real length |
| `422` | digest, signature, or scanner rejection |
| `429` | transfer admission or rate limit |
| `460` | tus `Upload-Checksum` does not match that request's bytes; the chunk is discarded and the offset does not move |
| `503` | storage or scanner unavailable |
| `504` | downstream timeout |
| `507` | out of storage capacity |
## Failure body
Every failure answers `application/problem+json` with a stable code and its URN:
Every failure answers the application's one error shape, the `Envelope` (`application/json`), with
the stable code, its category, the shared Korean client message for that category and the
identifying values in `error.details`:
```json
{
"type": "urn:fileserver:problem:upload-offset-mismatch",
"title": "Upload offset mismatch",
"status": 409,
"code": "UPLOAD_OFFSET_MISMATCH",
"retryable": true,
"ambiguous": false,
"reconciliationRequired": false,
"traceId": "..."
"success": false,
"data": null,
"error": {
"code": "UPLOAD_OFFSET_MISMATCH",
"category": "CONFLICT",
"message": "현재 상태에서는 요청을 처리할 수 없습니다.",
"retryable": true,
"details": {
"uploadId": "...",
"expectedOffset": 1024,
"currentOffset": 2048
}
},
"meta": { "requestId": "...", "traceId": "...", "correlationId": "..." }
}
```
`details` carries only what the failure context holds: `fileId`, `uploadId`, `expectedOffset`,
`currentOffset`, `state`, and the flags `ambiguous` and `reconciliationRequired` when they are true.
The server-side exception message never appears. `ambiguous` is the field a client must read before
retrying: an ambiguous failure may already have taken effect.
retrying: an ambiguous failure may already have taken effect. `retryable` is this occurrence's
decision and is never wider than the code allows.
A batch upload part that is rejected carries the same `error` object (`code`, `category`,
`message`, `retryable`) in its `results[]` entry.
### Protocol exceptions to the Envelope rule
Owner decision 2 keeps one HTTP error shape; the protocol pieces below are not error vocabulary and
stay as the protocol defines them (owner decision 12):
- tus protocol headers (`Tus-Resumable`, `Upload-Offset`, `Upload-Length`, …) on every tus
response, success or failure.
- `Retry-After` and the unsatisfied-range `Content-Range` on a failure (see the header contract).
- The IETF resumable-upload draft's offset-mismatch response
(`Draft12UploadController#offsetMismatch`): `409 application/problem+json` with
`type = https://iana.org/assignments/http-problem-types#mismatching-upload-offset`,
`expectedOffset` and `providedOffset`. It is the only non-Envelope failure body.
## Header contract
+12 -3
View File
@@ -51,9 +51,18 @@ opens nothing.
## Authorization
Every public operation calls the injected `FileAccessPolicy` before any quota reservation or storage
mutation, so a denial leaves no record, no reservation, and no staging object. Startup refuses to
run a production profile with an allow-all policy.
Every public operation calls the injected `FileAccessPolicyPort` before any quota reservation or storage
mutation, so a denial leaves no record, no reservation, and no staging object. Finalize is
authorized as `FINALIZE`, and management-plane reads as `ADMIN_READ`. Startup refuses to run a
production profile with an allow-all policy.
Each file records its owner: the principal that created it and, when the transport resolved one,
its tenant (the `tenant` subject attribute). The default role policy grants an operation on an
existing file only to its owner in the same tenant, so two callers holding the same role cannot
read, download, finalize, delete, copy or move each other's files. An admin role does not bypass
this — acting on another caller's file is what the audited management plane is for. A file created
before ownership was recorded (migration V5) has no owner and is reachable only through the
management plane. Anonymous read, when enabled, publishes every file and skips the owner check.
## Delegation
+4 -15
View File
@@ -20,7 +20,6 @@ that does not exist, so a level can never outlive the test that justified it.
|---|---|---|
| Local filesystem (ext4) content store | Stable | `fileserver-local-ext4-contract` |
| Spring MVC transport (raw, multipart, batch, download) | Stable | `fileserver-http-contract` |
| Spring WebFlux transport | Experimental | `fileserver-http-contract` |
| Path, filename, range, and problem-detail hardening | Stable | `fileserver-security-suite` |
| Bounded-memory transfer | Stable | `fileserver-bounded-memory` |
| Application and architecture invariants | Stable | `fileserver-unit-and-architecture` |
@@ -37,21 +36,11 @@ that does not exist, so a level can never outlive the test that justified it.
| Full release verification | Stable | `fileserver-full-verification` |
| HTTP resumable uploads draft-12 | Experimental | `fileserver-http-contract` |
### Why WebFlux is Experimental, not Stable
### WebFlux transport removed
The reactive router, handlers and readers are now wired: `FileserverReactiveConfiguration`
contributes the scheduler, the handlers and a `RouterFunction` bean under
`@ConditionalOnWebApplication(type = REACTIVE)` plus the platform master switch. Previously nothing
built them at all, so "Stable" described the source tree rather than a running server.
It stays `Experimental` because the shipped composition cannot select it. `adapter:inbound:web`
also puts `DispatcherServlet` on the classpath — deliberately, so adding `spring-webflux` does not
drag a second embedded server onto the runtime — and Boot's application-type deduction therefore
resolves SERVLET. A fork that removes the servlet stack and adds a reactive server gets working
routes without editing any Fileserver code; the shipped template does not exercise that path.
Raising it to Stable requires a contract job that drives the routes over a running reactive server
rather than through direct construction.
The reactive router and handlers (`web.fileserver.reactive`) were removed on 2026-09-25 (D4: the
template is servlet on virtual threads). The shipped composition could never select them — the web
leaf puts `DispatcherServlet` on the classpath, so Boot resolves SERVLET.
## Explicitly not claimed
+4 -4
View File
@@ -6,8 +6,8 @@ The Fileserver ships off. Nothing is registered — no endpoint, no thread pool,
is enabled explicitly.
```yaml
ca-skeleton:
fileserver:
app:
fileserver-platform:
enabled: true
instance-id: ${HOSTNAME}
default-namespace: default
@@ -26,8 +26,8 @@ to an unkeyed digest, which would be reversible for an enumerable identifier spa
Each is a separate switch, and each defaults to off:
```yaml
ca-skeleton:
fileserver:
app:
fileserver-platform:
admin:
enabled: false # management plane; intended for a management port
tus:
+16 -22
View File
@@ -12,18 +12,19 @@ production deployment must decide has either no default or an unusable one, and
| Property | Type | Default | Environment |
|---|---|---|---|
| `app.httpclient.enabled` | boolean | `false` | `APP_HTTPCLIENT_ENABLED` |
| `app.httpclient.enabled` | boolean | `true` | `APP_HTTPCLIENT_ENABLED` |
Off is the shipped state and it is a structural one. `HttpClientPlatformAutoConfiguration` lives in
a package the composition root's component scan excludes, so while the switch is absent or false the
class is never processed and neither is anything it imports: no property is bound, and no transport
The module is on when present: a service adds `runtimeOnly project(':adapter:outbound:httpclient')`
to `app-bootstrap/build.gradle`, and the module's own `config/module-defaults/httpclient.yml` (loaded at the lowest
precedence by the support leaf's `ModuleDefaultsEnvironmentPostProcessor`) supplies `enabled: true`. Absent from the
build is the ordinary off state. `false` is the explicit off: `HttpClientPlatformAutoConfiguration`
is then never processed and neither is anything it imports — no property is bound, and no transport
provider, connection pool, TLS context, credential, thread, gateway or actuator endpoint exists. A
malformed HTTP client setting cannot fail the startup of a deployment that never wanted outbound
HTTP.
malformed HTTP client setting cannot fail the startup of a deployment that switched it off.
Anything that is not exactly `true` — `yes`, `1`, blank — leaves the platform off. Turning it on
with no client declared is a startup failure carrying `HTTPCLIENT_ACTIVE_WITHOUT_CLIENTS`: a
platform with nothing to call still holds transport providers and gateways no caller can reach.
Anything that is not exactly `true` — `yes`, `1`, blank — turns the platform off. On with no client
declared is a startup failure carrying `HTTPCLIENT_ACTIVE_WITHOUT_CLIENTS`: a platform with nothing
to call still holds transport providers and gateways no caller can reach.
## Declaring clients from the environment
@@ -66,8 +67,7 @@ materialise a nameless client in every deployment, which the aggregate validatio
| `base-url` | URI | — | Required for a trusted profile; no userinfo, no query |
| `allowed-hosts` | list | empty | Required in production |
| `allowed-ports` | list | empty | Compared against the effective port |
| `api` | `REST_CLIENT` \| `WEB_CLIENT` | `REST_CLIENT` | Decides blocking or reactive runtime |
| `transport` | `APACHE` \| `JDK` \| `REACTOR_NETTY` \| `JETTY` \| `SIMPLE` | `APACHE` | `SIMPLE` is rejected in production |
| `transport` | `APACHE` \| `JDK` \| `JETTY` \| `SIMPLE` | `APACHE` | `SIMPLE` is rejected in production; `JETTY` needs a deployment-registered provider |
| `protocols` | list | `HTTP_1_1` | The default transport is Apache, whose classic client is HTTP/1.1 only; a profile that wants HTTP/2 declares it together with a transport that can deliver it. `HTTP_3` requires the experimental acknowledgement |
| `experimental-acknowledgement` | string | — | Must equal `I_ACCEPT_HTTP3_EXPERIMENTAL_SEMANTICS` |
@@ -99,7 +99,6 @@ materialise a nameless client in every deployment, which the aggregate validatio
| `response-header` | `2s` | Until final response headers |
| `read-idle` | `3s` | Between response chunks |
| `total-call` | `4s` | The whole logical call, including retry backoff |
| `streaming-idle` | `30s` | Silence on a long-lived stream |
`total-call` must not be shorter than `connect` or `response-header`; the validator emits
`INVALID_TIMEOUT_BUDGET` otherwise.
@@ -190,9 +189,9 @@ materialise a nameless client in every deployment, which the aggregate validatio
`HOSTNAME_VERIFICATION_REQUIRED`, `PLAINTEXT_FALLBACK_FORBIDDEN`, `TLS_PROTOCOL_FORBIDDEN`,
`RETRY_BACKOFF_REQUIRED`, `MISSING_PRODUCTION_SETTING`, `DUPLICATE_CLIENT_NAME`,
`HTTPCLIENT_ACTIVE_WITHOUT_CLIENTS`, `DYNAMIC_BASE_URL_REQUIRED`,
`DYNAMIC_TARGET_PROXY_UNSUPPORTED`, `REACTIVE_AUTHENTICATION_UNSUPPORTED`,
`DYNAMIC_TARGET_PROXY_UNSUPPORTED`,
`HTTP2_REQUIRED_TRANSPORT_UNSUPPORTED`, `POOL_ROUTE_EXCEEDS_TOTAL`,
`TLS_PROTOCOL_SET_REQUIRED`, `REACTIVE_REDIRECT_UNSUPPORTED`,
`TLS_PROTOCOL_SET_REQUIRED`,
`RETRY_POLICY_CONTRADICTS_ATTEMPTS`, `FULL_URL_RECORDING_FORBIDDEN`, `BODY_LOGGING_FORBIDDEN`,
`DNS_TIMEOUT_UNSUPPORTED`, `PROXY_CREDENTIAL_UNSUPPORTED`, `PROXY_AMBIENT_NO_PROXY_UNSUPPORTED`.
@@ -204,16 +203,11 @@ unaffected — only a deliberate, unmet request fails.
Three of these are about a guarantee that used to be silently unmet rather than refused:
- `HTTP2_REQUIRED_TRANSPORT_UNSUPPORTED` — declaring `protocols: [HTTP_2]` alone states that HTTP/2
is required. Only `REACTOR_NETTY` can be configured to offer H2 and nothing else; the JDK client
treats it as a preference and negotiates HTTP/1.1, and Apache's classic client is HTTP/1.1 only.
- `POOL_ROUTE_EXCEEDS_TOTAL` — a per-route ceiling above the total is incoherent, and on Reactor,
where the per-route knob is the only one that exists, it silently becomes the effective limit.
is required. No transport can be configured to offer H2 and nothing else; the JDK client treats it
as a preference and negotiates HTTP/1.1, and Apache's classic client is HTTP/1.1 only.
- `POOL_ROUTE_EXCEEDS_TOTAL` — a per-route ceiling above the total is incoherent.
- `TLS_PROTOCOL_SET_REQUIRED` — an empty `tls.protocols` used to pass and then let the JVM choose,
so emptying the list to "tighten" a profile loosened it.
- `REACTIVE_REDIRECT_UNSUPPORTED` — engine redirect following is disabled on every transport and
only the blocking stack has a coordinator that follows hops with per-hop re-validation. A
`WEB_CLIENT` profile with `redirect.enabled=true` did not follow redirects; the caller received the
3xx as an ordinary response. Refused until the reactive coordinator exists.
- `RETRY_POLICY_CONTRADICTS_ATTEMPTS` — `retry.policy` was read by nothing on the execution path, so
the actuator could report `none` for a profile retrying three times. The two settings must now
agree: `policy: none` requires `max-attempts: 1`, and any other policy requires more than one.
+3 -7
View File
@@ -1,8 +1,8 @@
# HTTP Client platform — Java field path to environment variable template.
#
# The SSOT is HttpClientPlatformSettings. HttpClientEnvironmentKeys derives this list from the
# record tree at runtime, HttpClientPlatformEnvManifestTest fails when the two disagree in either
# direction, and the platform refuses to start on an APP_HTTPCLIENT_ variable that is not here. So a
# The SSOT is HttpClientPlatformSettings. HttpClientPlatformEnvManifestTest derives this list from
# the record tree and fails when the two disagree in either direction, and the shared strict binder
# refuses to start on an APP_HTTPCLIENT_ variable that names no field. So a
# field added with no entry, an entry whose field was renamed, and a misspelled variable in a
# deployment are all failures rather than silence.
#
@@ -39,8 +39,6 @@ fields:
env: APP_HTTPCLIENT_CLIENTS_N_ALLOWED_HOSTS_M
- field: clients[N].allowed-ports[M]
env: APP_HTTPCLIENT_CLIENTS_N_ALLOWED_PORTS_M
- field: clients[N].api
env: APP_HTTPCLIENT_CLIENTS_N_API
- field: clients[N].transport
env: APP_HTTPCLIENT_CLIENTS_N_TRANSPORT
- field: clients[N].protocols[M]
@@ -83,8 +81,6 @@ fields:
env: APP_HTTPCLIENT_CLIENTS_N_TIMEOUT_READ_IDLE
- field: clients[N].timeout.total-call
env: APP_HTTPCLIENT_CLIENTS_N_TIMEOUT_TOTAL_CALL
- field: clients[N].timeout.streaming-idle
env: APP_HTTPCLIENT_CLIENTS_N_TIMEOUT_STREAMING_IDLE
- field: clients[N].redirect.enabled
env: APP_HTTPCLIENT_CLIENTS_N_REDIRECT_ENABLED
- field: clients[N].redirect.max-hops
-64
View File
@@ -1,64 +0,0 @@
# Migrating from `RestTemplate`
`RestTemplate` is permitted only inside `…httpclient.migration`; `RestTemplateBoundaryTest` enforces
that. New retry, Dynamic Target, and HTTP/3 capabilities are deliberately unreachable from the
migration path — a caller that wants them moves to a Named Client Profile.
## 1. Audit before changing anything
```java
RestTemplateInventory inventory = new RestTemplateInventoryScanner().scan(existingTemplate);
```
The inventory reports the request factory, message converters, interceptors, error handler, and URI
template handler, plus findings:
| Code | Severity | Meaning |
|---|---|---|
| `SIMPLE_REQUEST_FACTORY` | blocking | no connection pool; unsupported in production |
| `NO_MESSAGE_CONVERTERS` | blocking | the template cannot encode or decode a body |
| `NO_INTERCEPTORS` | warning | confirm where correlation and timeouts are applied |
| `TIMEOUTS_NOT_INTROSPECTABLE` | informational | declare timeouts explicitly on the target profile |
## 2. Bridge without changing behaviour
```java
RestClient client = new RestTemplateToRestClientAdapter().adaptChecked(existingTemplate);
```
`adaptChecked` refuses to migrate a template with a blocking finding. The bridge carries the
existing converters, interceptors, error handler, and URI handler across, so this step changes the
API and nothing else.
## 3. Move to a Named Client Profile
Turn the platform on with `APP_HTTPCLIENT_ENABLED=true` — it ships off, and while it is off none of
the settings below are bound — then declare the upstream as `app.httpclient.clients[N]` with its
`name` and an explicit base URL, transport, timeouts, pool, body limits, authentication, retry
policy, redirect policy, and TLS profile. Startup validation will tell you exactly which of those is
missing. See `docs/httpclient/configuration-reference.md` for the environment form.
## 4. Move to a typed client
```java
@HttpClientProfile("payment")
@HttpExchange("/payments")
public interface PaymentClient {
@PostExchange
@HttpOperationPolicy(
name = "create-payment",
idempotency = OperationIdempotency.IDEMPOTENCY_KEY_REQUIRED,
retryPolicy = "payment-write")
PaymentResponse create(
@RequestHeader("Idempotency-Key") String idempotencyKey, @RequestBody PaymentRequest request);
}
```
The interface fails startup validation unless it declares a profile, gives every method a stable
operation name and an explicit idempotency, supplies a key parameter when the operation requires
one, keeps a single execution model, and does not enable retry on a non-idempotent write.
## 5. Retire the template
Once no production package references `RestTemplate`, `RestTemplateBoundaryTest` keeps it that way.
+6 -3
View File
@@ -79,8 +79,8 @@ a mesh retry policy changes.
## Error model
Every outbound failure is one of these stable types. The type is derived from the classified failure
category, not from whatever the engine happened to throw, so it means the same thing on Apache, JDK,
and Reactor Netty. Each carries `HttpFailureMetadata`: client, operation, method, URI **template**,
category, not from whatever the engine happened to throw, so it means the same thing on Apache and
JDK. Each carries `HttpFailureMetadata`: client, operation, method, URI **template**,
evidence, replayability, stage, retryability, attempt, elapsed, remaining deadline, status, trace id
— and nothing else.
@@ -105,7 +105,10 @@ evidence, replayability, stage, retryability, attempt, elapsed, remaining deadli
| `HttpDeadlineExceededException` | the effective deadline was reached | never |
| `HttpCircuitOpenException` | the upstream circuit is open | never |
| `HttpBulkheadRejectedException` | no attempt or logical admission permit was available | never |
| `HttpRateLimitRejectedException` | the local attempt rate limit or retry budget rejected the attempt | never |
| `HttpRateLimitRejectedException` | the local attempt rate limiter rejected the attempt | never |
| `HttpRetryBudgetExhaustedException` | the per-upstream retry budget refused a further attempt | never |
| `HttpRuntimeDrainingException` | the profile's runtime was retired (certificate rotation) before a granted retry started | never — a new call runs on the replacement |
| `HttpUnknownTransportException` | the engine failed in a way no category above describes; the metadata evidence, not the type, says whether it was sent | never |
| `HttpAmbiguousExecutionException` | a non-idempotent request was sent and the outcome is unknown | never — reconcile instead |
## Traces
-1
View File
@@ -29,7 +29,6 @@ never silently degrades into a pass.
| `RetryStormBudgetTest` | 10 000 logical calls against a failing upstream produce at most 11 000 physical attempts at a 10 % budget | structural |
| `LargeBodyResourceTest` | a 32 MiB streaming download consumes every byte without buffering the payload on the heap | structural + machine-dependent heap bound |
| `PoolSaturationPerformanceTest` | 24 concurrent calls against a 4-connection pool all reach a terminal outcome; none hang | structural |
| `Http2StreamSaturationTest` | 32 concurrent reactive streams share a 2-connection pool and complete | structural |
| `OAuthRefreshContentionTest` | 100 genuinely concurrent callers produce exactly one token request | structural |
| `RuntimeRotationDrainTest` | 50 rotations close all 50 retired generations and leave no drain thread | structural |
+2 -4
View File
@@ -9,7 +9,6 @@ cd src
./gradlew :adapter:outbound:httpclient:test --console=plain
./gradlew :adapter:outbound:httpclient:httpClientStableContractTest --console=plain
./gradlew :adapter:outbound:httpclient:httpClientSecurityTest --console=plain
./gradlew :adapter:outbound:httpclient:httpClientBlockHoundTest --console=plain
./gradlew :adapter:outbound:httpclient:spring62CompatibilityTest --console=plain
./gradlew :adapter:outbound:httpclient:spring70CompatibilityTest --console=plain
./gradlew :adapter:outbound:httpclient:httpClientFailureInjectionTest --console=plain # needs Docker
@@ -24,7 +23,7 @@ python3 ../scripts/verify-httpclient-docs.py
- [ ] Typed clients are the default entry point; H2 and H3 are separately authorised.
- [ ] H1–H4 cannot bypass timeout, host, TLS, auth, size, or observation policy.
- [ ] Apache, JDK, and Reactor produce identical result and exception metadata.
- [ ] Apache and JDK produce identical result and exception metadata.
- [ ] Pool, DNS, connect, TLS, and retry backoff all fit inside the effective deadline.
- [ ] Every extra attempt is explained by idempotency, replayability, evidence, deadline, and budget.
- [ ] Non-idempotent `SENT_NO_RESPONSE` surfaces as `HttpAmbiguousExecutionException`.
@@ -33,12 +32,11 @@ python3 ../scripts/verify-httpclient-docs.py
- [ ] Trust-all and hostname-verification bypass fail at startup.
- [ ] Canonicalisation, DNS/IP validation, redirect revalidation, and egress control all pass.
- [ ] No transparent retry occurs after the first delivered byte.
- [ ] No platform code blocks a Reactor event loop, proven by a BlockHound self-check.
- [ ] The negotiated wire protocol matches what the support matrix claims per transport.
- [ ] Logical calls and attempts are separate metrics with no forbidden label.
- [ ] DNS, pool, TLS, reset, partial response, and HTTP/2 GOAWAY are reproducible.
- [ ] Thread, heap, direct memory, pool, and retry budget bounds hold.
- [ ] The support matrix, configuration reference, security guide, runbook, and migration guide match the code.
- [ ] The support matrix, configuration reference, security guide and runbook match the code.
## Experimental
+3 -5
View File
@@ -48,12 +48,10 @@ Root package: `io.backend.skeleton.httpclient` → `dev.caskeleton.adapter.outbo
| `httpclient-auth` | `…httpclient.auth` | `…outbound.httpclient.auth` |
| `httpclient-security` | `…httpclient.security` | `…outbound.httpclient.security` |
| `httpclient-observability` | `…httpclient.observation` | `…outbound.httpclient.observation` |
| `httpclient-transport-reactor-netty` | `…httpclient.reactor` | `…outbound.httpclient.reactor` |
| `httpclient-webclient` | `…httpclient.webclient` | `…outbound.httpclient.webclient` |
| `httpclient-transport-reactor-netty` | `…httpclient.reactor` | removed (decision 9, 2026-09-25: blocking only) |
| `httpclient-webclient` | `…httpclient.webclient` | removed (decision 9, 2026-09-25: blocking only) |
| `httpclient-service-client` | `…httpclient.service` | `…outbound.httpclient.service` |
| `httpclient-dynamic-target` | `…httpclient.dynamic` | `…outbound.httpclient.dynamic` |
| `httpclient-resttemplate-migration` | `…httpclient.migration` | `…outbound.httpclient.migration` |
| `httpclient-spring7-service-groups` | `…httpclient.spring7` | `…outbound.httpclient.spring7` |
| `httpclient-jetty-http3-experimental` | `…httpclient.http3` | `…outbound.httpclient.http3` |
| `httpclient-spring-boot-starter` | `…httpclient.autoconfigure` | `dev.caskeleton.adapter.outbound.httpclient.autoconfigure` |
| `httpclient-testkit` | `…httpclient.testkit` | `…outbound.httpclient.testkit` (`testkit` source set) |
@@ -63,7 +61,7 @@ Root package: `io.backend.skeleton.httpclient` → `dev.caskeleton.adapter.outbo
| Design assumption | Repository reality | Adaptation |
|---|---|---|
| Gradle Kotlin DSL, `build-logic` convention plugin | Groovy DSL, root `build.gradle` conventions, `LockMode.STRICT` dependency locking | Dependencies declared in `src/adapter/outbound/httpclient/build.gradle`; `gradle.lockfile` regenerated. |
| Spring Framework 6.2 baseline with 7.0 compatibility | Spring Boot 4.0.8 / Spring Framework 7.0 is the repository baseline | Common code targets the Spring 6.2 **API surface** (no 6.2-only or 7.0-only classes in common packages). The Spring 7 HTTP Service Group integration stays isolated in `…httpclient.spring7`, exactly as the design requires. |
| Spring Framework 6.2 baseline with 7.0 compatibility | Spring Boot 4.0.8 / Spring Framework 7.0 is the repository baseline | Common code targets the Spring 6.2 **API surface** (no 6.2-only or 7.0-only classes in common packages). The Spring 7 HTTP Service Group integration and the `RestTemplate` migration package were removed. |
| `settings.gradle.kts` module registration | Fail-closed registry | No registry change; leaf identity, gradle path, allowed dependencies unchanged. |
| Design §6.2 grades Apache HttpClient 5 as HTTP/2-capable | Spring's blocking factory drives Apache's **classic** client, which is HTTP/1.1 only; HTTP/2 lives in Apache's async client | `ApacheBlockingTransportProvider` declares HTTP/1.1 and rejects an HTTP/2 profile at startup. Blocking HTTP/2 is served by the JDK transport, measured by `NegotiatedProtocolContractTest`. |
| Design §28.1 names WireMock for stateful fixtures | WireMock's Jetty modules bind a different Jetty 12 ABI than the Boot-managed one this module already needs for HTTP/3, and fail at server start | `StatefulUpstream` provides path-keyed stateful responses on the existing fixture server; the WireMock dependency was removed rather than worked around with a shaded jar |
+13 -29
View File
@@ -2,13 +2,10 @@
## Response lifecycle
A blocking streaming download returns `BlockingStreamingResponse`, never a bare `InputStream`.
Closing is idempotent and always releases the connection — after a full read, a partial read, a
decode failure, or a size rejection. The status is validated before any body byte is delivered, so a
failed download never becomes a half-consumed stream the caller has to reason about.
A reactive download emits bounded `DataBuffer` values. Buffers are released on completion, error,
and cancellation; a dropped buffer is direct memory nobody returns.
A streaming download returns `BlockingStreamingResponse`, never a bare `InputStream`. Closing is
idempotent and always releases the connection — after a full read, a partial read, a decode failure,
or a size rejection. The status is validated before any body byte is delivered, so a failed download
never becomes a half-consumed stream the caller has to reason about.
Wire bytes and decoded bytes are bounded independently, because a compressed payload passes a wire
check and then expands. Limits are enforced while reading, not after buffering.
@@ -19,34 +16,21 @@ check and then expands. Limits are enforced while reading, not after buffering.
response headers received
→ nothing delivered yet
→ a read-only operation may still be retried
→ first InputStream read or first Flux onNext
→ transparent retry is permanently disabled
→ the response is handed to the caller
→ transparent retry is no longer possible
```
`FirstByteDeliveryGuard` latches once and never resets. Retrying after delivery would replay a
stream the caller has already partly consumed, producing duplicated or reordered data that no
downstream code can detect.
Retrying after delivery would replay a stream the caller has already partly consumed, producing
duplicated or reordered data that no downstream code can detect. The streaming gateway hands out
the response only after the attempt has finished, so there is no retry left to run once the caller
reads.
## Request bodies
A reopenable body is opened once per attempt, which is what makes it replayable; reusing the
previous stream would silently send an empty body on the retry. A one-shot stream or publisher
instance is never retried. `ReactiveBodySource` takes a publisher *factory* rather than a publisher
so a reactive body can honestly declare itself replayable.
A multipart body is exactly as replayable as its weakest part.
previous stream would silently send an empty body on the retry. A one-shot stream is never retried.
## Server-sent events
Three budgets stay separate:
- `setupDeadline` — establishing the stream
- `streamingIdleTimeout` — silence once it is open
- `maxStreamDuration` — optional total lifetime
Applying the request-shaped `total-call` timeout to an SSE subscription would terminate a perfectly
healthy stream on schedule, so it is not applied.
`Last-Event-ID` is opt-in. Replaying from an id is only correct when the producer guarantees it;
sending it blindly can skip or duplicate events. Reconnects consume the retry budget like any other
physical attempt, and cancelling the subscription stops both the stream and any pending reconnect.
The platform has no server-sent-event client. It was part of the reactive stack, which was removed
(decision 9, 2026-09-25): the platform runs blocking calls on the caller's thread only.
+17 -18
View File
@@ -7,23 +7,24 @@ proves it; anything the suite cannot prove is **Experimental** and says so.
| API | Grade | Role | Constraint |
|---|---|---|---|
| `RestClient` | Stable | Blocking execution | Bounded concurrency and an effective deadline are mandatory |
| `WebClient` | Stable | Reactive, streaming, SSE | No blocking work on the event loop |
| `RestClient` | Stable | Blocking execution (the only execution model) | Bounded concurrency and an effective deadline are mandatory |
| HTTP Service Client (`@HttpExchange`) | Default | Declarative typed client | Operation metadata is mandatory |
| `RestTemplate` | Migration only | Moving existing calls | No new profile or feature |
| Generic Exchange (H2) | Restricted | Dynamic method, path, body | Base URL and policy are immutable |
| Dynamic Target (H3) | Restricted | User-supplied URL | Separate SSRF policy; inherits no credential |
| Native engine | Internal | Engine-specific configuration | Never an application-facing API |
## Transports
| Transport | Blocking | Reactive | HTTP/1.1 | HTTP/2 | HTTP/3 | Grade | Verified by |
|---|---:|---:|---:|---:|---:|---|---|
| Apache HttpClient 5 (classic) | yes | no | yes | **no** | no | Stable (blocking default) | `httpClientStableContractTest`, `NegotiatedProtocolContractTest` |
| JDK HttpClient | yes | `sendAsync` | yes | yes (TLS/ALPN) | no | Stable (lightweight, blocking HTTP/2) | `NegotiatedProtocolContractTest` |
| Reactor Netty | limited | yes | yes | yes | experimental | Stable (reactive default) | `NegotiatedProtocolContractTest` |
| Jetty | facade | yes | yes | yes | yes | **Experimental** | `Http3OptInTest` only |
| Simple request factory | yes | no | limited | no | no | Local test only | rejected in production by `ClientProfileValidator` |
The platform is blocking only (decision 9, 2026-09-25): every call runs on the caller's thread —
a virtual thread in this template — through `RestClient`. There is no reactive execution path, no
`WebClient`, and no Reactor Netty transport.
| Transport | HTTP/1.1 | HTTP/2 | HTTP/3 | Grade | Verified by |
|---|---:|---:|---:|---|---|
| Apache HttpClient 5 (classic) | yes | **no** | no | Stable (default) | `httpClientStableContractTest`, `NegotiatedProtocolContractTest` |
| JDK HttpClient | yes | yes (TLS/ALPN) | no | Stable (lightweight, HTTP/2) | `NegotiatedProtocolContractTest` |
| Jetty | yes | yes | yes | **Experimental** | `Http3OptInTest` only |
| Simple request factory | limited | no | no | Local test only | rejected in production by `ClientProfileValidator` |
### Apache is HTTP/1.1 here, and why
@@ -34,8 +35,9 @@ classic client fails outright against a prior-knowledge h2c server.
So `ApacheBlockingTransportProvider.capabilities()` declares HTTP/1.1, and a profile that pairs
Apache with `HTTP_2` is rejected at startup instead of quietly running HTTP/1.1 while this table
claims otherwise. **Blocking HTTP/2 is served by the JDK transport**; reactive HTTP/2 by Reactor
Netty. Both are measured from the client after a real TLS handshake, not read from configuration.
claims otherwise. **HTTP/2 is served by the JDK transport**, measured from the client after a real
TLS handshake, not read from configuration. No transport can be restricted to HTTP/2 alone, so a
profile that declares only `HTTP_2` is refused (`HTTP2_REQUIRED_TRANSPORT_UNSUPPORTED`).
The JDK transport declares `routeScopedPool=false`, `boundedPendingAcquireQueue=false`, and
`dynamicTargetStable=false`. A profile that needs any of those is rejected at startup rather than
@@ -46,7 +48,7 @@ gives route-scoped pooling and Dynamic Target pinning, JDK gives HTTP/2.
| Capability | Gate |
|---|---|
| Dynamic Target (H3) | Apache and Reactor Netty only; JDK and Jetty are rejected |
| Dynamic Target (H3) | Apache only; JDK and Jetty are rejected |
| HTTP/3 | `experimentalAcknowledgement` must equal `I_ACCEPT_HTTP3_EXPERIMENTAL_SEMANTICS` |
| Cross-origin redirect | opt-in per profile; credentials are stripped on the hop |
| Retry | evidence-based; never enabled by HTTP method alone |
@@ -59,10 +61,8 @@ gives route-scoped pooling and Dynamic Target pinning, JDK gives HTTP/2.
| Spring Framework 6.2 API surface | every PR | required | `spring62CompatibilityTest` |
| Apache HC5 + RestClient | every PR | required | `httpClientStableContractTest -Phttpclient.contract.transports=apache` |
| JDK HttpClient + RestClient | every PR | required | `httpClientStableContractTest -Phttpclient.contract.transports=jdk` |
| Reactor Netty + WebClient | every PR | required | `httpClientStableContractTest -Phttpclient.contract.transports=reactor` |
| SSRF / cardinality suite | every PR | required | `httpClientSecurityTest` |
| Toxiproxy fault suite | nightly, release | required | `httpClientFailureInjectionTest` |
| Event-loop blocking (BlockHound) | every PR | required | `httpClientBlockHoundTest` |
| Performance certification | nightly, release | required | `httpClientPerformanceTest -Pperformance.assertions.enabled=true` |
| Jetty HTTP/3 | nightly | Experimental, non-blocking | `test -Phttp3.tests.enabled=true` |
@@ -70,8 +70,8 @@ gives route-scoped pooling and Dynamic Target pinning, JDK gives HTTP/2.
This repository's Spring Boot 4.0 baseline pins Spring Framework 7, so a real 6.2 runtime cannot be
resolved here. `spring62CompatibilityTest` therefore verifies the **API surface**: the common
packages must not reference any Spring 7-only type, and `org.springframework.web.service.registry`
is confined to `…httpclient.spring7`. Executing the suite against an actual 6.2 distribution
packages must not reference any Spring 7-only type, and no class uses
`org.springframework.web.service.registry`. Executing the suite against an actual 6.2 distribution
requires a host project on that line. This limitation is stated rather than hidden behind a passing
check.
@@ -83,6 +83,5 @@ Stated so the matrix is read as a measurement rather than an aspiration.
| Gap | Why | What is proven instead |
|---|---|---|
| HTTP/2 frame injection (`REFUSED_STREAM`, arbitrary `GOAWAY`) | The fixture server exposes no frame-level control, and a purpose-built h2 server is a larger dependency than the guarantee is worth here | `Http2EvidenceMapperTest` proves the frame → evidence mapping, and `NegotiatedProtocolContractTest` proves h2 is really negotiated |
| Netty buffer-leak detection | Netty reports a leak when an unreferenced buffer is collected, which the suite does not force | `NettyLeakDetectionExtension` asserts the PARANOID detector is live and reports nothing; explicit release assertions in the streaming suites are the primary guarantee |
| Spring 6.2 runtime | This repository's Boot 4.0 baseline pins Spring 7 | `spring62CompatibilityTest` confines the common packages to the 6.2 API surface |
| Performance latency baseline | Numbers measured on a build agent are not a certification | `httpClientPerformanceTest` asserts structural bounds unconditionally; latency and heap bounds run under `-Pperformance.assertions.enabled=true` |
+3 -1
View File
@@ -1,6 +1,8 @@
# Experimental Promotion Checklist
`ExperimentalPromotionGate` evaluates this checklist. Every technical item, then the ADR.
A reviewer evaluates this checklist. Every technical item, then the ADR. (The
`ExperimentalPromotionGate` class that encoded it in main code was removed on 2026-09-25; nothing
called it.)
## Technical evidence
+15 -15
View File
@@ -1,22 +1,22 @@
# Experimental Support Matrix
Everything here is off unless its `backend.jpa.experimental.*` flag is explicitly true, and none of
it is part of the Stable composition.
Experimental code is library code in `dev.caskeleton.adapter.outbound.persistence.experimental`.
Nothing composes it and no setting turns it on: a deployment that wants one of these creates the
entry point in its own adapter code, and that call is the opt-in. None of it is part of the Stable
composition, and `JpaModuleBoundaryTest` keeps Stable packages from depending on it.
| Feature | Flag | State |
|---|---|---|
| Shared-schema multi-tenancy (column) | `backend.jpa.experimental.multitenancy-column` | Experimental |
| PostgreSQL RLS multi-tenancy | `backend.jpa.experimental.multitenancy-rls` | Experimental |
| Schema-per-tenant | `backend.jpa.experimental.multitenancy-schema` | Experimental |
| Database-per-tenant | `backend.jpa.experimental.multitenancy-database` | Experimental |
| Consistency-aware read replica | `backend.jpa.experimental.read-replica` | Experimental |
| Jakarta Persistence 4.0 lane | `backend.jpa.experimental.jakarta-persistence-4` | Experimental |
| Hibernate ORM 8 lane | `backend.jpa.experimental.hibernate-8` | Experimental |
| PostgreSQL 19 lane | `backend.jpa.experimental.postgresql-19` | Experimental |
| Feature | Entry point | Evidence (PostgreSQL lane unless noted) | State |
|---|---|---|---|
| Shared-schema multi-tenancy (column) | `tenant.TenantContext`, `tenant.TenantAwareRepositoryGuard` | `TenantColumnIsolationTest` | Experimental |
| PostgreSQL RLS multi-tenancy | `rls.RlsTenantSessionBinder`, `rls.RlsPolicyVerifier` | `RlsIsolationFailureTest` | Experimental |
| Schema-per-tenant | `schema.SchemaMultiTenantConnectionProvider`, `schema.SchemaTenantMigrationOrchestrator` | `SchemaTenantMigrationContractTest` | Experimental |
| Database-per-tenant pool budget | `database.TenantDataSourceRegistry`, `database.TenantPoolBudget` | `TenantPoolCapacityContractTest` | Experimental |
| Consistency-aware read replica | `replica.ConsistencyAwareDataSourceRouter` (you implement `ReplicaLagMonitor`) | `ReadAfterWriteRoutingContractTest` | Experimental |
| Jakarta Persistence 4.0, Hibernate ORM 8, PostgreSQL 19 | none — probes in `.github/workflows/jpa-next.yml` record `NOT_EXECUTABLE` | `Jpa4CompatibilityTest`, `Hibernate8CompatibilityTest`, `PostgreSql19CompatibilityTest` (unit-lane version canaries) | Not executable |
Presence on the classpath is not consent. `ExperimentalFeatureGate` fails startup when a module is
present and its flag is not set, because an experimental module can arrive transitively and a
tenant-isolation feature that switched itself on would be the worst possible default.
The `backend.jpa.experimental.*` flags and `ExperimentalFeatureGate` that used to front these were
removed on 2026-09-25: no code read the flags from configuration, so setting one did nothing, and
the gate only checked a map the caller built itself.
## Known constraints
+9 -7
View File
@@ -18,8 +18,10 @@ whichever instance started first.
## Validation fails closed and never repairs
`FlywayValidationGate` throws `SchemaMismatchException` on a checksum mismatch, a missing migration,
or a schema Hibernate disagrees with. It never calls `repair`.
At startup Flyway's own validation (and Hibernate `ddl-auto=validate`) refuses a checksum mismatch,
a missing migration, or a schema Hibernate disagrees with. Nothing in the application calls
`repair`. In tests, the testkit's `FlywayValidationGate` turns a failed `ValidateResult` into
`SchemaMismatchException`; the migration contract tests use it.
Repair rewrites the schema history table to match whatever scripts are on disk. That resolves the
symptom by deleting the evidence: a checksum mismatch means the deployed script differs from the
@@ -40,15 +42,15 @@ one by default. The migration therefore needs a companion configuration:
executeInTransaction=false
```
`ConcurrentIndexMigrationInspector` fails validation without it, and additionally requires the
migration to contain nothing else. A failed concurrent build leaves an invalid index behind;
The testkit's `ConcurrentIndexMigrationInspector` checks a script for this in a migration test
(nothing checks it at startup), and additionally requires the migration to contain nothing else. A failed concurrent build leaves an invalid index behind;
recovering is a single `DROP INDEX` when the migration did nothing else, and a manual reconstruction
of partial state when it did.
An invalid index is not merely useless — the planner ignores it while every write still maintains
it. `FailedConcurrentIndexRecovery` reports them with the statement to run, and deliberately does
not drop them: an invalid index can also mean a build is still running, and the two are
indistinguishable from the catalog alone.
it. [runbooks.md](runbooks.md) has the query that finds them. Nothing drops them automatically: an
invalid index can also mean a build is still running, and the two are indistinguishable from the
catalog alone.
## Upgrade scenarios
+34 -37
View File
@@ -2,55 +2,52 @@
Design §37. What is measured, and what must never appear in a measurement.
## What is emitted by default
Nothing JPA-specific. No composition constructs a `MeterRegistry`-backed observation for the
platform, and `SpringTransaction` records no transaction metric. The `jpa.transaction.*` meters
this page used to list (`duration`, `rollback`, `timeout`, `completion.unknown`) were produced by
`JpaTransactionObservation`, which nothing constructed; it was removed on 2026-09-25
(`docs/capability-status.md`). Transaction outcomes are visible through the shared persistence error
codes and the application's own metrics, not through a JPA meter.
## Query metrics — only when the caller asks
`jpa.query.duration` and `jpa.query.rows` are recorded by `MicrometerQueryObservation`, and only
when a service passes it to a library executor that accepts a `QueryObservation`
(`JpaStreamExecutor`, `HibernateBulkDmlExecutor`). The default is `NoopQueryObservation`. Rows are
measured as well as duration because a query that issues one statement and hydrates twenty thousand
rows is fast per statement and catastrophic per request — a duration metric alone reports it as
merely slow.
## Bounded tags, always
Every JPA metric carries exactly five tags: persistence unit, operation, query, outcome, failure
category. All five are registered identifiers, validated by `LowCardinality` at construction rather
than at the registry — so an unbounded value fails where it was introduced instead of surviving
until a dashboard stops loading.
Every meter `MicrometerQueryObservation` records carries exactly five tags: persistence unit,
operation, query, outcome, failure category (`JpaMetricTags`). All five are registered identifiers,
validated by `LowCardinality` at construction rather than at the registry — so an unbounded value
fails where it was introduced instead of surviving until a dashboard stops loading.
Never a tag: entity id, tenant id, SQL parameter, exception message, JDBC URL. Each is unbounded, so
each creates a time series per row or per failure; several are also the data the platform keeps out
of logs, which a metrics backend would store just as durably and export just as widely.
## Transaction metrics
| Meter | Why it exists |
|---|---|
| `jpa.transaction.duration` | the baseline |
| `jpa.transaction.rollback` | rollback rate by failure category |
| `jpa.transaction.timeout` | timeouts, distinct from other rollbacks |
| `jpa.transaction.completion.unknown` | its own counter, deliberately |
Completion-unknown gets a separate counter rather than being folded into failures. It is the one
outcome that means a human has to look: every other failure is a transaction that definitely did not
happen, while this one is a transaction that may have.
## Query metrics
`jpa.query.duration` and `jpa.query.rows`. Rows are measured as well as duration because a query
that issues one statement and hydrates twenty thousand rows is fast per statement and catastrophic
per request — a duration metric alone reports it as merely slow.
## Retry metrics
Attempts are metrics, not warnings. Optimistic conflicts and serialization failures are the expected
cost of concurrency; logging each at WARN pages someone for a system working as designed, after
which the retry log gets filtered out and takes the genuinely interesting entries with it.
`jpa.retry.attempt`, `jpa.retry.attempts` (distribution per operation), `jpa.retry.exhausted`.
## Query names in SQL
`NamedStatementInspector` prefixes each statement with its registered query name as a SQL comment,
which travels into `pg_stat_activity`, `auto_explain`, and the slow-query log. Without it, "which
endpoint issues this query" is answered by grepping the codebase for fragments of SQL.
`JpaRepositoryFragmentSupport` sets the registered query name as the `org.hibernate.comment` hint;
Hibernate writes it into the SQL only when `hibernate.use_sql_comments=true`. The alternative is
`NamedStatementInspector`, which prefixes a statement with the query name bound by
`JpaStreamExecutor`, `JpaKeysetQuerySupport` or `JpaRepositoryFragmentSupport.observing(..)`.
Neither is on by default: a deployment enables the inspector with
`spring.jpa.properties.hibernate.session_factory.statement_inspector=dev.caskeleton.adapter.outbound.persistence.hibernate.NamedStatementInspector`.
The comment then travels into `pg_stat_activity`, `auto_explain`, and the slow-query log. Without it,
"which endpoint issues this query" is answered by grepping the codebase for fragments of SQL.
## Diagnostics
`SqlDiagnosticRedactor` removes string literals, numbers, and anything email-shaped before SQL
reaches a log. Redaction is blunt on purpose: preserving "harmless" values would require knowing
which columns hold personal data.
`SqlDiagnosticRedactor.redact(sql)` removes string literals, numbers, and anything email-shaped. It is
a utility for code that is about to log SQL; nothing in the platform logs SQL through it. Redaction
is blunt on purpose: preserving "harmless" values would require knowing which columns hold personal
data.
## The actuator endpoint
-22
View File
@@ -17,28 +17,6 @@ single field with a magic zero is how "no wait" becomes "wait forever".
the first leaves the transaction alive and the caller in control; the second has already been rolled
back by the server.
## Work claims
`FOR UPDATE SKIP LOCKED` is reachable only through a registered `WorkQueueName`, never as a
repository flag. It deliberately returns an incomplete view of the table: correct for handing
disjoint work to competing workers, silently wrong for anything that needs to see every matching
row. A registered claim statement must skip locked rows and impose a deterministic `ORDER BY`.
## Upserts
`INSERT ... ON CONFLICT ... RETURNING` under a registered `NativeWriteName` with a fixed conflict
target and update column set. The conflict target cannot be a bound parameter, so accepting one from
a caller would mean building SQL from input.
An upsert is the correct answer to a create race precisely because the database decides.
Read-then-write cannot be made correct: another transaction can commit between the read and the
write. `(xmax = 0) AS inserted` in the `RETURNING` list is what lets the platform report
insert-versus-update without a second query.
The executor flushes before and clears after: a native write is invisible to the Persistence
Context, so a pending managed change would otherwise overwrite it, and a managed entity loaded
beforehand would keep serving pre-upsert values.
## JSONB
`JsonDocument` carries a schema name and version alongside the payload. A JSONB column is schemaless
+4 -3
View File
@@ -4,9 +4,10 @@ Design §23-§28. How queries are chosen, bounded, and proven.
## Named queries
Every registered query carries a `QueryName`. It becomes the metric tag, the trace attribute, and
the SQL comment that appears in `pg_stat_activity` and the slow-query log — which is the only thing
that connects a statement on the server back to the use case that issued it. The format rejects raw
Every registered query carries a `QueryName`. It is the tag `MicrometerQueryObservation` records
under and the SQL comment that appears in `pg_stat_activity` and the slow-query log — which is the
only thing that connects a statement on the server back to the use case that issued it. Neither is on
by default; [observability.md](observability.md) says how a deployment turns each on. The format rejects raw
SQL for a reason: a metric tag built from a query string is unbounded by construction, and one built
from a parameterised value leaks row data into telemetry.
+16 -15
View File
@@ -29,7 +29,7 @@ This is the same adaptation already applied to the HTTP client platform
| Plan module | Repository home | Reason |
|---|---|---|
| `jpa-spring-boot-starter` | `:app-bootstrap` (`dev.caskeleton.bootstrap.autoconfigure.jpa`) | This repository's composition root owns wiring, startup validation, and actuator surface; an adapter leaf must not auto-configure itself. `AGENTS.md` assigns composition to `app-bootstrap`. |
| `jpa-spring-boot-starter` | `:adapter:outbound:persistence-jpa` (`…persistence.autoconfigure`, `…persistence.startup`) | Relational persistence is a capability module selected by one build line (`AGENTS.md` capability rules): the leaf registers its own auto-configuration, startup validation, actuator view and shipped settings, and the default composition does not carry it. Use-case assembly over its ports (the outbox relay) stays in `app-bootstrap`. |
| `jpa-testkit`, `jpa-testkit-postgresql`, `jpa-testkit-migration`, `jpa-testkit-queryplan` | `:adapter:outbound:persistence-jpa` `src/testkit/java/**/testkit` | The plan forbids production modules depending on the testkit. A source set whose dependencies are declared only on test configurations gives the same guarantee without a new Gradle project, and more than one lane consumes it. |
The package boundary is enforced by `JpaModuleBoundaryTest`. It holds a closed catalog of the
@@ -57,17 +57,17 @@ Root package: `io.backend.skeleton.jpa` → `dev.caskeleton.adapter.outbound.per
| `jpa-spring-data` | `…jpa.springdata` | `…persistence.springdata` |
| `jpa-querydsl` | `…jpa.querydsl` | `…persistence.querydsl` |
| `jpa-hibernate` | `…jpa.hibernate` (+ `.batch`, `.bulk`, `.stateless`) | `…persistence.hibernate` (+ same subpackages) |
| `jpa-postgresql` | `…jpa.postgresql` (+ `.error`, `.lock`, `.constraint`, `.json`, `.array`, `.range`, `.write`) | `…persistence.postgresql` (+ same subpackages) |
| `jpa-postgresql` | `…jpa.postgresql` (+ `.error`, `.lock`, `.constraint`, `.json`, `.array`, `.range`, `.write`) | `…persistence.postgresql` (+ same subpackages except `.write`, removed 2026-09-25) |
| `jpa-postgresql-copy` | `…jpa.postgresql.copy` | `…persistence.postgresql.copy` |
| `jpa-migration-flyway` | `…jpa.migration` | `…persistence.migration` |
| `jpa-auditing` | `…jpa.auditing` | `…persistence.auditing` |
| `jpa-auditing` | `…jpa.auditing` | none — removed; `…persistence.audit.AuditableEntity` is the one audit mechanism |
| `jpa-envers` | `…jpa.envers` | `…persistence.envers` |
| `jpa-cache-hibernate` | `…jpa.cache` | `…persistence.cache` |
| `jpa-observability` | `…jpa.observation` | `…persistence.observation` |
| `jpa-security` | `…jpa.security` | `…persistence.security` |
| `jpa-spring-boot-starter` | `…jpa.autoconfigure` | `dev.caskeleton.bootstrap.autoconfigure.jpa` |
| `jpa-spring-boot-starter` | `…jpa.autoconfigure` | `…persistence.autoconfigure`, `…persistence.startup` |
| `jpa-testkit*` | `…jpa.testkit` (+ `.id`, `.mapping`, `.lifecycle`, `.query`, `.fetch`, `.postgresql`, `.migration`, `.queryplan`, `.failure`, `.pool`, `.release`) | `…persistence.testkit` (+ same subpackages), `testkit` source set |
| `jpa-experimental/*` | `…jpa.experimental` (+ `.tenant`, `.rls`, `.schema`, `.database`, `.replica`, `.next`) | `…persistence.experimental` (+ same subpackages) |
| `jpa-experimental/*` | `…jpa.experimental` (+ `.tenant`, `.rls`, `.schema`, `.database`, `.replica`, `.next`) | `…persistence.experimental` (+ same subpackages except `.next`, removed 2026-09-25) |
The existing `…persistence.transaction` and `…persistence.postgresql` packages already hold this
leaf's `TransactionPort` implementation and PostgreSQL vendor composition. The platform types are
@@ -79,7 +79,8 @@ existing name.
The plan declares seven JVM test suites (`test`, `integrationTest`, `contractTest`,
`migrationTest`, `failureTest`, `performanceTest`, `compatibilityTest`). This leaf already owns a
Docker-backed `postgresqlIntegrationTest` source set and its readiness Gradle tasks are registered
in a fail-closed contract (`verifyJpaReadinessRegistry` in `src/build.gradle`).
as strict lanes in this leaf's `build.gradle`; `JpaReadinessRegistryTest` holds the readiness cards
to those lanes (it replaced the build-tools `verifyJpaReadinessRegistry`).
| Plan suite | Repository lane |
|---|---|
@@ -101,7 +102,7 @@ Docker-dependent lanes fail closed rather than skipping, matching the existing
| `settings.gradle.kts` module registration | Fail-closed 19-leaf registry | No registry change: leaf identity, Gradle path, allowed dependencies, and runtime memberships are unchanged. |
| `infra/jpa/{postgres,roles,toxiproxy}` | Repository already owns `infra/` | Created at the same repository-relative paths. |
| `docs/jpa/**`, `docs/adr/ADR-JPA-*`, `.github/workflows/jpa-*.yml` | Repository already owns `docs/` and `.github/workflows/` | Created at the same repository-relative paths. |
| release blocking aggregate | `.github/workflows/jpa-release.yml` | CI names the blocking JPA lanes directly; Gradle only defines how each lane runs. |
| release blocking aggregate | `jpaReleaseQualification` (persistence-jpa `build.gradle`) over `config/jpa/release-registry.json`, run per PostgreSQL major by the `jpa-release-gate` job in `.github/workflows/release.yml` | The registry names the blocking lanes; Gradle defines how each lane runs; CI only schedules the matrix. | |
| Per-task `git add` + `git commit` | `AGENTS.md`: commit policy is `human-only`; agents do not stage, commit, amend, or push | Implementation is delivered unstaged. This is the only plan step intentionally not executed, and it is recorded here. |
| Querydsl as an optional module dependency | Querydsl is not part of this repository's dependency set | `querydsl` is implemented against the plan's contracts with the Querydsl types kept behind `compileOnly`, so the Stable runtime classpath never carries Querydsl and a deployment opting in adds the artifact itself. |
| Hibernate Envers as a module dependency | Envers is not part of this repository's dependency set | Same treatment as Querydsl: `compileOnly` + explicit opt-in, matching the plan's "Envers is opt-in and never enabled by a global base class". |
@@ -121,7 +122,7 @@ boundary the module map exists to hold.
|---|---|---|---|
| `TransactionCompletionEvidence` | `jpa-transaction` | `…persistence.api.transaction` | `TransactionCompletionUnknownException` (design §17.3 types the field) |
| `ConstraintCode` | `jpa-postgresql` | `…persistence.api.error` | `ConstraintViolationDetails` (design §22.4) |
| `SqlStateResolver`, `SqlExceptionSqlStateResolver` | `jpa-transaction` | `…persistence.api.error` | both the transaction module's commit classifier and the PostgreSQL translator |
| `SqlExceptionSqlStateResolver` | `jpa-transaction` | `…persistence.api.error` | the PostgreSQL translators |
The ArchUnit rule pack (`JpaArchitectureRules`, `EntityMappingCondition`, `EntityExposureCondition`)
is placed in the `testkit` source set rather than in `…persistence.security` production code. ArchUnit
@@ -136,10 +137,9 @@ showed it. Both are recorded here because the design text still reads the old wa
- **§17.2 commit ambiguity is not only SQLSTATE class `08`.** `pg_terminate_backend` on a backend
with a commit in flight reports `57P01` (`admin_shutdown`), not a connection-class state — and the
commit record may already be in the WAL when it arrives. `CommitFailureClassifier` now treats
`57P01`/`57P02`/`57P03` as completion-unknown alongside `40003`, class `08`, and transport breaks.
`CommitAmbiguityContractTest` asserts the SQLSTATE directly so the rule cannot silently narrow
again.
commit record may already be in the WAL when it arrives. The classifier that encoded this
(`CommitFailureClassifier`) was removed with the second transaction engine on 2026-09-25;
`PostgreSqlConcurrencyFailureContractTest` still pins the injection points.
- **Schema-per-tenant status must be read back, not inferred from the run.** `MigrateResult`'s
target version is empty for a tenant that was already current, so recording it reported migrated
tenants as unmigrated during a partial rollout. `SchemaTenantMigrationOrchestrator` now reads the
@@ -159,6 +159,7 @@ showed it. Both are recorded here because the design text still reads the old wa
`ddl-auto` never mutates a deployed schema.
- `CREATE INDEX CONCURRENTLY` requires an explicit non-transactional migration marker.
- Metric labels and ordinary logs never carry SQL parameters, entity IDs, tenant IDs, or PII.
- Experimental features (multi-tenancy, RLS, schema/database tenancy, read replica, JPA 4,
Hibernate 8, PostgreSQL 19) stay behind `backend.jpa.experimental.*` flags and never enter the
Stable composition.
- Experimental features (multi-tenancy, RLS, schema/database tenancy, read replica) are library code
a deployment constructs itself and never enter the Stable composition. JPA 4, Hibernate 8 and
PostgreSQL 19 are `NOT_EXECUTABLE` probes, not features. The `backend.jpa.experimental.*` flags
were removed on 2026-09-25: nothing read them.
+19 -16
View File
@@ -4,8 +4,8 @@ Operator procedures for the failures this platform is designed to surface rather
## A transaction reported completion unknown
**Signal:** `jpa.transaction.completion.unknown` incremented; a `CompletionUnknownRecord` in the
reconciliation channel.
**Signal:** a write use case failed with a commit-phase error (connection lost, `57P01`, class
`08`) from `TransactionPort`.
**What it means:** the commit may or may not have happened. It is not a rollback.
@@ -14,31 +14,26 @@ reason.
**Procedure:**
1. Take the `transactionKey` from the record.
1. Take the idempotency key or operation id of the failed request.
2. Check the idempotency record for that key.
3. Check the business row the use case would have written.
4. Check the outbox for a corresponding event.
5. If all three agree the write happened, mark the record `COMMITTED` and stop.
5. If all three agree the write happened, stop — the request succeeded.
6. If all three agree it did not, the use case may be re-run.
7. If they disagree or are inconclusive, leave it `STILL_UNKNOWN` and escalate. An inconclusive
answer is a legitimate outcome; guessing is not.
A record with no `transactionKey` cannot be resolved automatically — use the operation name and
timestamp.
7. If they disagree or are inconclusive, escalate. An inconclusive answer is a legitimate outcome;
guessing is not.
## Deadlock or serialization rate rising
**Signal:** `jpa.retry.attempt` rising; `jpa.retry.exhausted` non-zero.
**Signal:** `DB_DEADLOCK` / serialization failures rising in the persistence error codes.
Retries are expected. Exhaustion is not.
`SpringTransaction` does not retry, so each one reaches the caller.
1. Group `jpa.retry.attempt` by operation. A single operation dominating means a hot row or an
1. Group the failures by operation. A single operation dominating means a hot row or an
inconsistent lock order.
2. For deadlocks, check whether two operations take the same rows in opposite orders — that is a
code fix, not a tuning one.
3. For serialization failures under `SERIALIZABLE`, confirm the isolation is actually required.
4. Only then consider raising `maxAttempts`. A larger budget on a hot row converts a fast failure
into a slow one.
## Pool exhaustion
@@ -64,12 +59,20 @@ The deployment is running against a schema it was not built for. It failed close
## An invalid index exists
**Signal:** `FailedConcurrentIndexRecovery.invalidIndexes()` is non-empty.
**Signal:** this query returns rows.
```sql
select n.nspname || '.' || i.relname as invalid_index
from pg_index x
join pg_class i on i.oid = x.indexrelid
join pg_namespace n on n.oid = i.relnamespace
where not x.indisvalid;
```
A concurrent build failed. The index is ignored by the planner and maintained by every write.
1. Confirm no build is currently running. An in-progress build looks identical in the catalog.
2. Run the reported `DROP INDEX CONCURRENTLY` outside a migration.
2. Run `DROP INDEX CONCURRENTLY IF EXISTS <invalid_index>;` outside a migration.
3. Re-apply the index migration.
The platform does not drop these automatically: on a rolling deploy every instance would race to
-2
View File
@@ -59,8 +59,6 @@ Refusing the runtime role `CREATE` closes the same route from the other side.
| sort field | part of ORDER BY | `SafeSortRegistry` allowlist |
| JSON path | part of the statement | registered `JsonPathName` |
| schema name | an identifier | registered `SchemaTenantRegistry` |
| upsert conflict target | an identifier list | registered `UpsertConflictTarget` |
| COPY table | an identifier | registered `RegisteredCopyStatement` |
| queue claim SQL | a whole statement | registered `WorkQueueDefinition` |
Values are always bound. Identifiers are always registered.
+22 -27
View File
@@ -12,9 +12,10 @@ evidence, and this document describes what the registry says.
Being a rendering used to be a claim rather than a mechanism: the tables below were still typed by
hand, so a major demoted in the registry stayed Stable here and kept its full release job.
`JpaReleaseRenderingTest` now compares the database table, the gate table and `jpa-release.yml`'s
matrix and promotion lists to the registry, and `verifyJpaReleaseGateTasks` resolves every gate's
task against the real Gradle task graph. Edit the registry; these tables follow, or the build fails.
`JpaReleaseRenderingTest` now compares the database table, the gate table and `release.yml`'s JPA
matrix and promotion lists to the registry, and the `jpaReleaseQualification` aggregate depends on
every blocking gate's task, so a gate naming a task that does not exist fails when the task graph is
built. Edit the registry; these tables follow, or the build fails.
Two renderings stayed outside that comparison until they were added to it. `jpa-nightly.yml` runs
its own matrix and nothing checked it, so a demotion corrected the release lane and left the nightly
@@ -31,14 +32,14 @@ it.
| PostgreSQL 16 | Stable | full contract suite, release lane (own matrix job) |
| PostgreSQL 17 | Stable | full contract suite, release lane (own matrix job) |
| PostgreSQL 18 | Stable | full contract suite, release lane (own matrix job) |
| PostgreSQL 19 | Experimental | [`jpa-next-postgresql19.yml`](../../.github/workflows/jpa-next-postgresql19.yml) — `NOT_EXECUTABLE`: no `postgres:19-alpine` is published, so no container of that major has been started; promotion requires an ADR |
| PostgreSQL 19 | Experimental | [`jpa-next.yml`](../../.github/workflows/jpa-next.yml) — `NOT_EXECUTABLE`: no `postgres:19-alpine` is published, so no container of that major has been started; promotion requires an ADR |
| H2 | Local convenience | **never** evidence of PostgreSQL behaviour |
Each major gets its **own release job**, because for a while it did not. The release lane passed
`-Pjpa.matrix.versions=16,17,18` to a `JpaPlatformContractSupport.start()` that used
`selectedVersions().get(0)`, so the whole integration suite ran against PostgreSQL 16 and this table
recorded 17 and 18 as fully covered on the strength of a three-assertion smoke test. `start()` now
refuses a multi-version selection outright, `jpa-release.yml` fans out to one job per major, and a
refuses a multi-version selection outright, the `jpa-release-gate` job in `release.yml` fans out to one job per major, and a
promotion job requires all three majors' evidence to carry the same commit SHA — so a removed major
removes the release, not the evidence for it.
@@ -78,17 +79,18 @@ the difference visible instead of asserting a constant against itself. See
## Capability support levels
The levels are the ones `JpaPlatformAutoConfiguration.capabilities()` reports through the
`jpaplatform` actuator endpoint. Advanced and Experimental rows are library code a service calls
itself (`src/adapter/outbound/persistence-jpa/README.md` "라이브러리 API").
| Capability | Level |
|---|---|
| Full-transaction retry | Stable |
| Commit completion evidence | Stable |
| Keyset pagination | Stable |
| JDBC batch | Stable |
| Flyway schema gate | Stable |
| Runtime role verification | Stable |
| Observability | Stable |
| PostgreSQL native write (`ON CONFLICT`/`RETURNING`) | Advanced |
| PostgreSQL work claim (`SKIP LOCKED`) | Advanced |
| Commit completion evidence | Advanced |
| JDBC batch | Advanced |
| Observability (query metrics, redaction) | Advanced |
| PostgreSQL JSONB | Advanced |
| PostgreSQL array and range | Advanced |
| Bulk DML | Advanced |
@@ -113,24 +115,17 @@ Each row is a way the platform could pass its tests and still be wrong in produc
| `runtime-role-no-ddl` | gate | the application's own credential being able to alter or drop schema objects |
| `collection-fetch-pagination` | gate | a paged collection fetch silently reading the whole table and paginating in memory |
### The two audit mechanisms
### The audit mechanism
`audit/AuditableEntity` is the canonical one: `created_*`/`updated_*`, a 256-character actor,
stamped explicitly by the repository adapter. It is what the sample entities extend and what the
migrations were written for.
`audit/AuditableEntity` is the only one: `created_*`/`updated_*`, a 256-character actor, stamped
explicitly by the repository adapter. It is what the sample entities extend and what the migrations
were written for. A second, Spring Data listener-based mechanism (`auditing/AuditMetadata`) was never
composed and has been removed; `JpaAuditMechanismRule.entitiesUseExactlyOneAuditMechanism` keeps it
from coming back on an entity.
`auditing/AuditMetadata` is a second, complete mechanism with different column names
(`modified_*`), a different actor length (64) and a different capture lifecycle (Spring Data
listeners). Nothing embeds it and nothing composes `JpaAuditingConfiguration`, which is why it is
listed as a candidate rather than as a capability: promoting it means choosing between reshaping it
to the canonical columns and writing a forward migration for the new ones, and that choice has not
been made. Until it is, an entity picks one mechanism or none — enforced on the production graph by
`JpaAuditMechanismRule.entitiesUseExactlyOneAuditMechanism`.
Neither mechanism reaches a bulk or native update. Both stamp on an ordinary save — one in the
adapter, one on a managed entity's lifecycle — so a statement that goes straight to the database
leaves the audit columns showing the previous save. A bulk update of an audited entity must
therefore set the audit column in the statement, which
The mechanism does not reach a bulk or native update. It stamps on an ordinary save in the adapter,
so a statement that goes straight to the database leaves the audit columns showing the previous save.
A bulk update of an audited entity must therefore set the audit column in the statement, which
`JpaAuditMechanismRule.bulkUpdatesOfAuditedEntitiesStampAudit` checks over the production graph.
## Explicitly unsupported
+30 -41
View File
@@ -4,63 +4,52 @@ Design §15-§20. What owns a transaction, what may be retried, and what must ne
## The application service owns the boundary
Repository adapters do not open transactions. The use case does, through `TransactionPort` or
`JpaTransactionExecutor`, because the unit of work is a business decision and only the use case
knows where it starts and ends.
Repository adapters do not open transactions. The use case does, through `TransactionPort`,
because the unit of work is a business decision and only the use case knows where it starts and
ends. `SpringTransaction` is the only implementation: one pre-built `TransactionTemplate` per
mode over Spring's `PlatformTransactionManager`, every mode pinned to `READ_COMMITTED`.
| Call | Propagation | When |
|---|---|---|
| `inWrite` | `REQUIRED`, read-write | command default |
| `inRootWrite` | `REQUIRED`, read-write, rejects an ambient transaction before running | orchestration that must prove a physical commit |
| `inRead` | `REQUIRED`, read-only | query default |
| `inNew` | `REQUIRES_NEW`, read-write | outbox / audit / compensation that must commit on its own |
Open Session In View is off in every runtime profile. It is on by default in Spring Boot, which is
why `JpaDangerousConfigurationGuard` fails startup rather than trusting configuration review.
## Profiles
A `TransactionProfile` fixes propagation, isolation, timeout, read-only, and the retry budget. A
write profile must carry a positive finite timeout — the type refuses to represent one without —
because an unbounded write transaction holds a connection, its locks, and its row versions for as
long as one stuck statement takes.
`REQUIRES_NEW` is opt-in. It acquires a second physical connection while pinning the first, so a
profile using it must be paired with the pool-pressure evidence in design §38:
`REQUIRES_NEW` acquires a second physical connection while pinning the first, so the pool must
satisfy:
```text
maximumPoolSize >= (concurrent_threads x (1 + max_requires_new_depth)) + 1
```
## Retry is per use case, never per statement
## Nothing is retried by the port
`FullTransactionRetryCoordinator` re-enters the executor, which produces a new transaction and a new
Persistence Context for every attempt. That granularity is the whole point: an optimistic conflict
means the state the attempt computed against is no longer the committed state, so re-issuing the
same statement would compute the same wrong answer. The domain rules have to run again against
reloaded data.
`SpringTransaction` runs the action once. A failure rolls back and propagates, translated to
the shared persistence error codes where the SQLSTATE is known. A caller that decides to retry must
re-run the whole use case in a new transaction — never re-issue one statement — because an
optimistic conflict or a serialization failure means the state the attempt computed against is no
longer the committed state.
Retryable: serialization failure (`40001`), deadlock (`40P01`), optimistic conflict.
Not retryable: constraint violations, schema mismatch, query timeout, and anything unclassified.
Two additional refusals, independent of budget:
- An attempt that declared an irreversible external effect through `IrreversibleSideEffectContext`.
Rollback reverses database work only; an email or a card charge has already changed the world.
- Anything completion-unknown.
A second engine with named policies, deadline budgets, transaction-local timeouts and automatic
full-transaction retry (`SpringJpaTransactionExecutor`, `FullTransactionRetryCoordinator`,
`PolicyTransactionPort`) existed next to this one and was removed on 2026-09-25. Its last commit is
recorded in `docs/capability-status.md`.
## Completion unknown
`TransactionCompletionUnknownException` is never retried, and the type system enforces it twice:
`JpaFailureContext` refuses to represent a retryable completion-unknown failure, and the exception
rebuilds its context through the safe factory whatever it is handed.
`EvidenceAwareJpaTransactionManager` marks the phase `COMMITTING` immediately before delegating to
the provider commit and never after. If the network, the JVM, or the server dies inside that call,
the last thing written is "we asked, we do not know" — which is exactly the state that must not be
mistaken for a rollback.
A connection can break while a commit is in flight; the server may have committed and only the
acknowledgement was lost. `TransactionCompletionUnknownException` is never retried, and the type
system enforces it: `JpaFailureContext` refuses to represent a retryable completion-unknown failure.
The port itself retries nothing, so such a commit surfaces to the caller as a failure exactly once
(`PostgreSqlTransactionIntegrationTest#connectionLossDuringCommitSurfacesAsAFailureAndIsNeverRetried`).
Recovery is reconciliation, not retry:
```text
record the transaction key -> check the idempotency record
-> check the business row
-> check the outbox
-> still undetermined? reconciliation queue
check the idempotency record -> check the business row -> check the outbox
-> still undetermined? escalate
```
`CompletionUnknownRecorder` writes that record through a channel outside the unknown transaction.
Writing it through the same connection would make the audit trail share the failure it documents.
+50 -50
View File
@@ -21,20 +21,16 @@ Application의 canonical integration event를 platform publish pipeline으로
producing-service identity다.
값이 없으면 `IntegrationEventPublishPort` bridge 자체를 만들지 않는다. `spring.application.name`이나
현재 process 이름으로 추론하지 않는다. 기존 legacy `OutboxEvent`/realtime 경로는 별도 cutover가
끝날 때까지 `app.messaging.broker` 경로를 유지한다.
현재 process 이름으로 추론하지 않는다. 모든 발행(outbox relay 포함)이 이 bridge를 지나므로 messaging
모듈이 켜진 상태에서 값이 없으면 기동이 거부된다.
## Outbox canonical transport-only cutover
## Outbox
`APP_OUTBOX_CANONICAL_TRANSPORT_ENABLED` / `ca-skeleton.outbox.canonical-transport-enabled`은
기존 `outbox_event` writer/claim/status authority를 유지한 채 canonical row의 **transport만** platform
publish path로 보내는 compatibility gate다. 기본값은 `false`이며 `POLLING_V2`를 활성화하지 않는다.
`true`일 때는 `OutboxAppendPort`가 `ValidatedIntegrationEvent`의 exact envelope bytes와 canonical
metadata를 기존 outbox row에 저장하고, claim된 canonical row는 `IntegrationEventPublishPort`로 간다.
legacy row는 계속 `MessageBroker`를 사용한다. 따라서 mixed-row compatibility 기간에는 relay가 켜져
있다면 `app.messaging.broker`도 계속 필요하며, canonical path를 위해 `IntegrationEventPublishPort`도
추가로 필요하다. legacy backlog가 0이라는 별도 증거 없이 broker 요구를 제거하지 않는다.
outbox는 canonical 하나다(2026-09-28). use case가 `IntegrationEventEncoderPort`로 만든
`ValidatedIntegrationEvent`를 `OutboxAppendPort`로 append하고, relay는 claim한 row의 exact envelope
bytes를 `IntegrationEventPublishPort`로 보낸다. 예전의 `app.outbox.canonical-transport-enabled`
gate와 legacy `MessageBroker → KafkaSender` 경로는 삭제됐다. 발행할 contract의 logical destination마다
아래 destination profile을 선언한다(템플릿의 durable operation event는 `durable-operations`).
## Destination profile
@@ -135,9 +131,10 @@ app:
## Broker profile
브로커는 `app.messaging.brokers` 아래에 한 번만 기술한다. `type`이 어느 계열의 설정이 적용되는지
결정하며, 다른 계열의 키(Kafka 항목의 `prefetch` 같은)는 무시되지 않고 부팅 실패로 거절된다 —
무시하면 그 줄을 쓴 사람은 무언가가 적용됐다고 믿게 된다.
브로커는 `app.messaging.brokers` 아래에 한 번만 기술한다. `type`은 `kafka`만 받는다 — transport가
있는 계열이 Kafka 하나뿐이다. RabbitMQ 키(`addresses`, `prefetch`, `quorum-queues` 등)와
`type: rabbitmq`는 2026-09-25에 설정 모델에서 삭제됐다. 연결할 transport 없이 바인딩만 되던 키라,
지금은 무시되지 않고 키 이름을 담아 부팅 실패로 거절된다.
### Kafka
@@ -160,32 +157,17 @@ app:
authentication-enabled: false # production이면 필수
```
### RabbitMQ
```yaml
app:
messaging:
brokers:
rabbit-primary:
type: rabbitmq
stable: true
production: false
addresses: [rabbit-1:5671]
publisher-confirms: true # stable에서 필수
publisher-returns: true # stable에서 필수
mandatory: true # stable에서 필수
confirm-timeout: 5s
auto-ack: false # 항상 금지
prefetch: 16
quorum-queues: true # durable work queue 필수
tls-enabled: false
authentication-enabled: false
```
`production: true`인 브로커는 `tls-enabled`와 `authentication-enabled`가 모두 참이어야 하고,
그렇지 않으면 `KafkaProfileValidator` / `RabbitProfileValidator`가 부팅을 거절한다. 위 예시가
`production: true`인 Kafka 브로커는 `tls-enabled`와 `authentication-enabled`가 모두 참이어야 하고,
그렇지 않으면 `KafkaProfileValidator`가 부팅을 거절한다. `app.messaging.broker`로 고를 수 있는 값은
`kafka`뿐이다. 위 예시가
`production: false`인 것은 이 페이지가 그대로 실행되는 fixture이기 때문이며, 실 배포는 셋 다 참이다.
Kafka producer는 이 항목 하나로 만든다. `bootstrap-servers`, `acks`, `enable-idempotence`,
`max-in-flight-requests-per-connection`, `delivery-timeout`이 그대로 client 설정이 된다.
`spring.kafka.bootstrap-servers`는 읽지 않는다. type이 `kafka`인 항목이 정확히 하나가 아니면 기동에
실패한다. `send()`가 metadata를 기다리며 호출 스레드를 막는 시간(`max.block.ms`)은 기본 publish
timeout(5s)이다.
## 보안
```yaml
@@ -197,6 +179,8 @@ app:
consumer: { type: SASL_SCRAM, credential-id: kafka-consumer }
# admin은 application runtime에 설정하지 않는다
hostname-verification: true
# 사설 CA로 서명된 TLS 브로커면(tls-enabled: true일 때만):
# trust-store: { location: /etc/kafka/ca.p12, type: PKCS12, password-credential-id: kafka-truststore }
access:
publishable: [order-events]
consumable: []
@@ -211,21 +195,37 @@ app:
연결 시점에 해석하므로, 설정 덤프나 힙 덤프에서 나오는 것은 이름뿐이다. producer와 consumer는
서로 다른 `credential-id`를 써야 하며, 같으면 부팅에 실패한다.
## Experimental / Optional
`SASL_SCRAM`·`USERNAME_PASSWORD`의 사용자 이름은 `CredentialProvider.username(credentialId)`가
준다. credential id를 사용자 이름으로 보내지 않는다. 비밀번호와 사용자 이름은 JAAS 문자열에 들어가지
않고, 연결이 인증할 때마다 provider에서 읽힌다. 그래서 provider가 만료 시각을 주는 credential은
재기동 없이 rotation된다(`security.md`).
기본값은 전부 `false`다.
`MUTUAL_TLS`는 클라이언트 인증서를 key store로 제출한다. `credential-id`는 key store 비밀번호를
가리킨다.
```yaml
app:
messaging:
experimental:
kafka-share: false
pulsar: false
nats: false
bridge:
spring-cloud-stream: false
```text
producer:
type: MUTUAL_TLS
credential-id: kafka-producer-tls # key store 비밀번호
key-store: { location: /etc/kafka/producer.p12, type: PKCS12 }
```
`trust-store`를 생략하면 JVM 기본 trust store를 쓴다. 사설 CA 브로커는 `trust-store.location`
(PKCS12·JKS·PEM)과, 잠긴 store면 `password-credential-id`를 준다.
Kafka producer는 이 항목을 실제 클라이언트 설정(`security.protocol`, `sasl.mechanism`,
`sasl.jaas.config`, `sasl.client.callback.handler.class`, `ssl.truststore.*`, `ssl.keystore.*`,
`ssl.enabled.protocols=TLSv1.3,TLSv1.2`, hostname 검증)으로 옮긴다. 평문으로 조용히 넘어가지
않도록 다음 경우 부팅에 실패한다: 브로커가 `tls-enabled`나 `authentication-enabled`를 켰는데
`app.messaging.security.<broker>`가 없을 때, security 항목은 있는데 `CredentialProvider` bean이 없을
때, 같은 브로커에 맞는 항목이 둘 이상일 때, provider가 SASL 사용자 이름을 주지 않을 때,
`MUTUAL_TLS`인데 `key-store`가 없거나 `tls-enabled`가 꺼져 있을 때, `trust-store`를 줬는데
`tls-enabled`가 꺼져 있을 때, store 파일을 열 수 없을 때.
`access.publishable`은 강제된다. security 항목이 있는 브로커의 destination은 이 목록에 있어야
publish된다. 목록 밖 publish는 `REJECTED`(`PUBLISH_FORBIDDEN`)이고, 빈 목록이면 아무것도 publish되지
않는다.
## Backpressure
```yaml
+3 -2
View File
@@ -27,8 +27,9 @@
`PublishResult` → `OutboxPublishOutcome`. registry에 leaf를 추가하는 변경이라 별도 커밋.
- golden contract 테스트: event/message ID, type, schema revision, partition/order/correlation/
causation/tenant/trace, payload digest, wire version이 bytes 단위로 보존되는지.
- 단일 publication authority: 기존 `OutboxPublicationAuthority` fence를 재사용해 writer/relay가
동시에 ACTIVE가 되지 않도록. **dual write/publish는 금지** — 한 business fact가 두 durable store와
- 단일 publication authority: writer/relay가 동시에 ACTIVE가 되지 않도록 하는 fence. 이 용도로 쓰려던
outbox V2의 `OutboxPublicationAuthority`는 한 번도 조립되지 않은 채 2026-09-25에 삭제됐으므로
(`docs/capability-status.md` "제거된 코드") cutover가 자기 fence를 새로 가져야 한다. **dual write/publish는 금지** — 한 business fact가 두 durable store와
두 relay로 나가는 상태가 cutover에서 가장 위험하다.
- 첫 cutover 범위는 **transport만** 교체(저장소는 기존 유지). storage migration은 shadow read →
authority switch → old backlog drain 순서로 별도 release.
+9 -48
View File
@@ -17,24 +17,22 @@ stopsAcceptingNewWorkDuringShutdown
**Experimental**은 아직 그 증명이 끝나지 않은 어댑터다.
현재 Experimental 어댑터는 없다. Kafka Share Group·Pulsar·NATS JetStream(Experimental), RabbitMQ,
Spring Cloud Stream bridge(Optional)는 SDK 없는 seam이거나 선택할 수 없는 상태여서 2026-09-25에
삭제했다(`docs/capability-status.md` 제거 표). 이 문서는 새 어댑터를 들일 때 지킬 규칙이다.
## 규칙
### 1. 기본 비활성
```yaml
messaging.experimental.kafka-share: false
messaging.experimental.pulsar: false
messaging.experimental.nats: false
```
새 Experimental 어댑터는 자기 활성화 플래그를 가지고 기본값은 `false`다.
활성화하지 않으면 validator가 `MessagingCapabilityUnavailableException`을 던진다.
Contract Suite가 아직 증명 중인 어댑터가 누군가의 기본 설정 때문에 load-bearing이 되어서는 안 된다.
### 2. Stable 모듈이 Experimental 모듈에 의존하지 않는다
Gradle 의존 그래프로 강제된다. `messaging-spring-boot-starter`의 `allowed_dependencies`에
`messaging-kafka-share-experimental`, `messaging-pulsar-experimental`,
`messaging-nats-experimental`, `messaging-spring-cloud-stream-bridge`가 **없다**.
Gradle 의존 그래프로 강제된다. Experimental leaf는 `messaging-spring-boot-starter`의
`allowed_dependencies`에 넣지 않는다.
`verifyCleanArchitectureDependencies`가 위반을 빌드 실패로 만든다.
@@ -45,45 +43,8 @@ Experimental 어댑터는 브로커의 차이를 `MessagingCapabilities`로 표
### 4. 없는 기능을 광고하지 않는다
| 어댑터 | 광고하지 않는 것 | 이유 |
|---|---|---|
| Kafka Share Group | orderedStream, keyedOrdering, replay, brokerTransaction | 경쟁 소비자 + 개별 ack는 partition 순서를 유지할 수 없다 |
| Pulsar | brokerTransaction | Pulsar에 있지만 플랫폼 Contract Suite로 증명되지 않았다 |
| Pulsar (Shared) | keyedOrdering | round-robin 분배 |
| NATS JetStream | nativeDeadLetter | delivery limit 초과 시 terminate할 뿐 라우팅하지 않는다 |
| NATS JetStream | keyedOrdering | subject 기반 모델에 per-key 순서가 없다 |
`false`인 capability를 요구하는 profile은 startup에서 실패한다.
조용히 약화되지 않는다.
### 5. 명시적 거부
| 조합 | 결과 |
|---|---|
| Kafka Share Group + ordering != NONE | 거부 |
| Kafka Share Group + pause/resume | `MessagingCapabilityUnavailableException` |
| Pulsar Shared + ordering=KEY | 거부 (Key_Shared 필요) |
| Pulsar + ordering=DESTINATION | 거부 |
| NATS Core + AT_LEAST_ONCE | 거부 (JetStream 필요) |
| NATS ordered consumer + 경쟁 워커 > 1 | 거부 |
| NATS + ordering=KEY | 거부 |
## Spring Cloud Stream bridge
Experimental이 아니라 **Optional**이다. 위험이 다르다.
Stream은 자체 binder 설정을 소유하므로, binding이 destination profile이 모르는
serializer·error handling·acknowledgement mode를 조용히 획득할 수 있다.
따라서 브리지는 **플랫폼 보장에 의존하지 않는 destination에만** 허용한다.
```text
ordering scope 선언 → 거부
retry policy 선언 → 거부
dead letter 선언 → 거부
```
이 셋 중 하나라도 필요하면 native adapter를 쓴다. 거기서만 실제로 강제되기 때문이다.
Contract Suite로 증명하지 않은 capability는 `MessagingCapabilities`에서 `false`로 둔다.
`false`인 capability를 요구하는 profile은 startup에서 실패한다. 조용히 약화되지 않는다.
## 승격 조건
+1 -2
View File
@@ -3,8 +3,7 @@
## 배포 전 체크
```bash
./gradlew verifyCleanArchitectureDependencies --console=plain
./gradlew verifyRuntimeModuleMembership --console=plain
./gradlew architectureCheck --console=plain
./gradlew checkstyleMain --console=plain
```
+40 -8
View File
@@ -21,8 +21,8 @@ Flyway version `1000..1999`를 예약해서 애플리케이션의 일반적인
classpath:db/migration/messaging
```
현재 순서는 `V1001..V1004`(outbox/admin)와 `V1101`(inbox)이다. starter 테스트가 두 JDBC
모듈을 실제 combined classpath로 올려 version 중복과 예약 대역 이탈을 검사한다. 개별 DDL의
현재 순서는 `V1001..V1005`(outbox/admin)와 `V1101`(inbox)이고, 모두
`messaging-reliability-jdbc-postgresql`에 있다. starter 테스트가 그 모듈을 실제 combined classpath로 올려 version 중복과 예약 대역 이탈을 검사한다. 개별 DDL의
의미와 전환 순서는 [migration-guide.md](migration-guide.md)를 따른다.
## Outbox
@@ -39,13 +39,18 @@ COMMIT;
### relay
```text
leaseBatch(100, 30s) -- lease로 다중 relay 인스턴스 안전
claimBatch(owner, 100, 30s, now, maxAttempts) -- owner + fencing token으로 다중 relay 인스턴스 안전
→ publish (messageId 그대로)
→ CONFIRMED → markPublished
→ AMBIGUOUS → markAmbiguous (같은 messageId로 재시도 가능)
→ REJECTED → markFailed
```
row 하나의 실패는 그 row에서 끝난다. envelope로 만들 수 없는 row(예약 header `msg.*`를 담은 row
등)는 `FAILED`가 되고, publisher가 예외를 던지면 결과를 모르므로 `AMBIGUOUS`가 된다. 같은 batch의
나머지 row는 그대로 publish된다. pass 전체가 실패하면(DB 연결 등) WARN 로그를 남기고
`messaging.outbox.relay.failed.passes` 카운터를 올린다.
### 핵심 규칙: ambiguous는 같은 messageId로 재시도
새 id를 발급하면 "전달됐을 수도 있는 메시지"가 "확실히 두 번째인 메시지"가 되어
@@ -61,8 +66,16 @@ status IN ('PENDING','AMBIGUOUS','IN_FLIGHT')
AND (lease_expires_at IS NULL OR lease_expires_at <= now)
AND next_attempt_at <= now
AND attempts < maxAttempts
AND (ordering_key IS NULL
OR 같은 destination·ordering_key의 더 오래된 미완료 row가 없음)
```
`ordering_key`가 있는 row는 같은 key의 더 오래된 row가 `PENDING`·`AMBIGUOUS`·`IN_FLIGHT`인 동안
claim되지 않는다. 이 조건이 없으면 두 relay가 같은 key의 두 row를 나눠 가져가거나, AMBIGUOUS로
재시도되는 row보다 뒤의 row가 먼저 나간다(`OutboxPostgresIT#aNewerRowWaitsWhileAnOlderRowWithTheSameOrderingKeyIsUnfinished`).
`V1005`의 partial index가 이 확인을 받친다. 더 오래된 row가 `FAILED`·`EXHAUSTED`가 되면 뒤의 row는
진행한다.
`IN_FLIGHT`가 목록에 있는 것이 핵심이다. relay가 publish 도중 죽으면 row는 `IN_FLIGHT`로 남는데,
이를 제외하면 그 메시지는 **영원히** 발행되지 않는다 — outbox가 막으려던 바로 그 실패다. 대신
lease가 만료됐을 때만 회수하므로, 살아 있는 relay가 들고 있는 row는 회수되지 않는다.
@@ -95,6 +108,24 @@ transactions.inTransaction(() -> {
별도 transaction으로 예약하면 Inbox가 닫으려던 바로 그 창이 다시 열린다.
### 소비와 연결 (소유자 결정 10)
consume 계약은 `MessageHandler<T>` 하나다. handler를 bean으로 등록하면 `messaging-spring-boot-starter-kafka`가
그 handler가 가리키는 destination마다 Kafka consumer를 연다(`app.messaging.enabled=false`면 없다).
- destination profile이 `guarantees.external-side-effect: INBOX_TRANSACTIONAL`이면 platform이 handler를
`InboxMessageHandler`로 감싼다. 예약과 handler의 쓰기가 같은 transaction에서 commit되고, 이미 예약된
message는 handler를 부르지 않고 `Success`로 settle한다. 이 경우 애플리케이션이 `IdempotentConsumer`
bean(inbox repository + transaction runner)을 둬야 하며, 없으면 기동이 실패한다.
- inbox의 consumer 식별자와 Kafka `group.id`는 destination의 `consumer.group`이다. 없으면 기동이 실패한다.
- offset은 handler가 `Success`로 답하고 (inbox destination이면) 그 transaction이 commit된 뒤에만, 또는
DLQ 토픽 기록이 확인된 뒤에만 넘어간다. auto-commit은 쓰지 않는다.
- `Retry`·예외·timeout은 `retry.max-attempts`까지 partition을 멈추고 다시 읽으며, 다 쓰면 DLQ 토픽에
원본 record를 남기고 넘어간다. DLQ가 없는 destination(at-most-once)은 넘어가지 않고 멈춘다.
- `Reject`는 at-most-once destination에서만 버리고, 그 밖에서는 dead letter로 보낸다.
실제 왕복·중복 제거·DLQ는 `MessagingKafkaConsumeQualificationTest`(Kafka + PostgreSQL Testcontainers)가 확인한다.
### 복합 키
`PRIMARY KEY (message_id, consumer_id)`.
@@ -107,13 +138,14 @@ message_id만으로 중복 제거하면 같은 event를 소비하는 두 번째
broker의 최대 redelivery window보다 **길어야** 한다.
row를 먼저 지우면 늦게 도착한 redelivery가 두 번 처리된다.
## Debezium CDC 대안
outbox·inbox cleanup job은 한 번에 최대 1,000행씩 지우고, 지운 수가 1,000보다 적으면 멈춘다.
repository port에는 개수 제한 없는 삭제 메서드가 없다.
polling relay 대신 WAL을 읽는다. polling interval과 lease 경합이 사라지지만
인프라와 그 자체의 실패 모드가 추가된다.
## CDC 대안
wire contract는 동일하다. `DebeziumOutboxEventRouter`가 polling relay와 같은 reserved header를
방출하므로 consumer는 어느 쪽이 발행했는지 구분할 수 없고, 전환은 배포 결정일 뿐 계약 변경이 아니다.
relay는 polling 하나뿐이다. Debezium Event Router 매핑(`DebeziumOutboxEventRouter` 등)은 조립하는
곳이 없어 2026-09-25에 삭제했다(`docs/capability-status.md` 제거 표). `messaging_outbox`의
`routing_key` 컬럼은 남아 있으므로 CDC를 다시 들일 때 그 컬럼을 message key로 쓴다.
## Claim Check
+9
View File
@@ -49,6 +49,15 @@ full jitter는 `[0, delay]` 균등 분포다. jitter가 없으면 같은 초에
pause-and-seek는 메시지가 로그의 자기 자리를 떠나지 않는다. partition을 멈추고, 기다리고,
같은 offset으로 seek해 재전달한다. 뒤의 메시지도 함께 기다리며 이것이 의도된 동작이다.
`KafkaConsumerRegistrar`가 handler 실패(예외, settle 없이 끝남, timeout)를 다루는 방식:
- 재전달은 destination `retry`의 backoff 뒤에 한다. 최소 1초. 0초 재시도는 없다.
- 같은 offset의 실패 횟수가 `retry.maxAttempts`에 닿으면 `KafkaQuarantinePublisher`에 쓰고,
쓰기가 확인되면 offset을 넘긴다. quarantine이 없으면 backoff로 계속 재시도한다(메시지를 버리지
않는다). 그래서 `production` destination은 quarantine 없이 만들 수 없다(`KAFKA_QUARANTINE_REQUIRED`).
- handler timeout이 지나도 handler가 끝날 때까지 partition slot을 잡고 있는다. `CompletableFuture`를
cancel해도 handler는 멈추지 않으므로, slot을 먼저 풀면 같은 offset이 두 번 동시에 돈다.
## RabbitMQ: delayed retry queue
core broker에 per-message delay가 없으므로 **TTL + DLX**로 구현한다.
+22 -6
View File
@@ -36,17 +36,30 @@ heap dump나 설정 출력에서 사용 가능한 credential이 나오지 않는
`CredentialIds`는 `bearer `, `sk-`, `-----begin`, `eyJ` 같은 접두사를 거부한다.
참조가 들어갈 자리에 secret 자체를 붙여넣는 가장 흔한 사고를 막는다.
SASL(PLAIN·SCRAM) 사용자 이름도 `CredentialProvider.username(credentialId)`가 준다. credential id는
저장소 안의 참조이지 broker가 아는 사용자 이름이 아니다. provider가 이름을 주지 않으면 기동에
실패한다.
key store·trust store는 경로만 설정에 둔다. 비밀번호는 credential id로 provider가 해석한다
(`configuration-reference.md` 보안 절).
## Rotation
`CredentialRotationPlan.isDue()`는 만료 **전에** 참이 된다.
broker가 연결을 거부하기 시작한 시점에는 이미 publish가 실패하고 consumer가 멈춰 있다.
rotation은 세대 교체다. `DefaultMessagingRuntimeRegistry.install()`이 새 세대를 원자적으로
게시하고, 이전 세대는 마지막 lease가 닫힐 때까지 열려 있다가 닫힌다.
진행 중인 publish는 시작한 연결에서 confirm을 받는다.
Kafka SASL credential은 producer를 다시 만들지 않고 바뀐다. JAAS 설정에는 login module 이름만
있고, `KafkaCredentialCallbackHandler`가 연결이 인증할 때마다 `CredentialRuntimeRegistry`에서
사용자 이름과 비밀번호를 읽는다. registry는 provider가 준 만료 시각의 rotation lead(기본 30분)
안으로 들어오면 새로 가져오므로, 새 연결과 재인증(broker `connections.max.reauth.ms`)이 새 값을
쓴다. 만료 시각을 주지 않는 provider의 credential은 캐시된 값을 계속 쓴다.
drain deadline이 이 대기를 제한한다. 없으면 lease 하나가 새면 폐기된 credential이
무기한 열려 있고, rotation이 보안상 무의미해진다.
key store·trust store 비밀번호는 예외다. Kafka가 SSL context를 만들 때 한 번 읽으므로 바꾸려면
producer를 다시 만들어야 한다(재기동).
transport 세대 교체(`DefaultMessagingRuntimeRegistry.install()`)는 transport 자체를 바꿀 때 쓴다.
새 세대를 원자적으로 게시하고, 이전 세대는 마지막 lease가 닫힐 때까지 열려 있다가 닫힌다.
drain deadline이 이 대기를 제한한다.
## Header
@@ -66,10 +79,13 @@ logical identity가 호출자 제어가 된다.
## ACL
`DestinationAccessValidator`가 broker ACL **이전에** 검사한다.
publisher가 broker ACL **이전에** 검사한다(`PUBLISH_FORBIDDEN`).
broker ACL 거부는 애플리케이션 컨텍스트가 없는 연결 수준 오류로 도착하므로
"어느 모듈이 어디에 publish하려 했는가"가 조사 대상이 된다.
publish 가능한 destination은 선언된 destination이다. broker에 `app.messaging.security.<broker>`
항목이 있으면 그중 `access.publishable`에 적힌 것만 남는다(빈 목록이면 publish 불가).
## 관측성 누출
`MessagingRedactor`는 denylist다.
+29 -49
View File
@@ -4,10 +4,12 @@
여기 없는 조합은 지원되지 않는다.
> **등급은 증거를 따른다.** `CompatibilityMatrix.Entry.hasLiveBrokerCertification()`은 선언된
> boolean이 아니라 `CertifiedEvidence`가 가진 레인 증거에서 파생된다. RabbitMQ가 Stable에서 내려온
> 이유가 이것이다 — 어댑터는 공유 contract 7개를 통과하고 `RabbitBrokerIT`가 실 컨테이너에서 정상
> 경로를 돌리지만, 이 저장소의 Stable 기준인 **장애 시나리오 증거**가 하나도 없다. 레인이 생겨
> 증거를 내면 등급은 코드 수정 없이 따라 올라간다.
> boolean이 아니라 `CertifiedEvidence`가 가진 레인 증거에서 파생된다. 레인이 생겨 증거를 내면 등급은
> 코드 수정 없이 따라 올라간다.
> **삭제된 어댑터.** RabbitMQ(선택할 수 없던 validator·설정 모음), Pulsar·NATS JetStream·Kafka Share
> Group(Experimental, SDK 없는 seam), Spring Cloud Stream bridge, Debezium outbox 매핑은 2026-09-25에
> 삭제했다. 복구 경로는 `docs/capability-status.md`의 제거 표에 있다.
> **인증 근거.** 이 표의 버전은 이 저장소의 컨테이너 레인이 실제로 실행한 이미지다. 이전 판은
> Kafka 4.2/4.3을 선언했지만 fixture는 `apache/kafka:4.1.0`, lockfile client는 4.1.1이었다 — 표와
@@ -15,8 +17,10 @@
> `BrokerFailureMatrix.shipped()` 하드코딩이 아니라 레인이 낸 증거(`BrokerCertificationEvidence`)에서
> 나온다. 증거가 없는 조합은 `NOT_COVERED`다 (MSG-014).
> **모듈 이름과 런타임 편입.** `messaging-outbox-jdbc-postgresql` / `messaging-inbox-jdbc-postgresql`은
> 이전에 `-jpa`로 불렸다. 구현은 Spring JDBC이고 SQL은 PostgreSQL 전용(`?::jsonb`,
> **모듈 이름과 런타임 편입.** 관계형 신뢰성 구현은 `messaging-reliability-jdbc-postgresql`,
> 그 port만 보는 relay·consumer 로직은 `messaging-reliability`다(2026-09-28에
> `messaging-outbox-jdbc-postgresql` / `messaging-inbox-jdbc-postgresql`을 이렇게 나눴다). 그 전에는
> `-jpa`로 불렸다. 구현은 Spring JDBC이고 SQL은 PostgreSQL 전용(`jsonb`,
> `FOR UPDATE SKIP LOCKED`, `ON CONFLICT`, `TIMESTAMPTZ`)이므로, 그 이름은 쓰지 않는 기술을
> 광고하고 vendor 중립 port(`messaging-reliability-api`)의 위치를 가렸다 (MSG-023).
>
@@ -29,10 +33,7 @@
| 브로커 | 등급 | 인증 기준 | Stable 기능 | 제한 |
|---|---|---|---|---|
| Kafka | Stable | 4.1.x | producer idempotence, consumer group, batch, pause/resume, replay, transaction capability | Share Group은 Experimental |
| RabbitMQ | Experimental | 4.3.x | exchange/routing, publisher confirm, mandatory return, manual ACK, quorum queue, retry queue, DLQ | **현재 starter에서 선택 불가** — production `RabbitChannelPublisher`/transport bridge가 없어 `app.messaging.broker=rabbit`은 startup에서 거부된다. 장애 시나리오 증거도 아직 없음 |
| Pulsar | Experimental | 4.0 LTS + 4.2 | typed publish/consume, Shared, Key_Shared, schema | transaction 미승격, 기본 비활성 |
| NATS JetStream | Experimental | 2.14.x | stream, durable consumer, explicit ACK, dedupe, replay | native DLQ 없음(플랫폼이 대행), 기본 비활성 |
| Kafka | Stable | 4.1.x | producer idempotence, consumer group, batch, pause/resume, replay, transaction capability | Share Group 미지원 |
| Artemis/JMS | Extension | 범위 밖 | adapter SPI만 | 별도 ADR + Contract Suite 통과 필요 |
## Capability 매트릭스
@@ -40,27 +41,20 @@
`MessagingCapabilities`가 런타임에 선언하는 값이다. `false`인 기능을 요구하는 destination profile은
**startup에서 실패**하며, 조용히 약화되지 않는다.
| Capability | Kafka | Kafka Share | RabbitMQ | Pulsar | NATS JS |
|---|---|---|---|---|---|
| brokerAcknowledgement | O | O | O | O | O |
| replicationOrPersistenceEvidence | O | O | O | O | O |
| perMessageSettlement | O | O | O | O | O |
| batchSettlement | O | X | X | O | O |
| orderedStream | O | **X** | X | X | O |
| keyedOrdering | O | **X** | X | Key_Shared만 | X |
| replay | O | X | X | O | O |
| delayedDelivery | X | X | retry queue로 대행 | O | X |
| brokerTransaction | O | X | X | 미승격 | X |
| deduplicatedPublish | O | X | X | X | O |
| nativeDeadLetter | X | X | O | O | **X** |
| topologyManagement | O | X | O | O | O |
Kafka Share Group이 ordering 전부 `X`인 것은 설계 결정이다. share group은 개별 record를
경쟁 소비자에게 나눠주고 개별 ack하므로 partition 순서를 유지할 수 없다. ordered destination을
share group에 설정하면 `KafkaShareProfileValidator`가 거부한다.
NATS JetStream의 `nativeDeadLetter=X`도 마찬가지다. JetStream은 delivery limit 초과 시 메시지를
**terminate**할 뿐 어디로도 라우팅하지 않으므로, 플랫폼이 DLQ publish를 직접 수행한다.
| Capability | Kafka |
|---|---|
| brokerAcknowledgement | O |
| replicationOrPersistenceEvidence | O |
| perMessageSettlement | O |
| batchSettlement | O |
| orderedStream | O |
| keyedOrdering | O |
| replay | O |
| delayedDelivery | X |
| brokerTransaction | O |
| deduplicatedPublish | O |
| nativeDeadLetter | X |
| topologyManagement | O |
## 기능 등급
@@ -73,8 +67,6 @@ NATS JetStream의 `nativeDeadLetter=X`도 마찬가지다. JetStream은 delivery
| Batch / Manual settlement / Pause·Resume / Delayed / Replay 요청 | M2 |
| Broker transaction / partition / routing / subscription | M3 |
| Replay 실행 / Redrive / offset reset / purge / delete | M4 Admin |
| Kafka Share Group, Pulsar, NATS | Experimental |
| Spring Cloud Stream bridge | Optional |
## 무엇이 "Stable"을 증명하는가
@@ -82,7 +74,7 @@ Stable 등급은 두 가지를 **모두** 통과해야 한다. `CompatibilityMat
### 1. 공유 Contract Suite (`MessagingAdapterContract`, 7개)
Kafka와 RabbitMQ가 동일한 7개 테스트를 변경 없이 통과한다. 결정적 하네스를 쓰므로
Kafka가 7개 테스트를 변경 없이 통과한다. 결정적 하네스를 쓰므로
확인 유실·settlement 유실 같은 장애를 요청 시점에 재현할 수 있다.
### 2. 실 브로커 인증 (Testcontainers)
@@ -92,7 +84,6 @@ Kafka와 RabbitMQ가 동일한 7개 테스트를 변경 없이 통과한다. 결
| `KafkaBrokerIT` | `acks=all`이 실제 replication 증거를 만든다 / 잘못된 토픽은 `REJECTED` / 발행-소비 왕복에서 identity 보존 및 contiguous commit |
| `KafkaAmbiguityChaosIT` | 브로커를 `docker pause`로 멈춘 상태의 publish가 **`AMBIGUOUS`** 로 보고된다 (broker acceptance 없음, confirmation level `NONE`, 비-retryable) |
| `KafkaBrokerCertificationIT` | 인증 레인. Toxiproxy를 broker 앞에 두고 connection cut / confirm 유실 / 지연 / settlement 유실을 각각 주입하고, 통과한 시나리오마다 `BrokerCertificationEvidence` 한 줄을 manifest에 쓴다 |
| `RabbitBrokerIT` | exchange가 confirm했는데 어떤 큐에도 바인딩되지 않은 publish가 **`REJECTED` + `UNROUTABLE`** 로 보고된다 |
| `OutboxPostgresIT` | 롤백된 트랜잭션은 발행 가능한 행을 남기지 않는다 / `SKIP LOCKED` lease가 두 relay를 분리한다 / ambiguous 행이 같은 `messageId`로 재클레임된다 |
| `InboxPostgresIT` | 재전달이 side effect를 두 번 적용하지 않는다 / 롤백은 예약도 되돌린다 |
@@ -137,7 +128,7 @@ delivery timeout으로 나타난다. 이를 `REJECTED`로 보고하는 것은
1. **Outbox `IN_FLIGHT` 고아 행** — lease 쿼리가 `PENDING`/`AMBIGUOUS`만 클레임 대상으로 봐서,
publish 도중 죽은 relay가 남긴 행이 lease 만료 후에도 영영 회수되지 않았다.
2. **Rabbit confirm 경합** — transport가 publish *후에* confirm을 등록해서, 연결 스레드에서
2. **Rabbit confirm 경합**(2026-09-25에 삭제된 Rabbit transport) — transport가 publish *후에* confirm을 등록해서, 연결 스레드에서
confirm이 먼저 도착하면 유실되고 호출자가 무한 대기했다.
둘 다 인메모리 double이 실제보다 관대해서 통과하고 있었다.
@@ -154,21 +145,10 @@ delivery timeout으로 나타난다. 이를 `REJECTED`로 보고하는 것은
- DLQ publish 확인 전 source ACK
## R1 compiler status
`adapter:outbound:messaging`의 contract/catalog/envelope compiler 군은 현재 **의도적으로 미배선**이다.
`DISABLED` + 빈 catalog/binding이 zero-resource 상태이며, 이 R1 compiler를 legacy
`MessagingConfig`에 연결해 Kafka ACK, wire compatibility, `ACTIVE_READY`, R2 qualification을
주장하지 않는다. 코드는 다음 세대 계약을 보존하지만 현재 채택 경로가 아니며, 실제 활성화는 별도 R2
composition/cutover에서 명시적으로 이뤄져야 한다.
### Optional mapping / bridge utilities
### Optional mapping utilities
- `messaging-cloudevents`는 starter runtime에 자동 편입되지 않는 **opt-in mapping utility**다.
내부 envelope와 CloudEvent 객체 사이의 제한된 profile mapping을 제공하지만 binary/structured
CloudEvents wire mode 전체를 구현하거나 임의 CloudEvents producer와의 1.0 interoperability를
인증하지 않는다.
- `messaging-spring-cloud-stream-bridge`는 현재 `ChannelSend` seam과 publish-evidence 판단을 제공하는
framework-neutral bridge contract다. Spring Cloud Stream `StreamBridge` dependency/auto-configuration은
제공하지 않으므로 shipped Spring Cloud Stream integration으로 분류하지 않는다.
- `messaging-claim-check`도 starter에 편입되지 않는 opt-in utility다.
@@ -12,7 +12,6 @@ ca-skeleton:
topology: REPLICA_SET
production: true
stable-api-strict: true
consistency-default: PRIMARY_MAJORITY
server-selection-timeout: 3s
connect-timeout: 2s
socket-read-timeout: 5s
@@ -21,7 +20,5 @@ ca-skeleton:
pool-max-size: 40
pool-max-wait-time: 500ms
uuid-representation: STANDARD
decimal-representation: DECIMAL128
runtime-auto-create-indexes: false
tls-required: true
authentication-required: true
+14 -6
View File
@@ -1,8 +1,9 @@
# Advanced — CSFLE and Queryable Encryption
**Capabilities:** `MongoCapability.CSFLE`, `MongoCapability.QUERYABLE_ENCRYPTION`
**Properties:** `ca-skeleton.persistence-mongo.advanced.csfle.enabled`,
`ca-skeleton.persistence-mongo.advanced.queryable-encryption.enabled`
**Enablement:** library API, no configuration property. The service's own adapter constructs the
entry point with a `MongoAdvancedCapabilityGuard` built from `MongoAdvancedCapabilityFlags` that
enables the capability; construction is refused otherwise.
**Status:** Advanced.
## Requirements
@@ -16,9 +17,16 @@
## 1. CSFLE
`MongoCsfleProfile` binds a collection to its `MongoCsfleFieldPolicy` list, a key vault
`MongoCredentialReference` and the key vault namespace. `MongoCsfleClientFactory` builds the encrypted
client; `MongoDataKeyResolver` resolves data keys.
`MongoCsfleProfile` binds a collection (`database` + `collection`) to its `MongoCsfleFieldPolicy`
list, a key vault `MongoCredentialReference` and the key vault namespace. `MongoCsfleClientFactory`
builds the encrypted client settings from it: the `$jsonSchema` is generated from the field policies
(a dotted path becomes nested `properties`) and keyed by the namespace `database.collection`, and the
key vault client is built from the profile's own credential through `MongoCredentialResolver`.
An automatic-encryption schema names a data key by id, not by alias. The adopter resolves each
`MongoCsfleFieldPolicy.keyAlias()` against the key vault (for example
`ClientEncryption.getKeyByAltName`) and passes the alias → key id map to `settingsFor`; an alias with
no id is refused. Deterministic fields are typed `string` in the schema.
`MongoCsfleMode`:
@@ -87,5 +95,5 @@ an outage.
Per [ADR-MONGO-ADV-001](../../adr/ADR-MONGO-ADV-001-capability-promotion.md), promotion requires the
real KMS and key vault, plus negative cases that fail closed: wrong key, missing permission, rotation
mid-operation (`MongoAtlasCapabilityContractSuite.kmsFailureModes`). A local key provider certifies
mid-operation. A local key provider certifies
none of these — it never rejects anything.
-63
View File
@@ -1,63 +0,0 @@
# Advanced — GridFS compatibility and migration
**Capability:** `MongoCapability.GRIDFS_COMPATIBILITY`
**Property:** `ca-skeleton.persistence-mongo.advanced.gridfs-compatibility.enabled`
**Status:** Advanced, compatibility only. Decision D-14.
## Position
GridFS is a **compatibility adapter for files that already exist there**. New files use the existing
Fileserver / Object Storage adapter, which is the source of truth for binary content.
The reason is not preference. GridFS stores file chunks in the same collections, on the same replica
set, competing for the same working set as your documents. A large file read evicts document pages
from cache, and file storage growth becomes replica-set growth — which means it becomes oplog
pressure, backup duration and failover time. Object storage was built for this and MongoDB was not.
## Reading legacy files
`MongoGridFsCompatibilityReader` reads existing GridFS content as
`GridFsLegacyContent(legacyId, filename, sizeBytes, checksum, stream)`. It reads; it does not write.
## Migration
`MongoGridFsMigrationJob` moves a file to object storage in a fixed order:
```
read legacy content
→ write to object storage
→ verify the target checksum matches the source
→ switch the reference
→ (later, separately) delete the source
```
Three properties, each of which exists because of a specific way this goes wrong:
1. **Verify before switching.** `MongoGridFsObjectReference` requires a non-blank checksum, and the
job returns empty and writes no reference when the target checksum does not match the source. A
migration that switches the reference on a successful *write* rather than a verified *copy*
silently points at a truncated object.
2. **The source is never deleted here.** Deletion is a separate, later decision after the new
location has been serving reads long enough to be trusted. A migration that deletes as it goes has
no rollback.
3. **The checkpoint separates migrated from failed.** `MongoGridFsMigrationCheckpoint` tracks
`migratedCount()`, `failedCount()`, `clean()` and `lastMigratedLegacyId()`, so a restart continues
from the last completed file rather than starting over, and a partially failed run is visible as
partial rather than as "done".
## Failure recovery
| Symptom | Cause | Action |
|---|---|---|
| `migrate` returns empty | Checksum mismatch | The copy is bad. Investigate before retrying; do not force the reference. |
| `IllegalArgumentException` on the reference | Missing checksum | A reference without a checksum cannot be verified and is refused. |
| Checkpoint not `clean()` | Some files failed | Re-run for the failed ids only; the checkpoint names the last successful one. |
| Reference switched but content missing | Source deleted too early | Restore from backup. This is what rule 2 prevents. |
## Promotion evidence
Actual-topology evidence against the real object storage backend, a security review of the storage
credential, the migration path above, failure cases (checksum mismatch refused, missing checksum
refused, restart resumes), and this document as the runbook.
New file storage does not go through here at all — see the fileserver adapter.
+10 -7
View File
@@ -2,16 +2,19 @@
**Capabilities:** `MongoCapability.SHARED_COLLECTION_TENANCY` (Advanced),
`MongoCapability.DATABASE_PER_TENANT` (Experimental)
**Properties:** `ca-skeleton.persistence-mongo.advanced.shared-collection-tenancy.enabled`,
`ca-skeleton.persistence-mongo.advanced.database-per-tenant.enabled`
**Enablement:** library API, no configuration property. The service's own adapter constructs the
entry point with a `MongoAdvancedCapabilityGuard` built from `MongoAdvancedCapabilityFlags` that
enables the capability; construction is refused otherwise.
Shared-collection tenancy has no entry point (its types are policies), so only
`DATABASE_PER_TENANT` is ever checked.
## 1. Shared collection
Every tenant's documents live in one collection, discriminated by a tenant field.
`MongoTenantContext` carries the tenant. `MongoTenantPredicateInjector` adds the tenant predicate to
every query, every atomic filter and the **first** aggregation stage. `TenantScopedMongoOperations`
is the entry point, so a caller cannot construct an unscoped operation by forgetting.
every query, every atomic filter and the **first** aggregation stage. The adopter's repository calls
the injector on every tenant-scoped path; there is no tenant-scoped operations facade in this leaf.
Three details are load-bearing:
@@ -38,8 +41,8 @@ grows with the customer list, and the tag ships tenant identity into the metrics
## 2. Database per tenant (Experimental)
`MongoTenantDatabaseResolver` maps a tenant to its database; `MongoTenantClientRegistry` holds the
clients.
`MongoTenantClientRegistry` holds one client per tenant under a cap with idle eviction; mapping a
tenant to its database is the adopter's code.
Experimental for a specific reason: it is correct in the small and unbounded in the large. Each tenant
database costs connections, file handles and monitoring cardinality. It works beautifully at 20
@@ -76,7 +79,7 @@ contractual isolation or per-tenant-restore requirement.
| Symptom | Cause | Action |
|---|---|---|
| Cross-tenant data visible | An operation bypassed `TenantScopedMongoOperations` | Treat as a security incident. Find the path, close it, audit access. |
| Cross-tenant data visible | An operation skipped `MongoTenantPredicateInjector` | Treat as a security incident. Find the path, close it, audit access. |
| Unique constraint fires across tenants | Unique index missing the tenant field | Rebuild the index with the tenant field as prefix; the validator catches this before it ships. |
| One shard holds most data | Tenant id as shard-key prefix with a dominant tenant | Refine the shard key with a high-cardinality suffix. |
| Connection exhaustion | Database-per-tenant beyond the connection budget | The scale limit. Consolidate or move to shared collections. |
-81
View File
@@ -1,81 +0,0 @@
# Advanced — Search and Vector Search
**Capabilities:** `MongoCapability.SEARCH`, `MongoCapability.VECTOR_SEARCH`
**Properties:** `ca-skeleton.persistence-mongo.advanced.search.enabled`,
`ca-skeleton.persistence-mongo.advanced.vector-search.enabled`
**Status:** Experimental (design §3.3). Hybrid search likewise.
## Requirements
| | |
|---|---|
| Topology | A deployment with the search service. Atlas Local in a container is a pull-request convenience and is **not** release evidence. |
| Privilege | `MongoPrincipalRole.SEARCH_ADMIN` for index management; the application role queries only. |
| Gate | `MongoAtlasCapabilityContractSuite` on the actual target deployment. |
## 1. Created is not ready
`MongoSearchIndexState`: `CREATED` → `BUILDING` → `READY`, plus `FAILED` and `DELETING`.
`MongoSearchReadinessGate.requireReady(state)` refuses anything but `READY`. A search index is built
asynchronously: the create call returns immediately and the index answers queries with *partial*
results while building. Not an error, not empty — partial. A deployment that creates an index and
starts querying serves incomplete results for as long as the build takes, and nothing reports it.
## 2. Search indexes are not application-owned
`MongoSearchIndexDescriptor.metadataOwnership()` is `MongoMetadataOwnership.SEARCH_MANAGED`, and
`droppableByApplicationDrift()` is false. The index reconciliation described in
[ADR-MONGO-004](../../adr/ADR-MONGO-004-index-schema-admin-plane.md) must not drop it.
## 3. Query guardrails
`MongoSearchQuery` binds an index, an allowlist of paths, the search text and a result limit.
- `requireAllowedPaths(allowed)` raises `MongoOperationRejectedException` on a path outside the
allowlist. Without it, a caller can search any indexed field, including ones indexed for a
different purpose.
- Search text length and result count are bounded at construction. An unbounded search text is a
cost multiplier on someone else's service.
## 4. Vector search
`MongoVectorIndexDescriptor.cosine(path, dimensions)` declares the index.
`MongoEmbedding.forIndex(index, values)` binds an embedding to it and **rejects a dimension
mismatch** — a 1536-dimension embedding against a 768-dimension index is not a runtime degradation,
it is a category error, and catching it at construction beats catching it as a confusing server
message.
`MongoEmbedding` copies its backing array in and out. A vector that shares an array with its caller
can be mutated after the query is built, which produces a query nobody wrote.
`MongoVectorQuery` requires `numCandidates > limit` — searching 10 candidates to return 10 results is
an exhaustive scan wearing an ANN index's name. `MongoVectorQuery.nearest(embedding, 10)` uses the
standard 20× ratio (200 candidates for 10 results).
## 5. Relevance is the gate, not functionality
`MongoVectorSearchBenchmarkGate.standard()` requires **recall** alongside latency and index size.
`requiredEvidence()` names recall explicitly.
This is the difference between search and everything else in the platform. A vector index can be
functionally perfect — it accepts the index, accepts the query, returns k results, within the latency
budget — and return the wrong k. A gate that measures only latency certifies a fast wrong answer.
`failures(recall, latencyMs, indexMb)` reports which dimension failed so the finding is actionable.
## 6. Failure recovery
| Symptom | Cause | Action |
|---|---|---|
| Incomplete results after a deploy | Queried a `BUILDING` index | Wait for `READY`. The gate prevents this; if it fired, something bypassed it. |
| `MongoOperationRejectedException` on a path | Path not in the allowlist | Add it deliberately, or fix the caller. |
| Dimension mismatch | Model changed | A new model means a new index. Build alongside, cut over, then retire. |
| Recall dropped without a code change | The index was rebuilt with different parameters, or the data distribution shifted | Re-run the benchmark gate; treat a recall regression like a failing test. |
| Index `FAILED` | Build error on the search service | Search-side diagnosis; the application must not fall back to a scan silently. |
## 7. Promotion evidence
Per [ADR-MONGO-ADV-001](../../adr/ADR-MONGO-ADV-001-capability-promotion.md): the actual target
deployment (not Atlas Local), security review of `SEARCH_ADMIN`, a rebuild path, failure cases
(non-ready index refused, disallowed path refused, dimension mismatch refused), this document as the
runbook, **and** relevance evidence. Search and vector search do not promote on functional success.
+3 -1
View File
@@ -1,7 +1,9 @@
# Advanced — Sharding
**Capability:** `MongoCapability.SHARDING`
**Property:** `ca-skeleton.persistence-mongo.advanced.sharding.enabled`
**Enablement:** library API, no configuration property. The service's own adapter constructs the
entry point with a `MongoAdvancedCapabilityGuard` built from `MongoAdvancedCapabilityFlags` that
enables the capability; construction is refused otherwise.
**Status:** Advanced. Reshard orchestration remains Experimental.
## Requirements
-73
View File
@@ -1,73 +0,0 @@
# Advanced — Time Series
**Capability:** `MongoCapability.TIME_SERIES`
**Property:** `ca-skeleton.persistence-mongo.advanced.time-series.enabled`
**Status:** Advanced.
## Requirements
| | |
|---|---|
| Topology | Replica set or sharded cluster. |
| Server | MongoDB 7.0 or 8.0. |
| Privilege | Standard application role; collection creation goes through the admin plane. |
## Descriptor
`MongoTimeSeriesDescriptor` declares:
- **timeField** — required, a BSON date. This is the bucketing axis.
- **metaField** — optional but nearly always wanted: the series identity (device id, tenant, sensor).
Documents sharing a `metaField` value bucket together, which is where the compression comes from.
- **granularity** — `MongoTimeSeriesGranularity`:
| Granularity | Bucket span | Use for |
|---|---|---|
| `SECONDS` | 1 hour | Sub-second to per-second ingest. |
| `MINUTES` | 24 hours | Per-minute metrics. |
| `HOURS` | 30 days | Hourly rollups. |
Granularity that is too fine produces many small buckets and loses the compression; too coarse
produces oversized buckets that must be read whole to answer a narrow query.
## What a time series collection is not
`MongoTimeSeriesCapabilityValidator` refuses the operations the collection type does not support, at
declaration time rather than at first use:
- **No arbitrary updates.** Time series data is append-mostly. Delete and limited update support
exists on recent servers but is not part of this platform's contract.
- **No unique index on the measurement.** There is no `_id` to be unique on in the usual sense.
- **No CSFLE.** Refused — see [encryption.md](encryption.md).
- **No change stream on the raw buckets** as a business event source. The bucket documents are a
storage representation, not your measurements.
Converting an existing regular collection to a time series collection is a copy, not an alter. Plan
it as a migration with a dual-write window.
## TTL
Time series collections use `expireAfterSeconds` on the collection rather than a TTL index on a
field. The [TTL rules](../schema-index-migration-guide.md#4-ttl) still apply: expiry is physical
cleanup on a bucket boundary, so a measurement can outlive its expiry by up to a bucket span plus the
monitor interval. Do not treat absence as a deadline.
## Operations
`MongoTimeSeriesOperations` is the port for insert and windowed read. Reads are bounded by the same
`MongoOperationBudget` as everything else: an unbounded time-range query on a time series collection
is the fastest way to read a year of data into heap.
## Failure recovery
| Symptom | Cause | Action |
|---|---|---|
| Writes rejected with an unsupported-operation error | An update or unique-index expectation | The collection type does not support it; change the access pattern. |
| Poor compression / large storage | Missing `metaField`, or granularity too fine | Both require a rebuild; measure on a copy before committing. |
| Slow range queries | Granularity too coarse for the query window | Same: rebuild with the granularity matched to the dominant query. |
## Promotion evidence
Actual-topology evidence on the target deployment, a migration path from the existing collection,
failure cases (unsupported update refused, CSFLE combination refused), and this document as the
runbook.
-105
View File
@@ -1,105 +0,0 @@
# Change Stream Guide
Design §20, decision D-12. A change stream is an **at-least-once projector**, not an event bus.
## 1. What a change stream is not
D-12 is explicit: a physical change event is not a business integration event. The two differ in
ways that matter to every consumer:
| Change event | Integration event |
|---|---|
| Emitted per document write | Emitted per business fact |
| Shape follows the storage schema | Shape is a published contract |
| A refactor of the document changes it | A refactor of the document does not change it |
| Replayed on resume, duplicated on retry | Versioned and deliberately evolved |
Publishing raw change events externally makes your storage schema a public API, and the first time
someone renames a field the downstream consumers break. If you need to bridge to messaging, use the
Advanced bridge, which maps to an owned envelope
([advanced/multi-tenancy.md](advanced/multi-tenancy.md) is separate;
the bridge is described in §7 below).
## 2. Subscription and resume
`MongoChangeStreamSubscription` declares the collection, pipeline and consistency. `MongoResumePosition`
is either a resume token or a cluster time; `MongoResumeCheckpoint` is what gets persisted and
`MongoResumeCheckpointStore` persists it.
The checkpoint stores the token as a Base64 `encodedToken` string rather than a byte array — a record
with an array component has broken equality, and a checkpoint that does not compare correctly is a
checkpoint that silently fails its own dedup test.
## 3. Checkpoint after processing, not after receiving
The ordering rule that makes at-least-once actually hold:
```
receive event
→ process it (idempotently)
→ persist the checkpoint
```
Checkpointing on receipt turns the delivery guarantee into at-most-once, and the events lost are
exactly the ones the process died while handling.
## 4. Idempotency
`MongoChangeEventIdentity` is the dedup key: `(resumeToken, documentKey, clusterTime, operationType)`.
`MongoChangeDeduplicationStore` records what has been applied. Duplicates are not an edge case — every
resume after any interruption replays at least one event, so a projector that is not idempotent is
wrong on its first restart, not on some rare day.
`MongoChangeProjector` returns a `MongoChangeProjectionResult` so the runner can distinguish applied
from skipped-as-duplicate, and the skip count is worth a metric: a sudden rise means something is
looping.
## 5. States and recovery
`MongoChangeStreamState`: `STARTING`, `RUNNING`, `RESUMING`, `STOPPED`, `HISTORY_LOST`.
`MongoChangeStreamRecoveryPolicy` returns a `MongoChangeStreamRecoveryDecision`, which is either
`resume()` (auto-resume from the checkpoint) or `halt(state, runbook)`. A halting decision **must**
name a runbook — a decision that only says "stopped" leaves the on-call engineer to work out from
scratch whether the projection can be rebuilt and from what.
| Situation | Decision |
|---|---|
| Transient network error, token still valid | `resume()` |
| Primary failover | `resume()` — the token survives an election |
| `invalidate` (collection dropped/renamed) | `halt(STOPPED, …)` → `MongoInvalidateRecovery` |
| Token no longer in the oplog | `halt(HISTORY_LOST, "history-lost")` → `MongoChangeHistoryLostException` |
## 6. History lost
`MongoChangeHistoryLostException` is raised when the resume token predates the oldest oplog entry.
The stream **cannot** be resumed: the events between the checkpoint and now are gone from the server,
and no amount of retrying brings them back.
What the platform will not do is silently restart from "now". That looks like a recovery and is
actually a silent gap in the projection — the worst possible outcome, because nothing reports it. The
runner halts and requires an operator decision. See
[runbooks/history-lost.md](runbooks/history-lost.md).
## 7. Bridging to messaging (Advanced)
`MongoChangeMessagingBridge` is opt-in behind `MongoCapability.CHANGE_STREAM` plus the bridge's own
flag. It maps a change event to a platform-owned `MongoIntegrationEventEnvelope` through
`MongoChangeToIntegrationEventMapper` and hands it to a `MongoIntegrationEventPublisher` port.
The port is defined in the bridge package rather than imported from the messaging adapter because the
architecture registry forbids adapter-to-adapter dependencies; the composition root supplies the
implementation.
`MongoBridgeOutboxPolicy` and `MongoBridgeCheckpointPolicy` state the delivery contract: publish then
checkpoint, at-least-once, consumers must dedup on the envelope's event id.
## 8. Operating notes
- Change streams require a replica set. `MongoStartupValidator` refuses a change-stream profile on
`STANDALONE`.
- The change-stream principal is its own role (`MongoPrincipalRole.CHANGE_STREAM`) with
`changeStream` and `find` — not the application write credential.
- Oplog window is the recovery budget. If the oplog holds four hours, a consumer that is down for five
hours needs a rebuild, not a resume. Alert on consumer lag against the oplog window, not against
wall-clock.
+10 -9
View File
@@ -31,8 +31,7 @@ Collapsing these two into one is how a concurrent overwrite becomes a 404.
## 3. Consistency profiles
`MongoConsistencyProfile` names the read/write concern pair; `MongoConsistencyRegistry` binds a
profile to an operation or collection, and `MongoConsistencyBinder` /
`ReactiveMongoConsistencyBinder` apply it at execution.
profile to an operation or collection, and `MongoConsistencyBinder` applies it at execution.
| Profile | Meaning | Use for |
|---|---|---|
@@ -47,17 +46,14 @@ without a registered profile is rejected rather than defaulting.
## 4. Causal sessions
`MongoCausalSessionContext` plus `SpringMongoCausalSessionExecutor` /
`ReactiveMongoCausalSessionExecutor` carry the cluster time and operation time between operations, so
`MongoCausalSessionContext` plus `SpringMongoCausalSessionExecutor` carry the cluster time and
operation time between operations, so
"write then read" returns the write even when the read lands on a different node. Without a causal
session, `PRIMARY_MAJORITY` gives you durability but not read-your-writes across two calls.
In the reactive path the session travels in the Reactor context (`ReactiveMongoContextKeys`), not in
a thread local — a thread local is empty on the next operator in the chain.
## 5. Transactions
`MongoTransactionExecutor` / `ReactiveMongoTransactionExecutor` open a session through the session
`MongoTransactionExecutor` opens a session through the session
factory, run the body, and commit. `MongoTransactionProfile` carries the consistency profile, the
`maxCommitTime` and the retry budget. Topology matters: a transaction requires a replica set, and
`MongoStartupValidator` refuses a transaction-declaring profile on `STANDALONE` at startup rather
@@ -122,5 +118,10 @@ driver type.
`MongoBulkExecutor` returns a `MongoBulkResult` with per-item `MongoBulkItemFailure` entries. An
unordered bulk write that partially fails is `PARTIAL_BULK_WRITE`, not a failure: some documents were
written. `MongoBulkPartialFailureException` carries the succeeded and failed indexes so a caller can
written. The result's per-item outcomes say which indexes succeeded and which failed, so a caller can
resume rather than replay.
`execute(context, documentType, plan)` maps every filter and update through the document type, as
the single-document path does, so `@Field` names and registered converters (`DomainDocumentId`,
`BigInteger`) mean the same thing in a batch. The command's byte ceiling is measured on those mapped
documents before anything is sent.
+3 -3
View File
@@ -39,8 +39,8 @@ is the first symptom, and by then the collection is already full of near-limit d
## 4. Identity
`DomainDocumentId` and `MongoIdRepresentation` fix how a domain identifier becomes `_id`. Pick the
representation once per collection and record it in the manifest:
`DomainDocumentId` is written to `_id` as a BSON string by `DomainIdWriteConverter`. Any other
representation is the document class's own field type. Pick the representation once per collection:
- `OBJECT_ID` — server-generated, monotonic, 12 bytes. Good default when the domain has no natural id.
- `UUID_BINARY` — a domain UUID stored as `Binary` subtype 4 (`STANDARD`). Never store a UUID as a
@@ -70,7 +70,7 @@ becomes a data migration; storing an alias keeps it a refactor. See
`MongoCollectionProfileRegistry` binds a `CollectionProfileName` to its consistency profile, budget
and allowlist. A collection that is not registered cannot be reached through
`MongoImperativeExecutor` or `ReactiveMongoExecutor` — the allowlist is the mechanism that keeps an
`MongoImperativeExecutor` — the allowlist is the mechanism that keeps an
unreviewed collection from appearing in production by accident.
## 8. What to write down before the first insert
+2 -16
View File
@@ -92,21 +92,7 @@ registered plan.
`allowDiskUse` is a declared property of the plan, not a runtime flag. A pipeline that needs disk is a
pipeline whose shape should be reviewed.
## 6. Reactive execution and cursors
`ReactiveMongoExecutor` / `DefaultReactiveMongoExecutor` carry the operation context in the Reactor
context. `MongoCursorGuard` and `MongoCursorLease` bound cursor lifetime:
- a cursor has a lease with a deadline
- cancellation closes the server-side cursor (`MongoCursorTermination`)
- an abandoned cursor is a server-side resource, so the lease is released on cancel, error *and*
completion — `MongoReactiveCursorPublisher` uses `Flux.using` so all three paths run the same
release
A leaked cursor does not fail anything locally; it consumes a connection and a snapshot on the server
until the server's own timeout, which is why the guard is not optional.
## 7. Geospatial
## 6. Geospatial
`MongoGeoQuery` + `MongoGeoPoint` + `MongoGeoDistance` over a `2dsphere` index. Distances are metres
on a sphere (`nearSphere` with `maxDistance`), never degrees — a degree of longitude is a different
@@ -114,7 +100,7 @@ distance in Oslo than in Nairobi, and a radius expressed in degrees is a bug tha
from the equator. `SpringMongoGeospatialOperations` is the Spring Data binding;
`MongoGeospatialOperations` is the port.
## 8. Native capability gateway
## 7. Native capability gateway
When a registered operation genuinely needs something outside the Stable API, it goes through
`MongoNativeCapabilityGateway` (`PolicyAwareMongoNativeGateway`), never through the driver directly.
+13 -18
View File
@@ -27,9 +27,8 @@ the tree for exact equality, and every observed edge must appear in it. A forbid
build the same way a missing Gradle dependency would, and so does a new package nobody registered.
This used to be a stronger claim than the test. The rules forbade a handful of reverse dependencies
and said nothing about the rest, so four edges outside the design's DAG existed and passed:
`reactive → imperative`, `reactive → query`, `transaction → reactive` and `geo → imperative`. They
are declared in the matrix now rather than removed — each is a real coupling the code relies on, and
and said nothing about the rest, so edges outside the design's DAG existed and passed, among them
`geo → imperative`. They are declared in the matrix now rather than removed — each is a real coupling the code relies on, and
the point of recording them is that the next one is a decision instead of an accident.
## 2. Package mapping
@@ -43,12 +42,10 @@ Root package: `io.backend.skeleton.mongodb` → `dev.caskeleton.adapter.outbound
| `mongodb-core-api` | `…outbound.mongo.api` (+ `.capability`, `.consistency`, `.error`, `.mapping`, `.observation`, `.profile`, `.schema`) |
| `mongodb-spring-data` | `…outbound.mongo.mapping` (+ `.type`), `…outbound.mongo.failure` |
| `mongodb-imperative` | `…outbound.mongo.imperative` (+ `.atomic`, `.bulk`, `.revision`) |
| `mongodb-reactive` | `…outbound.mongo.reactive` (+ `.cursor`) |
| `mongodb-query` | `…outbound.mongo.query` (+ `.budget`, `.pagination`) |
| `mongodb-aggregation` | `…outbound.mongo.aggregation` |
| `mongodb-transaction` | `…outbound.mongo.transaction` (+ `.retry`, `.session`) |
| `mongodb-index-schema` | `…outbound.mongo.schema` (+ `.index`, `.manifest`, `.model`, `.ttl`, `.validation`) |
| `mongodb-change-stream` | `…outbound.mongo.changestream` (+ `.projector`, `.recovery`) |
| `mongodb-geospatial` | `…outbound.mongo.geo` |
| `mongodb-migration-core` | `…outbound.mongo.migration` |
| `mongodb-migration-flamingock` | `…outbound.mongo.migration.flamingock` |
@@ -68,22 +65,22 @@ the reusable ArchUnit rule set a fork applies to its own document/repository cod
| Design module | Repository package |
|---|---|
| `mongodb-sharding` | `…outbound.mongo.advanced.sharding` (+ `.admin` for the D4 shard plane) |
| `mongodb-timeseries` | `…outbound.mongo.advanced.timeseries` |
| `mongodb-csfle` | `…outbound.mongo.advanced.encryption.csfle` |
| `mongodb-queryable-encryption` | `…outbound.mongo.advanced.encryption.qe` |
| `mongodb-search` | `…outbound.mongo.advanced.search` |
| `mongodb-vector-search` | `…outbound.mongo.advanced.vector` |
| `mongodb-tenancy-shared` | `…outbound.mongo.advanced.tenancy.shared` |
| `mongodb-tenancy-database` | `…outbound.mongo.advanced.tenancy.database` |
| `mongodb-change-stream-messaging-bridge` | `…outbound.mongo.advanced.bridge` |
| `mongodb-gridfs-compat` | `…outbound.mongo.advanced.gridfs` |
| `mongodb-testkit-sharded` | `…outbound.mongo.testkit.sharded` (`testkit` source set) |
| `mongodb-testkit-atlas` | `…outbound.mongo.testkit.atlas` (`testkit` source set) |
`mongodb-timeseries`, `mongodb-search`, `mongodb-vector-search`, `mongodb-gridfs-compat` and
`mongodb-testkit-atlas` have no package any more: each was an operations interface with no
implementation plus the descriptors that parametrised it, and was removed on 2026-09-25
(`docs/capability-status.md`).
The design's rule that a Stable module never depends on an Advanced one survives as an ArchUnit rule
(`stableNeverDependsOnAdvanced`) plus the opt-in flag: every Advanced entry point requires
`MongoAdvancedCapabilityFlags` to have the matching capability enabled and refuses construction
otherwise. Being on the classpath is not being enabled.
(`stableNeverDependsOnAdvanced`). Every Advanced entry point takes a `MongoAdvancedCapabilityGuard`
and refuses construction unless its `MongoAdvancedCapabilityFlags` enable the matching capability.
There is no configuration property behind the flags: the Advanced types are library API, and the
adopter's adapter that constructs them builds the guard.
## 3. Other deliberate substitutions
@@ -114,13 +111,11 @@ otherwise. Being on the classpath is not being enabled.
- Registered operation names and manifests for query, aggregation and index; no free-form JSON query
and no unbounded pipeline.
- Keyset pagination with an authenticated cursor and a unique tie-breaker requirement.
- Change stream as an at-least-once projector with resume-token checkpointing and explicit
history-lost handling.
- TTL as physical cleanup only, never the sole basis for access denial or business scheduling.
- Manifest-owned index/validator state with an apply policy that never drops what it does not own.
- Low-cardinality observation tags, command redaction, and the credential reference indirection.
- The Stable release gate's evidence categories, and the Advanced promotion gate's requirement for
actual-topology evidence.
- The Stable release gate's evidence categories. The Advanced promotion requirements
(actual-topology evidence) are a review obligation in ADR-MONGO-ADV-001; no class checks them.
## 5. Verification
-90
View File
@@ -1,90 +0,0 @@
---
title: Runbook — MongoDB change stream history lost
category: mongodb
severity: P1
owner: oncall
last_updated: 2026-08-13
status: active
---
# Runbook: change stream history lost
Design §20.3, scenarios `OPLOG_HISTORY_LOSS`, `RESUME_TOKEN_LOSS`.
The stored resume token predates the oldest entry in the oplog. The events between the checkpoint and
now are gone from the server; no retry recovers them. `MongoChangeStreamRecoveryPolicy` returns
`halt(HISTORY_LOST, "history-lost")` and the runner stops.
**The platform will not silently restart from "now".** That looks like a recovery and is actually a
permanent, unreported gap in the projection.
## Symptoms
- `MongoChangeHistoryLostException`.
- `MongoChangeStreamState.HISTORY_LOST`; the consumer is stopped, not looping.
- Precedes it: consumer lag approaching the oplog window, or a consumer that was down for a long
period (a deploy that failed, a scaled-to-zero worker, a long outage).
## Diagnosis
1. **Determine the gap.** The checkpoint's cluster time is the start; the oldest oplog entry is the
end of what is unrecoverable. Everything in between was never processed.
2. **Determine the oplog window.** `rs.printReplicationInfo()` on the primary gives the first and last
oplog timestamps. If the window is materially smaller than it was, the write rate rose or the
oplog was resized — the consumer may be fine and the server changed.
3. **Determine what the projection is missing.** Which collections and which operations does this
projector consume? The gap is bounded by that, not by everything that happened.
4. **Check for a second consumer.** If another projector on the same collection is healthy, its
checkpoint tells you whether the problem is this consumer or the oplog.
## Action
Resuming is not an option. The choices are:
**Rebuild from source.** If the projection is derivable from the current state of the source
collections, rebuild it: stop the consumer, rebuild the projection, then start the stream from the
cluster time at which the rebuild snapshot was taken. This is the correct answer whenever the
projection is a materialised view rather than an event log, and it is the reason a projection should
be derivable.
**Backfill the gap.** If the source documents carry a timestamp covering the gap, run a bounded
backfill for that window through the migration runner (checkpointed, resumable — see
[schema-index-migration-guide.md](../schema-index-migration-guide.md) §5), then resume from the
current cluster time.
**Accept the gap explicitly.** Only when the projection is advisory and the business owner says so.
Record the window in the incident log and reset the checkpoint. This is a decision someone signs, not
a default.
Never: reset the checkpoint to "now" and restart quietly. That converts a visible P1 into an
invisible data-quality defect that surfaces months later as "the report has been wrong since March".
## Prevention
- **Alert on lag against the oplog window, not wall-clock.** "Consumer is 30 minutes behind" is fine
with a 24-hour oplog and an emergency with a 45-minute one. The threshold that matters is
`lag / oplogWindow`.
- **Size the oplog for the longest tolerable consumer outage**, including a failed deploy discovered
the next morning.
- **Checkpoint after processing, never on receipt** — see
[change-stream-guide.md](../change-stream-guide.md) §3.
- **Back up the checkpoint store.** `RESUME_TOKEN_LOSS` is the same incident reached from the other
direction: the oplog is fine, the checkpoint is gone.
- **Make the projection rebuildable.** A projection that can only be built by replaying every event
has no recovery path once the oplog rolls.
## Escalation
- P1 on detection. The consumer is stopped, so lag grows for as long as this is unresolved.
- Page the service owner for the rebuild decision, and the database owner if the oplog window shrank
unexpectedly.
## Verification
```bash
cd src
./gradlew :adapter:outbound:persistence-mongo:mongoFailoverTest --console=plain
```
`MongoFailoverScenario.OPLOG_HISTORY_LOSS` and `RESUME_TOKEN_LOSS` assert the runner halts and names
this runbook rather than restarting from the current position.
+8 -7
View File
@@ -119,13 +119,14 @@ command's arguments.
`MongoStartupValidator` runs at context refresh, before the first request:
1. `MongoTopologyProbe` reports the actual `MongoTopology`.
2. Each declared `MongoTopologyRequirement` is checked against it — a transaction, causal-session or
change-stream requirement fails closed on `STANDALONE`.
3. `MongoSecurityProfileValidator` checks credentials and TLS.
4. `MongoCapabilitySupport` checks declared capabilities against the server version, with
`MongoSupportLevel` distinguishing `STABLE` / `ADVANCED` / `EXPERIMENTAL` / `UNSUPPORTED`.
5. `MongoPlatformHealthIndicator` reports the outcome for the readiness probe.
1. `MongoTopologyProbe` reports the actual `MongoTopology` and its `MongoCapabilitySet`.
2. Every profile's declared topology must match it, and a production profile on `STANDALONE` fails.
3. With `platform.transactions=true`, the probe must report `TRANSACTION` as `STABLE`; on
`STANDALONE` it does not, so startup fails.
4. `MongoSecurityProfileValidator` checks credentials and TLS, and that the admin credential differs
from the runtime one; the `MongoSchemaVersionRange` must not be inverted.
5. `MongoPlatformHealthIndicator` reports topology mismatch and secondary availability for the
readiness probe.
A misconfiguration found at startup costs a failed deploy. The same misconfiguration found at runtime
costs an incident, and the failing operation is rarely the one that reveals the cause.
+11 -11
View File
@@ -12,7 +12,6 @@ adds a row.
| Spring Boot | 4.0.0 | BOM-managed. Individual driver overrides are forbidden. |
| Spring Data MongoDB | 5.0.0 | Repository and `MongoTemplate` integration. Version comes from the Boot BOM. |
| MongoDB Java Driver | 5.6.1 | BOM-managed. Never pinned directly in the module. |
| Reactor | 3.8.0 | Reactive execution path. |
| Micrometer | 1.16.0 | Driver-native observability. |
| Testcontainers | 2.0.2 | Replica-set, failover, migration and compatibility lanes. |
@@ -40,19 +39,19 @@ fails `certifies()`.
| Topology | Status | What is certified | What is not |
|---|---|---|---|
| Standalone | **Smoke only** | Basic CRUD and mapping. | Not a production profile and never counts as Stable release evidence (D-03). Transactions, retryable writes and change streams are refused at startup by `MongoStartupValidator`. |
| Standalone | **Smoke only** | Basic CRUD and mapping. | Not a production profile and never counts as Stable release evidence (D-03). A production profile, or `platform.transactions=true`, on a Standalone server is refused at startup by `MongoStartupValidator`. |
| Single-node replica set | **Local default** (D-02) | Transactions, retryable writes, change streams — the same semantics as production. | Elections. A single-node set never holds one, so failover behaviour is untested here. |
| 3-node replica set | **Stable production gate** | Everything above plus primary failover, unknown-commit handling and change-stream resume across an election. | Shard routing. |
| 3-node replica set | **Stable production gate** | Everything above plus primary failover and unknown-commit handling. | Shard routing. |
| Sharded cluster | **Advanced gate** | Shard-key routing classification, scatter-gather refusal, `admin` plane operations. | Not included in the Stable gate. |
| Atlas / provider-managed | **Per-capability gate** | Search, vector search and encryption against the actual target deployment. | Atlas Local in a container is a pull-request convenience, explicitly **not** release evidence (`MongoAtlasCapabilityContractSuite.Environment`). |
| Atlas / provider-managed | **Not certified** | Encryption against the actual target deployment is the adopter's evidence to produce. | Search and vector search have no implementation in this leaf; a native `$search` command can only go through `PolicyAwareMongoNativeGateway` as a registered D3 operation. |
## 4. Stable API and client generations
| Plane | Stable API | Purpose |
|---|---|---|
| D1 Standard document persistence | V1, `apiStrict=true` | Repositories, typed queries, atomic updates, optimistic revision. |
| D2 Advanced document operations | V1, `apiStrict=true` | `MongoTemplate`, transactions, bulk, aggregation, keyset cursors, change streams. |
| D3 Explicit Mongo capability | Not strict | Native BSON, time series, search/vector, CSFLE/QE, shard-aware operations — each behind a registered capability. |
| D2 Advanced document operations | V1, `apiStrict=true` | `MongoTemplate`, transactions, bulk, aggregation, keyset cursors. |
| D3 Explicit Mongo capability | Not strict | Native BSON, CSFLE/QE, shard-aware operations — each behind a registered capability. |
| D4 Admin plane | Not strict | Collection, validator, index, migration, shard and repair commands. Separate credential, separate client. |
D3 is not a raw-client escape. Every call passes capability registration → database profile →
@@ -83,9 +82,10 @@ feature request:
| Tier | Capabilities | Enablement |
|---|---|---|
| Stable | Mapping, imperative/reactive execution, atomic update, optimistic lock, transactions, consistency profiles, retry/translation, query and aggregation guardrails, schema/index manifests, keyset pagination, bulk partial results, change streams, TTL contract, GeoJSON, security, observability | On when `ca-skeleton.persistence-mongo.enabled=true`. |
| Advanced | Sharding-aware query, time series, CSFLE, Queryable Encryption (equality/range), change-stream→messaging bridge, shared-collection multi-tenancy | Each behind `ca-skeleton.persistence-mongo.advanced.<capability>.enabled`. |
| Experimental | Search, vector search, hybrid search, database-per-tenant, collection-per-tenant, reshard orchestration, provider-specific features | Same flag mechanism; promotion additionally requires the evidence in [ADR-MONGO-ADV-001](../adr/ADR-MONGO-ADV-001-capability-promotion.md). |
| Stable, auto-configured | Mapping and BSON converters, imperative execution, atomic update, bulk partial results, consistency profiles, retry/translation, operation budgets, observability, typed client profiles, startup validation, health | Beans registered when `app.persistence-mongo.enabled=true`. |
| Stable, library API | Transactions, causal sessions, optimistic revision, query builder and keyset pagination, aggregation executor, schema/index/validator manifests and diffs, TTL contract, GeoJSON, migration runner, admin plane, native capability gateway | The adopter's adapter leaf takes this leaf as `implementation` and constructs the type. |
| Advanced, library API | Sharding-aware query and shard admin, CSFLE, Queryable Encryption (equality/range), shared-collection tenancy policies | Same, plus a `MongoAdvancedCapabilityGuard` whose flags enable the capability. No configuration property. |
| Experimental, library API | Database-per-tenant client registry and migration coordinator, reshard approval | Same as Advanced; promotion additionally requires the evidence in [ADR-MONGO-ADV-001](../adr/ADR-MONGO-ADV-001-capability-promotion.md). |
`MongoAdvancedCapabilityFlags.propertyFor(capability)` is the authoritative property name for any
capability; the table above is its prose form.
Search, vector search, time series and GridFS compatibility were interfaces with no implementation
and were removed on 2026-09-25 (`docs/capability-status.md`).
@@ -4,6 +4,13 @@
Accepted (2026-08-15). NTF-018 대응.
**갱신 (2026-09-25):** R1 type은 삭제됐다. production consumer가 끝까지 0건이었고 fake로만 증명된
계약이라, 새 consumer를 막는 ArchUnit 규칙을 유지할 이유가 없어졌다. 남은 것은 adapter core의
`RoutingNotifier`가 구현하는 단순 알림 포트 3개(`NotificationPort`, `Notification`,
`NotificationChannel`)뿐이다. 그래서 아래 「강제」의 `NOTIFICATION_R1_AND_PLATFORM_DO_NOT_DEPEND_ON_EACH_OTHER`
규칙과 `compatibility.r1` 예외 패키지도 함께 없어졌다. 삭제 목록과 마지막 커밋은
`docs/capability-status.md`의 「제거된 코드」 표에 있다. 아래 본문은 결정 당시 기록이다.
## 문제
같은 저장소에 notification 모델이 **두 개** 있다.
+10 -200
View File
@@ -1,6 +1,8 @@
# NTF-022 — public type surface of the notification platform.
# Every top-level public type under the platform packages. Growth is a reviewed
# change: ./gradlew updateNotificationApiSurface -PapproveNotificationApiChange
# NTF-022 — public type surface of the notification platform (application-notification + adapter:outbound:notification).
# Every top-level public type under the platform packages. Growth is a reviewed change.
# Update only after review with:
# ./gradlew :adapter:outbound:notification:updateNotificationApiSurface -PapproveNotificationApiSurfaceChange
# types: 362
dev.caskeleton.adapter.outbound.notification.NotificationConfig
dev.caskeleton.adapter.outbound.notification.NotificationRoutesSettings
dev.caskeleton.adapter.outbound.notification.core.FailOpenNotificationProvider
@@ -23,7 +25,6 @@ dev.caskeleton.adapter.outbound.notification.platform.autoconfigure.SmtpProvider
dev.caskeleton.adapter.outbound.notification.platform.callback.CallbackLimits
dev.caskeleton.adapter.outbound.notification.platform.callback.CallbackVerificationResult
dev.caskeleton.adapter.outbound.notification.platform.callback.MapProviderCallbackAdapterRegistry
dev.caskeleton.adapter.outbound.notification.platform.callback.MapProviderEventProjectorRegistry
dev.caskeleton.adapter.outbound.notification.platform.callback.ProviderCallbackAdapter
dev.caskeleton.adapter.outbound.notification.platform.callback.ProviderCallbackAdapterRegistry
dev.caskeleton.adapter.outbound.notification.platform.callback.ProviderCallbackVerificationRequest
@@ -31,12 +32,8 @@ dev.caskeleton.adapter.outbound.notification.platform.callback.VerifiedCallback
dev.caskeleton.adapter.outbound.notification.platform.dispatch.AttemptPermit
dev.caskeleton.adapter.outbound.notification.platform.dispatch.CapabilityReconciliationGateway
dev.caskeleton.adapter.outbound.notification.platform.dispatch.ConfiguredProfileCatalog
dev.caskeleton.adapter.outbound.notification.platform.dispatch.CredentialProbe
dev.caskeleton.adapter.outbound.notification.platform.dispatch.CredentialValidationException
dev.caskeleton.adapter.outbound.notification.platform.dispatch.JacksonRoutingPlanCodec
dev.caskeleton.adapter.outbound.notification.platform.dispatch.LeaseRecoveryService
dev.caskeleton.adapter.outbound.notification.platform.dispatch.LoggingInboxSignalPublisher
dev.caskeleton.adapter.outbound.notification.platform.dispatch.MapTemplateRendererRegistry
dev.caskeleton.adapter.outbound.notification.platform.dispatch.NotificationBackgroundWorkers
dev.caskeleton.adapter.outbound.notification.platform.dispatch.NotificationDispatchProperties
dev.caskeleton.adapter.outbound.notification.platform.dispatch.NotificationSchedulerWorker
@@ -44,11 +41,9 @@ dev.caskeleton.adapter.outbound.notification.platform.dispatch.ProviderAttemptLi
dev.caskeleton.adapter.outbound.notification.platform.dispatch.ProviderEventReplayWorker
dev.caskeleton.adapter.outbound.notification.platform.dispatch.ProviderRuntime
dev.caskeleton.adapter.outbound.notification.platform.dispatch.ProviderRuntimeRegistry
dev.caskeleton.adapter.outbound.notification.platform.dispatch.ProviderRuntimeRotator
dev.caskeleton.adapter.outbound.notification.platform.dispatch.ReconciliationJobWorker
dev.caskeleton.adapter.outbound.notification.platform.dispatch.RegistryProviderDispatchGateway
dev.caskeleton.adapter.outbound.notification.platform.dispatch.RegistryProviderRuntimeControl
dev.caskeleton.adapter.outbound.notification.platform.dispatch.RuntimeDrainCoordinator
dev.caskeleton.adapter.outbound.notification.platform.dispatch.SingleTenantContext
dev.caskeleton.adapter.outbound.notification.platform.dispatch.UuidV7Generator
dev.caskeleton.adapter.outbound.notification.platform.observation.LoggingNotificationAudit
@@ -58,37 +53,17 @@ dev.caskeleton.adapter.outbound.notification.platform.observation.NotificationHe
dev.caskeleton.adapter.outbound.notification.platform.observation.NotificationHealthSnapshot
dev.caskeleton.adapter.outbound.notification.platform.observation.NotificationServingThresholds
dev.caskeleton.adapter.outbound.notification.platform.provider.EmailAttachments
dev.caskeleton.adapter.outbound.notification.platform.provider.EmailRecipients
dev.caskeleton.adapter.outbound.notification.platform.provider.NotificationEndpoints
dev.caskeleton.adapter.outbound.notification.platform.provider.ProviderResults
dev.caskeleton.adapter.outbound.notification.platform.provider.UnconfiguredAttachmentResolver
dev.caskeleton.adapter.outbound.notification.platform.provider.apns.ApnsFailureClassifier
dev.caskeleton.adapter.outbound.notification.platform.provider.apns.ApnsNotificationProviderAdapter
dev.caskeleton.adapter.outbound.notification.platform.provider.apns.ApnsProviderProperties
dev.caskeleton.adapter.outbound.notification.platform.provider.apns.ApnsRequestMapper
dev.caskeleton.adapter.outbound.notification.platform.provider.fcm.FcmBatchCoordinator
dev.caskeleton.adapter.outbound.notification.platform.provider.fcm.FcmBatchResult
dev.caskeleton.adapter.outbound.notification.platform.provider.fcm.FcmContactPointUpdater
dev.caskeleton.adapter.outbound.notification.platform.provider.fcm.FcmFailureClassifier
dev.caskeleton.adapter.outbound.notification.platform.provider.fcm.FcmGateway
dev.caskeleton.adapter.outbound.notification.platform.provider.fcm.FcmMessageMapper
dev.caskeleton.adapter.outbound.notification.platform.provider.fcm.FcmNotificationProviderAdapter
dev.caskeleton.adapter.outbound.notification.platform.provider.fcm.FcmProviderProperties
dev.caskeleton.adapter.outbound.notification.platform.provider.fcm.FcmTargetMapper
dev.caskeleton.adapter.outbound.notification.platform.provider.fcm.FcmWireTarget
dev.caskeleton.adapter.outbound.notification.platform.provider.http.JdkNotificationHttpGateway
dev.caskeleton.adapter.outbound.notification.platform.provider.http.NotificationEndpoints
dev.caskeleton.adapter.outbound.notification.platform.provider.http.NotificationHttpGateway
dev.caskeleton.adapter.outbound.notification.platform.provider.http.NotificationHttpRequest
dev.caskeleton.adapter.outbound.notification.platform.provider.http.NotificationHttpResponse
dev.caskeleton.adapter.outbound.notification.platform.provider.http.NotificationHttpTransportException
dev.caskeleton.adapter.outbound.notification.platform.provider.ses.AwsSignatureV4Signer
dev.caskeleton.adapter.outbound.notification.platform.provider.ses.SesCallbackAdapter
dev.caskeleton.adapter.outbound.notification.platform.provider.ses.SesDeliveryProjector
dev.caskeleton.adapter.outbound.notification.platform.provider.ses.SesClients
dev.caskeleton.adapter.outbound.notification.platform.provider.ses.SesEventNormalizer
dev.caskeleton.adapter.outbound.notification.platform.provider.ses.SesFailureClassifier
dev.caskeleton.adapter.outbound.notification.platform.provider.ses.SesNotificationProviderAdapter
dev.caskeleton.adapter.outbound.notification.platform.provider.ses.SesProviderProperties
dev.caskeleton.adapter.outbound.notification.platform.provider.ses.SesRequestMapper
dev.caskeleton.adapter.outbound.notification.platform.provider.ses.SesSuppressionUpdater
dev.caskeleton.adapter.outbound.notification.platform.provider.ses.SnsCertificateProvider
dev.caskeleton.adapter.outbound.notification.platform.provider.ses.SnsSignatureVerifier
dev.caskeleton.adapter.outbound.notification.platform.provider.smtp.JavaMailSenderSmtpDispatch
@@ -98,31 +73,6 @@ dev.caskeleton.adapter.outbound.notification.platform.provider.smtp.SmtpFailureC
dev.caskeleton.adapter.outbound.notification.platform.provider.smtp.SmtpMimeMessageFactory
dev.caskeleton.adapter.outbound.notification.platform.provider.smtp.SmtpNotificationProviderAdapter
dev.caskeleton.adapter.outbound.notification.platform.provider.smtp.SmtpProviderProperties
dev.caskeleton.adapter.outbound.notification.platform.provider.twilio.TwilioCallbackAdapter
dev.caskeleton.adapter.outbound.notification.platform.provider.twilio.TwilioDeliveryProjector
dev.caskeleton.adapter.outbound.notification.platform.provider.twilio.TwilioFailureClassifier
dev.caskeleton.adapter.outbound.notification.platform.provider.twilio.TwilioProviderProperties
dev.caskeleton.adapter.outbound.notification.platform.provider.twilio.TwilioReconciliationCapability
dev.caskeleton.adapter.outbound.notification.platform.provider.twilio.TwilioRequestMapper
dev.caskeleton.adapter.outbound.notification.platform.provider.twilio.TwilioSignatureValidator
dev.caskeleton.adapter.outbound.notification.platform.provider.twilio.TwilioSmsProviderAdapter
dev.caskeleton.adapter.outbound.notification.platform.provider.twilio.TwilioStatusNormalizer
dev.caskeleton.adapter.outbound.notification.platform.provider.webhook.WebhookNotificationProviderAdapter
dev.caskeleton.adapter.outbound.notification.platform.provider.webhook.WebhookSignatureStrategy
dev.caskeleton.adapter.outbound.notification.platform.provider.webhook.WebhookSubscription
dev.caskeleton.adapter.outbound.notification.platform.provider.webpush.EncryptedWebPushPayload
dev.caskeleton.adapter.outbound.notification.platform.provider.webpush.Rfc8291Aes128GcmEncryptor
dev.caskeleton.adapter.outbound.notification.platform.provider.webpush.VapidAuthorizationProvider
dev.caskeleton.adapter.outbound.notification.platform.provider.webpush.VapidJwtSigner
dev.caskeleton.adapter.outbound.notification.platform.provider.webpush.VapidKeyRegistry
dev.caskeleton.adapter.outbound.notification.platform.provider.webpush.WebPushFailureClassifier
dev.caskeleton.adapter.outbound.notification.platform.provider.webpush.WebPushNotificationProviderAdapter
dev.caskeleton.adapter.outbound.notification.platform.provider.webpush.WebPushProviderProperties
dev.caskeleton.adapter.outbound.notification.platform.provider.webpush.WebPushReceiptCapability
dev.caskeleton.adapter.outbound.notification.platform.provider.webpush.WebPushRequestMapper
dev.caskeleton.adapter.outbound.notification.platform.reactor.ReactiveNotificationOrchestrator
dev.caskeleton.adapter.outbound.notification.platform.reactor.ReactorContextBridge
dev.caskeleton.adapter.outbound.notification.platform.reactor.ReactorNotificationOrchestrator
dev.caskeleton.adapter.outbound.notification.platform.security.AesGcmCallbackPayloadProtection
dev.caskeleton.adapter.outbound.notification.platform.security.AesGcmContactPointProtector
dev.caskeleton.adapter.outbound.notification.platform.security.AesGcmNotificationPayloadProtection
@@ -135,117 +85,18 @@ dev.caskeleton.adapter.outbound.notification.platform.template.JacksonInboxConte
dev.caskeleton.adapter.outbound.notification.platform.template.JacksonNotificationVariablesCodec
dev.caskeleton.adapter.outbound.notification.platform.template.JacksonTemplateContentCodec
dev.caskeleton.adapter.outbound.notification.platform.template.JsonSchemaVariableValidator
dev.caskeleton.adapter.outbound.notification.platform.template.NotificationDigest
dev.caskeleton.adapter.outbound.notification.platform.template.NotificationJsonMapper
dev.caskeleton.adapter.outbound.notification.platform.template.NotificationTemplateEngine
dev.caskeleton.adapter.outbound.notification.platform.template.PlaceholderTemplateEngine
dev.caskeleton.adapter.outbound.notification.platform.template.Sha256MessageDigestAdapter
dev.caskeleton.adapter.outbound.notification.platform.template.TemplateSlotMode
dev.caskeleton.adapter.outbound.notification.platform.template.TemplateSlotPolicy
dev.caskeleton.adapter.outbound.notification.platform.template.ThymeleafNotificationRenderer
dev.caskeleton.adapter.outbound.notification.platform.template.ThymeleafStringTemplateEngine
dev.caskeleton.adapter.outbound.notification.slack.webhook.SlackClient
dev.caskeleton.adapter.outbound.notification.slack.webhook.SlackNotificationAdapterConfig
dev.caskeleton.adapter.outbound.notification.slack.webhook.SlackWebhookProvider
dev.caskeleton.application.notification.ApplyNotificationReceiptCommand
dev.caskeleton.application.notification.ApplyNotificationReceiptResult
dev.caskeleton.application.notification.ApplyNotificationReceiptUseCase
dev.caskeleton.application.notification.ConsentCheckMode
dev.caskeleton.application.notification.EmailRecipientReference
dev.caskeleton.application.notification.InitializeNotificationWriterFencesCommand
dev.caskeleton.application.notification.InitializeNotificationWriterFencesOperation
dev.caskeleton.application.notification.InitializeNotificationWriterFencesResult
dev.caskeleton.application.notification.InitializeNotificationWriterFencesUseCase
dev.caskeleton.application.notification.InlineNotificationAttemptPort
dev.caskeleton.application.notification.NormalizedNotificationReceiptCommand
dev.caskeleton.application.notification.Notification
dev.caskeleton.application.notification.NotificationAdmissionClass
dev.caskeleton.application.notification.NotificationAdmissionGateCommand
dev.caskeleton.application.notification.NotificationAdmissionGateUseCase
dev.caskeleton.application.notification.NotificationAdmissionReadinessPort
dev.caskeleton.application.notification.NotificationAppendResult
dev.caskeleton.application.notification.NotificationApplicationException
dev.caskeleton.application.notification.NotificationAttemptId
dev.caskeleton.application.notification.NotificationCanonicalWriterFenceGuard
dev.caskeleton.application.notification.NotificationCanonicalWriterFencePort
dev.caskeleton.application.notification.NotificationCanonicalWriterRouteSet
dev.caskeleton.application.notification.NotificationCapabilityCompatibilityValidator
dev.caskeleton.application.notification.NotificationChannel
dev.caskeleton.application.notification.NotificationDeliveryId
dev.caskeleton.application.notification.NotificationDeliveryStorePort
dev.caskeleton.application.notification.NotificationDispatchCommand
dev.caskeleton.application.notification.NotificationDispatchResult
dev.caskeleton.application.notification.NotificationDispatchUseCase
dev.caskeleton.application.notification.NotificationEvidenceTrustSnapshot
dev.caskeleton.application.notification.NotificationFaultScope
dev.caskeleton.application.notification.NotificationFrozenPlan
dev.caskeleton.application.notification.NotificationIntentAppendPort
dev.caskeleton.application.notification.NotificationIntentDraft
dev.caskeleton.application.notification.NotificationIntentId
dev.caskeleton.application.notification.NotificationKindId
dev.caskeleton.application.notification.NotificationKindPolicy
dev.caskeleton.application.notification.NotificationLegacyWriterPermitCommand
dev.caskeleton.application.notification.NotificationLegacyWriterPermitResult
dev.caskeleton.application.notification.NotificationLegacyWriterPermitUseCase
dev.caskeleton.application.notification.NotificationMaintenanceCommand
dev.caskeleton.application.notification.NotificationMaintenanceResult
dev.caskeleton.application.notification.NotificationMaintenanceStorePort
dev.caskeleton.application.notification.NotificationMaintenanceUseCase
dev.caskeleton.application.notification.NotificationMode
dev.caskeleton.application.notification.NotificationOperationsSnapshot
dev.caskeleton.application.notification.NotificationOperationsSnapshotPort
dev.caskeleton.application.notification.NotificationOperationsSnapshotQuery
dev.caskeleton.application.notification.NotificationOperationsSnapshotUseCase
dev.caskeleton.application.notification.NotificationPlanPort
dev.caskeleton.application.notification.NotificationPlanningResult
dev.caskeleton.application.notification.NotificationPort
dev.caskeleton.application.notification.NotificationProviderAttemptPort
dev.caskeleton.application.notification.NotificationProviderCapabilityDescriptor
dev.caskeleton.application.notification.NotificationReasonCode
dev.caskeleton.application.notification.NotificationReceiptEventId
dev.caskeleton.application.notification.NotificationReceiptFact
dev.caskeleton.application.notification.NotificationReceiptIngressCapabilityDescriptor
dev.caskeleton.application.notification.NotificationReceiptProjection
dev.caskeleton.application.notification.NotificationReceiptStorePort
dev.caskeleton.application.notification.NotificationRecipientReference
dev.caskeleton.application.notification.NotificationReconciliationPort
dev.caskeleton.application.notification.NotificationRequestResult
dev.caskeleton.application.notification.NotificationRouteId
dev.caskeleton.application.notification.NotificationRouteStrategy
dev.caskeleton.application.notification.NotificationSignedEvidenceHeader
dev.caskeleton.application.notification.NotificationStoreCapabilityDescriptor
dev.caskeleton.application.notification.NotificationTechnicalSuppressionPort
dev.caskeleton.application.notification.NotificationTemplateParameters
dev.caskeleton.application.notification.NotificationTemplateRef
dev.caskeleton.application.notification.NotificationTemplateValue
dev.caskeleton.application.notification.NotificationWriterCutoverPort
dev.caskeleton.application.notification.NotificationWriterInventoryEvidence
dev.caskeleton.application.notification.NotificationWriterInventoryEvidenceVerifierPort
dev.caskeleton.application.notification.NotificationWriterOwnership
dev.caskeleton.application.notification.NotificationWriterQuiescenceAttestationPort
dev.caskeleton.application.notification.NotificationWriterRouteSet
dev.caskeleton.application.notification.ProviderAttemptOutcome
dev.caskeleton.application.notification.ReconcileNotificationDeliveriesCommand
dev.caskeleton.application.notification.ReconcileNotificationDeliveriesResult
dev.caskeleton.application.notification.ReconcileNotificationDeliveriesUseCase
dev.caskeleton.application.notification.RecordNotificationWriterQuiescenceAttestationCommand
dev.caskeleton.application.notification.RecordNotificationWriterQuiescenceAttestationOperation
dev.caskeleton.application.notification.RecordNotificationWriterQuiescenceAttestationResult
dev.caskeleton.application.notification.RecordNotificationWriterQuiescenceAttestationUseCase
dev.caskeleton.application.notification.RetryDisposition
dev.caskeleton.application.notification.SignedNotificationWriterInventoryManifest
dev.caskeleton.application.notification.SignedNotificationWriterQuiescenceManifest
dev.caskeleton.application.notification.SlackAudienceReference
dev.caskeleton.application.notification.SubmissionCertainty
dev.caskeleton.application.notification.SwitchNotificationWriterOwnershipCommand
dev.caskeleton.application.notification.SwitchNotificationWriterOwnershipOperation
dev.caskeleton.application.notification.SwitchNotificationWriterOwnershipResult
dev.caskeleton.application.notification.SwitchNotificationWriterOwnershipUseCase
dev.caskeleton.application.notification.TargetAttemptOutcome
dev.caskeleton.application.notification.TerminalizeExpiredNotificationWriterPermitsCommand
dev.caskeleton.application.notification.TerminalizeExpiredNotificationWriterPermitsOperation
dev.caskeleton.application.notification.TerminalizeExpiredNotificationWriterPermitsResult
dev.caskeleton.application.notification.TerminalizeExpiredNotificationWriterPermitsUseCase
dev.caskeleton.application.notification.platform.admin.AdminAccessDeniedException
dev.caskeleton.application.notification.platform.admin.AdminActor
dev.caskeleton.application.notification.platform.admin.AdminAuthorizationGuard
@@ -280,7 +131,6 @@ dev.caskeleton.application.notification.platform.api.NormalizedEventType
dev.caskeleton.application.notification.platform.api.NormalizedProviderEvent
dev.caskeleton.application.notification.platform.api.NotificationAcceptance
dev.caskeleton.application.notification.platform.api.NotificationId
dev.caskeleton.application.notification.platform.api.NotificationOrchestrator
dev.caskeleton.application.notification.platform.api.NotificationPlan
dev.caskeleton.application.notification.platform.api.NotificationReceipt
dev.caskeleton.application.notification.platform.api.NotificationSnapshot
@@ -311,31 +161,19 @@ dev.caskeleton.application.notification.platform.api.delivery.DeliveryOutcome
dev.caskeleton.application.notification.platform.api.delivery.EvidenceLevel
dev.caskeleton.application.notification.platform.api.delivery.RecipientDeliveryState
dev.caskeleton.application.notification.platform.api.delivery.SubmissionOutcome
dev.caskeleton.application.notification.platform.api.error.AmbiguousSubmissionException
dev.caskeleton.application.notification.platform.api.error.AttachmentIntegrityException
dev.caskeleton.application.notification.platform.api.error.AttachmentUnavailableException
dev.caskeleton.application.notification.platform.api.error.CallbackProjectionException
dev.caskeleton.application.notification.platform.api.error.CallbackValidationException
dev.caskeleton.application.notification.platform.api.error.FailureCategory
dev.caskeleton.application.notification.platform.api.error.IdempotencyConflictException
dev.caskeleton.application.notification.platform.api.error.InvalidContactPointException
dev.caskeleton.application.notification.platform.api.error.NotificationCapacityException
dev.caskeleton.application.notification.platform.api.error.NotificationException
dev.caskeleton.application.notification.platform.api.error.NotificationExpiredException
dev.caskeleton.application.notification.platform.api.error.NotificationFailureCode
dev.caskeleton.application.notification.platform.api.error.NotificationFailureDescriptor
dev.caskeleton.application.notification.platform.api.error.NotificationSuppressedException
dev.caskeleton.application.notification.platform.api.error.NotificationValidationException
dev.caskeleton.application.notification.platform.api.error.ProviderAuthenticationException
dev.caskeleton.application.notification.platform.api.error.ProviderAuthorizationException
dev.caskeleton.application.notification.platform.api.error.ProviderConfigurationException
dev.caskeleton.application.notification.platform.api.error.ProviderPayloadLimitException
dev.caskeleton.application.notification.platform.api.error.ProviderPermanentException
dev.caskeleton.application.notification.platform.api.error.ProviderRejectedException
dev.caskeleton.application.notification.platform.api.error.ProviderThrottledException
dev.caskeleton.application.notification.platform.api.error.ProviderTransientException
dev.caskeleton.application.notification.platform.api.error.ProviderUnavailableException
dev.caskeleton.application.notification.platform.api.error.ReconciliationException
dev.caskeleton.application.notification.platform.api.error.TemplateNotFoundException
dev.caskeleton.application.notification.platform.api.error.TemplateRenderingException
dev.caskeleton.application.notification.platform.api.error.TemplateVariableValidationException
@@ -357,7 +195,6 @@ dev.caskeleton.application.notification.platform.callback.ProjectionStatus
dev.caskeleton.application.notification.platform.callback.ProviderEventLedger
dev.caskeleton.application.notification.platform.callback.ProviderEventProjectionService
dev.caskeleton.application.notification.platform.callback.ProviderEventProjector
dev.caskeleton.application.notification.platform.callback.ProviderEventProjectorRegistry
dev.caskeleton.application.notification.platform.callback.ProviderEventRecord
dev.caskeleton.application.notification.platform.callback.ProviderEventRecordId
dev.caskeleton.application.notification.platform.callback.ProviderEventSource
@@ -378,7 +215,6 @@ dev.caskeleton.application.notification.platform.contact.MobilePushTarget
dev.caskeleton.application.notification.platform.contact.PhoneNumber
dev.caskeleton.application.notification.platform.contact.WebPushSubscriptionValue
dev.caskeleton.application.notification.platform.dispatch.AcceptNotificationApplicationUseCase
dev.caskeleton.application.notification.platform.dispatch.ApplicationReceiptServiceImpl
dev.caskeleton.application.notification.platform.dispatch.AttachmentIntegrityGuard
dev.caskeleton.application.notification.platform.dispatch.CancelNotificationApplicationUseCase
dev.caskeleton.application.notification.platform.dispatch.CanonicalNotificationPlanEncoder
@@ -393,7 +229,7 @@ dev.caskeleton.application.notification.platform.dispatch.DispatchOutcomeRecorde
dev.caskeleton.application.notification.platform.dispatch.DispatchPipeline
dev.caskeleton.application.notification.platform.dispatch.DuplicateIdempotencyKeyException
dev.caskeleton.application.notification.platform.dispatch.GetNotificationApplicationUseCase
dev.caskeleton.application.notification.platform.dispatch.MessageDigestPort
dev.caskeleton.application.notification.platform.dispatch.LeaseRecoveryService
dev.caskeleton.application.notification.platform.dispatch.NotificationDispatchService
dev.caskeleton.application.notification.platform.dispatch.NotificationIdGeneratorPort
dev.caskeleton.application.notification.platform.dispatch.NotificationRequestInsertOutcome
@@ -404,6 +240,7 @@ dev.caskeleton.application.notification.platform.dispatch.NotificationRoutePlann
dev.caskeleton.application.notification.platform.dispatch.NotificationRoutingPlanCodecPort
dev.caskeleton.application.notification.platform.dispatch.NotificationSubmissionService
dev.caskeleton.application.notification.platform.dispatch.NotificationVariablesCodecPort
dev.caskeleton.application.notification.platform.dispatch.PlanFingerprint
dev.caskeleton.application.notification.platform.dispatch.PolicyRoutePlanner
dev.caskeleton.application.notification.platform.dispatch.ProviderDispatchGatewayPort
dev.caskeleton.application.notification.platform.dispatch.ProviderProfileCatalogPort
@@ -417,14 +254,10 @@ dev.caskeleton.application.notification.platform.dispatch.ReconciliationGatewayP
dev.caskeleton.application.notification.platform.dispatch.ReconciliationJob
dev.caskeleton.application.notification.platform.dispatch.ReconciliationJobStorePort
dev.caskeleton.application.notification.platform.dispatch.ReconciliationService
dev.caskeleton.application.notification.platform.dispatch.RequestFingerprint
dev.caskeleton.application.notification.platform.dispatch.ScheduleNotificationApplicationUseCase
dev.caskeleton.application.notification.platform.dispatch.SubmitNotificationApplicationUseCase
dev.caskeleton.application.notification.platform.dispatch.SyntheticEventFingerprint
dev.caskeleton.application.notification.platform.dispatch.TemplateRendererRegistry
dev.caskeleton.application.notification.platform.dispatch.TenantContextPort
dev.caskeleton.application.notification.platform.email.EmailNotification
dev.caskeleton.application.notification.platform.email.EmailNotifier
dev.caskeleton.application.notification.platform.inbox.CreateInboxItemCommand
dev.caskeleton.application.notification.platform.inbox.InboxContentCodecPort
dev.caskeleton.application.notification.platform.inbox.InboxCursor
@@ -512,35 +345,14 @@ dev.caskeleton.application.notification.platform.provider.ReconciliationCapabili
dev.caskeleton.application.notification.platform.provider.ReconciliationResult
dev.caskeleton.application.notification.platform.provider.ResolvedAttachment
dev.caskeleton.application.notification.platform.provider.TraceContext
dev.caskeleton.application.notification.platform.push.ApplicationIdentity
dev.caskeleton.application.notification.platform.push.ApplicationReceipt
dev.caskeleton.application.notification.platform.push.ApplicationReceiptService
dev.caskeleton.application.notification.platform.push.MobilePushNotification
dev.caskeleton.application.notification.platform.push.MobilePushNotifier
dev.caskeleton.application.notification.platform.push.ReceiptAuthorizationException
dev.caskeleton.application.notification.platform.push.ReceiptKind
dev.caskeleton.application.notification.platform.push.ReceiptResult
dev.caskeleton.application.notification.platform.security.AccessContext
dev.caskeleton.application.notification.platform.security.ContactPointProtector
dev.caskeleton.application.notification.platform.security.NotificationPayloadProtection
dev.caskeleton.application.notification.platform.security.NotificationPayloadUnreadableException
dev.caskeleton.application.notification.platform.security.NotificationRedactor
dev.caskeleton.application.notification.platform.security.ProtectedContactPoint
dev.caskeleton.application.notification.platform.security.SafeDiagnosticContext
dev.caskeleton.application.notification.platform.security.SecretKeyMaterial
dev.caskeleton.application.notification.platform.security.SecretMaterialProvider
dev.caskeleton.application.notification.platform.security.SecretPurpose
dev.caskeleton.application.notification.platform.security.SensitiveValueClassifier
dev.caskeleton.application.notification.platform.security.SensitiveValueKind
dev.caskeleton.application.notification.platform.security.UnsafeDiagnosticFieldException
dev.caskeleton.application.notification.platform.sms.E164PhoneNumberParser
dev.caskeleton.application.notification.platform.sms.GsmAlphabet
dev.caskeleton.application.notification.platform.sms.InvalidPhoneNumberException
dev.caskeleton.application.notification.platform.sms.SmsEncoding
dev.caskeleton.application.notification.platform.sms.SmsEstimate
dev.caskeleton.application.notification.platform.sms.SmsNotification
dev.caskeleton.application.notification.platform.sms.SmsNotifier
dev.caskeleton.application.notification.platform.sms.SmsSegmentEstimator
dev.caskeleton.application.notification.platform.template.NotificationTemplateRenderer
dev.caskeleton.application.notification.platform.template.NotificationTemplateVersion
dev.caskeleton.application.notification.platform.template.RenderCommand
@@ -553,5 +365,3 @@ dev.caskeleton.application.notification.platform.template.TemplateStatus
dev.caskeleton.application.notification.platform.template.TemplateVariableValidator
dev.caskeleton.application.notification.platform.template.TemplateVersionConflictException
dev.caskeleton.application.notification.platform.template.VariableSchema
dev.caskeleton.application.notification.platform.webpush.WebPushNotification
dev.caskeleton.application.notification.platform.webpush.WebPushNotifier
+1 -1
View File
@@ -104,7 +104,7 @@ the three they achieved.
one thing — `AesGcmCallbackPayloadProtection`, which protects raw callback bodies — and by nothing on
the accept path. Demanding it would make a deployment supply a key that protects nothing while the
payload it appears to be about stays in plaintext. The repository already has one defect of that
exact shape: `backend.graphql.cursor.key-ids`, which production refuses to start without and which no
exact shape: `app.graphql.cursor.key-ids` (key removed 2026-09-25), which production refuses to start without and which no
code signs a cursor with (GQL-INT-003). Adding a second would make the pattern a habit.
## Consequence
@@ -50,3 +50,7 @@ writes projections directly.
Where a provider has no status-query capability, the platform records `Unsupported` and leaves the
attempt ambiguous. It does not infer a final status.
The shipped families, SES and SMTP, have no reconciliation: their assemblers contribute no
`ReconciliationCapability`, so every reconciliation job for them ends `Unsupported`. The slot on
`AssembledProvider` is for a provider family an adopter assembles with a status query of its own.
+27 -29
View File
@@ -1,20 +1,25 @@
# Configuration reference
The notification delivery platform binds under `ca-skeleton.notification.platform`. The tree lives in
`src/app-bootstrap/src/main/resources/application.yml`, disabled by default, and every value carries
an inline default so a deployment that leaves the platform off supplies nothing.
The notification delivery platform binds under `app.notification.platform`. The tree lives in
`src/composition/notification-platform/src/main/resources/config/module-defaults/notification.yml`,
which the support leaf's `ModuleDefaultsEnvironmentPostProcessor` loads at the lowest precedence,
so an application without the module carries none of it. The module is in no default composition: a
service selects it with `runtimeOnly project(':composition:notification-platform')` (plus the
persistence-jpa line) in `app-bootstrap/build.gradle`, and it is on when present. Every value carries
an inline default, so a deployment that switches the platform off supplies nothing.
Until 2026-08-15 this page named properties the binding did not have — `max-retry-concurrency`,
`scheduler-poll-interval`, `callback-worker-concurrency` — and omitted three it did. There was no
tree in `application.yml` at all, so the only way to configure the platform was to guess environment
variable names from Boot's relaxed binding. `./gradlew verifyNotificationConfiguration` now fails
when this page, the YAML tree and `docs/registries/env-keys.yaml` disagree.
variable names from Boot's relaxed binding. `NotificationEnvironmentRegistryTest`
(`:composition:notification-platform:test`) now fails when the shipped YAML and
`docs/registries/env-keys.yaml` disagree.
## Master switch
| Property | Environment variable | Default | Meaning |
|---|---|---|---|
| `enabled` | `APP_NOTIFICATION_PLATFORM_ENABLED` | `false` | Binds nothing at all while false: no runtime, no schema check, no scheduler thread, no secret required |
| `enabled` | `APP_NOTIFICATION_PLATFORM_ENABLED` | `true` | On while the module is present. `false` binds nothing at all: no runtime, no schema check, no scheduler thread, no secret required |
| `mode` | `APP_NOTIFICATION_PLATFORM_MODE` | `SERVING` | `SERVING` refuses to start without a working provider; `INGEST_ONLY` stores requests and does not dispatch |
## Dispatch
@@ -40,7 +45,7 @@ still waiting on gets claimed by a second worker, and the recipient receives the
|---|---|---|---|
| `callbacks.enabled` | `APP_NOTIFICATION_PLATFORM_CALLBACKS_ENABLED` | `false` | boolean |
| `callbacks.max-body-bytes` | `APP_NOTIFICATION_PLATFORM_CALLBACK_MAX_BODY_BYTES` | `65508` | 1..65508 |
| `callbacks.replay-skew` | `APP_NOTIFICATION_PLATFORM_CALLBACK_REPLAY_SKEW` | `5m` | positive |
| `callbacks.replay-skew` | `APP_NOTIFICATION_PLATFORM_CALLBACK_REPLAY_SKEW` | `5m` | positive; SNS messages whose `Timestamp` is further than this from receipt, either way, are rejected |
| `callbacks.trusted-proxies` | `APP_NOTIFICATION_PLATFORM_CALLBACK_TRUSTED_PROXIES` | *(empty)* | CSV of peer addresses |
여러 provider가 요청 URL에 서명하므로, 그 URL을 잘못 재구성하면 정상 webhook이 전부 서명 실패가 된다.
@@ -55,20 +60,17 @@ nonce and tag. A larger configured value would pass every check above the databa
## Provider profiles
Profiles are a map under `providers`, keyed by profile id. Arbitrary deployment-chosen ids can be
supplied as YAML or through Spring relaxed binding (`CA_SKELETON_NOTIFICATION_PLATFORM_PROVIDERS_<ID>_<FIELD>`).
supplied as YAML or through Spring relaxed binding (`APP_NOTIFICATION_PLATFORM_PROVIDERS_<ID>_<FIELD>`).
The shipped reference profiles `smtp` and `ses` additionally expose explicit `APP_NOTIFICATION_PLATFORM_SMTP_*`
and `APP_NOTIFICATION_PLATFORM_SES_*` aliases so operators do not have to invent binding names.
| Field | Meaning |
|---|---|
| `type` | `APNS`, `FCM`, `SES`, `SMTP`, `TWILIO`, `WEB_PUSH`, `WEBHOOK` — a closed enum, so an unknown value fails binding rather than assembling into nothing |
| `type` | `SES`, `SMTP` — a closed enum, so an unknown value fails binding rather than assembling into nothing |
| `enabled` | A disabled profile is bound and validated but contributes no runtime |
| `primary-for-channel` | Exactly one primary per channel |
| `environment` | Required when enabled |
| `credential-profile` | Provider credential key id resolved through `SecretMaterialProvider`; never inline secret material |
| `topic` | APNs bundle id |
| `vapid-public-key` | Web Push application server key |
| `callback-signing-secret-ref` | Reference, not material |
| `timeout` | Positive and finite |
| `max-concurrency` | Positive |
| `rate-per-second` | Positive |
@@ -82,11 +84,12 @@ An enabled SES profile adds a typed `ses` block:
| Field | Meaning |
|---|---|
| `ses.endpoint` | SES API base URI; the mapper appends `/v2/email/outbound-emails` |
| `ses.region` | SigV4 region |
| `ses.endpoint` | SES API base URI, used as the AWS SDK client's endpoint override |
| `ses.region` | AWS region the SDK signs for |
| `ses.sender-identity` | verified SES From identity |
| `ses.access-key-id` | AWS access key id; identifier only, not secret material |
| `ses.configuration-set` | optional SES configuration-set name |
| `ses.allowed-topic-arns` | SNS topic ARNs whose SES events this profile accepts (`APP_NOTIFICATION_PLATFORM_SES_ALLOWED_TOPIC_ARNS`, comma-separated). Required when `callbacks.enabled=true`: binding fails without it, because a valid SNS signature only proves AWS sent the message and anyone can own a topic |
| `credential-profile` | key id for the secret access-key material; generation 1 is activated at assembly |
The shipped reference profile is `providers.ses` and is disabled by default. It is controlled by
@@ -94,22 +97,19 @@ The shipped reference profile is `providers.ses` and is disabled by default. It
`APP_NOTIFICATION_PLATFORM_PROVIDER_CREDENTIAL_KEY`, whose active key id must match
`APP_NOTIFICATION_PLATFORM_SES_CREDENTIAL_KEY_ID`.
`type` is the closed **provider model**, not a promise that the shipped composition contains a
dispatch assembler for every value. Current shipped reachability is:
`type` lists only the families the shipped composition can assemble. Current shipped
reachability is:
| Provider type | Contract/adapter code | Shipped dispatch assembler | Shipped callback assembler | What happens when enabled for dispatch |
|---|---|---|---|---|
| `SMTP` | yes | **yes** | no | assembles when Spring Mail relay settings are complete |
| `SES` | yes | **yes** | **yes** | assembles an EMAIL runtime from the typed `ses` block; SNS callback verification remains available in `INGEST_ONLY` |
| `TWILIO` | yes | no | no | dispatch fails startup by profile name |
| `FCM` | yes | no | no | dispatch fails startup by profile name |
| `APNS` | yes | no | no | dispatch fails startup by profile name |
| `WEB_PUSH` | yes | no | no | dispatch fails startup by profile name |
| `WEBHOOK` | yes | no | no | dispatch fails startup by profile name |
This distinction is deliberate: tested provider protocol code is not the same thing as a
composition-reachable provider. Adding a family to the shipped runtime requires a
`ProviderRuntimeAssembler` plus the settings/secret inputs that adapter actually needs.
APNs, FCM, Twilio, Web Push and Webhook adapters used to ship as protocol code with no assembler, so
enabling one failed startup. They were removed; the `docs/capability-status.md` "제거된 코드" table
names the last commit that had them. Adding a family back means adding its adapter, a
`ProviderRuntimeAssembler`, its `ProviderType` constant and the settings/secret inputs it actually
needs, together.
## SMTP relay
@@ -135,7 +135,7 @@ already owns them and a second spelling would be a second thing to keep in step.
| Property | Environment variable | Default | Bound |
|---|---|---|---|
| `smtp.sender-identity` | `APP_NOTIFICATION_PLATFORM_SMTP_SENDER_IDENTITY` | `no-reply@example.invalid` | address |
| `smtp.max-concurrency` | `APP_NOTIFICATION_PLATFORM_SMTP_DISPATCH_CONCURRENCY` | `4` | positive |
| `smtp.dispatch-concurrency` | `APP_NOTIFICATION_PLATFORM_SMTP_DISPATCH_CONCURRENCY` | `4` | positive |
SMTP transport configuration has one owner: Spring Mail. The actual `JavaMailSenderImpl` must use required STARTTLS (`mail.smtp.starttls.enable=true` plus `mail.smtp.starttls.required=true`) or implicit TLS (`mail.smtp.ssl.enable=true`). It must also have positive `mail.smtp.connectiontimeout`, `mail.smtp.timeout`, and `mail.smtp.writetimeout` values. SMTP assembly fails before serving traffic when those properties are absent or invalid.
@@ -158,8 +158,7 @@ Startup fails rather than degrading when:
- a TTL-required profile has no expiry source
- a callback signing secret is missing
- a production profile enables trust-all
- an APNs profile is missing its environment or topic
- a Web Push profile is missing its VAPID key
- an SES profile is missing its `ses` block, or callbacks are on and `ses.allowed-topic-arns` is empty
- two provider profiles share an id
- a route points only at disabled providers
- `mode` is `SERVING` and no provider profile is enabled
@@ -171,7 +170,7 @@ All key material arrives through `SecretMaterialProvider`. Nothing is read from
committed file, or from a plaintext log. Contact point encryption and lookup HMAC keys must be
distinct, and the encryption key must be exactly 256 bits.
Eight purposes, eight keys. Each is base64 of at least 32 bytes and each must differ from every
Seven purposes, seven keys. Each is base64 of at least 32 bytes and each must differ from every
other; the platform decodes them at startup and refuses to boot if one is blank, short or shared. A
blank value used to be skipped, which meant the platform started without the key and found out on
the first contact point — in production, on a recipient's notification.
@@ -189,7 +188,6 @@ any example: a value that appears in the repository is a value that has been dis
| Provider credential encryption | `APP_NOTIFICATION_PLATFORM_PROVIDER_CREDENTIAL_KEY` | `APP_NOTIFICATION_PLATFORM_PROVIDER_CREDENTIAL_KEY_ID` |
| Provider request lookup HMAC | `APP_NOTIFICATION_PLATFORM_PROVIDER_REQUEST_LOOKUP_HMAC_KEY` | `APP_NOTIFICATION_PLATFORM_PROVIDER_REQUEST_LOOKUP_HMAC_KEY_ID` |
| Payload encryption | `APP_NOTIFICATION_PLATFORM_PAYLOAD_ENCRYPTION_KEY` | `APP_NOTIFICATION_PLATFORM_PAYLOAD_ENCRYPTION_KEY_ID` |
| Web Push VAPID signing | `APP_NOTIFICATION_PLATFORM_VAPID_SIGNING_KEY` | `APP_NOTIFICATION_PLATFORM_VAPID_SIGNING_KEY_ID` |
A key id is not secret — an id identifies key material without revealing it — but it is required,
and it has no default on purpose. A constant id makes a rotation indistinguishable from the key it

Some files were not shown because too many files have changed in this diff Show More