M12.4: qualify migration ownership across TLS path loss
Foundation / checks (ecs) (push) Successful in 2m29s
Foundation / checks (deploy) (push) Successful in 4m8s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (checks) (push) Canceled after 18m9s
Foundation / checks (client) (push) Canceled after 18m8s
Foundation / checks (network) (push) Canceled after 18m7s
Foundation / checks (tsan) (push) Canceled after 15m39s
Foundation / checks (postgres) (push) Canceled after 18m13s

This commit is contained in:
dingo
2026-10-18 13:19:59 -04:00
parent 0f071f3f8b
commit e0a7c13f6b
16 changed files with 707 additions and 14 deletions
+55
View File
@@ -1,5 +1,60 @@
# Validation report
## 2026-10-18 - M12.4k TLS migration request/receipt and owner partitions
Test-only qualification extends ADR-0147–0149 with opaque loopback TCP relays and
the unchanged adapter's end-to-end `verify-full` PostgreSQL TLS. A separate
disposable cluster mode admits only the test runtime login over loopback TLS;
ordinary fixtures keep TCP disabled. Full/sanitizer CI paths run this matrix.
See [fixture, tooling and limits](M12_MIGRATION_TRANSPORT_FAULTS.md).
Executed locally:
- Native MSVC Release **78/78 passed**, 12.63 s.
- Actual GCC 14 optional targets rebuilt; final TLS matrix passed **35 s**
(34 s population phase), with both raw/cohort markers for request/reply loss
and independent owner partition/expiry/replacement/heal.
- Linux Clang 19 **ASan/UBSan** TLS matrix passed **62 s** (58 s population phase),
with no sanitizer reports.
- Separate Linux Clang 19 **ThreadSanitizer** optional PostgreSQL build and TLS
matrix passed **63 s** (60 s population phase), with no race reports.
- Explicit clang-tidy 19 on the relay and publication/fault tests passed with no
owned warnings. Repository clang-format 19 and shell syntax checks passed.
- Complete frozen-binary private PostgreSQL qualification passed with **exit 0**,
**540 s**: C++ integration/process/load/history (432 s), the separate TLS fault
matrix (36 s), life reservations, backup/restore, host-loss DR, upgrade,
migration history/rollback, runtime permission audit and checksum/future-version
rejection. The detached runner recorded its completion code.
Wrong-hostname TLS connections fail. Discarded requests return unknown with the
exact prepared manifests while independent observation proves both heads stayed
unchanged. Discarded commit replies return unknown while independent observation
proves both exact results committed. Source preparation, destination staging and
explicit abort also lose real replies without losing retained work or activating
ghosts. Either owner remains isolated through actual lease expiry, while its
healthy peer keeps the same epoch and freeze. Replacement gets a newer epoch and
the same retained work; stale publication fails with both heads unchanged.
Explicit current-source abort reconciles lost receipts. The healthy host resumes
identical biology; a healed old owner stays fenced while replacement authority
is held. All of these cases run for raw and cohort representations with actual
player-origin wildlife and the existing full replay/continuation matrix.
The initial analysis found avoidable stop-token copies in the test relay; both
callback/run arguments now use const references. No warning suppression or
production retry/TLS escape hatch was added. The new relay is test-owned and its
worker is joined; no production thread/service is introduced.
Limits: byte discard at an application TCP boundary on one machine is not kernel
packet loss, a multi-host routing/firewall failure, a database host outage, object
store unavailability or an orchestrator drill. Existing local objects stay
available. The CI-only image adds distro OpenSSL/Python utilities for ephemeral
credentials/port selection; local versions/licensing evidence are recorded in
the fixture document. No Docker image build or remote CI result is claimed here.
Linked ecology, maturation, global census/cuts, target-host costs and actual
elapsed-day soak remain open. No SQL, production adapter, biological format/rule,
golden, live database, World0 or deployment changed. `Build_Errors.txt` and unrelated
local work remain untracked; prior captured CI runner failures remain separate.
## 2026-10-18 - M12.4j atomic paired biological publication and recovery
ADR-0149/schema 49 commits both exact bundle-10 no-tick results and one immutable