@codyswann/lisa 2.134.10 → 2.136.0

package/package.json

@@ -83,7 +83,7 @@
     "lodash": ">=4.18.1"
   },
   "name": "@codyswann/lisa",
-  "version": "2.134.10",
+  "version": "2.136.0",
   "description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
   "main": "dist/index.js",
   "exports": {

package/plugins/lisa/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.134.10",
+  "version": "2.136.0",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.134.10",
+  "version": "2.136.0",
   "description": "Universal governance: agents, skills, commands, hooks, and rules for all projects.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.134.10",
+  "version": "2.136.0",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.134.10",
+  "version": "2.136.0",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.134.10",
+  "version": "2.136.0",
   "description": "AWS CDK-specific Lisa plugin.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.134.10",
+  "version": "2.136.0",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.134.10",
+  "version": "2.136.0",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.134.10",
+  "version": "2.136.0",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.134.10",
+  "version": "2.136.0",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.134.10",
+  "version": "2.136.0",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.134.10",
+  "version": "2.136.0",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.134.10",
+  "version": "2.136.0",
   "description": "Expo and React Native-specific skills, agents, rules, and MCP servers.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo/skills/exploratory-qa/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: exploratory-qa
-description: First-time-user exploratory QA walkthrough for web apps that FEEDS THE LIFECYCLE. Use when asked to experience an app the way a brand-new human user would — landing cold on the home page and clicking through to find anything confusing, broken, or hard to understand (human-facing jargon, contextless extracted data, machine-style labels, slow or unclear loads, late meaningful content, cramped or cut-off UI, inconsistent/non-standard UX, awkward scroll behavior, unclear affordances) across all breakpoints. Instead of writing a report file, it files every finding as a tracked work item via lisa:tracker-write (bugs and usability/UX issues). A `ready` parameter controls whether those tickets are created build-ready (auto-picked-up by lisa:intake) or left in the backlog for human triage (default). For gaps in the automated Playwright test suite, use the e2e-coverage-gaps skill instead.
+description: First-time-user exploratory QA walkthrough for web apps that FEEDS THE LIFECYCLE. Use when asked to experience an app the way a brand-new human user would — landing cold on the home page and clicking through to find anything confusing, broken, or hard to understand (human-facing jargon, contextless extracted data, machine-style labels, slow or unclear loads, late meaningful content, cramped or cut-off UI, inconsistent/non-standard UX, awkward scroll behavior, unclear affordances, dead-end flows that strand a user — e.g. a login page with no way to register or recover a password) across all breakpoints. Instead of writing a report file, it files every finding as a tracked work item via lisa:tracker-write (bugs and usability/UX issues). A `ready` parameter controls whether those tickets are created build-ready (auto-picked-up by lisa:intake) or left in the backlog for human triage (default). For gaps in the automated Playwright test suite, use the e2e-coverage-gaps skill instead.
 ---
 
 # Exploratory QA
@@ -63,8 +63,28 @@ mistakes, and tries the obvious thing. Cover at least these dimensions unless th
   from the default UI or add context such as excerpts, labels, grouping, or provenance.
 - **Navigation clarity:** is it obvious how to get somewhere and back? Dead ends, hidden entry points,
   surprising redirects, broken links, no clear "home".
+- **Flow completeness & expected counterparts:** a screen that gates access or shows one side of a
+  standard paired flow must offer the other side — or a clear path to it. A brand-new user must never
+  hit a dead end with no next step. Flag missing companion actions, especially on auth and entry
+  screens:
+  - **Sign-in with no sign-up:** a login page with no "Create account" / "Register" link strands
+    anyone who does not already have an account; likewise a registration page with no link back to
+    sign in.
+  - **No account recovery:** login with no "Forgot password?", no way to reset, and no way to resend a
+    verification email.
+  - **No exit from a state:** a signed-in app with no visible sign-out, or a modal / wizard / detail
+    view with no back, close, or cancel.
+  - **One-way actions:** create/add with no matching edit or delete (or the reverse) where a user
+    would reasonably expect both.
+  - **Unreachable entry points:** a feature only reachable by guessing a URL, or an empty state with
+    no primary action to populate it.
+  When the missing counterpart makes a core task impossible for a whole class of users (e.g. a new
+  user literally cannot create an account), file a `Bug`; otherwise file a usability `Improvement`.
 - **Visual/layout quality:** cut-off or truncated text, overlap, cramped/crowded density, offscreen or
-  unreachable controls, accidental horizontal scroll, awkward empty space.
+  unreachable controls, accidental horizontal scroll, awkward empty space. **Do not judge this by
+  eyeballing a screenshot alone** — a control clipped by a few pixels or pushed just past a container
+  edge looks fine in a thumbnail. Confirm it with the programmatic layout-integrity sweep in §5 at
+  every width.
 - **Consistency / standard UX:** components, spacing, button styles, terminology, and interaction
   patterns should be consistent across the app and follow common conventions. Flag anything
   non-standard or that differs screen-to-screen.
@@ -84,11 +104,39 @@ mistakes, and tries the obvious thing. Cover at least these dimensions unless th
 
 - Discover breakpoints from the app (design tokens, CSS, responsive layout changes) when possible; if
   unknown, use a practical baseline: phone, tablet/narrow, desktop, plus any app-specific cutoff.
-- At each breakpoint, walk the key paths again and confirm the experience holds: expected
+- **Do not test only the named breakpoints.** Clipping and overflow most often appear at the
+  *in-between* widths — where a row can no longer fit its contents but has not yet collapsed to the
+  next layout. Sweep a range of widths (e.g. 360, 390, 414, 600, 768, 834, 1024, 1280, 1440) plus a
+  few intermediate steps (e.g. ~900–1180) and re-check the key paths at each.
+- At each width, walk the key paths again and confirm the experience holds: expected
   shell/navigation variant, critical controls visible and reachable, no unintended horizontal
   overflow, intentional scroll containers still usable, nothing cut off or crowded.
 
-### 5. Watch Load & Latency
+### 5. Run Layout-Integrity Checks — Don't Eyeball Alone
+
+A screenshot glance misses controls clipped by a few pixels or pushed just past a container edge. At
+**every width**, in addition to looking, take DOM measurements via the browser automation tool
+(Playwright, Chrome MCP, etc.) and treat any of these as a finding:
+
+- **Document / container overflow:** `document.documentElement.scrollWidth > clientWidth`, or a
+  horizontal scrollbar on a container that should not scroll → accidental horizontal overflow.
+- **Clipped or offscreen controls:** for every interactive control (buttons, links, inputs, selects,
+  menu items), compare its `getBoundingClientRect()` against the viewport and against each ancestor
+  that has `overflow: hidden | clip | auto | scroll`. If any edge of the control falls outside those
+  bounds, it is partially or fully clipped / unreachable — even when the page looks fine in a thumbnail.
+  This is exactly the case that gets missed: a submit/apply button whose right edge is cut off by its
+  filter card.
+- **Truncated meaningful text:** an element whose `scrollWidth > clientWidth` (or that renders an
+  ellipsis) where the hidden text carries meaning — e.g. a select showing "Any CRD state" jammed into
+  its chevron, a label cut mid-word.
+- **Colliding controls:** a label or value overlapping an adjacent control (icon, chevron, button)
+  with no gap between them.
+
+Record which width(s) trigger each, the offending element, and a screenshot. **A primary or
+interactive control that is clipped, offscreen, or unreachable is a `Bug`, not merely an
+Improvement** — a user literally cannot see or click all of it.
+
+### 6. Watch Load & Latency
 
 - Measure separate milestones: visible app shell, `document.readyState`, first meaningful
   route-specific content, and visually stable/full route content.
@@ -122,6 +170,10 @@ validation gate; never call a vendor `*-write-*` skill directly). Map each findi
 | User-visible **bug** (broken behavior) | `Bug` | the `ready` flag (default `false`) |
 | **Usability / UX / clarity issue** | `Improvement` | the `ready` flag (default `false`) |
 
+A control that is **clipped, offscreen, or otherwise unreachable** (per §5) counts as broken behavior
+→ file it as a `Bug`, not an `Improvement`. Pure crowding/clarity with the control still fully usable
+is an `Improvement`.
+
 Each finding is a flat leaf (no children), so `build_ready` applies directly — pass it explicitly on
 every create. Each ticket MUST be a complete spec (the validator rejects thin tickets):
 

package/plugins/lisa-expo-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.134.10",
+  "version": "2.136.0",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo-agy/skills/exploratory-qa/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: exploratory-qa
-description: First-time-user exploratory QA walkthrough for web apps that FEEDS THE LIFECYCLE. Use when asked to experience an app the way a brand-new human user would — landing cold on the home page and clicking through to find anything confusing, broken, or hard to understand (human-facing jargon, contextless extracted data, machine-style labels, slow or unclear loads, late meaningful content, cramped or cut-off UI, inconsistent/non-standard UX, awkward scroll behavior, unclear affordances) across all breakpoints. Instead of writing a report file, it files every finding as a tracked work item via lisa:tracker-write (bugs and usability/UX issues). A `ready` parameter controls whether those tickets are created build-ready (auto-picked-up by lisa:intake) or left in the backlog for human triage (default). For gaps in the automated Playwright test suite, use the e2e-coverage-gaps skill instead.
+description: First-time-user exploratory QA walkthrough for web apps that FEEDS THE LIFECYCLE. Use when asked to experience an app the way a brand-new human user would — landing cold on the home page and clicking through to find anything confusing, broken, or hard to understand (human-facing jargon, contextless extracted data, machine-style labels, slow or unclear loads, late meaningful content, cramped or cut-off UI, inconsistent/non-standard UX, awkward scroll behavior, unclear affordances, dead-end flows that strand a user — e.g. a login page with no way to register or recover a password) across all breakpoints. Instead of writing a report file, it files every finding as a tracked work item via lisa:tracker-write (bugs and usability/UX issues). A `ready` parameter controls whether those tickets are created build-ready (auto-picked-up by lisa:intake) or left in the backlog for human triage (default). For gaps in the automated Playwright test suite, use the e2e-coverage-gaps skill instead.
 ---
 
 # Exploratory QA
@@ -63,8 +63,28 @@ mistakes, and tries the obvious thing. Cover at least these dimensions unless th
   from the default UI or add context such as excerpts, labels, grouping, or provenance.
 - **Navigation clarity:** is it obvious how to get somewhere and back? Dead ends, hidden entry points,
   surprising redirects, broken links, no clear "home".
+- **Flow completeness & expected counterparts:** a screen that gates access or shows one side of a
+  standard paired flow must offer the other side — or a clear path to it. A brand-new user must never
+  hit a dead end with no next step. Flag missing companion actions, especially on auth and entry
+  screens:
+  - **Sign-in with no sign-up:** a login page with no "Create account" / "Register" link strands
+    anyone who does not already have an account; likewise a registration page with no link back to
+    sign in.
+  - **No account recovery:** login with no "Forgot password?", no way to reset, and no way to resend a
+    verification email.
+  - **No exit from a state:** a signed-in app with no visible sign-out, or a modal / wizard / detail
+    view with no back, close, or cancel.
+  - **One-way actions:** create/add with no matching edit or delete (or the reverse) where a user
+    would reasonably expect both.
+  - **Unreachable entry points:** a feature only reachable by guessing a URL, or an empty state with
+    no primary action to populate it.
+  When the missing counterpart makes a core task impossible for a whole class of users (e.g. a new
+  user literally cannot create an account), file a `Bug`; otherwise file a usability `Improvement`.
 - **Visual/layout quality:** cut-off or truncated text, overlap, cramped/crowded density, offscreen or
-  unreachable controls, accidental horizontal scroll, awkward empty space.
+  unreachable controls, accidental horizontal scroll, awkward empty space. **Do not judge this by
+  eyeballing a screenshot alone** — a control clipped by a few pixels or pushed just past a container
+  edge looks fine in a thumbnail. Confirm it with the programmatic layout-integrity sweep in §5 at
+  every width.
 - **Consistency / standard UX:** components, spacing, button styles, terminology, and interaction
   patterns should be consistent across the app and follow common conventions. Flag anything
   non-standard or that differs screen-to-screen.
@@ -84,11 +104,39 @@ mistakes, and tries the obvious thing. Cover at least these dimensions unless th
 
 - Discover breakpoints from the app (design tokens, CSS, responsive layout changes) when possible; if
   unknown, use a practical baseline: phone, tablet/narrow, desktop, plus any app-specific cutoff.
-- At each breakpoint, walk the key paths again and confirm the experience holds: expected
+- **Do not test only the named breakpoints.** Clipping and overflow most often appear at the
+  *in-between* widths — where a row can no longer fit its contents but has not yet collapsed to the
+  next layout. Sweep a range of widths (e.g. 360, 390, 414, 600, 768, 834, 1024, 1280, 1440) plus a
+  few intermediate steps (e.g. ~900–1180) and re-check the key paths at each.
+- At each width, walk the key paths again and confirm the experience holds: expected
   shell/navigation variant, critical controls visible and reachable, no unintended horizontal
   overflow, intentional scroll containers still usable, nothing cut off or crowded.
 
-### 5. Watch Load & Latency
+### 5. Run Layout-Integrity Checks — Don't Eyeball Alone
+
+A screenshot glance misses controls clipped by a few pixels or pushed just past a container edge. At
+**every width**, in addition to looking, take DOM measurements via the browser automation tool
+(Playwright, Chrome MCP, etc.) and treat any of these as a finding:
+
+- **Document / container overflow:** `document.documentElement.scrollWidth > clientWidth`, or a
+  horizontal scrollbar on a container that should not scroll → accidental horizontal overflow.
+- **Clipped or offscreen controls:** for every interactive control (buttons, links, inputs, selects,
+  menu items), compare its `getBoundingClientRect()` against the viewport and against each ancestor
+  that has `overflow: hidden | clip | auto | scroll`. If any edge of the control falls outside those
+  bounds, it is partially or fully clipped / unreachable — even when the page looks fine in a thumbnail.
+  This is exactly the case that gets missed: a submit/apply button whose right edge is cut off by its
+  filter card.
+- **Truncated meaningful text:** an element whose `scrollWidth > clientWidth` (or that renders an
+  ellipsis) where the hidden text carries meaning — e.g. a select showing "Any CRD state" jammed into
+  its chevron, a label cut mid-word.
+- **Colliding controls:** a label or value overlapping an adjacent control (icon, chevron, button)
+  with no gap between them.
+
+Record which width(s) trigger each, the offending element, and a screenshot. **A primary or
+interactive control that is clipped, offscreen, or unreachable is a `Bug`, not merely an
+Improvement** — a user literally cannot see or click all of it.
+
+### 6. Watch Load & Latency
 
 - Measure separate milestones: visible app shell, `document.readyState`, first meaningful
   route-specific content, and visually stable/full route content.
@@ -122,6 +170,10 @@ validation gate; never call a vendor `*-write-*` skill directly). Map each findi
 | User-visible **bug** (broken behavior) | `Bug` | the `ready` flag (default `false`) |
 | **Usability / UX / clarity issue** | `Improvement` | the `ready` flag (default `false`) |
 
+A control that is **clipped, offscreen, or otherwise unreachable** (per §5) counts as broken behavior
+→ file it as a `Bug`, not an `Improvement`. Pure crowding/clarity with the control still fully usable
+is an `Improvement`.
+
 Each finding is a flat leaf (no children), so `build_ready` applies directly — pass it explicitly on
 every create. Each ticket MUST be a complete spec (the validator rejects thin tickets):
 

package/plugins/lisa-expo-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.134.10",
+  "version": "2.136.0",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo-copilot/skills/exploratory-qa/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: exploratory-qa
-description: First-time-user exploratory QA walkthrough for web apps that FEEDS THE LIFECYCLE. Use when asked to experience an app the way a brand-new human user would — landing cold on the home page and clicking through to find anything confusing, broken, or hard to understand (human-facing jargon, contextless extracted data, machine-style labels, slow or unclear loads, late meaningful content, cramped or cut-off UI, inconsistent/non-standard UX, awkward scroll behavior, unclear affordances) across all breakpoints. Instead of writing a report file, it files every finding as a tracked work item via lisa:tracker-write (bugs and usability/UX issues). A `ready` parameter controls whether those tickets are created build-ready (auto-picked-up by lisa:intake) or left in the backlog for human triage (default). For gaps in the automated Playwright test suite, use the e2e-coverage-gaps skill instead.
+description: First-time-user exploratory QA walkthrough for web apps that FEEDS THE LIFECYCLE. Use when asked to experience an app the way a brand-new human user would — landing cold on the home page and clicking through to find anything confusing, broken, or hard to understand (human-facing jargon, contextless extracted data, machine-style labels, slow or unclear loads, late meaningful content, cramped or cut-off UI, inconsistent/non-standard UX, awkward scroll behavior, unclear affordances, dead-end flows that strand a user — e.g. a login page with no way to register or recover a password) across all breakpoints. Instead of writing a report file, it files every finding as a tracked work item via lisa:tracker-write (bugs and usability/UX issues). A `ready` parameter controls whether those tickets are created build-ready (auto-picked-up by lisa:intake) or left in the backlog for human triage (default). For gaps in the automated Playwright test suite, use the e2e-coverage-gaps skill instead.
 ---
 
 # Exploratory QA
@@ -63,8 +63,28 @@ mistakes, and tries the obvious thing. Cover at least these dimensions unless th
   from the default UI or add context such as excerpts, labels, grouping, or provenance.
 - **Navigation clarity:** is it obvious how to get somewhere and back? Dead ends, hidden entry points,
   surprising redirects, broken links, no clear "home".
+- **Flow completeness & expected counterparts:** a screen that gates access or shows one side of a
+  standard paired flow must offer the other side — or a clear path to it. A brand-new user must never
+  hit a dead end with no next step. Flag missing companion actions, especially on auth and entry
+  screens:
+  - **Sign-in with no sign-up:** a login page with no "Create account" / "Register" link strands
+    anyone who does not already have an account; likewise a registration page with no link back to
+    sign in.
+  - **No account recovery:** login with no "Forgot password?", no way to reset, and no way to resend a
+    verification email.
+  - **No exit from a state:** a signed-in app with no visible sign-out, or a modal / wizard / detail
+    view with no back, close, or cancel.
+  - **One-way actions:** create/add with no matching edit or delete (or the reverse) where a user
+    would reasonably expect both.
+  - **Unreachable entry points:** a feature only reachable by guessing a URL, or an empty state with
+    no primary action to populate it.
+  When the missing counterpart makes a core task impossible for a whole class of users (e.g. a new
+  user literally cannot create an account), file a `Bug`; otherwise file a usability `Improvement`.
 - **Visual/layout quality:** cut-off or truncated text, overlap, cramped/crowded density, offscreen or
-  unreachable controls, accidental horizontal scroll, awkward empty space.
+  unreachable controls, accidental horizontal scroll, awkward empty space. **Do not judge this by
+  eyeballing a screenshot alone** — a control clipped by a few pixels or pushed just past a container
+  edge looks fine in a thumbnail. Confirm it with the programmatic layout-integrity sweep in §5 at
+  every width.
 - **Consistency / standard UX:** components, spacing, button styles, terminology, and interaction
   patterns should be consistent across the app and follow common conventions. Flag anything
   non-standard or that differs screen-to-screen.
@@ -84,11 +104,39 @@ mistakes, and tries the obvious thing. Cover at least these dimensions unless th
 
 - Discover breakpoints from the app (design tokens, CSS, responsive layout changes) when possible; if
   unknown, use a practical baseline: phone, tablet/narrow, desktop, plus any app-specific cutoff.
-- At each breakpoint, walk the key paths again and confirm the experience holds: expected
+- **Do not test only the named breakpoints.** Clipping and overflow most often appear at the
+  *in-between* widths — where a row can no longer fit its contents but has not yet collapsed to the
+  next layout. Sweep a range of widths (e.g. 360, 390, 414, 600, 768, 834, 1024, 1280, 1440) plus a
+  few intermediate steps (e.g. ~900–1180) and re-check the key paths at each.
+- At each width, walk the key paths again and confirm the experience holds: expected
   shell/navigation variant, critical controls visible and reachable, no unintended horizontal
   overflow, intentional scroll containers still usable, nothing cut off or crowded.
 
-### 5. Watch Load & Latency
+### 5. Run Layout-Integrity Checks — Don't Eyeball Alone
+
+A screenshot glance misses controls clipped by a few pixels or pushed just past a container edge. At
+**every width**, in addition to looking, take DOM measurements via the browser automation tool
+(Playwright, Chrome MCP, etc.) and treat any of these as a finding:
+
+- **Document / container overflow:** `document.documentElement.scrollWidth > clientWidth`, or a
+  horizontal scrollbar on a container that should not scroll → accidental horizontal overflow.
+- **Clipped or offscreen controls:** for every interactive control (buttons, links, inputs, selects,
+  menu items), compare its `getBoundingClientRect()` against the viewport and against each ancestor
+  that has `overflow: hidden | clip | auto | scroll`. If any edge of the control falls outside those
+  bounds, it is partially or fully clipped / unreachable — even when the page looks fine in a thumbnail.
+  This is exactly the case that gets missed: a submit/apply button whose right edge is cut off by its
+  filter card.
+- **Truncated meaningful text:** an element whose `scrollWidth > clientWidth` (or that renders an
+  ellipsis) where the hidden text carries meaning — e.g. a select showing "Any CRD state" jammed into
+  its chevron, a label cut mid-word.
+- **Colliding controls:** a label or value overlapping an adjacent control (icon, chevron, button)
+  with no gap between them.
+
+Record which width(s) trigger each, the offending element, and a screenshot. **A primary or
+interactive control that is clipped, offscreen, or unreachable is a `Bug`, not merely an
+Improvement** — a user literally cannot see or click all of it.
+
+### 6. Watch Load & Latency
 
 - Measure separate milestones: visible app shell, `document.readyState`, first meaningful
   route-specific content, and visually stable/full route content.
@@ -122,6 +170,10 @@ validation gate; never call a vendor `*-write-*` skill directly). Map each findi
 | User-visible **bug** (broken behavior) | `Bug` | the `ready` flag (default `false`) |
 | **Usability / UX / clarity issue** | `Improvement` | the `ready` flag (default `false`) |
 
+A control that is **clipped, offscreen, or otherwise unreachable** (per §5) counts as broken behavior
+→ file it as a `Bug`, not an `Improvement`. Pure crowding/clarity with the control still fully usable
+is an `Improvement`.
+
 Each finding is a flat leaf (no children), so `build_ready` applies directly — pass it explicitly on
 every create. Each ticket MUST be a complete spec (the validator rejects thin tickets):
 

package/plugins/lisa-expo-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.134.10",
+  "version": "2.136.0",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo-cursor/skills/exploratory-qa/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: exploratory-qa
-description: First-time-user exploratory QA walkthrough for web apps that FEEDS THE LIFECYCLE. Use when asked to experience an app the way a brand-new human user would — landing cold on the home page and clicking through to find anything confusing, broken, or hard to understand (human-facing jargon, contextless extracted data, machine-style labels, slow or unclear loads, late meaningful content, cramped or cut-off UI, inconsistent/non-standard UX, awkward scroll behavior, unclear affordances) across all breakpoints. Instead of writing a report file, it files every finding as a tracked work item via lisa:tracker-write (bugs and usability/UX issues). A `ready` parameter controls whether those tickets are created build-ready (auto-picked-up by lisa:intake) or left in the backlog for human triage (default). For gaps in the automated Playwright test suite, use the e2e-coverage-gaps skill instead.
+description: First-time-user exploratory QA walkthrough for web apps that FEEDS THE LIFECYCLE. Use when asked to experience an app the way a brand-new human user would — landing cold on the home page and clicking through to find anything confusing, broken, or hard to understand (human-facing jargon, contextless extracted data, machine-style labels, slow or unclear loads, late meaningful content, cramped or cut-off UI, inconsistent/non-standard UX, awkward scroll behavior, unclear affordances, dead-end flows that strand a user — e.g. a login page with no way to register or recover a password) across all breakpoints. Instead of writing a report file, it files every finding as a tracked work item via lisa:tracker-write (bugs and usability/UX issues). A `ready` parameter controls whether those tickets are created build-ready (auto-picked-up by lisa:intake) or left in the backlog for human triage (default). For gaps in the automated Playwright test suite, use the e2e-coverage-gaps skill instead.
 ---
 
 # Exploratory QA
@@ -63,8 +63,28 @@ mistakes, and tries the obvious thing. Cover at least these dimensions unless th
   from the default UI or add context such as excerpts, labels, grouping, or provenance.
 - **Navigation clarity:** is it obvious how to get somewhere and back? Dead ends, hidden entry points,
   surprising redirects, broken links, no clear "home".
+- **Flow completeness & expected counterparts:** a screen that gates access or shows one side of a
+  standard paired flow must offer the other side — or a clear path to it. A brand-new user must never
+  hit a dead end with no next step. Flag missing companion actions, especially on auth and entry
+  screens:
+  - **Sign-in with no sign-up:** a login page with no "Create account" / "Register" link strands
+    anyone who does not already have an account; likewise a registration page with no link back to
+    sign in.
+  - **No account recovery:** login with no "Forgot password?", no way to reset, and no way to resend a
+    verification email.
+  - **No exit from a state:** a signed-in app with no visible sign-out, or a modal / wizard / detail
+    view with no back, close, or cancel.
+  - **One-way actions:** create/add with no matching edit or delete (or the reverse) where a user
+    would reasonably expect both.
+  - **Unreachable entry points:** a feature only reachable by guessing a URL, or an empty state with
+    no primary action to populate it.
+  When the missing counterpart makes a core task impossible for a whole class of users (e.g. a new
+  user literally cannot create an account), file a `Bug`; otherwise file a usability `Improvement`.
 - **Visual/layout quality:** cut-off or truncated text, overlap, cramped/crowded density, offscreen or
-  unreachable controls, accidental horizontal scroll, awkward empty space.
+  unreachable controls, accidental horizontal scroll, awkward empty space. **Do not judge this by
+  eyeballing a screenshot alone** — a control clipped by a few pixels or pushed just past a container
+  edge looks fine in a thumbnail. Confirm it with the programmatic layout-integrity sweep in §5 at
+  every width.
 - **Consistency / standard UX:** components, spacing, button styles, terminology, and interaction
   patterns should be consistent across the app and follow common conventions. Flag anything
   non-standard or that differs screen-to-screen.
@@ -84,11 +104,39 @@ mistakes, and tries the obvious thing. Cover at least these dimensions unless th
 
 - Discover breakpoints from the app (design tokens, CSS, responsive layout changes) when possible; if
   unknown, use a practical baseline: phone, tablet/narrow, desktop, plus any app-specific cutoff.
-- At each breakpoint, walk the key paths again and confirm the experience holds: expected
+- **Do not test only the named breakpoints.** Clipping and overflow most often appear at the
+  *in-between* widths — where a row can no longer fit its contents but has not yet collapsed to the
+  next layout. Sweep a range of widths (e.g. 360, 390, 414, 600, 768, 834, 1024, 1280, 1440) plus a
+  few intermediate steps (e.g. ~900–1180) and re-check the key paths at each.
+- At each width, walk the key paths again and confirm the experience holds: expected
   shell/navigation variant, critical controls visible and reachable, no unintended horizontal
   overflow, intentional scroll containers still usable, nothing cut off or crowded.
 
-### 5. Watch Load & Latency
+### 5. Run Layout-Integrity Checks — Don't Eyeball Alone
+
+A screenshot glance misses controls clipped by a few pixels or pushed just past a container edge. At
+**every width**, in addition to looking, take DOM measurements via the browser automation tool
+(Playwright, Chrome MCP, etc.) and treat any of these as a finding:
+
+- **Document / container overflow:** `document.documentElement.scrollWidth > clientWidth`, or a
+  horizontal scrollbar on a container that should not scroll → accidental horizontal overflow.
+- **Clipped or offscreen controls:** for every interactive control (buttons, links, inputs, selects,
+  menu items), compare its `getBoundingClientRect()` against the viewport and against each ancestor
+  that has `overflow: hidden | clip | auto | scroll`. If any edge of the control falls outside those
+  bounds, it is partially or fully clipped / unreachable — even when the page looks fine in a thumbnail.
+  This is exactly the case that gets missed: a submit/apply button whose right edge is cut off by its
+  filter card.
+- **Truncated meaningful text:** an element whose `scrollWidth > clientWidth` (or that renders an
+  ellipsis) where the hidden text carries meaning — e.g. a select showing "Any CRD state" jammed into
+  its chevron, a label cut mid-word.
+- **Colliding controls:** a label or value overlapping an adjacent control (icon, chevron, button)
+  with no gap between them.
+
+Record which width(s) trigger each, the offending element, and a screenshot. **A primary or
+interactive control that is clipped, offscreen, or unreachable is a `Bug`, not merely an
+Improvement** — a user literally cannot see or click all of it.
+
+### 6. Watch Load & Latency
 
 - Measure separate milestones: visible app shell, `document.readyState`, first meaningful
   route-specific content, and visually stable/full route content.
@@ -122,6 +170,10 @@ validation gate; never call a vendor `*-write-*` skill directly). Map each findi
 | User-visible **bug** (broken behavior) | `Bug` | the `ready` flag (default `false`) |
 | **Usability / UX / clarity issue** | `Improvement` | the `ready` flag (default `false`) |
 
+A control that is **clipped, offscreen, or otherwise unreachable** (per §5) counts as broken behavior
+→ file it as a `Bug`, not an `Improvement`. Pure crowding/clarity with the control still fully usable
+is an `Improvement`.
+
 Each finding is a flat leaf (no children), so `build_ready` applies directly — pass it explicitly on
 every create. Each ticket MUST be a complete spec (the validator rejects thin tickets):
 

package/plugins/lisa-harper-fabric/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.134.10",
+  "version": "2.136.0",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.134.10",
+  "version": "2.136.0",
   "description": "Harper/Fabric-specific Lisa rules for TypeScript component apps.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric/skills/exploratory-qa/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: exploratory-qa
-description: First-time-user exploratory QA walkthrough for web apps that FEEDS THE LIFECYCLE. Use when asked to experience an app the way a brand-new human user would — landing cold on the home page and clicking through to find anything confusing, broken, or hard to understand (human-facing jargon, contextless extracted data, machine-style labels, slow or unclear loads, late meaningful content, cramped or cut-off UI, inconsistent/non-standard UX, awkward scroll behavior, unclear affordances) across all breakpoints. Instead of writing a report file, it files every finding as a tracked work item via lisa:tracker-write (bugs and usability/UX issues). A `ready` parameter controls whether those tickets are created build-ready (auto-picked-up by lisa:intake) or left in the backlog for human triage (default). For gaps in the automated Playwright test suite, use the e2e-coverage-gaps skill instead.
+description: First-time-user exploratory QA walkthrough for web apps that FEEDS THE LIFECYCLE. Use when asked to experience an app the way a brand-new human user would — landing cold on the home page and clicking through to find anything confusing, broken, or hard to understand (human-facing jargon, contextless extracted data, machine-style labels, slow or unclear loads, late meaningful content, cramped or cut-off UI, inconsistent/non-standard UX, awkward scroll behavior, unclear affordances, dead-end flows that strand a user — e.g. a login page with no way to register or recover a password) across all breakpoints. Instead of writing a report file, it files every finding as a tracked work item via lisa:tracker-write (bugs and usability/UX issues). A `ready` parameter controls whether those tickets are created build-ready (auto-picked-up by lisa:intake) or left in the backlog for human triage (default). For gaps in the automated Playwright test suite, use the e2e-coverage-gaps skill instead.
 ---
 
 # Exploratory QA
@@ -63,6 +63,23 @@ mistakes, and tries the obvious thing. Cover at least these dimensions unless th
   from the default UI or add context such as excerpts, labels, grouping, or provenance.
 - **Navigation clarity:** is it obvious how to get somewhere and back? Dead ends, hidden entry points,
   surprising redirects, broken links, no clear "home".
+- **Flow completeness & expected counterparts:** a screen that gates access or shows one side of a
+  standard paired flow must offer the other side — or a clear path to it. A brand-new user must never
+  hit a dead end with no next step. Flag missing companion actions, especially on auth and entry
+  screens:
+  - **Sign-in with no sign-up:** a login page with no "Create account" / "Register" link strands
+    anyone who does not already have an account; likewise a registration page with no link back to
+    sign in.
+  - **No account recovery:** login with no "Forgot password?", no way to reset, and no way to resend a
+    verification email.
+  - **No exit from a state:** a signed-in app with no visible sign-out, or a modal / wizard / detail
+    view with no back, close, or cancel.
+  - **One-way actions:** create/add with no matching edit or delete (or the reverse) where a user
+    would reasonably expect both.
+  - **Unreachable entry points:** a feature only reachable by guessing a URL, or an empty state with
+    no primary action to populate it.
+  When the missing counterpart makes a core task impossible for a whole class of users (e.g. a new
+  user literally cannot create an account), file a `Bug`; otherwise file a usability `Improvement`.
 - **Visual/layout quality:** cut-off or truncated text, overlap, cramped/crowded density, offscreen or
   unreachable controls, accidental horizontal scroll, awkward empty space. **Do not judge this by
   eyeballing a screenshot alone** — a control clipped by a few pixels or pushed just past a container

package/plugins/lisa-harper-fabric-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.134.10",
+  "version": "2.136.0",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric-agy/skills/exploratory-qa/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: exploratory-qa
-description: First-time-user exploratory QA walkthrough for web apps that FEEDS THE LIFECYCLE. Use when asked to experience an app the way a brand-new human user would — landing cold on the home page and clicking through to find anything confusing, broken, or hard to understand (human-facing jargon, contextless extracted data, machine-style labels, slow or unclear loads, late meaningful content, cramped or cut-off UI, inconsistent/non-standard UX, awkward scroll behavior, unclear affordances) across all breakpoints. Instead of writing a report file, it files every finding as a tracked work item via lisa:tracker-write (bugs and usability/UX issues). A `ready` parameter controls whether those tickets are created build-ready (auto-picked-up by lisa:intake) or left in the backlog for human triage (default). For gaps in the automated Playwright test suite, use the e2e-coverage-gaps skill instead.
+description: First-time-user exploratory QA walkthrough for web apps that FEEDS THE LIFECYCLE. Use when asked to experience an app the way a brand-new human user would — landing cold on the home page and clicking through to find anything confusing, broken, or hard to understand (human-facing jargon, contextless extracted data, machine-style labels, slow or unclear loads, late meaningful content, cramped or cut-off UI, inconsistent/non-standard UX, awkward scroll behavior, unclear affordances, dead-end flows that strand a user — e.g. a login page with no way to register or recover a password) across all breakpoints. Instead of writing a report file, it files every finding as a tracked work item via lisa:tracker-write (bugs and usability/UX issues). A `ready` parameter controls whether those tickets are created build-ready (auto-picked-up by lisa:intake) or left in the backlog for human triage (default). For gaps in the automated Playwright test suite, use the e2e-coverage-gaps skill instead.
 ---
 
 # Exploratory QA
@@ -63,6 +63,23 @@ mistakes, and tries the obvious thing. Cover at least these dimensions unless th
   from the default UI or add context such as excerpts, labels, grouping, or provenance.
 - **Navigation clarity:** is it obvious how to get somewhere and back? Dead ends, hidden entry points,
   surprising redirects, broken links, no clear "home".
+- **Flow completeness & expected counterparts:** a screen that gates access or shows one side of a
+  standard paired flow must offer the other side — or a clear path to it. A brand-new user must never
+  hit a dead end with no next step. Flag missing companion actions, especially on auth and entry
+  screens:
+  - **Sign-in with no sign-up:** a login page with no "Create account" / "Register" link strands
+    anyone who does not already have an account; likewise a registration page with no link back to
+    sign in.
+  - **No account recovery:** login with no "Forgot password?", no way to reset, and no way to resend a
+    verification email.
+  - **No exit from a state:** a signed-in app with no visible sign-out, or a modal / wizard / detail
+    view with no back, close, or cancel.
+  - **One-way actions:** create/add with no matching edit or delete (or the reverse) where a user
+    would reasonably expect both.
+  - **Unreachable entry points:** a feature only reachable by guessing a URL, or an empty state with
+    no primary action to populate it.
+  When the missing counterpart makes a core task impossible for a whole class of users (e.g. a new
+  user literally cannot create an account), file a `Bug`; otherwise file a usability `Improvement`.
 - **Visual/layout quality:** cut-off or truncated text, overlap, cramped/crowded density, offscreen or
   unreachable controls, accidental horizontal scroll, awkward empty space. **Do not judge this by
   eyeballing a screenshot alone** — a control clipped by a few pixels or pushed just past a container