wake: bump manifest version 0.6.12 -> 0.6.13 (#943 review §2)
ci/woodpecker/pr/ci Pipeline was successful

#942 and #943 both changed detector.sh after the 0.6.12 stamp, leaving
three materially different detectors under one version string. version=
is the component's sole self-identity claim (no per-file hashes), so a
reseed reading 0.6.12 -> 0.6.12 looks 'already current' while the file
changed underneath. Deploy itself is safe (wake-install decides by
cmp -s byte content) — this restores the identity claim, per mos-dt's
review suggestion adopted by MOS as a merge condition.

Co-Authored-By: Claude Fable 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01NsKce8iZuSuRnu3gVMCBKB
This commit is contained in:
Jason Woltje
2026-07-30 06:44:16 -05:00
co-authored by Claude Fable 5
parent 2621335e77
commit 052b8f15f9
@@ -306,8 +306,20 @@
# absence of these fields.
# Changed: detector.sh, digest.sh (+ test-wake-detector.sh
# D10/D11/D12/D13, test-wake-digest-quarantine.sh Q10).
# 0.6.13 #942/#943 SLACK-knob validation hardening, split from 0.6.12 because
# version= is the component's SOLE self-identity claim (no per-file
# hashes here) and two detector-changing merges after the 0.6.12
# stamp had left three materially different detectors under one
# version string (#943 review §2). #942: the knob is resolved once,
# shape-validated, LOUD fallback 300, and forced base-10 (10#) so
# zero-padded values mean what the operator wrote instead of octal.
# #943: validation is a whole-string case pattern, not grep, so an
# embedded newline ($'300\n8' — accepted per-line by grep's ^...$
# anchors, fatal in $((...))) rejects. Full rationale in the knob
# paragraph of the 0.6.12 entry above.
# Changed: detector.sh (+ test-wake-detector.sh D13).
component=wake
version=0.6.12
version=0.6.13
# Watch-list schema this component consumes, and the INCLUSIVE range of
# schema_version values it supports. A wake-watch-list.json whose schema_version