@com55/node-red-ai-access 0.2.0-beta.8 → 0.2.0-beta.9

package/CHANGELOG.md

@@ -6,6 +6,28 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.2.0-beta.9] - 2026-11-02
+
+- Redesign the dashboard with a GitHub-Settings-style grouped left sidebar and
+  inline SVG icons. Show one section at a time with hash routing and browser
+  back/forward navigation, single-column rows, a 1200px container and a narrow
+  top menu. Improve current-page semantics, group labels and heading focus
+  (#110).
+- Harden the approval queue against deployments that finish after the
+  five-minute cap. Block approvals with `deploy_outcome_unknown` until
+  settlement, restart or an attempt-matched "Confirm live checked", unless an
+  audited override is used; allow rejection with a warning. Audit late
+  overwrites across tabs, alert on affected later decisions, show a dashboard
+  banner and mark proposals that landed after withdrawal (#111).
+- Keep `outputs`, `wires` and switch `rules` coupled during rebase for every
+  node type. Preserve the owner acknowledgement flag when an unchanged
+  replacement body still differs from base (#111).
+- Fix OpenAPI loading in the CommonJS build with `import.meta` shims and an
+  `__dirname` fallback (#111).
+- Reuse production builds in tests through a content-hash build stamp, with
+  `SKIP_TEST_BUILD=1` support (#111). Exclude `dist/.production-build-hash` from
+  the npm package.
+
 ## [0.2.0-beta.8] - 2026-10-29
 
 - Proposal review shows human conflict reasons and Base / Live / Proposed field

package/README.md

@@ -418,22 +418,28 @@ minute hard cap is reached. Before the cap, a late success marks the proposal
 approved with its `resultRev`; a late failure clears `deployPending` and keeps
 it pending for retry. At the cap the queue and proposal lock are released,
 `deployPending.queueReleased` becomes true, and the card asks reviewers to check
-the live flow before approving again. Later runtime settlement leaves this
-unknown-outcome record unchanged. Every subsequent approval re-reads live flows
-before rebasing and deploying, recognizing already-applied results. Queued
-approvals time out after 60 seconds with **504** `approve_queue_timeout` without
-deploying. Queued proposals can still be rejected or withdrawn; their approvals
-then return `proposal_not_pending` when dequeued. These three deadlines are
-configurable in `settings.js` under `aiAccess` (positive milliseconds; invalid
-values use the defaults shown above). When choosing **proposed** during conflict
-resolution, unchanged secret spans keep their live editor values. If spans
-cannot be aligned safely, proposed values are retained with a
-`secret_may_revert` warning on the dashboard card. Deliberately deleted secret
-spans do not raise this warning. Deleting one of several identical secret lines
-while their live values changed keeps the proposal in conflict; resolve that
-field against the live flow or choose **live**. Changed env arrays with
-duplicate names show `duplicate_env_keys`, since pairing by name is ambiguous
-when entries are reordered.
+the live flow before approving again. Approvals remain blocked until settlement
+or a matching confirm-live-checked action, unless explicitly overridden with an
+audit entry. Late settlement clears the matching unknown-outcome record. A late
+deploy that changes other tabs writes a warning and a `late_deploy_overwrite`
+audit entry, even when only editor changes were overwritten. Closed proposals
+are alerted only if their decision changed after the cap snapshot. A withdrawn
+proposal keeps its decision and shows “Landed after withdraw” if its deploy
+lands. Every subsequent approval re-reads live flows before rebasing and
+deploying, recognizing already-applied results. Queued approvals time out after
+60 seconds with **504** `approve_queue_timeout` without deploying. Queued
+proposals can still be rejected or withdrawn; their approvals then return
+`proposal_not_pending` when dequeued. These three deadlines are configurable in
+`settings.js` under `aiAccess` (positive milliseconds; invalid values use the
+defaults shown above). When choosing **proposed** during conflict resolution,
+unchanged secret spans keep their live editor values. If spans cannot be aligned
+safely, proposed values are retained with a `secret_may_revert` warning on the
+dashboard card. Deliberately deleted secret spans do not raise this warning.
+Deleting one of several identical secret lines while their live values changed
+keeps the proposal in conflict; resolve that field against the live flow or
+choose **live**. Changed env arrays with duplicate names show
+`duplicate_env_keys`, since pairing by name is ambiguous when entries are
+reordered.
 
 Open proposals merge changes per node and tab field. Different fields on the
 same node merge automatically; changes to the same field conflict even when both

package/ai-access.html

@@ -14,7 +14,7 @@
     }
     window.__com55AiAccessSidebarLoading = true;
 
-    var EDITOR_SIDEBAR_ASSET_VERSION = '0.2.0-beta.8';
+    var EDITOR_SIDEBAR_ASSET_VERSION = '0.2.0-beta.9';
     var root = (RED.settings.httpAdminRoot || '/').replace(/\/$/, '');
     var src =
       (root || '') +