vinta-ai-workflows 0.7.0-alpha11 → 0.7.0-alpha13

package/CHANGELOG.md

@@ -7,6 +7,8 @@ the project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [0.7.0] — YYYY-MM-DD
 
+<!-- pre-release: 0.7.0-alpha13 on 2026-09-16 -->
+<!-- pre-release: 0.7.0-alpha12 on 2026-09-15 -->
 <!-- pre-release: 0.7.0-alpha11 on 2026-09-15 -->
 <!-- pre-release: 0.7.0-alpha10 on 2026-09-15 -->
 <!-- pre-release: 0.7.0-alpha9 on 2026-09-14 -->
@@ -281,6 +283,28 @@ the project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
   **generated** from a zod source rather than hand-written — see
   [`schemas/README.md`](schemas/README.md).
 
+- **The monitor keeps thinking when you look away, and thinks out loud.**
+  Asking used to be one long HTTP request that produced the whole answer inside
+  it, which made the turn's lifetime the browser's connection: switching view,
+  reloading or letting a laptop sleep killed the monitor mid-thought and left a
+  question with no answer and no record that one had been attempted. The daemon
+  owns the turn now — `POST` answers `202`, and the monitor journals each
+  thought and each sentence as it produces them, so the conversation is
+  readable while it is being written and by any tab that opens it. The panel
+  renders through the same rows a phase's transcript uses, which is what the
+  API always claimed and the UI never did.
+
+- **A phase's transcript says which agent wrote each line, and holds the gates.**
+  Every spawn on a node appends to one file whatever its role, so a phase that
+  took two fix rounds held five agents' output in one undifferentiated stream —
+  the role was in scope at the append and simply not written down. Each line now
+  carries the role and the session slot that produced it, the view bands the
+  list where one agent stops and the next starts, and gate runs are entries in
+  it rather than only in a log beside it. The operator's own steering stays the
+  operator's (§7), even though the adapter echoes it back on the agent's event
+  stream. Transcripts written before this render exactly as they did, with no
+  bands.
+
 ### Changed
 
 - **Phase branches base on their dependencies, not on the previous phase.** A phase
@@ -319,8 +343,97 @@ the project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
   `plan/{plan-id}/lane-{phase-id}` branches, merged `--no-ff` into the single plan
   branch at each wave boundary, so the unit commits survive.
 
+- **`project.prepare_cmd`, for the shared servers a run depends on.** A project
+  whose databases are `delivery: external` and whose services point at one Redis
+  has no long-lived containers of its own — the shape these fields recommend —
+  and that makes some *other* stack a hard dependency of every run. Nothing in
+  the package could bring it up. `setup_cmd` looks like the place and is not: it
+  runs per lane, long after the template database was created on a server that
+  had to be up for `createdb` to work at all.
+
+  It runs in the repository root **before anything else a run does** — before
+  the preflight, before the templates, before the first worktree — and again
+  before every lane recycle, so a server that dies mid-run is restored at the
+  next hand-off rather than failing every phase after it. Failure aborts with
+  the exit code and a bounded stderr tail, and says what the failure means
+  rather than only that a command exited. It must be idempotent, and `--wait`
+  is only as good as the `healthcheck` a service declares: without one, compose
+  returns as soon as the container starts and `createdb` races the server.
+
 ### Fixed
 
+- **The monitor's conversation could never be written on Windows.** It is kept
+  under a reserved node id that becomes a directory, and that id was
+  `monitor:conversation` — a colon, chosen because no phase id may contain one,
+  and the drive separator on Windows. `mkdir` failed with `ENOENT`, so every
+  question threw on its first append and the endpoint reported the monitor
+  unavailable. A colon is legal in a macOS or Linux filename, which is why no
+  machine the feature was built on ever saw it. The id is now
+  `_monitor-conversation`: still unrepresentable as a phase id, and legal
+  everywhere. Conversations recorded under the old id are not migrated.
+
+- **An implementer was told both to commit and never to commit.** The prompt
+  carried "never commit while a gate is red" beside "the turn is not complete
+  until `git status --porcelain` is empty of your work" — a contradiction
+  whenever the gate could not be turned green inside the turn, which is most of
+  why fix rounds exist. Agents obeyed the `never`, and the reviewer one node
+  later raised the BLOCKER it is told to raise for uncommitted work, spending a
+  fix round re-implementing code that was already on disk. A red gate now
+  changes the report and never the decision to commit: commit, and report
+  FAILURE saying what is still red.
+
+  The reviewer's side was a false BLOCKER independently of that. Any unclean
+  tree was a finding, and a lane's tree is never clean — the pool copies
+  configuration in, links dependency trees, and the gates leave build output
+  behind, none of which the implementer is allowed to stage. It is scoped to
+  the failure it was written for now: work that is in the tree and missing from
+  the diff.
+- **A live transcript stops following at entry sixty.** The effect that kept the
+  box on the newest row was keyed on how many rows were *shown*, which is
+  `min(entries, window)` — so it stopped changing the moment a transcript
+  outgrew one window, and the following died silently and permanently, including
+  after the operator scrolled back to the bottom to ask for it. Which is roughly
+  minute two of any real phase. It follows on the entry count now, growing the
+  window keeps the reader on the row they were reading instead of teleporting
+  them, and a **Jump to latest** button says so out loud rather than leaving a
+  60px band at the bottom of a scroller as the only way back in.
+
+- **The transcript spends its space on the noisiest rows.** An agent's answer,
+  its private reasoning and four hundred characters of tool-call JSON all
+  rendered as the same two lines at the same weight. Thinking is now small and
+  quiet, and a streamed thought is one row rather than the dozen events it
+  arrived as; tool calls and their results fold to the argument that says what
+  they did — a command, a path — and open individually or a whole kind at a time
+  from the panel header. Prose is untouched and never folds.
+
+- **A panel's expand control did nothing on the node view.** It expanded by
+  taking `col-span-full`, which on the run view bought a strip a third wider and
+  on the node view matched nothing at all — those panels sit in a flex column,
+  not a grid, so the only thing the button changed was the height of the
+  scroller inside it. It now opens the panel over the whole page through a
+  portal, so no scrolling ancestor can clip it, with Escape to leave and the
+  page behind it held still. A transcript that was following stays on its newest
+  row across the change.
+
+- **`doctor` checks that the shared servers answer.** It verified that binaries
+  existed and disk fitted, and never looked at a `server_url` — so a project
+  whose Postgres lives in another checkout's compose stack passed the preflight
+  with that stack down and died on the first `createdb`, before a worktree
+  existed. Each external database's server and each service URL is now probed
+  with a TCP connect, and a failure names the address that did not answer. A
+  compose-delivered database is deliberately not probed: the lane starts it.
+
+  The order matters as much as the check. `prepare_cmd` runs *before* the
+  preflight, so the check reports the world that hook just made rather than the
+  one in front of it.
+
+- **A service's `create_cmd` runs with the lane's environment.** `reset_cmd`
+  always had it and `create_cmd` did not, so a `create_cmd` that reached for
+  `docker compose` ran against the lane's own compose file with no project name
+  and no override — booting a stack on the project's fixed host ports, which is
+  the collision the override exists to prevent, caused by the step that sets a
+  lane up.
+
 - **`vinta-ai-maestro with` waits for the lock instead of giving up on it.** Its
   usage said it blocked until the resource was granted, and it did — for about
   five minutes, which is where Node's own `fetch` stops waiting for a response.
@@ -1141,7 +1254,6 @@ the project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
   **Consumers**: re-sync to pick up the opt-in questions. E2E-disabled projects
   are unaffected (the e2e regions strip out as before).
 
-
 <!-- pre-release: 0.2.0-alpha6 on 2026-07-13 -->
 
 ### Changed
@@ -1178,7 +1290,6 @@ the project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ### Added
 
-
 - **`handoff` foundation skill — session-continuation handoff docs between
   agents.** Write mode captures the current task (goal, verified-vs-unverified
   state, decisions + rejected alternatives, landmines, single concrete next

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vinta-ai-workflows",
-  "version": "0.7.0-alpha11",
+  "version": "0.7.0-alpha13",
   "description": "Bootstrap AI tooling (AGENTS.md, skills, sub-agents) across Claude Code, Codex, Cursor, and VS Code + GitHub Copilot.",
   "type": "module",
   "bin": {

package/schemas/workflow.v1.schema.json

@@ -331,6 +331,11 @@
           "additionalProperties": false,
           "description": "How a lane’s compose stack is isolated past `COMPOSE_PROJECT_NAME`."
         },
+        "prepare_cmd": {
+          "description": "Run in the repository root **before anything else a run does** — before the preflight, before the template databases, before the first worktree. Its job is to make the shared servers this project’s lanes connect to reachable: `docker compose up -d --wait db redis` for a stack in the root checkout, `brew services start postgresql` for a host install, nothing at all for a project whose lanes boot their own. `setup_cmd` cannot do this — it runs per lane, long after the template database has been created on a server that had to be up already. MUST be idempotent: it runs again before every lane recycle, which is what restores a server that died mid-run. Note that `--wait` only waits for services that declare a `healthcheck`; without one it returns as soon as the container is started, and `createdb` races the server.",
+          "type": "string",
+          "minLength": 1
+        },
         "setup_cmd": {
           "description": "The project’s own lane-setup command, run inside each freshly provisioned lane with that lane’s environment applied. The escape hatch for whatever a project needs that no field here describes. It MUST be idempotent: it runs again every time the lane is recycled for another phase.",
           "type": "string",