설계: 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>
2.7 KiB
2.7 KiB
HTTP Client Platform — Release Checklist
A release is complete when each item below is demonstrated by a command, not by review.
Gates
cd src
./gradlew :adapter:outbound:httpclient:test --console=plain
./gradlew :adapter:outbound:httpclient:httpClientStableContractTest --console=plain
./gradlew :adapter:outbound:httpclient:httpClientSecurityTest --console=plain
./gradlew :adapter:outbound:httpclient:httpClientBlockHoundTest --console=plain
./gradlew :adapter:outbound:httpclient:spring62CompatibilityTest --console=plain
./gradlew :adapter:outbound:httpclient:spring70CompatibilityTest --console=plain
./gradlew :adapter:outbound:httpclient:httpClientFailureInjectionTest --console=plain # needs Docker
./gradlew :adapter:outbound:httpclient:httpClientPerformanceTest \
-Pperformance.assertions.enabled=true --console=plain
./gradlew verifyCleanArchitectureDependencies --console=plain
./gradlew :app-bootstrap:architectureTest --console=plain
python3 ../scripts/verify-httpclient-docs.py
Completion criteria (design §33)
- Typed clients are the default entry point; H2 and H3 are separately authorised.
- H1–H4 cannot bypass timeout, host, TLS, auth, size, or observation policy.
- Apache, JDK, and Reactor produce identical result and exception metadata.
- Pool, DNS, connect, TLS, and retry backoff all fit inside the effective deadline.
- Every extra attempt is explained by idempotency, replayability, evidence, deadline, and budget.
- Non-idempotent
SENT_NO_RESPONSEsurfaces asHttpAmbiguousExecutionException. - Pool and buffers are reclaimed after unread bodies, decode errors, cancels, and size rejections.
- OAuth2 refresh is single-flight and 401 replay happens at most once.
- Trust-all and hostname-verification bypass fail at startup.
- Canonicalisation, DNS/IP validation, redirect revalidation, and egress control all pass.
- No transparent retry occurs after the first delivered byte.
- No platform code blocks a Reactor event loop, proven by a BlockHound self-check.
- The negotiated wire protocol matches what the support matrix claims per transport.
- Logical calls and attempts are separate metrics with no forbidden label.
- DNS, pool, TLS, reset, partial response, and HTTP/2 GOAWAY are reproducible.
- Thread, heap, direct memory, pool, and retry budget bounds hold.
- The support matrix, configuration reference, security guide and runbook match the code.
Experimental
Jetty HTTP/3 stays Experimental until Http3CapabilityReport reports QUIC and TLS 1.3 and the
contract subset it declares passes in a dedicated environment. It is never auto-configured by the
Stable starter.