Repository navigation
v3.6.2
What's new
Bug Fixes
The workflow guard's marker parser (parseMarkerBody) hard-rejected any persisted marker whose protocolVersion didn't exactly match the current MARKER_PROTOCOL_VERSION (2), with no fallback for v1 markers minted before PR #741's version bump.
A user resuming an OpenCode session across the upgrade would carry v1 markers into v2 code, where the read path treated them as malformed, aggregating to guard-unavailable and dropping an in-flight guarded unit instead of recovering it.
Since MarkerSource's shape didn't change between v1 and v2 (the version bump was coordinated with an unrelated receipt-envelope schema bump), a persisted v1 marker recovers identically under v2 parsing. This fix mirrors the existing LEGACY_RECEIPT_PROTOCOL_VERSION pattern already used in receipt-ledger.ts: parseMarkerBody now accepts both MARKER_PROTOCOL_VERSION and a new LEGACY_MARKER_PROTOCOL_VERSION, with test coverage added for a persisted v1 marker parsed under v2 code.