docs: replace fictional ^1.0.0 peer ranges + drop changeset reference

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>

Author: Goosterhof

CONTRIBUTING.md

@@ -13,5 +13,6 @@ npm run test:coverage # Run tests with 100% coverage threshold
 npm run test:mutation # Run mutation testing with 90% threshold
 npm run format        # Format with oxfmt
 npm run lint          # Lint with oxlint
-npx changeset         # Create a changeset for your changes
+# To release: bump the affected package's `version` in its package.json and merge to main
+# (push to main with a **/package.json change triggers OIDC Trusted Publishing — no changeset bot)
 ```

docs/architecture.md

@@ -81,7 +81,7 @@ When packages do depend on each other (like `fs-loading` using `fs-http`'s middl
 
 ```json
 // fs-loading's package.json
-{"peerDependencies": {"@script-development/fs-http": "^1.0.0", "vue": "^3.5.0"}}
+{"peerDependencies": {"@script-development/fs-http": "^0.1.0 || ^0.2.0 || ^0.3.0", "vue": "^3.5.33"}}
 ```
 
 ## Middleware Architecture

docs/packages/adapter-store.md

@@ -6,7 +6,7 @@ Reactive state management with CRUD resource adapters.
 npm install @script-development/fs-adapter-store
 ```
 
-**Peer dependencies:** `vue ^3.5.0`, `@script-development/fs-http ^1.0.0`, `@script-development/fs-storage ^1.0.0`, `@script-development/fs-loading ^1.0.0`, `@script-development/fs-helpers ^1.0.0`
+**Peer dependencies:** `vue ^3.5.33`, `@script-development/fs-http ^0.1.0 || ^0.2.0 || ^0.3.0`, `@script-development/fs-storage ^0.1.0`, `@script-development/fs-loading ^0.1.0`, `@script-development/fs-helpers ^0.1.0`
 
 ## What It Does
 

docs/packages/loading.md

@@ -6,7 +6,7 @@ Reactive loading state service with counter-based tracking and HTTP middleware i
 npm install @script-development/fs-loading
 ```
 
-**Peer dependencies:** `vue ^3.5.0`, `@script-development/fs-http ^1.0.0`
+**Peer dependencies:** `vue ^3.5.33`, `@script-development/fs-http ^0.1.0 || ^0.2.0 || ^0.3.0`
 
 ## What It Does