wifi-densepose

Commit Graph

Author	SHA1	Message	Date
rUv	880a3a41d3	chore(ci): add fix-markers for recent merges (#559 , #561 , #588 , #593 , #590-CI) (#606 ) Six new entries in scripts/fix-markers.json so the regression guard (.github/workflows/fix-regression-guard.yml + scripts/check_fix_markers.py) catches a future revert of any of these fixes: - RuView#559 — ./verify points at archive/v1/ paths - RuView#561 — README app flash offset 0x20000 + ota_data_initial.bin at 0xf000 + canonical provision.py path - RuView#588-SEC020 — provision.py prints (set)/(empty), not '' len(pw) (forbids the asterisk-run pattern that leaks password length) - RuView#593 — vital_signs.rs uses phase_circular_variance for wrapped phases - RuView#590-fuzz-stub — esp_stubs.h declares wifi_ps_type_t / WIFI_PS_NONE / esp_wifi_set_ps (keeps Fuzz Testing job green) - RuView#590-swarm-test — qemu_swarm.py passes --force-partial to provision.py (keeps Swarm Test ADR-062 job green) Verified: `python scripts/check_fix_markers.py` reports All 17 fix markers present.	2026-05-17 17:33:07 -04:00
ruv	eda45a6857	ci: fix-marker regression guard (witness-style) Adds a fast per-PR gate that asserts previously-shipped fixes are still present in the tree — the CI analogue of the ruflo witness fix-marker system, but self-contained (no plugin dependency, reviewable as plain JSON). Complements the heavier checks (firmware build, deterministic pipeline proof, release witness bundle) by catching the silent-revert class of regression that build+test wouldn't. - scripts/fix-markers.json manifest: 11 markers (RuView#396, #521, #517, #505, #354, #263, #266/#321, #265, #232/#375/#385/#386/#390, ADR-028 proof + witness bundle). Each has files / require (literal substring or /regex/) / optional forbid / rationale / ref. - scripts/check_fix_markers.py stdlib-only checker. Exit 0 clean / 1 regression / 2 bad manifest. Modes: --list, --json, --only ID. - .github/workflows/fix-regression-guard.yml runs on PR + push to main/master; gates on the checker and writes the result table into the run summary + an artifact. If a fix is intentionally removed, update scripts/fix-markers.json in the same PR with a rationale — the diff becomes the audit trail. Co-Authored-By: claude-flow <ruv@ruv.net>	2026-05-11 10:48:14 -04:00

Author

SHA1

Message

Date

rUv

880a3a41d3

chore(ci): add fix-markers for recent merges (#559 , #561 , #588 , #593 , #590-CI) (#606 )

Six new entries in scripts/fix-markers.json so the regression guard
(.github/workflows/fix-regression-guard.yml + scripts/check_fix_markers.py)
catches a future revert of any of these fixes:

- RuView#559 — ./verify points at archive/v1/ paths
- RuView#561 — README app flash offset 0x20000 + ota_data_initial.bin at 0xf000
                + canonical provision.py path
- RuView#588-SEC020 — provision.py prints (set)/(empty), not '*' * len(pw)
                (forbids the asterisk-run pattern that leaks password length)
- RuView#593 — vital_signs.rs uses phase_circular_variance for wrapped phases
- RuView#590-fuzz-stub — esp_stubs.h declares wifi_ps_type_t / WIFI_PS_NONE
                / esp_wifi_set_ps (keeps Fuzz Testing job green)
- RuView#590-swarm-test — qemu_swarm.py passes --force-partial to provision.py
                (keeps Swarm Test ADR-062 job green)

Verified: `python scripts/check_fix_markers.py` reports All 17 fix markers
present.

2026-05-17 17:33:07 -04:00

ruv

eda45a6857

ci: fix-marker regression guard (witness-style)

Adds a fast per-PR gate that asserts previously-shipped fixes are still
present in the tree — the CI analogue of the ruflo witness fix-marker
system, but self-contained (no plugin dependency, reviewable as plain
JSON). Complements the heavier checks (firmware build, deterministic
pipeline proof, release witness bundle) by catching the silent-revert
class of regression that build+test wouldn't.

  - scripts/fix-markers.json   manifest: 11 markers (RuView#396, #521,
    #517, #505, #354, #263, #266/#321, #265, #232/#375/#385/#386/#390,
    ADR-028 proof + witness bundle). Each has files / require (literal
    substring or /regex/) / optional forbid / rationale / ref.
  - scripts/check_fix_markers.py  stdlib-only checker. Exit 0 clean /
    1 regression / 2 bad manifest. Modes: --list, --json, --only ID.
  - .github/workflows/fix-regression-guard.yml  runs on PR + push to
    main/master; gates on the checker and writes the result table into
    the run summary + an artifact.

If a fix is intentionally removed, update scripts/fix-markers.json in the
same PR with a rationale — the diff becomes the audit trail.

Co-Authored-By: claude-flow <ruv@ruv.net>

2026-05-11 10:48:14 -04:00

2 Commits