# 0.1.4 Release Prep Implementation Plan

> **For Claude:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.

**Goal:** Prepare the repository for a local/manual `0.1.4` release and verify it is ready to publish.

**Architecture:** Keep the release prep narrowly scoped to version metadata, local release instructions, and preflight verification. Do not publish from the implementation step; instead, leave the workspace in a verified, reviewable state and hand off the final npm commands.

**Tech Stack:** Node.js, npm, PowerShell, package metadata files

---

### Task 1: Update Release Metadata

**Files:**
- Create: `docs/plans/2026-03-01-release-0.1.4-design.md`
- Create: `docs/plans/2026-03-01-release-0.1.4.md`
- Modify: `package.json`
- Modify: `package-lock.json`
- Modify: `.anson/release-ci-cd-notes.md`

**Step 1: Write the failing test**

Inspect the current version references and confirm they still show `0.1.3`.

**Step 2: Run test to verify it fails**

Run: `rg -uu -n "0\\.1\\.3|0\\.1\\.4" .`
Expected: package metadata and local release-note examples still point to `0.1.3`.

**Step 3: Write minimal implementation**

- Change package version fields to `0.1.4`.
- Update local release-note example commands and CDN URLs to `0.1.4`.
- Save the release design and implementation plan docs.

**Step 4: Run test to verify it passes**

Run: `rg -uu -n "0\\.1\\.3|0\\.1\\.4" package.json package-lock.json .anson/release-ci-cd-notes.md`
Expected: only `0.1.4` appears in those release-facing files.

**Step 5: Commit**

```bash
git add docs/plans/2026-03-01-release-0.1.4-design.md docs/plans/2026-03-01-release-0.1.4.md package.json package-lock.json .anson/release-ci-cd-notes.md
git commit -m "release: prep v0.1.4"
```

### Task 2: Run Release Preflight

**Files:**
- Modify: `dist/docx-redline-js.esm.js`

**Step 1: Write the failing test**

Assume the built artifact banner still reflects the previous version until the build runs.

**Step 2: Run test to verify it fails**

Run: `rg -n "v0\\.1\\.3|v0\\.1\\.4" dist/docx-redline-js.esm.js`
Expected: the banner still shows `v0.1.3` before rebuilding.

**Step 3: Write minimal implementation**

Run the documented preflight:

- `npm test:isolation`
- `npm test`
- `npm run build`
- `npm pack --dry-run`

**Step 4: Run test to verify it passes**

Run: `rg -n "v0\\.1\\.3|v0\\.1\\.4" dist/docx-redline-js.esm.js`
Expected: the banner shows `v0.1.4`, and the preflight commands complete successfully.

**Step 5: Commit**

```bash
git add dist/docx-redline-js.esm.js
git commit -m "build: refresh dist for v0.1.4"
```

### Task 3: Publish Handoff

**Files:**
- No file changes

**Step 1: Write the failing test**

Confirm the package is not yet published from this session.

**Step 2: Run test to verify it fails**

Run: `npm view @ansonlai/docx-redline-js version`
Expected: the registry version may still report the prior published release until you publish manually.

**Step 3: Write minimal implementation**

Provide the exact local commands for npm auth check, publish, optional tag push, and post-publish verification.

**Step 4: Run test to verify it passes**

User runs the publish commands locally and confirms `npm view @ansonlai/docx-redline-js version` returns `0.1.4`.

**Step 5: Commit**

No additional commit required.