@codyswann/lisa 2.191.14 → 2.192.1

package/dist/configs/eslint/harper-fabric.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"harper-fabric.d.ts","sourceRoot":"","sources":["../../../src/configs/eslint/harper-fabric.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,QAAQ,CAAC;AACrC,OAAO,EACL,cAAc,EACd,iBAAiB,EAElB,MAAM,iBAAiB,CAAC;AAEzB,OAAO,EAAE,cAAc,EAAE,iBAAiB,EAAE,CAAC;AAE7C;;GAEG;AACH,eAAO,MAAM,0BAA0B,UAUtC,CAAC;AAEF;;;;;;;GAOG;AACH,wBAAgB,qBAAqB,CAAC,EACpC,eAAe,EACf,cAA2C,EAC3C,UAA8B,GAC/B,EAAE;IACD,eAAe,EAAE,MAAM,CAAC;IACxB,cAAc,CAAC,EAAE,MAAM,EAAE,CAAC;IAC1B,UAAU,CAAC,EAAE,OAAO,iBAAiB,CAAC;CACvC,GAAG,MAAM,CAAC,MAAM,EAAE,CAkClB"}
+{"version":3,"file":"harper-fabric.d.ts","sourceRoot":"","sources":["../../../src/configs/eslint/harper-fabric.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,QAAQ,CAAC;AACrC,OAAO,EACL,cAAc,EACd,iBAAiB,EAElB,MAAM,iBAAiB,CAAC;AAEzB,OAAO,EAAE,cAAc,EAAE,iBAAiB,EAAE,CAAC;AAE7C;;GAEG;AACH,eAAO,MAAM,0BAA0B,UAetC,CAAC;AAEF;;;;;;;GAOG;AACH,wBAAgB,qBAAqB,CAAC,EACpC,eAAe,EACf,cAA2C,EAC3C,UAA8B,GAC/B,EAAE;IACD,eAAe,EAAE,MAAM,CAAC;IACxB,cAAc,CAAC,EAAE,MAAM,EAAE,CAAC;IAC1B,UAAU,CAAC,EAAE,OAAO,iBAAiB,CAAC;CACvC,GAAG,MAAM,CAAC,MAAM,EAAE,CAkClB"}

package/dist/configs/eslint/harper-fabric.js

@@ -11,6 +11,11 @@ export const defaultHarperFabricIgnores = [
     "*.config.local.ts",
     "harper-app/resources.js",
     "harper-app/resource-*.js",
+    // Root-level compiled Harper modules (resources.js, resource-*.js, and any
+    // other build output emitted straight into harper-app/). The single-star does
+    // not cross a directory separator, so hand-written shims one level down
+    // (harper-app/<route>/index.js) are still linted.
+    "harper-app/*.js",
     "harper-app/web/**",
     "harper-app/lib/**",
 ];

package/dist/configs/eslint/harper-fabric.js.map

@@ -1 +1 @@
-{"version":3,"file":"harper-fabric.js","sourceRoot":"","sources":["../../../src/configs/eslint/harper-fabric.ts"],"names":[],"mappings":"AAQA,OAAO,EACL,cAAc,EACd,iBAAiB,EACjB,mBAAmB,GACpB,MAAM,iBAAiB,CAAC;AAEzB,OAAO,EAAE,cAAc,EAAE,iBAAiB,EAAE,CAAC;AAE7C;;GAEG;AACH,MAAM,CAAC,MAAM,0BAA0B,GAAG;IACxC,GAAG,cAAc;IACjB,WAAW;IACX,UAAU;IACV,WAAW;IACX,mBAAmB;IACnB,yBAAyB;IACzB,0BAA0B;IAC1B,mBAAmB;IACnB,mBAAmB;CACpB,CAAC;AAEF;;;;;;;GAOG;AACH,MAAM,UAAU,qBAAqB,CAAC,EACpC,eAAe,EACf,cAAc,GAAG,0BAA0B,EAC3C,UAAU,GAAG,iBAAiB,GAK/B;IACC,OAAO;QACL,GAAG,mBAAmB,CAAC;YACrB,eAAe;YACf,cAAc;YACd,UAAU;SACX,CAAC;QACF;YACE,KAAK,EAAE,CAAC,aAAa,CAAC;YACtB,KAAK,EAAE;gBACL,2BAA2B,EAAE,OAAO;gBACpC,mBAAmB,EAAE,OAAO;gBAC5B,iCAAiC,EAAE,OAAO;gBAC1C,0BAA0B,EAAE,OAAO;gBACnC,0CAA0C,EAAE,OAAO;aACpD;SACF;QACD;YACE,KAAK,EAAE,CAAC,oBAAoB,EAAE,oBAAoB,CAAC;YACnD,KAAK,EAAE;gBACL,2BAA2B,EAAE,KAAK;gBAClC,mBAAmB,EAAE,KAAK;gBAC1B,iCAAiC,EAAE,KAAK;gBACxC,0BAA0B,EAAE,KAAK;gBACjC,0CAA0C,EAAE,KAAK;aAClD;SACF;QACD;YACE,KAAK,EAAE,CAAC,qBAAqB,EAAE,eAAe,CAAC;YAC/C,KAAK,EAAE;gBACL,sBAAsB,EAAE,KAAK;aAC9B;SACF;KACiB,CAAC;AACvB,CAAC"}
+{"version":3,"file":"harper-fabric.js","sourceRoot":"","sources":["../../../src/configs/eslint/harper-fabric.ts"],"names":[],"mappings":"AAQA,OAAO,EACL,cAAc,EACd,iBAAiB,EACjB,mBAAmB,GACpB,MAAM,iBAAiB,CAAC;AAEzB,OAAO,EAAE,cAAc,EAAE,iBAAiB,EAAE,CAAC;AAE7C;;GAEG;AACH,MAAM,CAAC,MAAM,0BAA0B,GAAG;IACxC,GAAG,cAAc;IACjB,WAAW;IACX,UAAU;IACV,WAAW;IACX,mBAAmB;IACnB,yBAAyB;IACzB,0BAA0B;IAC1B,2EAA2E;IAC3E,8EAA8E;IAC9E,wEAAwE;IACxE,kDAAkD;IAClD,iBAAiB;IACjB,mBAAmB;IACnB,mBAAmB;CACpB,CAAC;AAEF;;;;;;;GAOG;AACH,MAAM,UAAU,qBAAqB,CAAC,EACpC,eAAe,EACf,cAAc,GAAG,0BAA0B,EAC3C,UAAU,GAAG,iBAAiB,GAK/B;IACC,OAAO;QACL,GAAG,mBAAmB,CAAC;YACrB,eAAe;YACf,cAAc;YACd,UAAU;SACX,CAAC;QACF;YACE,KAAK,EAAE,CAAC,aAAa,CAAC;YACtB,KAAK,EAAE;gBACL,2BAA2B,EAAE,OAAO;gBACpC,mBAAmB,EAAE,OAAO;gBAC5B,iCAAiC,EAAE,OAAO;gBAC1C,0BAA0B,EAAE,OAAO;gBACnC,0CAA0C,EAAE,OAAO;aACpD;SACF;QACD;YACE,KAAK,EAAE,CAAC,oBAAoB,EAAE,oBAAoB,CAAC;YACnD,KAAK,EAAE;gBACL,2BAA2B,EAAE,KAAK;gBAClC,mBAAmB,EAAE,KAAK;gBAC1B,iCAAiC,EAAE,KAAK;gBACxC,0BAA0B,EAAE,KAAK;gBACjC,0CAA0C,EAAE,KAAK;aAClD;SACF;QACD;YACE,KAAK,EAAE,CAAC,qBAAqB,EAAE,eAAe,CAAC;YAC/C,KAAK,EAAE;gBACL,sBAAsB,EAAE,KAAK;aAC9B;SACF;KACiB,CAAC;AACvB,CAAC"}

package/harper-fabric/copy-contents/.prettierignore

@@ -4,6 +4,7 @@
 # source formatting inputs.
 harper-app/resources.js
 harper-app/resource-*.js
+harper-app/*.js
 harper-app/web/**
 harper-app/lib/**
 research/articles/

package/harper-fabric/copy-contents/gitignore

@@ -1,6 +1,13 @@
 # BEGIN: AI GUARDRAILS HARPER-FABRIC
+# Compiled Harper modules are emitted straight into harper-app/ from src/. The
+# root-level `harper-app/*.js` rule covers resources.js, resource-*.js, and any
+# other build output (e.g. detail-shell-negotiation.js) without matching
+# hand-written shims nested one level down (harper-app/<route>/index.js). If you
+# keep a hand-written .js at the harper-app root (e.g. an SEO shell), re-include
+# it with a `!harper-app/<file>.js` line placed BELOW this managed block.
 harper-app/resources.js
 harper-app/resource-*.js
+harper-app/*.js
 harper-app/web/**
 harper-app/lib/**
 .lisabak/

package/harper-fabric/copy-overwrite/.github/dependabot.yml

@@ -0,0 +1,47 @@
+# This file is managed by Lisa.
+# Do not edit directly — changes will be overwritten on the next `lisa` run.
+
+# Harper/Fabric override of the TypeScript dependabot template.
+# A fresh Harper/Fabric repo ships with only a `main` branch, so this file
+# omits `target-branch` — Dependabot then opens PRs against the repository's
+# default branch instead of a `dev` branch that does not exist. If a project
+# adopts a long-lived integration branch, set `target-branch` back per updater.
+
+version: 2
+updates:
+  # JavaScript/Node.js dependencies
+  - package-ecosystem: npm
+    directory: /
+    schedule:
+      interval: weekly
+      day: monday
+    open-pull-requests-limit: 10
+    groups:
+      production-dependencies:
+        dependency-type: production
+        update-types:
+          - minor
+          - patch
+      development-dependencies:
+        dependency-type: development
+        update-types:
+          - minor
+          - patch
+    labels:
+      - dependencies
+    commit-message:
+      prefix: 'chore(deps)'
+      prefix-development: 'chore(deps-dev)'
+
+  # GitHub Actions
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: weekly
+      day: monday
+    open-pull-requests-limit: 5
+    labels:
+      - dependencies
+      - github-actions
+    commit-message:
+      prefix: 'ci(deps)'

package/harper-fabric/copy-overwrite/ast-grep/rules/harper/no-early-return-in-search-loop.yml

@@ -0,0 +1,27 @@
+# This file is managed by Lisa.
+# Do not edit directly — changes will be overwritten on the next `lisa` run.
+id: harper-no-early-return-in-search-loop
+language: typescript
+severity: warning
+message: |
+  Early `return`/`break` out of a `for await (... of tables.X.search(...))` loop
+  leaves Harper's read transaction open — the iterator is abandoned before the
+  scan completes and the transaction is not released, leaking a read handle.
+note: >-
+  Drain or explicitly close the iterator on early exit. Prefer bounding the query
+  so the loop finishes naturally (`search({ ..., limit: 1 })` when you only need
+  the first row), or drive the iterator manually and call `iterator.return?.()`
+  in a `finally` block so Harper releases the read transaction. This is a
+  heuristic — a `break` that belongs to an inner `switch` or a `return` inside a
+  nested callback is a false positive; suppress those with an inline
+  `// ast-grep-ignore: harper-no-early-return-in-search-loop`.
+rule:
+  any:
+    - kind: return_statement
+    - kind: break_statement
+  inside:
+    kind: for_in_statement
+    stopBy: end
+    has:
+      field: right
+      pattern: $ITER.search($$$ARGS)

package/harper-fabric/copy-overwrite/ast-grep/rules/harper/no-empty-conditions-with-sort.yml

@@ -0,0 +1,45 @@
+# This file is managed by Lisa.
+# Do not edit directly — changes will be overwritten on the next `lisa` run.
+id: harper-no-empty-conditions-with-sort
+language: typescript
+severity: error
+message: |
+  A Harper `search()` with `sort` but an empty `conditions: []` array crashes
+  the query planner — it cannot seed the btree scan from the sort attribute and
+  throws at runtime (a latent 500 the first time an unfiltered, sorted page is
+  requested).
+note: >-
+  Seed a floor/sentinel condition on the sort attribute so the planner has an
+  index range to walk, e.g. `{ attribute: "lastName", comparator:
+  "greater_than_equal", value: "" }` (or `not_equal: null`), then apply the sort.
+  Centralize this in the page helper (`searchPageAndCount`) rather than
+  duplicating a sentinel at each call site. If a sort-only scan is genuinely
+  intended and the attribute is guaranteed present, suppress with an inline
+  `// ast-grep-ignore: harper-no-empty-conditions-with-sort` and a comment.
+rule:
+  kind: object
+  all:
+    - has:
+        kind: pair
+        all:
+          - has:
+              field: key
+              regex: ^conditions$
+          - has:
+              field: value
+              kind: array
+              regex: "^\\[\\s*\\]$"
+    - has:
+        kind: pair
+        has:
+          field: key
+          regex: ^sort$
+  inside:
+    kind: arguments
+    stopBy: end
+    inside:
+      kind: call_expression
+      stopBy: end
+      has:
+        field: function
+        regex: search$

package/harper-fabric/copy-overwrite/ast-grep/rules/harper/no-full-table-scan.yml

@@ -0,0 +1,33 @@
+# This file is managed by Lisa.
+# Do not edit directly — changes will be overwritten on the next `lisa` run.
+id: harper-no-full-table-scan
+language: typescript
+severity: warning
+message: |
+  Possible full table scan in a Harper resource. Loading a whole table on every
+  request does not scale — one large table (e.g. an employment/event history) was
+  the root cause of multi-second `/Search` and directory responses and a day-long
+  red deploy gate in production.
+note: >-
+  Fetch only the rows you need through an indexed attribute
+  (`rowsByAttribute(tables.$TABLE, "someIndexedId", value)`), or page with
+  `searchPageAndCount` / `search({ conditions, limit, offset })`. A conditionless
+  `tables.$TABLE.search({})` / `search()` and the `allRows` / `optionalAll`
+  helpers read every row. Small lookup tables can be legitimate to scan — this is
+  a warning; if a full scan is genuinely intended (a one-off offline script, never
+  a Resource handler), suppress with an inline
+  `// ast-grep-ignore: harper-no-full-table-scan` and a comment saying why.
+rule:
+  any:
+    # Non-generic full-table reads via common directory helpers.
+    - pattern: allRows(tables.$TABLE)
+    - pattern: optionalAll(tables.$TABLE)
+    # Generic form, e.g. allRows<AdvisorRow>(tables.Advisor): the type argument
+    # nests the callee in an instantiation_expression, so the plain patterns
+    # above miss it. Any single-arg generic call passing the whole table is a
+    # full scan regardless of helper name (the scoped rowsByAttribute helper
+    # takes 3 args and is not matched).
+    - pattern: $FN<$TYPE>(tables.$TABLE)
+    # Raw unconditional table scans.
+    - pattern: tables.$TABLE.search({})
+    - pattern: tables.$TABLE.search()

package/harper-fabric/copy-overwrite/ast-grep/rules/harper/require-statuscode-on-thrown-error.yml

@@ -0,0 +1,41 @@
+# This file is managed by Lisa.
+# Do not edit directly — changes will be overwritten on the next `lisa` run.
+id: harper-require-statuscode-on-thrown-error
+language: typescript
+severity: error
+message: |
+  This error carries `status` but not `statusCode`. Harper's thrown-error HTTP
+  response writer reads `error.statusCode` (falling back to 500); a plain
+  `status` is ignored, so every intended 4xx becomes a 500 on the wire.
+note: >-
+  Set `statusCode` (keep `status` too if callers/tests rely on it):
+  `Object.assign(error, { status, statusCode: status })`, or in an Error
+  subclass assign `this.statusCode = status` alongside `this.status`. Verified
+  live on harperdb 4.7.32 — a 401/403/404 thrown with only `status` was served
+  as 500. Direct `err.status = code` assignments are not auto-detected; when you
+  attach an HTTP code to a thrown error, always set `statusCode`.
+rule:
+  any:
+    # `Object.assign(error, { status })` with only a `status` property — the
+    # exact object match excludes the correct `{ status, statusCode }` form.
+    - pattern: 'Object.assign($E, { status: $S })'
+    # Error subclass that assigns `this.status` but never mentions `statusCode`
+    # anywhere in the class body.
+    - pattern: this.status = $S
+      inside:
+        kind: class_declaration
+        stopBy: end
+        all:
+          - has:
+              kind: class_heritage
+              stopBy: end
+              has:
+                kind: extends_clause
+                has:
+                  field: value
+                  regex: Error$
+          - not:
+              has:
+                kind: property_identifier
+                regex: ^statusCode$
+                stopBy: end

package/harper-fabric/copy-overwrite/knip.json

@@ -15,6 +15,7 @@
     "**/node_modules/**",
     "harper-app/resources.js",
     "harper-app/resource-*.js",
+    "harper-app/*.js",
     "harper-app/web/**",
     "harper-app/lib/**"
   ],

package/harper-fabric/copy-overwrite/tsconfig.eslint.json

@@ -22,6 +22,7 @@
     "coverage",
     "harper-app/resources.js",
     "harper-app/resource-*.js",
+    "harper-app/*.js",
     "harper-app/web/**",
     "harper-app/lib/**"
   ]

package/harper-fabric/merge/.oxlintrc.json

@@ -12,6 +12,7 @@
     "**/generated/**",
     "harper-app/resources.js",
     "harper-app/resource-*.js",
+    "harper-app/*.js",
     "harper-app/web/**",
     "harper-app/lib/**"
   ]

package/oxlint/harper-fabric.json

@@ -7,6 +7,7 @@
     "node_modules/**",
     "harper-app/resources.js",
     "harper-app/resource-*.js",
+    "harper-app/*.js",
     "harper-app/web/**",
     "harper-app/lib/**"
   ]

package/package.json

@@ -95,7 +95,7 @@
     "ws": ">=8.20.1"
   },
   "name": "@codyswann/lisa",
-  "version": "2.191.14",
+  "version": "2.192.1",
   "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.191.14",
+  "version": "2.192.1",
   "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.191.14",
+  "version": "2.192.1",
   "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.191.14",
+  "version": "2.192.1",
   "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.191.14",
+  "version": "2.192.1",
   "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.191.14",
+  "version": "2.192.1",
   "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.191.14",
+  "version": "2.192.1",
   "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.191.14",
+  "version": "2.192.1",
   "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.191.14",
+  "version": "2.192.1",
   "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.191.14",
+  "version": "2.192.1",
   "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.191.14",
+  "version": "2.192.1",
   "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.191.14",
+  "version": "2.192.1",
   "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.191.14",
+  "version": "2.192.1",
   "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": "2.191.14",
+  "version": "2.192.1",
   "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": "2.191.14",
+  "version": "2.192.1",
   "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": "2.191.14",
+  "version": "2.192.1",
   "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": "2.191.14",
+  "version": "2.192.1",
   "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.191.14",
+  "version": "2.192.1",
   "description": "Harper/Fabric-specific Lisa rules for TypeScript component apps.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric/generated-artifact-globs.txt

@@ -1,4 +1,5 @@
 harper-app/resources.js
 harper-app/resource-*.js
+harper-app/*.js
 harper-app/web/**
 harper-app/lib/**

package/plugins/lisa-harper-fabric/hooks/block-generated-artifact-edits.sh

@@ -33,6 +33,7 @@ matches_glob() {
   local file="$1"
   local glob="$2"
 
+  # Recursive directory globs: "dir/**" matches everything under dir.
   if [ "${glob: -3}" = "/**" ]; then
     local dir="${glob%/**}"
     case "$file" in
@@ -41,6 +42,38 @@ matches_glob() {
     return 1
   fi
 
+  # Single-star globs like "harper-app/*.js": the star must not cross a
+  # directory separator, so a broadened root-level pattern protects compiled
+  # modules emitted straight into harper-app/ (resources.js, resource-*.js, and
+  # any other build output such as detail-shell-negotiation.js) WITHOUT matching
+  # hand-written files nested one level down (e.g. harper-app/<route>/index.js).
+  case "$glob" in
+    */\** | \**)
+      local base_glob="${glob##*/}"
+      local dir_glob=""
+      case "$glob" in
+        */*) dir_glob="${glob%/*}" ;;
+      esac
+      local file_base="${file##*/}"
+      local file_dir=""
+      case "$file" in
+        */*) file_dir="${file%/*}" ;;
+      esac
+      case "$file_base" in
+        $base_glob) ;;
+        *) return 1 ;;
+      esac
+      [ -z "$dir_glob" ] && return 0
+      # Match the directory exactly, or as a suffix so absolute/prefixed paths
+      # (e.g. /repo/harper-app/foo.js) still resolve.
+      case "$file_dir" in
+        $dir_glob | */"$dir_glob") return 0 ;;
+      esac
+      return 1
+      ;;
+  esac
+
+  # Literal (wildcard-free) globs.
   case "$file" in
     $glob | */$glob) return 0 ;;
   esac
@@ -50,6 +83,24 @@ matches_glob() {
 
 NORMALIZED_FILE=$(normalize_path "$FILE_PATH")
 
+# Project-owned allowlist of hand-written files that live under harper-app/ and
+# must NOT be treated as generated (e.g. a hand-authored SEO shell, or route
+# index.js shims kept at the harper-app root). The broadened root-level
+# `harper-app/*.js` protection would otherwise block editing them. One glob per
+# line (same syntax as the globs file); blank lines and `#` comments ignored.
+# Prefer naming compiled resource modules `resource-*.ts` so their JS output is
+# unambiguously generated and never needs allowlisting.
+ALLOWLIST_FILE="${CLAUDE_PROJECT_DIR:-.}/.lisa/harper-generated-artifact-allowlist.txt"
+if [ -f "$ALLOWLIST_FILE" ]; then
+  while IFS= read -r allow || [ -n "$allow" ]; do
+    [ -n "$allow" ] || continue
+    case "$allow" in \#*) continue ;; esac
+    if matches_glob "$NORMALIZED_FILE" "$allow"; then
+      exit 0
+    fi
+  done <"$ALLOWLIST_FILE"
+fi
+
 while IFS= read -r glob || [ -n "$glob" ]; do
   [ -n "$glob" ] || continue
   case "$glob" in \#*) continue ;; esac

package/plugins/lisa-harper-fabric/rules/harper-fabric.md

@@ -13,7 +13,7 @@ These rules apply to Harper/Fabric component apps managed by Lisa.
 - TypeScript under `src/` is the source of truth for Harper resources, browser modules, shared libraries, and operational scripts.
 - `harper-app/config.yaml`, `harper-app/schema.graphql`, HTML, CSS, docs, and research fixtures are source assets.
 - `harper-app/config.yaml` does not merge with Harper defaults. Keep every required top-level extension declared when editing it; the Harper Fabric hook blocks accidental extension drops unless the removal is documented in `.lisa/harper-config-extension-allowlist.json`.
-- `harper-app/resources.js` and `harper-app/web/**/*.js` are generated deploy artifacts. Never edit them directly; change the matching TypeScript and run `bun run build`.
+- Every `.js` at the harper-app root (`harper-app/*.js` — `resources.js`, `resource-*.js`, and any other compiled module) plus `harper-app/web/**/*.js` and `harper-app/lib/**` are generated deploy artifacts. Never edit them directly; change the matching TypeScript and run `bun run build`. Name compiled resource modules `resource-*.ts` so their output is unambiguously generated; a hand-written `.js` kept at the harper-app root must be re-included in `.gitignore` and listed in `.lisa/harper-generated-artifact-allowlist.txt` so the block hook allows editing it.
 - Deployment, bootstrap, smoke, seed, verify, preview, token, crawl, ingest, and extraction commands must run from compiled JavaScript or generated Harper assets, not stale checked-in JavaScript.
 
 ## Harper/Fabric Deploy Surface

package/plugins/lisa-harper-fabric/skills/harper-auth/SKILL.md

@@ -260,6 +260,54 @@ Guidance:
   webhook must bypass Harper auth, verify its signature first and keep its table
   writes narrowly scoped.
 
+## Session cookies are `SameSite=None` — guard state-changing POSTs
+
+Harper hardcodes the session cookie's `SameSite=None` attribute on HTTPS. The
+browser therefore attaches the session cookie to **cross-site** requests, so a
+same-origin app cannot rely on `SameSite` to block CSRF on cookie-authenticated,
+state-changing routes (`POST`/`PUT`/`PATCH`/`DELETE`).
+
+Add an app-side origin check in the resource before mutating. Reject requests
+whose `Origin` (or `Referer` fallback) is not an allowed origin:
+
+```javascript
+const ALLOWED_ORIGINS = new Set([
+  'https://app.example.com',
+]);
+
+function requireSameOrigin(context) {
+  const headers = context.requestContext?.headers ?? context.headers;
+  const origin =
+    headers?.get?.('origin') ??
+    headers?.get?.('referer');
+  const ok =
+    typeof origin === 'string' &&
+    [...ALLOWED_ORIGINS].some((allowed) => origin.startsWith(allowed));
+  if (!ok) {
+    const error = new Error('Cross-origin request rejected');
+    error.statusCode = 403; // Harper reads statusCode, not status
+    throw error;
+  }
+}
+
+export class Watchlists extends tables.Watchlists {
+  static async post(target, data, context) {
+    requireSameOrigin(context);
+    // ...authorization and write
+    return super.post(target, await data, context);
+  }
+}
+```
+
+Guidance:
+
+- Call the check on every cookie-authenticated state-changing route. Read-only
+  `GET` handlers and token/`Authorization: Bearer` APIs (not cookie-driven) do
+  not need it.
+- Prefer an allowlist of exact origins over substring matching that a lookalike
+  host could satisfy.
+- This is defense the app owns; Harper will not add it for you.
+
 ## Verification matrix
 
 Run the local app, create the test users, and check unauthenticated, reader, and

package/plugins/lisa-harper-fabric/skills/harper-build-and-deploy/SKILL.md

@@ -50,15 +50,30 @@ What the build actually does:
 
 Generated Harper deploy artifacts usually include:
 
-- `harper-app/resources.js`
-- `harper-app/resource-*.js`
+- `harper-app/*.js` — every compiled module the build emits to the harper-app
+  root (`resources.js`, `resource-*.js`, and any other output such as a route
+  negotiation module). The single-star does **not** cross a directory separator,
+  so it does not match hand-written shims one level down.
 - `harper-app/web/**`
 - `harper-app/lib/**`
 
+The guard surfaces (`generated-artifact-globs.txt` for the PreToolUse block hook,
+`.gitignore`, `.prettierignore`, the ESLint/oxlint/knip ignores, and
+`tsconfig.eslint.json`) all key off `harper-app/*.js` so a newly-named compiled
+module is protected automatically. **Name compiled resource modules
+`resource-*.ts`** so their JS output is unambiguously generated.
+
+If you keep a *hand-written* `.js` at the harper-app root (e.g. an SEO shell),
+the root-level rule would otherwise treat it as generated: re-include it with a
+`!harper-app/<file>.js` line below the managed gitignore block, and add it to
+`.lisa/harper-generated-artifact-allowlist.txt` so the block hook lets you edit
+it. Hand-written shims nested under `harper-app/<route>/index.js` need no
+exemption — the root-level rule never matches them.
+
 Every lint, format, dead-code, search, or generated-artifact guard must ignore
-those generated paths unless it is explicitly validating the build output itself.
-When a new generated path appears, add it to every relevant ignore surface in the
-same change; partial ignores fail later gates in non-obvious ways.
+generated paths unless it is explicitly validating the build output itself. When
+a new generated *directory* appears, add it to every relevant ignore surface in
+the same change; partial ignores fail later gates in non-obvious ways.
 
 - **TypeScript under `src/` is source.** `bun run build` produces the deployable
   Harper assets from it.