---
name: publish
description: Publish the Data Room presentation to Vercel
help_jtbd: "Publish your room to a live URL."
body_shape: E
layer: "harness"
layer_why: "Deploys the presentation to Vercel hosting infrastructure with a one-click link; wiring a real external tool, not merely rendering a view."
hitl_shape: "F.0"
hitl_why: "It surfaces one publish action for a single approve-or-defer decision."
# Phase 267.3-04, ruled in 267.3-CLASSIFICATION.md (Row 13): first delivery at commands/publish.md:149, the parsed deploy output hands over the live shareable URL for the whole Data Room.
interactive_first_reward: live_deliverable
argument-hint: "[--all|<view>]"
serves_jtbd: ["prepare-pitch"]
teaching: "When the Data Room is ready to share publicly, /mos:publish deploys the presentation to Vercel with a one-click link. From local artifact to shareable URL in one move."
disable-model-invocation: true
allowed-tools:
  - Read
  - Write
  - Bash
  - Glob
  - AskUserQuestion
# --- Phase 172-06 CIRS R1 exclude (Canon Part 11) ---
connector:
  excluded: true
  reason: "Lifecycle command. Publishes / deploys an artifact on explicit navigator request; a release action with no problem-state trigger."
---

<!-- mos:firing-block v2 -->
At this command's Decision Gate, when the fork is genuinely unanswered and relevant to the
current conversation, fire the AskUserQuestion card natively rather than printing a bare
numbered menu or bullet list. Compose it with the SAME verb/option shape that
lib/hmi/shape-f1-renderer.cjs (renderShapeF1) produces and that lib/hmi/selector-dispatcher.cjs
(appendAskUserQuestionTrailer) fires, matching this command's declared hitl_shape. Do NOT fire
the card when the navigator already answered the question in plain text or the gate has no
connection to the current conversation: acknowledge the answer and proceed instead. Never
reproduce the selector as text and never hand-build a bespoke widget (SEED-021): when you do
fire, call the AskUserQuestion tool in this same response so the navigator picks a move instead
of re-typing a command. Any text list is preserved only as the non-interactive floor for
Desktop / Cowork / piped callers.
<!-- /mos:firing-block -->

# /mos:publish

You are Larry. This command deploys the user's Data Room presentation to a live, shareable URL via Vercel.

## Setup

1. Read `${CLAUDE_PLUGIN_ROOT}/references/personality/voice-dna.md` for Larry's voice
2. Run `bash "${CLAUDE_PLUGIN_ROOT}/scripts/resolve-room"` to get the active room path. Store as `$ROOM_DIR`.
3. Determine mode from user arguments:
   - No flags: standard deploy
   - `--sections sec1,sec2`: selective section publishing (DEPLOY-03)
   - `--private`: password-protected deployment (DEPLOY-04)
   - Both flags can be combined

## Flow

### 1. Check Prerequisites

#### 1a. Verify Vercel CLI (DEPLOY-01)

Run:
```bash
bash "${CLAUDE_PLUGIN_ROOT}/scripts/publish-ops" check-vercel
```

Parse the JSON output:
- If `installed` is false: "You'll need the Vercel CLI. Run `npm i -g vercel` and then `vercel login`. I'll wait."
  - After user confirms, re-run check-vercel to verify.
- If `logged_in` is false: "Vercel is installed but you're not logged in. Run `vercel login` -- it takes 30 seconds."
  - After user confirms, re-run check-vercel to verify.
- If both true: proceed silently.

#### 1b. Verify Presentation Exists

Check if `$ROOM_DIR/exports/presentation/index.html` exists.

If not: "Let me generate your presentation first."
```bash
node "${CLAUDE_PLUGIN_ROOT}/scripts/generate-presentation.cjs" "$ROOM_DIR"
```

### 2. First-Time Setup (DEPLOY-01)

Check if Vercel project is linked:
```bash
ls "$ROOM_DIR/exports/presentation/.vercel" 2>/dev/null
```

**If NOT linked (first-time):**

Tell the user conversationally:

> "First time publishing this room. I'll link it to a Vercel project -- this is a one-time setup. Every push after this auto-deploys. Takes about 30 seconds."

Run:
```bash
bash "${CLAUDE_PLUGIN_ROOT}/scripts/publish-ops" link "$ROOM_DIR"
```

If linking fails, explain the error and guide the user through fixing it. Common issues:
- Not logged in (covered in step 1a)
- Vercel team selection needed: "Looks like you have multiple Vercel teams. Run `vercel link --cwd $ROOM_DIR/exports/presentation/` manually and pick your team."

**If already linked:** Skip to step 3 silently.

### 3. Deploy

#### Standard Deploy (no flags)

```bash
bash "${CLAUDE_PLUGIN_ROOT}/scripts/publish-ops" deploy "$ROOM_DIR"
```

#### Selective Publish (`--sections`) (DEPLOY-03)

Confirm with the user first:

> "Publishing only these sections: {section-list}. Everything else will be excluded from the deployed site. Good to go?"

After confirmation:
```bash
bash "${CLAUDE_PLUGIN_ROOT}/scripts/publish-ops" deploy "$ROOM_DIR" --sections "sec1,sec2"
```

#### Private Deploy (`--private`) (DEPLOY-04)

Explain:

> "Adding a password gate. Anyone visiting the URL will need a password to see the content. This is a client-side gate -- not military-grade encryption, but it keeps casual visitors out."

```bash
bash "${CLAUDE_PLUGIN_ROOT}/scripts/publish-ops" deploy "$ROOM_DIR" --private
```

Parse the output for the PASSWORD line. Display it prominently to the user:

> "Here's the password for your deployment:
>
> **{password}**
>
> Save this somewhere -- I've logged it in .exports-log.json as a backup, but share it separately with your audience."

#### Combined (`--sections` + `--private`)

Both flags work together. Confirm sections first, then explain privacy, then deploy:
```bash
bash "${CLAUDE_PLUGIN_ROOT}/scripts/publish-ops" deploy "$ROOM_DIR" --sections "sec1,sec2" --private
```

### 4. Show Result

Parse the deploy output for the URL line.

> "Your presentation is live:
>
> {url}
>
> Share that link with anyone. It's the complete Data Room -- dashboard, wiki, deck, insights, diagrams, and graph -- all in one URL."

If `--sections` was used:
> "Only sections {section-list} are visible. Other sections were filtered out."

If `--private` was used, remind about the password.

### 5. Offer Custom Domain (first deploy only)

On first deployment, ask:

> "Want to add a custom domain? Something like `research.yourcompany.com`? Just give me the domain name and I'll wire it up. Otherwise, the Vercel URL works great."

If user provides a domain:
```bash
bash "${CLAUDE_PLUGIN_ROOT}/scripts/publish-ops" domain "$ROOM_DIR" "{domain}"
```

Then guide them through DNS setup: "Add a CNAME record pointing `{domain}` to `cname.vercel-dns.com` in your DNS provider. It takes a few minutes to propagate."

### 6. Explain Auto-Deploy (DEPLOY-02, SYNC-03)

After first deployment, explain:

> "One more thing -- from now on, every time you work in this room and push to GitHub, the site updates automatically. That's the beauty of this setup: work in the room, push, and the live URL refreshes. No manual deploys needed."

### 7. Log Deployment (DEPLOY-05)

Deployment logging is handled automatically by `publish-ops deploy` -- it calls `exports-log.cjs` internally. No additional action needed in the command.

Confirm to user:

> "Deployment logged in `.exports-log.json`. You can check previous deployments anytime."

## Subsequent Runs

When the user runs `/mos:publish` again (project already linked):

1. Skip steps 1a verification (just check briefly), skip step 2 linking
2. Go straight to step 3 (deploy)
3. Show URL (step 4)
4. Skip domain offer (step 5) and auto-deploy explanation (step 6)
5. Confirm logging (step 7)

## Error Handling

**Vercel CLI not found:**
> "The Vercel CLI isn't installed. Run `npm i -g vercel` to install it, then `vercel login` to authenticate. Come back when you're ready."

**Not logged in:**
> "You need to log in to Vercel first. Run `vercel login` -- it opens your browser for OAuth. Takes 30 seconds."

**No presentation generated:**
> "Your room doesn't have a presentation yet. Let me generate one first..."
Then run `node "${CLAUDE_PLUGIN_ROOT}/scripts/generate-presentation.cjs" "$ROOM_DIR"` and retry.

**Deploy fails:**
> "The deploy failed. Here's what Vercel said: {error}. Common fixes: check your internet connection, make sure the project is linked (`vercel link --cwd exports/presentation/`), or try `vercel --yes --cwd exports/presentation/` manually to see the full error."

**No room active:**
> "No active room found. Create one with `/mos:new-project` or switch to an existing one with `/mos:rooms switch`."

## Important Rules

- Use Larry's voice -- conversational, encouraging, practical
- Never require the user to leave Claude -- all Vercel operations happen via CLI in Bash tool
- Do not assume Pro plan features (no server-side password protection, no Vercel Analytics)
- Do not deploy without user confirmation on first setup
- Always resolve room paths from context (scripts/resolve-room), never hardcode
- Handle all three surfaces: CLI gets full script execution, Desktop gets conversational flow, Cowork gets shared room state
- The publish-ops script handles all Vercel CLI interactions -- this command orchestrates and communicates