@ontrails/store 1.0.0-beta.17 → 1.0.0-beta.19

package/CHANGELOG.md

@@ -1,5 +1,35 @@
 # @ontrails/store
 
+## 1.0.0-beta.19
+
+### Patch Changes
+
+- e41c382: Document beta-channel install guidance in package and adapter README install snippets so consumers use explicit `@beta` (or pinned `1.0.0-beta.N`) tags instead of accidental `latest` resolution during the prerelease line. Adds the policy doc at `docs/releases/beta-channel-policy.md`, prints both `latest` and `beta` dist-tags in `bun run publish:registry-check`, and aligns plugin/skill install snippets.
+- ab1c77c: Advertise first-party adapter target metadata for catalog derivation.
+- Updated dependencies [e41c382]
+- Updated dependencies [1eb5bdc]
+- Updated dependencies [f8d80b9]
+- Updated dependencies [846a597]
+- Updated dependencies [223aaad]
+- Updated dependencies [3125f4d]
+- Updated dependencies [2494dc6]
+- Updated dependencies [2d53717]
+- Updated dependencies [16cb740]
+- Updated dependencies [8894ecb]
+- Updated dependencies [fdf7ec9]
+- Updated dependencies [d76be13]
+- Updated dependencies [84f56a5]
+- Updated dependencies [431b04c]
+- Updated dependencies [5d88104]
+- Updated dependencies [f04a9ef]
+  - @ontrails/core@1.0.0-beta.19
+
+## 1.0.0-beta.18
+
+### Patch Changes
+
+- @ontrails/core@1.0.0-beta.18
+
 ## 1.0.0-beta.17
 
 ### Patch Changes

package/README.md

@@ -146,16 +146,13 @@ created.id;
 
 ## Adapter Support Subpath
 
-Adapter authors who bind a `store(...)` definition to a concrete backend should
-import signal-binding helpers from `@ontrails/store/adapter-support`:
+Adapter authors who bind a `store(...)` definition to a concrete backend should import signal-binding helpers from `@ontrails/store/adapter-support`:
 
 ```typescript
 import { bindStoreDefinition } from '@ontrails/store/adapter-support';
 ```
 
-The subpath owns `bindStoreDefinition`, `createStoreTableSignals`,
-`composeStoreSignalId`, `isValidResourceId`, and `StoreSignalChange`. The root
-package stays focused on backend-agnostic store contracts.
+The subpath owns `bindStoreDefinition`, `createStoreTableSignals`, `composeStoreSignalId`, `isValidResourceId`, and `StoreSignalChange`. The root package stays focused on backend-agnostic store contracts.
 
 Writable bindings fire those canonical scoped signals automatically when you access the resource through `db.from(ctx)` inside a trail context.
 
@@ -227,8 +224,7 @@ This keeps the default happy path derived and typed, while still giving you full
 
 ## Adapter binding
 
-`@ontrails/drizzle` keeps the durable `store(...)` declaration in
-`@ontrails/store` and binds it to a concrete runtime:
+`@ontrails/drizzle` keeps the durable `store(...)` declaration in `@ontrails/store` and binds it to a concrete runtime:
 
 ```typescript
 import { connectDrizzle, connectReadOnlyDrizzle } from '@ontrails/drizzle';
@@ -249,13 +245,11 @@ export const readonly = connectReadOnlyDrizzle(definition, {
 });
 ```
 
-The root package still owns the authored persistence model; adapter packages
-project that model into runnable resources.
+The root package still owns the authored persistence model; adapter packages project that model into runnable resources.
 
 ## Schema export for external tooling
 
-If you need the raw derived Drizzle tables for tooling such as `drizzle-kit`,
-read them from the bound resource's `tables` field:
+If you need the raw derived Drizzle tables for tooling such as `drizzle-kit`, read them from the bound resource's `tables` field:
 
 ```typescript
 import { connectDrizzle } from '@ontrails/drizzle';
@@ -276,13 +270,13 @@ const schema = db.tables;
 ## Installation
 
 ```bash
-bun add @ontrails/store zod
+bun add @ontrails/store@beta zod
 ```
 
 Add Drizzle only when you want the external SQLite/ORM adapter:
 
 ```bash
-bun add @ontrails/drizzle
+bun add @ontrails/drizzle@beta
 ```
 
 ## Migration

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ontrails/store",
-  "version": "1.0.0-beta.17",
+  "version": "1.0.0-beta.19",
   "files": [
     "src/**/*.ts",
     "!src/**/__tests__/**",
@@ -26,9 +26,21 @@
     "clean": "rm -rf dist *.tsbuildinfo"
   },
   "dependencies": {
-    "@ontrails/core": "^1.0.0-beta.16"
+    "@ontrails/core": "^1.0.0-beta.19"
   },
   "peerDependencies": {
     "zod": "^4.3.5"
+  },
+  "trails": {
+    "adapterTargets": {
+      "store": {
+        "placements": [
+          "extracted",
+          "subpath"
+        ],
+        "supportImport": "@ontrails/store/adapter-support",
+        "testingImport": "@ontrails/store/testing"
+      }
+    }
   }
 }

package/src/trails/crud.ts

@@ -39,7 +39,7 @@ type GeneratedFieldsOf<TTable extends AnyStoreTable> =
 
 /**
  * Input type `deriveTrail` projects for a given CRUD operation against a
- * store table. Routes through `TableContour<TTable>` so the projected input
+ * store table. Uses `TableContour<TTable>` so the projected input
  * structurally matches the contour-backed derivation path in
  * `@ontrails/core`'s `deriveTrail`.
  */

package/src/types.ts

@@ -43,7 +43,7 @@ type GeneratedFieldNames<
   ? TGenerated[number]
   : never;
 
-// We intentionally use Zod v4's shape-routed object infer helpers here because
+// We intentionally use Zod v4's shape-based object infer helpers here because
 // the public z.input/z.output path widens away the generic equality we need at
 // store/core trail boundaries. These $-prefixed helpers are semi-internal Zod
 // v4 API; that maintenance tradeoff is acceptable here because the public path
@@ -65,7 +65,7 @@ type ObjectOutputOf<TShape extends z.ZodRawShape> = z.core.$InferObjectOutput<
  * fixtures can omit timestamps and similar server-managed values when the mock
  * store can synthesize them.
  *
- * Routes input inference through the object's `shape` via a conditional
+ * Feeds input inference through the object's `shape` via a conditional
  * `infer` so fixture inputs stay structurally aligned with the derived
  * create/upsert inputs they meet at store/core trail boundaries.
  *
@@ -101,11 +101,11 @@ export type StoreFixtureInput<
 /**
  * Normalized fixture row after schema validation and default application.
  *
- * Mirror of {@link StoreFixtureInput} on the output side — routed through
+ * Mirror of {@link StoreFixtureInput} on the output side — computed through
  * `$InferObjectOutput<TShape, Record<never, never>>` so row types stay
  * structurally aligned with the contour output shapes they compose against.
  *
- * As with {@link StoreFixtureInput}, this is a shape-routed equivalent rather
+ * As with {@link StoreFixtureInput}, this is a shape-based equivalent rather
  * than the identical `z.output<TSchema>` inference path core uses directly.
  */
 export type StoreFixtureRow<
@@ -428,11 +428,11 @@ export type GeneratedKeysOf<TTable extends AnyStoreTable> = Extract<
 /**
  * Insert shape: entity minus generated fields, with defaulted fields optional.
  *
- * Routes through `$InferObjectInput<TShape, Record<never, never>>` via a
+ * Uses `$InferObjectInput<TShape, Record<never, never>>` via a
  * conditional `infer` on the object's `shape`. At concrete instantiations
  * this collapses to the same structural shape as
  * `Omit<z.input<TTable['schema']>, GeneratedKeysOf<TTable>>`, but the
- * shape-routed form lets TypeScript prove structural equality with
+ * shape-based form lets TypeScript prove structural equality with
  * `CreateInputOf<Contour, ...>` at trail boundaries without widening
  * generic call sites to `Record<string, unknown>`.
  *