Files
clean-architecture-backend-…/docs/capability-status.md
T
DongHyeonkaandClaude Opus 5.5 6d27356e2b refactor: 부가 기능을 capability 모듈로 포장하고 기본 조립을 web-only로 전환
설계: docs/superpowers/specs/2026-09-25-capability-module-packaging-design.md
계획/진행 기록: docs/superpowers/plans/2026-09-25-capability-module-packaging.md

- Wave 0: 규칙 고정(AGENTS.md capability 완료 기준·테스트 규칙) + 차단 결함 7건
  (compose overlay 검사, redis-sdk CI job, 적용된 V9/V13 원복 + V16, @EnableScheduling,
  messaging bridge 순서, prod 에러 상세 validator, sample loggers read-only)
- Wave 1: 데이터·보안 Critical 10건 (durable operation 25P02, operation 유스케이스 이동,
  outbox 재인코딩, Kafka TLS/SASL, 알림 트랜잭션, SNS 서명, tus checksum, GraphQL fragment,
  Redis lane, gRPC FAILED_TERMINAL)
- Wave 2: 리팩터링 잔재·실험용 자리 삭제, outbox v1 fencing(V17), 멱등성 V2 정본화
- Wave 3: 라이브러리형 코드 정리(동작하지 않는 설정·인터페이스·gate 제거, web-advanced 분리)
- Wave 4: capability 11개를 "있으면 켜짐" 모듈로 포장, 끄는 장치 제거, 기본 조립 web-only,
  qualificationBootJar 분리
- Wave 5: 빌드 로직 축소(17.2k -> 10.8k줄), sample 테스트 컨벤션 적용

삭제한 코드는 docs/capability-status.md "제거된 코드" 표에 복구 커밋(208077fd)과 함께 기록.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-09-25 12:49:07 +09:00

77 KiB

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.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.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 <커밋>:<경로>).

대상 경로 마지막으로 존재한 커밋 이유
파일 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의 같은 이름 테스트로 옮김