cc-watch script fixes — interactive playground

Three bugs fixed in OrchestKit's CC release-watch pipeline (closes #1693, #1694, #1696 — milestone M134). Use the panels below to simulate each scenario and observe the new vs. old behaviour.

What changed
W1b Watcher uses snapshot-presence-on-disk as the only filter (no more silent-skip when floor jumps ahead).
W1c New --reissue-existing X.Y.Z[,…] flag on cc-release-watch.mjs + matching workflow_dispatch input.
W1d cc-triage.mjs now retries on timeout / empty-array / parse-error and writes parse_failed: true on final failure (root cause of M134 stuck state).

W1b — silent-skip filter

Inputs

knownLatest (cc-support.json floor) Versions in CHANGELOG (comma-sep) Already snapshotted on disk (comma-sep)

Output

Click Simulate to see which versions get picked up.

W1c — --reissue-existing flag

Inputs

Versions in CHANGELOG Already snapshotted on disk --reissue-existing arg

Output

Click Simulate. Reissued versions retain their snapshot body and re-emit empty-features gap entries.

W1d — empty-array → retry → parse_failed

Inputs

Attempt 1 result (model output) Attempt 2 result (model output)

Output

Click Simulate to see retry behaviour and final gap-entry state.

OrchestKit · M134 follow-up · branch fix/cc-watch-script-bugs-and-retry