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
1.3 KiB
Plaintext
16 lines
1.3 KiB
Plaintext
## 95. P2 — release gate가 실제로 차단하는 것은 hermetic test 3개이고, mongo용 CI workflow는 없다
|
|
|
|
이 leaf는 릴리스 증거 장치를 정성껏 만들었다. `MongoReleaseEvidenceVerifier`는 exit code 대신 **JUnit XML을 읽고**, testsuite 이름이 contract의 클래스와 일치하는지 확인하고, 파일이 실행 시작 시각보다 오래됐으면 거부하고, 전부 skip된 lane을 거부한다. 그 근거도 정확하다.
|
|
|
|
> A Gradle test task exits zero when it runs the tests and also when its selector matched a different test… So "sharded topology certified" was satisfied by a hermetic unit test whose name happened to contain `Shard`.
|
|
|
|
그런데 그 장치가 실제로 지키는 목록을 열어 보면(`138-...` §8.3c, `src/config/mongodb/release-contracts.json`):
|
|
|
|
| | id | task | class | topology |
|
|
|---|---|---|---|---|
|
|
| **blocking** | MONGO-REL-001 | `mongoStableContractTest` | `MongoModuleBoundaryTest` | none |
|
|
| | MONGO-REL-002 | `mongoStableContractTest` | `MongoAdvancedRulesTest` | none |
|
|
| | MONGO-REL-003 | `mongoStableContractTest` | `MongoTransactionRetryCoordinatorTest` | none |
|
|
| **experimental** | MONGO-REL-010 | `mongoShardedTest` | `MongoShardedTopologyContractTest` | sharded |
|
|
| | MONGO-REL-011 | `mongoAtlasTest` | `MongoAtlasContractTest` | atlas |
|