[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/project-arc-open-work-register.md

@@ -6,6 +6,7 @@ metadata:
   type: project
   permalink: claude-memory/project-arc-open-work-register
   originSessionId: b85f1094-0658-47b4-a0ba-7a4323383aa9
+  modified: 2026-08-17T13:22:01.355Z
 ---
 
 # ARC open-work register
@@ -27,7 +28,7 @@ metadata:
 
 - **B1. Glimpse location + title cleanup.** `[OPEN — steward manual]` **[verified]** — steward does this by hand (2026-06-11). 193 live glimpses; **4 lack `location:` frontmatter**; titles need a cleanup pass. NB the glimpse *rendering* bugs (phone full-bleed, no-vessel) were fixed + deployed in Stage M — this is content/metadata, not code. Absorbs the residual of `project-arc-apparatus-refactor-todo` Tier 3 (EXIF/location for existing glimpses — now ~done).
 - **B2. Threshold-`---` promotion walk.** `[OPEN — steward content track]` — apply the 2026-06-07 differentiated-hr doctrine across existing pieces: a bare `---` at a foreword→main-text *threshold* becomes `.ornament` (dots); `---` *within the body* stays silence. Doctrine + CSS settled (§IV amended, zero CSS change); the per-piece content walk remains.
-- **B3. Ornament content migration (Option A) — the content half of A2.** `[OPEN — gated on A2; scope VERIFIED 2026-06-11]` — steward ruled Option A (2026-05-03): once the cul-de-lampe asset exists (**A2**), migrate content off the retired-ornament classes onto the canonical Close/Pause, then retire the old SCSS. **Verified scope (sizable):** ~**95 content files** carry hand-authored `<div class="ornament …"></div>` — `completion` ×51 (= the Close / end-of-piece, the cul-de-lampe's job), `section` ×50, `thought` ×14, `chamber` ×12, `musical` ×7, `hermetic` ×5, `mathematical` ×2, … Several variants (`thought`, `mathematical`) aren't even in the current CSS → they already collapse to bare `.ornament`. All retired per §IV; all await the designed asset. Not negligible, and not runnable until A2. Files: `project-arc-ornament-spec-vs-content-mismatch-pending`, `project-arc-pause-close-ornament-and-hr-audit-pending`.
+- **B3. Ornament content migration (Option A) — the content half of A2.** `[OPEN — UNGATED 2026-06-17 when A2 landed; scope VERIFIED 2026-06-11]` — ⚠ *label corrected 2026-08-17: this read `gated on A2` for two months after A2 completed. A2's own entry had recorded "the content half (B3) is now unblocked + started" on 06-17 — so the fact was known and written, just never written **here**, which is where a reader checking B3's status looks. Kept as a marker of that failure mode rather than silently amended.* — steward ruled Option A (2026-05-03): once the cul-de-lampe asset exists (**A2**), migrate content off the retired-ornament classes onto the canonical Close/Pause, then retire the old SCSS. **Verified scope (sizable):** ~**95 content files** carry hand-authored `<div class="ornament …"></div>` — `completion` ×51 (= the Close / end-of-piece, the cul-de-lampe's job), `section` ×50, `thought` ×14, `chamber` ×12, `musical` ×7, `hermetic` ×5, `mathematical` ×2, … Several variants (`thought`, `mathematical`) aren't even in the current CSS → they already collapse to bare `.ornament`. All retired per §IV; all await the designed asset. Not negligible, and not runnable until A2. Files: `project-arc-ornament-spec-vs-content-mismatch-pending`, `project-arc-pause-close-ornament-and-hr-audit-pending`.
 - **B4. Major content audit / archive of non-current files.** `[OPEN — was deferred]` — per ARC `CLAUDE.md` Known state: deferred until "the current version of the site is established; do not rearrange the content tree until that session." Stage G sealed arguably satisfies that condition now — candidate to schedule.
 - **B5. Rethink the versioning links.** `[OPEN — design reconsideration; steward-raised 2026-06-17, NOT for now]` — the steward feels something "doesn't sit right" about the version-stamp links and couldn't yet name it. Current behaviour (verified in built HTML): the piece-end stamp reads *"Begun [place] **[origin-date→/v/]** · Revised [place] [revised-date, plain]"* — the **origin date is the only link**, leading to the prior version; the `/v/` page announces "You are reading a prior version… Read current →." Executor's candidate diagnoses (offered, not settled): **(1)** the cul-de-lampe (a *completion* seal, *finis coronat opus*) and the version link pull opposite ways — the close says *done*, the link a few lines below pulls *backward* into the superseded version; adding the close may have sharpened a latent tension. **(2)** "Begun [date]" frames the link as inception/seed, but the destination is a *complete prior essay*, not a beginning — label/destination mismatch. **(3)** for pieces revised by *subtraction* (Mushi-Ken's appendix, Vespers' loudness), the linked prior is the version the author *improved away from* — disclosing *that* a revision happened is integrity, but making the discarded version the foot-of-page reading-*destination* may overreach: provenance offered as invitation. Hunch: it's #1+#3 — ADR-005 designed versioning as a *record*, but rendered as a link it behaves like a parallel reading-path, and that sits oddly under a completion mark. Revisit when the steward can name it. (Grounds: ADR-005, essay-versioning-specification.md §3–4; the version-stamp builder in `site.hs`.)