문제: 설계서·계획서·납품 패키지·증거·학습 문서와 ADR이 기록이라는 표시 없이 지금 문서처럼 읽힌다. 상태 칸이 설계서 72개 중 40개, 계획서는 거의 없고, 있어도 Approved·확정·Accepted.처럼 값이 제각각이며 영어다. 고른 방법: docs/design, docs/history, docs/adr, docs/notification/adr의 .md 246개 맨 위에 같은 모양의 머리 블록을 단다. 칸은 상태·작성일· 요약(한국어 한 문장)·현재 정본, 대체됐으면 대체됨이다. 블록은 표시 줄 두 개로 감싸서 빼면 원문 바이트가 그대로 돌아온다(246개 모두 대조함). - 종류는 폴더가 정하고 둘째 줄에 적는다(plans/evidence는 증거). - 상태는 원래 상태 줄을 고정 어휘로 바꾼 값이다. 상태 줄이 없는 설계서와 체크 상자가 다 표시되지 않은 계획서는 「확인 안 함」. capability-status.md 제거 표로 지운 것이 확인된 설계서 다섯은 「폐기」, 2026-07-20 하네스 설계·계획과 production capability platform 설계는 「대체됨」이다. - 현재 정본은 구조 정리로 옮겨질 수 있는 src/messaging·src/grpc 대신 docs/ 쪽 문서나 옮기지 않는 leaf README를 가리킨다. docs/README.md에 「문서 수명과 언어」「기록 문서의 머리 블록」「문서와 코드를 같은 변경에서 고친다」를 더하고, 파생 서비스 안내에 머리 블록 충돌 가능성을 적었다. 버린 대안: H1 제목 아래에 블록을 두는 안은 보기에는 낫지만 빼는 규칙이 파일마다 달라져 원문 복원이 기계적이지 않다. 「종류」 칸을 따로 두는 안은 폴더와 같은 정보를 두 번 쓰게 한다. 위험·한계: 「확인 안 함」 설계서 38개, 계획서 51개는 지금 유효한지 아무도 판정하지 않았다. 요약은 제목·목표 줄을 보고 쓴 것이라 본문을 끝까지 읽지 않았다. 납품 패키지 셋의 MANIFEST.sha256는 이제 맞지 않는다 (납품 당시 바이트의 해시이고, 블록을 빼면 다시 맞는다). 리뷰 폴더에는 아직 머리 블록을 달지 않았다. 검증: 머리 블록을 뺀 내용과 HEAD 원본 246개 일치, check-work-docs.py rc=0, --links docs·README.md·CLAUDE.md·AGENTS.md 깨진 링크 0.
7.1 KiB
기록 · 계획서 본문은 쓴 때의 원문이다. 지금 동작은 「현재 정본」을 읽는다.
- 상태: 끝남
- 작성일: 2026-07-28
- 요약: HTTP client 활성화를 명시적인 조립 결정으로 만드는 실행 계획이다.
- 현재 정본:
docs/httpclient/support-matrix.md
HTTP Client Canonical Zero-Binding Implementation Plan
For agentic workers: REQUIRED SUB-SKILL: Use
superpowers:subagent-driven-developmentorsuperpowers:executing-plans. Repository policy overrides the skill's commit steps: do not stage, commit, amend, or push.
Goal: Make HTTP client activation an explicit canonical composition decision and prove that the default zero-binding state creates no client, executor, shutdown guard, retry/circuit-breaker registry, or transport resource.
Architecture: adapter:outbound:httpclient owns strict canonical configuration, immutable
binding/provider/catalog/readiness registries, and a pure activation resolver. app-bootstrap owns
the composition root that binds canonical properties and publishes an inert capability descriptor.
The existing JDK OutboundHttpClient remains an explicitly constructed R1 migration facade; its
legacy settings and infrastructure configuration must no longer be discovered automatically.
Scope boundary: This increment does not add Apache HC5, a provider factory, a real semantic
upstream binding, hard wire cancellation, TLS/DNS/proxy/auth, or an R2 readiness claim. Every current
ACTIVE selection must fail closed because the only derived readiness card remains
NOT_IMPLEMENTED.
Task 1: Add strict canonical selection and provider binding models
Files:
-
Create:
src/adapter/outbound/httpclient/src/main/java/dev/caskeleton/adapter/outbound/httpclient/activation/HttpClientExpectedState.java -
Create:
src/adapter/outbound/httpclient/src/main/java/dev/caskeleton/adapter/outbound/httpclient/activation/HttpClientCanonicalConfiguration.java -
Create:
src/adapter/outbound/httpclient/src/main/java/dev/caskeleton/adapter/outbound/httpclient/activation/HttpClientCanonicalConfigurationBinder.java -
Test:
src/adapter/outbound/httpclient/src/test/java/dev/caskeleton/adapter/outbound/httpclient/activation/HttpClientCanonicalConfigurationBinderTest.java -
Write RED tests for the canonical YAML shape under
ca-skeleton.capabilities.http-clientandca-skeleton.providers.http-client. -
Reject unknown fields, malformed IDs, unknown expected state, and any legacy input entering canonical composition, including the DISABLED state.
-
Preserve
OutboundHttpSettingsconstructors as migration API, but remove its global@ConfigurationPropertiesScanparticipation. -
Keep provider definitions inert data; configuration alone must not create a transport.
Task 2: Add catalog/readiness registries and pure fail-closed activation resolution
Files:
-
Create:
src/adapter/outbound/httpclient/src/main/java/dev/caskeleton/adapter/outbound/httpclient/activation/HttpOperationCatalogRegistry.java -
Create:
src/adapter/outbound/httpclient/src/main/java/dev/caskeleton/adapter/outbound/httpclient/activation/HttpClientReadinessCardRegistry.java -
Create:
src/adapter/outbound/httpclient/src/main/java/dev/caskeleton/adapter/outbound/httpclient/activation/ResolvedHttpClientCapability.java -
Create:
src/adapter/outbound/httpclient/src/main/java/dev/caskeleton/adapter/outbound/httpclient/activation/HttpClientActivationResolver.java -
Test:
src/adapter/outbound/httpclient/src/test/java/dev/caskeleton/adapter/outbound/httpclient/activation/HttpClientActivationResolverTest.java -
Prove
DISABLED + bindings 0 + provider definitions 0resolves toDISABLED_VERIFIED, selected binding/card count 0. -
Reject
DISABLEDwith bindings or provider resources. -
Reject
ACTIVEwith zero bindings. -
For every binding, require an exact provider, provider destination, and registered operation catalog for the same destination.
-
Derive the
httpclient-static-bufferedcard from each current buffered classic profile. -
Mark that card
NOT_IMPLEMENTED; reject ACTIVE before any provider resource/factory exists.
Task 3: Move HTTP Spring activation to the composition root
Files:
-
Modify:
src/adapter/outbound/httpclient/src/main/java/dev/caskeleton/adapter/outbound/httpclient/OutboundHttpClientConfig.java -
Modify:
src/adapter/outbound/httpclient/src/main/java/dev/caskeleton/adapter/outbound/httpclient/OutboundHttpSettings.java -
Modify:
src/adapter/outbound/httpclient/src/main/java/dev/caskeleton/adapter/outbound/httpclient/resilience/OutboundHttpResilienceConfig.java -
Create:
src/app-bootstrap/src/main/java/dev/caskeleton/bootstrap/httpclient/HttpClientCompositionConfig.java -
Modify:
src/app-bootstrap/src/main/resources/application.yml -
Modify:
src/app-bootstrap/src/test/java/dev/caskeleton/adapter/outbound/OptionalAdapterBeanGatingTest.java -
Test:
src/app-bootstrap/src/test/java/dev/caskeleton/bootstrap/httpclient/HttpClientCompositionConfigTest.java -
Detach legacy HTTP infrastructure from component/configuration-properties scanning while preserving direct constructors/factory methods used by forks and existing unit tests.
-
Register only canonical configuration, immutable registries, resolver, and inert descriptor in the composition root.
-
Default application YAML to canonical
expected-state: DISABLED, empty bindings, and empty provider definitions; keep legacy migration keys out of both main and test application YAML. -
Assert zero
OutboundHttpClient,RestClient,OutboundCallExecutor,OutboundHttpShutdownGuard,OutboundHttpResilience,RetryRegistry, andCircuitBreakerRegistrybeans/resources in the default context. -
Assert contradictory/ACTIVE configurations fail startup before resource construction.
-
Load the real
application.ymlin composition tests and prove ACTIVE reaches theNOT_IMPLEMENTEDreadiness card rather than a legacy conflict.
Task 4: Document exact readiness and verify
Files:
-
Modify:
src/adapter/outbound/httpclient/README.md -
Modify:
src/adapter/outbound/httpclient/CLAUDE.md -
Modify:
docs/superpowers/specs/2026-07-27-httpclient-production-capability-design.md -
Modify:
docs/superpowers/plans/2026-07-28-httpclient-production-capability-foundation.md -
Mark canonical zero-binding as implemented without marking HTTP R2 complete.
-
Keep HC5/provider resources/security/real-network qualification explicitly unimplemented.
-
Run focused tests:
cd src
./gradlew :adapter:outbound:httpclient:check --rerun-tasks --console=plain
./gradlew :app-bootstrap:check --rerun-tasks --console=plain
./gradlew :sample-portfolio:test --rerun-tasks --console=plain
./gradlew verifyCleanArchitectureDependencies verifyConfigurationPropertiesProcessor \
verifyEnvKeys verifyPublicPathSnapshot --console=plain
Do not edit unrelated notification, messaging, object-storage, JPA, MongoDB, GraphQL, gRPC, web, or WebSocket files.