LocalSetup 4.53.3

LocalSetup 4.53.3

LocalSetup 4.53.3 separates reviewed Herdr source evidence from stable release pins and keeps manually dispatched GitHub validation complete.

Highlights

• Review source changes without implying an upgrade: the Herdr watcher records a separately reviewed source revision and reports its exact immutable comparison links. Existing release and bundled-schema pins stay unchanged.
• Keep watching the API owner: source tracking includes the operation-definition module introduced by the upstream schema refactor. The operating guide now accurately describes the compact GitHub issue handoff used for confirmed drift.
• Keep release validation complete: manually dispatched checks retain full Git history and schedule required Python shards after optional checks are skipped. Older release anchors stay reachable, and missing test results cannot satisfy release validation.

Compatibility

This maintenance patch preserves Herdr v0.9.5 release, artifact and bundled-schema pins. It does not install, upgrade, restart or qualify a running Herdr client or server.

Existing manifests without a separate watched-source revision continue to use the release source revision. An explicitly malformed watched-source revision produces unknown baseline evidence and no fabricated comparison URL; confirmed file drift remains visible.

The reviewed upstream refactor retains the wire operations used by the existing LocalSetup adapter. Source review is not a claim that every newer upstream capability or live server is supported.

Published v4.53.1 is the verified baseline. The Herdr provenance maintenance slice advances to 4.53.2, and the validation-history maintenance slice advances to 4.53.3. Release preparation, fixups and generated/version synchronization add no increment. Historical tags, releases and artifacts are preserved.

Update

Use the existing installation or package-refresh workflow for selected packages. No dependency or configuration migration is required.

Start with the Herdr master skill and use its provenance specialist for explicit source checks. New upstream evidence remains a review handoff, never authority for a host upgrade.

Verification

Run focused provenance, watcher and QC regressions and the standard source/catalog/document checks. Validate the final exact signed candidate with the required hosted jobs, including all eight Python shards.

Before publication, verify the required-key signed commit and tag, the actual downloaded archive with its .sha256 checksum and .cdx.json SBOM sidecars, build provenance, draft release prose and an isolated installation. Keep source evidence distinct from live service qualification.

Download the archive with its .sha256 checksum and .cdx.json SBOM sidecars, then follow the release guide.