@manny-est/node-red-flowpilot 0.6.0-beta.1 → 0.6.1

package/CHANGELOG.md

@@ -2,34 +2,87 @@
 
 All notable changes to FlowPilot are documented here.
 
-## [0.6.0-beta.1] - 2026-08-31
+## [0.6.1] - 2026-09-02
 
-Prerelease — published to the `beta` npm tag only. `latest` stays on `0.5.2`.
+### Fixed
+- **Deterministic run summaries actually work now.** 0.6.0 shipped this
+  feature — the per-item ✓/✗ outcome from a Modify or Generate run,
+  built from what the WRITE tools actually reported instead of the
+  model's own retelling — but a control-flow bug in the message-
+  rendering path made it unreachable for every real run: the code path
+  that shows the deterministic summary as primary (with the model's
+  own explanation demoted underneath) never executed. Every response
+  fell through to showing the model's own prose at full weight
+  instead, exactly the narrative-accuracy gap this feature exists to
+  close. Found and fixed during this release's own go-live testing,
+  now live-verified against a real agentic write.
+- **Installed-package awareness was silently non-functional — FlowPilot
+  now actually receives your palette.** The feature that keeps
+  Generate/Modify from proposing node types you don't have, and lets
+  FlowPilot correctly answer "is X installed?", called a Node-RED API
+  that doesn't exist on this version's plugin interface. The call was
+  a silent no-op on every single request: FlowPilot never had real
+  palette information to work with, so the model either said as much
+  or, in some cases, guessed. This wasn't a timing bug or a stale
+  cache — the underlying data source itself never worked. Now reads
+  the live node registry directly and is correct immediately, from
+  the very first request after a restart.
+
+## [0.6.0] - 2026-09-01
+
+Promoted from `0.6.0-beta.1` to the stable `latest` npm tag.
 
 ### Added
-- **Agentic WRITE-tool loop for Modify** (behind the `enableAgentWrite`
-  setting, default off): step-by-step tool calls against the live flow
-  (`apply_step`, `remove_step`, `rename_node`, `group_nodes`), each
-  write-gated by a per-step consent prompt (Proceed / Skip this step) before
-  it touches the canvas. Multi-item requests are tracked and executed as
-  separate, individually-verified steps rather than one all-or-nothing
-  envelope; an injected mid-run failure (e.g. a referenced node no longer
-  exists) fails only that item, with the rest completing normally.
+- **Agentic WRITE-tool loop for Modify and Generate** (behind the
+  `enableAgentWrite` setting, default off): step-by-step tool calls
+  against the live flow (`apply_step`, `remove_step`, `rename_node`,
+  `group_nodes`), each write-gated by a per-step consent prompt (Proceed
+  / Skip this step) before it touches the canvas. Multi-item requests are
+  tracked and executed as separate, individually-verified steps rather
+  than one all-or-nothing envelope; an injected mid-run failure (e.g. a
+  referenced node no longer exists) fails only that item, with the rest
+  completing normally. Generate joined the same agentic runtime Modify
+  already used, closing the last place a mutation could land through the
+  older, less-verified classic JSON path while write-tool mode is on.
 - **`ask_user` clarifying-question tool**: an agent-strategy turn can pause
   mid-run to ask a single focused question (with optional quick-reply
   buttons) instead of guessing, and resumes exactly where it left off once
   answered.
+- **Deterministic run summaries**: when a Modify or Generate run actually
+  applied WRITE-tool steps, the per-item outcome you see (✓ applied and
+  verified / ✗ failed, with why) now comes straight from what the tools
+  actually reported — not from the model's own retelling. The model's own
+  wrap-up explanation still shows, underneath, clearly secondary — useful
+  context, never the thing you have to trust to know what really
+  happened.
 - **Contract-exclusivity enforcement**: a server-side safety net
   (`enforceAgentContract`) strips any classic-style mutation fields
-  (`changes`/`newNodes`/`newWires`/`removeNodes`/`newGroups`) that
+  (`changes`/`newNodes`/`newWires`/`removeNodes`/`newGroups`/`flow`) that
   accidentally appear on an agent-strategy turn with no tool calls, before
   they ever reach the client — the two mutation paths (classic envelope vs.
-  agentic WRITE tools) stay mutually exclusive per turn.
+  agentic WRITE tools) stay mutually exclusive per turn, for every mode
+  that can run agentically.
 - **Run identity and honest interruption**: agent-strategy runs now carry a
   stable run/operation id so a duplicate tool-call delivery (a retry, or the
   model repeating itself) is applied at most once; a run that's stopped or
   hits its step/token ceiling reports an honest "interrupted after N steps"
-  instead of silently truncating.
+  instead of silently truncating. That step-by-step record is also now
+  visible to the server (previously client-side only), the foundation for
+  the deterministic run summaries above.
+
+### Fixed
+- **The FlowPilot sidebar's entire client script was loading twice on
+  every single editor page load** — a packaging issue present since the
+  plugin's first release, only now found and fixed. In practice this
+  meant a page reload silently lost the current conversation (a second,
+  redundant script execution would stomp the first one's restored state)
+  and, more subtly, any other one-time setup code in the client ran
+  twice per load. Reloading the Node-RED editor now correctly picks the
+  conversation back up where you left off.
+- Anthropic (Claude) responses now get the exact same deterministic
+  run-summary and contract-exclusivity treatment as every other
+  provider — verified directly against Claude Sonnet, not just the
+  OpenAI-compatible path.
 
 ### Security
 - **API keys are now write-only over HTTP** (previously exposed on
@@ -60,6 +113,59 @@ Prerelease — published to the `beta` npm tag only. `latest` stays on `0.5.2`.
   `dev-docs/current/Phase10-Build-Progress.md` and
   `dev-docs/current/Phase10-Gate-Closeout-Final.md`.
 
+## [0.5.2] - 2026-08-04
+
+This release continues the 0.5.x line. Phase 10's agentic Modify redesign
+(WRITE-tool loop, per-call consent gates, `ask_user`) is developed
+separately and is not included here — it ships under its own beta line
+until it's ready to replace this one.
+
+### Added
+- **Anthropic provider support**: FlowPilot can now talk directly to the
+  Anthropic API (Claude models) alongside any OpenAI-compatible endpoint.
+  A new Provider Type dropdown in Settings switches between them; message
+  format, tool-call translation, and streaming (SSE) are handled
+  transparently by a dedicated adapter. Leave Base URL blank to use
+  `api.anthropic.com`.
+- **Reasoning model support**: FlowPilot detects reasoning models
+  (Nemotron, DeepSeek, QwQ, and any model returning `reasoning_content` or
+  `<think>` blocks) and shows a live collapsing "Thinking…" block during
+  streaming, or a pre-collapsed one on the agent-loop path.
+- **Auto-preflight on model change**: switching models and sending a
+  message silently probes capabilities first — no more manual "Test
+  Provider" click after every model swap.
+- **`/refresh` command**: re-renders the message panel from the in-memory
+  record store without losing conversation history — restores interactive
+  Apply buttons and review panels that went stale after a long session.
+- **Build loop — consent gates for side-effecting steps, checkpoint
+  questions, context-aware start from a selection, and an explicit
+  done/fail confirmation** instead of silently stopping.
+- **Modify — todo/plan checklist rendering**: multi-item Modify requests
+  now show a checklist that resolves as verification confirms each item
+  landed, instead of a single opaque pass/fail.
+- **Config node support**: config nodes (MQTT brokers, TLS configs, etc.)
+  are now exposed in context and can be created/connected by Modify.
+- **Server-side validator/repair layer**: malformed model output is
+  caught and, where possible, automatically repaired before it reaches
+  the canvas.
+
+### Fixed
+- Redaction round-trip poisoning, token-credential redaction gaps, and
+  several redaction echo/false-positive fixes across Modify and the build
+  loop's review step.
+- Group data corruption from a stray `changes` patch touching a group's
+  membership array directly; mixed-membership group create/extend
+  corruption.
+- Invalid port wiring (wiring to/from a port index that doesn't exist)
+  now guarded instead of silently applied.
+- New-node insertion collision avoidance tuned for faster, more reliable
+  separation on dense flows.
+- Several build-loop review false positives (metadata-field echoes,
+  debug/function/mqtt node misclassification, stale in-progress status
+  read as a real error).
+- Partial id-validation no longer discards an entire valid Modify batch
+  over one bad node id.
+
 ## [0.5.1] - 2026-07-24
 
 ### Added

package/README.md

@@ -26,7 +26,9 @@ installation, the sidebar UI, and a chapter on every feature.
 - **User-initiated only** — FlowPilot never changes your flow without an
   explicit request.
 - **Complete visibility** — every proposed change is shown as a diff/review
-  before anything is applied.
+  before it's applied; in the opt-in agentic mode (below), each step is
+  gated by its own Proceed/Skip prompt instead, so you're still in control
+  of what actually lands on the canvas.
 - **Undo first** — every change goes through Node-RED's native undo
   (Ctrl+Z), including multi-part changes (insertions + rewires + new nodes)
   as a single step.
@@ -73,6 +75,13 @@ See the [User Guide](USER-GUIDE.md#privacy-and-safety) for the full details.
   Document, with a clear notice when older messages are truncated.
 - **Clarifying questions** — if an instruction is too vague to act on
   safely, FlowPilot asks ONE question instead of guessing.
+- **Agentic mode (opt-in, Settings)** — Generate and Modify can work
+  step by step instead of one big review-then-apply diff: each step
+  (insert, rewire, rename, remove, group) lands on the canvas as it's
+  proposed, gated by its own Proceed/Skip consent prompt for anything
+  beyond the safest node types. The summary you see when a run finishes
+  is built from what the tools actually reported happened, not just the
+  model's own retelling — if a step failed or was skipped, it says so.
 - **Streaming replies** — optional SSE streaming for chat responses.
 - **`/build`** — describe a goal and FlowPilot plans it, proposes a first
   flow, then walks an interactive build → deploy → debug → review → fix loop

package/flowpilot-core.css

@@ -108,6 +108,21 @@
     border-color: rgba(80, 130, 255, 0.35);
 }
 
+/* Subordinate to the deterministic run summary above it (C1): same shape,
+   visibly de-emphasized so a model's free-text recap can't be mistaken for
+   the authoritative per-item outcome. */
+.fp-secondary {
+    padding: 8px 14px;
+    background: transparent;
+    border-style: dashed;
+    font-size: 12px;
+    color: var(--red-ui-secondary-text-color, #888);
+}
+
+.fp-secondary .fp-label {
+    opacity: 0.7;
+}
+
 /* Reasoning / thinking block — shown for models that emit reasoning_content
    (e.g. Nemotron, DeepSeek-R1). Sits above the assistant response bubble.
    Expanded while the model thinks; collapses automatically when content starts. */

package/flowpilot-node-entry.js

@@ -0,0 +1,15 @@
+// Node-RED's "nodes" registration entry needs its own .js file, separate
+// from flowpilot.js — Node-RED derives an editor-template path for every
+// declared "nodes" entry by replacing the .js extension with .html
+// (@node-red/registry/lib/loader.js loadNodeConfig: `file.replace(/\.c?js$/,".html")`),
+// with NO awareness of the "plugins" entry that already explicitly declares
+// flowpilot.html. If this entry pointed at flowpilot.js directly, Node-RED
+// would derive "flowpilot.html" as this node's own template, find the real
+// file (same basename), and load its content a SECOND time — the plugin's
+// entire client bundle (flowpilot/core.js and its inline init script)
+// ends up in the editor page twice, executing every module-level
+// side effect (including sessionStorage init) twice per page load.
+// This shim's own basename ("flowpilot-node-entry") has no matching .html,
+// so Node-RED's template lookup misses (ENOENT) and loads no content for
+// it — exactly what a route-registration-only, no-editor-UI node needs.
+module.exports = require("./flowpilot.js");