Files
clean-architecture-backend-…/docs/fileserver/support-matrix.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

4.1 KiB

Fileserver support matrix

A support level here is a claim about evidence, not about intent. Every row names the CI job that produces that evidence; FileserverDocumentationCoverageTest fails the build if a row names a job that does not exist, so a level can never outlive the test that justified it.

Levels

Level What it means
Stable Certified on every pull request. Contract changes are breaking changes.
Beta Certified nightly. The contract may still change with a deprecation notice.
Limited Certified on the release gate only, under stated constraints.
Compatibility Accepted but not optimized; known caveats are listed inline.
Experimental Off by default, unratified upstream, may change without notice.

Runtime profiles

Profile Level CI job
Local filesystem (ext4) content store Stable fileserver-local-ext4-contract
Spring MVC transport (raw, multipart, batch, download) Stable fileserver-http-contract
Path, filename, range, and problem-detail hardening Stable fileserver-security-suite
Bounded-memory transfer Stable fileserver-bounded-memory
Application and architecture invariants Stable fileserver-unit-and-architecture
Runtime assembly (the capability starts with the flag on) Stable fileserver-unit-and-architecture
tus 1.0 resumable uploads Stable fileserver-http-contract
Crash-recovery matrix Beta fileserver-process-kill-matrix
NFSv4 ambiguity handling Beta fileserver-nfs-ambiguity
Large-file and slow-client performance Beta fileserver-large-file-performance
Multi-instance writer lease Beta fileserver-multi-instance-lease
Kubernetes ReadWriteOnce PVC Limited fileserver-pvc-certification (manifest checks in CI; cluster run is operator-driven)
Nginx X-Accel-Redirect delegation Limited fileserver-http-contract
Telemetry sensitive-data suppression Stable fileserver-sensitive-telemetry-scan
Documentation and support-claim coverage Stable fileserver-documentation-gate
Full release verification Stable fileserver-full-verification
HTTP resumable uploads draft-12 Experimental fileserver-http-contract

WebFlux transport removed

The reactive router and handlers (web.fileserver.reactive) were removed on 2026-09-25 (D4: the template is servlet on virtual threads). The shipped composition could never select them — the web leaf puts DispatcherServlet on the classpath, so Boot resolves SERVLET.

Explicitly not claimed

These have no job, and therefore no claim:

  • An automated Kubernetes cluster result. fileserver-pvc-certification validates the manifest on every release and applies it only when a release cluster is configured; without one it warns and records that nothing was certified. The cluster tuple is produced by an operator and read from storage-certification.md.

  • Kubernetes ReadWriteMany PVC. Concurrent writers across nodes are not certified.

  • Windows NTFS as a production storage root. The filename policy strips the characters NTFS reserves, but no job certifies the publish path there.

  • Object storage as a content store. The contract exists (ContentStoreContract) but no adapter implements it yet.

  • Server-side malware scanning. The verification pipeline has the port and the verdict precedence; no scanner is shipped.

Where the rest is written down