EPIC-PROPERTY-COMMAND-WINDOW: stale device read-backs flip controls back after a command

#summary

EPIC-PROPERTY-COMMAND-WINDOW: stale device read-backs flip controls back after a command

The maintainer traces a virtual lamp command through Shelly reports, a backend write queue, projection and HomeKit. A prior command’s confirmation entered the store 1.2 seconds after a newer command had been accepted. The plan compares backend command windows with client-side settling and device timestamps, selects backend reconciliation, and orders the overlapping implementation serially with one worker. It separates the architecture issue from an orchestration handoff and an acceptance ledger; green CI and a merged child are not treated as a physical-device pass.

The original HomeKit gateway PR had 29 commits and automated review rounds; a September 9 cache-hardening PR explicitly says its HAP GET path was not the observed trigger. A further September 27 repair PR reported three staging command/restore cycles with six client convergence measurements of 304–1067 ms on an unpublished candidate. The dated ledger rejects those samples as a substitute for its planned 20 idle + 20 poll-overlap trials, rapid-tap Apple Home/admin/panel checks and normal upgrade test. The epic and validation ledger remained open when checked October 2. The Studio81 account attributes the initial implementation to Gemini and independent review to Codex, but GitHub does not expose sessions mapping each patch to a model; active human hours, model spend and independent customer use remain missing. This is a feature→repair record, not a feature→value estimate.

Read at github.com · 25 min