chore: use the ueberbrot npm scope

.fallowrc.jsonc

@@ -44,7 +44,7 @@
     "@tanstack/intent",
     "effect",
     // Fallow resolves workspace imports to source but misses the root package dependency.
-    "effect-api-query",
+    "@ueberbrot/effect-api-query",
     "publint",
     // React belongs to the private apps; Fallow attributes shared example sources to the root.
     "react",

README.md

@@ -9,7 +9,7 @@ Your application controls transport, client lifetime, and cache policy.
 Install the package and TanStack Query Core:
 
 ```sh
-pnpm add effect-api-query @tanstack/query-core
+pnpm add @ueberbrot/effect-api-query @tanstack/query-core
 ```
 
 The package requires one exact Effect 4 release because its RPC and HTTP API modules are unstable.
@@ -42,7 +42,7 @@ Client integration in `client.ts`:
 
 ```ts
 import { QueryClient } from '@tanstack/query-core'
-import { createRpcQueryUtils } from 'effect-api-query'
+import { createRpcQueryUtils } from '@ueberbrot/effect-api-query'
 import type { RpcClient, RpcGroup } from 'effect/rpc'
 
 import { usersRpc } from './rpc-contract.ts'
@@ -87,7 +87,7 @@ Client integration in `client.ts`:
 
 ```ts
 import { QueryClient } from '@tanstack/query-core'
-import { createHttpApiQueryUtils } from 'effect-api-query'
+import { createHttpApiQueryUtils } from '@ueberbrot/effect-api-query'
 import type { HttpApiClient } from 'effect/http-api'
 
 import { usersApi } from './http-contract.ts'
@@ -137,10 +137,10 @@ npx skills add ueberBrot/effect-api-query --full-depth --skill effect-api-query
 ```
 
 The npm package includes the same skill. After installing the library, run
-`npx @tanstack/intent@latest install` and enable `effect-api-query`, then load it with:
+`npx @tanstack/intent@latest install` and enable `@ueberbrot/effect-api-query`, then load it with:
 
 ```sh
-npx @tanstack/intent@latest load effect-api-query#effect-api-query
+npx @tanstack/intent@latest load @ueberbrot/effect-api-query#effect-api-query
 ```
 
 Intent loads the skill from your installed library version. Update a skill installed from GitHub

_artifacts/domain_map.yaml

@@ -1,5 +1,5 @@
 library:
-  name: effect-api-query
+  name: '@ueberbrot/effect-api-query'
   version: 0.1.0
   repository: https://github.com/ueberBrot/effect-api-query
   description: TanStack Query utilities derived from ready Effect RPC and HTTP clients.
@@ -16,7 +16,7 @@ skills:
       consumers.
     type: core
     packages:
-      - effect-api-query
+      - '@ueberbrot/effect-api-query'
     covers:
       - RPC construction and canonical identity
       - HTTP decoded requests, SSE, multipart mutations, and metadata
@@ -47,10 +47,10 @@ skills:
       - Choose an application-owned transport within documented version and host boundaries.
     subsystems:
       - name: RPC
-        package: effect-api-query
+        package: '@ueberbrot/effect-api-query'
         config_surface: Literal RpcGroup, flat ready client, prefix, key encoders, runner.
       - name: HTTP
-        package: effect-api-query
+        package: '@ueberbrot/effect-api-query'
         config_surface: Literal HttpApi, ready client, prefix, request encoders, runner.
     reference_candidates:
       - topic: Adapter inputs and capabilities

_artifacts/skill_spec.md

@@ -17,8 +17,8 @@ The entry point contains shared rules and directs conditional tasks to six refer
 | Hydration and SSR    | Snapshots, paired view codecs, preparation and cleanup             |
 | Frameworks and hosts | Provider setup, Suspense, reactive accessors, transports and hosts |
 
-Consumers load the guidance from their installed package without repository-local
-authoring skills. Planning records remain outside the shipped package.
+Consumers load the guidance from installed `@ueberbrot/effect-api-query` without
+repository-local authoring skills. Planning records remain outside the shipped package.
 
 ## Sources and boundaries
 

_artifacts/skill_tree.yaml

@@ -1,5 +1,5 @@
 library:
-  name: effect-api-query
+  name: '@ueberbrot/effect-api-query'
   version: 0.1.0
 generated_from:
   domain_map: _artifacts/domain_map.yaml

apps/docs/astro.config.mts

@@ -347,7 +347,7 @@ export default defineConfig({
         },
       ],
       social: [{ icon: 'github', label: 'GitHub', href: repositoryUrl }],
-      title: packageManifest.name,
+      title: 'effect-api-query',
     }),
   ],
   site: 'https://ueberbrot.github.io',

apps/docs/public/package-version.js

@@ -1,6 +1,6 @@
 ;(() => {
-  const packageUrl = 'https://www.npmjs.com/package/effect-api-query'
-  const packageManifestUrl = 'https://registry.npmjs.org/effect-api-query/latest'
+  const packageUrl = 'https://www.npmjs.com/package/@ueberbrot/effect-api-query'
+  const packageManifestUrl = 'https://registry.npmjs.org/@ueberbrot%2Feffect-api-query/latest'
   const semanticVersion = /^\d+\.\d+\.\d+(?:-[0-9A-Za-z.-]+)?(?:\+[0-9A-Za-z.-]+)?$/
 
   const updatePackageVersion = (version) => {

apps/docs/src/content/docs/getting-started/compatibility-and-stability.md

@@ -3,7 +3,7 @@ title: Compatibility and Stability
 description: Check supported integrations, module format, and the release policy.
 ---
 
-Import both factories from the `effect-api-query` package root. They use the same peer dependencies.
+Import both factories from the `@ueberbrot/effect-api-query` package root. They use the same peer dependencies.
 The package's [manifest](https://github.com/ueberBrot/effect-api-query/blob/main/package.json)
 defines the peer requirements. The [workspace catalog](https://github.com/ueberBrot/effect-api-query/blob/main/pnpm-workspace.yaml)
 lists the versions tested in this repository. See the

apps/docs/src/content/docs/getting-started/http-quick-start.md

@@ -45,8 +45,8 @@ Client integration in `client.ts`:
 
 ```ts
 import { MutationObserver, QueryClient } from '@tanstack/query-core'
+import { createHttpApiQueryUtils } from '@ueberbrot/effect-api-query'
 import { ManagedRuntime } from 'effect'
-import { createHttpApiQueryUtils } from 'effect-api-query'
 import { FetchHttpClient } from 'effect/http'
 import { HttpApiClient } from 'effect/http-api'
 

apps/docs/src/content/docs/getting-started/installation.md

@@ -6,7 +6,7 @@ description: Install effect-api-query and its peer dependencies.
 Install the package and TanStack Query Core:
 
 ```sh
-pnpm add effect-api-query @tanstack/query-core
+pnpm add @ueberbrot/effect-api-query @tanstack/query-core
 ```
 
 With pnpm's default peer installation enabled, this command also installs the exact Effect release that the package requires.

apps/docs/src/content/docs/getting-started/quick-start.md

@@ -42,8 +42,8 @@ Client integration in `client.ts`:
 
 ```ts
 import { MutationObserver, QueryClient } from '@tanstack/query-core'
+import { createRpcQueryUtils } from '@ueberbrot/effect-api-query'
 import { Effect, Exit, Layer, Scope } from 'effect'
-import { createRpcQueryUtils } from 'effect-api-query'
 import { FetchHttpClient } from 'effect/http'
 import { RpcClient, RpcSerialization } from 'effect/rpc'
 

apps/docs/src/content/docs/guides/cache-filters.md

@@ -5,7 +5,7 @@ description: Read typed entries and target native cache operations with generate
 
 For typed `getQueryData` and `setQueryData`, use a generated concrete key. For native
 `invalidateQueries`, `cancelQueries`, and query-state filters, use root, branch, leaf, or view prefixes.
-To select one supported cache view, import `viewPrefix` from `effect-api-query`.
+To select one supported cache view, import `viewPrefix` from `@ueberbrot/effect-api-query`.
 Choose the scope before adding `type`, `stale`, `fetchStatus`, or `predicate` conditions:
 
 | Scope                 | Key                                                    | Matches                                                            |

apps/docs/src/content/docs/guides/cancellation.md

@@ -4,7 +4,7 @@ description: Cancel queries and request server-side cancellation for long-runnin
 ---
 
 In your application client module, forward TanStack's `AbortSignal` to the runtime.
-Import `RunPromiseExit` from `effect-api-query`:
+Import `RunPromiseExit` from `@ueberbrot/effect-api-query`:
 
 ```ts
 const runPromiseExit: RunPromiseExit = (effect, options) => runtime.runPromiseExit(effect, options)

apps/docs/src/content/docs/guides/conditional-queries.md

@@ -13,7 +13,7 @@ use `{ input: skipToken }`. The builder still accepts TanStack options such as `
 `select`, or `initialData`:
 
 ```ts
-import { skipToken } from 'effect-api-query'
+import { skipToken } from '@ueberbrot/effect-api-query'
 
 type User = { id: number; name: string }
 

apps/docs/src/content/docs/guides/handle-failures.md

@@ -7,8 +7,8 @@ A failed RPC `Exit` becomes `EffectRpcQueryError`. The error records the RPC tag
 operation, and the complete Effect `Cause`. Inspect the error in your application handler:
 
 ```ts
+import { isEffectRpcQueryError } from '@ueberbrot/effect-api-query'
 import { Cause } from 'effect'
-import { isEffectRpcQueryError } from 'effect-api-query'
 
 const logRpcError = (error: unknown) => {
   if (isEffectRpcQueryError(error)) {
@@ -36,7 +36,7 @@ bounded attempt counts, and synchronous preparation errors.
 
 ## Inspect HTTP failures
 
-Import `isEffectHttpApiQueryError` from `effect-api-query` to recognize a failed HTTP execution.
+Import `isEffectHttpApiQueryError` from `@ueberbrot/effect-api-query` to recognize a failed HTTP execution.
 The wrapper records `apiId`, `groupId`, `endpoint`, `method`, and `operation`. Its `cause`
 retains the complete original Effect Cause. Use `Cause.findError` to inspect declared endpoint
 errors, middleware errors, Schema errors, and HTTP client errors. Use `Cause.hasDies` and

apps/docs/src/content/docs/guides/query-defaults.md

@@ -18,7 +18,7 @@ builder's inference. The library supplies the generated keys and execution funct
 ## Register native defaults
 
 In the cache module, import `QueryClient` from `@tanstack/query-core` and `viewPrefix` from
-`effect-api-query`:
+`@ueberbrot/effect-api-query`:
 
 ```ts
 const queryClient = new QueryClient({
@@ -61,7 +61,7 @@ the cache owner's lifetime. Builders reject per-call hashing overrides. See
 
 If a policy belongs to one leaf and view, use `withQueryPolicy`. `QueryPolicy` types reusable
 objects with that leaf's native options. Retry and refetch callbacks retain its data and error types.
-Import both from `effect-api-query`:
+Import both from `@ueberbrot/effect-api-query`:
 
 ```ts
 const policy = {
@@ -90,7 +90,7 @@ use a value such as `staleTime: 0` or `retry: false`.
 
 ## Bind mutation invalidation
 
-Import `withMutationPolicy` from `effect-api-query`. Seed the returned user and invalidate affected
+Import `withMutationPolicy` from `@ueberbrot/effect-api-query`. Seed the returned user and invalidate affected
 reads once for every use of the creation builder:
 
 ```ts

apps/docs/src/content/docs/guides/react-query.md

@@ -45,9 +45,9 @@ Client integration in `client.ts`:
 
 ```ts
 import { QueryClient } from '@tanstack/react-query'
+import { createHttpApiQueryUtils } from '@ueberbrot/effect-api-query'
+import type { RunPromiseExit } from '@ueberbrot/effect-api-query'
 import { ManagedRuntime } from 'effect'
-import { createHttpApiQueryUtils } from 'effect-api-query'
-import type { RunPromiseExit } from 'effect-api-query'
 import { FetchHttpClient } from 'effect/http'
 import { HttpApiClient } from 'effect/http-api'
 

apps/docs/src/content/docs/guides/retry-queries.md

@@ -58,7 +58,7 @@ unknown values safely. The adapter guard rejects custom runner failures that pas
 ## Bind a typed RPC policy
 
 Import `withQueryPolicy`, `isEffectRpcQueryError`, and the type `InferQueryError` from
-`effect-api-query`, plus `RpcClientError` from `effect/rpc`. After acquiring your ready client and
+`@ueberbrot/effect-api-query`, plus `RpcClientError` from `effect/rpc`. After acquiring your ready client and
 creating `rpc`, bind the profile read:
 
 ```ts
@@ -82,7 +82,7 @@ belongs to the application that owns those transports.
 
 ## Bind the same decision to HTTP
 
-Import `isEffectHttpApiQueryError` from `effect-api-query` and `HttpClientError` from `effect/http`.
+Import `isEffectHttpApiQueryError` from `@ueberbrot/effect-api-query` and `HttpClientError` from `effect/http`.
 Reuse the shared retry logic with HTTP's transport classifier:
 
 ```ts

apps/docs/src/content/docs/guides/solid-query.md

@@ -23,7 +23,7 @@ with `name`:
 
 ```ts
 import { useQuery } from '@tanstack/solid-query'
-import { skipToken } from 'effect-api-query'
+import { skipToken } from '@ueberbrot/effect-api-query'
 import { createSignal } from 'solid-js'
 
 import { rpc } from './queries.ts'

apps/docs/src/content/docs/guides/stream-snapshots.md

@@ -9,7 +9,7 @@ query and awaits local iterator cleanup. Ordinary `queryClient.query` waits for
 
 ## Capture data before dehydration
 
-Import `fetchStreamSnapshot` from `effect-api-query`. In the request loader or server snapshot
+Import `fetchStreamSnapshot` from `@ueberbrot/effect-api-query`. In the request loader or server snapshot
 module, use your existing `rpc`, request-local `queryClient` and abort `signal`. Keep the ready
 client and runner alive until capture settles. For the declared `updates.watch` stream:
 

apps/docs/src/content/docs/guides/suspense-and-recovery.md

@@ -27,9 +27,9 @@ import {
   useSuspenseQueries,
   useSuspenseQuery,
 } from '@tanstack/react-query'
+import { createRpcQueryUtils, isEffectRpcQueryError } from '@ueberbrot/effect-api-query'
+import type { InferQueryData, InferQueryError } from '@ueberbrot/effect-api-query'
 import { Cause, Result, Schema } from 'effect'
-import { createRpcQueryUtils, isEffectRpcQueryError } from 'effect-api-query'
-import type { InferQueryData, InferQueryError } from 'effect-api-query'
 import { Rpc, RpcGroup } from 'effect/rpc'
 import type { RpcClient } from 'effect/rpc'
 import { Component, Suspense } from 'react'

apps/docs/src/content/docs/guides/trace-streams.md

@@ -38,9 +38,9 @@ Client tracing in `trace-feed.ts`:
 
 ```ts
 import { QueryClient } from '@tanstack/query-core'
+import { createHttpApiQueryUtils, fetchStreamSnapshot } from '@ueberbrot/effect-api-query'
+import type { RunPromiseExit } from '@ueberbrot/effect-api-query'
 import { Effect, Layer, ManagedRuntime, Stream, Tracer } from 'effect'
-import { createHttpApiQueryUtils, fetchStreamSnapshot } from 'effect-api-query'
-import type { RunPromiseExit } from 'effect-api-query'
 import { FetchHttpClient } from 'effect/http'
 import { HttpApiClient } from 'effect/http-api'
 import { OtlpSerialization, OtlpTracer } from 'effect/observability'

apps/docs/src/content/docs/guides/vue-query.md

@@ -22,8 +22,8 @@ Here `users.read` returns a user with a `name`:
 
 ```ts
 import { useQuery } from '@tanstack/vue-query'
-import { skipToken } from 'effect-api-query'
-import type { InferQueryData, InferQueryError } from 'effect-api-query'
+import { skipToken } from '@ueberbrot/effect-api-query'
+import type { InferQueryData, InferQueryError } from '@ueberbrot/effect-api-query'
 import { computed, ref } from 'vue'
 
 import { rpc } from './queries.ts'

apps/docs/src/content/docs/reference/http-factory.md

@@ -5,7 +5,7 @@ description: HTTP factory options, decoded request input, response data, and cac
 
 `createHttpApiQueryUtils(api, options)` builds and freezes an HTTP utility tree from an Effect
 HttpApi and a ready HttpApiClient. The application manages the client's lifetime.
-The factory is exported from `effect-api-query`.
+The factory is exported from `@ueberbrot/effect-api-query`.
 
 The [HTTP Quick Start](/effect-api-query/getting-started/http-quick-start/) shows factory setup.
 [HTTP Builders](/effect-api-query/reference/http-builders/) defines each generated option and key.

apps/docs/src/content/docs/reference/public-exports.md

@@ -3,7 +3,7 @@ title: Public Exports
 description: Package-root values and types.
 ---
 
-The package root, `effect-api-query`, exports all supported values and types.
+The package root, `@ueberbrot/effect-api-query`, exports all supported values and types.
 
 | Export                                    | Purpose                                                                        |
 | ----------------------------------------- | ------------------------------------------------------------------------------ |

apps/docs/src/content/docs/reference/type-inference.md

@@ -3,7 +3,7 @@ title: Type Inference
 description: Derive operation inputs, cached data, mutation results, and failures from generated leaves.
 ---
 
-These types are exported from `effect-api-query`. Each describes a generated leaf's contract:
+These types are exported from `@ueberbrot/effect-api-query`. Each describes a generated leaf's contract:
 
 | Type                          | Result                                                    |
 | ----------------------------- | --------------------------------------------------------- |

e2e-docs/docs.spec.ts

@@ -1,8 +1,8 @@
 import { expect, test } from '@playwright/test'
 
 const docsBase = '/effect-api-query/'
-const registryUrl = 'https://registry.npmjs.org/effect-api-query/latest'
-const packageUrl = 'https://www.npmjs.com/package/effect-api-query'
+const registryUrl = 'https://registry.npmjs.org/@ueberbrot%2Feffect-api-query/latest'
+const packageUrl = 'https://www.npmjs.com/package/@ueberbrot/effect-api-query'
 const repositoryUrl = 'https://github.com/ueberBrot/effect-api-query'
 
 test('opens tutorials and feature guides and searches the production index', async ({

examples/shared/error-description.ts

@@ -1,5 +1,5 @@
+import { isEffectHttpApiQueryError, isEffectRpcQueryError } from '@ueberbrot/effect-api-query'
 import { Cause } from 'effect'
-import { isEffectHttpApiQueryError, isEffectRpcQueryError } from 'effect-api-query'
 
 // oxlint-disable-next-line anti-slop/no-unknown-parameters
 export const describeEffectError = (error: unknown) => {

examples/tanstack-start/package.json

@@ -14,8 +14,8 @@
     "@tanstack/react-router": "catalog:",
     "@tanstack/react-router-ssr-query": "catalog:",
     "@tanstack/react-start": "catalog:",
+    "@ueberbrot/effect-api-query": "workspace:*",
     "effect": "catalog:",
-    "effect-api-query": "workspace:*",
     "react": "catalog:",
     "react-dom": "catalog:"
   },

examples/tanstack-start/src/components/conditional-user-query.tsx

@@ -1,6 +1,6 @@
 import type { User } from '@effect-api-query/contracts'
 import { useQuery } from '@tanstack/react-query'
-import { skipToken } from 'effect-api-query'
+import { skipToken } from '@ueberbrot/effect-api-query'
 import { useState } from 'react'
 
 import type { TanStackStartApplication } from '../lib/application.ts'

examples/tanstack-start/src/lib/application.ts

@@ -2,9 +2,13 @@ import { exampleHttpApi, exampleRpcGroup } from '@effect-api-query/contracts'
 import { startExampleRpcClient } from '@effect-api-query/contracts/client'
 import type { ExampleRpcClient, StartedExampleRpcClient } from '@effect-api-query/contracts/client'
 import { QueryClient } from '@tanstack/react-query'
+import {
+  createHttpApiQueryUtils,
+  createRpcQueryUtils,
+  fetchStreamSnapshot,
+} from '@ueberbrot/effect-api-query'
+import type { RunPromiseExit } from '@ueberbrot/effect-api-query'
 import { Effect, Layer, ManagedRuntime } from 'effect'
-import { createHttpApiQueryUtils, createRpcQueryUtils, fetchStreamSnapshot } from 'effect-api-query'
-import type { RunPromiseExit } from 'effect-api-query'
 import { FetchHttpClient, HttpClient, HttpClientRequest } from 'effect/http'
 import { HttpApiClient } from 'effect/http-api'
 

examples/tanstack-start/tests/server-render.test.tsx

@@ -1,8 +1,8 @@
 import { startExampleRpcServer } from '@effect-api-query/server'
 import { QueryClient } from '@tanstack/react-query'
 import { createMemoryHistory, RouterProvider } from '@tanstack/react-router'
+import { createRpcQueryUtils, fetchStreamSnapshot } from '@ueberbrot/effect-api-query'
 import { Deferred, Effect, Exit, Schema, Scope, Stream } from 'effect'
-import { createRpcQueryUtils, fetchStreamSnapshot } from 'effect-api-query'
 import { Rpc, RpcGroup } from 'effect/rpc'
 import type { RpcClient } from 'effect/rpc'
 import { renderToString } from 'react-dom/server'