Server onboarding and authority¶
Curated source-specific evidence, not a new run or qualification of current source. Dates, measurements, failure outcomes and original source identifiers retain their recorded meaning. Old tags/assets have been retired and original commits may no longer resolve after the privacy rewrite. Where identifiers were sanitized earlier, the original hardware/run association cannot be independently recovered from the public derivative. Current acceptance lives in the roadmap.
Operator accepted the Phase 5 onboarding/paired-subscription correction on
2026-10-14 at application a34004f, qualification 50e9957 and documentation
492f4db. The paired-record subscription regression failed before the writable
repair, then passed 182 native and 182 sanitizer assertions, 193 in a local
trusted browser and 199 per installed architecture. Exact source/merge tree and
limits remain in paired-subscription data.
The prior Server foundation covered administration, security, service lifecycle, resource observations and both installed architectures; its source/package associations remain in Phase 5 data. These are scoped synthetic fixtures, not live acquisition or fleet throughput.
Consequential corrections and limitations¶
- A caller's OpenSSL error queue contaminated an independent fixture connection; isolating the test-client error state preserved the actual TLS failure verdict. It was a fixture correction, not proof that arbitrary TLS errors are harmless.
- Browser readiness must wait for visible enabled controls and successful persisted requests, never assume an early disabled-form submit exercised administration.
- Private-PKI rollout exposed a renewal-unit UID/GID transition failure. Keep only the required initial SETUID/SETGID capability and drop it before credential use.
- A read-only human session must replace prior machine-operator authority on the same socket. The actual-TLS regression failed before repair; the corrected path denies account management while permitting job inventory.
- The 2026-10-19 sanitizer
configuration_lock_lifetimehelper probe timed out with empty stderr. Direct helpers passed; a leak-sanitizer cause was not established. Added exit/signal/read diagnostics passed 52 assertions under the original deadline. That pass did not diagnose the original anomaly.
The final 2026-10-25 acceptance correction used reviewed baseline
5dd320766e21015eda6526b779b8fe3c246c7c68 and main runs 40153301820 /
40193722967 plus release run 40155888034. Local checks recorded 388 real
onboarding, 160 sanitizer acceptance, 88 ingestion and 128 mounted-fault
assertions across six faults. Post-rename directory-open/fsync faults retained
recovery authority; a controlled issuer barrier proved independent control,
record bytes and ACK progress. Late/stale responses could not publish authority.
These results do not transfer to a new source revision.
Current identity operations and Server operations replace the old step-by-step deployment and CI scheduling narratives.