@mindstudio-ai/remy 0.1.73 → 0.1.75

package/dist/headless.js

@@ -2328,13 +2328,17 @@ var runScenarioTool = {
   clearable: true,
   definition: {
     name: "runScenario",
-    description: "Run a scenario to seed the dev database with test data. Truncates all tables first, then executes the seed function and impersonates the scenario roles. Blocks until complete. Scenario IDs are defined in mindstudio.json. If it fails, check .logs/tunnel.log or .logs/requests.ndjson for details. Return synchronously - no need to sleep before checking results.",
+    description: "Run a scenario to seed the dev database with test data. By default truncates all tables first, then executes the seed function and impersonates the scenario roles. Use skipTruncate to run the seed function against existing data without resetting. Blocks until complete. Scenario IDs are defined in mindstudio.json. If it fails, check .logs/tunnel.log or .logs/requests.ndjson for details. Return synchronously - no need to sleep before checking results.",
     inputSchema: {
       type: "object",
       properties: {
         scenarioId: {
           type: "string",
           description: "The scenario ID from mindstudio.json."
+        },
+        skipTruncate: {
+          type: "boolean",
+          description: "When true, skip the database reset step and run the seed function against existing data. Defaults to false (clean-slate)."
         }
       },
       required: ["scenarioId"]
@@ -2371,6 +2375,28 @@ var runMethodTool = {
   }
 };
 
+// src/tools/code/queryDatabase.ts
+var queryDatabaseTool = {
+  clearable: true,
+  definition: {
+    name: "queryDatabase",
+    description: "Execute a raw SQL query against the dev database and return the results. Use for inspecting data and debugging issues.",
+    inputSchema: {
+      type: "object",
+      properties: {
+        sql: {
+          type: "string",
+          description: "The SQL query to execute."
+        }
+      },
+      required: ["sql"]
+    }
+  },
+  async execute() {
+    return "ok";
+  }
+};
+
 // src/subagents/common/analyzeImage.ts
 var VISION_MODEL = "gemini-3-flash";
 var VISION_MODEL_OVERRIDE = JSON.stringify({
@@ -4595,6 +4621,7 @@ var ALL_TOOLS = [
   editsFinishedTool,
   runScenarioTool,
   runMethodTool,
+  queryDatabaseTool,
   screenshotTool,
   browserAutomationTool,
   // LSP

package/dist/index.js

@@ -2001,13 +2001,17 @@ var init_runScenario = __esm({
       clearable: true,
       definition: {
         name: "runScenario",
-        description: "Run a scenario to seed the dev database with test data. Truncates all tables first, then executes the seed function and impersonates the scenario roles. Blocks until complete. Scenario IDs are defined in mindstudio.json. If it fails, check .logs/tunnel.log or .logs/requests.ndjson for details. Return synchronously - no need to sleep before checking results.",
+        description: "Run a scenario to seed the dev database with test data. By default truncates all tables first, then executes the seed function and impersonates the scenario roles. Use skipTruncate to run the seed function against existing data without resetting. Blocks until complete. Scenario IDs are defined in mindstudio.json. If it fails, check .logs/tunnel.log or .logs/requests.ndjson for details. Return synchronously - no need to sleep before checking results.",
         inputSchema: {
           type: "object",
           properties: {
             scenarioId: {
               type: "string",
               description: "The scenario ID from mindstudio.json."
+            },
+            skipTruncate: {
+              type: "boolean",
+              description: "When true, skip the database reset step and run the seed function against existing data. Defaults to false (clean-slate)."
             }
           },
           required: ["scenarioId"]
@@ -2052,6 +2056,34 @@ var init_runMethod = __esm({
   }
 });
 
+// src/tools/code/queryDatabase.ts
+var queryDatabaseTool;
+var init_queryDatabase = __esm({
+  "src/tools/code/queryDatabase.ts"() {
+    "use strict";
+    queryDatabaseTool = {
+      clearable: true,
+      definition: {
+        name: "queryDatabase",
+        description: "Execute a raw SQL query against the dev database and return the results. Use for inspecting data and debugging issues.",
+        inputSchema: {
+          type: "object",
+          properties: {
+            sql: {
+              type: "string",
+              description: "The SQL query to execute."
+            }
+          },
+          required: ["sql"]
+        }
+      },
+      async execute() {
+        return "ok";
+      }
+    };
+  }
+});
+
 // src/subagents/common/analyzeImage.ts
 async function analyzeImage(params) {
   const { prompt, imageUrl, timeout = 2e5, onLog } = params;
@@ -4585,6 +4617,7 @@ var init_tools5 = __esm({
     init_restartProcess();
     init_runScenario();
     init_runMethod();
+    init_queryDatabase();
     init_screenshot2();
     init_browserAutomation();
     init_designExpert();
@@ -4624,6 +4657,7 @@ var init_tools5 = __esm({
       editsFinishedTool,
       runScenarioTool,
       runMethodTool,
+      queryDatabaseTool,
       screenshotTool,
       browserAutomationTool,
       // LSP

package/dist/prompt/compiled/auth.md

@@ -149,7 +149,7 @@ import { auth } from '@mindstudio-ai/agent';
 
 ### `auth.requireRole(...roles)`
 
-Throws 403 if the current user doesn't have **any** of the specified roles.
+Throws 401 (unauthenticated) if there is no current user. Throws 403 (forbidden) if the current user doesn't have **any** of the specified roles.
 
 ```typescript
 auth.requireRole('admin');
@@ -162,7 +162,7 @@ Returns `boolean`. Same logic as `requireRole` but doesn't throw.
 
 ### `auth.userId`
 
-The current user's ID (the row ID in the auth table). Always available when auth is enabled.
+The current user's ID (the row ID in the auth table), or `null` for unauthenticated requests. Check for null before using in database queries when the method might be called without auth.
 
 ### `auth.roles`
 
@@ -221,7 +221,7 @@ import { auth } from '@mindstudio-ai/agent';
 import { Users } from './tables/users';
 
 export async function getDashboard() {
-  const user = await Users.get(auth.userId);
+  const user = auth.userId ? await Users.get(auth.userId) : null;
 
   if (auth.hasRole('admin')) {
     const allUsers = await Users.toArray();

package/dist/prompt/compiled/methods.md

@@ -100,8 +100,8 @@ const { markdown } = await agent.scrapeUrl({
   url: 'https://example.com',
 });
 
-// Look up a user from your auth table
-const user = await Users.get(auth.userId);
+// Look up a user from your auth table (auth.userId is null if unauthenticated)
+const user = auth.userId ? await Users.get(auth.userId) : null;
 ```
 
 No separate API keys needed — the platform routes to the correct provider (OpenAI, Anthropic, Google, etc.) automatically.
@@ -127,7 +127,7 @@ export async function approveVendor(input: { vendorId: string }) {
 }
 ```
 
-`auth.requireRole()` throws a 403 automatically if the user doesn't have the required role.
+`auth.requireRole()` throws 401 if unauthenticated, 403 if the user doesn't have the required role.
 
 ## Common Patterns
 
@@ -159,8 +159,8 @@ export async function deleteVendor(input: { vendorId: string }) {
   const vendor = await Vendors.get(input.vendorId);
   if (!vendor) throw new Error('Vendor not found.');
 
-  await Vendors.remove(input.vendorId);
-  return { success: true };
+  const { deleted } = await Vendors.remove(input.vendorId);
+  return { deleted };
 }
 ```
 

package/dist/prompt/compiled/tables.md

@@ -142,10 +142,15 @@ The conflict key must match a declared `unique` constraint on the table. Throws
 
 ### Reading Records
 
+All read methods return lazy `Query` objects — nothing executes until `await`. Every read method (including `get()`, `findOne()`, `count()`, etc.) is batchable via `db.batch()`.
+
 ```typescript
 // By ID
 const vendor = await Vendors.get('uuid-here');  // Vendor | null
 
+// All rows
+const allVendors = await Vendors.toArray();
+
 // Find one matching a predicate
 const first = await Vendors.findOne(v => v.status === 'approved');
 
@@ -159,13 +164,15 @@ const results = await Vendors
   .skip(10)
   .take(5);
 
-// Aggregates
+// Aggregates — all return Query objects (batchable)
 const count = await Vendors.count();
 const any = await Vendors.some(v => v.status === 'pending');
-const all = await Vendors.every(v => v.status !== 'rejected');
-const empty = await Vendors.isEmpty();
 const cheapest = await Vendors.min(v => v.totalCents);
 const grouped = await Vendors.groupBy(v => v.status);
+
+// These two return Promises directly (not batchable)
+const all = await Vendors.every(v => v.status !== 'rejected');
+const empty = await Vendors.isEmpty();
 ```
 
 ### Updating Records
@@ -181,9 +188,9 @@ const updated = await Vendors.update(vendor.id, {
 ### Deleting Records
 
 ```typescript
-await Vendors.remove(vendor.id);                                    // by ID
-const count = await Vendors.removeAll(v => v.status === 'rejected'); // by predicate
-await Vendors.clear();                                               // delete all
+const { deleted } = await Vendors.remove(vendor.id);                 // { deleted: boolean }
+const count = await Vendors.removeAll(v => v.status === 'rejected'); // number (count removed)
+const cleared = await Vendors.clear();                               // number (count deleted)
 ```
 
 ### Filter Predicates
@@ -234,6 +241,11 @@ const user = await Users.upsert('email', data).catch(err => {
 });
 ```
 
+Write methods throw `MindStudioError` with specific codes:
+- `push()` → `'insert_failed'` (500) if the insert returns no row
+- `update()` → `'row_not_found'` (404) if the ID doesn't exist
+- `upsert()` → `'missing_conflict_key'` (400) if the conflict column is missing from the data, `'no_unique_constraint'` (400) if no matching unique constraint is declared
+
 ### Batching
 
 `db.batch()` combines multiple operations into a single HTTP round-trip. Every `await` on a table operation is a network call, so batching is critical for performance. Use it whenever you have multiple reads, writes, or a mix of both. `upsert()` works in batches just like `push()` and `update()`:
@@ -262,7 +274,7 @@ const [_, newOrder, pending] = await db.batch(
 
 **Always batch instead of sequential awaits.** A loop with `await Table.update()` inside makes N separate HTTP calls. Mapping to mutations and passing them to `db.batch()` makes one.
 
-**Note:** `Table.get(id)` is a direct async method that returns `Promise<T | null>` — it does not return a `Query` and cannot be passed to `db.batch()`. To batch a get-by-id, use `Table.filter(row => row.id === someId).first()` instead, which returns a batchable `Query`.
+**Note:** Almost all read methods return batchable `Query` objects — including `get()`, `findOne()`, `count()`, `some()`, `min()`, `max()`, and `groupBy()`. The exceptions are `every()` and `isEmpty()`, which return Promises directly and cannot be batched.
 
 ## Migrations
 

package/dist/subagents/browserAutomation/prompt.md

@@ -142,6 +142,7 @@ You can use the `screenshotFullPage` tool to take a full-height screenshot of th
   - The snapshot in the response is always the most current page state. Even if a wait times out, check the snapshot field; the content you were waiting for may have appeared by then.
   - Execution stops on first error. If step 2 of 5 fails, steps 3-5 don't run. The response will contain results for steps 0-2 (with step 2 having an error field) plus the current snapshot. Adjust and retry from the failed step.
   - Always call `resetBrowser` as your final action after all tests are complete. This restores the preview to a clean state for the user.
+  - If something fails, bail early. Do not attempt to diagnose why; do not do things like attempt different inputs to try to work around an error - just report the failure and early return.
 </rules>
 
 <voice>

package/dist/subagents/codeSanityCheck/prompt.md

@@ -27,6 +27,7 @@ These are things we already know about and have decided to accept:
   - react-textarea-autosize
 - Preferences:
   - use [wouter](https://github.com/molefrog/wouter) for React routing instead of reaching for react-router
+  - uploading user files should mostly always happen via @mindstudio-ai/interface's platform.uploadFile() - it does the whole signed S3 upload dance and returns a permanent CDN url, including query-string-resizable images, videos + auto-thumbnails, etc.
 
 ### Common pitfalls (always flag these)
 

package/dist/subagents/designExpert/prompts/images.md

@@ -62,10 +62,21 @@ Remember: It's 2026. Everything is lifestyle and editorial these days. Even a la
 Default to photography with real subjects — people, scenes, moments, environments. Use editorial and fashion photography vocabulary in your prompts. When abstract art is the right call (textures, editorial collages, gradient art), make it bold and intentional, not generic gradient blobs.
 
 #### Match style to context
+
 Editorial photography is the right call for hero images, landing pages, marketing sites, and branding. But when generating images for scenario seed data — sample posts, user uploads, profile content, anything that's supposed to look like a real user created it — the target is authentic user-generated content, not a photographer's portfolio. A social app's seed photos should look like they came from someone's phone camera roll in 2026: well-lit because the phone's computational photography is good, but casually framed, slightly imperfect, real-life backgrounds. Think "my friend posted this on Instagram" not "Unsplash top pick." The difference between a compelling demo and a fake-feeling one is whether the seed content feels like real people made it.
 
 The developer should never need to source their own imagery. Always provide URLs.
 
+### Icons and logos
+
+App icons and logos require work and thinking to get right. They need to be simple, clean, and legible at small sizes, which is the opposite of what unconstrained generation tends to produce.
+
+**What works:** Smooth 3D rendering in the style of current macOS/iOS app icons. One clear, simplified object or symbol — chunky, rounded, toy-like proportions. Clean surfaces with soft lighting and gentle shadows. Two or three accent colors, not a rainbow. Always generate with `transparentBackground: true`.
+
+**What doesn't work:** Flat illustration look dated, photorealistic rendering is too noisy at small sizes, overly detailed scenes becomes illegible, clay/matte textures read as craft projects, not real apps.
+
+Generate multiple variants — small-size readability is hard to predict from a prompt. What looks great at full resolution may turn to mush at 64px. When reviewing generated icons, mentally shrink them to favicon size and ask if the subject is still recognizable.
+
 ### When to use images
 
 Include image recommendations in your designs when the product calls for it. A landing page without photography feels like a wireframe. A feature section with a real image feels finished. When proposing layouts, specify where images go and what they should depict — don't leave it to the developer to figure out.

package/dist/subagents/designExpert/tools/images/enhance-image-prompt.md

@@ -46,6 +46,17 @@ For photorealistic images, be specific about:
 
 **Casual / phone photography:** When the brief calls for candid, user-generated, or social-media-style photos, steer away from professional photography language. Instead describe the qualities of a good 2026 smartphone photo: sharp subject with computational HDR, natural ambient lighting, slightly busy or imperfect backgrounds, centered or off-center casual framing, no deliberate composition or artistic bokeh. The subject should look like someone pointed their phone and tapped — not posed, not art-directed. Describe it as "phone photo" or "iPhone photo" style, not "digital photography with shallow depth of field." Real people's photos are well-lit (phones are good now) but unpolished — a messy kitchen counter in frame, a friend mid-laugh with eyes half-closed, a dog blurry because it moved. That imperfection is what makes them feel authentic.
 
+## Icons and logos
+
+For app icons and logos, the goal is something that reads clearly at small sizes and feels polished enough to sit on a home screen or in an app header.
+
+- Frame as "A 3D icon against a white background:" followed by the subject. Do NOT use the phrase "app icon" — it triggers mockup framing (the model renders an icon inset on a phone screen or mounted on a wall). "3D icon" works.
+- Describe smooth, rounded, simplified 3D objects — think current macOS/iOS app icon design language. Clean surfaces, soft lighting, gentle shadows. Not flat illustration, not photorealistic, not clay/matte.
+- Subjects should be chunky, toy-like, and immediately recognizable. Prefer one clear object or symbol, not a scene. Simplify aggressively — detail that looks good at 1024px becomes mud at 64px.
+- Specify "reads well at small sizes" as an explicit constraint.
+- Keep color intentional and limited — two or three accent colors plus the object's base tone. Colors should complement the app's brand if known.
+- Always use transparent background for icons and logos.
+
 ## Output
 
 Respond with ONLY the enhanced prompt. 3-5 sentences maximum. Be specific and visual, not abstract or conceptual.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mindstudio-ai/remy",
-  "version": "0.1.73",
+  "version": "0.1.75",
   "description": "MindStudio coding agent",
   "repository": {
     "type": "git",