fix(track-a): reconcile canonical bootstrap admission on current main

[blakinio]

Current-main replay of accepted reconciliation Draft #433.

Base: exact main@0bdc82583417616ccd4a2ef52a9005bcc18eb660, after independent isolated DRI-repair client evidence #432 was archived by #434.
Source reconciliation: #433@cb4a9283cd8c2ad8bcbb584f631619a9255c2ce0.

The source code is replayed from GitHub's conflict-free merge tree against the new main, so the admission validator is unchanged from the independently validated #433 code. Only the canonical-runtime task checkpoint is refreshed to this branch/base and now consumes the newer archived physical fact: the DRI repair restores GLX and removes the prior allowlisted QXcb no-GLX/EGL failure signature, but the exact client remains alive with zero visible windows through 35 seconds.

Therefore this PR does two bounded things:

1. fixes the stale pre-feat(track-a): repair canonical bootstrap transition #371 unconditional bootstrap rejection so a future separately authorized one-attempt invocation of the already-promoted feat(track-a): repair canonical bootstrap transition #371/docs(track-a): archive canonical bootstrap implementation #375 fail-closed transaction can be represented correctly;
2. explicitly preserves blind_canonical_bootstrap_retry_forbidden:true because diag(track-a): revalidate DRI repair in isolated client startup #431/docs(track-a): promote isolated DRI repair client revalidation #432/docs(track-a): archive isolated DRI repair client revalidation #434 prove the visible-window prerequisite is still unsatisfied after GLX restoration.

This PR is GitHub-hosted only (runtime_access:none, mutation_authorized:false). No Synology, canonical lease/registration/session, official client, credentials/login/gameplay, Track B or #303 runtime surface is touched.

Source #433 independent validator 31970995035 / job 95223324421 = SUCCESS. Source final governance and both pre-ready/ready required CI generations were green; merge was refused only because strict required-status policy observed main advance through #432/#434. This replacement must obtain fresh exact-current-main governance/CI before merge.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.