flow-workflows 0.73.0 → 0.75.0

package/adapters/opencode/commands/flow-work-query.md

@@ -18,6 +18,8 @@ description: Put a data-access query on trial — schema, indexes, execution pla
 
 Read `~/.claude/flow/CORE.opencode.md` first (shared rules: `FLOW.md` step 0, models, autonomy modes and hard gates, how a stop reads, the live panel, `00-summary.md`) — skip if you already read it in this session. **Models: the subagents it launches take `models.agents`; its parallel rounds take `models.workers`.**
 
+**Panel words are closed** — `mark`: `done` · `current` · `pending` · `wait` · `block` · `info`; `style`: `normal` · `dim` · `title` · `accent` · `ok` · `warn` · `error`. Anything else is dropped by the reader in silence: the panel still paints, and nobody is told.
+
 **A query is approved by its plan, not by prose.** Fact sheet → challenger attacks → each point settled with a **plan or a number**. **Cross-cutting** (feat or bug), **repeatable**, does **not** advance `meta.json.phase`; runs with or without a work folder.
 
 Invoked by `/flow-feat-review` and `/flow-bug-review` (duel over the diff), `/flow-work-respond` (a reviewer objected to a query), `/flow-feat-design` (access paths), `/flow-feat-build`, `/flow-feat-validate`. Invoke directly for any doubt outside them (chat question, comment on an open MR/PR, a year-old query).

package/adapters/opencode/commands/flow-work-respond.md

@@ -28,6 +28,8 @@ Extract from `git`: `host`, `cli` (empty → the default for that host), `assign
 
 Read `~/.claude/flow/CORE.opencode.md` first (shared rules: `FLOW.md` step 0, models, autonomy modes and hard gates, how a stop reads, the live panel, `00-summary.md`) — skip if you already read it in this session. **Models: this command runs with the model it was launched with (no `models` key).**
 
+**Panel words are closed** — `mark`: `done` · `current` · `pending` · `wait` · `block` · `info`; `style`: `normal` · `dim` · `title` · `accent` · `ok` · `warn` · `error`. Anything else is dropped by the reader in silence: the panel still paints, and nobody is told.
+
 **Autonomy.** Modes as in flow-core §2 (`autonomy.mode`: `manual` | `guided` | `auto`; empty = `manual`); `guided`/`auto` record their choices in `08-feedback.md`. **Hard gates — ALWAYS stop and ask, in every mode, no exceptions:**
 1. **Posting any comment/reply** to the MR/PR (§7).
 2. **Any push** (§6.2).

package/adapters/opencode/commands/flow-work-resume.md

@@ -18,6 +18,8 @@ description: Resume the work associated with the current branch and suggest the
 
 Read `~/.claude/flow/CORE.opencode.md` first (shared rules: `FLOW.md` step 0, autonomy, how a stop reads, the live panel, `00-summary.md`) — skip if you already read it in this session.
 
+**Panel words are closed** — `mark`: `done` · `current` · `pending` · `wait` · `block` · `info`; `style`: `normal` · `dim` · `title` · `accent` · `ok` · `warn` · `error`. Anything else is dropped by the reader in silence: the panel still paints, and nobody is told.
+
 Use when returning to a work after a break (next morning, another session).
 
 ## 1. Detection

package/adapters/opencode/commands/flow-work-status.md

@@ -18,6 +18,8 @@ description: Summary of all open works in .claude/work/
 
 Read `~/.claude/flow/CORE.opencode.md` first (shared rules: `FLOW.md` step 0, autonomy, how a stop reads, the live panel, `00-summary.md`) — skip if you already read it in this session.
 
+**Panel words are closed** — `mark`: `done` · `current` · `pending` · `wait` · `block` · `info`; `style`: `normal` · `dim` · `title` · `accent` · `ok` · `warn` · `error`. Anything else is dropped by the reader in silence: the panel still paints, and nobody is told.
+
 Overview of works in progress; detects divergences between artifacts and actual git state.
 
 ## 1. List works

package/adapters/opencode/commands/flow-work-try.md

@@ -18,6 +18,8 @@ description: Point the main checkout at a branch to test it (then return), re-sy
 
 Read `~/.claude/flow/CORE.opencode.md` first (shared rules: `FLOW.md` step 0, autonomy, how a stop reads, the live panel, `00-summary.md`) — skip if you already read it in this session.
 
+**Panel words are closed** — `mark`: `done` · `current` · `pending` · `wait` · `block` · `info`; `style`: `normal` · `dim` · `title` · `accent` · `ok` · `warn` · `error`. Anything else is dropped by the reader in silence: the panel still paints, and nobody is told.
+
 Temporarily point the **main checkout** at another branch to test it against this checkout's live environment (running stack, DB, containers), then return — a generic `make wt-try`/`wt-back` pair. The git switch is built in; the project-specific re-sync (e.g. migrations) comes from `git.worktree_resync` in `FLOW.md`. Operates **in place**; never creates or touches worktrees.
 
 ## 1. Parse the argument

package/adapters/opencode/commands/flow-work-watch.md

@@ -18,6 +18,8 @@ description: Monitor the observability platform after a deploy and alert on erro
 
 Read `~/.claude/flow/CORE.opencode.md` first (shared rules: `FLOW.md` step 0, models, autonomy modes and hard gates, how a stop reads, the live panel, `00-summary.md`) — skip if you already read it in this session. **Models: this command runs with the model it was launched with; the wait it delegates takes `models.supervisors`.**
 
+**Panel words are closed** — `mark`: `done` · `current` · `pending` · `wait` · `block` · `info`; `style`: `normal` · `dim` · `title` · `accent` · `ok` · `warn` · `error`. Anything else is dropped by the reader in silence: the panel still paints, and nobody is told.
+
 **Autopiloted post-deploy monitoring**: signals **scoped to the change** over a window (default 30 min), against a baseline; alert on errors or performance regressions from the deploy.
 
 Usage: `/flow-work-watch {PREFIX}XXXXX [duration]` (prefix from `tracker.prefix`; default `30m`).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "flow-workflows",
-  "version": "0.73.0",
+  "version": "0.75.0",
   "description": "Guided feat/bug workflows (start→ship), post-deploy monitoring and multi-agent code review, stack-agnostic. Each repo uses a shared FLOW.md plus optional harness overlay.",
   "type": "module",
   "bin": {

package/plugins/flow/.claude-plugin/plugin.json

@@ -3,7 +3,7 @@
   "name": "flow",
   "displayName": "Flow — guided dev workflows",
   "description": "Guided feat/bug workflows (start→ship), post-deploy monitoring and multi-agent code review, stack-agnostic. Each repo uses a shared FLOW.md plus optional harness overlay.",
-  "version": "0.73.0",
+  "version": "0.75.0",
   "author": {
     "name": "Alberto Vioque",
     "email": "mashware@gmail.com"

package/plugins/flow/CHANGELOG.md

@@ -5,6 +5,51 @@ plugin and is what `/flow:news` reads to show you what changed since your previo
 
 The canonical, richest notes live in the [GitHub Releases](https://github.com/mashware/flow-workflows/releases).
 
+## v0.75.0 — The words the panel understands now travel with every command  ·  2026-09-22
+
+**In short**
+- **Every command carries the panel's vocabulary on its own opening lines**, so an agent whose shared
+  rules were dropped by a context compaction keeps publishing a panel that can still be read.
+- **The panel stops degrading in silence.** The reader discards a word it does not know without
+  saying so, which is why the failure was invisible from the inside.
+- **The release check pins every copy to one constant**: the sentence is built from the vocabulary
+  so the two cannot disagree, a locally edited copy fails, a new command without the line fails, and
+  a trigger that stops matching any file fails instead of going quietly green.
+
+`flow-core` is read once per session. A compaction drops it, and from that moment the agent publishes
+panels from memory — observed on 22 September: correct panels for thirty minutes, a compaction, then
+four lines carrying the invented mark `doing`, and a panel that had become a paragraph of grey text
+next to a pane whose panel was still laid out in full. Nobody was told, because an unknown word is
+dropped by design.
+
+The fix is one frozen sentence in all 24 command files, on the line after the one that loads the
+skill — **not** at the points that order a publication: `build`, `review` and `validate` order none of
+their own, and they are exactly the long phases where the failure was seen. `check_panel_reminder`
+keeps the copies honest: every copy must be byte-identical to the constant, every file that loads the
+skill must carry one — so the twenty-fifth command is caught the day it is added rather than by a
+count nobody updated — and the check fails if its own trigger ever matches no file at all, which is
+how a guard retires without telling anyone.
+
+`docs/DESIGN.md` records the boundary this draws against the rule that removed eighteen hand copies of
+a shared preamble: prose that can be reworded lives once; a closed enumeration may be repeated, if and
+only if a check pins every copy to one constant.
+
+## v0.74.0 — The thing you were asked to approve was the thing the terminal hid  ·  2026-09-22
+
+**In short**
+- **What a gate asks about now travels with the question** — the brief, the MR/PR body, the plan — so it is read in the prompt being answered instead of by opening the artifact in an editor.
+- **Nothing runs between showing it and asking.** A tool call right after is what lets a terminal collapse that message into one line, and the line it collapses is exactly the one the user needed.
+- Applied at the two briefs (`feat:build`, `bug:fix`) and at the MR/PR preview, the three gates that exist to catch scope before there is a diff to argue with.
+
+The rule already said to print the brief and then ask. It never said what had to sit between them,
+so a status line, a file write or a `git` call landed in the middle — and a chat UI that folds a
+message once a tool call follows it turned a nine-line brief into "· summarized". What reached the
+user was a one-line paraphrase above a Yes/No, and the honest way to answer it was to open
+`05-implementation.md` and read the brief there, which is the cost the gate exists to avoid.
+
+Where a harness's question cannot hold the content, it is printed as the **last** thing before
+asking, with the tool calls already done.
+
 ## v0.73.0 — The panel kept asking what you had already answered  ·  2026-09-22
 
 **In short**