vinta-ai-workflows 0.7.0-alpha2 → 0.7.0-alpha3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,7 @@ the project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
|
7
7
|
|
|
8
8
|
## [0.7.0] — YYYY-MM-DD
|
|
9
9
|
|
|
10
|
+
<!-- pre-release: 0.7.0-alpha3 on 2026-09-12 -->
|
|
10
11
|
<!-- pre-release: 0.7.0-alpha2 on 2026-09-12 -->
|
|
11
12
|
<!-- pre-release: 0.7.0-alpha1 on 2026-09-11 -->
|
|
12
13
|
|
|
@@ -217,6 +218,27 @@ the project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
|
217
218
|
|
|
218
219
|
### Fixed
|
|
219
220
|
|
|
221
|
+
- **Two diagnostics that named the symptom and hid the cause.** Both came out of
|
|
222
|
+
one real run, and neither was a wrong answer — just an unusable one.
|
|
223
|
+
- **A phase whose plan is not committed** failed with `prompt_ref "…" names no
|
|
224
|
+
readable file`, against a path that was spelled correctly. A lane is a fresh
|
|
225
|
+
worktree of the base branch, so a plan sitting untracked in the operator's
|
|
226
|
+
checkout is in the one place the run cannot look. The message now names the
|
|
227
|
+
directory it resolved against and says why a plan is often not in it.
|
|
228
|
+
- **A lane summary the daemon could not accept** reported `summary unreadable`
|
|
229
|
+
and advised deleting the lane — which takes its forked databases with it,
|
|
230
|
+
over what turned out to be two wrong fields. `doctor` now names the fields
|
|
231
|
+
and what was expected, and offers repair before deletion. A file that does
|
|
232
|
+
not parse at all still reports as unreadable, because there is no field to
|
|
233
|
+
name. Neither message carries the offending *value*: a summary holds
|
|
234
|
+
database names and connection variables, and the value that failed
|
|
235
|
+
validation is the likeliest thing in it to be one.
|
|
236
|
+
|
|
237
|
+
`prepare-worktree` gained the rule that would have prevented the summary in
|
|
238
|
+
the first place — its `|` alternatives are closed sets read by machine, `null`
|
|
239
|
+
is how you say "none", and a strategy outside the set should be the closest
|
|
240
|
+
one plus a `note:` rather than a fourth word.
|
|
241
|
+
|
|
220
242
|
- **`npx vinta-ai-maestro` now runs.** The published package pointed its `bin` at
|
|
221
243
|
`src/cli/bin.ts` and relied on Node stripping the types at startup — which Node
|
|
222
244
|
refuses to do anywhere under `node_modules`, unconditionally and with no flag to
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "vinta-ai-workflows",
|
|
3
|
-
"version": "0.7.0-
|
|
3
|
+
"version": "0.7.0-alpha3",
|
|
4
4
|
"description": "Bootstrap AI tooling (AGENTS.md, skills, sub-agents) across Claude Code, Codex, Cursor, and VS Code + GitHub Copilot.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"packageManager": "pnpm@10.33.0",
|
|
@@ -355,7 +355,7 @@ state:
|
|
|
355
355
|
files: [.env, .envrc, ...]
|
|
356
356
|
dev_db:
|
|
357
357
|
engine: postgres | mysql | sqlite | mongo | redis
|
|
358
|
-
strategy: fork | share | stub
|
|
358
|
+
strategy: fork | share | stub # closed set — see "The summary is read by machine"
|
|
359
359
|
forked_name: <forked db name> # null when share / stub
|
|
360
360
|
connection_url_var: DATABASE_URL
|
|
361
361
|
reset_cmd: <shell command that returns this DB to the state of a fresh checkout>
|
|
@@ -365,7 +365,7 @@ state:
|
|
|
365
365
|
# instead of reusing this worktree across a migration boundary.
|
|
366
366
|
test_db:
|
|
367
367
|
engine: ...
|
|
368
|
-
strategy: fork | share
|
|
368
|
+
strategy: fork | share # closed set, as above
|
|
369
369
|
forked_name: ...
|
|
370
370
|
connection_url_var: TEST_DATABASE_URL
|
|
371
371
|
reset_cmd: <same idea, for the test DB> # null when not resettable
|
|
@@ -467,6 +467,14 @@ Every step gated on user confirmation when the worktree has un-pushed branches.
|
|
|
467
467
|
|
|
468
468
|
- **Symlink for reads, copy for writes, fork for state.** This is the only mental model that scales. Default to fork when unsure — disk is cheap, corrupted main-checkout DBs are not.
|
|
469
469
|
- **Never share a writable DB across worktrees by default.** The race conditions are subtle and the failure mode is silent data corruption.
|
|
470
|
+
### The summary is read by machine
|
|
471
|
+
|
|
472
|
+
This file is not a note to the next human. [vinta-ai-maestro](https://github.com/vintasoftware/vinta-ai-workflows/tree/main/packages/vinta-ai-maestro) parses it to decide whether a lane can be handed to another phase, so **every `|` above is a closed set and every key is required** — `null` is how you say "none", and omitting the key is not the same thing.
|
|
473
|
+
|
|
474
|
+
A value outside the set makes the lane unusable by the daemon. It does not fail loudly at write time; it fails later, as `doctor` reporting the lane and the field it could not accept, long after the worktree and its forked databases exist. Seen in the wild: a `strategy: create-empty-and-migrate` invented to describe a database that had been created empty and migrated by hand, with `reset_cmd` left off entirely. Neither is in the spec, and the pair cost eleven lanes their readability.
|
|
475
|
+
|
|
476
|
+
If none of the listed strategies describes what you did, **the honest record is the closest one plus a `note:`** — the schema keeps `note` free-form for exactly this. A database created empty and migrated is a `fork` whose `reset_cmd` re-runs that same creation; a database you could not provision at all is a `stub`. What it must never be is a fourth word.
|
|
477
|
+
|
|
470
478
|
- **`COMPOSE_PROJECT_NAME` does not isolate `external:`/fixed-`name:` volumes or fixed host ports — always run the [4a](#4a--neutralize-compose-isolation-leaks) generator.** For a compose-delivered DB the data volumes are forked *unconditionally* (independent of `schema_change` and `test_db_strategy`): the worktree runs its own server, and two servers on one volume is corruption. "Share the DB" only ever means share a connection to a single already-running server, never a second server on shared storage. The fix is a generated, out-of-tree override + a `COMPOSE_FILE` line in the copied `.env` — never an edit to any tracked compose file. Verify the volume-differs invariant before declaring the worktree runnable.
|
|
471
479
|
- **Every fork decision lands in `.vinta-ai-workflows/worktrees/<name>.yaml`.** Teardown reads it; humans grep it; agents resuming a stalled plan read it. No decision lives only in conversation memory.
|
|
472
480
|
- **Worktree root governed by runtime conventions.** claude-code uses `.claude/worktrees/`; other harnesses use sibling dirs. Don't fight the harness — match it.
|