wowbagger 0.1.0-alpha.1 → 0.1.0-alpha.2

package/CHANGELOG.md

@@ -7,6 +7,39 @@ consolidation. The first tagged release inherits this file.
 
 ## Unreleased
 
+## 0.1.0-alpha.2 - 2026-08-12
+
+### Fixed
+
+- `claim-verify` now reports `git_finalized` and `git_commit` for each successful
+  claimed publication. Reconciliation logs stay inside the configured ledger,
+  including repository-root ledgers. Items 55-57.
+- A new empty ledger now starts on schema version 2. Existing non-empty
+  schema-version-1 ledgers remain compatible until migration. Item 54.
+- The installed skill now identifies the active claim as the work-in-flight
+  signal while the item remains in `backlog`. Item 58.
+- The npm package now ships the mutation and work-claim contract documents that
+  the installed skill references. Item 59.
+- The npm package now ships the documented schema-version-2 migration
+  entrypoint for package-only consumers. Item 60.
+- The installed work-claim contract now distinguishes durable reconciliation
+  state from per-publication Git finalization. Item 61.
+
+- The Claude Code plugin manifest and marketplace metadata now use the same
+  distribution version as `package.json`. The packaging gate rejects release
+  identity drift before npm, Git, or marketplace publication. Item 48.
+- Capability help now distinguishes the core's unbound default claim profile
+  from one provisioned ledger's work-claim profile. It names
+  `contract_version` as the core version and
+  `operations.work_claim.api_version` as the work-claim API version. Items 47
+  and 51.
+- `provision --help`, README, and the shipped skill now expose the accessible
+  Git-checkout prerequisite and the pre-provision
+  `claim capabilities --ledger <dir> --json` gate. Item 50.
+- The isolated consumer dogfood runbook now creates or selects the disposable
+  worktree before agent launch and requires a session-root Git preflight before
+  installation or ledger mutation. Item 52.
+
 ## 0.1.0-alpha.1 - 2026-08-11
 
 ### Behaviour changes

package/README.md

@@ -51,6 +51,11 @@ mismatch is detectable instead of silent: it reads `contract_version` from
 not support. It will not fall back to editing ledger files by hand, because that
 would bypass validation and atomic publication.
 
+For an isolated consumer pilot, create or select the disposable worktree before
+the agent starts. Then launch a new session with that worktree as its project
+root. Follow the [isolated dogfood pilot runbook](docs/isolated-dogfood-pilot.md);
+do not try to drive a sibling worktree from an already-running agent session.
+
 To use the core directly from a clone instead, see
 [Core commands](#core-commands).
 
@@ -88,7 +93,10 @@ whether a core supports your request.
   with release evidence). Do not assume a platform is officially supported just
   because the CLI starts.
 - **Other tooling:** `wowbagger` manages a Git-tracked Markdown ledger. It
-  needs `git` present for work-claim and namespace operations.
+  needs an accessible Git checkout for work-claim and namespace operations.
+  Before `provision`, run
+  `wowbagger claim capabilities --ledger <dir> --json` and require
+  `result.operations.work_claim.supported: true`.
 
 ### Security
 
@@ -141,9 +149,9 @@ Then verify, exactly as on first install:
 wowbagger capabilities --json
 ```
 
-`contract_version` is the compatibility gate. The plugin and adapter refuse a
-core that reports a version they do not support; if you automate against the
-core directly, do the same rather than guessing.
+The top-level `contract_version` is the core compatibility gate. The plugin
+and adapter refuse a core that reports a version they do not support; if you
+automate against the core directly, do the same rather than guessing.
 
 The shipped adapter selects only adapter contract version 2 and requires core
 contract version 2. A v1-only consumer receives
@@ -327,11 +335,14 @@ operation. See [the work-claim contract](docs/work-claim-contract.md) for the
 request envelopes, refusal precedence, recovery rules, and the difference
 between strict fenced and merge-coordinated backends.
 
-The `contract_version` reported by `capabilities` is what an adapter or plugin
-declares it requires. A consumer pairing one with a core that reports a
-different contract version gets a refusal, not a guess. Direct checkout use —
-`./bin/wowbagger.js` from a clone — remains supported and is what this
-repository's own ledger uses.
+Core and work-claim versions use distinct negotiation fields. Read the
+top-level `contract_version` from core `capabilities`. Read
+`result.operations.work_claim.api_version` from
+`claim capabilities --ledger <dir> --json`. A claim response's top-level
+`contract_version` is the legacy claim-envelope marker; do not compare it with
+the core version. A consumer that receives an unsupported version refuses
+rather than guessing. Direct checkout use—`./bin/wowbagger.js` from a
+clone—remains supported and is what this repository's own ledger uses.
 
 ## Verify a checkout