laracrew 0.2.0 → 0.2.1

package/CHANGELOG.md

@@ -17,6 +17,20 @@ Planned, in order — see `.claude/PLAN.md`:
 - `laracrew run <task>` for one-shot cross-project sequences
 - Background daemon: `up --detach`, `attach`, `status`, `logs -f`
 
+## [0.2.1] — 2026-09-20
+
+### Added
+
+- **A stack builder**, [`docs/stack-builder.html`](docs/stack-builder.html) — a single self-contained
+  page that writes a `stack.yaml` from projects and process commands as you fill them in. It
+  encodes the rules the config resolver enforces, so it catches the mistakes before laracrew does:
+  a service with no command, `stop.artisan` on a service with no project, a `needs:` pointing at
+  nothing, an auto-started service depending on one you have to start by hand, a dependency cycle.
+  It also shows the boot order the `needs:` graph produces, level by level.
+
+  Open it from disk or serve `docs/` with GitHub Pages. It is not part of the npm package — no
+  runtime dependencies, no build step, nothing to install.
+
 ## [0.2.0] — 2026-09-20
 
 Graceful shutdown for any process, not only Laravel queue workers, and a `doctor` that only
@@ -166,7 +180,8 @@ once, from one command.
 - Accepted by the schema but not yet acted on: `watch`, `metrics` (read by `doctor` only), and
   `hooks`. Stack files written today stay valid.
 
-[Unreleased]: https://github.com/vidux/laracrew/compare/v0.2.0...HEAD
+[Unreleased]: https://github.com/vidux/laracrew/compare/v0.2.1...HEAD
+[0.2.1]: https://github.com/vidux/laracrew/compare/v0.2.0...v0.2.1
 [0.2.0]: https://github.com/vidux/laracrew/compare/v0.1.2...v0.2.0
 [0.1.2]: https://github.com/vidux/laracrew/compare/v0.1.1...v0.1.2
 [0.1.1]: https://github.com/vidux/laracrew/releases/tag/v0.1.1

package/README.md

@@ -155,6 +155,11 @@ laracrew doctor dual
 laracrew up dual
 ```
 
+**Prefer not to write YAML by hand?** Open [`docs/stack-builder.html`](docs/stack-builder.html) in
+a browser. Add your projects and the commands that run under them, and it writes the `stack.yaml`
+as you go — checking the same rules laracrew does, so a stack that looks right there boots. No
+install, no build step; it is one file.
+
 ---
 
 ## One command per project set
@@ -575,7 +580,7 @@ project, `LARACREW_PROJECT=<key>`.
 
 ## Status
 
-**v0.2.0 — supervisor and full-screen view are built and tested.**
+**v0.2.1 — supervisor and full-screen view are built and tested.**
 
 Working now: config pipeline, dependency-ordered boot with readiness gates, restart policies with
 exponential backoff, the graceful stop ladder — `stop.exec` for any process, `stop.artisan` as the

package/dist/index.js

@@ -3555,7 +3555,7 @@ ${paint("bold", "TASKS")}`);
 };
 
 // src/cli/program.ts
-var VERSION = true ? "0.2.0" : versionFromPackageJson();
+var VERSION = true ? "0.2.1" : versionFromPackageJson();
 var resolveStackName = (explicit, env = process.env) => {
   if (explicit) return explicit;
   const configured = loadGlobalConfig(env).defaultStack;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "laracrew",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Boot and supervise all the long-running processes of your projects with one command. Laravel-aware, works with anything.",
   "keywords": [
     "laravel",