User justinsforge no public site

Justin stated clearly: "I don't want justinsforge to have a front-facing website." This came up when evaluating whether to use justinsforge.com as the homepage URL for Google OAuth brand verification.

When Google OAuth verification or any other task requires a public URL, do NOT use justinsforge.com as the destination. Alternative options discussed: a /forge or /app sub-path on justinwieb.com (Workspace domain), a cheap separate domain (e.g. forge-personal.com), or a GitHub Pages URL.

Why: justinsforge.com is Justin's internal command center and second-brain surface. It is Cloudflare Access-gated by design. Exposing it publicly would conflict with its security posture and its nature as a private operational hub.

How to apply: Any time a task requires a publicly accessible URL (verification submissions, OAuth consent screen, third-party integrations), never suggest justinsforge.com as the homepage. Suggest justinwieb.com sub-path or a dedicated landing domain instead.

[auto-memory session 1a660aac-56d2-400d-8206-c59564bbff19, confidence 0.88, mode direct]