Initial docs portal for docs.byteveda.org

[pratyush618]

Summary

• Scaffolds a Next.js 16 static-export site at docs.byteveda.org that mirrors the byteveda.org landing's brand (same Geist fonts, zinc + accent palette, ui/ primitives, dark mode default)
• Portal is a single page that lists the 5 tools and links into per-tool docs at docs.byteveda.org/<slug>/ — GitHub org + project Pages routing handles the subpath resolution automatically
• Deploys to GitHub Pages via deploy.yml (replaces the old hand-written index.html placeholder, now archived under archive/legacy-index.html)
• CNAME moved into public/ so it's bundled in the static export output
• scripts/sync-ui.sh pulls shared primitives (Button, Badge, Section, Wordmark, TerminalChip, ExternalLink, icons, cn, theme, footer) from the sibling byteveda.site repo — one-command sync keeps the two sites visually identical
• CI parity with the landing repo: Biome lint, tsc typecheck, Next.js build, CodeQL, dependency review, Dependabot

Commits

1. chore: scaffold next.js portal with biome
2. chore: archive legacy placeholder
3. chore: move CNAME into public for static export
4. feat: add site config, tools, and utilities
5. feat: set up theme tokens and root layout
6. feat: add ui primitives
7. feat: build docs portal sections
8. chore: add sync-ui script for shared primitives
9. chore: add favicon from byteveda org avatar
10. ci: add pages deploy workflow
11. ci: add lint, typecheck, and build workflow
12. ci: add codeql and dependency review
13. chore: add dependabot config

Test plan

• pnpm install && pnpm build — static export to out/ succeeds
• pnpm exec biome check — clean
• out/CNAME contains docs.byteveda.org
• Side-by-side visual parity with byteveda.org: colors, fonts, navbar, footer, theme toggle
• pnpm sync-ui round-trips cleanly from a sibling byteveda.site checkout
• After merge: Settings → Pages → Source = GitHub Actions; confirm docs.byteveda.org custom domain; deploy workflow runs green
• docs.byteveda.org/<tool>/ correctly resolves to each tool repo's project Pages (relies on existing per-tool docs.yml workflows)

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.