fix: host authenticated gateways on protected Spaces

[osolmaz]

Private Hugging Face Spaces put an identity-aware edge in front of the app. The scripts-only approval sandbox cannot reliably send that edge cookie, so delegated approval requests fail before reaching MLClaw.

What changed

• Create and converge hosted gateways to protected Space visibility by default: source remains private while the app URL reaches MLClaw authentication.
• Preserve public visibility only when --public-space is explicitly requested.
• Detect visibility through the official paginated repository-settings API for users and organizations.
• Teach doctor --fix to repair hosted visibility.
• Remove credentialed CORS from delegated approval responses.
• Update the runtime to MLClaw 0.4.7 and openclaw-brokerkit 0.3.3.

Testing

• npm run check on Node 24.18.0
• 317 tests passed, 2 fixture-dependent tests skipped
• 97.92% statement/line coverage and 92.96% branch coverage
• Slophammer DRY and full gates passed
• Focused organization pagination regression passed
• Live read-only Hugging Face settings query confirmed GoePT is currently reported as private

Risks

Protected Spaces require a Hugging Face plan that supports protected visibility. The app edge becomes reachable, but MLClaw still requires its signed OAuth session for gateway/control pages and a signed, short-lived BrokerKit session plus exact opaque origin for delegated approval APIs.