wowbagger 0.1.0-alpha.11 → 0.1.0-alpha.12

package/CHANGELOG.md

@@ -7,6 +7,25 @@ consolidation. The first tagged release inherits this file.
 
 ## Unreleased
 
+## 0.1.0-alpha.12 - 2026-08-28
+
+### Fixed
+
+- **Out-of-protocol local states remain global reconciliation barriers.**
+  Alpha.11 could misclassify an unknown committed revision, an authorized
+  working-tree predecessor over an unknown `HEAD`, or a working-tree deletion
+  over an authorized `HEAD` as advisory sibling synchronization when another
+  worktree owned the expected revision. `claim-verify` still failed, but an
+  unrelated mutation could proceed through the documented global barrier.
+  Alpha.12 classifies local state before owner and target scope, while genuine
+  authorized sibling predecessors remain target-scoped synchronization.
+- **Windows report path resolution preserves the read-failure error class.**
+  Windows can report `ENOENT` where POSIX reports `ENOTDIR` when an output path
+  descends through a regular file. Report generation now recognizes that
+  non-directory ancestor and returns `report-read-failed` with
+  `resolve-output-path` and `ENOTDIR` before publication, instead of surfacing
+  `report-write-failed` with `EEXIST`.
+
 ## 0.1.0-alpha.11 - 2026-08-27
 
 ### Fixed

package/README.md

@@ -30,8 +30,8 @@ agent to use those guarantees instead of hand-editing your Markdown.
 
 **Start here:** [install the core and set up a ledger](#start-here).
 
-> **Status: alpha, published, and self-hosted.** `0.1.0-alpha.11` is on npm under
-> the `next` tag and on this repository's `v0.1.0-alpha.11` tag. It is the
+> **Status: alpha, published, and self-hosted.** `0.1.0-alpha.12` is on npm under
+> the `next` tag and on this repository's `v0.1.0-alpha.12` tag. It is the
 > version this repository runs its own backlog on. The API is not frozen and the
 > version will move before a stable release.
 >
@@ -77,7 +77,7 @@ Wowbagger is the core authority for a Git-native work ledger. Use it instead
 of editing ledger Markdown by hand.
 
 ```sh
-wowbagger --version                 # require 0.1.0-alpha.11
+wowbagger --version                 # require 0.1.0-alpha.12
 wowbagger capabilities --json       # require contract_version: 5
 wowbagger validate --ledger ledger --json
 wowbagger ready --ledger ledger --as-of YYYY-MM-DD --json
@@ -103,10 +103,10 @@ cooperating writers; they are not exclusive locks.
 Install the core CLI, then verify it. The core requires Node.js 20 or later:
 
 ```sh
-npm install -g wowbagger@0.1.0-alpha.11   # exact plugin-matched release
+npm install -g wowbagger@0.1.0-alpha.12   # exact plugin-matched release
 # or, from this release's Git tag:
-# npm install -g github:lstutzman/wowbagger#v0.1.0-alpha.11
-wowbagger --version         # 0.1.0-alpha.11
+# npm install -g github:lstutzman/wowbagger#v0.1.0-alpha.12
+wowbagger --version         # 0.1.0-alpha.12
 wowbagger capabilities --json              # must report contract_version: 5
 ```
 
@@ -325,7 +325,7 @@ two supported install routes:
   registry requires a `latest` tag), so a bare install resolves to the same
   bytes.
 - **git tag** —
-  `npm install -g github:lstutzman/wowbagger#v0.1.0-alpha.11` installs this
+  `npm install -g github:lstutzman/wowbagger#v0.1.0-alpha.12` installs this
   release. Installing at a ref installs the core and every adapter that ref
   carries.
 
@@ -397,7 +397,7 @@ Upgrade the pieces you installed:
 
 ```sh
 npm install -g wowbagger@next                  # public npm registry
-npm install -g github:lstutzman/wowbagger#v0.1.0-alpha.11  # immutable Git release
+npm install -g github:lstutzman/wowbagger#v0.1.0-alpha.12  # immutable Git release
 git pull && npm ci                            # or: a direct checkout
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wowbagger",
-  "version": "0.1.0-alpha.11",
+  "version": "0.1.0-alpha.12",
   "description": "Git-native work ledger for coding agents: deterministic ready queues, guarded CAS mutations, claims and fencing, and self-contained HTML reports.",
   "type": "module",
   "license": "MIT",

package/skills/wowbagger/SKILL.md

@@ -14,7 +14,7 @@ publish something.
 Install the core separately before using this skill:
 
 ```sh
-npm install -g wowbagger@0.1.0-alpha.11
+npm install -g wowbagger@0.1.0-alpha.12
 ```
 
 The core requires Node.js 20 or later. This plugin ships only agent
@@ -34,9 +34,9 @@ wowbagger capabilities --json
 
 Read the plain distribution version from the first command and the top-level
 `contract_version` from the second. **This skill requires distribution version
-`0.1.0-alpha.11` and core `contract_version: 5`.**
+`0.1.0-alpha.12` and core `contract_version: 5`.**
 
-The distribution pin names the published `0.1.0-alpha.11` release; the cut that
+The distribution pin names the published `0.1.0-alpha.12` release; the cut that
 publishes core `contract_version: 5` moves it. Earlier cores report
 `contract_version: 3` or lower and lack behavior this skill requires, including
 the bounded item source, so the version check refuses them. Do not soften

package/src/claim-publication.js

@@ -773,6 +773,20 @@ async function reconciliationDiagnosis({
   workingTreeChanged,
 }) {
   const pathLabel = expectedPath ?? 'the item path';
+  // Two remedies, both named, in the order that makes the cost obvious. The
+  // field report behind item #113 read the single restore sentence as the only
+  // way out and discarded reviewed, merged work to obey it.
+  const unauthorizedRevision = {
+    reason: 'unauthorized-revision',
+    ...(expectedPath ? { expected_path: expectedPath } : {}),
+    remediation: `Restore the authorized revision at ${pathLabel}, then run claim-verify; that discards the edit. Or adopt the committed revision of ${pathLabel} with claim-adopt, then run claim-verify; that keeps the edit.`,
+  };
+  const hasOutOfProtocolLocalState = (
+    (actualRevision !== null && !authorizedRevisions.has(actualRevision))
+    || (headRevision !== null && !authorizedRevisions.has(headRevision))
+    || (actualRevision === null && headRevision !== null)
+  );
+  if (hasOutOfProtocolLocalState) return unauthorizedRevision;
   let expectedOwner = null;
   if (headRevision !== null && actualRevision === headRevision
     && headRevision !== expectedRevision) {
@@ -828,14 +842,7 @@ async function reconciliationDiagnosis({
       };
     }
   }
-  // Two remedies, both named, in the order that makes the cost obvious. The
-  // field report behind item #113 read the single restore sentence as the only
-  // way out and discarded reviewed, merged work to obey it.
-  return {
-    reason: 'unauthorized-revision',
-    ...(expectedPath ? { expected_path: expectedPath } : {}),
-    remediation: `Restore the authorized revision at ${pathLabel}, then run claim-verify; that discards the edit. Or adopt the committed revision of ${pathLabel} with claim-adopt, then run claim-verify; that keeps the edit.`,
-  };
+  return unauthorizedRevision;
 }
 
 function activePublicationMismatch(entries, record, actualRevision, observedAt) {

package/src/report.js

@@ -1,4 +1,4 @@
-import { mkdir, open, readFile, realpath, rename, rm } from 'node:fs/promises';
+import { mkdir, open, readFile, realpath, rename, rm, stat } from 'node:fs/promises';
 import path from 'node:path';
 import { projectReadiness } from './ready.js';
 import { buildAttention } from './report-attention.js';
@@ -502,7 +502,16 @@ async function resolvePhysicalPath(targetPath) {
 
   while (true) {
     try {
-      return path.join(await realpath(existingPath), ...missingSegments.reverse());
+      const resolvedPath = await realpath(existingPath);
+      // Windows realpath reports ENOENT, not ENOTDIR, when a path component
+      // is a regular file, so the walk can land on a file that still has
+      // segments missing below it. Restate that as the ENOTDIR POSIX raises.
+      if (missingSegments.length > 0 && !(await stat(resolvedPath)).isDirectory()) {
+        const notADirectory = new Error(`ENOTDIR: not a directory, realpath '${targetPath}'`);
+        notADirectory.code = 'ENOTDIR';
+        throw notADirectory;
+      }
+      return path.join(resolvedPath, ...missingSegments.reverse());
     } catch (error) {
       if (error?.code !== 'ENOENT') {
         throw error;