vinta-ai-workflows 0.7.0-alpha12 → 0.7.0-alpha13

package/CHANGELOG.md

@@ -7,6 +7,7 @@ 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 -->
@@ -282,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
@@ -339,6 +362,59 @@ the project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ### 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
@@ -1178,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
@@ -1215,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-alpha12",
+  "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": {