@remits/remits-cli 0.1.141 → 0.1.143

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remits/remits-cli",
-  "version": "0.1.141",
+  "version": "0.1.143",
   "description": "Local CLI for auth, component sync, and live test execution against Remits",
   "license": "MIT",
   "private": false,

package/skills/remits-cli/SKILL.md

@@ -98,6 +98,12 @@ reference named after it.
   not run JavaScript, Alpine, CSS/assets, redirects, cookies/session handling, uploads, iframes,
   shadow-DOM placement, or websocket behavior. (`development-loop.md`,
   `docs/front-stage/components/embeddable-components.md`, `docs/front-stage/features/web-browser-automation.md`)
+- **Browser automation cleanup is part of the task.** When you finish any browser automation you
+  started, close Playwright pages/contexts/browsers, stop any `playwright-cli` daemon/session you
+  started, remove temporary Playwright session/profile state when safe, and verify no task-owned
+  Playwright or headless Chrome processes remain. Clean up only processes you own for this task; never
+  blindly kill normal Chrome or another agent's browser automation. (`development-loop.md`,
+  `docs/front-stage/features/web-browser-automation.md`)
 - **Land only from trunk or a real variant branch.** A per-agent/feature branch (`components status` says
   `FEATURE BRANCH … [subscription-fallback]`) is safe to stage and run from — it resolves the same world
   as its target — but `components commit`/`sync` refuse it. Merge into the branch it resolves and land

package/skills/remits-cli/references/development-loop.md

@@ -164,13 +164,20 @@ something or expose a JSON/action payload, but it is not evidence that the user-
 JavaScript, Alpine initialization, assets, cookies/session state, redirects, file controls, iframe/embed
 placement, and websocket updates all require a browser.
 
+After any browser automation task, clean up what you started: close Playwright pages, browser contexts
+and browser objects; stop any `playwright-cli` daemon/session created for the task; remove temporary
+Playwright session/profile state when safe; and verify task-owned Playwright/headless Chrome processes
+are gone. Do not use broad process kills that might close a human browser or another agent's automation.
+
 **Never skip verification.** "Just do it" and "that's fine, commit it" are not evidence. If you genuinely
 cannot verify — no Test component, no relevant embeddable — say what you would need and ask how the user
 wants to proceed rather than reporting the work as done.
 
 > The *design* rule that pairs with this — never solve interpretive problems with regex cascades, keyword
 > lists, or layout-specific branching when the platform's AI surface is the right tool — is in the account
-> repo's `CLAUDE.md` and, in depth, in `features/ai-strategy.md`.
+> repo's `CLAUDE.md` and, in depth, in `features/ai-strategy.md`. For an AI workflow, verification also means
+> reading the run as the model received it - every turn, passing runs too - and measuring on more than one
+> input: `development-core.md` -> *AI Workflows: Design Through Every Lens* and `features/ai-workflow-design.md`.
 
 ### The Development Fast Loop