dld-kit 1.0.0-rc.4 → 1.0.0-rc.5

package/README.md

@@ -73,7 +73,7 @@ function retryWithBackoff(fn: () => Promise<Response>): Promise<Response> {
 
 The **always-on rule** is a short instruction installed for each agent: read the decision behind an annotation before changing that code. If a change would contradict it, the agent checks with you, and a new decision records the change.
 
-- **Accepted decisions aren't rewritten.** Once a decision is `accepted` and shared, you don't edit its reasoning. To change course, record a new decision that supersedes or amends it, so the history stays complete. Only metadata such as `status` and `references` gets updated. Statuses run `proposed` → `accepted` → `superseded` or `deprecated`.
+- **Merged decisions aren't rewritten.** While a decision is only on your branch, edit it as much as you like. Once it's on the main branch, you don't edit its reasoning: to change course, record a new decision that supersedes or amends it, so the history stays complete. The frontmatter (`status`, `references`, links, title) can always be updated; `id` and `timestamp` can't. `decision_edits` in the config can relax this. Statuses run `proposed` → `accepted` → `superseded` or `deprecated`.
 - **The docs are generated.** `/dld-snapshot` builds `OVERVIEW.md` and `SNAPSHOT.md` from the decisions. You never edit a spec by hand.
 - **Drift gets caught.** `/dld-audit` finds annotations without a decision, references to files that no longer exist, and annotated code that changed.
 - **Conventions live in one file.** An optional `decisions/PRACTICES.md` holds your testing, style and architecture conventions, and `/dld-implement` follows it.
@@ -150,6 +150,7 @@ Tessl installs and skills copied to other folders need one more step first: see
 - **`implement_review: false`** skips the review subagent in `/dld-implement`.
 - **`snapshot_artifacts`** adds documents for `/dld-snapshot` to generate, each from a prompt you write.
 - **`annotation_exclude`** lists paths whose `@decision` comments are only examples, such as docs.
+- **`decision_edits`** sets whether agents may edit the prose of decisions already on the main branch: `block` (default), `ask` or `allow`.
 
 All the options: [project configuration](docs/framework/project-configuration.md).
 
@@ -173,10 +174,11 @@ Run `npx dld-kit <command>`, or `npm install --global dld-kit` for a `dld` comma
 | `dld update` | Update the installed skills and rule; `--agent` adds agents |
 | `dld install-rule --agent <names>` | Install or refresh only the always-on rule |
 | `dld session-context --agent <name>` | Print the rule for a session hook, unless the agent loads it already (used by the Claude Code plugin) |
+| `dld check-decision-edits` | List edits to the prose of decisions already on the base branch; exits 3 under `decision_edits: block`, for a CI gate ([details](docs/framework/project-configuration.md#decision-edits)) |
 
 `init` and `update` won't overwrite files from a newer dld-kit unless you pass `--force`.
 
-These four commands, with their flags, exit codes and documented output, follow semantic versioning, as do `--help` and `--version`. The other commands in `dld --help` (`next-id`, `create-decision`, `regenerate-index` and so on) are internal: the skills run them from their bundled copy, and they can change in a minor release. Don't script against them.
+These five commands, with their flags, exit codes and documented output, follow semantic versioning, as do `--help` and `--version`. The other commands in `dld --help` (`next-id`, `create-decision`, `regenerate-index` and so on) are internal: the skills run them from their bundled copy, and they can change in a minor release. Don't script against them.
 
 ## Learn more