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

package/CHANGELOG.md

@@ -2,84 +2,63 @@
 
 All notable changes to FlowPilot are documented here.
 
-## [0.5.2] - 2026-08-04
+## [0.6.0-beta.1] - 2026-08-31
 
-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.
+Prerelease — published to the `beta` npm tag only. `latest` stays on `0.5.2`.
 
 ### 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.
+- **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.
+- **`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.
+- **Contract-exclusivity enforcement**: a server-side safety net
+  (`enforceAgentContract`) strips any classic-style mutation fields
+  (`changes`/`newNodes`/`newWires`/`removeNodes`/`newGroups`) 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.
+- **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.
+
+### Security
+- **API keys are now write-only over HTTP** (previously exposed on
+  `GET`/`POST /flowpilot/settings` — a fork-hygiene regression from the
+  0.5.1 stable line, now ported forward and closed for good). Every
+  provider's `apiKey` is masked to a sentinel or `""` in both responses;
+  the real key never leaves the server. `settings.json` and per-conversation
+  transcripts are now created with `0600` permissions.
+- **Provider-confirmation gate (SSRF mitigation)**: no chat, generate,
+  modify, document, build, agent-step, or model-list request reaches a
+  configured provider's Base URL until that exact URL has passed a real
+  FlowPilot connection check (Pre-flight check / Test Provider). The check
+  itself is blind on failure — a non-provider target's response is never
+  reflected back to the client — so pointing a provider at an unintended
+  internal address yields nothing readable. Confirmation is tied to the
+  exact URL and clears automatically if the Base URL or API key changes.
+  See `dev-docs/decisions/ADR-007-Provider-Confirmation-Gate.md` for the
+  full design.
+- **Audit-trail completeness**: an agent-strategy request whose very first
+  model turn is a tool call (rather than a later continuation) is now
+  always recorded to the audit log — previously this specific case left no
+  trace at all.
 
-### Fixed
-- **Build loop — status-only evidence false negatives**: a live, working
-  node could be declared "disconnected"/broken off a single coarse
-  node-status read, with no way to confirm otherwise. Evidence is now
-  tagged by source (`debug` vs. `status`); when only status-line evidence
-  is available and it doesn't clearly prove success or failure, the build
-  loop asks a direct yes/no confirmation instead of guessing.
-- **Modify's wire verification** read a node's stale `.wires` array
-  instead of the live link registry — a wire added earlier in the same
-  editing session could be reported as "did not land" even though it was
-  actually there. Verification now reads from `RED.nodes.eachLink`.
-- **Phantom output port on newly-created nodes**: a model-supplied
-  `wires` array that disagreed with a node type's real port count (e.g.
-  a stray empty port on a 0-output type like `http response`) rendered a
-  visible port anchor that shouldn't exist. The array length is now
-  reconciled against the node's real output count on insertion.
-- **New-node layout scatter**: the collision-avoidance grid still placed
-  two nodes at the same vertical level; switched to a single-column
-  layout (one node per row, wrap to a new column after 5 rows).
-- **`newWires` endpoint aliases**: a model response using `fromId`/`toId`
-  instead of `from`/`to` on a `newWires` entry is now repaired
-  automatically instead of both endpoints silently appearing missing.
-- **`.fp-chip-card-alt` background**: the secondary "Just add to canvas"
-  chip relied on its surrounding message bubble being dark to read as
-  part of the same chip-card family as the primary action above it —
-  bubbles follow Node-RED's light editor theme by default, so it rendered
-  as a plain white box instead.
-- 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.
+### Internal
+- Phase 10: strategy propagation, contract-exclusivity enforcement, agent
+  turn output caps, run identity/idempotency, and verification consolidation
+  across the classic and agentic Modify paths. Full history in
+  `dev-docs/current/Phase10-Build-Progress.md` and
+  `dev-docs/current/Phase10-Gate-Closeout-Final.md`.
 
 ## [0.5.1] - 2026-07-24
 

package/USER-GUIDE.md

@@ -134,7 +134,11 @@ OpenAI-compatible endpoint), LM Studio, etc.
 ![Provider settings: Base URL, API key, model, and temperature fields](https://github.com/manny-est/flowpilot/releases/download/v0.2.1/sidebar-settings-providers.png)
 
 4. Click **Pre-flight check**. This saves your settings and sends a small
-   test request. A reply in the chat panel means you're connected.
+   test request. A reply in the chat panel means you're connected. **This
+   step is required** — a provider must pass Pre-flight check before Chat,
+   Generate, Modify, Document, or Build will send it anything; a provider
+   you just added or just changed the Base URL/API key on starts
+   unconfirmed until this check passes again.
 
 ![A successful Pre-flight check reply in Chat](https://github.com/manny-est/flowpilot/releases/download/v0.2.1/preflight-success.png)
 

package/flowpilot-core.css

@@ -249,7 +249,7 @@
     padding: 4px 0;
 }
 
-.fp-typing span:not(.fp-typing-label) {
+.fp-typing span:not(.fp-typing-label):not(.fp-typing-elapsed) {
     width: 7px;
     height: 7px;
     border-radius: 50%;
@@ -258,8 +258,15 @@
     animation: fp-bounce 1.2s infinite ease-in-out;
 }
 
-.fp-typing span:nth-child(2) { animation-delay: 0.18s; }
-.fp-typing span:nth-child(3) { animation-delay: 0.36s; }
+/* CLAUDE-033: matches the base rule's :not() clauses too, so specificity
+   (0,4,1) beats the base rule's (0,3,1) — otherwise the base rule's
+   "animation" SHORTHAND implicitly resets animation-delay back to 0s on
+   every dot regardless of source order, since shorthand properties reset
+   unspecified sub-values, and CSS resolves same-property conflicts by
+   specificity first. Without this, all three dots silently bounce in
+   perfect sync instead of staggered. */
+.fp-typing span:not(.fp-typing-label):not(.fp-typing-elapsed):nth-child(2) { animation-delay: 0.18s; }
+.fp-typing span:not(.fp-typing-label):not(.fp-typing-elapsed):nth-child(3) { animation-delay: 0.36s; }
 
 .fp-typing-label {
     font-size: 11px;
@@ -268,6 +275,12 @@
     align-self: center;
 }
 
+.fp-typing-elapsed {
+    font-size: 11px;
+    color: var(--red-ui-secondary-text-color, #999);
+    align-self: center;
+}
+
 .fp-agent-stop {
     margin-left: 8px;
     align-self: center;
@@ -371,15 +384,11 @@
     font-size: 16px;
 }
 
-/* Secondary/escape-hatch variant: muted dark background, muted text.
+/* Secondary/escape-hatch variant: transparent background, muted text.
    Same hover glow as fp-chip-card so it reads as part of the same family
-   without competing visually with the primary action above it. Explicit
-   background, not transparent — .fp-message's surrounding bubble follows
-   Node-RED's light editor theme variable by default, so "transparent"
-   showed through as plain white instead of blending into a dark parent
-   that doesn't actually exist. */
+   without competing visually with the primary action above it. */
 .fp-chip-card.fp-chip-card-alt {
-    background: #171e25;
+    background: transparent;
     border-color: #2a333c;
     color: #8a96a3;
 }
@@ -388,6 +397,14 @@
     font-weight: 500;
 }
 .fp-chip-card.fp-chip-card-alt:hover {
+    /* CLAUDE-031: this variant's background stays transparent at rest by
+       design, so on Node-RED's LIGHT theme it inherits a white/near-white
+       surrounding background — the near-white hover text below then had
+       nothing dark to sit on and became unreadable. A solid dark fill on
+       hover (paired with the same green glow as the primary chip) fixes
+       contrast regardless of the surrounding theme, without touching the
+       transparent, theme-following look at rest. */
+    background: #141a21;
     border-color: #46d39a;
     box-shadow: inset 0 1px 0 rgba(255, 255, 255, 0.05), 0 0 0 1px #46d39a, 0 0 14px -2px #46d39a;
     color: #dfe6ee;
@@ -722,6 +739,17 @@
 .fp-todo-item-done    { color: #1a7a1a; }
 .fp-todo-item-failed  { color: #b22222; }
 
+/* P10-D2: honest-interruption notice appended inside a "todo" record whose
+   last run event isn't "done" (see rerenderTodoRecord, modes.js). */
+.fp-todo-interrupted {
+    margin-top: 6px;
+    padding: 4px 8px;
+    border-radius: 4px;
+    font-size: 12px;
+    background: rgba(200, 140, 0, 0.10);
+    color: #8a5a00;
+}
+
 .fp-json-toolbar {
     display: flex;
     justify-content: flex-end;