feat: domain registration and GitHub Pages for verify page (HITL)

[gkanitz]

What to build

Register the canonical domain for the CodeRepute verify page and publish it via GitHub Pages. This makes QR codes on printed PDFs resolve to a stable, professional URL independent of the GitHub username.

Steps (all require owner account access):

1. Register `coderepute.dev` (~$12/yr) — primary domain for the verify page
2. Register `coderepute.com` (~$12/yr) — redirect to `coderepute.dev`
3. Enable GitHub Pages on this repository (Settings → Pages → Branch: main, folder: /docs)
4. Add a `CNAME` file to the `docs/` directory containing `coderepute.dev`
5. Configure DNS: point `coderepute.dev` A records at GitHub Pages IPs and add a CNAME for `www`
6. In GitHub Pages settings, set the custom domain to `coderepute.dev` and enable "Enforce HTTPS"
7. Configure `coderepute.com` to redirect to `coderepute.dev` at the registrar level

Once live, `https://coderepute.dev/verify/\` should serve `docs/verify/index.html`.

After this slice is merged, update the domain constant in the report package from `grkanitz.github.io/CodeRepute/verify/` to `coderepute.dev/verify/`.

Acceptance criteria

• `https://coderepute.dev/verify/\` serves the verify page over HTTPS
• `https://coderepute.com\` redirects to `https://coderepute.dev\`
• `CNAME` file present in `docs/`
• Domain constant in the report package updated to `https://coderepute.dev/verify/\`

Blocked by

None — can start immediately in parallel with other slices.

[gkanitz]

Status: docs/CNAME (coderepute.dev) and the Pages setup are in the repo; registrar-level state (coderepute.com redirect, HTTPS enforcement, DNS) is unconfirmed. #57 (Launch readiness) carries the live-surface checklist — either confirm the .com redirect there or explicitly descope it here. Close this issue when #57's domain boxes are ticked and the report-package URL constant points at https://coderepute.dev/verify/.