docs(docs): close BS-UPG-110 staging qualification

[BakerSean168]

Summary

• mark BS-UPG-110 canonical staging qualification CLOSED
• record the qualified exact SHA 1484604e28ed6a792d7b2c2e661049f9cfdb708d
• preserve explicit evidence for all 11 staging acceptance checks
• record PRs fix(ops): harden staging requalification gates #229-fix(ai): pin Treatment to tool output transport #234 and the final Treatment ToolOutput transport repair
• state explicitly that BS-UPG-120 / production was not started

Why this PR is intentionally draft / unmerged

Repository delivery semantics publish a new exact-SHA candidate after every successful main push, including docs-only pushes. Merging this administrative closeout immediately would manufacture a new staging SHA after the already-qualified candidate and create a qualification/documentation loop. Keeping this closeout as a draft preserves main and canonical staging on the exact candidate that passed BS-UPG-110.

Merge this administrative record only together with the next intentionally qualified/released main transition, or after the production release boundary is explicitly opened.

Qualified staging evidence

• main push CI: 36836256480 PASS
• Publish Main Candidate: 36837085439 PASS
• canonical staging deploy: STAGING_DEPLOY=PASS at 1484604e28ed6a792d7b2c2e661049f9cfdb708d
• final live registration/profile/consultation/Diagnosis/Treatment proposal: PASS in 22.5s
• exact-SHA OCR qualification: PASS
• exact-SHA 3D/CDN/console gate: 2/2 PASS in 4.6m
• infrastructure-image rollback drill: PASS with managed revision unchanged

Production boundary

No production deploy, release promotion, or BS-UPG-120 execution is part of this PR.