chore: update

Author: antfu

docs/content/1.guide/10.standalone-cli.md

@@ -185,11 +185,6 @@ defineDevframe({
 ```
 
 Booleans become `--verbose` / `--no-verbose`, else `--depth <value>`; keys are camelCase in TS, kebab-case on the CLI (`configFile` → `--config-file`). Flags outside the schema pass through.
-
-## Common RPC functions
-
-Recipes for opening files in the editor or OS explorer live in `devframe/recipes/common-rpc-functions` ([Common RPC Functions](/references/common-rpc-functions)).
-
 ## Snapshot queries for static builds
 
 For an RPC function returning one payload per build, set `snapshot: true`; the build adapter runs the handler once, baking the result in:

docs/content/1.guide/19.services.md

@@ -7,7 +7,7 @@ description: 'ctx.services lets one devframe expose a typed, namespaced capabili
 
 `ctx.services` lets one devframe expose a typed, namespaced capability visible to every devframe. Two tiers: in-process services (`provide`/`get`) share live objects between devframes; [wire services](#wire-services) also register RPC and advertise to RPC clients.
 
-The [Services reference](/references/services) collects the host methods, the definition/descriptor fields, and the built-in services as lookup tables.
+The [Node-Side API reference](/references/node-api#devframeserviceshost) collects the host methods and the definition/descriptor fields as lookup tables.
 
 ## Providing a service
 

docs/content/5.add-ons/2.services/1.open.md

@@ -5,7 +5,7 @@ navigation:
 description: 'The @devframes/service-open wire service: open files in an editor or reveal them in the OS explorer over RPC, with workspace-root path containment and editor gating.'
 ---
 
-Open files in an editor or reveal them in the OS explorer, shared over RPC by every devframe on the host. Replaces per-devframe registration of the (deprecated) [`common-rpc-functions`](/references/common-rpc-functions) recipe with one install, feature-detectable from RPC clients, adding workspace-root path containment on top of editor gating.
+Open files in an editor or reveal them in the OS explorer, shared over RPC by every devframe on the host. Replaces per-devframe registration of the (deprecated) `devframe/recipes/common-rpc-functions` recipe with one install, feature-detectable from RPC clients, adding workspace-root path containment on top of editor gating.
 
 Package: `@devframes/service-open` · Scope: `devframes:service:open`
 

docs/content/5.add-ons/2.services/index.md

@@ -5,7 +5,7 @@ navigation:
 description: 'Built-in wire services (@devframes/service-*): one node-side capability installed once per host and consumed by every devframe and RPC client, without re-implementing or re-bundling it.'
 ---
 
-Built-in [wire services](/guide/services#wire-services) (`@devframes/service-*`) — one node-side capability installed once per host and consumed by every devframe and RPC client, without re-implementing or re-bundling it. See [Cross-Devframe Services](/guide/services) for the mechanism and the [Services reference](/references/services) for the host API.
+Built-in [wire services](/guide/services#wire-services) (`@devframes/service-*`) — one node-side capability installed once per host and consumed by every devframe and RPC client, without re-implementing or re-bundling it. See [Cross-Devframe Services](/guide/services) for the mechanism and the [Node-Side API reference](/references/node-api#devframeserviceshost) for the host API.
 
 | Service | Scope | RPC functions | What it does |
 |---------|-------|---------------|--------------|

docs/content/5.add-ons/index.md

@@ -27,7 +27,7 @@ Complete tools, each picking its own UI framework yet sharing one node-side API
 
 ## Services
 
-Shared node-side capabilities other devframes install and consume — see [Cross-Devframe Services](/guide/services) for the mechanism, and the [Services reference](/references/services) for the host API.
+Shared node-side capabilities other devframes install and consume — see [Cross-Devframe Services](/guide/services) for the mechanism, and the [Node-Side API reference](/references/node-api#devframeserviceshost) for the host API.
 
 | Service | Scope | What it does |
 |---------|-------|--------------|

docs/content/6.errors/DF0062.md

@@ -19,7 +19,7 @@ Install the exact declared version to serve byte-identical assets:
 npm install @devframes/plugin-git-client@1.2.3
 ```
 
-A major-version mismatch is rejected instead — see [DF0061](/errors/DF0061.md).
+A major-version mismatch is rejected instead — see [DF0061](/errors/DF0061).
 
 ## Source
 

docs/content/7.migrations/4.migration-0.6.md

@@ -23,7 +23,7 @@ export default defineDevframe({
 })
 ```
 
-See [Devframe Definition](/guide/devframe-definition#sourcing-metadata-from-package-json) for the full reference and the optional `duplicationStrategy`.
+See [Devframe Definition](/guide/devframe-definition#sourcing-metadata-from-packagejson) for the full reference and the optional `duplicationStrategy`.
 
 ## Auth handshake methods are renamed
 

docs/content/8.references/11.services.md

@@ -2,7 +2,7 @@
 title: 'Node-Side API'
 navigation:
   icon: i-lucide-server-cog
-description: 'Lookup tables for the node side: DevframeDefinition fields, CLI options, storage scopes, RPC function types, broadcast options, streaming lifecycle, remote assets, diagnostics prefixes, and the auth surface.'
+description: 'Lookup tables for the node side: DevframeDefinition fields, CLI options, storage scopes, RPC function types, broadcast options, streaming lifecycle, remote assets, the cross-devframe services surface, diagnostics prefixes, and the auth surface.'
 ---
 
 Lookup tables for a devframe's node side. Each section links the guide page that teaches the concept.
@@ -102,6 +102,65 @@ The fields of a `RemoteAssets` source for `clientAssets` and `hostStatic` — [R
 | `provider` | `'jsdelivr'` (default), `'unpkg'`, or a custom provider (internal mirror). |
 | `offline` | `true` serves only from local install or cache, never network. |
 
+## `DevframeServicesHost`
+
+The methods on `ctx.services` — [Cross-Devframe Services](/guide/services#the-devframeserviceshost-api).
+
+| Method | Signature | Role |
+|--------|-----------|------|
+| `provide` | `(id, service) => revoke` | Publish an in-process service under a namespaced id. Throws [`DF0037`](/errors/DF0037) if the id is taken. |
+| `get` | `(id) => service \| undefined` | The service currently provided under `id` (augmented type, else `unknown`). |
+| `has` | `(id) => boolean` | Whether a service is provided under `id`. |
+| `whenAvailable` | `(id, cb) => unsubscribe` | Run `cb` as soon as the service exists — now if provided, else on `provide` — and re-fire on revoke/re-provide. |
+| `keys` | `() => string[]` | Ids of every currently-provided service. |
+| `install` | `(input, options?) => Promise<api \| undefined>` | Install a [wire service](#wire-service-definition-fields) at runtime (the dynamic escape hatch; the common path is declarative). `options.resolveFrom` is the descriptor's resolution base. |
+| `ready` | `() => Promise<void>` | **Internal.** Construct every queued wire service before any `setup` runs. Adapters call it; application code uses declarative `services`. |
+
+## Service tiers
+
+The two tiers a service can take — [Cross-Devframe Services](/guide/services).
+
+| Tier | Shared how | Registers RPC | Advertised to clients |
+|------|-----------|---------------|-----------------------|
+| In-process service (`provide`/`get`) | live object, node side only | No | No |
+| [Wire service](/guide/services#wire-services) (`install` / declarative `services`) | npm package, node API + RPC | Yes, under its `scope` | Yes, via `devframe:services` shared state |
+
+## Wire-service definition fields
+
+The fields of a `DevframeServiceDefinition` returned by a service package's `create<X>Service` factory — [Shipping a wire service](/guide/services#shipping-one).
+
+| Field | Type | Description |
+|-------|------|-------------|
+| `package` | `string` | **Required.** npm package name — also its registry key (`ctx.services.has(pkg)`). |
+| `version` | `string` | **Required.** Semver; advertised to clients, checked against declared ranges. |
+| `scope` | `string` | **Required.** RPC namespace its functions register under (e.g. `devframes:service:open`); `setup` gets a context pre-scoped to it. |
+| `meta` | `Record<string, unknown>` | Extra advertised metadata (feature flags, defaults). Must be JSON-serializable. |
+| `options` | `Options` | This instance's own option set, baked in by its factory; joins the merge. |
+| `mergeOptions` | `(sets: Options[]) => Options` | Merge multiple installers' option sets. Default: shallow, later wins. |
+| `setup` | `(ctx, info) => api` | **Required.** Register RPC on the pre-scoped context; return the node API served from `ctx.services.get(package)`. |
+
+## Wire-service descriptor fields
+
+The declarative reference form on `DevframeDefinition.services` / `initHub({ services })` — [Declaring services](/guide/services#declaring).
+
+| Field | Type | Description |
+|-------|------|-------------|
+| `package` | `string` | **Required.** npm package name; its default export is the factory the host imports. |
+| `version` | `string` | Accepted semver range. Unsatisfied warns ([`DF0069`](/errors/DF0069)), or throws ([`DF0068`](/errors/DF0068)) when `required`. |
+| `required` | `boolean` | Fail hard on a missing package ([`DF0067`](/errors/DF0067)) or unsatisfied range. Default `false` — a missing service is skipped and clients see `has() === false`. |
+| `options` | `Options` | Option set this installer contributes to the merge. |
+
+## Advertised service meta
+
+Each installed service's entry in the `devframe:services` [shared state](/guide/shared-state), mirrored to RPC clients as `rpc.services` — [Feature-detecting on the RPC client](/guide/services#feature-detecting-on-the-rpc-client).
+
+| Field | Description |
+|-------|-------------|
+| `package` | npm package name — the registry key. |
+| `version` | Installed version of the service. |
+| `scope` | RPC namespace its functions live under. |
+| `meta` | Extra service-declared metadata. |
+
 ## Diagnostic code prefixes
 
 Prefixes in use across the ecosystem — [Structured Diagnostics](/guide/diagnostics#code-conventions).