@codyswann/lisa 4.64.1 → 4.64.3

package/plugins/lisa-copilot/skills/lisa-review-local/SKILL.md

@@ -18,14 +18,20 @@ One deterministic gate runs ahead of the judgement-based review and is exempt
 from the confidence filtering below, because it is decided by a script rather
 than by an agent's opinion.
 
-**Design-source gate (`design-source-of-truth` rule).** Run it against the
-branch diff before step 1:
+**Design-source gate (`design-source-of-truth` rule).** First read
+`designSource.enabled` in `.lisa.config.json`. Only boolean `false` opts out:
+omit the design-source review step; do not request DESIGN-SOURCE markers, Figma
+nodes, or Figma access for this obligation. Record `SKIPPED: designSource.enabled=false`
+in the review. Absent, true, or invalid values keep enforcement enabled.
+The separate design-value binding review below still applies.
+
+When enabled, run the gate against the branch diff before step 1:
 
 ```bash
 node "${CLAUDE_PLUGIN_ROOT:-.}/scripts/design-source-gate.mjs" --base=main --head=HEAD
 ```
 
-Exit 0 = PASS, exit 1 = FAIL. A FAIL is a **blocking** review finding and is
+Exit 0 = PASS or explicit SKIPPED, exit 1 = FAIL. A FAIL is a **blocking** review finding and is
 reported verbatim at the top of the review — it is never scored, never filtered
 by confidence, and never demoted to a nitpick. It qualifies under
 `convergent-review` because it names a concrete failure scenario: the design

package/plugins/lisa-copilot/skills/lisa-tdd-implementation/SKILL.md

@@ -72,7 +72,8 @@ TDD Cycle:
 
 - Write the minimum production code to make the test pass
 - Do not optimize, do not add features beyond what the test requires
-- For any UI surface the implementation adds or changes, the `design-source-of-truth` rule requires its design-source declaration to land in the same commit as the surface it describes — `DESIGN-SOURCE: <figma-url>` when the surface is backed by a Figma node (sync it back first if Figma access exists), or the exception marker `DESIGN-SOURCE: none — not in Figma` when it genuinely is not captured at the source. `scripts/design-source-gate.mjs` fails closed on an undeclared surface. Cite the rule; do not restate its marker grammar here.
+- Read `designSource.enabled` in `.lisa.config.json` before preparing design-source instructions. Only boolean `false` opts out: omit the design-source step and do not request DESIGN-SOURCE markers, Figma nodes, or Figma access for this obligation. Absent, true, or invalid values keep enforcement enabled.
+- When enabled, for any UI surface the implementation adds or changes, the `design-source-of-truth` rule requires its design-source declaration to land in the same commit as the surface it describes — `DESIGN-SOURCE: <figma-url>` when the surface is backed by a Figma node (sync it back first if Figma access exists), or the exception marker `DESIGN-SOURCE: none — not in Figma` when it genuinely is not captured at the source. `scripts/design-source-gate.mjs` fails closed on an undeclared surface. Cite the rule; do not restate its marker grammar here.
 - Separately, the `design-value-binding` rule governs where each *value* on that surface came from: in an axis with a published variable collection, bind the variable and use a screenshot only to verify; in an axis with none, measure and record what you derived. A literal in a typed axis is a block, not a TODO. Cite the rule; do not restate its conditions here.
 - The goal is the simplest code that makes the test green
 

package/plugins/lisa-copilot/skills/lisa-tracker-source-artifacts/SKILL.md

@@ -93,7 +93,9 @@ Mocks define visual *intent*, not implementation shortcut. Every UI-touching tic
 
 If no existing component fits, building a new one is an explicit decision that must be recorded in the ticket (with rationale) before implementation. Lovable-generated components are never the reuse target — always use the project's own components.
 
-The divergence note above covers the **ticket** side of this event. The **code** side is governed by the `design-source-of-truth` rule: a UI surface built with no Figma source behind it is either synced back to Figma and annotated `DESIGN-SOURCE: <figma-url>`, or explicitly marked `DESIGN-SOURCE: none — not in Figma`, and review fails closed if neither happened. Cite the rule for the code obligation rather than restating it here — a ticket comment closes with the ticket, the annotation stays with the surface.
+Before adding the code-side obligation to ticket or teammate instructions, read `designSource.enabled` in `.lisa.config.json`. Only boolean `false` opts out: omit the design-source step; do not request DESIGN-SOURCE markers, Figma nodes, or Figma access for this obligation. Absent, true, or invalid values keep enforcement enabled. Preserve supplied artifacts and component-reuse requirements regardless; `design-value-binding` remains independent.
+
+When enabled, the divergence note above covers the **ticket** side of this event. The **code** side is governed by the `design-source-of-truth` rule: a UI surface built with no Figma source behind it is either synced back to Figma and annotated `DESIGN-SOURCE: <figma-url>`, or explicitly marked `DESIGN-SOURCE: none — not in Figma`, and review fails closed if neither happened. Cite the rule for the code obligation rather than restating it here — a ticket comment closes with the ticket, the annotation stays with the surface.
 
 ## 8. Preservation gate (run after creating tickets)
 

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

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

package/plugins/lisa-cursor/hooks/threshold-ratchet-compare.mjs

@@ -18,6 +18,7 @@ import {
   extractStrykerConstraints,
   extractStrykerMutate,
   familyFor,
+  globRoot,
   parseJson,
 } from "./threshold-ratchet-families.mjs";
 
@@ -154,15 +155,56 @@ function compareStryker(relPath, base, current) {
   );
   const baseMutate = extractStrykerMutate(base);
   const currentMutate = extractStrykerMutate(current);
+  // Roots the gate already covered, and roots this change adds. An exclusion
+  // scoped to a newly added root narrows territory that was not being mutated
+  // a moment ago, so it cannot shrink the gate — the change is a net widening.
+  //
+  // Without this, repairing an INERT `mutate` list is unreachable without a
+  // human-approved ratchet exception: the repair necessarily adds source roots
+  // AND the test-file exclusions that belong with them, and every one of those
+  // exclusions read as a weakening. Measured on two repositories whose real
+  // effect was 0 -> 69 and 0 -> 75 files mutated (CodySwannGT/lisa#4243).
+  const baseRoots = [...baseMutate.positives].map(globRoot);
+  /**
+   * Whether an exclusion might touch any baseline positive.
+   *
+   * Both containment directions matter: excluding `src` removes a baseline
+   * rooted at `src/existing`, too. An empty prefix (wildcards, braces, classes
+   * or extglobs at the root) might cover everything. We grant an exemption
+   * only for provably disjoint territory, never from a guessed glob overlap.
+   * @param {string} root A rooted glob prefix
+   * @returns {boolean} True when overlap cannot be ruled out
+   */
+  const overlapsBase = root =>
+    baseRoots.some(
+      base =>
+        root === "" ||
+        base === "" ||
+        root === base ||
+        root.startsWith(`${base}/`) ||
+        base.startsWith(`${root}/`)
+    );
+  const addedRoots = [...currentMutate.positives]
+    .filter(positive => !baseMutate.positives.has(positive))
+    .map(globRoot)
+    .filter(root => root !== "");
+  /**
+   * Whether a root lies inside territory THIS change is adding.
+   * @param {string} root A rooted glob prefix
+   * @returns {boolean} True when an added root equals or contains it
+   */
+  const underAdded = root =>
+    addedRoots.some(added => root === added || root.startsWith(`${added}/`));
   for (const negation of currentMutate.negations) {
-    if (!baseMutate.negations.has(negation)) {
-      findings.push({
-        file: relPath,
-        key: `mutate ${negation}`,
-        type: TYPE_EXEMPTION_ADDED,
-        message: `${relPath}: new mutation-testing exclusion "${negation}" — excluding files from a gate is a weakening.`,
-      });
-    }
+    if (baseMutate.negations.has(negation)) continue;
+    const root = globRoot(negation);
+    if (!overlapsBase(root) && underAdded(root)) continue;
+    findings.push({
+      file: relPath,
+      key: `mutate ${negation}`,
+      type: TYPE_EXEMPTION_ADDED,
+      message: `${relPath}: new mutation-testing exclusion "${negation}" — excluding files from a gate is a weakening.`,
+    });
   }
   for (const positive of baseMutate.positives) {
     if (!currentMutate.positives.has(positive)) {

package/plugins/lisa-cursor/hooks/threshold-ratchet-families.mjs

@@ -308,6 +308,30 @@ export function extractStrykerMutate(conf) {
   return { positives, negations };
 }
 
+/**
+ * The literal directory prefix a glob is rooted at, before any wildcard.
+ *
+ * `lib/**\/*.spec.ts` and `!lib/**\/*.d.ts` are both rooted at `lib`. This is
+ * what lets the ratchet tell territory a change ADDED from territory it
+ * already covered: an exclusion inside a newly added root cannot shrink a
+ * gate, because nothing there was being mutated a moment ago.
+ * @param {string} glob A stryker mutate entry, with or without a leading `!`
+ * @returns {string} The rooted prefix, or "" when the glob starts with a wildcard
+ */
+export function globRoot(glob) {
+  const bare = glob.startsWith("!") ? glob.slice(1) : glob;
+  // Backslash escapes and parent traversal make textual containment unsafe.
+  // An unknown prefix overlaps everything rather than granting an exemption.
+  if (bare.includes("\\") || bare.split("/").includes("..")) return "";
+  const rooted = [];
+  for (const segment of bare.split("/")) {
+    if (segment === "." || segment === "") continue;
+    if (["*", "?", "{", "[", "("].some(meta => segment.includes(meta))) break;
+    rooted.push(segment);
+  }
+  return rooted.join("/");
+}
+
 /**
  * Parse one k6 threshold expression (`p(95)<1000`, `rate>=0.99`, …) into a
  * ratchet constraint. Upper bounds (`<`, `<=`) may only decrease; lower

package/plugins/lisa-cursor/rules/design-source-of-truth-reference.mdc

@@ -6,18 +6,41 @@ alwaysApply: false
 # Design Source of Truth
 
 > Demoted from the always-on eager tier by CodySwannGT/lisa#3992. The
-> section below is the former eager head, preserved verbatim; the full
+> section below is the former eager head, maintained with the full
 > contract follows it. Reachable on demand via [the rule index](00-rule-index.mdc).
 
 ## Design Source of Truth (load-bearing)
 
-**Figma is the design source of truth, and every UI surface a change touches declares where its design came from.** A changed UI surface that neither cites a Figma node nor carries the designated marker is a contract violation — and so is a surface whose declaration the gate cannot resolve.
+**When enabled, Figma is the design source of truth, and every UI surface a change touches declares where its design came from.** A changed UI surface that neither cites a Figma node nor carries the designated marker is a contract violation — and so is a surface whose declaration the gate cannot resolve.
 
 **One vendor-neutral contract, cited by** `lisa-implement`, `lisa-tdd-implementation`, `lisa-review-local`, `lisa-quality-review`, and `lisa-tracker-source-artifacts` (the `leaf-only-lifecycle` / `repo-scope-split` precedent: one shared slug, never divergent per-skill prose).
 
+## Explicit project opt-out
+
+A project with **no design source at all** may set this in `.lisa.config.json`:
+
+```json
+{ "designSource": { "enabled": false } }
+```
+
+Only `designSource.enabled` set to boolean `false` opts out. Absent, true, and
+invalid values retain the default enforcement. The explicit configuration is
+the auditable record; it replaces per-file exception markers for this project.
+The gate exits 0 with `SKIPPED: designSource.enabled=false` before resolving the
+diff. JSON output reports `verdict: "SKIPPED"`, the config key in `reasons`, and
+zero judged surfaces. A skip does not claim that surfaces passed inspection.
+
+When opted out, the five consuming skills omit the design-source step from
+plans, tickets, teammate instructions, and review; they do not ask for markers,
+Figma nodes, or Figma access for this obligation. All declaration, sync-back,
+and fail-closed requirements below apply only when enabled. Host design-system
+rules, `design-value-binding`, and `bdd-e2e-coverage` remain independent and
+unchanged. A project that has Figma must still not use `exclude` to hide its UI
+tree from this contract.
+
 ## Membership
 
-Membership is **surface, not repo name or file extension**: a file is in scope the moment a change makes it render something user-observable — a screen, component, layout, style token, visual state, or markup a user reads. Barrels, pure-logic modules, tests, stories, generated output, and vendored code are out. Projects narrow or widen the default detection through `designSource.include` / `designSource.exclude` in `.lisa.config.json`; they never turn the obligation off.
+Membership is **surface, not repo name or file extension**: a file is in scope the moment a change makes it render something user-observable — a screen, component, layout, style token, visual state, or markup a user reads. Barrels, pure-logic modules, tests, stories, generated output, and vendored code are out. Projects narrow or widen the default detection through `designSource.include` / `designSource.exclude` in `.lisa.config.json`; those filters never turn the obligation off. Only the explicit project opt-out above does.
 
 ## The two declarations
 
@@ -44,7 +67,7 @@ Projects that carry their own design-system rules (`figma-design-system`, `desig
 
 ## Bootstrap and degradation
 
-Adoption never demands a retroactive backfill: the gate judges **only the surfaces this change touched**. Pre-existing unannotated UI is burndown, recorded and worked down, not this work item's blocker. If a project has no Figma at all, that is not an exemption — every changed surface carries the marker, and the resulting exception list is the honest record of how much of the product lives outside its design source. Behavior obligations for the same surfaces are unchanged and still governed by `bdd-e2e-coverage`.
+Adoption never demands a retroactive backfill: the gate judges **only the surfaces this change touched**. Pre-existing unannotated UI is burndown, recorded and worked down, not this work item's blocker. A project with no design source may use the explicit project opt-out above; otherwise every changed surface still needs a declaration. Behavior obligations for the same surfaces are unchanged and still governed by `bdd-e2e-coverage`.
 
 ---
 
@@ -193,7 +216,7 @@ Two consequences worth stating plainly:
 node design-source-gate.mjs --base=origin/main [--head=HEAD] [--figma-access] [--json]
 ```
 
-Exit `0` = PASS, `1` = FAIL, `2` = usage error. It classifies every changed file into one status:
+Exit `0` = PASS or explicit SKIPPED, `1` = FAIL, `2` = usage error. When enabled, it classifies every changed file into one status:
 
 | Status | Verdict | Meaning |
 |---|---|---|
@@ -236,8 +259,7 @@ so a repository with hundreds of unannotated legacy components can adopt the con
 and be green on Tuesday. Pre-existing unannotated UI is **burndown**: recorded, worked down
 opportunistically as files are touched, never treated as the current work item's blocker.
 
-A project with no Figma at all is not exempt. Every changed surface carries the marker, and the
-resulting exception list is the honest, mounting record of how much of the product lives outside its
-design source — which is far more useful than an exemption flag that makes the question disappear.
-Deleting or excluding a surface to make the gate green is a violation of the same kind as deleting a
-BDD scenario to improve coverage: mark it, do not drop it.
+A project with no design source may opt out explicitly using `designSource.enabled: false`.
+Without that explicit opt-out, every changed surface still declares its source. In an enabled
+project, deleting or excluding a surface to make the gate green is a violation of the same kind as
+deleting a BDD scenario to improve coverage: mark it, do not drop it.

package/plugins/lisa-cursor/scripts/design-source-gate.mjs

@@ -19,7 +19,11 @@
  * at the source; it is the exception, not the default, and the gate reports
  * every one of them so review can challenge it.
  *
- * **The gate fails closed.** Anything it cannot resolve into one of those two
+ * Projects with no design source may explicitly set `designSource.enabled`
+ * to boolean false. The gate reports SKIPPED before resolving the diff; all
+ * other values retain the default enforcement.
+ *
+ * **When enabled, the gate fails closed.** Anything it cannot resolve into one of those two
  * declarations is a violation: no annotation, a malformed one, a file that both
  * cites Figma and denies having a source, a changed file it could not read, or
  * a diff it could not compute. A gate that returns PASS when it could not look
@@ -32,7 +36,7 @@
  * to all of it — it asks only whether the design source is declared.
  *
  * Run it: `node design-source-gate.mjs --base=origin/main [--head=HEAD] [--json]`
- * Exit 0 = PASS, 1 = FAIL (any violation, or anything unresolvable), 2 = usage.
+ * Exit 0 = PASS or SKIPPED, 1 = FAIL (any violation, or anything unresolvable), 2 = usage.
  */
 import { execFileSync } from "node:child_process";
 import { readFileSync, realpathSync } from "node:fs";
@@ -338,10 +342,10 @@ export const VIOLATION_STATUSES = new Set([
  *   files?: readonly { path: string, changeType?: string, content?: string | null }[] | null,
  *   diffError?: string | null,
  *   figmaAccess?: boolean,
- *   config?: { include?: readonly string[], exclude?: readonly string[] }
+ *   config?: { enabled?: unknown, include?: readonly string[], exclude?: readonly string[] }
  * }} input Change under evaluation.
  * @returns {{
- *   verdict: "PASS" | "FAIL",
+ *   verdict: "PASS" | "FAIL" | "SKIPPED",
  *   reasons: string[],
  *   violations: object[],
  *   exceptions: object[],
@@ -352,6 +356,21 @@ export const VIOLATION_STATUSES = new Set([
  * }} The gate result.
  */
 export function evaluateDesignSource(input = {}) {
+  // Only the explicit boolean opts out: a missing or mistyped setting must
+  // never silently remove enforcement from an existing adopter.
+  if (input.config?.enabled === false) {
+    return {
+      verdict: "SKIPPED",
+      reasons: ["designSource.enabled=false"],
+      violations: [],
+      exceptions: [],
+      syncBackPreferred: [],
+      sealed: [],
+      notApplicable: [],
+      summary: { judged: 0, sealed: 0, exceptions: 0, violations: 0 },
+    };
+  }
+
   const reasons = [];
   const files = Array.isArray(input.files) ? input.files : null;
 
@@ -452,7 +471,7 @@ export function collectChangedFiles(base, head) {
 /**
  * Read the optional `designSource` block from `.lisa.config.json`.
  *
- * @returns {{ include?: string[], exclude?: string[] }} Project overrides, or {}.
+ * @returns {{ enabled?: unknown, include?: string[], exclude?: string[] }} Project overrides, or {}.
  */
 function readProjectConfig() {
   try {
@@ -471,6 +490,9 @@ function readProjectConfig() {
  * @returns {string} Report text.
  */
 export function renderReport(result) {
+  if (result.verdict === "SKIPPED") {
+    return "design-source gate: SKIPPED: designSource.enabled=false";
+  }
   const lines = [`design-source gate: ${result.verdict}`];
 
   if (result.verdict === "PASS") {
@@ -534,15 +556,15 @@ export function runCli(argv) {
     return 2;
   }
 
-  const { files, diffError } = collectChangedFiles(
-    base,
-    args.get("head") ?? "HEAD"
-  );
+  const config = readProjectConfig();
+  const change =
+    config.enabled === false
+      ? {}
+      : collectChangedFiles(base, args.get("head") ?? "HEAD");
   const result = evaluateDesignSource({
-    files,
-    diffError,
+    ...change,
     figmaAccess: args.get("figma-access") === "true",
-    config: readProjectConfig(),
+    config,
   });
 
   process.stdout.write(
@@ -550,7 +572,7 @@ export function runCli(argv) {
       ? `${JSON.stringify(result, null, 2)}\n`
       : `${renderReport(result)}\n`
   );
-  return result.verdict === "PASS" ? 0 : 1;
+  return result.verdict === "FAIL" ? 1 : 0;
 }
 
 /**

package/plugins/lisa-cursor/skills/lisa-design-intake/SKILL.md

@@ -14,7 +14,7 @@ This skill carries the **judgment**. It does not carry the **policy** — that i
 
 ## What this is not
 
-`design-source-of-truth` and `scripts/design-source-gate.mjs` already ask whether a changed surface **declares where its design came from**. This asks the orthogonal question: are the **values on it bound**. Both apply. A surface can cite a perfectly valid design node and still paint a literal that no variable backs — that is the case this skill exists for, and it is invisible to the other gate.
+`design-source-of-truth` and `scripts/design-source-gate.mjs` already ask whether a changed surface **declares where its design came from**. This asks the orthogonal question: are the **values on it bound**. Design-source declarations apply unless the project explicitly sets `designSource.enabled` to boolean `false`; that opt-out does not disable this skill or `design-value-binding`. A surface can cite a perfectly valid design node and still paint a literal that no variable backs — that is the case this skill exists for, and it is invisible to the other gate.
 
 ## Why this gate is executable and not advisory
 

package/plugins/lisa-cursor/skills/lisa-implement/SKILL.md

@@ -160,7 +160,9 @@ IF it is a Fix (bug), execute the Reproduce sub-flow FIRST:
 
 For any Fix flow, and for any Build flow that changes user-visible behavior, regression coverage is a required deliverable at the highest practical observation level for the reported surface. If the project has a browser, device, or end-to-end harness for that platform (for example Playwright, Maestro, Detox, Cypress, or an equivalent runtime), the task plan and definition of done MUST include a deterministic regression spec against the reported surface, using mocked or seeded data where needed. This is alongside unit or integration coverage, not a substitute for it. For **frontend work** the deliverable is defined by the `bdd-e2e-coverage` rule and has two halves, both landing in this PR: the Gherkin scenario (stable ID, required platforms) added or updated in the project's behavior contract, and aligned automation in the project's configured runner for **every** platform that scenario requires — no runner substitutes for another, because they guard different platforms of the same behavior. The coverage gate must pass and the matrix and burndown be regenerated before the item is done. Cite the rule; do not restate its scenario, waiver, or bootstrap mechanics here.
 
-For work that adds or changes a **UI surface**, the `design-source-of-truth` rule adds a second non-demotable deliverable landing in this same PR: every UI surface the change touches declares where its design came from. Figma is the source of truth, so **prefer sync-back** — if the surface is not in Figma yet and the tool-access preflight proved Figma access, reflect it there and cite the node with `DESIGN-SOURCE: <figma-url>`. Only when the surface genuinely does not belong in the design source (debug affordance, dev-only playground, internal tooling) does it carry the exception marker `DESIGN-SOURCE: none — not in Figma`, ideally with a trailing reason. `scripts/design-source-gate.mjs` decides this deterministically and fails closed on anything it cannot resolve; a FAIL blocks the item exactly as a failing coverage gate does. Host design-system rules (`figma-design-system`, `design-system`, `use-the-design-library`, or the project's equivalent) stay authoritative about *what* to build — this obligation is only about declaring the source. Cite the rule; do not restate its marker grammar, host-precedence, or bootstrap mechanics here.
+Before preparing any design-source tasks or teammate instructions, read `designSource.enabled` in `.lisa.config.json`. Only boolean `false` opts out: omit the design-source step from the plan and all teammate prompts; do not request DESIGN-SOURCE markers, Figma nodes, or Figma access for this obligation. Absent, true, or invalid values keep enforcement enabled. The separate `design-value-binding` obligation and host design-system rules remain in force.
+
+When enabled, for work that adds or changes a **UI surface**, the `design-source-of-truth` rule adds a second non-demotable deliverable landing in this same PR: every UI surface the change touches declares where its design came from. Figma is the source of truth, so **prefer sync-back** — if the surface is not in Figma yet and the tool-access preflight proved Figma access, reflect it there and cite the node with `DESIGN-SOURCE: <figma-url>`. Only when the surface genuinely does not belong in the design source (debug affordance, dev-only playground, internal tooling) does it carry the exception marker `DESIGN-SOURCE: none — not in Figma`, ideally with a trailing reason. `scripts/design-source-gate.mjs` decides this deterministically and fails closed on anything it cannot resolve; a FAIL blocks the item exactly as a failing coverage gate does. Host design-system rules (`figma-design-system`, `design-system`, `use-the-design-library`, or the project's equivalent) stay authoritative about *what* to build — this obligation is only about declaring the source. Cite the rule; do not restate its marker grammar, host-precedence, or bootstrap mechanics here.
 
 The `design-value-binding` rule adds a second, orthogonal obligation on the same surfaces: **values come from design variables where a variable system exists.** That contract asks whether the values are *bound*, not whether the source is *declared* — a surface can cite a valid design node and still paint a literal no variable backs. Resolve the regime per axis, block only on the five objectively checkable conditions, and record every value derived in an untyped axis on the work item. `/lisa:design:intake` runs it. Cite the rule; do not restate its conditions, config schema, or comment grammar here.
 

package/plugins/lisa-cursor/skills/lisa-quality-review/SKILL.md

@@ -16,7 +16,7 @@ For each changed file, evaluate:
 3. **Test coverage** -- Tests present? Testing behavior, not implementation details? Edge cases covered?
 4. **Documentation** -- JSDoc on new functions explaining "why"? Preambles on new files?
 5. **Code clarity** -- Readable variable names? Unnecessary complexity? Could a new team member understand this?
-6. **Design source** -- For UI surfaces, does each changed file say where its design came from? Run the deterministic gate rather than judging by eye:
+6. **Design source** -- Read `designSource.enabled` in `.lisa.config.json` first. Only boolean `false` opts out: omit the design-source review step; do not request DESIGN-SOURCE markers, Figma nodes, or Figma access for this obligation. Record `SKIPPED: designSource.enabled=false` in the review. Absent, true, or invalid values keep enforcement enabled. When enabled, for UI surfaces, does each changed file say where its design came from? Run the deterministic gate rather than judging by eye:
 
    ```bash
    node "${CLAUDE_PLUGIN_ROOT:-.}/scripts/design-source-gate.mjs" --base=main --head=HEAD
@@ -24,7 +24,7 @@ For each changed file, evaluate:
 
    Exit 1 is a **Critical** finding under the `design-source-of-truth` rule -- the change is blocked until every UI surface either cites a Figma node (`DESIGN-SOURCE: <figma-url>`, the preferred fix -- sync it back) or carries the exception marker `DESIGN-SOURCE: none — not in Figma`. The gate fails closed: an unreadable file or an uncomputable diff is a FAIL, not a pass. Host design-system rules (`figma-design-system`, `design-system`, `use-the-design-library`, or the project's equivalent) stay authoritative about what to build; this checks only that the source is declared. If the gate script is absent, say so in the review rather than skipping silently.
 
-   Review the same surfaces against the `design-value-binding` rule as well — it asks the orthogonal question of whether each value is *bound* to what the design system publishes, not whether the source is declared. A literal in an axis the project publishes variables for is a **Critical** finding; the identical literal in an axis with no variable collection is correct and must not be flagged. Aesthetic disagreement is never a finding under this rule. Cite the rule; do not restate its conditions here.
+7. **Design-value binding** -- Independently of the design-source opt-out, review the same surfaces against the `design-value-binding` rule — it asks the orthogonal question of whether each value is *bound* to what the design system publishes, not whether the source is declared. A literal in an axis the project publishes variables for is a **Critical** finding; the identical literal in an axis with no variable collection is correct and must not be flagged. Aesthetic disagreement is never a finding under this rule. Cite the rule; do not restate its conditions here.
 
 ## Output Format
 

package/plugins/lisa-cursor/skills/lisa-review-local/SKILL.md

@@ -18,14 +18,20 @@ One deterministic gate runs ahead of the judgement-based review and is exempt
 from the confidence filtering below, because it is decided by a script rather
 than by an agent's opinion.
 
-**Design-source gate (`design-source-of-truth` rule).** Run it against the
-branch diff before step 1:
+**Design-source gate (`design-source-of-truth` rule).** First read
+`designSource.enabled` in `.lisa.config.json`. Only boolean `false` opts out:
+omit the design-source review step; do not request DESIGN-SOURCE markers, Figma
+nodes, or Figma access for this obligation. Record `SKIPPED: designSource.enabled=false`
+in the review. Absent, true, or invalid values keep enforcement enabled.
+The separate design-value binding review below still applies.
+
+When enabled, run the gate against the branch diff before step 1:
 
 ```bash
 node "${CLAUDE_PLUGIN_ROOT:-.}/scripts/design-source-gate.mjs" --base=main --head=HEAD
 ```
 
-Exit 0 = PASS, exit 1 = FAIL. A FAIL is a **blocking** review finding and is
+Exit 0 = PASS or explicit SKIPPED, exit 1 = FAIL. A FAIL is a **blocking** review finding and is
 reported verbatim at the top of the review — it is never scored, never filtered
 by confidence, and never demoted to a nitpick. It qualifies under
 `convergent-review` because it names a concrete failure scenario: the design

package/plugins/lisa-cursor/skills/lisa-tdd-implementation/SKILL.md

@@ -72,7 +72,8 @@ TDD Cycle:
 
 - Write the minimum production code to make the test pass
 - Do not optimize, do not add features beyond what the test requires
-- For any UI surface the implementation adds or changes, the `design-source-of-truth` rule requires its design-source declaration to land in the same commit as the surface it describes — `DESIGN-SOURCE: <figma-url>` when the surface is backed by a Figma node (sync it back first if Figma access exists), or the exception marker `DESIGN-SOURCE: none — not in Figma` when it genuinely is not captured at the source. `scripts/design-source-gate.mjs` fails closed on an undeclared surface. Cite the rule; do not restate its marker grammar here.
+- Read `designSource.enabled` in `.lisa.config.json` before preparing design-source instructions. Only boolean `false` opts out: omit the design-source step and do not request DESIGN-SOURCE markers, Figma nodes, or Figma access for this obligation. Absent, true, or invalid values keep enforcement enabled.
+- When enabled, for any UI surface the implementation adds or changes, the `design-source-of-truth` rule requires its design-source declaration to land in the same commit as the surface it describes — `DESIGN-SOURCE: <figma-url>` when the surface is backed by a Figma node (sync it back first if Figma access exists), or the exception marker `DESIGN-SOURCE: none — not in Figma` when it genuinely is not captured at the source. `scripts/design-source-gate.mjs` fails closed on an undeclared surface. Cite the rule; do not restate its marker grammar here.
 - Separately, the `design-value-binding` rule governs where each *value* on that surface came from: in an axis with a published variable collection, bind the variable and use a screenshot only to verify; in an axis with none, measure and record what you derived. A literal in a typed axis is a block, not a TODO. Cite the rule; do not restate its conditions here.
 - The goal is the simplest code that makes the test green
 

package/plugins/lisa-cursor/skills/lisa-tracker-source-artifacts/SKILL.md

@@ -93,7 +93,9 @@ Mocks define visual *intent*, not implementation shortcut. Every UI-touching tic
 
 If no existing component fits, building a new one is an explicit decision that must be recorded in the ticket (with rationale) before implementation. Lovable-generated components are never the reuse target — always use the project's own components.
 
-The divergence note above covers the **ticket** side of this event. The **code** side is governed by the `design-source-of-truth` rule: a UI surface built with no Figma source behind it is either synced back to Figma and annotated `DESIGN-SOURCE: <figma-url>`, or explicitly marked `DESIGN-SOURCE: none — not in Figma`, and review fails closed if neither happened. Cite the rule for the code obligation rather than restating it here — a ticket comment closes with the ticket, the annotation stays with the surface.
+Before adding the code-side obligation to ticket or teammate instructions, read `designSource.enabled` in `.lisa.config.json`. Only boolean `false` opts out: omit the design-source step; do not request DESIGN-SOURCE markers, Figma nodes, or Figma access for this obligation. Absent, true, or invalid values keep enforcement enabled. Preserve supplied artifacts and component-reuse requirements regardless; `design-value-binding` remains independent.
+
+When enabled, the divergence note above covers the **ticket** side of this event. The **code** side is governed by the `design-source-of-truth` rule: a UI surface built with no Figma source behind it is either synced back to Figma and annotated `DESIGN-SOURCE: <figma-url>`, or explicitly marked `DESIGN-SOURCE: none — not in Figma`, and review fails closed if neither happened. Cite the rule for the code obligation rather than restating it here — a ticket comment closes with the ticket, the annotation stays with the surface.
 
 ## 8. Preservation gate (run after creating tickets)
 

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "4.64.1",
+  "version": "4.64.3",
   "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": "4.64.1",
+  "version": "4.64.3",
   "description": "Expo and React Native-specific skills, agents, rules, and MCP servers.",
   "author": {
     "name": "Cody Swann"

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

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

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

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

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

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

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "4.64.1",
+  "version": "4.64.3",
   "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": "4.64.1",
+  "version": "4.64.3",
   "description": "Harper/Fabric-specific Lisa rules for TypeScript component apps.",
   "author": {
     "name": "Cody Swann"

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

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

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

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

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

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

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "4.64.1",
+  "version": "4.64.3",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "4.64.1",
+  "version": "4.64.3",
   "description": "NestJS-specific skills and migration write-protection hooks.",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "4.64.1",
+  "version": "4.64.3",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "4.64.1",
+  "version": "4.64.3",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "4.64.1",
+  "version": "4.64.3",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "4.64.1",
+  "version": "4.64.3",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "4.64.1",
+  "version": "4.64.3",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, across Claude and Codex.",
   "author": {
     "name": "Cody Swann"