changeledger 0.6.0 → 0.6.1

package/AGENTS.md

@@ -6,8 +6,10 @@ under `.changeledger/changes/`, persistent truth under `.changeledger/specs/`.
 <!-- changeledger -->
 > [!IMPORTANT]
 > This repo uses **ChangeLedger**. Before creating or modifying files, run
-> `changeledger context` (or `changeledger context <change-id>`) and follow its output.
-> If the command is unavailable, stop and restore/install ChangeLedger; do not proceed from memory.
+> `changeledger context`, read its complete output, and follow it.
+> If the output is truncated/incomplete, stop and restore complete context before
+> proceeding. If the command is unavailable, stop and restore/install
+> ChangeLedger; do not proceed from memory.
 
 The canonical ChangeLedger contract is split into task-focused fragments under
 [`templates/contract/`](templates/contract/). The deterministic

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "changeledger",
-  "version": "0.6.0",
+  "version": "0.6.1",
   "description": "Turn conversations into buildable changes.",
   "type": "module",
   "bin": {

package/src/contract.mjs

@@ -37,8 +37,10 @@ const LEGACY_CONTRACT_HASHES = new Set([
 export const REFERENCE = `${MARKER}
 > [!IMPORTANT]
 > This repo uses **ChangeLedger**. Before creating or modifying files, run
-> \`changeledger context\` (or \`changeledger context <change-id>\`) and follow its output.
-> If the command is unavailable, stop and restore/install ChangeLedger; do not proceed from memory.
+> \`changeledger context\`, read its complete output, and follow it.
+> If the output is truncated/incomplete, stop and restore complete context before
+> proceeding. If the command is unavailable, stop and restore/install
+> ChangeLedger; do not proceed from memory.
 `;
 
 export const contractLink = (changeledgerDir) => path.join(changeledgerDir, 'AGENTS.md');

package/templates/contract/core.md

@@ -5,6 +5,10 @@ reflection. Work is planned and documented before code is written.
 
 ## Non-negotiable fast path
 
+Running `changeledger context` is discovery, not compliance by itself. Read the
+complete output and follow the current mode. If the output is truncated or
+incomplete, stop and restore complete context before creating or modifying files.
+
 1. Work starts with conversation. Read-only investigation may clarify a request,
    but create no change or implementation artifact until there is enough clarity
    to document faithfully **and** the human explicitly authorizes documentation. A direct request such
@@ -22,6 +26,11 @@ reflection. Work is planned and documented before code is written.
 8. After human acceptance, graduate persistent truth or record an explicit skip,
    then archive the done change.
 
+If no approved or in-progress change applies, do not silently edit repository
+files. Create or update a change, or ask the human whether a purely operational,
+reversible edit with no persistent truth or observable behavior change should be
+done directly. If unsure, document it in ChangeLedger.
+
 Humans consume changes in `changeledger view`; write for the rendered view.
 
 ## Lifecycle