@starlein/paperclip-plugin-company-wizard 0.4.16 → 0.4.18

package/dist/ui/index.js

@@ -581,7 +581,7 @@ var __iconNode45 = [
 var Zap = createLucideIcon("zap", __iconNode45);
 
 // src/ui/components/WizardShell.tsx
-import { useEffect as useEffect9 } from "react";
+import { useEffect as useEffect9, useRef as useRef8 } from "react";
 
 // src/ui/context/WizardContext.tsx
 import { createContext, useCallback, useContext, useState } from "react";
@@ -679,6 +679,8 @@ function reducer(state, action) {
     }
     case "GO_TO":
       return { ...state, step: action.step, error: null };
+    case "RESTORE_NAV":
+      return { ...state, path: action.path, step: action.step, error: null };
     case "SET_COMPANY_NAME":
       return { ...state, companyName: action.value };
     case "SET_GOALS":
@@ -4024,6 +4026,19 @@ CardFooter.displayName = "CardFooter";
 
 // src/ui/components/steps/StepOnboarding.tsx
 import { Fragment, jsx as jsx3, jsxs } from "react/jsx-runtime";
+async function upgradeInstalledPlugin(pluginId, version) {
+  const response = await fetch(`/api/plugins/${encodeURIComponent(pluginId)}/upgrade`, {
+    method: "POST",
+    headers: { "Content-Type": "application/json" },
+    credentials: "include",
+    body: JSON.stringify({ version })
+  });
+  if (!response.ok) {
+    const body = await response.json().catch(() => null);
+    throw new Error(body?.error || `Plugin upgrade failed (${response.status})`);
+  }
+  return response.json();
+}
 function PathCard({
   icon: Icon2,
   title,
@@ -4060,9 +4075,12 @@ function StepOnboarding() {
   const dispatch = useWizardDispatch();
   const refreshTemplates = usePluginAction("refresh-templates");
   const checkUpdate = usePluginAction("check-update");
+  const preparePluginUpdate = usePluginAction("prepare-plugin-update");
   const [refreshing, setRefreshing] = useState2(false);
   const [refreshMsg, setRefreshMsg] = useState2(null);
   const [updateInfo, setUpdateInfo] = useState2(null);
+  const [pluginUpdating, setPluginUpdating] = useState2(false);
+  const [pluginUpdateMsg, setPluginUpdateMsg] = useState2(null);
   useEffect(() => {
     let cancelled = false;
     checkUpdate({}).then((result) => {
@@ -4090,6 +4108,43 @@ function StepOnboarding() {
       setRefreshing(false);
     }
   };
+  const handlePluginUpdate = async () => {
+    setPluginUpdating(true);
+    setPluginUpdateMsg("Updating templates...");
+    try {
+      const prepared = await preparePluginUpdate({});
+      if (!prepared?.ok) {
+        throw new Error(prepared?.error || "Could not prepare plugin update");
+      }
+      if (!prepared.updateAvailable) {
+        setUpdateInfo({
+          ok: true,
+          currentVersion: prepared.currentVersion,
+          latestVersion: prepared.latestVersion,
+          updateAvailable: false
+        });
+        setPluginUpdateMsg("Templates updated. Plugin is already current.");
+        return;
+      }
+      if (!prepared.pluginId || !prepared.latestVersion) {
+        throw new Error("Could not resolve installed plugin record or target version");
+      }
+      setPluginUpdateMsg(`Installing Company Wizard ${prepared.latestVersion}...`);
+      await upgradeInstalledPlugin(prepared.pluginId, prepared.latestVersion);
+      setUpdateInfo({
+        ok: true,
+        currentVersion: prepared.latestVersion,
+        latestVersion: prepared.latestVersion,
+        updateAvailable: false
+      });
+      setPluginUpdateMsg("Plugin updated. Reloading...");
+      window.setTimeout(() => window.location.reload(), 1200);
+    } catch (err) {
+      setPluginUpdateMsg(err instanceof Error ? err.message : "Plugin update failed");
+    } finally {
+      setPluginUpdating(false);
+    }
+  };
   return /* @__PURE__ */ jsxs("div", { className: "space-y-8", children: [
     /* @__PURE__ */ jsxs("div", { className: "space-y-2", children: [
       /* @__PURE__ */ jsx3("h1", { className: "text-2xl font-semibold tracking-tight", children: "Create a company" }),
@@ -4147,7 +4202,7 @@ function StepOnboarding() {
         "button",
         {
           onClick: handleRefresh,
-          disabled: refreshing,
+          disabled: refreshing || pluginUpdating,
           className: "flex items-center gap-1.5 text-xs text-muted-foreground hover:text-foreground transition-colors disabled:opacity-50",
           children: [
             /* @__PURE__ */ jsx3(RefreshCw, { className: cn("h-3 w-3", refreshing && "animate-spin") }),
@@ -4163,14 +4218,28 @@ function StepOnboarding() {
           updateInfo.currentVersion,
           " \u2192 ",
           updateInfo.latestVersion,
+          /* @__PURE__ */ jsxs(
+            "button",
+            {
+              type: "button",
+              onClick: handlePluginUpdate,
+              disabled: pluginUpdating,
+              className: "inline-flex items-center gap-1 font-medium text-foreground hover:underline disabled:opacity-50 disabled:no-underline",
+              title: "Install the latest Company Wizard plugin, refresh templates, and reload",
+              children: [
+                /* @__PURE__ */ jsx3(RefreshCw, { className: cn("h-3 w-3", pluginUpdating && "animate-spin") }),
+                pluginUpdating ? "Updating..." : "Update now"
+              ]
+            }
+          ),
           updateInfo.url && /* @__PURE__ */ jsxs(
             "a",
             {
               href: updateInfo.url,
               target: "_blank",
               rel: "noreferrer",
-              className: "inline-flex items-center gap-0.5 font-medium text-foreground hover:underline",
-              title: "Update the Company Wizard plugin package, then reload Paperclip",
+              className: "inline-flex items-center gap-0.5 text-muted-foreground hover:text-foreground hover:underline",
+              title: "Open the npm package page",
               children: [
                 "npm",
                 /* @__PURE__ */ jsx3(ExternalLink, { className: "h-3 w-3" })
@@ -4179,6 +4248,16 @@ function StepOnboarding() {
           )
         ] })
       ] }),
+      pluginUpdateMsg && /* @__PURE__ */ jsx3(
+        "span",
+        {
+          className: cn(
+            "basis-full text-center text-xs",
+            pluginUpdateMsg.includes("failed") || pluginUpdateMsg.includes("Could not") ? "text-destructive" : "text-muted-foreground"
+          ),
+          children: pluginUpdateMsg
+        }
+      ),
       refreshMsg && /* @__PURE__ */ jsx3("span", { className: "text-xs text-muted-foreground", children: refreshMsg })
     ] })
   ] });
@@ -6184,10 +6263,10 @@ function StepSummary() {
 import { useState as useState8, useRef as useRef4, useEffect as useEffect5 } from "react";
 import { usePluginAction as usePluginAction4 } from "@paperclipai/plugin-sdk/ui";
 
-// raw:/paperclip/paperclip-plugin-company-wizard/src/ui/prompts/interview-system.md
+// raw:/home/runner/work/paperclip-plugin-company-wizard/paperclip-plugin-company-wizard/src/ui/prompts/interview-system.md
 var interview_system_default = 'You are the Company Wizard \u2014 an expert at assembling AI agent teams. You\'re enthusiastic but concise. Company Wizard bootstraps AI-agent company workspaces from composable templates.\n\nYou are conducting a guided interview to understand what company to set up.\n\n{{CATALOG}}\n\n## How Roles Work\n\n- **Base roles** (marked "always included") are auto-added. You do NOT list them in the JSON.\n- **All other roles** (listed under "Available Extra Roles") are OPTIONAL and must be EXPLICITLY listed in your JSON `roles` array if you want them.\n- **Critically: `engineer` is NOT a base role.** Most software projects need an engineer. If the project involves writing code, building software, or maintaining a repository, you MUST include `engineer` in your `roles` array. The preset does NOT auto-add roles \u2014 you must list every non-base role the company needs.\n- When in doubt, include the engineer. A company that builds software without an engineer agent will have no one to write code.\n\n## Interview Rules\n\n- Ask exactly ONE question per turn. Keep it short and energetic (1-2 sentences). Use a conversational tone.\n- Do NOT output JSON during questions \u2014 just ask the question as plain text.\n- Tailor each question based on previous answers. Show you understood what they said.\n- After 3 questions, summarize what you understood in a brief, enthusiastic paragraph. End with: "Ready to generate your configuration?"\n- When the user confirms, output a human-readable recommendation with reasoning, then the JSON config.\n\n## What to Ask About\n\nAcross your 3 questions, try to cover as many of these as the user\'s initial description left unclear:\n\n1. **What they\'re building** \u2014 Product type, target users, domain (fintech, SaaS, game, etc.)\n2. **Current stage** \u2014 Greenfield, existing codebase, research phase, relaunch?\n3. **Quality vs speed** \u2014 Ship fast, iterate? Or production-grade, high quality from the start?\n4. **Team needs** \u2014 Do they need code review, security, design, marketing, docs, DevOps?\n5. **Special requirements** \u2014 Compliance, accessibility, specific tech stack, CI/CD, game engine?\n6. **Repository** \u2014 Should Paperclip create a new Git repository/workspace, or should the agents use an existing external repo such as GitHub/GitLab? If external, ask for URL and branch/ref; never ask for tokens.\n\nDon\'t ask about things already clear from the initial description. Skip to what\'s missing.\n\n## Information Preservation\n\nThe user\'s interview answers are the primary source of context for the company. When generating the configuration:\n\n- **`companyDescription`**: Write a comprehensive 2-4 paragraph description that captures EVERYTHING learned during the interview \u2014 what the company does, what it\'s building, who it\'s for, key technical decisions, constraints, priorities, and any special context. This is the company\'s permanent record. Be thorough. Do NOT summarize into a single vague sentence.\n- **`goals`**: Array of goals. The first goal is the main user-specific company goal \u2014 its description is the most important field. Keep it outcome-first and product-first: the title and opening sentence must state the primary deliverable or operating outcome, not a supporting constraint. Write a THOROUGH, DETAILED description that includes EVERYTHING the user shared: full requirements, technical specs, acceptance criteria, constraints, edge cases, API contracts, user stories, design decisions, performance targets. Put compliance/security/accessibility/performance constraints in a clearly labelled "Constraints / quality bars" section unless the user explicitly says that constraint is the primary project. If the user\'s wording mixes a main outcome with secondary facts, determine which thing the agents should build/operate first and write that as the top-level goal; put side facts into acceptance criteria, risks, or sub-goals only when they are independent workstreams. Preset/module template goals are added by the wizard after your JSON, so do NOT replace the user\'s objective with generic preset goals like "Build a REST API" or "Set up CI/CD" unless the user explicitly asked only for that.\n- **`projects`**: Array of projects. Each has a `name`, `description`, `goals` array (goal titles it\'s linked to), and repository workspace metadata. If the user chose an external repo, use `workspace.sourceType: "git_repo"` with `repoUrl`, plus `repoRef`/`defaultRef` exactly when the user or repository context provides one; do not force a branch name or remote prefix. If no external repo was provided, use a fresh local Git repository with `workspace.sourceType: "local_path"`, `workspace.defaultRef: "main"` unless the user requested another initial branch, `workspace.setupCommand: "git init -b <defaultRef>"`, and `workspace.isPrimary: true`. Do not include `executionWorkspacePolicy`; the assembler applies isolated worktrees only when Paperclip\'s experimental isolated-workspaces setting is enabled and a usable project base ref exists.\n- **`issues`**: Array of 6-12 CONCRETE, domain-specific initial work items taken straight from what you learned in the interview \u2014 the real features, components, and integrations the user actually described, each with a `title`, a `description` with acceptance criteria, a `priority` (`critical`/`high`/`medium`/`low`), and `assignTo` set to a role on the team. These seed the backlog so the project starts in its actual domain. Issue titles should lead with the core product capability; secondary constraints belong in acceptance criteria or risk notes unless the issue is specifically about that constraint. Do NOT put generic scaffolding here (vision docs, linters, CI, branch protection) \u2014 the wizard adds those automatically.\n\n## RECOMMENDATION Format (when generating config)\n\n- One paragraph explaining your reasoning: why this preset, why these modules, why these roles.\n- A bullet list of the key choices.\n\nThen output the JSON (no markdown fences):\n{{CONFIG_FORMAT}}\n\n## Rules\n\n- `modules` should list ALL modules to activate (including preset ones).\n- `roles` should list ALL non-base roles the company needs. This includes roles that come with the preset. The system does not auto-add preset roles \u2014 you must list them explicitly.\n- If the project involves building software, `engineer` MUST be in `roles`.\n- The primary project MUST state whether it uses a fresh local Git repository or an external Git repository. Do not put credentials or tokens in repository fields.\n- Be pragmatic \u2014 don\'t over-engineer. Match the config to actual needs.\n';
 
-// raw:/paperclip/paperclip-plugin-company-wizard/src/ui/prompts/single-shot-system.md
+// raw:/home/runner/work/paperclip-plugin-company-wizard/paperclip-plugin-company-wizard/src/ui/prompts/single-shot-system.md
 var single_shot_system_default = 'You are the Company Wizard. Company Wizard bootstraps AI-agent company workspaces from composable templates.\n\nGiven a natural language description of what the user wants to build, you select the best configuration.\n\n{{CATALOG}}\n\n## How Roles Work\n\n- **Base roles** (marked "always included") are auto-added. You do NOT list them in the JSON.\n- **All other roles** (listed under "Available Extra Roles") are OPTIONAL and must be EXPLICITLY listed in your JSON `roles` array if you want them.\n- **Critically: `engineer` is NOT a base role.** Most software projects need an engineer. If the project involves writing code, building software, or maintaining a repository, you MUST include `engineer` in your `roles` array. The preset does NOT auto-add roles \u2014 you must list every non-base role the company needs.\n- When in doubt, include the engineer. A company that builds software without an engineer agent will have no one to write code.\n\n## Instructions\n\n1. Analyze the user\'s description to understand: what they\'re building, their team size preference, quality vs speed priority, and any specific needs.\n2. Select the best preset as a starting point.\n3. List ALL modules to activate (including preset ones). Add extra modules beyond the preset if the description warrants them.\n4. List ALL non-base roles the company needs. This includes roles from the preset. If the project involves software, include `engineer`.\n5. Suggest a company name (PascalCase-friendly, short, memorable) if not obvious from the description.\n6. Write a thorough company description (2-4 paragraphs) capturing everything the user described \u2014 product, audience, tech stack, constraints, priorities, stage, and special context. This is the company\'s permanent record.\n7. Define goals as an array. The first goal is the main user-specific company goal \u2014 its description is the most important field. Keep it **outcome-first and product-first**: the title and opening sentence must state the primary deliverable or operating outcome, not a supporting constraint. Preserve compliance, security, accessibility, performance, tech-stack, and domain constraints inside the description under a clear "Constraints / quality bars" section unless the user explicitly says that constraint is the primary project. If the user\'s wording mixes a main outcome with secondary facts, ask yourself which thing the agents should build/operate first and write that as the top-level goal; put side facts into acceptance criteria, risks, or sub-goals only when they are independent workstreams. Include EVERYTHING the user described: full requirements, technical specs, acceptance criteria, constraints, edge cases, API contracts, user stories, performance targets. If the user provided a detailed spec, reproduce it in full, but do not let one constraint dominate the goal or initial issues. Preset/module template goals are added by the wizard after your JSON, so do NOT replace the user\'s objective with generic preset goals like "Build a REST API" or "Set up CI/CD" unless the user explicitly asked only for that.\n8. Define projects as an array. Most setups need one project linked to all goals. Name and describe the project concretely.\n9. Always decide the repository setup for the primary project:\n   - If the user gives an existing GitHub/GitLab/remote Git repo, set `workspace.sourceType: "git_repo"`, include `repoUrl`, and set `repoRef`/`defaultRef` exactly when the user or repository context provides one. Do not force a branch name or remote prefix; Paperclip\'s project/worktree settings decide the worktree base ref.\n   - If no external repository is given, assume Paperclip should create a fresh local Git repository. Set `workspace.sourceType: "local_path"`, `workspace.defaultRef: "main"` unless the user requested another initial branch, `workspace.setupCommand: "git init -b <defaultRef>"`, and `workspace.isPrimary: true`. Do NOT include an `executionWorkspacePolicy`; the assembler applies isolated worktrees only when Paperclip\'s experimental isolated-workspaces setting is enabled and a usable project base ref exists.\n   - Never include credentials or tokens in repository URLs or project text.\n10. Define an `issues` array of 6-12 CONCRETE, domain-specific initial work items taken straight from the description \u2014 the real features, components, and integrations the user actually described, each with a `title`, a `description` with acceptance criteria, a `priority`, and `assignTo` set to a role on the team. These seed the backlog so the project starts in its actual domain instead of only doing generic setup. Issue titles should lead with the core product capability; secondary constraints belong in acceptance criteria or risk notes unless the issue is specifically about that constraint. Do NOT put generic scaffolding here (vision docs, linters, CI, branch protection) \u2014 the wizard adds those automatically.\n\nFirst write one paragraph explaining your reasoning: why this preset, why these modules, why these roles.\n\nThen output the JSON (no markdown fences):\n{{CONFIG_FORMAT}}\n';
 
 // src/ui/prompts/messages.json
@@ -7555,6 +7634,30 @@ var STEP_COMPONENTS = {
   provision: StepProvision,
   done: StepDone
 };
+var WIZARD_HISTORY_MARKER = "company-wizard";
+function isObject(value) {
+  return typeof value === "object" && value !== null;
+}
+function isStep(value) {
+  return typeof value === "string" && value in STEP_COMPONENTS;
+}
+function isWizardPath(value) {
+  return value === null || value === "manual" || value === "ai" || value === "update";
+}
+function readWizardHistoryState(value) {
+  if (!isObject(value)) return null;
+  if (value.__paperclipPlugin !== WIZARD_HISTORY_MARKER) return null;
+  if (!isStep(value.step) || !isWizardPath(value.path)) return null;
+  return { step: value.step, path: value.path };
+}
+function buildWizardHistoryState(currentState, path, step) {
+  return {
+    ...isObject(currentState) ? currentState : {},
+    __paperclipPlugin: WIZARD_HISTORY_MARKER,
+    path,
+    step
+  };
+}
 function StepIndicator() {
   const state = useWizard();
   const current = getUserStepIndex(state);
@@ -7579,10 +7682,46 @@ function StepIndicator() {
 function WizardShell() {
   const state = useWizard();
   const dispatch = useWizardDispatch();
+  const restoredFromHistory = useRef8(false);
+  const seededHistory = useRef8(false);
   const StepComponent = STEP_COMPONENTS[state.step];
   useEffect9(() => {
     window.scrollTo({ top: 0 });
   }, [state.step]);
+  useEffect9(() => {
+    const handlePopState = (event) => {
+      const historyState = readWizardHistoryState(event.state);
+      if (!historyState?.step) return;
+      restoredFromHistory.current = true;
+      dispatch({
+        type: "RESTORE_NAV",
+        path: historyState.path ?? null,
+        step: historyState.step
+      });
+    };
+    window.addEventListener("popstate", handlePopState);
+    return () => window.removeEventListener("popstate", handlePopState);
+  }, [dispatch]);
+  useEffect9(() => {
+    if (!seededHistory.current) {
+      seededHistory.current = true;
+      window.history.replaceState(
+        buildWizardHistoryState(window.history.state, state.path, state.step),
+        "",
+        window.location.href
+      );
+      return;
+    }
+    if (restoredFromHistory.current) {
+      restoredFromHistory.current = false;
+      return;
+    }
+    window.history.pushState(
+      buildWizardHistoryState(window.history.state, state.path, state.step),
+      "",
+      window.location.href
+    );
+  }, [state.path, state.step]);
   return /* @__PURE__ */ jsxs15("div", { className: "flex flex-col", children: [
     getUserStepIndex(state) >= 1 && state.step !== "provision" && state.step !== "done" && /* @__PURE__ */ jsx21("div", { className: "flex items-center justify-end px-6 py-3", children: /* @__PURE__ */ jsx21(StepIndicator, {}) }),
     /* @__PURE__ */ jsx21("main", { className: "flex-1 flex items-start justify-center p-6", children: /* @__PURE__ */ jsx21("div", { className: "w-full max-w-2xl", children: /* @__PURE__ */ jsx21(StepComponent, {}) }) }),