Brief: P7 edge-door plan, review round 6 (confirming)

Rounds 1–5 are the CODEX-FINDINGS-P7-EDGE-DOOR*.md files beside the plan. The plan is now revision 6.

Rounds 4 and 5 showed that every invented visitor address (unknown, then 192.0.0.8) meets some framework that reads it as local, private or trusted. So revision 6 invents nothing. A door request carries the box's own public address, the one its edges file publishes, and is claimed to be exactly equivalent to a request from a process on the box to the instance's public URL.

1. Disposition table for round 5's two findings: closed / partly / not closed.
2. Test the equivalence claim. Find any observable difference, to the app, the gate, analytics, the cache, or the far edge of a backhaul, between a door request and a public HTTPS request from the same box to the same URL. Include headers the edge adds or strips on each path. Say which differences confer anything.
3. New findings only where they are P1 or P2.

Only the code in this checkout exists; Tasks 1 and 3 are built and Task 2 is being built, so read the plan for the rest. Check every path:line you cite. End with one line saying whether the plan is ready to build. Keep it under about 800 words.