@pouchy_ai/world-sdk 0.25.0 → 0.26.0

package/CHANGELOG.md

@@ -1,5 +1,27 @@
 # @pouchy_ai/world-sdk
 
+## 0.26.0
+
+- **`WorldDeliberationResponse.viewTrimmed`** — whether the role's view had to
+  be trimmed to fit the previewer's input budget. The budget grows with the
+  worldline, so a long session reaches it where a short one never does, and a
+  previewer working from a cut-down view is not the same instrument as one that
+  saw the whole state.
+- The server has always computed it and told nobody. A field test read its
+  absence in a downstream response as "no trimming happened" — a different claim
+  from "nobody reports this" — and retired a live hypothesis on that reading.
+  Always present, `true` or `false`: a flag that appears on only one branch
+  cannot separate "it did not happen" from "we did not look".
+- Additive; nothing else on the deliberation surface moved.
+
+## 0.25.1
+
+- **Docs links now resolve.** The README sent readers to `docs/*.md` "in the Pouchy
+  repo" — which is PRIVATE, so every pointer in the shipped package was a dead end
+  for the people the package is for. The world documentation is now published at
+  pouchy.ai/docs, and the README links there.
+- No code change; the client surface is byte-identical to 0.25.0.
+
 ## 0.25.0
 
 - **`WorldApiError.rejectedEffects`** — a rejected turn (422) now arrives with

package/README.md

@@ -266,8 +266,8 @@ It returns the recent refusals with a closed reason vocabulary — `missing`,
 `malformed`, `unknown_key`, `stale`, `bad_signature`, `no_keys` — plus how many
 audit rows it scanned, because an empty feed is not a clean bill of health.
 
-`docs/world-sdk-errors.md` in the Pouchy repo maps every reason and every
-`WorldApiError` code to what to change.
+[World SDK — errors and refusals](https://pouchy.ai/docs/world-sdk-errors) maps
+every reason and every `WorldApiError` code to what to change.
 
 ## The three things integrators get wrong
 
@@ -310,11 +310,13 @@ and exits non-zero on the first structural failure.
 
 ## Quickstarts
 
-- `docs/world-quickstart-drama.md` — screenplay → world → new screenplay draft
-- `docs/world-quickstart-npc.md` — one town, three NPCs, one shared state
-- `docs/world-quickstart-nextjs.md` — a Next.js app: one route handler, one page,
+- [An interactive drama](https://pouchy.ai/docs/world-quickstart-drama) — screenplay → world → new screenplay draft
+- [NPCs that share one world](https://pouchy.ai/docs/world-quickstart-npc) — one town, three NPCs, one shared state
+- [Inside your Next.js app](https://pouchy.ai/docs/world-quickstart-nextjs) — one route handler, one page,
   no browser login anywhere in the deployment
 
+Everything else starts at the [documentation index](https://pouchy.ai/docs/pouchy-world).
+
 ## License
 
 See LICENSE.

package/dist/index.d.ts

@@ -4,7 +4,7 @@
  *  a project is running — which is exactly the field you reach for when a
  *  customer's integration behaves like an older SDK than they say they have.
  *  It sat at '0.1.0' for eight releases before anything compared the two. */
-export declare const WORLD_SDK_VERSION = "0.25.0";
+export declare const WORLD_SDK_VERSION = "0.26.0";
 export declare const DEFAULT_BASE_URL = "https://pouchy.ai/v1";
 /** One direction a beat could take. The WHOLE of what a deliberation shows a
  *  player: no reasoning, no role secrets, no simulated effects, no scores. */
@@ -30,6 +30,16 @@ export interface WorldDeliberationResponse {
     /** Why it stopped. A run that hit a ceiling says so rather than letting a
      *  short list pass for a complete one. */
     stop: 'complete' | 'candidate_cap' | 'model_call_cap' | 'token_cap' | 'time_cap' | 'no_roles';
+    /** True when the role's view had to be trimmed to fit the previewer's input
+     *  budget — which grows with the worldline, so a long session can reach it
+     *  where a short one never does.
+     *
+     *  It matters because a previewer working from a cut-down view is not the
+     *  same instrument as one that saw the whole state, and until 0.26.0 the
+     *  server computed this and told nobody. A field test then read its absence
+     *  as "no trimming happened" — a different claim from "nobody reports this"
+     *  — and retired a live hypothesis on it. Always present, true or false. */
+    viewTrimmed: boolean;
 }
 /** The refusal classes a world call can produce. `unknown` is deliberate: an
  *  unrecognized status is never quietly folded into a neighbour. */

package/dist/index.js

@@ -23,7 +23,7 @@ import { createHash, createHmac, randomUUID } from 'node:crypto';
  *  a project is running — which is exactly the field you reach for when a
  *  customer's integration behaves like an older SDK than they say they have.
  *  It sat at '0.1.0' for eight releases before anything compared the two. */
-export const WORLD_SDK_VERSION = '0.25.0';
+export const WORLD_SDK_VERSION = '0.26.0';
 export const DEFAULT_BASE_URL = 'https://pouchy.ai/v1';
 /** Read the commit turn id out of an envelope, so the signature covers the id
  *  the server will commit under. The payload half is base64url JSON; the

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@pouchy_ai/world-sdk",
-	"version": "0.25.0",
+	"version": "0.26.0",
 	"description": "Server-side TypeScript client for Pouchy World \u2014 story packages, world definitions, world sessions, coordinated turns, trusted events, replay verification and script drafts. Node only: it holds a project Secret Key and a source signing key, which never belong in a browser or a mobile app.",
 	"type": "module",
 	"license": "SEE LICENSE IN LICENSE",