stack dev -> hexclave dev

apps/dashboard/src/app/api/development-environment/health/route.ts

@@ -17,9 +17,9 @@ function shellQuote(value: string): string {
 
 function devRestartCommand(configFilePath: string | undefined): string {
   if (configFilePath == null) {
-    return "stack dev --config-file <path-to-stack.config.ts> -- <your app command>";
+    return "hexclave dev --config-file <path-to-hexclave.config.ts> -- <your app command>";
   }
-  return `stack dev --config-file ${shellQuote(configFilePath)} -- <your app command>`;
+  return `hexclave dev --config-file ${shellQuote(configFilePath)} -- <your app command>`;
 }
 
 function healthResponse(body: HealthResponse, status: number): NextResponse<HealthResponse> {

apps/dashboard/src/app/development-environment/browser-secret/page-client.tsx

@@ -114,7 +114,7 @@ export function BrowserSecretConfirmationPageClient() {
         </div>
         <h1 className="text-2xl font-semibold tracking-tight">Authorize this browser</h1>
         <p className="mt-3 text-sm leading-6 text-muted-foreground">
-          This dashboard is reachable through a forwarded address. To keep it private, enter the 6-character confirmation code shown by the running <code className="rounded bg-black/[0.04] dark:bg-white/[0.06] px-1 py-0.5 text-xs">stack dev</code> command.
+          This dashboard is reachable through a forwarded address. To keep it private, enter the 6-character confirmation code shown by the running <code className="rounded bg-black/[0.04] dark:bg-white/[0.06] px-1 py-0.5 text-xs">hexclave dev</code> command.
         </p>
         <p className="mt-3 text-sm text-muted-foreground">{expiresText}</p>
         <form className="mt-5 space-y-4" onSubmit={(event) => {

apps/dashboard/src/app/layout-client.tsx

@@ -94,7 +94,7 @@ async function refreshDevEnvironmentHealth() {
     }
     setSnapshotIfCurrent({
       status: "unhealthy",
-      restartCommand: "stack dev --config-file <path-to-stack.config.ts> -- <your app command>",
+      restartCommand: "hexclave dev --config-file <path-to-hexclave.config.ts> -- <your app command>",
     });
   }
 }

docs-mintlify/guides/apps/authentication/cli-authentication.mdx

@@ -7,7 +7,7 @@ sidebarTitle: CLI App Authentication
 If you're building your own command-line application, you can use Hexclave to let users log in from a terminal.
 
 <Info>
-  This page is about adding authentication to your own CLI app. For the official `stack` command, see the [Stack CLI guide](/guides/going-further/cli).
+  This page is about adding authentication to your own CLI app. For the official Hexclave CLI, see the [Hexclave CLI guide](/guides/going-further/cli).
 </Info>
 
 To do so, we provide a Python template that you can use as a starting point. [Download it here](https://github.com/hexclave/hexclave/tree/main/docs/public/stack-auth-cli-template.py) and copy it into your project, for example:

docs-mintlify/guides/going-further/cli.mdx

@@ -1,7 +1,7 @@
 ---
-title: "Stack CLI"
+title: "Hexclave CLI"
 description: "Use the Hexclave CLI to manage config and run admin scripts"
-sidebarTitle: "Stack CLI"
+sidebarTitle: "Hexclave CLI"
 ---
 
 import { hexclaveAgentRemindersText } from "/snippets/hexclave-agent-reminders.jsx";

docs-mintlify/guides/going-further/local-vs-cloud-dashboard.mdx

@@ -8,7 +8,7 @@ Hexclave has two common ways to work with a project:
 
 | Option | Best for | How it is configured |
 | --- | --- | --- |
-| Local dashboard | Development | A local `hexclave.config.ts` file plus `stack dev --config-file ...`. |
+| Local dashboard | Development | A local `hexclave.config.ts` file plus `hexclave dev --config-file ...`. |
 | Cloud dashboard | Production | A hosted project on [app.hexclave.com](https://app.hexclave.com) with project ID and keys in your app environment. |
 
 ## Development Environment
@@ -33,13 +33,13 @@ export const config: HexclaveConfig = "show-onboarding";
 ```json title="package.json"
 {
   "scripts": {
-    "dev": "stack dev --config-file ./hexclave.config.ts -- npm run dev:inner",
+    "dev": "hexclave dev --config-file ./hexclave.config.ts -- npm run dev:inner",
     "dev:inner": "<your-existing-dev-script>"
   }
 }
 ```
 
-For the full config file reference, see [`hexclave.config.ts`](/guides/going-further/hexclave-config). For CLI details, see [Stack CLI](/guides/going-further/cli).
+For the full config file reference, see [`hexclave.config.ts`](/guides/going-further/hexclave-config). For CLI details, see [Hexclave CLI](/guides/going-further/cli).
 
 ## Cloud Dashboard
 

examples/demo/hexclave.config.ts

@@ -2,7 +2,7 @@
  * Hexclave project configuration as code (demo app).
  *
  * Source of truth for RBAC permissions/roles, auth methods, OAuth providers,
- * sign-up rules, API keys, and payment plans. The Hexclave CLI (`stack dev`)
+ * sign-up rules, API keys, and payment plans. The Hexclave CLI (`hexclave dev`)
  * bundles + executes this file and provisions the project to match.
  *
  * It's wrapped in `defineHexclaveConfig(...)`, so the shared-backend config updater takes

packages/cli/src/lib/dev-env-state.test.ts

@@ -131,7 +131,7 @@ describe("dev env state", () => {
     }
     // A hand-edited / cross-version file with a non-string version would
     // otherwise reach parseVersionCore (version.trim()) and throw, crashing
-    // `stack dev` outside the auto-update fail-open guard. Drop the entry.
+    // `hexclave dev` outside the auto-update fail-open guard. Drop the entry.
     writeFileSync(statePath, JSON.stringify({
       version: 1,
       localDashboardsByPort: { "26700": { port: 26700, secret: "s", pid: 999, startedAtMillis: 1, version: 2 } },

packages/shared/src/helpers/init-prompt.ts

@@ -9,7 +9,7 @@ The Hexclave CLI already created or linked this project to a local Hexclave deve
 ${configPath}
 \`\`\`
 
-Do not create or link another Hexclave project. When the SDK setup instructions mention creating \`stack.config.ts\` or wrapping the dev script with \`stack dev --config-file\`, use the config file path above.
+Do not create or link another Hexclave project. When the SDK setup instructions mention creating \`hexclave.config.ts\` or wrapping the dev script with \`hexclave dev --config-file\`, use the config file path above.
 `;
   }