refactor: 빌드 최적화 및 ci 수정

2026-09-17 15:24:31 +09:00
parent 944a1e348b
commit ace8aaaef6
263 changed files with 1975 additions and 3130 deletions
@@ -36,10 +36,9 @@ design package's assumed module layout onto this leaf lives in
  `verifyCleanArchitectureDependencies` only checks that resolved edges are a subset of the declared
  ones, so an unused permission passes every run; `MongoRegistryPermissionParityTest` checks the
  other direction and fails when the two sets differ.
- `runtime_memberships` is `["app-bootstrap"]`, and the composition root really does declare
-  `implementation(project(':adapter:outbound:persistence-mongo'))` — with the reactive starter and
-  the reactivestreams driver excluded, because there is no reactive port in the shipped Stable
-  scope. `RuntimeMembershipClasspathAgreementTest` compares the registry against the resolved
+- The composition root declares `implementation(project(':adapter:outbound:persistence-mongo'))` —
+  with the reactive starter and the reactivestreams driver excluded, because there is no reactive
+  port in the shipped Stable scope. The actual Gradle runtime graph is the runtime SSOT;
  runtime classpath, so the membership cannot drift from what the jar carries. Property-only
  activation therefore works here: the switch turns on a module that already ships, and shipping it
  off is not the same contract as leaving it out, because absence cannot be reversed at deploy time