@softr/sdk 0.0.92-emailotc.0 → 0.0.93-alpha.0

package/skills/softr-sdk/charts-and-metrics/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91
+  library_version: 0.0.93-alpha.0
 ---
 
 **Boundary.** `ds` lives on `@softr/sdk/server` and runs only inside a `createServerFn` handler or a server-side route hook — importing it into a component fails the build. `defineQuery` and every type come from `@softr/sdk` and can be imported anywhere.

package/skills/softr-sdk/current-user/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91
+  library_version: 0.0.93-alpha.0
 ---
 
 # The current user

package/skills/softr-sdk/file-uploads/SKILL.md

@@ -7,7 +7,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91
+  library_version: 0.0.93-alpha.0
 ---
 
 **Boundary.** `upload` lives on `@softr/sdk/server` and runs inside server functions. `useFileUpload` and `FileItem` live on `@softr/sdk` and run in components. `FileAttachment` comes from `@softr/sdk` and can be imported anywhere.

package/skills/softr-sdk/formatting/SKILL.md

@@ -8,7 +8,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91
+  library_version: 0.0.93-alpha.0
 ---
 
 # Dates, times and numbers

package/skills/softr-sdk/integrations/SKILL.md

@@ -7,7 +7,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91
+  library_version: 0.0.93-alpha.0
 ---
 
 **Boundary.** `integration` lives on `@softr/sdk/server` and runs only inside a `createServerFn` handler — importing it into a component fails the build. `defineIntegration` and every type come from `@softr/sdk` and can be imported anywhere.

package/skills/softr-sdk/mcp/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91
+  library_version: 0.0.93-alpha.0
 ---
 
 **Boundary.** `softrMcpMiddleware` lives on `@softr/sdk` and is registered once, in `src/start.ts`. The actions you hand it are the same `defineQuery` / `defineMutation` values the app's own pages use — declared wherever they already live, not duplicated for MCP.
@@ -53,10 +53,25 @@ The list is the whole tool surface. Write it out:
 
 - An action you leave out is invisible to the assistant, even where the app's pages use it freely.
 - An action you list still obeys its own `permissions`. Listing it does not widen who may run it — the assistant runs as whoever signed in, with that user's groups.
+- The assistant calls the action directly and skips server functions, so a row filter written in one does not apply. A listed read returns every row the user's data restrictions allow, and a listed update or delete takes any id that passes them. On a table whose rows belong to people, list an action only once a data restriction scopes the table to the user's own rows.
+- A create on a table whose rows belong to a person gets its owner from `owner`, never from the assistant. See below.
 - Two actions with the same `id` throw at startup. So does anything that is not a `defineQuery` or `defineMutation` value.
 
 Reads first. Add a write only when the user asked for one, and name it back to them.
 
+## The owner of a person's record
+
+The assistant knows the caller's login, not their row in the people table. Left to fill an owner link, it writes the login id, which shows as a stray name, or anyone's row it likes. `owner` takes the field out of the tool and fills it with the caller's own row, found the way `auth.currentUserRow` finds it:
+
+```ts
+softrMcpMiddleware({
+  actions: [listRequests, requestTimeOff],
+  owner: { users: usersQuery, email: 'email', fields: { requestTimeOff: 'employee' } },
+})
+```
+
+`fields` maps each create or update action id to its owner link. A caller with no row in the people table is refused, and nothing is created. On an update the field is only taken out, so nobody moves a record to someone else.
+
 ## The login round trip
 
 Connecting starts with an approval page the app serves. Most people hit it signed out, and that page cannot sign anyone in. It sends them to the login page named in `softr.json` (`auth.routes.login.path`), with the approval page in the search param named there (`auth.routes.login.redirectParam`).

package/skills/softr-sdk/pwa/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91
+  library_version: 0.0.93-alpha.0
 ---
 
 # Installing the app

package/skills/softr-sdk/record-mutations/SKILL.md

@@ -8,7 +8,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91
+  library_version: 0.0.93-alpha.0
 ---
 
 **Boundary.** `ds` lives on `@softr/sdk/server` and runs only inside a `createServerFn` handler — importing it into a component fails the build. `defineMutation` and every type come from `@softr/sdk` and can be imported anywhere.

package/skills/softr-sdk/record-queries/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91
+  library_version: 0.0.93-alpha.0
 ---
 
 **Boundary.** `ds` lives on `@softr/sdk/server` and runs only inside a `createServerFn` handler or a server-side route hook — importing it into a component fails the build. The same holds for any helper that calls `ds`: declare it inside the handler. A function at module level that calls `ds` keeps the server-only import in the browser bundle, and every page stops loading until it moves. `defineQuery` and every type come from `@softr/sdk` and can be imported anywhere.

package/skills/softr-sdk/region-visibility/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91
+  library_version: 0.0.93-alpha.0
 ---
 
 **Boundary.** `Audience` and `defineVisibility` come from `@softr/sdk` and work anywhere.

package/skills/softr-sdk/routes-and-visibility/SKILL.md

@@ -3,13 +3,13 @@ name: routes-and-visibility
 description: >-
   Add a route file and declare its settings: definePage with its visibility
   (LOGGED_IN_USERS, NON_LOGGED_IN_USERS and customGroups) and its title,
-  guardRoute or assertRouteAccess in beforeLoad, pageHead in head,
-  isAuthorized and checkAccess anywhere, rendering an access error, and the
-  lint rules that require the declaration.
+  guardRoute or assertRouteAccess in beforeLoad, pageHead in head, isAuthorized
+  and checkAccess anywhere, rendering an access error, and the lint rules that
+  require the declaration.
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91
+  library_version: 0.0.93-alpha.0
 ---
 
 **Boundary.** `definePage`, `pageHead`, the access functions and the error predicates come from `@softr/sdk` and work anywhere.

package/skills/softr-sdk/workflows/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91
+  library_version: 0.0.93-alpha.0
 ---
 
 **Boundary.** `workflow` lives on `@softr/sdk/server` and runs only inside a `createServerFn` handler — importing it into a component fails the build. `defineWorkflow` and every type come from `@softr/sdk` and can be imported anywhere.

package/dist/auth/methods/emailCode2fa.d.ts

@@ -1,34 +0,0 @@
-import { User } from "../user.js";
-import { AuthError, Result } from "./utils.js";
-
-//#region src/auth/methods/emailCode2fa.d.ts
-
-/**
- * Finishes a sign-in that answered `emailCodeRequired`, with the code emailed
- * to the visitor.
- *
- * A `signedIn` result means the visitor is signed in. An app that also asks for
- * an authenticator app answers `authenticatorRequired` instead, naming the step
- * to send them to next.
- */
-declare function verifyEmailCode(details: {
-  code: string;
-}): Promise<Result<{
-  status: "signedIn";
-  user: User;
-} | {
-  status: "authenticatorRequired";
-  /**
-   * `verify`: they have an authenticator app and owe a code.
-   * `setup`: the app requires one and they have none yet.
-   * `setupOptional`: same, except they may skip it instead.
-   */
-  step: "verify" | "setup" | "setupOptional";
-}, AuthError>>;
-/**
- * Emails the code for {@link verifyEmailCode} again. Asking again within a
- * short wait sends nothing and still succeeds.
- */
-declare function resendEmailCode(): Promise<Result<null, AuthError>>;
-//#endregion
-export { resendEmailCode, verifyEmailCode };

package/dist/auth/methods/emailCode2fa.js

@@ -1,71 +0,0 @@
-import { assert, panic } from "../../assertions.js";
-import { writeCookies } from "../../cookies.js";
-import { sessionConfig } from "../config.js";
-import { clearPendingAuth, makePendingAuthCookie, makeSessionDataCookie, makeSessionTokenCookie, readPendingAuthToken } from "../session.js";
-import { makePlatform } from "../platform.js";
-import { authError } from "./utils.js";
-
-//#region src/auth/methods/emailCode2fa.ts
-/**
-* Finishes a sign-in that answered `emailCodeRequired`, with the code emailed
-* to the visitor.
-*
-* A `signedIn` result means the visitor is signed in. An app that also asks for
-* an authenticator app answers `authenticatorRequired` instead, naming the step
-* to send them to next.
-*/
-async function verifyEmailCode(details) {
-	const result = await makePlatform(sessionConfig().applicationId).emailCodeVerify(readPendingAuthToken(), details.code);
-	if (!result.ok) {
-		if (result.status === 400 || result.status === 401) return authError("invalidCode", result.message);
-		if (result.status === 429) return authError("tooManyAttempts", result.message);
-		if (result.status >= 500) panic(`Expected to verify the emailed code, but got ${result.status}: ` + result.message);
-		throw new Error(`${result.message}. Check SOFTR_APPLICATION_ID and that the app asks for an emailed code at sign-in.`);
-	}
-	if (result.data.status === "MFA_REQUIRED") {
-		const { mfa } = result.data;
-		assert(mfa, "Expected a challenge from verification, but got none");
-		writeCookies([makePendingAuthCookie(mfa.challengeToken)]);
-		return {
-			success: true,
-			data: {
-				status: "authenticatorRequired",
-				step: mfa.action === "VERIFICATION_REQUIRED" ? "verify" : mfa.action === "SETUP_REQUIRED" ? "setup" : "setupOptional"
-			}
-		};
-	}
-	const { session } = result.data;
-	assert(session, "Expected a session from verification, but got none");
-	writeCookies([...makeSessionTokenCookie(session.jwt), makeSessionDataCookie({
-		user: session.user,
-		permissions: session.permissions
-	}, session.jwt)]);
-	clearPendingAuth();
-	return {
-		success: true,
-		data: {
-			status: "signedIn",
-			user: session.user
-		}
-	};
-}
-/**
-* Emails the code for {@link verifyEmailCode} again. Asking again within a
-* short wait sends nothing and still succeeds.
-*/
-async function resendEmailCode() {
-	const result = await makePlatform(sessionConfig().applicationId).emailCodeResend(readPendingAuthToken());
-	if (!result.ok) {
-		if (result.status === 401) return authError("notAuthenticated", result.message);
-		if (result.status === 429) return authError("tooManyAttempts", result.message);
-		if (result.status >= 500) panic(`Expected the code to be emailed again, but got ${result.status}: ` + result.message);
-		throw new Error(`${result.message}. Check SOFTR_APPLICATION_ID and that the app asks for an emailed code at sign-in.`);
-	}
-	return {
-		success: true,
-		data: null
-	};
-}
-
-//#endregion
-export { resendEmailCode, verifyEmailCode };