@seanyao/roll 2026.524.2 → 2026.526.1

package/lib/slides/components/pipeline.html

@@ -0,0 +1,12 @@
+<!-- pipeline: requires stages[].{title_en,title_zh,desc_en,desc_zh,css_class} -->
+<div class="pipeline-bar">
+{{#stages}}
+<div class="pipe-stage {{css_class}}">
+<h4><span class="lang-en">{{title_en}}</span><span class="lang-zh">{{title_zh}}</span></h4>
+<p><span class="lang-en">{{desc_en}}</span><span class="lang-zh">{{desc_zh}}</span></p>
+</div>
+{{^last}}
+<div class="pipe-arrow">→</div>
+{{/last}}
+{{/stages}}
+</div>

package/lib/slides/components/plain.html

@@ -0,0 +1,7 @@
+<!-- plain: requires body_en (raw HTML), body_zh (raw HTML) -->
+<div class="lang-en">
+{{{body_en}}}
+</div>
+<div class="lang-zh">
+{{{body_zh}}}
+</div>

package/lib/slides/components/quote.html

@@ -0,0 +1,4 @@
+<!-- quote: requires text_en, text_zh -->
+<div class="quote-block">
+<p><span class="lang-en">{{text_en}}</span><span class="lang-zh">{{text_zh}}</span></p>
+</div>

package/lib/slides/components/timeline.html

@@ -0,0 +1,9 @@
+<!-- timeline: requires items[].{title_en,title_zh,body_en,body_zh} -->
+<div class="timeline">
+{{#items}}
+<div class="timeline-item">
+<h4><span class="lang-en">{{title_en}}</span><span class="lang-zh">{{title_zh}}</span></h4>
+<p><span class="lang-en">{{{body_en}}}</span><span class="lang-zh">{{{body_zh}}}</span></p>
+</div>
+{{/items}}
+</div>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@seanyao/roll",
-  "version": "2026.524.2",
+  "version": "2026.526.1",
   "description": "Roll — Roll out features with AI agents",
   "scripts": {
     "test": "bash tests/run.sh"

package/skills/roll-brief/SKILL.md

@@ -179,8 +179,8 @@ git push origin main
 写完文件后在终端或 CI 日志中打印简报路径：
 
 ```
-📋 简报已生成：.roll/briefs/2026-05-10-01.md
-   发布就绪：✅ 可发版
+📋 $(msg brief.generated ".roll/briefs/YYYY-MM-DD-NN.md")
+   $(msg brief.release_readiness): ✅ $(msg brief.release_ready_status)
 ```
 
 有升级事项时须显著打印，不得遗漏。

package/skills/roll-build/SKILL.md

@@ -90,16 +90,16 @@ git worktree add .worktrees/{action-id} -b dispatch/{action-id}
 **Status notifications (required):**
 
 ```
-🔀 Parallel Dispatch: N Actions running in parallel
+🔀 $(msg build.parallel_dispatch N)
 
-  Agent 1 [Action: ...]  ⏳ Running...
-  Agent 2 [Action: ...]  ⏳ Running...
+  $(msg build.agent_running 1 "...")
+  $(msg build.agent_running 2 "...")
 
-  Agent 1 [Action: ...]  ✅ Done (N TCR commits)
-  Agent 2 [Action: ...]  ✅ Done (N TCR commits)
+  $(msg build.agent_done 1 "..." N)
+  $(msg build.agent_done 2 "..." N)
 
-🔀 Merge: N/N succeeded, merging...
-🧪 Integration tests: running...
+🔀 $(msg build.merge_summary N N)
+🧪 $(msg build.integration_tests)
 ```
 
 When parallel conditions are not met, execute Actions sequentially.
@@ -123,9 +123,9 @@ Activate when input does not match any `US-XXX` / `FIX-XXX` pattern, or when no
 Before any code, assess clarity:
 
 ```
-🎯 Clarified Goal: {1-2 sentences capturing user intent}
-📏 Complexity Assessment: {small|medium|large}
-🔍 Uncertainty Areas: {list what needs investigation/decision}
+🎯 $(msg build.clarified_goal): {1-2 sentences capturing user intent}
+📏 $(msg build.complexity_assessment): {small|medium|large}
+🔍 $(msg build.uncertainty_areas): {list what needs investigation/decision}
 ```
 
 **If uncertainty areas are non-empty or the request is vague, auto-trigger `$roll-.clarify`:**
@@ -138,11 +138,11 @@ Before any code, assess clarity:
 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
+📐 $(msg build.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}
+   1. $(msg build.what_changes): {what will be built or modified}
+   2. $(msg build.the_approach): {specific format / automation level / structure chosen}
+   3. $(msg build.files_touched): {list of files}
 
    Proceeding unless you say otherwise.
 ```
@@ -205,14 +205,14 @@ Press Enter to launch peer review, or type 'n' to skip. Auto-executing in 10s...
 Before writing implementation code:
 
 ```
-🧪 Test Design for Action: {Action name}
+🧪 $(msg build.test_design): {Action name}
 
-   Scenarios:
+   $(msg build.scenarios):
    ├── {Happy path scenario}
    ├── {Edge case scenario}
    └── {Failure/regression scenario}
 
-   Test Types:
+   $(msg build.test_types):
    ├── Unit tests for: {logic components}
    ├── Integration tests for: {API/data flows}
    └── Manual verification for: {UI/visual elements}
@@ -231,10 +231,10 @@ Reference `$roll-.qa` for coverage requirements and test pyramid strategy.
 
 ```
 ┌────────────────────────────────────────────────────────────┐
-│  TCR CYCLE (Test && Commit || Revert)                       │
+│  $(msg build.tcr_cycle)                                      │
 └────────────────────────────────────────────────────────────┘
 
-MICRO-STEP {N}: {description of smallest testable change}
+$(msg build.micro_step {N} "{description of smallest testable change}")
 
    Step 1: Write/Update Test
       └── Run test → Confirm RED (expected failure)
@@ -485,17 +485,17 @@ Follow the repo's deployment path (Vercel / Railway / etc.) and record the deplo
 **Before marking as DONE, fresh evidence must be provided.**
 
 ```
-🚦 Verification Gate
+🚦 $(msg build.verification_gate)
 
-   Evidence checklist (each item must have actual output):
-   ├── [ ] Tests passed: paste actual test run output
-   ├── [ ] Build succeeded: paste build output
-   ├── [ ] Online verification: screenshot / curl output / log snippet
-   └── [ ] No regression: verify at least one existing feature still works
+   $(msg build.evidence_checklist):
+   ├── [ ] $(msg build.tests_passed)
+   ├── [ ] $(msg build.build_succeeded)
+   ├── [ ] $(msg build.online_verification)
+   └── [ ] $(msg build.no_regression)
 
-   Gate Decision:
-   ├── ✅ All items have evidence → Can mark as DONE
-   └── ❌ Any item missing evidence → Gather evidence before passing the gate
+   $(msg build.gate_decision):
+   ├── ✅ $(msg build.gate_pass)
+   └── ❌ $(msg build.gate_fail)
 ```
 
 **Hard Rule**: "I confirmed the tests passed" does not count as evidence. Must be **freshly run** command output from this session.
@@ -552,20 +552,20 @@ git push
 ### Phase 12: Report & Celebrate
 
 ```
-✅ Pushed to GitHub: origin/main
-🚀 Deployed: <url>
-✅ Verified: <what was checked>
-📦 Changes: <summary>
-🔢 Commits: <count> micro-commits via TCR
-🧪 Tests: <what tests were added/modified>
-📊 TCR Stats: <success rate, revert count if any>
-📋 Review Gate: <self-review findings summary>
-📝 BACKLOG: <US-ID> marked ✅ Done
-📄 CHANGELOG: bundled into completion commit (Phase 11)
+✅ $(msg build.pushed_to)
+🚀 $(msg build.deployed): <url>
+✅ $(msg build.verified): <what was checked>
+📦 $(msg build.changes_summary): <summary>
+🔢 $(msg build.commits_count): <count> micro-commits via TCR
+🧪 $(msg build.tests_added): <what tests were added/modified>
+📊 $(msg build.tcr_stats): <success rate, revert count if any>
+📋 $(msg build.review_gate): <self-review findings summary>
+📝 $(msg build.backlog_updated "<US-ID>")
+📄 $(msg build.changelog_bundled)
 
-🎉 Shipped.
+🎉 $(msg build.shipped)
 
-🔄 Next Options:
+🔄 $(msg build.next_options):
 1. Continue to next Action (if Story has more)
 2. Start next US (if Fly mode created multiple)
 3. Done (if all completed)

package/skills/roll-fix/SKILL.md

@@ -100,13 +100,13 @@ Before creating any file or directory:
 ### 3. Test Design Review (TCR Core)
 
 ```
-🧪 Test Design for Fix:
+🧪 $(msg fix.test_design):
    
-   Verification Approach: {unit test | integration test | manual check}
+   $(msg fix.verification_approach): {unit test | integration test | manual check}
    
-   Test Scenarios:
-   ├── Fix verification: {how to confirm the fix works}
-   └── Regression check: {how to ensure we didn't break anything}
+   $(msg fix.test_scenarios):
+   ├── $(msg fix.fix_verification): {how to confirm the fix works}
+   └── $(msg fix.regression_check): {how to ensure we didn't break anything}
 ```
 
 **Reference `$roll-.qa` for test strategy:**
@@ -122,10 +122,10 @@ Before creating any file or directory:
 
 ```
 ┌─────────────────────────────────────────────────────────────────────┐
-│ TCR CYCLE FOR FIX                                                    │
+│ $(msg fix.tcr_cycle)                                                 │
 └─────────────────────────────────────────────────────────────────────┘
 
-MICRO-STEP 1: {description of the fix}
+$(msg fix.micro_step 1 "{description of the fix}")
 
    Step 1: Write/Update Test
       └── Run test → Confirm RED (bug reproduced or test fails)
@@ -198,12 +198,12 @@ $roll-.review staged
 
 **Review Output:**
 ```
-🔍 Self Review Report
-├── Scope: X files (+Y/-Z lines)
-├── 🔴 Critical: N issues (must fix)
-├── 🟡 Warnings: N issues (should fix)
-├── 🟢 Suggestions: N items (optional)
-└── ✅ Passed dimensions: [...]
+🔍 $(msg fix.self_review)
+├── $(msg fix.scope): X files (+Y/-Z lines)
+├── 🔴 $(msg fix.critical): N issues (must fix)
+├── 🟡 $(msg fix.warnings): N issues (should fix)
+├── 🟢 $(msg fix.suggestions): N items (optional)
+└── ✅ $(msg fix.passed_dimensions): [...]
 ```
 
 **Review Dimensions** (correctness guaranteed by TCR):
@@ -269,17 +269,17 @@ Verify the shipped fix on the deployed target:
 **Fresh evidence** must be provided — claiming completion based on assumptions is not acceptable.
 
 ```
-🚦 Verification Gate
+🚦 $(msg build.verification_gate)
    
-   Evidence checklist (each item must have actual output):
-   ├── [ ] Tests pass: paste actual test run output
-   ├── [ ] Build succeeds: paste build output
-   ├── [ ] Issue resolved: screenshot / curl output / log excerpt as proof
-   └── [ ] No regression: verify at least one existing feature still works
+   $(msg build.evidence_checklist):
+   ├── [ ] $(msg build.tests_passed)
+   ├── [ ] $(msg build.build_succeeded)
+   ├── [ ] $(msg fix.issue_resolved): screenshot / curl output / log excerpt as proof
+   └── [ ] $(msg build.no_regression)
    
-   Gate Decision:
-   ├── ✅ All items have evidence → Can mark as DONE
-   └── ❌ Any item lacks evidence → Provide evidence before passing the gate
+   $(msg build.gate_decision):
+   ├── ✅ $(msg build.gate_pass)
+   └── ❌ $(msg build.gate_fail)
 ```
 
 **Hard Rule**: "I confirm tests passed" does not count as evidence. It must be **freshly run** command output from this session.

package/skills/roll-loop/SKILL.md

@@ -6,7 +6,8 @@ description: |
   Autonomous BACKLOG executor. Runs on a schedule (hourly via cron or GitHub
   Actions), scans .roll/backlog.md for 📋 Todo items, and routes each to the
   appropriate skill: US-XXX → $roll-build, FIX-XXX → $roll-fix,
-  REFACTOR-XXX → $roll-build. Handles agent fallback on token/network failure.
+  REFACTOR-XXX → $roll-build. Retries the primary agent up to 3 times on
+  transient failure; pauses with ALERT on persistent failure.
   Never cuts a release autonomously — release is always a human decision.
   Triggers roll-brief when a Feature completes.
 ---
@@ -73,8 +74,7 @@ denied operations and the cycle will idle-exit.
 ```yaml
 # ~/.roll/config.yaml
 loop:
-  primary_agent: claude          # claude | deepseek | kimi
-  fallback_agent: deepseek       # used when primary fails
+  primary_agent: claude          # claude | deepseek | kimi | pi | ...
   max_items_per_run: 1           # one story per cycle — atomic delivery, predictable cycle time
   brief_on_feature_complete: true
   retry_backoff: [2, 4, 8, 16]  # seconds, exponential
@@ -103,12 +103,24 @@ this point, any `🔨 In Progress` row in `.roll/backlog.md` belongs to a
 previous cycle that crashed before flipping it back; reclaim it before
 scanning.
 
+**Important — skip `manual-only:*` rows.** A row tagged `manual-only:*`
+means a human (or another non-loop process) has explicitly claimed it;
+it is not loop's to reclaim. Reverting it would silently undo the
+human's claim and cause confusing churn for `roll-brief` / dashboard
+readers. The rule mirrors the gate in Step 2.
+
 1. Scan .roll/backlog.md for all rows whose Status column contains `🔨 In Progress`.
-2. For each row found: revert the status back to `📋 Todo`, commit
-   `chore: revert orphan 🔨 US-XXX to 📋`, and append a line to
-   `~/.shared/roll/loop/ALERT-<slug>.md` recording the orphan id and time
-   so the next brief surfaces it.
-3. After orphan sweep, proceed to Step 1.5 (Pre-run CI health check) before scanning.
+2. For each candidate row, run the manual-only gate before touching it:
+   ```bash
+   bash -c 'source "$(command -v roll)"; _loop_is_manual_only "<story-id>" .roll/backlog.md'
+   #   exit 0 → row has `manual-only:*` → SKIP (human-claimed; not orphan)
+   #   exit 1 → reclaimable orphan; continue to step 3
+   ```
+3. For each row that passes the gate: revert the status back to
+   `📋 Todo`, commit `chore: revert orphan 🔨 US-XXX to 📋`, and append
+   a line to `~/.shared/roll/loop/ALERT-<slug>.md` recording the orphan
+   id and time so the next brief surfaces it.
+4. After orphan sweep, proceed to Step 1.5 (Pre-run CI health check) before scanning.
 
 ### Step 1.5 — Pre-run CI Health Check
 
@@ -427,21 +439,20 @@ Attempt 1 fails
 
 ```
 Primary agent fails (non-network error)
-  → switch to fallback_agent from config
-  → retry current item with fallback
-  → if fallback also fails → PAUSE
+  → 3 attempts at the agent_invoke phase (with 30s back-off between)
+  → still failing → PAUSE
 ```
 
 ### Pause + Alert
 
-When both agents fail:
+When the primary agent exhausts its retry budget:
 
 1. Write state:
 ```yaml
 status: paused
 paused_at: "2026-05-10T02:07:00+08:00"
 paused_on: US-AUTH-003
-reason: "both primary (claude) and fallback (deepseek) unavailable"
+reason: "primary agent (claude) unavailable after 3 attempts"
 ```
 
 2. Write alert:
@@ -450,11 +461,11 @@ reason: "both primary (claude) and fallback (deepseek) unavailable"
 
 **Time**: 2026-05-10 02:07
 **Paused on**: US-AUTH-003
-**Reason**: claude: token exhausted; deepseek: network error after 5 retries
+**Reason**: claude exited non-zero on 3 consecutive attempts
 
 **Action required** (choose one):
 - Top up credits and run: `roll loop resume`
-- Switch agent: edit `~/.roll/config.yaml` → `loop.primary_agent`
+- Switch agent: edit `~/.roll/config.yaml` → `primary_agent`
 - Take over manually: `$roll-build US-AUTH-003`
 ```
 

package/skills/roll-onboard/SKILL.md

@@ -65,15 +65,15 @@ Run `roll-doc --dry-run` (READ-ONLY mode). This reports:
 
 Present these in chat. **Aim for total time ≤ 3 minutes.** Group 1 confirms your understanding; group 2 scopes the work; group 3 handles privacy and next steps.
 
-**Group 1 — Project cognition check**
+**$(msg onboard.questions_group1)**
 
-1. I see this is a **[type]** project doing **[description]** — correct?
-2. The main business domains look like **[domain A, domain B, …]** — anything to add or correct?
-3. The key modules are **[X, Y, Z]** — any missed or mis-identified?
+1. $(msg onboard.q1 "[type]" "[description]")
+2. $(msg onboard.q2 "[domain A, domain B, …]")
+3. $(msg onboard.q3 "[X, Y, Z]")
 
-**Group 2 — Generation scope**
+**$(msg onboard.questions_group2)**
 
-4. Which artifacts should I generate? Multi-select:
+4. $(msg onboard.q4) Multi-select:
    - `backlog` — initial BACKLOG with seeded stories
    - `features` — features index + per-feature spec stubs
    - `domain` — DDD context map