amos 3fa3dd73ca Add 1 MEDIUM task from batch 28: ESP event loop accounting
Batch 28 commit a7fca39 gave ESP event loop accounting as MEDIUM: 2 of
3 attempts passed and the failure was a wrong fix in a complete session.
The task comes from the commit Qwen measured, its digest matches, and it
is still present at the batch branch head.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-05 11:54:54 +08:00
..

Event diagnostics workbench

This workbench builds the generic ESP event-loop implementation on an application-thread software adapter. Run make smoke with GCC and Make. The smoke program exercises one normal event.

The complete public behavior used by this application is in docs/event-contract.md; the original API comments remain in components/esp_event/include/. All clauses in that contract are delivery requirements.

Only these files are collected for grading:

  • components/esp_event/esp_event.c
  • components/esp_event/private_include/esp_event_internal.h

The upstream source and headers retain their original contents. The local platform/ files supply byte queues, mutexes, logical task identities, logging and a deterministic clock. They do not dispatch events or maintain handler statistics. The adapter supports application-thread loops (task_name = NULL); dedicated OS tasks and ISR posting are outside this workbench.