@hitch42/applet 0.1.1-beta.6 → 0.1.1-beta.8

package/dist/{auth-DaVK0k5R.js → workspace-XVtM12ZC.js}

@@ -1,5 +1,7 @@
+import { createRequire } from "node:module";
+import { existsSync } from "node:fs";
 import { chmod, mkdir, readFile, writeFile } from "node:fs/promises";
-import { join } from "node:path";
+import { basename, dirname, join, resolve } from "node:path";
 import { spawn } from "node:child_process";
 import { homedir } from "node:os";
 //#region ../shared/auth/src/store.mts
@@ -326,6 +328,33 @@ async function loginWithDevice(instanceUrl, options = {}) {
 	};
 }
 //#endregion
+//#region ../shared/auth/src/workspace.mts
+const ORG_CODE_PATTERN = /^[a-z][a-z0-9]*(?:-[a-z0-9]+)*$/;
+const require = createRequire(import.meta.url);
+function readWorkspaceConfig(dir) {
+	const path = resolve(dir, "hitch.config.ts");
+	if (!existsSync(path)) return void 0;
+	let module;
+	try {
+		module = require(path);
+	} catch (error) {
+		throw new Error(`Failed to load ${path}.`, { cause: error });
+	}
+	const config = module !== null && typeof module === "object" && "default" in module ? module.default : module;
+	if (config === null || typeof config !== "object" || !("sdk" in config) || typeof config.sdk !== "string" || config.sdk.length === 0 || !("org" in config) || typeof config.org !== "string" || !ORG_CODE_PATTERN.test(config.org)) throw new Error(`Invalid Hitch config in ${path}: "sdk" must be a package spec and "org" an organization code.`);
+	const githubWorkflow = "githubWorkflow" in config ? config.githubWorkflow : void 0;
+	if (githubWorkflow !== void 0 && typeof githubWorkflow !== "boolean") throw new Error(`Invalid Hitch config in ${path}: "githubWorkflow" must be a boolean.`);
+	return {
+		sdk: config.sdk,
+		org: config.org,
+		githubWorkflow
+	};
+}
+function findWorkspaceConfig(cwd) {
+	const appletsDir = dirname(cwd);
+	return readWorkspaceConfig(cwd) ?? (basename(appletsDir) === "applets" ? readWorkspaceConfig(dirname(appletsDir)) : void 0);
+}
+//#endregion
 //#region src/auth.ts
 async function fetchWithOrgAuth(orgCode, options, request) {
 	const fetcher = options.fetch ?? globalThis.fetch;
@@ -334,9 +363,10 @@ async function fetchWithOrgAuth(orgCode, options, request) {
 	const auth = await resolveAuthForOrg(instanceUrl, orgCode, options.store);
 	if (auth !== void 0) {
 		const response = await request(organizationUrl, bearerToken(auth));
-		if (response.status !== 401 && response.status !== 403) return response;
+		rejectEnvironmentKey(response, auth);
+		if (response.status !== 401) return response;
 	}
-	if (!(options.stdinIsTTY ?? process.stdin.isTTY === true)) throw new Error("not logged in — set HITCH_API_KEY or run in a terminal to log in");
+	if (!(options.stdinIsTTY ?? process.stdin.isTTY === true)) throw new AuthenticationError("Not logged in. Run applet login, or set HITCH_API_KEY.");
 	await (options.login ?? loginWithDevice)(instanceUrl, {
 		expectedOrg: orgCode,
 		fetch: fetcher,
@@ -347,4 +377,14 @@ async function fetchWithOrgAuth(orgCode, options, request) {
 	return request(organizationUrl, bearerToken(credentials));
 }
 //#endregion
-export { resolveInstanceUrl as i, organizationInstanceUrl as n, resolveAuthForOrg as r, fetchWithOrgAuth as t };
+//#region src/workspace.ts
+function resolveWorkspaceOrg(appletRoot) {
+	const appletsDir = dirname(appletRoot);
+	if (basename(appletsDir) === "applets") {
+		const config = readWorkspaceConfig(dirname(appletsDir));
+		if (config !== void 0) return config.org;
+	}
+	throw new Error(`No Hitch workspace found for ${appletRoot}. An applet must live at <workspace>/applets/<code> with hitch.config.ts in the workspace root.`);
+}
+//#endregion
+export { loginWithDevice as a, organizationInstanceUrl as c, resolveInstanceUrl as d, readWorkspaceConfig as i, rejectEnvironmentKey as l, fetchWithOrgAuth as n, AuthenticationError as o, findWorkspaceConfig as r, bearerToken as s, resolveWorkspaceOrg as t, resolveAuthForOrg as u };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hitch42/applet",
-  "version": "0.1.1-beta.6",
+  "version": "0.1.1-beta.8",
   "license": "MIT",
   "bin": {
     "applet": "./dist/applet.js"
@@ -27,6 +27,10 @@
       "source": "./src/react/index.ts",
       "default": "./dist/react.js"
     },
+    "./telephony": {
+      "source": "./src/telephony/index.ts",
+      "default": "./dist/telephony.js"
+    },
     "./vite": {
       "source": "./src/vite.ts",
       "default": "./dist/vite.js"
@@ -53,6 +57,7 @@
     "@tanstack/react-query-persist-client": "5.101.4",
     "@tanstack/router-cli": "^1.167.24",
     "@tanstack/router-plugin": "^1.168.23",
+    "@telnyx/webrtc": "^2.27.10",
     "@tiptap/core": "^3.30.3",
     "@tiptap/extension-image": "^3.30.3",
     "@tiptap/extension-list": "^3.30.3",

package/scaffold/.agents/skills/hitch-applets/SKILL.md

@@ -13,24 +13,27 @@ Treat each applet as an isolated microfrontend. Keep it separate from the data s
 
 This file holds the common rules. Read each matching reference before you edit an applet. Paths are relative to this file.
 
-| Read this                   | When the task involves                                                                                   |
-| --------------------------- | -------------------------------------------------------------------------------------------------------- |
-| `references/client.md`      | Client routes, navigation, page layout, forms, controls, or other user interface work                    |
-| `references/records.md`     | Listing, querying, creating, or updating records; filters, includes, aggregates; a missing record method |
-| `references/files.md`       | Uploading or reading files, attachment attributes, download links                                        |
-| `references/markdown.md`    | Rendering or editing markdown, image uploads, Hitch file links                                           |
-| `references/server.md`      | The applet server: secrets, env variables, external services, the `api` client                           |
-| `references/schedules.md`   | Cron schedules and background runs                                                                       |
-| `references/workflows.md`   | Multi-step server work: `createWorkflow`, `step.do`, `step.sleep`, starting, reading, and listing runs   |
-| `references/manifest.md`    | The applet definition in `applet.manifest.ts`: objects, access, variables, and packages                  |
-| `references/performance.md` | Data access design: client versus server, N+1 reads, includes, aggregates, pagination, batch writes      |
+| Read this                      | When the task involves                                                                                   |
+| ------------------------------ | -------------------------------------------------------------------------------------------------------- |
+| `references/client.md`         | Client routes, navigation, page layout, forms, controls, or other user interface work                    |
+| `references/records.md`        | Listing, querying, creating, or updating records; filters, includes, aggregates; a missing record method |
+| `references/files.md`          | Uploading or reading files, attachment attributes, download links                                        |
+| `references/email-tracking.md` | Creating pixels and reading raw email hits                                                               |
+| `references/markdown.md`       | Rendering or editing markdown, image uploads, Hitch file links                                           |
+| `references/server.md`         | The applet server: secrets, env variables, external services, the `api` client                           |
+| `references/schedules.md`      | Cron schedules and background runs                                                                       |
+| `references/workflows.md`      | Multi-step server work: `createWorkflow`, `step.do`, `step.sleep`, starting, reading, and listing runs   |
+| `references/manifest.md`       | The applet definition in `applet.manifest.ts`: objects, access, variables, and packages                  |
+| `references/performance.md`    | Data access design: client versus server, N+1 reads, includes, aggregates, pagination, batch writes      |
 
 For attribute types, filters, and API limits, read `../hitch-data/SKILL.md`. To inspect or change Hitch data and settings from the shell, read `../hitch-cli/SKILL.md`.
 
 ## Work with the workspace
 
 - Run package commands with `pnpm`.
-- If `package.json` is absent, read `sdk` from `hitch.config.ts`. Run `pnpm dlx <sdk> bootstrap` from the workspace root.
+- Run `pnpm exec applet login` from the workspace root or an applet directory to sign in. It uses the organization in `hitch.config.ts` and shares credentials with `hitch login`. Add `--no-browser` to print the sign-in URL without opening a browser.
+- A server permission error is not a login request.
+- After a workspace is linked to a repository, deploy in two ways. Run `pnpm exec applet deploy` to release a change immediately. Push to the production branch to deploy through CI and keep releases in sync with the repository.
 - Run `pnpm exec applet new <code>` from the workspace root to create a full applet.
 - Add `--client-only` or `--server-only` when the applet needs only one part.
 - Use `--client-only` for a user interface that uses the current user's Hitch access and needs no server.
@@ -44,16 +47,21 @@ For attribute types, filters, and API limits, read `../hitch-data/SKILL.md`. To
 - Run `pnpm --dir applets/<code> run generate` after a Hitch object, operation, or theme changes.
 - Run generation at the start of a session when the task depends on current Hitch types.
 - Run `pnpm --dir applets/<code> run dev` and `pnpm --dir applets/<code> run build` from the workspace root.
+- The dev server runs as you in the production org. Reads and writes use real data.
+- The dev server prints a preview link. Open the link to see the local applet inside Hitch.
+- Chrome asks once to allow local network access for the Hitch site.
+- The preview lasts until you select Stop preview or close the tab.
+- A pending `requiresChangeset` schema is not available in dev. Deploy to test it.
 - Run `pnpm --dir applets/<code> run deploy` only when the user requests a deployment.
-- Edit only `hitch.config.ts`, `applet.manifest.ts`, and files in `src`.
-- Treat all other workspace files as generated output. The applet CLI replaces them.
+- Edit only `hitch.config.ts`, `applet.manifest.ts`, files in `src`, and `.gitignore` rules below the generated block.
+- Treat all other workspace files as generated output. The applet CLI replaces them. It creates `.github/workflows/hitch.yml` only when the file is absent. To stop it, set `githubWorkflow: false` in `hitch.config.ts` and delete the file.
 - Remember that generation refreshes the local theme copy. Deployed applets load the public org theme from its Hitch `.com` URL.
 
 ## Use Vite and Vitest
 
 - Import configuration APIs from `vite`.
 - Import test APIs from `vitest`.
-- Keep Vite configuration in the generated `vite.config.ts` file.
+- Do not edit `vite.config.ts`. The applet CLI rewrites it. Do not add another Vite config.
 - Add applet packages to `dependencies` or `devDependencies` in `applet.manifest.ts`.
 
 ## Access Hitch data
@@ -121,7 +129,7 @@ Read `references/files.md` before download links, attachment attributes, or serv
 - Add useful `console.<level>` calls around important server work and failures. Deployed logs often provide the clearest evidence for applet issues.
 - Choose `console.log`, `console.info`, `console.warn`, or `console.error` deliberately. The console method sets the entry level used by log filters.
 - Run `pnpm --dir applets/<code> exec applet logs --filter '{"type":"applet"}'` from the workspace root to inspect applet code logs.
-- Include the applet type filter during diagnosis. Without it, Cloudflare invocation entries can hide the useful applet entries.
+- Include the applet type filter during diagnosis. Without it, Cloudflare invocation entries can hide the useful applet entries. For a workflow run, use `--run <id>` or `--filter '{"type":"workflow"}'` instead.
 - Do not log secrets, tokens, or personal data.
 
 ## Verify changes
@@ -138,3 +146,11 @@ pnpm --dir applets/<code> run build
 If missing packages block a check, stop package checks. Do not retry the check through another binary.
 
 If a command fails, report the exact blocker. Do not deploy as a verification step.
+
+## Deploy from GitHub
+
+- A push to the production branch runs `applet deploy` in the workspace root through GitHub Actions.
+- An applet deploys when its own folder changed since its current CI release. Every applet deploys when a file outside `applets/` changed. An applet without a CI release always deploys. An applet also deploys when CI cannot load the commit of its current release.
+- The deploy skips other applets and logs the reason. A skip is expected, not a failure.
+- A schema change in Hitch alone does not trigger CI.
+- Do not import from a sibling applet folder. The change check does not follow such imports.

package/scaffold/.agents/skills/hitch-applets/references/email-tracking.md

@@ -0,0 +1,49 @@
+# Email tracking
+
+Create one pixel for each email. Put its URL in the HTML before send.
+Add the pixel next to CID images. A CID image cannot make a tracking request.
+
+```ts
+const { id, url } = await hitch.email.tracking.createPixel({
+  tags: { campaignId: "fall", buyerId: "acme", version: "v2" },
+});
+const html = `<p>Hello</p><img src="${url}" width="1" height="1" alt="">`;
+// Send the email with the applet's email provider.
+await hitch.email.tracking.markSent({ id });
+```
+
+`markSent({ id, sentAt })` accepts an ISO time. A later call replaces the sent time.
+`get({ id })` returns one tracker. `list()` returns up to 100 trackers by default.
+Use `filter`, `sentAt`, `cursor`, and `limit` to select a page.
+
+```ts
+const tracker = await hitch.email.tracking.get({ id });
+const query = {
+  filter: { buyerId: "acme" },
+  sentAt: { $gte: "2026-10-01T00:00:00Z" },
+  limit: 100,
+};
+const page = await hitch.email.tracking.list(query);
+const next = page.nextCursor
+  ? await hitch.email.tracking.list({ ...query, cursor: page.nextCursor })
+  : null;
+const opened =
+  tracker.lastHitAt !== null &&
+  new Date(tracker.lastHitAt).getTime() >
+    new Date(tracker.sentAt ?? tracker.createdAt).getTime() + 60_000;
+```
+
+The example rule counts a tracker as opened when `lastHitAt` is more than 60 seconds after send or creation.
+Hitch records `firstHitAt` and `lastHitAt`. It does not classify opens.
+Each page must repeat the same filter, `sentAt`, and limit.
+
+Tags stay fixed after creation. Use at most 10 tags. A key starts with an ASCII letter.
+The rest contains ASCII letters, digits, or underscores, up to 64 characters total.
+Each value has 1 to 200 characters. A filter matches every tag by exact equality.
+Everyone with applet access sees all its trackers.
+
+Gmail can fetch through `GoogleImageProxy` a few seconds after send.
+A real Gmail open has the same user agent. A Gmail draft preview can fetch before send.
+Apple Mail Privacy Protection fetches on delivery with `Mozilla/5.0`.
+That fetch looks like a real open. Proton fetches on delivery.
+Clients with images off never fetch the pixel.

package/scaffold/.agents/skills/hitch-applets/references/files.md

@@ -67,7 +67,7 @@ Use `download` when a component needs one fresh link without query state:
 
 ```ts
 const file = await hitch.files.download(id);
-file.downloadUrl; // a download link, valid for one hour
+file.downloadUrl; // a download link, valid for at least a day
 ```
 
 Use the `get` query utilities when React needs file metadata as query state.
@@ -86,11 +86,11 @@ if (fileQuery.data) {
   row.filename; // "report.csv"
   row.contentType; // "text/csv"
   row.sizeBytes; // 1024
-  downloadUrl; // a download link, valid for one hour
+  downloadUrl; // a download link, valid for at least a day
 }
 ```
 
-A `downloadUrl` expires after one hour. Call `get` again for a fresh link instead of storing one.
+A `downloadUrl` expires after 24 to 48 hours. Call `get` again for a fresh link instead of storing one.
 
 ## Link a file to a record
 

package/scaffold/.agents/skills/hitch-applets/references/manifest.md

@@ -11,6 +11,7 @@ The applet tool reads `org` from `hitch.config.ts` in the workspace root.
 - `name` gives the applet a display name.
 - `code` gives the applet its stable code and URL prefix.
 - `objects` declares record objects and attribute access.
+- `requiresChangeset` optionally names the schema changeset that the code needs.
 - `variables` optionally declares runtime variables.
 - `schedules` optionally declares scheduled server calls.
 - `dependencies` optionally declares applet runtime packages.
@@ -42,6 +43,22 @@ The manifest and applet definition reject unknown fields.
 - Expect the Vite base path to be `/<code>/`.
 - Include the code in each client route path.
 
+## Set `requiresChangeset`
+
+Set `requiresChangeset` when the code needs a schema change that is not live yet.
+
+```ts
+requiresChangeset: "0192a1b2-c3d4-7e5f-8a9b-0c1d2e3f4a5b",
+```
+
+- Use the ID of a changeset in the same organization.
+- Generate, build, and deploy all use this field. The CLI has no changeset flag.
+- While the changeset is pending, types and the build use the schema that the changeset will produce.
+- While the changeset is pending, a deploy binds the release to the changeset. The release goes live when a person applies the changeset in Hitch.
+- After the changeset applies, the field uses the live schema. A deploy then promotes as usual. Remove the field when it is convenient.
+- A deploy fails when the changeset was abandoned. Remove the field or name a pending changeset.
+- A git push uses the same rules. The push never applies the changeset.
+
 ## Declare objects
 
 Add one entry for each object that the applet needs.
@@ -75,14 +92,16 @@ Each object entry has five required fields.
 
 The object declaration caps record access for the applet identity.
 
-- Declare only the objects that scheduled applet work needs.
-- Declare only the attributes that scheduled applet work needs.
+- Declare only the objects that the applet uses.
+- Declare only the attributes that the applet uses.
+- The declaration sets both the generated contract and the applet identity's cap.
 - Use `readOnly` for attributes that the applet identity must not change.
 - Use `readWrite` for attributes that the applet identity can change.
 - Set `canCreate` and `canDelete` to the required values.
 - The generated contract omits undeclared objects.
 - The generated contract removes `create` when `canCreate` is false.
 - The generated contract removes `delete` when `canDelete` is false.
+- The generated contract removes `update` and `updateWhere` when `readWrite` is empty.
 - Regenerate after an object grant changes.
 - Do not restore a removed object or method with a cast.
 

package/scaffold/.agents/skills/hitch-applets/references/performance.md

@@ -33,7 +33,7 @@ Never call `get` once per row of a list. Use one of these instead:
 ## Page every list
 
 - Every list request returns at most 200 records. A larger `limit` is clamped to 200 with no error.
-- Show a page size or a bounded scroll area in the product, with a next-page control that passes the returned `cursor`.
+- Show a page size or a bounded scroll area in the product, with a next-page control that passes the returned `next_cursor` as `cursor`.
 - Loop the cursor only when the code must visit the whole dataset. Name the bound in a comment, and stop at it.
 - Do not write a whole-dataset loop for a number that `aggregate` can return.
 

package/scaffold/.agents/skills/hitch-applets/references/records.md

@@ -97,7 +97,7 @@ const page = await hitch.records.deals.query({
 - Use a direct field value as shorthand for `$eq`.
 - Use `$eq`, `$in`, or `$not_empty` for identity fields.
 - Use `$eq` or `$not_empty` for checkbox fields.
-- Use only `$not_empty` for attachment fields.
+- Use `$eq`, `$in`, or `$not_empty` for attachment fields. Pass file IDs.
 - Use `$eq`, `$in`, `$not_empty`, `$contains`, `$starts_with`, or `$ends_with` for text fields.
 - Use `$eq`, `$in`, `$not_empty`, `$lt`, `$lte`, `$gt`, or `$gte` for ordered fields.
 - Use `$contains`, `$starts_with`, `$ends_with`, `$lt`, `$lte`, `$gt`, `$gte`, and `sort` only on an attribute with the `indexed` flag. Read `../../hitch-data/references/limits.md`.
@@ -106,11 +106,11 @@ const page = await hitch.records.deals.query({
 - Pass a string to `$contains`, `$starts_with`, and `$ends_with`.
 - Sort with `{ attribute, direction }`.
 - Use `asc` or `desc` as the sort direction.
-- Do not sort by multi-value, reference, user, or attachment attributes.
+- Do not sort by multi-value, reference, user, attachment, or rich text attributes.
 - Omit `sort` to sort by `createdAt` in descending order.
 - Use a positive integer for `limit`.
 - The service caps `limit` at 200 and uses 50 by default.
-- Pass the returned pagination cursor back as `cursor`.
+- Pass the returned `next_cursor` back as `cursor`. A null `next_cursor` means the last page.
 - Pass `include` as one string. Use the include name, which is the code without its `_id` or `_ids` suffix. Separate several names with commas.
 
 ## Aggregate records
@@ -148,6 +148,7 @@ The generated contract contains only objects declared in the manifest.
 
 - The contract removes `create` when `canCreate` is false.
 - The contract removes `delete` when `canDelete` is false.
+- The contract removes `update` and `updateWhere` when `readWrite` is empty.
 - Treat a missing method as a missing manifest grant, and edit the manifest when required.
 - Run generation after a manifest or Hitch schema change.
 - Do not bypass the contract with a cast.

package/scaffold/.agents/skills/hitch-applets/references/schedules.md

@@ -2,6 +2,12 @@
 
 Use a schedule to call an applet server procedure from a cron expression.
 
+## Local dev
+
+The dev server does not run cron.
+Run `pnpm --dir applets/<code> exec applet schedules run <schedule>` from the workspace root while `pnpm --dir applets/<code> run dev` runs.
+The run acts as you, not as the applet. The run writes real data.
+
 ## Define the target procedure
 
 - Add the target to the applet's server router.
@@ -44,7 +50,7 @@ schedules: [
 - The five fields are minute, hour, day of month, month, and day of week.
 - The registered router type checks the path after type generation.
 - A nested procedure uses its nested router path.
-- The scheduler invokes the named router procedure with no input.
+- The scheduler invokes the named router procedure with the input `{}`. Accept an empty object or declare no input.
 
 ## Understand the run identity
 
@@ -82,5 +88,4 @@ const uploaded = await hitch.files.upload(file);
 - Read the stored status, path, HTTP status, and error details.
 - Check the applet logs for procedure details.
 - Follow the log commands in the main Hitch applet skill.
-- Include `--level log` during diagnosis.
 - Do not log secrets, tokens, or personal data.

package/scaffold/.agents/skills/hitch-applets/references/server.md

@@ -29,9 +29,6 @@ export default { router };
 ```
 
 - Nest procedure objects when the applet needs nested paths.
-- Do not name a top-level procedure `hitch`.
-- The client reserves `hitch` for the Hitch data client.
-- The generated API client type rejects a router with that reserved key.
 
 ## Call the router from the client
 

package/scaffold/.agents/skills/hitch-applets/references/workflows.md

@@ -2,6 +2,15 @@
 
 Use a workflow for server work that runs in steps, retries a step, or waits between steps.
 
+## Local dev
+
+In `pnpm --dir applets/<code> run dev`, workflows run in the dev server as you. The server keeps runs in memory.
+Runs disappear when the dev server stops.
+In local dev, a step fails when it runs longer than 5 minutes. A deployed step can run for 15 minutes.
+Set `HITCH_DEV_SKIP_SLEEP=1` in the shell that runs `pnpm --dir applets/<code> run dev` to skip sleeps and step retry delays.
+A `.env` file does not set this value for the dev server.
+With this value, a polling loop that sleeps between checks calls Hitch without pause.
+
 ## Define a workflow
 
 - Import `createWorkflow` from `@hitch42/applet/server`.
@@ -63,11 +72,10 @@ export default { router, workflows };
 - Each step has the same limits as a scheduled run: 30,000 milliseconds of CPU and 1,000 subrequests.
 - A step that still fails after its retries throws inside the workflow function. Catch it to run a compensating step. An error you do not catch fails the run.
 - A run keeps the release it started on. A new release does not stop or change a run that is in progress or asleep.
-- An owner or admin can terminate an open run from the applet settings page. A terminated run has the status `terminated` and does not resume.
+- The owner or a member with the `applets:manage` capability can terminate an open run from the applet settings page. A terminated run has the status `terminated` and does not resume.
 
 ## Diagnose a failed run
 
 - Call `get(id)` and read `error`.
 - Workflow step output is in the applet logs with the type `workflow`, the run id, and the workflow code.
-- Run `applet logs <code> --run <id>` to see one run.
-- Include `--level log` during diagnosis.
+- Run `pnpm --dir applets/<code> exec applet logs --run <id>` from the workspace root to see one run.

package/scaffold/.agents/skills/hitch-cli/SKILL.md

@@ -12,25 +12,26 @@ The `hitch` command talks to one organization on one Hitch instance. Its data an
 ## Sign in
 
 - Run `hitch login` to sign in with the device flow. The command prints a URL and a code. Open the URL and confirm the code. Add `--no-browser` when the shell cannot open a browser.
+- `applet login` uses this same device flow and credential store. Both commands preselect the organization from `hitch.config.ts` at the workspace root or in an applet directory. Use `hitch login --org <code>` to select it explicitly.
 - Run `hitch login --api-key` to store an API key instead. The command prompts for the key. Pass `--api-key <key>` to skip the prompt.
-- Set `HITCH_API_KEY` to use a key for one shell session. It overrides every stored login. While it is set, `hitch login` and `hitch logout` refuse to run.
+- Set `HITCH_API_KEY` to use a key for one shell session. It overrides every stored login. While it is set, `hitch login`, `applet login`, and `hitch logout` refuse to run.
 - Run `hitch whoami` to print the current person, email, organization name, and organization id as JSON.
-- Run `hitch logout` to remove every stored login and cached command set.
-- Set `HITCH_API_URL` or pass `--instance <url>` to `hitch login` for an instance other than the default.
+- Run `hitch logout` to remove the stored logins and cached command sets for the current instance.
+- Set `HITCH_API_URL` for an instance other than the default. `hitch login --instance <url>` affects only that login. Set `HITCH_API_URL` too, so later commands use the same instance.
 
 ## Select the organization
 
 The CLI resolves the organization in this order. The first match wins.
 
 1. `--org <code>` on any command.
-2. The workspace organization: the `hitch.org` field in the nearest `package.json`, or in the workspace root when the current directory is an applet under `applets/`.
+2. The workspace organization: the `org` field in `hitch.config.ts` in the current directory, or in the workspace root when the current directory is an applet under `applets/`.
 3. `HITCH_DEFAULT_ORG`.
 
 There is no remembered active organization. When `--org` and the workspace disagree, the command fails with `--org "x" does not match workspace organization "y"`. When several organizations are stored and none is selected, the command fails and names the three ways to choose.
 
 ## Refresh the commands
 
-- Run `hitch sync` after a sign-in, after a schema change, and whenever `hitch --help` lacks an object. The command downloads the organization's API and caches the generated commands. It prints `Synced 3 objects.`
+- `hitch login` syncs the commands. Run `hitch sync` after a schema change, and whenever `hitch --help` lacks an object. The command downloads the organization's API and caches the generated commands. It prints `Synced 3 objects.`
 - If the CLI prints `the cached commands ... no longer load — run hitch sync`, run `hitch sync`. Until then only the built-in commands work.
 - The `admin` commands appear only when the signed-in identity holds an admin capability. A missing `admin` command means no capability, not a broken CLI.
 
@@ -40,11 +41,11 @@ Every generated command follows the API route.
 
 - Data commands: `hitch <object> <verb>`. The object is its code, for example `deals`. The verbs are `list`, `get`, `create`, `update`, `delete`, `query`, `update-where`, and `aggregate`. `hitch batch` sends a batch.
 - Admin commands: `hitch admin <route segments> <verb>`. The verb comes from the HTTP method: `list` or `get` for GET, `create` for POST, `update` for PATCH, `set` for PUT, `delete` for DELETE. For example `PUT /admin/v1/teams/{id}/members/{userId}` is `hitch admin teams members set`.
-- Every path, query, and body field becomes a flag in kebab case: `--id`, `--team-id`, `--can-read`. An object or array field takes JSON: `--filter '{"stage":"won"}'`.
+- Every path, query, and body field becomes a flag in kebab case: `--id`, `--team-id`, `--can-read`. An object field takes JSON: `--filter '{"stage":"won"}'`. An array field takes one JSON value per item: `--aggregates '{"op":"sum","attribute":"amount","as":"total"}' '{"op":"count","as":"n"}'`.
 - A required field is a required flag. The CLI does not prompt for a missing value. It prints the usage error.
 - Run `hitch <object> <verb> --help` to see the flags for that organization's schema.
 - Every `delete` command asks for confirmation. Pass `--yes` to skip it. A script without a terminal must pass `--yes`.
-- A command prints its result as JSON. A list prints one item per line. A command with no result prints nothing.
+- A command prints its result as JSON. A list prints one JSON object with `data` and `next_cursor`. A command with no result prints nothing.
 - An error prints `hitch: <message>` and exits with code 1.
 
 ## Work with records
@@ -59,8 +60,8 @@ hitch deals update --id 0192f1a2-3b4c-7d5e-8f60-123456789abc --stage won
 hitch deals delete --id 0192f1a2-3b4c-7d5e-8f60-123456789abc --yes
 hitch deals query --filter '{"stage":{"$in":["open","won"]}}' --sort '{"attribute":"createdAt","direction":"desc"}' --limit 50
 hitch deals update-where --filter '{"stage":"open"}' --set '{"stage":"lost"}' --expect 3
-hitch deals aggregate --aggregates '[{"op":"sum","attribute":"amount","as":"total"}]' --group-by '[{"attribute":"stage"}]'
-hitch batch --requests '[{"method":"POST","path":"/v1/deals","body":{"name":"A","stage":"open"}}]'
+hitch deals aggregate --aggregates '{"op":"sum","attribute":"amount","as":"total"}' --group-by '[{"attribute":"stage"}]'
+hitch batch --requests '{"method":"POST","path":"/v1/deals","body":{"name":"A","stage":"open"}}'
 ```
 
 - The filter, sort, include, aggregate, and batch bodies use the same shapes as the SDK. Read the `hitch-data` skill for the rules and limits.
@@ -106,22 +107,23 @@ hitch admin changesets update --id <changesetId> --adopt <otherChangesetId>
 
 - A schema command without `--changeset-id` applies at once when it has no blockers. With a blocker, Hitch stages it in a new pending changeset and names it in the error.
 - Add `--dry-run` to evaluate a schema command without a change.
-- Add `--indexed` to an attribute that a query must sort or filter with ordered or text operators. Add `--is-multi` for a multi-value attribute. Pass `--type-config` and `--options` as JSON.
+- Add `--indexed` to an attribute that a query must sort or filter with ordered or text operators. Add `--is-multi` for a multi-value attribute. Pass `--type-config` as JSON. Pass `--options` as one JSON value per option.
 - Run `blockers list` before an apply. Any blocker stops the apply with HTTP 409.
 - Run `hitch sync` after an apply, so the new objects and attributes appear as commands.
 - Run `pnpm --dir applets/<code> run generate` after an apply, so applet types match.
+- To build applet code before the apply, set `requiresChangeset` in `applet.manifest.ts` to the changeset ID. Generate, build, and deploy then use the changeset schema, and the release goes live when the changeset applies.
 
 ## Fix common errors
 
-| Message                                              | Cause and fix                                                                            |
-| ---------------------------------------------------- | ---------------------------------------------------------------------------------------- |
-| `Not logged in. Run hitch login.`                    | No stored login and no `HITCH_API_KEY`. Sign in.                                         |
-| `HITCH_API_KEY was rejected.`                        | The key in the environment is invalid or revoked. Unset it or replace it.                |
-| `API key is scoped to organization "x", not "y".`    | The key belongs to another organization. Select `x` or use another key.                  |
-| `--org "x" does not match workspace organization`    | Run the command outside the workspace, or drop `--org`.                                  |
-| `Multiple organizations are stored ...`              | Pass `--org`, set `hitch.org`, or set `HITCH_DEFAULT_ORG`.                               |
-| `the cached commands ... no longer load`             | Run `hitch sync`.                                                                        |
-| `Refusing to delete without --yes`                   | Add `--yes` in a script.                                                                 |
-| `hitch <object>` is an unknown command               | Run `hitch sync`. The object is new or the cache is stale.                               |
-| `User's teams lack the `read` grant on this object.` | The identity has no grant on that object. Ask for a team grant, or use another identity. |
-| `hitch admin` is missing                             | The identity holds no admin capability.                                                  |
+| Message                                              | Cause and fix                                                                                        |
+| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
+| `Not logged in. Run hitch login.`                    | No stored login and no `HITCH_API_KEY`. Sign in.                                                     |
+| `HITCH_API_KEY was rejected.`                        | The key in the environment is invalid or revoked. Unset it or replace it.                            |
+| `API key is scoped to organization "x", not "y".`    | The key belongs to another organization. Select `x` or use another key.                              |
+| `--org "x" does not match workspace organization`    | Run the command outside the workspace, or drop `--org`.                                              |
+| `Multiple organizations are stored ...`              | Pass `--org`, use the workspace `hitch.config.ts`, or set `HITCH_DEFAULT_ORG`.                       |
+| `the cached commands ... no longer load`             | Run `hitch sync`.                                                                                    |
+| `Refusing to delete without --yes`                   | Add `--yes` in a script.                                                                             |
+| `hitch <object>` is an unknown command               | Run `hitch whoami`. If you are signed in, run `hitch sync`. The object is new or the cache is stale. |
+| `User's teams lack the `read` grant on this object.` | The identity has no grant on that object. Ask for a team grant, or use another identity.             |
+| `hitch admin` is missing                             | The identity holds no admin capability.                                                              |

package/scaffold/.agents/skills/hitch-data/SKILL.md

@@ -42,10 +42,10 @@ An organization's data lives in Hitch objects. Each object has attributes. Each
 - Every attribute accepts `$eq` and `$not_empty`. Every attribute except checkbox accepts `$in`.
 - Ordered operators, text-match operators, and `sort` need the `indexed` flag on the attribute. A new attribute starts with the flag off. Ask for the flag on the attributes a query needs, not on every attribute.
 - A filter can nest through a reference, through an inverse face, and can express an anti-join with `$not`.
-- An aggregate filter does not need the flag. Sum, average, minimum, and maximum need a single-value numeric attribute. A group dimension is a checkbox, select, reference, user, or a bucketed date or datetime.
+- Aggregating or grouping by an attribute does not need the flag. An aggregate filter follows the same flag rules as a query filter. Sum, average, minimum, and maximum need a single-value numeric attribute. A group dimension is a checkbox, select, reference, user, or a bucketed date or datetime.
 
 ## Schema changes
 
 - Every object or attribute change goes through a changeset. Hitch evaluates the change against existing records and dependent applets.
 - A change that would break existing data, such as a unique constraint with duplicates, is blocked until the data is fixed.
-- An applet release can bind to a pending changeset. The changeset apply switches the schema and promotes the release together.
+- An applet release can bind to a pending changeset. Set `requiresChangeset` in `applet.manifest.ts` to bind it. The changeset apply switches the schema and promotes the release together.

package/scaffold/.agents/skills/hitch-data/references/limits.md

@@ -8,15 +8,15 @@ Some limits clamp with no error. Some reject the request. Design for both.
 
 A page is the unit of a read. A screen shows one page and asks for the next one. A page holds at most 200 root records. An included reference has no cap on linked records, so include only small links.
 
-| Limit                              | Value       | Past the limit                   |
-| ---------------------------------- | ----------- | -------------------------------- |
-| `limit` on `list` and `query`      | 50 default  | Clamped to 200, no error         |
-| `limit` on `list` and `query`, max | 200         | Clamped to 200, no error         |
-| Filter nesting depth               | 20          | HTTP 400                         |
-| `include` depth                    | 1           | HTTP 400 for a dotted path       |
-| `include` on an inverse reference  | Not allowed | HTTP 400                         |
-| Records per included reference     | No cap      | All linked records return        |
-| IDs in one `$in` array             | No cap      | Only 200 records return per page |
+| Limit                              | Value       | Past the limit                                        |
+| ---------------------------------- | ----------- | ----------------------------------------------------- |
+| `limit` on `list` and `query`      | 50 default  | Clamped to 200, no error                              |
+| `limit` on `list` and `query`, max | 200         | `list` clamps to 200; the `query` schema rejects more |
+| Filter nesting depth               | 20          | HTTP 400                                              |
+| `include` depth                    | 1           | HTTP 400 for a dotted path                            |
+| `include` on an inverse reference  | Not allowed | HTTP 400                                              |
+| Records per included reference     | No cap      | Every linked record the caller can read returns       |
+| IDs in one `$in` array             | No cap      | Only 200 records return per page                      |
 
 ## Aggregates
 
@@ -56,7 +56,7 @@ Advanced filters and sorting are opt-in per attribute. This keeps each record ch
 - Ordered operators, text-match operators, and `sort` need the `indexed` flag on the attribute. Without it the request fails with HTTP 400 and a message that starts with `Enable advanced filters and sort for`.
 - New attributes start with `indexed` off. Ask the organization admin to turn it on for the attributes a query needs. Do not ask for it on every attribute.
 - No attribute allows `sort` when it is multi-value, rich text, reference, user, or attachment.
-- An aggregate filter does not need `indexed`. Sum, average, minimum, and maximum need a single-value numeric attribute.
+- Aggregating or grouping by an attribute does not need `indexed`. An aggregate filter follows the same `indexed` rules as a query filter. Sum, average, minimum, and maximum need a single-value numeric attribute.
 
 ## Grant conditions