hub-launch 1.26.0 → 1.28.0

package/dist/services/plan/PlanBranchService.js

@@ -0,0 +1,95 @@
+import { existsSync, readFileSync } from 'fs';
+import { isAbsolute, join } from 'path';
+import { sanitizePlanName } from '../../utils/validators.js';
+import { GitService } from '../git/GitService.js';
+import { FilePublishService } from '../git/FilePublishService.js';
+import { PlanService } from './PlanService.js';
+/**
+ * Thrown when the plan file cannot be found anywhere — not on disk, not on
+ * the feature branch, not on the base branch. Callers translate this into the
+ * historical "Plan not found locally or on origin/main" error handling.
+ */
+export class PlanNotFoundError extends Error {
+    constructor(planPath) {
+        super(`Plan not found locally or on any git ref: ${planPath}`);
+        this.name = 'PlanNotFoundError';
+    }
+}
+/**
+ * Resolve the plan's content, preferring the freshest source:
+ *   1. the working tree (where /hula-plan writes and validation edits it)
+ *   2. the feature branch on origin (plan-branch flow, plan already pushed)
+ *   3. the base branch on origin, then local base (legacy plans, relaunches)
+ *
+ * Returns `null` when the plan exists nowhere.
+ */
+async function resolvePlanContent(gitService, relativePath, planFsPath, branch, branchOnOrigin, baseBranch) {
+    if (existsSync(planFsPath)) {
+        return readFileSync(planFsPath, 'utf-8');
+    }
+    if (branchOnOrigin &&
+        (await gitService.fileExistsOnRef(`origin/${branch}`, relativePath))) {
+        return gitService.showFile(`origin/${branch}`, relativePath);
+    }
+    for (const ref of [`origin/${baseBranch}`, baseBranch]) {
+        if (await gitService.fileExistsOnRef(ref, relativePath)) {
+            return gitService.showFile(ref, relativePath);
+        }
+    }
+    return null;
+}
+/**
+ * Ensure the feature branch for `issueName` exists on origin and carries the
+ * current plan file — the core of the plan-branch flow.
+ *
+ * - Branch missing on origin → create it from `origin/<uploadBranch ?? main>`
+ *   with the plan committed (one worktree publish, one push).
+ * - Branch exists but the plan file on it is missing or stale → publish the
+ *   fresh content to the branch.
+ * - Branch exists with identical content → no-op.
+ *
+ * This runs BEFORE the beforeLaunch hook in `hula launch`, so hooks (e.g.
+ * Vercel branch-scoped env vars) can rely on the git branch existing on the
+ * remote. It is also invoked at plan time via `hula upload --branch`.
+ *
+ * @throws PlanNotFoundError when the plan content cannot be resolved anywhere.
+ */
+export async function ensurePlanBranch(config, planPath, issueName, repoRoot) {
+    const branch = sanitizePlanName(issueName);
+    const baseBranch = config.uploadBranch ?? 'main';
+    const gitService = new GitService(repoRoot);
+    const planService = new PlanService(config.planPath);
+    const relativePath = planService.getRelativePath(planPath);
+    const planFsPath = isAbsolute(planPath) || !repoRoot ? planPath : join(repoRoot, planPath);
+    // One fetch up front so every origin/<ref> read below is current.
+    await gitService.fetch('origin');
+    const branchOnOrigin = await gitService.remoteBranchExists(branch);
+    const content = await resolvePlanContent(gitService, relativePath, planFsPath, branch, branchOnOrigin, baseBranch);
+    if (content === null) {
+        throw new PlanNotFoundError(planPath);
+    }
+    if (branchOnOrigin) {
+        // Skip the publish when the branch already holds this exact content.
+        // `git show` output matches committed bytes, so string equality is exact.
+        if (await gitService.fileExistsOnRef(`origin/${branch}`, relativePath)) {
+            const onBranch = await gitService.showFile(`origin/${branch}`, relativePath);
+            if (onBranch === content) {
+                return { branch, created: false, updated: false };
+            }
+        }
+        const publisher = new FilePublishService(config, repoRoot);
+        await publisher.publishFile(relativePath, content, {
+            commitMessage: 'chore: update plan via hula',
+            branch,
+        });
+        return { branch, created: false, updated: true };
+    }
+    const publisher = new FilePublishService(config, repoRoot);
+    await publisher.publishFile(relativePath, content, {
+        commitMessage: 'chore: create plan branch via hula',
+        branch,
+        createFromRef: `origin/${baseBranch}`,
+    });
+    return { branch, created: true, updated: true };
+}
+//# sourceMappingURL=PlanBranchService.js.map

package/dist/services/plan/PlanBranchService.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"PlanBranchService.js","sourceRoot":"","sources":["../../../src/services/plan/PlanBranchService.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAE,YAAY,EAAE,MAAM,IAAI,CAAC;AAC9C,OAAO,EAAE,UAAU,EAAE,IAAI,EAAE,MAAM,MAAM,CAAC;AAExC,OAAO,EAAE,gBAAgB,EAAE,MAAM,2BAA2B,CAAC;AAC7D,OAAO,EAAE,UAAU,EAAE,MAAM,sBAAsB,CAAC;AAClD,OAAO,EAAE,kBAAkB,EAAE,MAAM,8BAA8B,CAAC;AAClE,OAAO,EAAE,WAAW,EAAE,MAAM,kBAAkB,CAAC;AAc/C;;;;GAIG;AACH,MAAM,OAAO,iBAAkB,SAAQ,KAAK;IAC1C,YAAY,QAAgB;QAC1B,KAAK,CAAC,6CAA6C,QAAQ,EAAE,CAAC,CAAC;QAC/D,IAAI,CAAC,IAAI,GAAG,mBAAmB,CAAC;IAClC,CAAC;CACF;AAED;;;;;;;GAOG;AACH,KAAK,UAAU,kBAAkB,CAC/B,UAAsB,EACtB,YAAoB,EACpB,UAAkB,EAClB,MAAc,EACd,cAAuB,EACvB,UAAkB;IAElB,IAAI,UAAU,CAAC,UAAU,CAAC,EAAE,CAAC;QAC3B,OAAO,YAAY,CAAC,UAAU,EAAE,OAAO,CAAC,CAAC;IAC3C,CAAC;IACD,IACE,cAAc;QACd,CAAC,MAAM,UAAU,CAAC,eAAe,CAAC,UAAU,MAAM,EAAE,EAAE,YAAY,CAAC,CAAC,EACpE,CAAC;QACD,OAAO,UAAU,CAAC,QAAQ,CAAC,UAAU,MAAM,EAAE,EAAE,YAAY,CAAC,CAAC;IAC/D,CAAC;IACD,KAAK,MAAM,GAAG,IAAI,CAAC,UAAU,UAAU,EAAE,EAAE,UAAU,CAAC,EAAE,CAAC;QACvD,IAAI,MAAM,UAAU,CAAC,eAAe,CAAC,GAAG,EAAE,YAAY,CAAC,EAAE,CAAC;YACxD,OAAO,UAAU,CAAC,QAAQ,CAAC,GAAG,EAAE,YAAY,CAAC,CAAC;QAChD,CAAC;IACH,CAAC;IACD,OAAO,IAAI,CAAC;AACd,CAAC;AAED;;;;;;;;;;;;;;;GAeG;AACH,MAAM,CAAC,KAAK,UAAU,gBAAgB,CACpC,MAAc,EACd,QAAgB,EAChB,SAAiB,EACjB,QAAiB;IAEjB,MAAM,MAAM,GAAG,gBAAgB,CAAC,SAAS,CAAC,CAAC;IAC3C,MAAM,UAAU,GAAG,MAAM,CAAC,YAAY,IAAI,MAAM,CAAC;IACjD,MAAM,UAAU,GAAG,IAAI,UAAU,CAAC,QAAQ,CAAC,CAAC;IAC5C,MAAM,WAAW,GAAG,IAAI,WAAW,CAAC,MAAM,CAAC,QAAQ,CAAC,CAAC;IAErD,MAAM,YAAY,GAAG,WAAW,CAAC,eAAe,CAAC,QAAQ,CAAC,CAAC;IAC3D,MAAM,UAAU,GACd,UAAU,CAAC,QAAQ,CAAC,IAAI,CAAC,QAAQ,CAAC,CAAC,CAAC,QAAQ,CAAC,CAAC,CAAC,IAAI,CAAC,QAAQ,EAAE,QAAQ,CAAC,CAAC;IAE1E,kEAAkE;IAClE,MAAM,UAAU,CAAC,KAAK,CAAC,QAAQ,CAAC,CAAC;IAEjC,MAAM,cAAc,GAAG,MAAM,UAAU,CAAC,kBAAkB,CAAC,MAAM,CAAC,CAAC;IAEnE,MAAM,OAAO,GAAG,MAAM,kBAAkB,CACtC,UAAU,EACV,YAAY,EACZ,UAAU,EACV,MAAM,EACN,cAAc,EACd,UAAU,CACX,CAAC;IACF,IAAI,OAAO,KAAK,IAAI,EAAE,CAAC;QACrB,MAAM,IAAI,iBAAiB,CAAC,QAAQ,CAAC,CAAC;IACxC,CAAC;IAED,IAAI,cAAc,EAAE,CAAC;QACnB,qEAAqE;QACrE,0EAA0E;QAC1E,IAAI,MAAM,UAAU,CAAC,eAAe,CAAC,UAAU,MAAM,EAAE,EAAE,YAAY,CAAC,EAAE,CAAC;YACvE,MAAM,QAAQ,GAAG,MAAM,UAAU,CAAC,QAAQ,CACxC,UAAU,MAAM,EAAE,EAClB,YAAY,CACb,CAAC;YACF,IAAI,QAAQ,KAAK,OAAO,EAAE,CAAC;gBACzB,OAAO,EAAE,MAAM,EAAE,OAAO,EAAE,KAAK,EAAE,OAAO,EAAE,KAAK,EAAE,CAAC;YACpD,CAAC;QACH,CAAC;QACD,MAAM,SAAS,GAAG,IAAI,kBAAkB,CAAC,MAAM,EAAE,QAAQ,CAAC,CAAC;QAC3D,MAAM,SAAS,CAAC,WAAW,CAAC,YAAY,EAAE,OAAO,EAAE;YACjD,aAAa,EAAE,6BAA6B;YAC5C,MAAM;SACP,CAAC,CAAC;QACH,OAAO,EAAE,MAAM,EAAE,OAAO,EAAE,KAAK,EAAE,OAAO,EAAE,IAAI,EAAE,CAAC;IACnD,CAAC;IAED,MAAM,SAAS,GAAG,IAAI,kBAAkB,CAAC,MAAM,EAAE,QAAQ,CAAC,CAAC;IAC3D,MAAM,SAAS,CAAC,WAAW,CAAC,YAAY,EAAE,OAAO,EAAE;QACjD,aAAa,EAAE,oCAAoC;QACnD,MAAM;QACN,aAAa,EAAE,UAAU,UAAU,EAAE;KACtC,CAAC,CAAC;IACH,OAAO,EAAE,MAAM,EAAE,OAAO,EAAE,IAAI,EAAE,OAAO,EAAE,IAAI,EAAE,CAAC;AAClD,CAAC"}

package/dist/templates/proceed-instructions.md

@@ -378,8 +378,9 @@ After the Completion Format block is printed, offer to launch the plan for the u
 
 Determine `<issueName>` before asking the question:
 
-1. **Look for a name the user specified** anywhere in this conversation — e.g. "use the branch name `foo`", "call the issue `bar`", or a name passed in the original `/hula-plan` arguments. If more than one was mentioned, **the most recent wins**. Use that name verbatim (kebab-case it if needed).
-2. **Otherwise derive the default from the plan file's basename** (the subfolder is never part of the name):
+1. **Look for a plan-branch created earlier in this session** — a `<!-- hula-branch: <name> -->` comment in the chat history (emitted by `/hula-plan` when it created the feature branch at plan time). If present, that name is the default: the branch already exists on origin with the plan on it.
+2. **Look for a name the user specified** anywhere in this conversation — e.g. "use the branch name `foo`", "call the issue `bar`", or a name passed in the original `/hula-plan` arguments. If more than one was mentioned, **the most recent wins**, and a user-specified name overrides the plan-branch default. Use that name verbatim (kebab-case it if needed). (Launching under a different name than the plan branch is fine — `hula launch` creates the new branch automatically; the unused plan branch can be deleted later.)
+3. **Otherwise derive the default from the plan file's basename** (the subfolder is never part of the name):
    - Strip the leading timestamp prefix matching `YYYY-MM-DD-HH:MM-` and the trailing `.md`.
    - The remaining text is the title slug (e.g. `auto-launch-offer-after-plan`).
    - If the slug is **longer than 3 words**, shorten it to the 2–3 most distinctive words (e.g. `auto-launch-offer-after-plan` → `auto-launch`). Otherwise keep it as-is.

package/dist/templates/skills/hula-help/SKILL.md

@@ -86,7 +86,7 @@ Read `README.md`'s "Quick Start" and "Requirements" sections (and the "Core Work
 Read the "Core Workflow" section of `README.md` live. Explain each step in plain language — one at a time if the user wants depth, or as a compact list if they want the overview:
 
 - `/hula-plan <description>` — writes a plan file to `.hublaunch/plans/`, validates it automatically.
-- `/hula-upload` — syncs the plan to `origin/main` (usually automatic as part of `/hula-launch`, rarely needed standalone).
+- `/hula-upload` — publishes the plan to its feature branch (`hula upload --branch <name>`) or to `origin/main` (usually automatic as part of `/hula-plan` and `/hula-launch`, rarely needed standalone).
 - `/hula-launch <name>` — creates the GitHub issue, runs the AI coding session in an isolated cloud container, opens a PR.
 - `/hula-verify` — checks the PR against the plan's acceptance criteria.
 - `/hula-fix <instructions>` — addresses gaps found by verify, or anything else you want changed on the PR branch.

package/dist/templates/skills/hula-launch/SKILL.md

@@ -153,6 +153,6 @@ The `cliOutput` already contains the per-repo roster, ✓/✗ summary, and any r
 
 ## Important Notes
 
-- Do NOT call the `Read` tool to check if the plan file exists. The `hula launch` CLI validates file existence (locally and on `origin/main`) and reports errors clearly.
-- Do NOT run `hula upload` separately. `hula launch` handles upload automatically.
+- Do NOT call the `Read` tool to check if the plan file exists. The `hula launch` CLI validates file existence (locally, on the plan's feature branch, and on `origin/main`) and reports errors clearly.
+- Do NOT run `hula upload` separately. `hula launch` publishes the plan to its feature branch automatically (creating the branch from the base branch if `/hula-plan` didn't already, and refreshing it after validation edits or a rename).
 - This command is typically run after `/hula-plan` and `/hula-confirm`.

package/dist/templates/skills/hula-plan/SKILL.md

@@ -122,17 +122,33 @@ The plan should be immediately actionable by a developer familiar with the codeb
 
 **⚠️ NEVER create plan files in the project root directory.** The plan file MUST always be inside the `.hublaunch/plans/` directory (or a subfolder of it). If you cannot read the config file, use the default path `.hublaunch/plans/`.
 
-### Step 2: Output the Plan Path and Next Steps
+### Step 2: Create the Plan Branch
+
+Right after saving the plan file, create the feature branch on origin with the plan committed to it. This is the **plan-branch flow**: the git branch exists from plan time onward, so branch-scoped infrastructure (Vercel Preview env vars, per-branch databases, beforeLaunch hooks) can rely on it well before the launch.
+
+1. **Resolve `<issueName>`** using the same rules as the Launch Offer's "Resolve the issue name" step in `hula instructions proceed`: a name the user specified anywhere in this conversation wins (most recent first); otherwise derive the default from the plan file's basename (strip the `YYYY-MM-DD-HH:MM-` prefix and `.md`, shorten a >3-word slug to its 2–3 most distinctive words, always kebab-case).
+2. **Create the branch** by running:
+
+   `hula upload <planPath> --branch <issueName>`
+
+   This creates branch `<issueName>` (sanitized) on origin from the base branch with the plan file committed, or refreshes the plan on the branch if it already exists.
+3. If the command fails (e.g. no network, no push permission), print a warning and continue — `hula launch` re-runs the same step as a safety net at launch time, so a plan-time failure is not fatal.
+
+### Step 3: Output the Plan Path and Next Steps
 
 **Output Format:**
 
 ```
 ✅ Plan created: `.hublaunch/plans/2025-12-29-14:30-feature-name.md`
+🌿 Branch created: `feature-name` (plan pushed to origin)
 <!-- hula-plan: .hublaunch/plans/2025-12-29-14:30-feature-name.md -->
+<!-- hula-branch: feature-name -->
 
 📋 **Proceeding to validation now…**
 ```
 
+(Substitute the actual resolved `<issueName>` in the branch line and the `hula-branch` comment. If branch creation failed in Step 2, replace the 🌿 line with `⚠️ Branch creation deferred to launch time` and omit the `hula-branch` comment.)
+
 Now proceed directly to plan validation **without waiting for the user**. The plan file was just created in this session — the path is already known.
 
 Read `hula instructions proceed` and execute the full validation workflow against the plan at `<path>` (substitute `<path>` with the actual plan file path you just created, e.g. `.hublaunch/plans/2025-12-29-14:30-feature-name.md`).
@@ -156,4 +172,4 @@ Read `hula instructions proceed` and execute the full validation workflow agains
   5. If `--test` and/or `--handoff <username>` were also present in `$ARGUMENTS`, pass them through to the launch — same as the Launch Offer's reply table does for a manual reply containing those flags.
 - **Without `--autoLaunch`**, behavior is completely unchanged: ask and wait as today.
 
-**Note:** The plan is saved locally. When you run `/hula-launch`, the plan is automatically synced to `origin/main` before the GitHub issue is created and the implementation begins — no separate upload step needed. Because validation ends with the Launch Offer, an affirmative reply runs the `/hula-launch` workflow for the user automatically; they can also decline and run `/hula-launch` themselves later. `/hula-confirm` remains available as a standalone command for re-validation at any time. If `--autoLaunch` was passed to `/hula-plan`, the launch runs automatically once validation completes — no reply needed.
+**Note:** The plan is saved locally AND pushed to its feature branch on origin (Step 2). When you run `/hula-launch`, the plan branch is re-synced automatically (covering validation edits and renames) before the GitHub issue is created and the implementation begins — no separate upload step needed. Because validation ends with the Launch Offer, an affirmative reply runs the `/hula-launch` workflow for the user automatically; they can also decline and run `/hula-launch` themselves later. `/hula-confirm` remains available as a standalone command for re-validation at any time. If `--autoLaunch` was passed to `/hula-plan`, the launch runs automatically once validation completes — no reply needed.

package/dist/templates/skills/hula-upload/SKILL.md

@@ -29,7 +29,7 @@ Your job is to:
      ```
      ℹ️ Upload is no longer a separate step.
 
-     `hula launch` automatically uploads the plan to `origin/main` before starting the job.
+     `hula launch` automatically publishes the plan to its feature branch before starting the job (creating the branch from the base branch if `/hula-plan` didn't already).
 
      **Next Step:** Run `/hula-launch <branch-name>` to upload and launch in one step.
 
@@ -84,7 +84,7 @@ Display this message to the user:
 ```
 ℹ️ Upload is no longer a separate step.
 
-`hula launch` automatically uploads the plan to `origin/main` before starting the job.
+`hula launch` automatically publishes the plan to its feature branch before starting the job (creating the branch from the base branch if `/hula-plan` didn't already).
 
 **Next Step:** Run `/hula-launch <branch-name>` to upload and launch in one step.
 

package/dist/utils/validators.d.ts

@@ -25,6 +25,14 @@ export declare function parseIssueNumber(value: string | number): number | null;
  * Validate email address
  */
 export declare function isValidEmail(email: string): boolean;
+/**
+ * Sanitize an issue/tracking name into the git branch name used for its run.
+ * MUST stay byte-identical to `sanitizePlanName` in hula-server's
+ * `packages/shared/src/utils.ts` — the server derives the sandbox branch from
+ * the same issueName, so both sides have to resolve the SAME branch name for
+ * the plan-branch flow to hand off correctly.
+ */
+export declare function sanitizePlanName(name: string): string;
 /**
  * Sanitize filename
  */

package/dist/utils/validators.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"validators.d.ts","sourceRoot":"","sources":["../../src/utils/validators.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH;;GAEG;AACH,wBAAgB,kBAAkB,CAAC,KAAK,EAAE,OAAO,GAAG,KAAK,IAAI,MAAM,CAElE;AAED;;GAEG;AACH,wBAAgB,qBAAqB,CAAC,QAAQ,EAAE,MAAM,GAAG,OAAO,CAG/D;AAED;;GAEG;AACH,wBAAgB,UAAU,CAAC,GAAG,EAAE,MAAM,GAAG,OAAO,CAO/C;AAED;;GAEG;AACH,wBAAgB,WAAW,CAAC,IAAI,EAAE,MAAM,GAAG,OAAO,CAEjD;AAED;;GAEG;AACH,wBAAgB,gBAAgB,CAAC,KAAK,EAAE,MAAM,GAAG,MAAM,GAAG,MAAM,GAAG,IAAI,CAUtE;AAED;;GAEG;AACH,wBAAgB,YAAY,CAAC,KAAK,EAAE,MAAM,GAAG,OAAO,CAGnD;AAED;;GAEG;AACH,wBAAgB,gBAAgB,CAAC,QAAQ,EAAE,MAAM,GAAG,MAAM,CAMzD"}
+{"version":3,"file":"validators.d.ts","sourceRoot":"","sources":["../../src/utils/validators.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH;;GAEG;AACH,wBAAgB,kBAAkB,CAAC,KAAK,EAAE,OAAO,GAAG,KAAK,IAAI,MAAM,CAElE;AAED;;GAEG;AACH,wBAAgB,qBAAqB,CAAC,QAAQ,EAAE,MAAM,GAAG,OAAO,CAG/D;AAED;;GAEG;AACH,wBAAgB,UAAU,CAAC,GAAG,EAAE,MAAM,GAAG,OAAO,CAO/C;AAED;;GAEG;AACH,wBAAgB,WAAW,CAAC,IAAI,EAAE,MAAM,GAAG,OAAO,CAEjD;AAED;;GAEG;AACH,wBAAgB,gBAAgB,CAAC,KAAK,EAAE,MAAM,GAAG,MAAM,GAAG,MAAM,GAAG,IAAI,CAUtE;AAED;;GAEG;AACH,wBAAgB,YAAY,CAAC,KAAK,EAAE,MAAM,GAAG,OAAO,CAGnD;AAED;;;;;;GAMG;AACH,wBAAgB,gBAAgB,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,CAErD;AAED;;GAEG;AACH,wBAAgB,gBAAgB,CAAC,QAAQ,EAAE,MAAM,GAAG,MAAM,CAMzD"}

package/dist/utils/validators.js

@@ -51,6 +51,16 @@ export function isValidEmail(email) {
     const emailRegex = /^[^\s@]+@[^\s@]+\.[^\s@]+$/;
     return emailRegex.test(email);
 }
+/**
+ * Sanitize an issue/tracking name into the git branch name used for its run.
+ * MUST stay byte-identical to `sanitizePlanName` in hula-server's
+ * `packages/shared/src/utils.ts` — the server derives the sandbox branch from
+ * the same issueName, so both sides have to resolve the SAME branch name for
+ * the plan-branch flow to hand off correctly.
+ */
+export function sanitizePlanName(name) {
+    return name.replace(/[^a-zA-Z0-9_-]/g, "_");
+}
 /**
  * Sanitize filename
  */

package/dist/utils/validators.js.map

@@ -1 +1 @@
-{"version":3,"file":"validators.js","sourceRoot":"","sources":["../../src/utils/validators.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH;;GAEG;AACH,MAAM,UAAU,kBAAkB,CAAC,KAAc;IAC/C,OAAO,OAAO,KAAK,KAAK,QAAQ,IAAI,MAAM,CAAC,SAAS,CAAC,KAAK,CAAC,IAAI,KAAK,GAAG,CAAC,CAAC;AAC3E,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,qBAAqB,CAAC,QAAgB;IACpD,8DAA8D;IAC9D,OAAO,+CAA+C,CAAC,IAAI,CAAC,QAAQ,CAAC,CAAC;AACxE,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,UAAU,CAAC,GAAW;IACpC,IAAI,CAAC;QACH,IAAI,GAAG,CAAC,GAAG,CAAC,CAAC;QACb,OAAO,IAAI,CAAC;IACd,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,KAAK,CAAC;IACf,CAAC;AACH,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,WAAW,CAAC,IAAY;IACtC,OAAO,IAAI,CAAC,MAAM,GAAG,CAAC,IAAI,CAAC,IAAI,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC;AACjD,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,gBAAgB,CAAC,KAAsB;IACrD,IAAI,OAAO,KAAK,KAAK,QAAQ,EAAE,CAAC;QAC9B,OAAO,kBAAkB,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,IAAI,CAAC;IAClD,CAAC;IAED,6BAA6B;IAC7B,MAAM,OAAO,GAAG,KAAK,CAAC,OAAO,CAAC,IAAI,EAAE,EAAE,CAAC,CAAC;IACxC,MAAM,GAAG,GAAG,QAAQ,CAAC,OAAO,EAAE,EAAE,CAAC,CAAC;IAElC,OAAO,kBAAkB,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,IAAI,CAAC;AAC9C,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,YAAY,CAAC,KAAa;IACxC,MAAM,UAAU,GAAG,4BAA4B,CAAC;IAChD,OAAO,UAAU,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;AAChC,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,gBAAgB,CAAC,QAAgB;IAC/C,OAAO,QAAQ;SACZ,OAAO,CAAC,wBAAwB,EAAE,GAAG,CAAC,CAAC,wBAAwB;SAC/D,OAAO,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC,8BAA8B;SACnD,OAAO,CAAC,KAAK,EAAE,GAAG,CAAC,CAAC,4BAA4B;SAChD,OAAO,CAAC,QAAQ,EAAE,EAAE,CAAC,CAAC,CAAC,kCAAkC;AAC9D,CAAC"}
+{"version":3,"file":"validators.js","sourceRoot":"","sources":["../../src/utils/validators.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH;;GAEG;AACH,MAAM,UAAU,kBAAkB,CAAC,KAAc;IAC/C,OAAO,OAAO,KAAK,KAAK,QAAQ,IAAI,MAAM,CAAC,SAAS,CAAC,KAAK,CAAC,IAAI,KAAK,GAAG,CAAC,CAAC;AAC3E,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,qBAAqB,CAAC,QAAgB;IACpD,8DAA8D;IAC9D,OAAO,+CAA+C,CAAC,IAAI,CAAC,QAAQ,CAAC,CAAC;AACxE,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,UAAU,CAAC,GAAW;IACpC,IAAI,CAAC;QACH,IAAI,GAAG,CAAC,GAAG,CAAC,CAAC;QACb,OAAO,IAAI,CAAC;IACd,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,KAAK,CAAC;IACf,CAAC;AACH,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,WAAW,CAAC,IAAY;IACtC,OAAO,IAAI,CAAC,MAAM,GAAG,CAAC,IAAI,CAAC,IAAI,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC;AACjD,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,gBAAgB,CAAC,KAAsB;IACrD,IAAI,OAAO,KAAK,KAAK,QAAQ,EAAE,CAAC;QAC9B,OAAO,kBAAkB,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,IAAI,CAAC;IAClD,CAAC;IAED,6BAA6B;IAC7B,MAAM,OAAO,GAAG,KAAK,CAAC,OAAO,CAAC,IAAI,EAAE,EAAE,CAAC,CAAC;IACxC,MAAM,GAAG,GAAG,QAAQ,CAAC,OAAO,EAAE,EAAE,CAAC,CAAC;IAElC,OAAO,kBAAkB,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,IAAI,CAAC;AAC9C,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,YAAY,CAAC,KAAa;IACxC,MAAM,UAAU,GAAG,4BAA4B,CAAC;IAChD,OAAO,UAAU,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;AAChC,CAAC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,gBAAgB,CAAC,IAAY;IAC3C,OAAO,IAAI,CAAC,OAAO,CAAC,iBAAiB,EAAE,GAAG,CAAC,CAAC;AAC9C,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,gBAAgB,CAAC,QAAgB;IAC/C,OAAO,QAAQ;SACZ,OAAO,CAAC,wBAAwB,EAAE,GAAG,CAAC,CAAC,wBAAwB;SAC/D,OAAO,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC,8BAA8B;SACnD,OAAO,CAAC,KAAK,EAAE,GAAG,CAAC,CAAC,4BAA4B;SAChD,OAAO,CAAC,QAAQ,EAAE,EAAE,CAAC,CAAC,CAAC,kCAAkC;AAC9D,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "hub-launch",
-  "version": "1.26.0",
+  "version": "1.28.0",
   "description": "GitHub Issue and PR automation CLI tool with plugin/hook system for project-specific customizations",
   "type": "module",
   "main": "./dist/index.js",
@@ -75,5 +75,13 @@
   "engines": {
     "node": ">=18.0.0"
   },
+  "overrides": {
+    "core-js": "^3.23.3"
+  },
+  "pnpm": {
+    "overrides": {
+      "core-js": "^3.23.3"
+    }
+  },
   "packageManager": "pnpm@9.1.1+sha512.14e915759c11f77eac07faba4d019c193ec8637229e62ec99eefb7cf3c3b75c64447882b7c485142451ee3a6b408059cdfb7b7fa0341b975f12d0f7629c71195"
 }