Skip to content

docs: peer-range and changeset drift cleanup — closes deferred item#76

Merged
jasperboerhof merged 2 commits into
mainfrom
engineer/docs-peer-range-and-changeset-drift-cleanup
May 12, 2026
Merged

docs: peer-range and changeset drift cleanup — closes deferred item#76
jasperboerhof merged 2 commits into
mainfrom
engineer/docs-peer-range-and-changeset-drift-cleanup

Conversation

@Goosterhof
Copy link
Copy Markdown
Contributor

Summary

Closes deferred entry fs-packages-docs-peer-range-and-changeset-drift-cleanup — path (b), the fast tactical fix. Path (a) (Armorer Level-1/2 build-time enforcement gate) remains queued for after this Engineer pass plus Warden M2 detonations land.

Four mechanical drift fixes surfaced by Engineer Order #2 (PR #73, docs/contributing.md rewrite) and previously catalogued by Adjutant M2:

  • docs/packages/adapter-store.md:9vue ^3.5.0^3.5.33; four ^1.0.0 fs-* peer claims → actual ranges from packages/adapter-store/package.json#peerDependencies (fs-http ^0.1.0 || ^0.2.0 || ^0.3.0; fs-helpers / fs-loading / fs-storage ^0.1.0).
  • docs/packages/loading.md:9 — same shape: matches packages/loading/package.json#peerDependencies verbatim (vue ^3.5.33; fs-http ^0.1.0 || ^0.2.0 || ^0.3.0).
  • docs/architecture.md:84 — fs-loading peer-deps code block now matches packages/loading/package.json source-of-truth.
  • CONTRIBUTING.md:17 — drop npx changeset quick-reference. No changeset bot exists; release path is **/package.json push to main triggering OIDC Trusted Publishing. Replacement wording aligned with docs/contributing.md Publishing section as merged in PR docs(contributing): rewrite Publishing + fix Node prereq + fs-http peer-range example #73.

Verification

  • npm run format:check clean (133 files)
  • npm run lint clean (0/0)
  • npm run build clean (all 10 packages)
  • npm run typecheck clean
  • npm run docs:build — VitePress SSR completes (4.93s), no errors
  • Rendered HTML at docs/.vitepress/dist/packages/{adapter-store,loading}.html and docs/.vitepress/dist/architecture.html shows the new peer-range strings with backticks rendered correctly.

Out of scope (filed for follow-up, not fixed here)

While verifying drift instances, found additional vue ^3.5.0 claims on five docs pages outside the order's named scope: docs/packages/translation.md:9, docs/packages/dialog.md:9, docs/packages/toast.md:9, docs/packages/theme.md:9, docs/packages/router.md:9 (also docs/packages/router.md:9 carries vue-router ^4.5.0 — actual ^5.0.6). Order discipline: not fixed on this PR; surfaced in execution report. Aligns with the Warden M2 README/docs duplication standing concern that Path (a) Armorer enforcement is queued to address.

Test plan

  • Local format:check / lint / build / typecheck / docs:build all green
  • CI 8-gate green
  • Visual review of rendered docs site (Cloudflare Pages preview)
  • Commander review and merge

🤖 Generated with Claude Code

@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages Bot commented May 8, 2026

Deploying fs-packages with  Cloudflare Pages  Cloudflare Pages

Latest commit: b712895
Status: ✅  Deploy successful!
Preview URL: https://6d6f6897.fs-packages.pages.dev
Branch Preview URL: https://engineer-docs-peer-range-and.fs-packages.pages.dev

View logs

Four mechanical drift fixes closing deferred item
`fs-packages-docs-peer-range-and-changeset-drift-cleanup`:

- docs/packages/adapter-store.md:9 — peer line now matches
  packages/adapter-store/package.json#peerDependencies verbatim
  (vue ^3.5.33; fs-http ^0.1.0 || ^0.2.0 || ^0.3.0;
  fs-storage / fs-loading / fs-helpers ^0.1.0).
- docs/packages/loading.md:9 — peer line now matches
  packages/loading/package.json#peerDependencies verbatim
  (vue ^3.5.33; fs-http ^0.1.0 || ^0.2.0 || ^0.3.0).
- docs/architecture.md:84 — fs-loading peer-deps code block now
  matches packages/loading/package.json source-of-truth.
- CONTRIBUTING.md:17 — drop `npx changeset` quick-reference (no
  changeset bot exists; release path is `**/package.json` push to
  main triggering OIDC Trusted Publishing) per the post-PR-#73
  Publishing wording in docs/contributing.md.

Path (b) of the deferred entry — the fast tactical fix. Path (a)
(Armorer Level-1/2 enforcement gate) remains queued.

Verification: format:check / lint / typecheck / docs:build all pass
locally; rendered HTML at docs/.vitepress/dist/packages/{adapter-store,
loading}.html and docs/.vitepress/dist/architecture.html shows the
new peer-range strings with backticks rendered correctly.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@Goosterhof Goosterhof force-pushed the engineer/docs-peer-range-and-changeset-drift-cleanup branch from 617aaf6 to 3b06b33 Compare May 8, 2026 10:47
@jasperboerhof jasperboerhof merged commit 08b749c into main May 12, 2026
2 checks passed
@jasperboerhof jasperboerhof deleted the engineer/docs-peer-range-and-changeset-drift-cleanup branch May 12, 2026 17:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants