@codyswann/lisa 4.17.19 → 4.19.0

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "4.17.19",
+  "version": "4.19.0",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "4.17.19",
+  "version": "4.19.0",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "4.17.19",
+  "version": "4.19.0",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "4.17.19",
+  "version": "4.19.0",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "4.17.19",
+  "version": "4.19.0",
   "description": "TypeScript-specific hooks for formatting, linting, and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "4.17.19",
+  "version": "4.19.0",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "4.17.19",
+  "version": "4.19.0",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "4.17.19",
+  "version": "4.19.0",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "4.17.19",
+  "version": "4.19.0",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "4.17.19",
+  "version": "4.19.0",
   "description": "Distributable LLM Wiki kernel — ingest, query, lint, and maintain a git-native markdown knowledge base across Claude and Codex.",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "4.17.19",
+  "version": "4.19.0",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "4.17.19",
+  "version": "4.19.0",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "4.17.19",
+  "version": "4.19.0",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/scripts/check-ui-demo-data.mjs

@@ -0,0 +1,102 @@
+#!/usr/bin/env node
+
+/**
+ * Evaluate the Lisa UI catalog in a code-generation-disabled VM and invoke the
+ * catalog's own renderer-aware audit. Keeping the audit in `ui/index.html`
+ * means the browser and repository guard cannot drift into different ideas of
+ * which values are renderable.
+ * @module scripts/check-ui-demo-data
+ */
+import { readFileSync } from "node:fs";
+import path from "node:path";
+import vm from "node:vm";
+
+import { invokedAsScript } from "./lib/invoked-as-script.mjs";
+
+const START_MARKER = "/* LISA_UI_CATALOG_START */";
+const END_MARKER = "/* LISA_UI_CATALOG_END */";
+const DEFAULT_UI_FILE = path.resolve("ui/index.html");
+const VM_TIMEOUT_MS = 2_000;
+
+/**
+ * Extract exactly one bounded catalog program from the HTML document.
+ * @param {string} html - Complete UI HTML
+ * @returns {string} Catalog JavaScript including the shared audit seam
+ */
+export function extractUiCatalogProgram(html) {
+  const start = html.indexOf(START_MARKER);
+  const end = html.indexOf(END_MARKER);
+  if (start === -1 || end === -1 || end <= start) {
+    throw new Error(
+      `UI catalog markers are missing or out of order (${START_MARKER}, ${END_MARKER})`
+    );
+  }
+  if (
+    html.indexOf(START_MARKER, start + START_MARKER.length) !== -1 ||
+    html.indexOf(END_MARKER, end + END_MARKER.length) !== -1
+  ) {
+    throw new Error("UI catalog markers must each occur exactly once");
+  }
+  return html.slice(start + START_MARKER.length, end);
+}
+
+/**
+ * Audit an HTML catalog and optionally exercise the live preparation path.
+ * @param {string} html - Complete UI HTML
+ * @param {{liveConfigPresent?: boolean, liveConfig?: unknown, filename?: string}} [options]
+ * @returns {{audit: {inspected: number, sections: number, violations: string[]}, preparation: object|null, catalog: object}}
+ */
+export function inspectUiDemoData(html, options = {}) {
+  const context = vm.createContext(
+    {
+      __liveConfigPresent: options.liveConfigPresent === true,
+      __liveConfig: options.liveConfig,
+    },
+    {
+      codeGeneration: { strings: false, wasm: false },
+      name: "lisa-ui-demo-data-audit",
+    }
+  );
+  const program = `${extractUiCatalogProgram(html)}
+    const __auditResult = auditUiCatalog(DATA);
+    const __preparationResult = globalThis.__liveConfigPresent
+      ? prepareUiCatalogForLive(DATA, globalThis.__liveConfig)
+      : null;
+    globalThis.__inspectionResult = {
+      audit: __auditResult,
+      preparation: __preparationResult,
+      catalog: DATA
+    };
+  `;
+  // The bounded catalog source is intentionally executed in a context with
+  // string/wasm code generation disabled and a hard timeout. This is the
+  // guard's shared-seam contract, not application input.
+  // eslint-disable-next-line sonarjs/code-eval -- Evaluate only the extracted catalog inside the locked VM above.
+  vm.runInContext(program, context, {
+    displayErrors: true,
+    filename: options.filename || "ui/index.html#catalog",
+    timeout: VM_TIMEOUT_MS,
+  });
+  return context.__inspectionResult;
+}
+
+/** Run the repository guard against a supplied file or the real UI. */
+function main() {
+  const file = path.resolve(process.argv[2] || DEFAULT_UI_FILE);
+  try {
+    const inspection = inspectUiDemoData(readFileSync(file, "utf8"), {
+      filename: file,
+    });
+    process.stdout.write(
+      `[ui-demo-data] PASS: inspected ${inspection.audit.inspected} rendered values across ${inspection.audit.sections} sections\n`
+    );
+  } catch (error) {
+    const message = error instanceof Error ? error.message : String(error);
+    process.stderr.write(`[ui-demo-data] FAIL: ${message}\n`);
+    process.exitCode = 1;
+  }
+}
+
+if (invokedAsScript(import.meta.url)) {
+  main();
+}

package/ui/README.md

@@ -4,14 +4,13 @@ A self-contained, zero-build prototype of the Lisa settings console. It catalogs
 every configuration surface Lisa exposes to host projects and presents it as a
 navigable, editable-looking settings UI.
 
-**Prototype scope:** every control is interactive (toggles, selects, inputs,
-tabs, dirty-state tracking, save bar). Reading real values IS wired up: see
-`lisa ui` below. Persistence is partial and the line to read is
-`src/sync/registry.ts`: a control whose config key is in `SYNC_REGISTRY` is
-written to `.lisa.config.json` through `POST /api/config`; every other control
-still only clears the in-memory dirty state on "Save". `gates` is **not** a
-registry key, so no console write can touch a gate declaration today — which is
-why the Doctor section reports and never repairs.
+**Prototype scope:** controls, tabs, dirty-state tracking, and the save bar are
+interactive. Reading real values IS wired up: see `lisa ui` below. The backend
+write contract now routes authorized keys through `POST /api/config`, but the
+page's **Save changes** button deliberately remains disabled until the separate
+save/rehydration UX ships. `gates` is **not** a registry key, so no console
+write can touch a gate declaration today — which is why the Doctor section
+reports and never repairs.
 
 ## Run it
 
@@ -31,6 +30,93 @@ live config it falls back to Lisa's shipped defaults:
 open ui/index.html
 ```
 
+## Demo-data boundary
+
+The standalone and CLI-served paths deliberately have different data
+contracts. Opening `ui/index.html` directly leaves
+`window.LISA_LIVE_CONFIG` absent and renders the fictional demo catalog. The
+CLI defines that property before the page boots, so the console enters live
+mode even when the injected value is `false`, `0`, an empty string, or `null`.
+Live mode scrubs every `demoOnly` block and row before the first render, keeps
+present falsey configuration values, turns missing configuration keys into
+`unknown`, and initializes probe/API values as pending or unknown. An empty
+live section and a filter with no matches both render a generic empty/unknown
+state; neither falls back to a demo value on a later render.
+
+Every renderer-bearing catalog value must declare exactly one provenance:
+
+- `key` for a value hydrated from `LISA_LIVE_CONFIG`;
+- `liveSource` for a probe, API, or injected live snapshot;
+- `demoOnly: true` for intentional direct-file sample data; or
+- `staticCopy` with a narrow reason for fixed Lisa documentation or semantics.
+
+The browser and repository guard invoke the same renderer-aware catalog audit.
+It discovers the current sections and values rather than relying on a hardcoded
+count, fails on unclassified or multiply classified values, and fails if it
+inspects nothing. Run it after adding or changing console data:
+
+```bash
+bun run check:ui-demo-data
+```
+
+`acme/acme-app` is not a forbidden string: a live project can legitimately use
+that name. The boundary is provenance, not a sentinel grep.
+
+## Config write contract (`POST /api/config`)
+
+The same-origin endpoint classifies the complete request before reading either
+config file. A key equal to a live `SYNC_REGISTRY` root, or below that root on a
+dot-segment boundary, belongs in the committed `.lisa.config.json`. Exactly
+three console-authorized developer keys belong in the gitignored
+`.lisa.config.local.json`: `atlassian.email`, `intake.assignee`, and
+`playStore.serviceAccountKeyPath`. Every other key — including `tracker`,
+`jira.verified_workflow_hash`, prefix lookalikes, and descendants of a local
+key — is rejected with HTTP 400 before file I/O. Responses contain the
+committed config only, so a local value is never echoed.
+
+Both documents remain strict JSON. Writes first compute the complete prospective
+objects, then apply deterministic non-overlapping `jsonc-parser` syntax-tree
+edits against the original text. Existing values replace only their value-node
+range; removals consume only targeted property runs and required commas; missing
+properties insert at stable object offsets. No edit range includes an unrelated
+property node, so bytes outside the targeted spans retain their hand-authored
+formatting even when one request mixes reconciliation and insertion in both
+files. The project root is canonicalized with `realpath`, and every request holds a
+cross-process lock for that canonical root while it takes bounded regular-file
+snapshots of **both** configs, validates both prospective documents, and
+publishes them. The lock lives in a user-private, repository-external temporary
+directory under a hash of the canonical path, so separate UI processes and
+symlink aliases share one transaction without leaving lock residue in the
+project. The root's canonical path and filesystem identity are revalidated
+before and after snapshots, validation, temporary-file creation, and each
+rename. This deterministically refuses a root or ancestor replacement at every
+available boundary. Node does not expose portable descriptor-relative
+temporary creation or rename, so a same-user process that wins the narrow gap
+between the last identity check and a path-based filesystem call can still
+redirect that call; the endpoint does not claim absolute race closure.
+
+For every routed key, persistence first removes the same dot path from its
+non-owner config and then sets it in the owner config. Removal is exact: a root
+removes its descendants, while a descendant removal retains unrelated siblings.
+That reconciliation prevents a stale local override and keeps local-only values
+out of both the committed file and the response. A scalar or array ancestor
+that prevents exact non-owner cleanup is rejected rather than silently retaining
+an overlay shadow. Invalid UTF-8 or recursively duplicated properties in either
+the request or config files, a surgical render whose reparsed structure differs
+from the prospective object, and a changed existing target with no write bit all
+reject before the first publish. Existing and rendered config images share the
+same 128 KiB bound, checked for both targets before either is published.
+
+Existing permission modes are restored exactly after the temporary write, even
+when umask would narrow a permissive mode such as `0666`; a new local config is
+still `0600`. Semantic no-ops skip replacement. Each changed file is published
+through a durable atomic replacement after its original bytes are rechecked.
+Filesystems do not offer one atomic rename spanning two files, so an I/O failure
+or an external writer arriving between the two final replacements can still
+leave the first target published and the second unchanged. The endpoint reports
+that failure instead of claiming an all-or-nothing cross-file transaction;
+canonical-root locking prevents silent lost updates among endpoint requests.
+
 ## Live status contract
 
 When served by `lisa ui`, the page fetches `GET /api/status` from the same