@launchsecure/launch-kit 0.0.44 → 0.0.45

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@launchsecure/launch-kit",
-  "version": "0.0.44",
+  "version": "0.0.45",
   "description": "LaunchSecure toolkit — launch-sequencer (pipeline runner + terminal bridge), launch-radar (feedback webhook receiver), launch-chart (project graph MCP), launch-deck (visual playground MCP), launch-kit-beacon (feedback Web Component), launch-recall (file-watcher backup). launch-pod is the container image these run inside.",
   "license": "MIT",
   "author": "LaunchSecure - AutomateWithUs",

package/scaffolds/ls-marketplace/plugins/kit/skills/ship/SKILL.md

@@ -12,6 +12,10 @@ The shipping log is a **Brief**: a markdown doc at `doc/shipping-logs/<date>-<ta
 
 Hard rule from project memory: **never push commits the user didn't explicitly name**, and **pushing to a deploy-tracked branch may auto-deploy** — so this skill always asks per-action before pushing, even when invoked with arguments. There is no `--yes-i-mean-it` flag.
 
+**Confirmation convention.** Every gated decision in this skill (the GO-WITH-CAVEATS gate, the migration gate, the Brief preview, the push) is presented as a **selectable option prompt via the `AskUserQuestion` tool** — not a "reply with `yes`" free-text instruction. Each gate below specifies its header + the exact options to offer. Two rules survive the switch to options:
+- **The default/recommended option is never the destructive/irreversible one.** List the safe choice (or `cancel`) first; mark the proceed option `(Recommended)` only where proceeding is genuinely the expected path.
+- **The escalation for a prod push is preserved by the option label itself** — the prod push option is labelled `Ship it` (not a generic `Push`), so selecting it is as deliberate as typing the word used to be. Selecting an option IS the explicit confirmation; there is no separate typed keyword.
+
 Parse `$ARGUMENTS`:
 
 - (empty) — full flow on the current branch → its upstream (resolved via `git rev-parse --abbrev-ref @{u}` or, missing that, `origin/<current-branch>`).
@@ -59,9 +63,10 @@ Invoke `/kit:deploy-check` against the resolved target. Forward `--quick` / `--s
 Verdict handling:
 
 - **NO-GO** → abort the ship. Print the failing checks verbatim from deploy-check. Tell the user what to fix. Do not offer to "force ship".
-- **GO WITH CAVEATS** → surface the warnings, then ask:
-  > "deploy-check returned GO WITH CAVEATS (<N> warnings listed above). Continue with ship? Reply `yes` to continue, `cancel` to abort."
-- **GO** → continue silently to step 2.
+- **GO WITH CAVEATS** → surface the warnings, then ask via `AskUserQuestion` (header `Ship gate`, question naming the caveat count, e.g. "deploy-check is GO WITH CAVEATS (<N> warnings above). Continue with ship?"):
+  - `Cancel ship` — abort; nothing written or pushed.
+  - `Continue (Recommended)` — proceed to step 2.
+- **GO** → continue silently to step 2 (no prompt).
 
 Hard rules:
 
@@ -112,11 +117,12 @@ Backup story:
     or add a backup step to CI. Recovery is impossible without one.
 ```
 
-Then ask:
+Then ask via `AskUserQuestion` (header `Migration gate`, question "This push includes <N> migration(s). Acknowledge and continue?"):
 
-> "Migration push detected. Type `understood` to continue, or `cancel` to abort."
+- `Cancel ship` — abort; nothing written or pushed.
+- `Understood — proceed` — acknowledge the migration push and continue.
 
-This is a deliberate friction point — typing a word is more honest than `y`. Do not accept `yes` here; require `understood`.
+This is a deliberate friction point: the acknowledgement option is labelled `Understood — proceed` (not a generic `yes`) and is **never** the auto-highlighted default — the user must actively pick it. Do not collapse this into the same prompt as another gate; the migration acknowledgement stands alone.
 
 ## Step 4 — Author the shipping-log Brief
 
@@ -190,25 +196,25 @@ Field sources:
 
 ### Preview + confirm
 
-Show the full Brief in a fenced block, then ask:
-
-> "Write this Brief to `doc/shipping-logs/<filename>` and commit it? Reply `yes` to write + commit, `edit` to tweak (summary, themes, note), `skip` to ship without a log, or `cancel` to abort the ship."
+Show the full Brief in a fenced block, then ask via `AskUserQuestion` (header `Shipping log`, question "Write this Brief to `doc/shipping-logs/<filename>` and commit it?"):
 
-- `yes` / `y` → write the file, then `git add doc/shipping-logs/<filename> && git commit -m "docs(shipping-logs): ship <YYYY-MM-DD> — <target> (<one-line summary>)"`. The Brief commit is now the payload's tip.
-- `edit` → ask what to change, redraft, re-show, re-ask.
-- `skip` → no file, no commit. The ship proceeds unlogged — say so plainly: `shipping without a log entry; there will be no record of this ship.`
-- `cancel` → abort the entire ship. Nothing was written, nothing was pushed.
+- `Write + commit (Recommended)` → write the file, then `git add doc/shipping-logs/<filename> && git commit -m "docs(shipping-logs): ship <YYYY-MM-DD> — <target> (<one-line summary>)"`. The Brief commit is now the payload's tip.
+- `Edit Brief` → ask what to change (summary, themes, note), redraft, re-show, re-ask.
+- `Skip log` → no file, no commit. The ship proceeds unlogged — say so plainly: `shipping without a log entry; there will be no record of this ship.`
+- `Cancel ship` → abort the entire ship. Nothing was written, nothing was pushed.
 
 ## Step 5 — Push confirmation
 
-Ask **exactly**:
+Ask via `AskUserQuestion` (header `Push`). The question text and the proceed-option label differ by `IS_PROD_PUSH`:
 
 - If `IS_PROD_PUSH=false`:
-  > "Push <N> commits to origin/<target-branch>? Reply `yes` to push, `cancel` to abort."
+  - Question: "Push <N> commits to origin/<target-branch>?"
+  - Options: `Cancel` (first) · `Push` — push and continue.
 - If `IS_PROD_PUSH=true`:
-  > "Push <N> commits to origin/<target-branch>. This is a deploy-tracked branch — <if DEPLOY_PLATFORM≠unknown: '<platform> will deploy automatically'; else: 'whatever deploy pipeline is wired to this branch will pick it up'>. Reply `ship it` to push, `cancel` to abort."
+  - Question: "Push <N> commits to origin/<target-branch>. This is a deploy-tracked branch — <if DEPLOY_PLATFORM≠unknown: '<platform> will deploy automatically'; else: 'whatever deploy pipeline is wired to this branch will pick it up'>. This deploys to production."
+  - Options: `Cancel` (first) · `Ship it` — push and trigger the deploy. The label is `Ship it` (not `Push`) so the prod choice is unmistakable.
 
-`<N>` includes the Brief commit from step 4 (when not skipped). Accept exactly `yes` / `ship it` (case-insensitive). Anything else → treat as cancel. **Never** accept silence, `ok`, `sure`, free-form approval. If `--dry-run`, skip this step entirely.
+`<N>` includes the Brief commit from step 4 (when not skipped). Only the explicit `Push` / `Ship it` option proceeds; selecting `Cancel`, dismissing the prompt, or any free-form answer → treat as cancel. The proceed option is **never** the auto-highlighted default for a prod push. If `--dry-run`, skip this step entirely (no prompt).
 
 On confirm: `git push origin <current-branch>:<target-branch>`. Stream stdout. If the push fails (non-fast-forward, hook reject, auth) — surface the error verbatim, do not retry, do not `--force`.
 
@@ -283,7 +289,7 @@ Comm Hub side (when the project is LaunchSecure-wired): the "Shipping Logs" cate
 
 ## Notes for the assistant
 
-- The user has explicit project-memory rules against unauthorised pushes and dumb reverts. Treat every confirmation as load-bearing — don't paraphrase the prompt wording, don't accept ambiguous approval.
+- The user has explicit project-memory rules against unauthorised pushes and dumb reverts. Treat every confirmation as load-bearing — present each gate as an `AskUserQuestion` option prompt (per the Confirmation convention above), keep the destructive option off the default, and treat anything other than an explicit proceed selection as cancel.
 - "Ship" is the user's verb for "I want this in production." If the target isn't actually deploy-tracked, the skill should still work but should say so clearly in the scope line (step 5 phrasing changes).
 - The shipping-log Brief is the durable artifact and (when synced) the published record at once — there is no separate "publish" step and no local NDJSON file. If you find `.launchsecure/ship-log.ndjson` in a repo, it's from a pre-Brief version of this skill; leave it alone (don't migrate, don't delete) and mention it once.
 - **Portability is the contract.** This skill is installed by `launch-kit init` into projects on stacks you can't predict. Anything you hardcode that isn't in *this* repo is a bug for the next repo. When in doubt, detect or degrade — never assume.

package/dist/deck-client/assets/channel-Cw2WDt9a.js

@@ -1 +0,0 @@
-import{aq as o,ar as n}from"./mermaid.core-DYi3A-qK.js";const t=(r,a)=>o.lang.round(n.parse(r)[a]);export{t as c};

package/dist/deck-client/assets/classDiagram-6PBFFD2Q-JLUXVCUr.js

@@ -1 +0,0 @@
-import{s as a,c as s,a as e,C as t}from"./chunk-4TB4RGXK-UDZXXga6.js";import{_ as i}from"./mermaid.core-DYi3A-qK.js";import"./chunk-FMBD7UC4-C-2idlFB.js";import"./chunk-YZCP3GAM-Cd3pNBtQ.js";import"./chunk-55IACEB6-CfcU6PIW.js";import"./chunk-EDXVE4YY-BK6F5Fof.js";import"./index-TFX8vtTG.js";var n={parser:e,get db(){return new t},renderer:s,styles:a,init:i(r=>{r.class||(r.class={}),r.class.arrowMarkerAbsolute=r.arrowMarkerAbsolute},"init")};export{n as diagram};

package/dist/deck-client/assets/classDiagram-v2-HSJHXN6E-JLUXVCUr.js

@@ -1 +0,0 @@
-import{s as a,c as s,a as e,C as t}from"./chunk-4TB4RGXK-UDZXXga6.js";import{_ as i}from"./mermaid.core-DYi3A-qK.js";import"./chunk-FMBD7UC4-C-2idlFB.js";import"./chunk-YZCP3GAM-Cd3pNBtQ.js";import"./chunk-55IACEB6-CfcU6PIW.js";import"./chunk-EDXVE4YY-BK6F5Fof.js";import"./index-TFX8vtTG.js";var n={parser:e,get db(){return new t},renderer:s,styles:a,init:i(r=>{r.class||(r.class={}),r.class.arrowMarkerAbsolute=r.arrowMarkerAbsolute},"init")};export{n as diagram};

package/dist/deck-client/assets/clone-H0XCnSb6.js

@@ -1 +0,0 @@
-import{b as r}from"./graph-Dtsd9Jwe.js";var e=4;function a(o){return r(o,e)}export{a as c};

package/dist/deck-client/assets/stateDiagram-v2-QKLJ7IA2-tfMSn8xx.js

@@ -1 +0,0 @@
-import{s as e,b as r,a,S as s}from"./chunk-OYMX7WX6-D6hBkYLP.js";import{_ as i}from"./mermaid.core-DYi3A-qK.js";import"./chunk-55IACEB6-CfcU6PIW.js";import"./chunk-EDXVE4YY-BK6F5Fof.js";import"./index-TFX8vtTG.js";var p={parser:a,get db(){return new s(2)},renderer:r,styles:e,init:i(t=>{t.state||(t.state={}),t.state.arrowMarkerAbsolute=t.arrowMarkerAbsolute},"init")};export{p as diagram};