Skip to content

v0.6.2 — Release provenance, recursive redaction, compatibility

Choose a tag to compare

@McphersonAI McphersonAI released this 05 Aug 17:50
· 2 commits to main since this release

Provenance, hardening, and documentation patch. No runtime governance behavior changed.

AUTHORITY                     NONE
ENFORCEMENT                   OFF
AUTOMATIC_MAPPING_ACTIVATION  OFF
OUTBOUND_ACTIONS              OFF
REGISTRY_MUTATION             OFF
REMOTE_DECISIONS              SHADOW_ONLY

Public release provenance — corrected

Through v0.6.1 the public artifact described the private build that produced it, in two ways no downloader could check:

  • RELEASE-PROVENANCE.json named the private candidate commit as the public source_commit.
  • V6-PACKAGE-MANIFEST.json recorded seventeen source files under private release/openclaw-public/… paths.

Both are corrected. Provenance moves to schema …/v2: source_commit/source_tree are the public base commit and tree, labelled PUBLIC_BASE_COMMIT/PUBLIC_BASE_TREE. The three bindings an artifact cannot make about itself — release commit, release tree, archive SHA-256 — are declared under external_bindings with the command that resolves each. No future commit is hardcoded and no self-referential commit claim is made.

The release is now reproducible outside McPherson AI:

git clone https://github.com/McphersonAI/mcpherson-governance-openclaw
cd mcpherson-governance-openclaw && git checkout v0.6.2
npm pack
shasum -a 256 mcphersonai-mcpherson-governance-openclaw-0.6.2.tgz
# de760e0469819fad58982d5573db63e868759676fa8bdd461606f35ff6fe3d87

Recursive secret redaction

New packages/governance-diagnostics/redaction.mjs removes credential material from every nested object and array before it reaches an output boundary — normalized key matching (token, access/refresh/device token, authorization, bearer, API key, secret, password, credential, cookie, session, private key, TOTP seed, recovery code, state key) plus value-shape scrubbing, depth-limited and cycle-safe. Wired into the observer's artifact-serialization choke point and every CLI output path, each followed by a final-output scan that fails closed. A no-op on well-formed artifacts.

Evidence stays usable: booleans, null, and undefined are never redacted, and authority, credential_id, token_shape and similar keep their values.

Compatibility and migration

New COMPATIBILITY.md:

OpenClaw Support
2026.6.33 (7af0cfc) Preferred target; fully lifecycle-proven
2026.6.5 (5181e4f) Fully lifecycle-proven
2026.7.1-2 (0790d9f) Exact-target binding, install and uninstall validated; live observation unsupported — the upstream local CLI does not issue the device-bound operator.read token

Also documents the v0.5.1 → v0.6.2 receipt-ledger migration end to end.

Verification

Artifact SHA-256 de760e0469819fad58982d5573db63e868759676fa8bdd461606f35ff6fe3d87
Packaged files 114
Checksum entries 113
Runtime dependencies 0
Verifier 42/42
Packaged tests 10/10
Regression tests 31/31
Lifecycle OpenClaw 2026.6.33 (7af0cfc9c5488e03c4e2f528bdc7ac9f7778b35e)

The packaged verifier now asserts all six safety values rather than two.