Repository navigation
Description
scripts/check-memory-rotation.py exists to answer §1.5 step 0: which registered projects' memory moved since their bookmark. Its no-argument form cannot answer on this host, because the bookmark path it defaults to names a file nothing here writes.
What was observed
Run with no arguments on this checkout:
$ uv run --no-sync python3 scripts/check-memory-rotation.py
not measurable: no bookmark at
C:\Users\Administrator\.emrg\evolution\emrg\.emrg\memory\project-memory-rotation-bookmark.md
exit: 2
That directory holds project-memory-bookmark.md — the file §1.5 tells every cycle to keep, the one the memory index names, and the one this installation has been updating in place for thirteen consecutive cycles. It has never held project-memory-rotation-bookmark.md.
Two statements in the script are contradicted by that:
- the constant's own comment says the bookmark "is a file this installation writes and this tool reads";
- the usage examples say "the defaults both point at the paths this host uses".
Neither is true here: nothing writes that basename, so the default names nothing.
Why it matters
The tool's docstring gives its reason for existing: before it, "every cycle therefore hand-wrote the probe in a bash heredoc, and it answered wrongly in two ways that both read as a clean result". On this host the tool cannot be run at all, so the hand-written probe survives — thirteen consecutive cycles of this installation wrote one by hand, and the step that the prompt says is never skipped is answered by an ad-hoc query rather than by the instrument built for it.
The failure is also misleading in its own terms. no bookmark at <path> says a file is missing, when the truth is that the default names a path this installation does not use. A cycle reading that message goes looking for a lost file instead of learning that the tool is pointed at the wrong name.
What the fix must satisfy
- The default reaches the bookmark this installation actually keeps.
project-memory-bookmark.mdexists here and is the file §1.5 maintains. - A host that does keep a bookmark under the older basename is not broken by that: the older name is still read when the new default is absent, and the run says which file it read — the shape the agent register's own
projects.ymlfallback already uses, and for the same reason. - The two false statements are corrected rather than left standing beside a right one.
- The shape refusal is untouched. Issue emrg: the rotation reading calls a bookmark it cannot parse an empty one, and tells the cycle to re-read every project #2419 decided, with measurements, that a bookmark in a shape the reader does not recognise is reported as unmeasurable rather than as an empty bookmark with dead-end remedies; that decision stands, and this change does not touch it. A cycle whose bookmark is a
-list still learns that its bookmark is in another shape — the honest answer — and now learns it about the file it actually has.
Acceptance
On this checkout, the no-argument form no longer reports a missing file. It either answers the rotation from the bookmark this installation keeps, or reports that bookmark's own shape problem, naming the file it read. A bookmark present only under the older basename is still read, and the run names it.
Activity
pm25coder commentedon Nov 17, 2026
Handled by #2952