- 결정 32: fileserver transport 연산 21개를 `port.in` use case로, 쓰기·읽기에 `file:*` 권한(소유자·tenant 정책은 유지), inbound 서비스 이름 `*UseCase`, port 구현 이름 `<Tech><Port>` 규칙(S2-#13b, 24개) - 디렉터리 descriptor 파일 primitive를 `adapter:outbound:support`로(S4-lead-2 일부 — fileserver는 번역만), persistence-fileserver를 scan·클래스별 조건 대신 명시적 `@Bean` 설정으로(S2-#8a 일부), `FileVerifier`를 adapter로 - 호출자 0인 `poster.image-attached` 이벤트 삭제, SES SDK client를 레지스트리 종료 때 close, fileserver migration V1–V5 고정 - P29: auxiliary 레인 → Gradle `jvm-test-suite`(BUILD-O3-5, build-logic 16,768 → 5,851줄), redis-sdk가 runtime을 api로(P22-new-3) - 통합: JPA API surface 기준선 재승인(이름 규칙 변경), migration lane에 V19 반영, messaging 통합 테스트가 jar 안 migration 목록 조회(ORCH-new-5) - P28·P29 에이전트가 세션 재시작으로 중단 — 커밋된 것만 합치고 결과 파일은 오케스트레이터가 확정, S6-#10a는 P30으로 검증: ./gradlew ci verifyDependencyLocks --warning-mode=fail(714 task) · mainCheck architectureCheck verifyPublicPathSnapshot :app-bootstrap:verifyEnvKeys configContractCheck · :app-bootstrap:integrationTest :sample-portfolio:integrationTest :sample-portfolio:systemTest integrationCheck · -p build-logic test · -p optional-platforms ci · releaseCheck qualificationBootJar 통과 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Keycloak realm artifact
realms/ca-skeleton-realm.json is imported by the keycloak service in docker-compose.infra.yml
and is the same realm every GraphQL qualification lane authenticates against.
The client secret is a reference, never a value
The confidential client ca-skeleton-api carries "secret": "${KEYCLOAK_GRAPHQL_SMOKE_CLIENT_SECRET}".
entrypoint.sh reads the value from the Compose secret mounted at
/run/secrets/keycloak-graphql-smoke-client-secret, exports it, and execs kc.sh start-dev --import-realm, so the value never reaches Git, a rendered Compose config, a command line, or an
evidence file. A realm file with a working credential in it is a credential in the repository, and
"it is only for smoke tests" is not something a scanner or a fork can tell.
No comment keys in the realm JSON
Keycloak deserializes this file into RealmRepresentation with unknown fields rejected, not
ignored. A "_comment" key here fails the whole import with Unrecognized field "_comment", the
container exits 1, and the lane fails on Keycloak rather than on anything it was testing. That is
why this rationale lives in Markdown next to the artifact instead of inside it.
What the realm grants
- realm role
user— the baseline role the application authorizes ordinary calls on - client role
ca-skeleton-api:graphql-query— permission to execute a GraphQL query - client roles
notification-submit,notification-template-publish,operation-submit— the platform permissionssecurity.ymlmaps them to - client roles
ROLE_FILE_READandROLE_FILE_WRITE— the fileserver's read and write tiers, whichsecurity.ymlalso maps tofile:readand tofile:upload,file:delete,file:copy,file:move;ROLE_FILE_ADMIN(file:admin) is defined but not granted to the service account, since the management plane is off by default - a service account for the client-credentials grant the qualification lane uses
- audience and realm/client role mappers, so the issued token carries what the resource server validates
Standard flow and direct access grants are disabled: the lane authenticates as a service, and an enabled password grant is a second way in that nothing tests.