space-architect 4.0.0 → 5.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: bb8f902d475bcc8a29e56740ce0c20328935fe05f9d919d38934b2cffd12e966
-  data.tar.gz: e31c5b6f8ad98219c9c4ed22225666900bc7aaf8f43bd929ef32e2d2b5aacdf2
+  metadata.gz: '09d047544f9e1b3a29c56cc1e982a9624f72d45c2198429fcd7ab4564c31da41'
+  data.tar.gz: ea4e880ceda1c31ba11b390448d2380ca6d45d39394aeef2963c80a0e59a0901
 SHA512:
-  metadata.gz: 5cbb47cbacf2231ed09eb74bfb11b80a1a6076bfde1427fe76a19b3581f3b3a8e38db4a6269307e339a022902723d73b1d40dd4b001acd6ffaab624871249d70
-  data.tar.gz: 171913d786d1e166a279f72b184ec7987785d561ec795bfe161db9341502210f6d97166c3eb8b7a097b59adba7e435a575c78ca66488ca482312b4bc7cca7249
+  metadata.gz: 01d09d4cd267afe17f189606d3620bdfa284802c4ccd506a2526172864b85c1124b8096aa3a5ed3fe61cfc3f18929d0aeb8f00d7d9c6238dfdf331ce1e2f8048
+  data.tar.gz: 313a4cf3c9dc69d5cb82d5d8bb1b95fa5d133de711d9ab5e320145525abddff4aebe8fc89cf58e0552d83147fae79ce697b567dce5a8ac387313f5064f58bf2b

data/CHANGELOG.md

@@ -5,6 +5,143 @@ 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.1.0] - 2026-07-19
+
+### Added
+
+- **`architect integrate --into <branch>`** — merge a lane into a named branch
+  instead of the slug-derived `project/<slug>` default (#47). Outside-touch-set
+  conflict message gains an `--into` hint; inside-touch conflict keeps "spec
+  defect".
+- **Conductor commit-mode** — `commit_mode: conductor` in `space.yaml` plus a
+  `--commit-mode` CLI flag on `verify`/`integrate`: canonical conductor commits
+  are classified as non-builder in the lane mechanical check, with canonical
+  message-shape matching (#55).
+- **`architect sync` subcommand** (`--ff-only`, per-repo status) plus a
+  `ground` stale-repo WARNING with behind count and `--into` hint. **No
+  auto-sync** — the operator runs `sync` (#49).
+- **`architect freeze --force` / `section --force`** — re-freeze an iteration
+  whose frozen region changed since the last freeze, or write a frozen section
+  after the freeze (pre-dispatch amend paths). Both refuse if any lane has
+  `dispatched_at` OR `integrate_sha` — moving `freeze_sha` or rewriting a frozen
+  section after a builder has run against the AC breaks the cardinal invariant
+  (AC freeze before results exist; judging quotes the freeze commit). The guard
+  names the offending lane and the reason.
+- **`architect merge --into <branch>` / `--commit-mode <mode>`** — wires the
+  existing `merge_lane!` `into:`/`commit_mode:` kwargs through the `Merge` CLI,
+  matching `Integrate`'s surface.
+- **`architect provision --force` / `worktree add --force`** — `worktree_add`
+  gains a `force: false` kwarg. When a worktree dir exists but is unknown to git
+  (stale, e.g. left by an aborted provision), `force: true` clears it via
+  `FileUtils.rm_rf` and re-creates; without `force` it still raises with a
+  `--force` hint so a genuine git-tracked dir is never silently destroyed.
+  `ensure_lane_materialized` (the auto-recovery path) stays non-force —
+  auto-recovery never silently `rm -rf`s; only an explicit operator `--force`.
+
+### Changed
+
+- **`dir/**` in-bounds touch glob is now recursive** — matches
+  `Dir.glob('**/**')` semantics; single-star `*` stays non-recursive.
+  Deep-globbed files inside a lane's declared touch set are in-bounds; outside
+  is still a spec defect (#52, #54).
+- **`dispatched_at` recorded in `space.yaml` at dispatch time** (#18).
+
+### Fixed
+
+- **Canonical `section`/`freeze` commit message shape** — per-section commits
+  and the freeze commit carry the correct canonical prefix and body.
+- **`space run --help` steers to the `--` separator** — a quoted multi-word
+  command otherwise arrives as one argv token → opaque in-guest failure; the
+  desc/argument/example now show the `--` form, with a subprocess test (#28).
+- **Dropped a load-time "assigned but unused variable" warning** — `build_dir`
+  in `worktree_add` was computed but never read.
+
+## [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

@@ -271,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 |
 |---------|-------|--------------------|
@@ -299,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
@@ -326,9 +330,9 @@ 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