feat: rebrand site content from Ordane to RoleWeave

[Bindy-lbb]

Tracking record

Closes #6

Summary

Rebrands the site from Ordane/org-workbench to RoleWeave
(bytefolk/roleweave, v0.1.1). Every product claim on the page is now
sourced from that repository's README and the v0.1.1 release notes:

• Brand: the nav badge and favicon are now the RoleWeave mark
  (branding/roleweave/roleweave-icon.svg, inlined). The --teal palette
  is replaced by --brand (violet #722ed1) / --azure (blue #1677ff),
  both converted to OKLCH so the existing contrast-audit method applies
  unchanged.
• Copy: #concept now explains "file tree is the org chart" with the
  actual examples/oss-maintainer directory layout instead of the line
  primitive; #principles mirrors the README's three daily-use flows and
  an updated Shipped/Building capability list; #runtime describes the
  Qoder-CLI-based default adapter and its actual verification status
  (macOS field-verified, Claude Code not yet in the verified baseline);
  #ladder becomes a download section with the real v0.1.1 assets
  (macOS arm64 DMG, Windows x64 EXE) plus a five-step get-started list
  lifted from the README.
• Download UX (added after the initial rebrand pass, per follow-up
  request): the nav/hero/CTA download buttons now open a hover/click
  dropdown listing the actual release assets, so picking one downloads it
  directly instead of routing through the releases page. Built as
  <details> so it still works with JavaScript disabled; the script only
  adds hover-to-open, Escape/outside-click dismissal, and a "this device"
  hint from navigator.userAgentData/platform (fails safe to no hint —
  wrapped in try/catch, and specifically avoids telling an Intel Mac the
  arm64-only DMG is theirs).
• Two corrections where a literal port of Ordane's tone would have
  overstated what roleweave documents: the footer's "local-first, no
  data leaves" became "workspace files stored locally · prompts still go
  to your configured AI provider" (README: local storage ≠ offline AI),
  and a download-card "field-verified" badge became "auto-update
  available" (README does not claim install/uninstall/auto-update
  verified end to end).

The hero keeps the same real, unretouched client screenshot as before;
its window title still reads the pre-rename org-workbench, called out
honestly in the caption rather than passed off as a current build.

Out of scope, intentionally: renaming the bytefolk/ordane repository or
moving off the bytefolk.github.io/ordane/ Pages URL (tracked
separately, not part of #6); any backend, analytics, or custom domain.

Verification

CI (verify) must be green. It runs, on every push:

• npm run verify:contrast — every text/background pair the page renders,
  both themes, against the WCAG thresholds. 48/48 passing (46 carried over
  from the palette rename plus 2 new pairs: the azure hero accent and the
  download-menu hover state).
• npm run verify:render — renders the page, screenshots hero/#runtime/
  #ladder, asserts all .reveal blocks trigger and the principles tab
  switches, fails closed on page errors. REVEALS=9/9, PAGE_ERRORS=none.
• fail-close guard — confirmed still exits non-zero on injected errors.

Additionally, since this PR also adds interactive behavior CI doesn't
cover: a throwaway Playwright script exercised the download dropdown
directly — hover-open, mouseenter/mouseleave across the button-to-menu
gap, Enter-to-open/Escape-to-close, outside-click dismissal, close-on-pick,
and the "this device" hint under four spoofed navigator.platform/UA
combinations (Windows → EXE hint, macOS → DMG hint, Linux/iPhone → no
hint). All passed; screenshots at 1440 and 390px, both themes, with the
menu open, showed no layout overflow. (This script is not part of the
diff — it was a local verification aid, not product code.)

• Checked at phone width as well as desktop
• Checked in both light and dark mode

Factual accuracy

• "File tree is the org chart" / roles live in folders — Shipped:
  roleweave README, "How workspaces work".

• Role budgets (budget.json), org tree, per-role chat, local history —
  Shipped: README capability list and examples/oss-maintainer.

• Reporting center (activity, org changes, turn outcomes, budget usage) —
  Shipped: README, "What you can do".

• Local HTTP service on 127.0.0.1, per-launch Bearer token except
  GET /health — Shipped: README, "For AI assistants and integrations".

• Windows auto-update, bounded context / independent dispatch / parallel
  groups, Claude Code live execution — Building/not yet verified: README's
  "Current limits" and the explicit "not part of the v0.1.1 installers"
  callout.

• v0.1.1 download assets and platform coverage (no Linux/Intel Mac) —
  Shipped: gh release view against bytefolk/roleweave v0.1.1.

• No capability is described as shipped unless a linked repo says so

• No pricing, invented metrics, or customer names

• Screenshots contain example-workspace data only

Risk and rollback

Low — page-only change, no backend, no user data. Rollback is reverting
this PR's merge commit.

Author checklist

• A maintainer confirmed the linked issue was ready before
  implementation began (Rebrand site content from Ordane to RoleWeave #6, opened alongside this PR).
• This branch was created from an up-to-date default branch and
  contains no unrelated changes.
• I ran the repository's applicable checks (npm run verify; see
  Verification above).
• I updated relevant documentation and changelog files (README.md,
  CHANGELOG.md).
• I reviewed the diff for secrets, personal data, generated artifacts,
  and dependency risk. Eight files changed (site, scripts, manifests,
  docs); no secrets, no personal data; the embedded screenshot is the
  same previously-reviewed example-workspace image, unchanged.
• The PR is ready for CI and review by someone other than the sole
  author.
• All reported results are reproducible (npm run verify locally;
  CI will confirm).

Reviewer notes

Please specifically check: (1) the new copy against bytefolk/roleweave's
README/release notes for anything I over- or under-claimed, (2) the
"this device" download hint's platform detection — it's decoration, not
load-bearing, but a wrong hint would be a bad look, (3) the
z-index fix on .hero-inner (2 instead of 1) — it's the only structural
CSS change outside the palette/copy swap and the download dropdown itself.

[Bindy-lbb]

Merge note: admin override of the independent-review requirement

CI (verify) is green. This repository has one active maintainer and no
second reviewer available right now, so the branch protection's required
approving review (1) could not be satisfied through the normal flow —
GitHub does not let the PR author approve their own pull request, and
GOVERNANCE.md
is explicit that the absence of a second reviewer is a staffing blocker,
not permission to self-approve.

@Bindy-lbb, the repository owner and sole author of this PR, explicitly
authorized merging via admin override (enforce_admins: false) rather than
waiting for a second reviewer, given the low-risk, page-only, already
CI-verified nature of this change. Recorded here per GOVERNANCE.md's
"documented rationale" expectation for decisions made without full
consensus/process. Follow-up: get a second maintainer or org-owner review
in place for future changes to this repository, per the governance
baseline's single-maintainer guidance.