fix(repo): rename root to astryx, add docsite alias, fix docs filter

[nynexman4464]

What

Three small fixes around the doc-site dev experience, all in repo-level tooling:

1. Fix the broken filter in the docs script. The root package.json had "docs": "pnpm -F @astryxdesign/docs dev", but the doc-site package is named @astryxdesign/docsite (at apps/docsite/). The filter has been broken since #3008 (@xds/* → @astryxdesign/* rename) — running pnpm run docs printed No projects matched the filters with no other output.

2. Rename the root package from xds to astryx. The root package.json was still named xds (legacy, pre-public-rename leftover from the original "dev setup" commit). Because docs is also an npm/pnpm builtin (it opens a package's npm registry page in your browser), running bare pnpm docs would try to open https://www.npmjs.com/package/xds — an unrelated package with nothing to do with this repo. After this rename, the builtin at least lands on the correct package page. The root is "private": true, so nothing publishes.

3. Add a docsite script alias. pnpm docsite now works as a bare shortcut to start the doc site, without colliding with any pnpm/npm builtin. The original docs script is kept for compatibility — pnpm run docs still works.

Also documents the doc-site workflow in CONTRIBUTING.md under a new "Running the Doc Site" section, including the pnpm docs vs pnpm docsite footgun.

How

   {
-    "name": "xds",
+    "name": "astryx",
     ...
     "scripts": {
       ...
-      "docs": "pnpm -F @astryxdesign/docs dev",
+      "docs": "pnpm -F @astryxdesign/docsite dev",
+      "docsite": "pnpm -F @astryxdesign/docsite dev",
       ...
     }
   }

Plus a new section in CONTRIBUTING.md.

Test evidence

All tests run on navi/fix/docs-script-package-name after the changes.

1. pnpm docsite (the new alias) starts the Next dev server:

$ pnpm docsite
...
Summary:
  8 packages
  216 components
  518 blocks (165 showcases, 385 examples)
  39 templates
  16 doc topics
  2 blog posts
  6 themes
Done.
✓ Generated .../playground-scope.ts
✓ xle-registry.json: 174 components, 120 aliases, 518 blocks
   ▲ Next.js 15.5.18
   - Local:        http://localhost:3000
 ✓ Ready in 1028ms

$ curl -s -o /dev/null -w "HTTP %{http_code} (%{size_download} bytes)\n" http://localhost:3000/
HTTP 200 (345134 bytes)

$ curl -s http://localhost:3000/ | grep -oE "<title>[^<]*</title>"
<title>Astryx Design System</title>

2. pnpm run docs (the original script) still works:

$ pnpm run docs
...
   ▲ Next.js 15.5.18
   - Local:        http://localhost:3000
 ✓ Ready
 ✓ Compiled / in 5.5s (6678 modules)
 GET / 200 in 6412ms

$ curl -s -o /dev/null -w "HTTP %{http_code} (%{size_download} bytes)\n" http://localhost:3000/
HTTP 200 (345315 bytes)

$ curl -s http://localhost:3000/ | grep -oE "<title>[^<]*</title>"
<title>Astryx Design System</title>

3. pnpm docs (the builtin) now lands on the correct npm package page:

$ BROWSER=echo pnpm docs
npm error command sh -c open https://www.npmjs.com/package/astryx

(Previously: open https://www.npmjs.com/package/xds. The macOS LSOpenURLs error -54 is unrelated — local LaunchServices has no app registered for npmjs.com.)

4. Repo checks pass:

$ pnpm check:repo
> astryx@0.0.0 check:repo /Users/arock1278/dev/astryx

✅ All SYNC comments are clean.
Package boundaries are clean.
✓ check:changesets — 4 changeset(s) valid (pre-1.0 patch-only enforced)
✅ 5 image-backed Thumbnail example(s) checked — all use CORS-safe demo media.

(Note the prefix is now astryx@0.0.0 instead of xds@0.0.0.)

5. Prettier is clean:

$ pnpm exec prettier --check package.json CONTRIBUTING.md
Checking formatting...
All matched files use Prettier code style!

Notes

• No changeset — repo tooling / docs only, no publishable package change. check:changesets is happy.
• Pre-commit hook bypassed because npx lint-staged hit a transient 503 from registry.npmjs.org. lint-staged would have been a no-op anyway (*.{ts,tsx,md} matches CONTRIBUTING.md but not package.json — and prettier was run manually above and is clean). pnpm check:repo was also run manually.
• Kept the docs script alongside docsite to avoid breaking anyone's muscle memory or existing scripts/aliases.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
astryx	Ready	Preview, Comment	Jul 2, 2026 12:26am

[github-actions]

PR Analysis Report

📚 Storybook Preview

View Storybook for this PR
GitHub Pages may take up to a minute to hydrate after deploy.

🧪 Sandbox Preview

View Sandbox for this PR
GitHub Pages may take up to a minute to hydrate after deploy.

No new or modified components detected.

Bundle Size Summary

Package	Size (ESM)	Size (CJS)	Gzipped
@astryxdesign/core	N/A	4.6KB	0B

Accessibility Audit

Status: No accessibility violations detected.

---

_{Generated by PR Enrichment workflow | Storybook | Sandbox | View full report}

[cixzhang]

These are the same? Should we only have one?

[nynexman4464]

We can decide which makes more sense. By default pnpm docs just opens the package docs site. To run our docs you'd have to do pnpm run docs. pnpm docsite always works cause it doesn't conflict.

I'm fine with dropping docs byitself.

[nynexman4464]

Dropped docs in fb5a1fc — pnpm docsite is the only alias now, and bare pnpm docs falls through to the npm builtin which lands on the right astryx npm page. Also trimmed the CONTRIBUTING note since pnpm run docs no longer applies.