Name the subject a conflict is actually about

A shared verb is not a shared fact. 「客厅的恒温器调到 22 度」 and
「卧室的恒温器调到 24 度」 agree with each other; the store had been
recording them as one thermostat moving, and the older side then left the
answer page — asking about the living room returned the bedroom's reading
as the only evidence. A conflict now requires the two memories to lead
with the same subject, and the subject is the first content word rather
than the first word, so 「The router forwards 220 packets」 still leads
with its router behind the article.

The rule trades one error for another, and both directions are measured
and pinned: a qualifier on the subject reads as a different thing, and
the first number under a label is the value that gets compared. Neither
hides a memory — each leaves a disagreement unrecorded for a person to
supersede by hand.

Six review findings, all measured before being changed:
- the archive rule string hid that an unset importance archives too
- a never-archived id reported {"restored": 1} while nothing moved
- the suppression condition (both sides in the page) was undocumented
- a determinism claim had no reproducible path, two latency numbers were
  never committed, and one cited test name did not exist

Gates: 374 passed, six acceptance files 73 passed, ruff clean, mypy cold
cache 24 errors in 9 files (the recorded 9cb46c1 baseline, net 0),
pyright 0 on the touched files, go build/vet/test + gofmt clean, npm
bundle unchanged, product audit clean, MCP smoke passing across processes.

backend/src/ely_eye/retrieval.py

@@ -185,7 +185,10 @@ class RetrievalService:
 
         Both memories stay in the store and this only filters the page; the conflict row names
         which side was dropped and why. Settling is the holder's call, and until it happens the
-        newer statement is what a reader should be shown.
+        newer statement is what a reader should be shown. Only a pair seen whole is settled: the
+        page is ranked from a window wider than itself, so both sides normally arrive together,
+        and an answer that never recalled the newer memory leaves the older value standing —
+        stale, but not silently contradicted by nothing.
         """
         losers = lifecycle_store.losing_sides(self.db, [hit.atom.atom_id for hit in hits])
         if not losers: