electron-rare/RTC_BL_PHONE
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ZeroClaw dual full-loop evidence run (2026-02-21) #23

New Issue
Closed
opened 2026-02-21 18:21:44 +00:00 by electron-rare · 4 comments
electron-rare commented 2026-02-21 18:21:44 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Summary

  • Kill_LIFE coordination: PR #11 merged (watcher + realtime infra on main).
  • RTC preflight: python3 scripts/zeroclaw_hw_preflight.py --require-port --zeroclaw-bin ... -> OK.
  • RTC builds: pio run -e esp32dev, pio run -e esp32-s3-devkitc-1 -> PASS.
  • Zacus preflight/build/upload on FreeNove: PASS (pio run, buildfs, upload/uploadfs).

Blockers observed

  • hw_validation.py couldn't complete a full dual-loop in this session because all detected S3/bench routing could not be validated and some ports are busy ([Errno 16] Resource busy) or command-incompatible.
  • Webhook traces from zeroclaw_webhook_send.sh to Kill_LIFE follow are returning HTTP 408 in this environment (and producing gateway parse warnings in logs).

Proposed next run

  1. Connect distinct, known RTC A252 + S3 + bench serial targets (or confirm mapping), then rerun
    python3 scripts/hw_validation.py --flash --port-a252 <A252_PORT> --port-s3 <S3_PORT> --bench-port <BENCH_PORT> --a252-base-url ... --s3-base-url ...
  2. Re-run webhook traces after correcting follow response parsing / provider timeout handling.

Artefacts

  • docs/rapport_hw.json
  • docs/rapport_tests_fonctionnels.md
  • Kill_LIFE artifacts: artifacts/zeroclaw/realtime_1min.log
## Summary - Kill_LIFE coordination: PR #11 merged (watcher + realtime infra on main). - RTC preflight: `python3 scripts/zeroclaw_hw_preflight.py --require-port --zeroclaw-bin ...` -> OK. - RTC builds: `pio run -e esp32dev`, `pio run -e esp32-s3-devkitc-1` -> PASS. - Zacus preflight/build/upload on FreeNove: PASS (`pio run`, buildfs, upload/uploadfs). ## Blockers observed - `hw_validation.py` couldn't complete a full dual-loop in this session because all detected S3/bench routing could not be validated and some ports are busy (`[Errno 16] Resource busy`) or command-incompatible. - Webhook traces from `zeroclaw_webhook_send.sh` to Kill_LIFE follow are returning HTTP 408 in this environment (and producing gateway parse warnings in logs). ## Proposed next run 1. Connect distinct, known RTC A252 + S3 + bench serial targets (or confirm mapping), then rerun `python3 scripts/hw_validation.py --flash --port-a252 <A252_PORT> --port-s3 <S3_PORT> --bench-port <BENCH_PORT> --a252-base-url ... --s3-base-url ...` 2. Re-run webhook traces after correcting follow response parsing / provider timeout handling. ## Artefacts - `docs/rapport_hw.json` - `docs/rapport_tests_fonctionnels.md` - `Kill_LIFE artifacts`: `artifacts/zeroclaw/realtime_1min.log`
electron-rare commented 2026-02-21 18:44:27 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Progress update:

  • Kill_LIFE stack smoke: , , , all OK.
  • watchlist alignment verified; spec_kit sync prepared and PR #13 opened in .
  • Zacus pass: preflight ok, + + + succeeded on .
  • RTC validation could not complete in this session: serial open fails at bench port () for and before scenario phase.
  • Realtime witness files updated: and now report with runner bench-port error.
  • Webhook traces: dry-run succeeded (), then normal run returned one on rtc trace (known parse issue) and one successful trace payload from .
Progress update: - Kill_LIFE stack smoke: , , , all OK. - watchlist alignment verified; spec_kit sync prepared and PR #13 opened in . - Zacus pass: preflight ok, + + + succeeded on . - RTC validation could not complete in this session: serial open fails at bench port () for and before scenario phase. - Realtime witness files updated: and now report with runner bench-port error. - Webhook traces: dry-run succeeded (), then normal run returned one on rtc trace (known parse issue) and one successful trace payload from .
electron-rare commented 2026-02-21 18:44:40 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Progress update:

  • Kill_LIFE stack smoke: /health, /8788, /8788/realtime_1min.log, /9090/-/ready all OK.
  • spec_kit alignment: specs sync prepared and PR #13 opened in Kill_LIFE.
  • Zacus pass: preflight ok, build + buildfs + uploadfs + upload succeeded on /dev/tty.usbmodem5AB90753301.
  • RTC validation hw_validation could not complete: bench port open fails with Resource busy for /dev/tty.SLAB_USBtoUART and /dev/cu.SLAB_USBtoUART before scenario phase.
  • Realtime witness files updated in RTC_BL_PHONE docs/rapport_hw.json and docs/rapport_tests_fonctionnels.md with runner error.
  • Webhooks: rtc dry-run success; normal rtc send returned HTTP 408 (known gateway parse warning), zacus webhook succeeded from zeroclaw_webhook_send.
Progress update: - Kill_LIFE stack smoke: /health, /8788, /8788/realtime_1min.log, /9090/-/ready all OK. - spec_kit alignment: specs sync prepared and PR #13 opened in Kill_LIFE. - Zacus pass: preflight ok, build + buildfs + uploadfs + upload succeeded on /dev/tty.usbmodem5AB90753301. - RTC validation hw_validation could not complete: bench port open fails with Resource busy for /dev/tty.SLAB_USBtoUART and /dev/cu.SLAB_USBtoUART before scenario phase. - Realtime witness files updated in RTC_BL_PHONE docs/rapport_hw.json and docs/rapport_tests_fonctionnels.md with runner error. - Webhooks: rtc dry-run success; normal rtc send returned HTTP 408 (known gateway parse warning), zacus webhook succeeded from zeroclaw_webhook_send.
electron-rare commented 2026-02-21 19:32:38 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Cycle RTC loop status (2026-02-21):\n- Kill_LIFE stack + web endpoints validated (, , , ).\n- preflight passes.\n- Full dual-loop validation is blocked by missing/mis-mapped bench / S3 port in current setup.\n - Available ports: and (same ESP32 A252 board, duplicate node), (ESP32-S3 board with STATUS-only profile).\n - No dedicated bench controller port found for scenario steps.\n- Zacus side: build + + + success on .\n- PR Kill_LIFE merged (main).\n\nNext: unblock only when a dedicated bench serial endpoint is connected and stable (or route bench loop to existing bench command set).

**Cycle RTC loop status (2026-02-21):**\n- Kill_LIFE stack + web endpoints validated (, , , ).\n- preflight passes.\n- Full dual-loop validation is **blocked by missing/mis-mapped bench / S3 port** in current setup.\n - Available ports: and (same ESP32 A252 board, duplicate node), (ESP32-S3 board with STATUS-only profile).\n - No dedicated bench controller port found for scenario steps.\n- Zacus side: build + + + success on .\n- PR Kill_LIFE merged (main).\n\nNext: unblock only when a dedicated bench serial endpoint is connected and stable (or route bench loop to existing bench command set).
electron-rare commented 2026-02-21 19:32:44 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Cycle RTC loop status (2026-02-21):

  • Kill_LIFE stack + web endpoints validated (3000/health, 8788/, 8788/realtime_1min.log, 9090/-/ready).
  • hw_validation preflight passes.
  • Full dual-loop validation is blocked by missing/mis-mapped bench / S3 port in current setup.
    • Available ports: /dev/tty.usbserial-0001 and /dev/tty.SLAB_USBtoUART (same ESP32 A252 board, duplicate node), /dev/tty.usbmodem5AB90753301 (ESP32-S3 board with STATUS-only profile).
    • No dedicated bench serial endpoint is present for bench-port scenario steps.
  • Zacus side: pio build + buildfs + uploadfs + upload success on /dev/tty.usbmodem5AB90753301.
  • PR Kill_LIFE #14 merged (main).

Next: unblock only when a dedicated bench serial endpoint is connected and stable (or route bench loop to existing bench command set).

**Cycle RTC loop status (2026-02-21):** - Kill_LIFE stack + web endpoints validated (`3000/health`, `8788/`, `8788/realtime_1min.log`, `9090/-/ready`). - `hw_validation` preflight passes. - Full dual-loop validation is **blocked by missing/mis-mapped bench / S3 port** in current setup. - Available ports: `/dev/tty.usbserial-0001` and `/dev/tty.SLAB_USBtoUART` (same ESP32 A252 board, duplicate node), `/dev/tty.usbmodem5AB90753301` (ESP32-S3 board with STATUS-only profile). - No dedicated bench serial endpoint is present for `bench-port` scenario steps. - Zacus side: `pio` build + `buildfs` + `uploadfs` + `upload` success on `/dev/tty.usbmodem5AB90753301`. - PR Kill_LIFE `#14` merged (main). Next: unblock only when a dedicated bench serial endpoint is connected and stable (or route bench loop to existing bench command set).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
 codex
documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
electron (Clément Saillant)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: electron-rare/RTC_BL_PHONE#23
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?