@seanyao/roll 2026.420.3 → 2026.421.2

package/bin/roll

@@ -4,7 +4,7 @@ set -euo pipefail
 # Roll — AI Agent Convention Manager
 # Single source of truth for how all AI coding agents behave.
 
-VERSION="2026.420.3"
+VERSION="2026.421.2"
 ROLL_HOME="${ROLL_HOME:-${HOME}/.roll}"
 ROLL_CONFIG="${ROLL_HOME}/config.yaml"
 ROLL_GLOBAL="${ROLL_HOME}/conventions/global"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@seanyao/roll",
-  "version": "2026.420.3",
+  "version": "2026.421.2",
   "description": "Roll — Roll out features with AI agents",
   "scripts": {
     "test": "find tests/unit tests/integration -name '*.bats' | sort | xargs ./tests/helpers/bats-core/bin/bats"

package/skills/roll-build/SKILL.md

@@ -132,6 +132,22 @@ Before any code, assess clarity:
 - Follow with 3–5 targeted questions
 - Stop and wait for user answers before proceeding
 
+**Approach Confirmation (required for UX / format / automation decisions):**
+
+If the request involves any of: output format, layout, automation level (manual vs automatic), or architecture structure — output a confirmation block **before writing any code**:
+
+```
+📐 Approach Confirmation
+
+   1. What changes: {what will be built or modified}
+   2. The approach: {specific format / automation level / structure chosen}
+   3. Files touched: {list of files}
+
+   Proceeding unless you say otherwise.
+```
+
+Wait for the user's response before editing files. If the user does not object within one exchange, proceed.
+
 **Complexity Rules (AI coding time):**
 
 | Level | Scope | Action |

package/skills/roll-release/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: roll-release
-description: Release skill for roll maintainers. Calculates next version (YYYY.MMDD.N format, auto-increments N from today's git tags), updates VERSION in bin/roll and package.json, commits, tags, and pushes to trigger npm auto-publish via GitHub Actions. Trigger: "release", "publish", "发版", "发布新版本".
+description: "Release skill for roll maintainers. Calculates next version (YYYY.MMDD.N format, auto-increments N from today's git tags), updates VERSION in bin/roll and package.json, commits, tags, and pushes to trigger npm auto-publish via GitHub Actions. Trigger: release, publish, 发版, 发布新版本."
 ---
 
 # Release (roll-release)
@@ -9,17 +9,25 @@ One-command publish flow for roll maintainers.
 
 ## Version Format
 
-`YYYY.MMDD.N` — e.g. `2026.0419.1`
+`YYYY.MMDD.N` — e.g. `2026.419.1`
 
-- `YYYY.MMDD` = today's date
+- `YYYY.MMDD` = today's date, month has **no leading zero** (e.g. `420` not `0420`)
 - `N` = auto-incremented from existing git tags for today (starts at 1)
 
 ## Execution Steps
 
 ### Step 1: Calculate Version
 
+First, inspect recent tags to confirm the actual format in use:
+
+```bash
+git tag | sort -V | tail -5
+```
+
+Then calculate:
+
 ```bash
-today=$(date +%Y.%m%d)
+today=$(date +%Y.%-m%d)
 last_n=$(git tag | grep "^v${today}\." | sed "s/^v${today}\.//" | sort -n | tail -1)
 n=$(( ${last_n:-0} + 1 ))
 version="${today}.${n}"
@@ -27,7 +35,8 @@ version="${today}.${n}"
 
 Show the proposed version to the user:
 ```
-Proposed version: v2026.0419.1
+Recent tags: v2026.419.1  v2026.419.2  v2026.420.3
+Proposed version: 2026.420.4
 Proceed? [y/N]
 ```
 
@@ -61,15 +70,21 @@ git tag "v${version}"
 git push && git push --tags
 ```
 
-GitHub Actions `publish.yml` picks up the `v*` tag and auto-runs `npm publish`.
+### Step 5: Publish to npm
+
+```bash
+npm publish --access public
+```
+
+This will open a browser for 2FA verification. Wait for it to complete before continuing.
 
-### Step 5: Confirm
+### Step 6: Confirm
 
-After push, show:
+After publish, show:
 ```
 ✅ Released v{version}
 🏷  Tag: v{version} pushed to origin
-📦 npm publish triggered via GitHub Actions
+📦 npm published: @seanyao/roll@{version}
 🔗 https://www.npmjs.com/package/@seanyao/roll
 ```