Host the marketing site at bytefolk.github.io/roleweave/ via a gh-pages branch #228

Problem

The RoleWeave marketing site currently lives in a separate repository,
bytefolk/ordane, and is served at https://bytefolk.github.io/ordane/.
That name is left over from the product's pre-rename identity and no
longer matches this repository's name or the product's current name.

bytefolk/roleweave is this name already, so bytefolk/ordane cannot
simply be renamed to roleweave (GitHub does not allow two repositories
with the same name in one organization). To serve the site at
https://bytefolk.github.io/roleweave/, the Pages-hosting repository must
literally be this one.

Proposal

• Add an orphan gh-pages branch to this repository, unrelated to main's
  history, containing only the static site (index.html, no build step,
  contrast/render verification scripts, README/CHANGELOG scoped to the
  site). This mirrors how the content already looked in bytefolk/ordane
  (rebranded there in ordane#7,
  already CI-verified and merged) — this migrates that content, unchanged
  in substance, to its new home.
• Configure GitHub Pages (Settings → Pages) to build from gh-pages /
  root, giving https://bytefolk.github.io/roleweave/.
• bytefolk/ordane is out of scope for this issue: whether to archive it,
  add a redirect notice, or leave it live is a separate decision (it
  requires an organization owner per GOVERNANCE.md's repository-lifecycle
  rule, which this account does not hold).

Why an orphan branch instead of main

main here is the product's application source (apps/, packages/,
its own package.json/workspace config). Mixing a no-build-step static
site into that tree risks colliding with the workspace's own tooling and
scope-creeps this repo's main history with unrelated commits. A gh-pages
branch is the conventional GitHub Pages deployment target: independent
history, independent review surface, zero risk to apps//packages/ CI.

Acceptance criteria

• https://bytefolk.github.io/roleweave/ serves the rebranded RoleWeave
  site (same content verified in bytefolk/ordane PR fix(examples): point oss-maintainer localReference paths at the macOS prefix #7).
• No file under apps/, packages/, or the root workspace config changes.
• bytefolk/ordane's current live site is left untouched pending its own
  decommission decision.