space-architect 3.0.0 → 5.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 135a6282cfe3e3073265b71867e7d228673cbfb9b7253feaaba5ad67a180b7cb
-  data.tar.gz: 0d0406a99feadadebb24a6167c11837de25bede933e752ef6507524208f4e5a7
+  metadata.gz: 6846eab011f92f0b54a7bb886d7b97cf8c727beb3fc6d279a2db603062645520
+  data.tar.gz: 0bc8f0b22f785fd2d3ed77419a1ad3b6058e4b76a6aaee41b7a66793b865702a
 SHA512:
-  metadata.gz: c8b161eff4f4b5a788c2e3c9b423bcc31a495915a076afb70445f6b0cdaf1cc2573ee381ce0c3e09ca712a8398b70ca091b015260b6b4e9c24914ece4a0f5539
-  data.tar.gz: f61cdd897881530ad2e81df5bd846c4e644fb85ac6847c4afd147e643b6045b59c7ecb89fd12b83f9a7b5c2ef12813c5e88e7634449a919aac2e4bc75052a6b0
+  metadata.gz: 77216fd23779d4ee5ae16f3c141fc9f7670b3efc3c8b7fe31292c31284be0903616505c4199fbe4e5d7b12988d0638e7a31cba600a4625caad2b939255fc9370
+  data.tar.gz: ca1fb9e9bd1c20c6ef201d60f763cdcb87b18b9c289169ff601be6c858b0558f283986b2b24bb82cf73b4b1001c3ce0a9955bd02675557548fcc2e930aea27d2

data/CHANGELOG.md

@@ -5,6 +5,92 @@ All notable changes to this project are documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [5.0.0] - 2026-07-06
+
+### Added
+
+- **`architect dispatch --prompt <file>`** — the lane prompt is authored anywhere
+  (a fresh scratch file) and dispatch copies it byte-for-byte to the canonical
+  `build/<id>-<lane>/prompt.md` before launch, announcing the copy. The CLI owns
+  the canonical path; the architect never blind-writes it (#48, #42).
+- **`architect brief new --from <file>` / `--stdin`** — write the authored brief
+  in one step instead of filling a pre-seeded template. Bare `brief new` still
+  scaffolds the placeholder, and now says so
+  (`Brief ready: … (template — Read it before editing)`).
+- **Flexible commit messages on every committing loop command** — `init`, `new`,
+  `freeze`, `brief new`, `section`, `verdict`, `evidence`, `merge`, and
+  `integrate` all take `-m`/`--message` and `--message-from <file>`. The first
+  line completes the subject after a short canonical prefix (`I01 spec: <your
+  subject>`, `lane <lane>: <your subject>`); remaining lines become the commit
+  body. Without the flags, the canonical messages are unchanged. The space's git
+  log is the loop's durable memory — detailed bodies are the point.
+
+### Changed
+
+- **`worktree add`/`provision` no longer pre-seed `prompt.md` with a placeholder
+  stub.** The unannounced stub made the architect's first `Write` trip the
+  harness read-before-write guard on every single lane (a failed-write → read →
+  rewrite round trip; 40 occurrences mined from real transcripts). Dispatch
+  still refuses a missing, empty, or legacy-stub prompt (#48, #42).
+- **`architect merge --message` semantics** — the message now composes with the
+  canonical `lane <lane>:` prefix (subject + body) instead of replacing the
+  whole message, matching every other committing command.
+- **Skill prose** — the architect authors all content (lane prompts, brief, PR
+  bodies) in fresh timestamped scratch files and hands them to the CLI via
+  `--from`/`--prompt`; PR bodies land at
+  `build/land/<repo>-pr-body-<yyyymmdd-hhmm>.md`; committing commands should
+  carry detailed `--message-from` bodies.
+
+## [4.0.0] - 2026-07-05
+
+Backfilled — the bump shipped without an entry. Five iterations run through the
+Architect Loop against `space-architect`'s own live-loop papercuts (#46), plus
+the `dispatched_at` producer (#45) and a test-suite hygiene pass (#32).
+
+### Added
+
+- **`architect provision <iteration> [--base <ref>] [--lane <name>]`** — materializes
+  every declared lane's worktree + `lane/<id>-<lane>` branch in one shot from the
+  frozen lane plan (idempotent; base resolves `--base`, else `project/<slug>` HEAD,
+  else the repo's default branch). `dispatch`/`integrate`/`gate`/`verify`
+  auto-materialize a missing worktree from the frozen declaration, so the flow
+  can't dead-end (#26).
+- **Fenced ` ```lanes ` block in the Specification** — `name`, `repo`, `touch`
+  globs, parsed at **freeze** into `space.yaml` lane entries, making the lane plan
+  (including the out-of-bounds touch-set contract) part of the frozen spec (#26).
+- **`space.yaml` schema v2** — the never-bumped `version` key now means something:
+  canonicalize on save, read + self-heal the two known v1 variants (v1a
+  `architect:`, v1b `project:`+`version: 1`) on load; a both-keys conflict refuses
+  and names both blocks rather than silently picking one (#33).
+- **`dispatched_at` on lane entries** — every dispatch stamps an ISO 8601 launch
+  time after preflight, before the run, on both foreground and detached paths
+  (#18, producer landed via #45).
+- **Self-verifying dispatch liveness** — a transient fiber inside dispatch checks
+  the launched run matches intent (model, growth of `run.jsonl`), retiring the
+  manual "canary" ceremony (#43, #44).
+- **`architect help` grouped by loop phase** — Spec / Build / Judge / Land /
+  Project, commands in loop order, with an embedded loop-status block when run
+  inside a project space; `space status` reports on a bare call and still sets on
+  `space status <value>`.
+
+### Changed
+
+- **Lane declaration is single-source-of-truth** — lanes were declared twice
+  (Specification prose + `worktree add` flags) with the touch-set divorced from
+  the frozen spec; the ` ```lanes ` block at freeze is now the one declaration.
+  The single-lane "dispatch in the repo checkout" fast path is removed (it never
+  worked with `merge_lane!`); manual `worktree add` remains as the internal
+  primitive `provision` wraps (#26).
+- **Skill prose** (`SKILL.md` §4–§6, `dispatch.md`) rewritten to the
+  declare → freeze → provision → dispatch lane lifecycle.
+
+### Fixed
+
+- **`architect integrate <it> --teardown`** (no `--lanes`) backtraced; teardown-only
+  mode now deletes per-lane branches and worktrees, never `project/<slug>` or
+  `main` (#30).
+- **Test suite hygiene** — zero warnings, zero stray output, 58.8s → 49.1s (#32).
+
 ## [3.0.0] - 2026-07-01
 
 ### Added

data/README.md

@@ -102,7 +102,9 @@ space show 20260531-name-of-space
 space path 20260531-name-of-space
 space current                                # based on $PWD
 space show                                   # based on $PWD
-space status done                            # based on $PWD
+space status                                 # report: metadata + loop status (based on $PWD)
+space status 20260531-name-of-space          # report another space
+space status done                            # set: active | paused | done | archived
 space status 20260531-name-of-space done
 space config set default_provider github.com
 space config set default_organization example-org
@@ -115,6 +117,12 @@ space use 20260531-name-of-space             # records recent state, prints the
 space ls --color=always                      # auto | always | never (--colors also accepted)
 ```
 
+`space status` is **report-or-set**: with no status keyword (bare, or with just
+a space id) it *reports* the space — its metadata plus a compact loop-status
+block (project status, current iteration, derived state) when the space runs an
+Architect project, quietly omitted otherwise; pass a status keyword (`active`,
+`paused`, `done`, `archived`) to *set* it instead. 🔁
+
 Repos are passed with a repeatable `-r` flag (`-r org/repo -r org/lib`); the
 comma form (`-r a,b`) works too. Space ids are date-prefixed
 (`20260531-name-of-space`) so they sort naturally, and duplicate names on the
@@ -263,8 +271,12 @@ build/
 ```
 
 **Iteration file anatomy** — one file, grown section by section. You author the
-*content*; the CLI owns the *persistence* (each command writes the section,
-commits it with the canonical message, and prints back what changed):
+*content* in fresh scratch files; the CLI owns the *persistence* (each command
+writes the section, commits it, and prints back what changed). Every committing
+command takes `-m`/`--message` and `--message-from <file>` — your first line
+completes the subject after a short canonical prefix (`I01 spec: <subject>`),
+the rest becomes the body. The space's git log is the loop's durable memory:
+write detailed messages.
 
 | Section | Holds | How you persist it |
 |---------|-------|--------------------|
@@ -291,12 +303,12 @@ inside a lane worktree are never grounded.
 
 ```sh
 architect init                              # scaffold ARCHITECT.md + the space.yaml project: block + SessionStart hook
-architect brief new                         # scaffold the durable project BRIEF.md
+architect brief new --from <f>              # write the durable project BRIEF.md (authored in a scratch file)
 architect new <iteration>                   # scaffold architecture/I<NN>-<iteration>.md
-architect section <it> <section> --from <f> # write + commit a section
+architect section <it> <section> --from <f> # write + commit a section (add -m/--message-from for a detailed commit)
 architect freeze <iteration>                # freeze the Acceptance Criteria ❄️
 architect worktree add <repo> <it> <lane>   # isolated worktree per lane (2–4 lanes)
-architect dispatch <it> <lane>              # dispatch a builder (add --detach to survive long runs)
+architect dispatch <it> <lane> --prompt <f> # copy the lane prompt in + dispatch a builder (--detach to survive long runs)
 architect verify <iteration>                # post-flight mechanical checks (reports only)
 architect evidence <it> --lane <lane>       # transcribe the builder's report verbatim
 architect gate <iteration>                  # run the frozen gate commands, stream raw output
@@ -308,14 +320,19 @@ architect variant add|compare|promote …     # competing (harness, model) lanes
 architect research dispatch|status|wait …   # parallel read-only research lanes (see below)
 ```
 
+`architect help` (or bare `architect`, `architect --help`) lists these grouped by
+loop phase — **Spec · Build · Judge · Land · Project · Groups**, in canonical
+order — and, inside an architect space, ends with a compact loop-status block
+(project status + current iteration) so you can see where you are in the loop. 🧭
+
 A typical session:
 
 ```sh
 architect init                                   # first time
 architect new my-feature                         # scaffold I01-my-feature.md
-architect section my-feature specification --from spec.md
+architect section my-feature specification --from spec.md -m "pull-based dispatcher seam"
 architect freeze my-feature                      # lock it ❄️
-architect dispatch my-feature lane-a --detach    # send a builder; poll the report
+architect dispatch my-feature lane-a --prompt tmp/prompts/I01-lane-a.md --detach   # send a builder; poll the report
 architect verify my-feature                      # mechanical post-flight checks
 architect evidence my-feature --lane lane-a      # transcribe raw evidence
 architect gate my-feature                        # run the frozen gates yourself