@codyswann/lisa 4.17.18 → 4.18.0

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "4.17.18",
+  "version": "4.18.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.18",
+  "version": "4.18.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.18",
+  "version": "4.18.0",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/typescript/copy-overwrite/scripts/check-skipped-required-checks.mjs

@@ -2164,10 +2164,12 @@ function main(argv) {
   };
   const blocking = result.violations.filter(blocks);
   const refusal = result.vacuity?.refusal ?? null;
+  const refusalBlocks =
+    refusal !== null && (!warnOnly || requireReviewEvidence);
   const failed =
     blocking.length > 0 ||
     (!result.trust.trusted && !warnOnly) ||
-    (refusal !== null && (!warnOnly || requireReviewEvidence));
+    refusalBlocks;
 
   if (argv.includes("--json")) {
     process.stdout.write(
@@ -2221,11 +2223,16 @@ function main(argv) {
       ""
     );
     process.stderr.write(
-      `::${warnOnly ? "warning" : "error"} title=${refusal.kind}::${refusal.reason.split("\n")[0]}\n`
+      `::${refusalBlocks ? "error" : "warning"} title=${refusal.kind}::${refusal.reason.split("\n")[0]}\n`
     );
   }
 
-  if (result.violations.length === 0) {
+  if (refusal !== null && result.violations.length === 0) {
+    // NOT INSPECTED is the whole verdict for this arm. Neither a clean summary
+    // nor a vacuity-violation summary may contradict a result that examined
+    // nothing. Independent offline violations still render below: a refused
+    // evidence read cannot erase what the skip declaration already proved.
+  } else if (result.violations.length === 0) {
     if (result.trust.trusted) {
       lines.push(
         `✅ ${result.checked} \`skip_jobs\` token(s) examined; none silences a ruleset-required status check.`,

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,61 @@ live config it falls back to Lisa's shipped defaults:
 open ui/index.html
 ```
 
+## 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