release: v1.11.0

Author: reslava

CHANGELOG.md

@@ -10,6 +10,15 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.11.0] - 2026-06-26
+
+### Added
+- **`loom install` now gives every project a user-owned `CLAUDE-LOCAL.md`.** Re-running `loom install` to pick up a newer Loom contract used to overwrite `.loom/CLAUDE.md` and destroy any project-local AI rules kept there. Install now creates a separate root `CLAUDE-LOCAL.md` — once, if absent, and **never overwritten, not even with `--force`** — and makes the root `CLAUDE.md` import both `@.loom/CLAUDE.md` (Loom-owned, regenerated every install) and `@CLAUDE-LOCAL.md` (yours). Put your project-specific AI rules in `CLAUDE-LOCAL.md` and they now survive every contract upgrade. The installed contract template gained a "File ownership" section spelling this out.
+- **`loom_append_done` accepts a batch `steps` array** to author a whole done doc in one call (step-ordered upsert, atomic fail-loud on an unknown step). The single `{ stepNumber, notes }` form is unchanged.
+
+### Fixed
+- **`loom_close_plan` no longer writes a stub done doc.** It had been delegating the done-doc body to an AI client that returned a fixed `TODO` placeholder whenever no API key was set — i.e. in every Claude Code session — silently writing a stub and marking the plan done regardless of the notes you passed. It now writes your notes verbatim (or appends a `## Closing notes` section to an existing per-step done doc) and fails loudly when there is nothing to write, instead of stubbing.
+
 ## [1.10.2] - 2026-06-22
 
 ### Fixed
@@ -505,7 +514,8 @@ the loop has been dogfooded on Loom itself across two threads.
 - **Physical Template Files**  
   `.loom/templates/` replaced by body generators in `core/bodyGenerators/`.
 
-[Unreleased]: https://github.com/reslava/loom/compare/v1.10.2...HEAD
+[Unreleased]: https://github.com/reslava/loom/compare/v1.11.0...HEAD
+[1.11.0]: https://github.com/reslava/loom/releases/tag/v1.11.0
 [1.10.2]: https://github.com/reslava/loom/releases/tag/v1.10.2
 [1.10.1]: https://github.com/reslava/loom/releases/tag/v1.10.1
 [1.10.0]: https://github.com/reslava/loom/releases/tag/v1.10.0

loom/ai-integration/loom-install-claude/chats/loom-install-claude-chat-001.md

@@ -9,7 +9,7 @@ version: 2
 tags: []
 parent_id: null
 requires_load: []
-last_ai_block: 6
+last_ai_block: 10
 ---
 # loom-install-claude Chat
 
@@ -203,4 +203,41 @@ docs/CLI_USER_GUIDE.md
 loom/refs/cli-commands-reference.md
 
 fold in the fix for `cwd`, do it now
-then commit
+then commit
+
+## AI:
+
+All three follow-ups done and committed to `main` as `5cd6f79` (11 files, build clean, full suite green).
+
+**Docs updated:**
+- `docs/CLI_USER_GUIDE.md` — install section now explains the two-file ownership model + the command table entry.
+- `loom/refs/cli-commands-reference.md` — `loom install` entry rewritten with the Loom-owned vs user-owned split.
+
+**`cwd` fix folded in:** `initLocal` now takes an injected `cwd` (`deps.cwd ?? process.cwd()`); `installWorkspace` passes `cwd: root`. The use-case is `process.cwd()`-pure now — the test dropped its `chdir` workaround and still passes, which is the proof. Standalone `loom init` is unchanged (still defaults to `process.cwd()`).
+
+**On your earlier open question** (whether the chord-flow backups go in the repo): `docs/internal/` is gitignored, so the backups *and* the extracted `docs/internal/chord-flow-claude/CLAUDE-LOCAL.md` stay local — nothing chord-flow-specific got committed here. The extraction is sitting there ready for you to copy to `J:/src/chord-flow/CLAUDE-LOCAL.md`.
+
+This isn't released yet — it ships whenever you next run `/do-release`. Once it's out, your chord-flow recovery sequence is: copy the extracted `CLAUDE-LOCAL.md` over, set chord-flow's root `CLAUDE.md` to the two-import block, upgrade the CLI, then `loom install`.
+
+Next: waiting for direction — nothing pending unless you want me to kick off a release.
+
+## Rafa:
+
+I pushed
+do-release 1.10.3 (last 2 commits was 2 fixes) or tell me if you consider 1.11.0 better
+
+## AI:
+
+**Go with `1.11.0`.** The "2 fixes" framing isn't quite right — here's what's actually in the release since `v1.10.2`:
+
+```
+5cd6f79  feat: loom install gives projects a user-owned CLAUDE-LOCAL.md
+d327c3f  docs: record append_done batch live-verify
+1a83f2b  fix:  loom_close_plan writes verbatim done docs, never a stub
+```
+
+So it's **1 feat + 1 fix + 1 docs**, not two fixes. The CLAUDE-LOCAL.md commit is a genuine new user-facing capability — a new file, new install behavior, a new section in the installed contract. Under semver that's a **MINOR** bump (`1.11.0`). `1.10.3` (PATCH) is reserved for backwards-compatible bug fixes only, and this release adds new behavior, so it would under-state what shipped.
+
+Recommendation: `/do-release 1.11.0`.
+
+(I can't run the release myself — it goes through your `/do-release` command. Fire it whenever you're ready.)

loom/ai-integration/loom-install-claude/plans/loom-install-claude-plan-001.md

@@ -11,6 +11,7 @@ tags: []
 parent_id: null
 requires_load: []
 target_version: 0.1.0
+actual_release: 1.11.0
 steps:
   - id: add-claude-local-md-user-owned
     order: 1

loom/core-engine/done-doc-review/plans/done-doc-review-plan-001.md

@@ -11,6 +11,7 @@ tags: []
 parent_id: ch_01KW2GNXP8MDZW467MGBDPK0KG
 requires_load: []
 target_version: 0.1.0
+actual_release: 1.11.0
 steps:
   - id: closeplan-use-case
     order: 1

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "@reslava-loom/monorepo",
-  "version": "1.10.2",
+  "version": "1.11.0",
   "private": true,
   "type": "module",
   "workspaces": [

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reslava-loom/app",
-  "version": "1.10.2",
+  "version": "1.11.0",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
   "scripts": {

packages/app/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reslava/loom",
-  "version": "1.10.2",
+  "version": "1.11.0",
   "license": "MIT",
   "repository": {
     "type": "git",

packages/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reslava-loom/core",
-  "version": "1.10.2",
+  "version": "1.11.0",
   "license": "MIT",
   "scripts": {
     "build": "tsc --build"

packages/core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reslava-loom/fs",
-  "version": "1.10.2",
+  "version": "1.11.0",
   "license": "MIT",
   "scripts": {
     "build": "tsc --build"