Skip to content
Colour intensity

Initial setup review

Reviewed the Copilot foundation at commit 80df4cba2ebbcbf3512cd023948f400ab702ddba on 30 September 2026.

Kept

  • npm workspaces for the website and shared packages, with Python-only MkDocs isolated in /docs.
  • Chakra v3 with Emotion for the main application, and a separate Ark UI/Panda alternative.
  • Canonical brand tokens, explicit Vivid/Muted selection and shared agent instructions.
  • Independent CI checks for website, documentation and the optional Worker.

Corrected

  • Imported 260 original logo, icon, font, licence and colour-reference files from the supplied v1.1 archive. Recorded archive and individual SHA-256 hashes; preserved the approval status of revised guidance.
  • Added self-hosted font faces and Chakra font tokens. Material navigation and content now use Lexend, headings use Arvo Bold, and code uses Hack.
  • Added real Vivid/Muted logo artwork, browser icons and Apple touch icons. PNG fallbacks accompany WebP logos.
  • Made both asset pipelines include icons and reject missing or modified sources. Builds no longer mutate the tracked provenance manifest. Generated app asset copies are ignored by Git.
  • Adapted brand heading units to Material's different root font scale without changing its navigation/layout scale.
  • Added domain-aware MkDocs metadata, consistent Cloudflare resource names and deployment instructions. Verified Pages v3 version controls: use an explicit pinned npm command and disable automatic dependency installation to avoid duplicate installs. Both Pages projects and custom domains were subsequently deployed; see Deployment for the verified status.
  • Kept the documentation's repository link without Material's automatic public GitHub statistics requests, which return 404 for this private repository. This issue was caught by the browser check in GitHub Actions.
  • Moved long setup/deployment/agent explanations from the root README into MkDocs. Kept a short root entry point and the agent adapters in their required locations.
  • Removed duplicate frontend type-check execution from validate:web; the production build already invokes TypeScript. Added a focused browser integration check for branding.

Validation boundaries

Run the commands on Agents and validation for the current revision. CI results are attached to the corresponding GitHub pull request and commit. Local browser checks do not prove a Cloudflare deployment is live. Manual assistive-technology testing and Nathan's acceptance of the revised v1.1 guidance remain distinct from technical build checks.