fix(release): Firecrawl start-relative depth, secret-key redaction, operation-backed credential contract, and audit cleanups

Author: waleedlatif1

.github/CI.md

@@ -10,7 +10,7 @@ Docs production builds run once and publish an artifact to isolated HTTP, corpus
 
 | Change | Expensive checks selected |
 | --- | --- |
-| Independent SDK | That workspace's tests and type-check; no app build, services, or browsers |
+| Standalone package | That workspace's tests and type-check; no app build, services, or browsers |
 | App unit test | App test shards and test type check |
 | Integration test | Both provision paths; no HTTP/browser job merely for the test edit |
 | Workspace UI | Database integration, mobile, SEO and live Electron, plus app tests/build |

.github/CONTRIBUTING.md

@@ -140,20 +140,15 @@ Using clear and consistent commit messages makes it easier for everyone to under
 
 To set up your local development environment:
 
-### Option 1: Using NPM Package (Simplest)
+### Option 1: Using the Setup Wizard (Simplest)
 
-The easiest way to run Sim locally is using our NPM package:
+Inside your clone, run the interactive setup wizard:
 
 ```bash
-npx simstudio
+bun run sim-setup
 ```
 
-After running this command, open [http://localhost:3000/](http://localhost:3000/) in your browser.
-
-#### Options
-
-- `-p, --port <port>`: Specify the port to run Sim on (default: 3000)
-- `--no-pull`: Skip pulling the latest Docker images
+It provisions the database, generates secrets, writes `.env`, and offers the source-only local development and Kubernetes modes. Outside a clone, `npx sim-setup` sets up a deployment from the published images instead.
 
 #### Requirements
 

apps/docs/content/docs/platform/self-hosting/networking.mdx

@@ -292,7 +292,7 @@ The practical consequence: a mandatory-egress-proxy environment can route LLM tr
 A request through the SSRF guard keeps its checks when it is proxied. Before each request, and again for each redirect hop, the app resolves the destination's hostname with its own DNS and refuses it if any policy in [Security](/platform/self-hosting/security#the-ssrf-boundary) blocks the address. It then hands the hostname, not the address, to the proxy, so a proxy that allowlists by domain sees the name it expects.
 
 - **DNS must still resolve inside the container.** A destination that the app cannot resolve is refused before the proxy is asked.
-- **The proxy resolves the name again.** The app cannot pin the address across a proxy, so the proxy's own egress policy is the last check.
+- **The proxy resolves the name again.** The app cannot pin the address across a proxy, so a name that answers differently to the proxy (a short-TTL rebind, or split-horizon DNS) reaches whatever the proxy resolves. The proxy's own egress policy is the last check: it must refuse private, loopback, and link-local ranges (including `169.254.169.254`) and your internal DNS zones, the same addresses the app's guard refuses.
 - **`https` destinations are tunneled** with `CONNECT host:443`. **`http` destinations are forwarded** to the proxy as an absolute URL, as curl and Bun do.
 - **Proxy credentials** go in the URL, e.g. `http://user:pass@proxy.internal:3128`. They are sent only to the proxy. An `https://` proxy URL also works; SOCKS proxies are not supported.
 - **The HTTP block's `proxyUrl`** still takes precedence for that one request.
@@ -301,6 +301,8 @@ A request through the SSRF guard keeps its checks when it is proxied. Before eac
 
 Set `NO_PROXY` for every destination that is not on the public internet, not just model endpoints. The app reaches the realtime server (`SOCKET_SERVER_URL`), the Presidio PII service (`PII_URL`), and itself (`INTERNAL_API_BASE_URL`) over the same default `fetch`, alongside self-hosted Ollama, LiteLLM, and vLLM — so a proxy that cannot reach your internal network breaks live updates and PII redaction, not only inference. AWS clients and OTLP export follow the same rule, so also add an internal S3-compatible store such as MinIO, AWS VPC endpoints, and an in-cluster OpenTelemetry collector.
 
+`NO_PROXY` matches hostnames, domain suffixes (`.internal` or `*.internal`), exact IP addresses, and an optional `:port`, or `*` alone for everything. It does not match CIDR ranges such as `10.0.0.0/8` or IPv6 addresses, so list internal destinations by name.
+
 Set it in the application environment, not your shell — under `app.env` on Helm, or the service's `environment:` on Compose. On Helm the suffixes alone are not enough: the chart wires `SOCKET_SERVER_URL`, `PII_URL`, and `OLLAMA_URL` to bare Service names, which no domain suffix matches. Add those names too — `helm template` prints the rendered ones, and the prefix is the release name unless it already contains `sim`, in which case it is the release name alone:
 
   ```yaml

apps/sim/app/(landing)/components/navbar/components/nav-menu-chip/constants.ts

@@ -128,14 +128,14 @@ export const RESOURCES_MENU: NavMenu = {
       items: [
         {
           title: 'Docs',
-          description: 'Guides, SDKs, and API reference',
+          description: 'Guides, CLI, and API reference',
           href: 'https://docs.sim.ai',
           external: true,
           preview: {
             kind: 'docs',
             eyebrow: 'Documentation',
             title: 'Build with Sim',
-            details: ['Quickstart', 'SDKs', 'API reference'],
+            details: ['Quickstart', 'CLI', 'API reference'],
           },
         },
         {

apps/sim/blocks/blocks/mistral_parse.ts

@@ -384,7 +384,7 @@ export const MistralParseV3Block: BlockConfig = {
       id: 'imageLimit',
       title: 'Max Images',
       type: 'short-input',
-      placeholder: 'Up to 100 (default 100)',
+      placeholder: '1 to 100 (default 100)',
       condition: { field: 'includeImageBase64', value: true },
       mode: 'advanced',
     },
@@ -463,7 +463,8 @@ export const MistralParseV3Block: BlockConfig = {
           parameters.includeImageBase64 = true
           parameters.imageLimit = parseOptionalNumberInput(params.imageLimit, 'Max Images', {
             integer: true,
-            min: 0,
+            min: 1,
+            max: 100,
           })
           parameters.imageMinSize = parseOptionalNumberInput(
             params.imageMinSize,

apps/sim/lib/compare/data/sim.ts

@@ -134,13 +134,13 @@ export const simProfile: CompetitorProfile = {
   facts: {
     platform: {
       builderType: {
-        value: 'Visual drag-and-drop canvas, natural-language (Chat), or code (API/SDK)',
+        value: 'Visual drag-and-drop canvas, natural-language (Chat), or code (REST API and CLI)',
         shortValue: 'Visual canvas, chat, or code',
         confidence: 'verified',
         sources: [
           {
             url: 'https://docs.sim.ai/introduction',
-            label: 'Sim Docs: Introduction (visual, natural-language, and API/SDK building)',
+            label: 'Sim Docs: Introduction (visual, natural-language, and API building)',
             asOf: '2026-07-08',
           },
         ],
@@ -155,7 +155,7 @@ export const simProfile: CompetitorProfile = {
         sources: [
           {
             url: 'https://docs.sim.ai/introduction',
-            label: 'Sim Docs: Introduction (visual, natural-language, and API/SDK building)',
+            label: 'Sim Docs: Introduction (visual, natural-language, and API building)',
             asOf: '2026-07-08',
           },
         ],

apps/sim/lib/core/security/redaction.test.ts

@@ -31,6 +31,9 @@ describe('isSensitiveKey', () => {
     'exa_api_key',
     'secretAccessKey',
     'awsSecretAccessKey',
+    'secretKey',
+    'bedrockSecretKey',
+    'deployKey',
     `${'a'.repeat(10000)}password`,
   ])('treats %s as sensitive', (key) => {
     expect(isSensitiveKey(key)).toBe(true)
@@ -39,7 +42,8 @@ describe('isSensitiveKey', () => {
   it.concurrent.each([
     'tokenCount',
     'tokenizer',
-    'secretKey',
+    'secretKeyId',
+    'deployKeyName',
     'passwordStrength',
     'authMethod',
     'name',

apps/sim/lib/core/security/redaction.ts

@@ -29,6 +29,10 @@ const SENSITIVE_KEY_PATTERNS: RegExp[] = [
   /^.*api[_-]?key$/i,
   // AWS's `secretAccessKey` / `awsSecretAccessKey`, which no suffix above covers.
   /^.*secret[_-]?access[_-]?key$/i,
+  // Credential fields named for the key itself: Clerk's `secretKey`, Bedrock's
+  // `bedrockSecretKey`, and Convex's `deployKey`.
+  /^.*secret[_-]?key$/i,
+  /^.*deploy[_-]?key$/i,
   /^passphrase$/i,
   /^authorization$/i,
   /^proxy[_-]?authorization$/i,

apps/sim/lib/credentials/service-account-secret.ts

@@ -388,7 +388,9 @@ async function buildTokenServiceAccountSecret(
     providerId,
     apiToken,
     ...(requiresDomain ? { domain: validation.normalizedDomain ?? domain } : {}),
-    ...(requiresWorkspace ? { providerWorkspaceId } : {}),
+    ...(requiresWorkspace
+      ? { providerWorkspaceId: validation.normalizedWorkspaceId ?? providerWorkspaceId }
+      : {}),
     metadata: { ...validation.storedMetadata, ...principalMetadata },
   }
   const { encrypted } = await encryptSecret(JSON.stringify(blob))

apps/sim/lib/credentials/token-service-accounts/server.ts

@@ -271,6 +271,8 @@ export interface TokenServiceAccountValidationResult {
   storedMetadata?: Record<string, string>
   /** Normalized domain to persist instead of the raw user input (when collected). */
   normalizedDomain?: string
+  /** Normalized account id to persist, so the stored id is the one the check verified. */
+  normalizedWorkspaceId?: string
 }
 
 export type TokenServiceAccountValidator = (