Files
clean-architecture-backend-…/docs/capability-status.md
T
DongHyeonkaandClaude Opus 5.5 016597ac78 review-followup Wave 2: 정합성 수정 통합과 검증, 현황표·재개 프롬프트
13개 작업 묶음(P1–P13)의 W2 커밋을 합치고 전체 게이트로 검증했다.

- 묶음별 정합성 수정(notification dispatch·recovery, object storage staged
  publication, fileserver 복구·정리, gRPC 플랫폼, Redis 분류·lease TTL, JPA
  outbox claim 순서·durable operation HTTP, web 요청 id·category 필수, graphql
  에러 mapper, Mongo profile 바인딩, build 소스 보존 게이트·compose smoke info 확인)
- 통합 때 드러난 3건 수정: outbox claim 테스트 fixture의 가짜 envelope hash,
  sample scan이 새 operation controller를 등록하던 문제, SpotBugs aux classpath
  파일이 truncate되지 않아 로컬에서 ".jar.jar"로 실패하던 문제
- 현황표: 묶음 결과 반영, 소유자 결정 21–27, 후속 발견 결함 47행, 요약 갱신
- docs/capability-status.md 「제거된 코드」에 85행 추가
- 묶음 결과 파일·에이전트 지시·스크립트를 docs로 옮기고 desktop 재개 프롬프트 추가

검증: check, ci verifyDependencyLocks, mainCheck, architecture/public path/env
keys/config contract, bootstrap·sample integration/system, build-logic·build-tools
test, optional-platforms ci, qualificationBootJar 통과. integrationCheck는 이번
작업 전에도 실패하던 lane(Redis topology 모드 인자, httpclient failure
injection, AWS 보호 lane)만 실패.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-09-28 14:46:30 +09:00

344 lines
104 KiB
Markdown

# Capability status — IMPLEMENTED / WIRED / QUALIFIED
Three different questions get three different answers, and conflating them is what the
2026-09-18 techlead review found over and over: a capability with 12,000 lines and 482 green tests
that no running application assembled, and a provider with no wiring that was nonetheless live.
"There is code for it" is not "the shipped artifact builds it" is not "it has been proven against a
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** | 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.
Each row below names the lane *and* the workflow, so "qualified" can be checked rather than believed.
## Status
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) | `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. |
| 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 **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.
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` 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 이름)으로 재정의 |