@rowan-hiro/inkan 0.2.1 → 0.2.2

package/README.md

@@ -208,7 +208,8 @@ must carry, and leaves flag-level syntax to `inkan help`, so a CLI change
 does not bump the protocol. The block carries a protocol number. `init`
 upgrades a block it generated under an earlier protocol in place and refuses
 to overwrite a block that was edited by hand, so the policy lives in exactly
-one place. `--lang <tag>` sets the language agents should write outcome
+one place. A block stamped with a protocol newer than the installed Inkan
+is reported as such, with a prompt to upgrade the tool, not as a hand edit. `--lang <tag>` sets the language agents should write outcome
 prose in. `inkan init --claude` also creates `CLAUDE.md` as a symlink to
 `AGENTS.md`: Claude Code reads its own file name, and there is still one
 policy, not a copy.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rowan-hiro/inkan",
-  "version": "0.2.1",
+  "version": "0.2.2",
   "description": "Seal the authoritative outcome; keep a trustworthy record of the process.",
   "type": "module",
   "bin": {

package/src/api.js

@@ -651,6 +651,15 @@ function writeProtocol(dir, lang) {
     fs.writeFileSync(agentsFile, content, 'utf8');
     return { root: dir, agentsFile, changed: true };
   }
+  // A block stamped with a protocol this tool does not know yet was written
+  // by a newer Inkan, not by hand. Say so and leave it alone.
+  const stamped = found.text.match(/<!-- inkan-protocol: (\d+) -->/);
+  const foundVersion = stamped ? Number(stamped[1]) : 0;
+  if (foundVersion > PROTOCOL_VERSION) {
+    throw new InkanError(
+      `${AGENTS_FILENAME} inkan block is protocol ${foundVersion}; this Inkan knows up to ${PROTOCOL_VERSION}. Upgrade Inkan; refusing to overwrite it`,
+    );
+  }
   throw new InkanError(`${AGENTS_FILENAME} inkan block was edited by hand; refusing to overwrite it`);
 }