@seanyao/roll 4.714.2 → 4.718.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@seanyao/roll",
-  "version": "4.714.2",
+  "version": "4.718.2",
   "description": "Roll — Roll out features with AI agents",
   "packageManager": "pnpm@11.1.3",
   "scripts": {
@@ -8,6 +8,8 @@
     "lint:story-ids": "node scripts/lint-story-ids.mjs",
     "lint:role-taxonomy": "node scripts/audit-role-taxonomy.mjs",
     "test:e2e": "pnpm -r build && pnpm --filter @roll/cli exec vitest run test/critical-flows.e2e.test.ts",
+    "test:browser-live": "pnpm -r build && ROLL_BROWSER_LIVE=1 pnpm --filter @roll/cli exec vitest run --config vitest.live.config.ts",
+    "test:controlled-capture-live": "pnpm -r build && ROLL_BROWSER_LIVE=1 pnpm --filter @roll/infra exec vitest run --config vitest.live.config.ts",
     "test:cov": "pnpm -r exec vitest run --coverage.enabled --coverage.provider=v8 --coverage.include='src/**' --coverage.reporter=text-summary --coverage.reporter=text",
     "bundle": "node scripts/bundle.mjs",
     "postinstall": "node scripts/postinstall-roll-capture.mjs",
@@ -28,6 +30,14 @@
   "bin": {
     "roll": "dist/roll.mjs"
   },
+  "dependencies": {
+    "chromium-bidi": "^12.0.0",
+    "playwright-core": "1.61.1"
+  },
+  "bundledDependencies": [
+    "chromium-bidi",
+    "playwright-core"
+  ],
   "license": "MIT",
   "author": "Sean Yao <sean.dlut@gmail.com>",
   "files": [

package/skills/roll-build/SKILL.md

@@ -34,7 +34,7 @@ same TCR, evidence, Evaluator, and release gates apply in both modes.
 2. Read backlog/spec and decide if the story fits one cycle.
 3. Split into small TCR actions; per Action route objective work to the 4-stage TCR loop and judgment-dependent work to a 3-stage criteria+Evaluator loop, then define verification.
 4. Run test-first implementation, self-review, evidence, and write-back.
-5. Commit on green, open PR, and leave remote evidence.
+5. Commit green TCR work, then hand off publishing and remote evidence to the Runner.
 
 ## Hard Gates
 
@@ -42,6 +42,7 @@ same TCR, evidence, Evaluator, and release gates apply in both modes.
 - No WIP commits or bypassed verification.
 - In the test-gated loop the tests are the weakest link: an isolated Test Adequacy reviewer (Phase 6 Agent 4) audits the tests against the AC, seeing only AC + test files — never the implementation diff or builder reasoning. Self-review of one's own tests (Phase 2) is necessary but not isolation.
 - Self-review, attest, and E2E evidence remain required. The Review Score is produced by the runner's fresh-session peer Reviewer — the agent does NOT self-score.
+- Inside a `roll-loop` cycle, never run `git push` or `gh pr create`; the Runner owns branch publication and PR creation after the gates pass.
 - Docs/code/product alignment is a DoD gate: user-visible behavior, command, output-copy, site, or delivery-view changes update the touched README/docs/guide/site/help in the same delivery.
 - Done ≡ merged to `main`. After publish the cycle is `awaiting_merge`; the Delivery Reconciler (no daemon) self-drives the merge and reconciles truth from `main` — manual merges are first-class (`delivered_external`). Never pre-flip a card to Done on an open PR.
 

package/skills/roll-build/references/full-contract.md

@@ -579,15 +579,17 @@ the full diff as a single-pass fallback — do not skip review entirely.
 🟢 Suggestions / ✅ All clear → Proceed to Phase 7
 ```
 
-### Phase 7: Commit & Push (branch + PR — NEVER direct to main)
+### Phase 7: Commit & Publish Handoff
 
-`main` is PR-protected. Push the worktree's branch and open a PR — never
-`git push origin main`. (When invoked by `roll-loop`, the runner already
-created the worktree + branch and opens the PR; this is the manual-path
-equivalent.)
+`main` is PR-protected. In a standalone guided session, push the worktree's
+branch and open a PR — never `git push origin main`. Inside a `roll-loop`
+cycle, stop after the green commits and evidence: the Runner publishes the
+branch and opens the PR after its gates pass. Do not run `git push` or
+`gh pr create` inside the Builder session.
 
 ```bash
-# All TCR micro-commits are already made on the worktree's branch (step A3.1).
+# Standalone guided session only. All TCR micro-commits are already made on
+# the worktree's branch (step A3.1).
 git log --oneline -{n}                 # Review TCR commits
 git push -u origin <branch>            # the dispatch/<id> branch from step A3.1
 gh pr create --title "{story-id}: …" --body "…"
@@ -761,12 +763,13 @@ delivered. Consequences you can rely on:
   PR-state (L1) / patch-id (L2) and flips the cycle to `delivered` — manual /
   external merges included (`delivered_external` is first-class).
 
-So on the manual path, flip the row to Done **after** the PR merges; under
-`roll-loop` the cycle ends at publish (`awaiting_merge`) and the reconciler
+So on the manual path, flip the row to Done **after** the PR merges. Under
+`roll-loop`, the Builder must not edit shared `.roll` completion status at
+all: the cycle ends at publish (`awaiting_merge`) and the reconciler
 self-drives the merge (`gh pr merge --squash` on green CI) and flips the row
 once the merge lands on `main` — do not pre-flip on a still-open PR.
 
-Both locations must be updated — neither can be skipped:
+On the manual path, both locations must be updated — neither can be skipped:
 
 **① Update .roll/backlog.md index row (Status column):**
 
@@ -777,7 +780,7 @@ Both locations must be updated — neither can be skipped:
 | [US-{ID}](.roll/features/<epic>/US-{ID}/spec.md) | {Title} | ✅ Done · [evidence](.roll/features/<epic>/US-{ID}/latest/US-{ID}-report.html) |
 ```
 
-Change the Status from `📋 Todo` or `🔨 In Progress` (whichever the row currently shows) to `✅ Done`. When invoked by `roll-loop`, the row will already be `🔨 In Progress` — that is the expected starting state, and the transition is the same Edit operation.
+Change the Status from `📋 Todo` or `🔨 In Progress` (whichever the row currently shows) to `✅ Done`.
 For Fly mode: first append an index row under the appropriate Epic > Feature group, then mark it done.
 
 **② Update `.roll/features/<epic>/<story>/spec.md`:**
@@ -804,7 +807,9 @@ For Fly mode: first append an index row under the appropriate Epic > Feature gro
 If the US section does not yet exist, create the full section (AC / Files / Dependencies).
 
 **Before committing, run `$roll-.changelog`** to stage CHANGELOG.md — then include
-it in the completion commit so no separate changelog commit is created.
+it in the completion commit so no separate changelog commit is created. This
+manual-path section does not apply inside `roll-loop`; its Runner owns
+metadata reconciliation after merge.
 
 ```bash
 # 1. Stage changelog (roll-.changelog stages CHANGELOG.md only, does not commit)
@@ -857,11 +862,10 @@ Before creating any file or directory:
 0. **Worktree-first, PR-at-end (ALWAYS)**
    Before writing any code, work in a dedicated git worktree on its own
    branch (`git worktree add ../wt-<id> -b <branch>`), never in the shared
-   checkout — so concurrent cycles / sessions never collide. Finish by
-   pushing the branch and opening a PR; `main` is PR-protected — NEVER
-   `git push origin main`. (Under `roll-loop` the runner creates the
-   worktree + branch and opens the PR; this rule is the manual-path
-   equivalent and must hold either way.)
+   checkout — so concurrent cycles / sessions never collide. In a standalone
+   session, finish by pushing the branch and opening a PR; `main` is
+   PR-protected — NEVER `git push origin main`. Under `roll-loop`, finish
+   green commits and evidence only: the Runner creates the PR.
 
 1. **No local-only "done" — Done ≡ merged (FIX-322/323)**
    Work is not complete until it reaches: