Evaluate moving the portfolio from GitHub Pages hostname to a custom domain

Context

docs/SYSTEM_STATE.md lists the GitHub Pages origin (mantoshkumar1.github.io) rather than a custom domain as a known limitation. The site’s stated commercial objective is credible conversion for Staff/Principal engineering opportunities and contracts.

Goal

Make an evidence-based decision on whether a custom domain materially improves professional positioning enough to justify the operational change.

Scope

• Compare keeping the current GitHub Pages hostname versus using a stable personal domain.
• Evaluate SEO/canonical migration, redirects, HTTPS, email/contact consistency, and GitHub Pages configuration.
• Identify any Ask Mantosh CORS/origin and Worker configuration changes required.
• Preserve existing URLs where possible and avoid breaking indexed links.
• Do not migrate solely for aesthetics; document the decision either way.

Acceptance criteria

• A clear keep/migrate decision is documented with rationale.
• If migrating, DNS, HTTPS, canonical, sitemap, social metadata, and redirect impacts are covered.
• Ask Mantosh exact-origin/CORS configuration is updated safely before cutover.
• Existing public links continue to resolve or redirect appropriately.
• Production smoke checks verify the chosen hostname after the change.

Start by reading docs/SYSTEM_STATE.md and verify the current GitHub Pages hostname, then inspect the existing site, Ask Mantosh origin/CORS, Worker, and deployment configuration. Compare the current hostname with a custom-domain option, documenting SEO, redirects, HTTPS, email, and public-link impacts. Done means a clear keep/migrate decision, configuration changes if needed, and production smoke checks for the chosen hostname.