Fix GitHub Pages 404 by publishing domain/routing metadata from static/

[Copilot]

The site was intermittently serving 404s on the custom domain because Pages-only deployment metadata was not included in the published artifact. This change aligns domain/routing metadata with the actual GitHub Pages publish root.

• Deployment artifact alignment

  • Added static/CNAME with vlostudios.dev so custom-domain mapping is part of the deployed site.
  • Added static/.nojekyll to ensure Pages serves static paths without Jekyll processing side effects.

• Resulting behavior

  • Pages now receives domain and no-Jekyll markers from the same directory configured as publish_dir (static/), preventing missing-file deploys that can surface as 404s.

static/
├── CNAME        # vlostudios.dev
├── .nojekyll
└── index.html

[Copilot]

🟢 Approval recommended

The reviewed changes are complete with no unresolved blocking issues.

Pull request overview

Aligns GitHub Pages metadata with the static/ publish directory to fix custom-domain routing and static-path 404s.

Changes:

• Adds static/CNAME for vlostudios.dev.
• Adds static/.nojekyll to disable Jekyll processing.

File summaries

File	Description
static/CNAME	Configures the custom domain.
static/.nojekyll	Preserves static-path serving behavior.

Review details

• Files reviewed: 1/2 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.