From 277d850a053b2c44cba49b3060dc5c8907525bf0 Mon Sep 17 00:00:00 2001 From: Claude Date: Sat, 17 Oct 2026 16:10:03 +0200 Subject: [PATCH] Release 0.1.2 Co-Authored-By: Claude Opus 5.5 --- CHANGELOG.md | 5 ++++- README.md | 4 ++-- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 1c3fbb8..93de500 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,8 @@ ## [Unreleased] +## [0.1.2] - 2026-10-17 + ### Changed - Pack hone's review into units of consecutive tasks up to ~400 changed lines instead of one unit per task, and after round 1 re-review only units not yet done: a unit is done after two consecutive clean reviews, and a fix re-opens every unit whose files it touches. Each round still logs a feature `- Rating:` line (the lowest unit rating), which smithy reads; the worked example's `code-review.md` shows the units ([#35](https://github.com/forkrul/damascus_development/pull/35)) @@ -80,6 +82,7 @@ _Initial release._ - Document the single-founder production-readiness plan ([#3](https://github.com/forkrul/damascus_development/pull/3)) - License the project under MIT; vendored submodules keep their upstream licenses ([#3](https://github.com/forkrul/damascus_development/pull/3)) -[Unreleased]: https://github.com/forkrul/damascus_development/compare/v0.1.1...HEAD +[Unreleased]: https://github.com/forkrul/damascus_development/compare/v0.1.2...HEAD +[0.1.2]: https://github.com/forkrul/damascus_development/releases/tag/v0.1.2 [0.1.1]: https://github.com/forkrul/damascus_development/releases/tag/v0.1.1 [0.1.0]: https://github.com/forkrul/damascus_development/releases/tag/v0.1.0 diff --git a/README.md b/README.md index fb82fe9..b4cbe2e 100644 --- a/README.md +++ b/README.md @@ -14,10 +14,10 @@ From your repo root, pinning a release tag (see [Releases](https://github.com/fo ```bash git submodule add https://github.com/forkrul/damascus_development.git vendor/damascus -git -C vendor/damascus checkout v0.1.1 # pin a release, never a moving branch +git -C vendor/damascus checkout v0.1.2 # pin a release, never a moving branch git -C vendor/damascus submodule update --init --recursive # damascus's own pinned submodules ./vendor/damascus/install.sh -git add .gitmodules vendor/damascus && git commit -m "chore: vendor damascus v0.1.1" +git add .gitmodules vendor/damascus && git commit -m "chore: vendor damascus v0.1.2" ``` Then, in an agent session in that repo, start a feature with the orchestrator — in Claude Code, `/smithy` (or its alias `/spdd-pipeline`), or just say "let's build *feature X*" and ask for the smithy skill. Smithy runs the next stage, halts at every gate for your signoff, and picks up where it left off on `smithy --resume`. To see what a finished run looks like before starting one, read [`examples/`](examples/): one feature's complete artifact trail through all five gates.