@oddington/sdk 0.1.27 → 0.1.29

package/README.md

@@ -75,8 +75,9 @@ runtime contains `run.id`, `data`, `files`, `connections`, `inbox`, and `step`.
 Accepted input and saved values are immutable snapshots. Access declarations set
 maximum named capabilities and grant no authority; the trusted host checks current
 authority. Response handler IDs are local to the routine and must be unique. A
-declared `review` handler crosses the Inbox publication seam as
-`invoice-import/review`, without deploying or executing that handler.
+declared `review` handler crosses the Inbox publication seam as `review`; Inbox
+retains the canonical `invoice-import` routine identity separately, without
+deploying or executing that handler.
 
 The bounded grammar supports closed objects with required properties, arrays with
 an explicit `maxItems` from 1 to 64, booleans, strings (at most 4096 code points),
@@ -254,8 +255,9 @@ contract map is needed. Descriptions combine safe structure with live readiness
 and connection availability. Starts validate the current definition and input;
 retained reads and publication recheck complete saved member/source/capability
 scope. No installation is needed. Bindings accept no endpoint, credential,
-command, path or configuration selector. Hosted declarations stay visible and
-unavailable until hosted execution exists. Operations reject with
+command, path or configuration selector. A local app uses its live Local Host;
+a hosted app uses its existing member session and workspace context to reach
+the current remote Run owner through the same bindings. Operations reject with
 `AppRoutineError.reason`: `authority_unavailable`, `execution_unavailable`, or
 `invalid_input`. Starts and publications are not automatically retried. A
 disconnected watch ends and requires `current()`. History returns at most 20
@@ -325,6 +327,9 @@ from the repository. This checks Node runtime exports and declarations, all publ
 text for leaks, and the named browser imports in a realm without Node globals or
 a module loader. It rejects bundler warnings, external dependencies, Node/shim
 code, unused implementations and increases beyond the reviewed SDK byte ceiling.
+During diagnosis, list the independently runnable phases with
+`bun --no-env-file run packages/sdk/scripts/verify-package.ts --list-phases`
+and rerun only the failed `artifact` or `browser` phase with `--phase <name>`.
 The newer Local Host app imports are bundled and exercised separately under the
 same strict compatibility audit, so they cannot weaken or inflate the hosted
 Data/Files size comparison.
@@ -503,6 +508,21 @@ replacement; repeat its options and links while omitting unrelated collections.
 There is no automatic retry or separate version fetch.
 Collection schemas omit Markdown storage hints.
 
+For schema-aware authoring, sign in with the OS CLI and run
+`os data schema general` inside the consuming TypeScript Git worktree. It writes
+one `os-data.generated.d.ts` and integrates that shared declaration into the
+worktree's TypeScript projects. Review and commit the declaration and changed
+project files so a fresh clone needs no credentials or regeneration. Customer
+source continues to import only from `@oddington/sdk`.
+
+Known repository literals then constrain collection/field/link names and query
+operands and infer projected `select`, `pages` and `all` values from normalized
+schemas. Multiple aliases share the root declaration. Refresh explicitly with
+the same CLI command after publishing schema changes; app builds and launches
+never refresh it. Missing metadata and dynamic repository strings retain generic
+types. Read/search/history and change payloads remain generic. Committed or stale
+types grant no runtime authority and never replace authoritative Data validation.
+
 Iterate matching Records on demand or collect them with an explicit total ceiling:
 
 ```ts