[FIX] Stamp 16 superseded trackers; harvest the rule one of them carried

The record is updated where information ARRIVES and never where a reader LOOKS.
Three instances found the same day, each with the correct information already
written down elsewhere:

  REVIEWED-81 (AUTHORIZED 07-28)      -> PENDING-81 still reads open
  the ARC open-work register, which   -> those 6 trackers still read live
    says in its own description that
    it supersedes them, with a
    per-file verified verdict
  register entry A2: "the content     -> register entry B3, one page below:
    half (B3) is now unblocked +         "[OPEN - gated on A2]"
    started" (06-17)

The third is the sharpest: both halves sit in the SAME document, so no tooling
gap explains it. ~/CLAUDE.md already rules this under Memory Discipline
("mark the superseded record as superseded"); the rule is being applied to facts
and not to trackers, PENDING items or register entries, which are also facts
about state.

Executed under steward authorization, arrears only:
- 16 trackers stamped `superseded_by:` + `superseded_on:` AND a visible in-body
  banner. The banner is the point — metadata alone repeats the defect, since the
  finding is about what a reader sees. 9 obsoleted by the 2026-07-07 MemPalace
  wind-down; 7 already carrying the register's own verified `DONE-retire`.
- B3's label corrected, with the two-month error left visible rather than
  silently amended.
- Nothing moved, renamed or deleted: 381 pointers resolve, 0 dead, 0 mis-authored.

HARVESTED BEFORE STAMPING, and this is why the harvest came first:
`project-mempalace-library-incremental-remine-strategy` carried a steward-verbatim
rule that is instrument-independent — never run a single multi-day index; order by
criticality; gate each tranche on READBACK, not on write-success (933,576 drawers
once stored successfully and could not be read back at all). It lived only inside
a MemPalace tracker, so retiring the instrument would have retired the rule with
it. ~/CLAUDE.md names that exact hazard: "state the obligation first and the
instrument second, or the next retired tool takes a rule down with it." Now
`feedback-bulk-indexing-runs-incrementally-with-readback.md`, and it applies to
studium-engine corpus work.

Held back deliberately: 2 correctly-parked files with named dependencies, 2 named
nowhere (returned to the steward), and 39 trackers unread — recorded as a gap,
not as a finding.

Measurement note: every earlier estimate of tracker staleness was wrong, because
both mtime and git-last-commit were reset across 283 files by the 2026-06-06
normalization sweep. The honest figure excludes it: median 90 days.

Filed as PENDING-142 ADDENDUM 2 per steward direction (fold, do not file anew).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Y6t6qx7cpaCu5xGdD36u4

claude/memory/session-ledger-2026-08-17.md

@@ -5,7 +5,7 @@ metadata:
   node_type: memory
   type: feedback
   originSessionId: 81f817e9-4016-4867-ae16-a486f1e8fb46
-  modified: 2026-08-17T12:34:44.862Z
+  modified: 2026-08-17T13:23:05.853Z
 ---
 
 # Session Ledger — 2026-08-17
@@ -19,6 +19,18 @@ metadata:
   did" — the record is the fullest of the week. Third firing, third false alarm; it is the
   candidate task the steward left open for today.
 
+- **2026-08-17T~15:05 — the scoped task was not the defect.** `wrap_inside` was queued as a
+  two-valued-detector fix. Diagnosing the class first found four defects; the arity was #4 and
+  the cause was a UTC/local time-base mismatch (+7201 s against a 900 s tolerance). Proven by
+  old-vs-new on the reconstructed wake instant: fixing only the scoped item would have shipped a
+  fix that left the alarm firing.
+- **2026-08-17T~15:25 — nearly reported 50 stale trackers off mtime.** Fifty files sharing
+  *exactly* 72.3 d is a bulk operation, not fifty edits. Checked git: it agreed with mtime, so the
+  bulk-touch suspicion was **refuted** — and then the commit itself turned out to be
+  `3f9a89b`, a 283-file normalization sweep that reset *both* signals. Third and fourth instances
+  in one day of an instrument whose subject is adjacent to the claim. The honest measure is the
+  last commit excluding the sweep.
+
 ## What held
 
 - The wake read every claim it reported against the substrate rather than relaying the digest:
@@ -46,6 +58,15 @@ metadata:
 
 ## Authorization moves
 
+- **2026-08-17 — steward authorized Groups A+B stamping, harvest first**, and directed the general
+  finding be folded into PENDING-142 rather than filed as a new item. Executed: rule harvested to
+  `feedback-bulk-indexing-runs-incrementally-with-readback.md` **before** any stamp; 16 trackers
+  stamped `superseded_by` + visible in-body banner; B3's label corrected with the two-month error
+  left visible. Nothing moved, renamed or deleted — 381 pointers still resolve, 0 dead.
+- **Held back from the same act:** Group C (2 correctly-parked files, named dependencies) and
+  Group E (2 files named nowhere — returned to the steward). The 39 unread trackers are recorded
+  as a **gap, not a finding**.
+
 ## Sub-agent dialogues
 
 ## Bypasses