Commit ffc32e5
claudeMM
docs(README): refresh UIK version requirement and verification snapshot
Two staleness fixes after the 2026-04-08 dogfooding round:
1. The "Publishing state (the other side)" subsection said "UIK v0.2.1 or
later required for the uik-daemon bin". v0.2.1 publishes device state
correctly but the agent slot still goes stale after its TTL because
that release only republishes the desktop heartbeat, not agent status.
v0.2.2 fixes that by republishing agent status on the same
POLL_INTERVAL_MS cadence. Updated the line to recommend v0.2.2 and
spell out what each daemon release added so readers don't pin to a
silently-broken version.
2. The "Latest local verification" snapshot was dated 2026-03-31 and
referred to v0.5.0. Refreshed to v0.6.1 and 2026-04-08 with the actual
dogfooded state (both devices and both agents active, zero stale,
after the UIK 0.2.2 deployment). Left the claude-mem line on its
original date because that path has not been re-verified since v0.5.0.
No code changes.1 parent f6f5967 commit ffc32e5
1 file changed
Lines changed: 4 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
299 | 299 | | |
300 | 300 | | |
301 | 301 | | |
302 | | - | |
| 302 | + | |
303 | 303 | | |
304 | 304 | | |
305 | 305 | | |
| |||
387 | 387 | | |
388 | 388 | | |
389 | 389 | | |
390 | | - | |
| 390 | + | |
391 | 391 | | |
392 | | - | |
393 | | - | |
| 392 | + | |
| 393 | + | |
394 | 394 | | |
395 | 395 | | |
396 | 396 | | |
| |||
0 commit comments