DongHyeonkaandClaude Opus 5
b2963105a8
The keycloak project ended with four open questions that design could not
settle. A two-VM lab was built to answer them by measurement, and this is
that material: 26 experiments, 125 raw command outputs, 22 browser captures.
Follows the import procedure in README.md.
source/ the originating repository verbatim — 78 documents, 28 SVGs,
8 manifests, plus .source-revision recording the commit
final/ the SSOT
document.md 729 lines written from the 29 experiment documents, not
concatenated: what was predicted, what was measured, and
where the measurement itself was wrong
evidence/raw 125 outputs, flattened to <experiment>__<file> because
the originals collided (01-baseline.txt appeared three
times) and the audit only globs the top level
evidence/meta one per raw file; command and exitCode are null and the
README says why rather than inventing them
evidence/browser 22 captures
assets/ three diagrams through techviz
.techviz/ their VizSpecs
A separate project rather than an addition to keycloak: the B-layer answers
that project's four questions, but the A, C and D layers are about cluster
failure, SSO and operations, and one document.md should hold one subject.
The four question records there can point here through 관계.
Recorded rather than papered over: only three of the 28 diagrams were
remade. The repository forbids hand-drawn SVG and forbids titles inside the
canvas; all 28 originals carry both, so converting them is redrawing, not
reformatting. They stay in source/ and the gap is written into the document.
verify-pipeline.py passes. audit-records.py reports no issues.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
47 lines
2.3 KiB
Plaintext
47 lines
2.3 KiB
Plaintext
# 릴리스 레지스트리가 이 게이트에 붙인 생산자 태스크
|
|
56: "name": "collection-fetch-pagination",
|
|
57- "task": ":adapter:outbound:persistence-jpa:jpaPlatformQueryPlanTest",
|
|
58- "blocking": true
|
|
59- }
|
|
# blocking 이 참인 게이트 / 거짓인 게이트: 6 / 0
|
|
# 매니페스트 파서가 blocking 을 읽는 줄: 0
|
|
# 게이트 검증기가 blocking 을 읽는 줄: 0
|
|
|
|
# 그 태스크와 게이트 테스트의 태그
|
|
250:def jpaPlatformContractTest = registerJpaPlatformLane(
|
|
251- 'jpaPlatformContractTest',
|
|
252- 'jpa-contract',
|
|
254:def jpaPlatformMigrationTest = registerJpaPlatformLane(
|
|
255- 'jpaPlatformMigrationTest',
|
|
256- 'jpa-migration',
|
|
258:def jpaPlatformFailureTest = registerJpaPlatformLane(
|
|
259- 'jpaPlatformFailureTest',
|
|
260- 'jpa-failure',
|
|
262:def jpaPlatformQueryPlanTest = registerJpaPlatformLane(
|
|
263- 'jpaPlatformQueryPlanTest',
|
|
264- 'jpa-queryplan',
|
|
266:def jpaPlatformSecurityTest = registerJpaPlatformLane(
|
|
267- 'jpaPlatformSecurityTest',
|
|
268- 'jpa-security',
|
|
238: includeTags tag
|
|
26:@Tag("jpa-contract")
|
|
# jpa-queryplan 태그를 단 클래스: PostgreSqlQueryPlanContractTest.java
|
|
|
|
# 그 불일치를 지나가게 하는 검증기가 무엇을 보는가
|
|
violations << "${name}: gate task must be an absolute Gradle path, was '${path}'"
|
|
violations << "${name}: no project at '${projectPath}' for gate task '${path}'"
|
|
violations << "${name}: no task '${taskName}' in '${projectPath}'"
|
|
violations << "${name}: '${path}' is not a Test task, so it produces no JUnit evidence"
|
|
# 레지스트리를 읽는 단위 테스트의 게이트 단언
|
|
45: for (String gate : JpaReleaseGate.required()) {
|
|
46- assertThat(manifest.taskFor(gate))
|
|
47- .as("gate %s must name the task that produces its evidence", gate)
|
|
48- .startsWith(":");
|
|
|
|
# 그래도 그 테스트는 다른 레인으로 돈다
|
|
jpa-nightly.yml:49: :adapter:outbound:persistence-jpa:jpaPlatformContractTest
|
|
jpa-pr.yml:86: :adapter:outbound:persistence-jpa:jpaPlatformContractTest
|
|
gradlew :adapter:outbound:persistence-jpa:jpaPlatformContractTest --console=plain
|
|
gradlew :adapter:outbound:persistence-jpa:jpaPlatformContractTest :adapter:outbound:persis
|
|
304: dependsOn jpaPlatformContractTest
|