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>
16 lines
584 B
Plaintext
16 lines
584 B
Plaintext
### 64.4 Idempotency real-PostgreSQL TTL boundaries
|
|
|
|
`evidence/raw/066-postgresql-idempotency-replay-boundary-probe.txt`
|
|
|
|
- exact `postgresqlIdempotencyIntegrationTest` lane
|
|
- `complete()` changed replay TTL false-same replay 재현
|
|
- expired COMPLETED row의 `inspect()`/`claim()` lifecycle 불일치 재현
|
|
- temporary test는 실행 후 source에서 복원
|
|
- BUILD SUCCESSFUL
|
|
|
|
### 64.5 Dedicated PostgreSQL unit test full fresh rerun
|
|
|
|
`evidence/raw/067-persistence-jpa-postgresql-unit-tests.txt`
|
|
|
|
9 dedicated test classes를 `--rerun-tasks`로 실행했고 BUILD SUCCESSFUL이다.
|