carlos / platform Public

Merge main into the scanning branch, and count the doors again

`main` moved 31 commits while this branch was being split and reviewed.
One conflict, in the one place designed to have it: `closedDoors`.

Both sides had added shut doors since the merge base — main two (the
build probe, the fleet-wide live tenancy read), this branch two (the
deployment-wide antivirus pair) — and both sides had bumped the same
literal from 17 to 19. Git took that identical edit silently, because
textually it was not a conflict at all: two people writing `19` agree.

They did not agree. The list holds 21. Had the merge been committed as
git resolved it, `TestEveryClosedDoorRefusesAServiceCredential` would
have failed on `seen != 21` — which is the outcome the redundant literal
is there to produce, and the reason it is written as a second assertion
beside `len(closedDoors)` rather than derived from it. A door added by
somebody who is not looking at your branch cannot slip in unremarked.

Resolved to 21, with the message naming all four of the newcomers.

Whole tree green.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExnZtUYmt2h8QFcymjPaSL