[HARDENING] FIX-lane check-in held and recorded; deferral re-based, half of it uncheckable

REVIEWED-85's provisional review, 30 days overdue and gating PENDING-173's
build and PENDING-177's typography gate, was held by steward and jurist
today. Outcome recorded in the index; the deferral block is discharged
with `resolved:` rather than deleted, and the drift-check now reports
0 COME DUE where it reported 1.

Item 1 — EXTENDED PROVISIONAL. The lane has been exercised by the
executor exactly once in thirty days, so n=1 settles nothing in either
direction. The 2026-08-08 Instruments entry is ratified on the merits as
class (i) and its procedure recorded as defective — executor-classified
under an authorization already lapsed into overdue-review, against the
lane's own instruction. Explicitly not precedent.

Item 2 — NOT DISCHARGED, and answered with two fresh failures rather than
a confirmation: REVIEWED-67's census and typography gate did not reach the
PDF lane in 42 days, at a measured cost of verify_conversion returning
5/5 PASS on word-damaged output.

Two things are recorded as gaps rather than closed:

- The re-based trigger is only half machine-checkable. The check-in was
  re-based from time to use precisely because a date trigger fired twice
  with nothing recorded, but the schema's vocabulary is glob/path-exists/
  date/manual and a use count is not expressible. The block carries the
  backstop date only; the use-count half sits in `discriminator:`. No
  proxy was invented — a glob over the index's rows would have fired on
  ruled and steward-instructed entries alike and looked machine-checked
  while counting the wrong thing, which is the schema's own stated reason
  for `manual`.

- Item 2's remedy is not placed. "What standing rule already governs the
  class I am about to route?" is a verification-ladder entry by shape,
  and the ladder is under REVIEWED-123's general freeze. Wrap or wake
  would accept it but fire at the wrong moment — the failure happens at
  adoption. Flagged rather than put somewhere it would be decorative.

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

PENDING.md

@@ -6525,8 +6525,20 @@ Two things follow, and they point opposite ways. **The check fired correctly**
      since: 2026-08-02
      trigger: date 2026-08-02
      owner: steward
+     resolved: 2026-09-01 — check-in held, steward + jurist; outcome EXTENDED PROVISIONAL, recorded at claude/memory/skill-harvest-fix-lane-index.md §FIX-LANE CHECK-IN
 -->
 
+<!-- DEFERRED-DECISION: fix-lane-checkin-2
+     since: 2026-09-01
+     trigger: date 2026-12-01
+     owner: steward
+     discriminator: the executor-classification rows in claude/memory/skill-harvest-fix-lane-index.md — the check-in is due at 5 of them, or on the backstop date, whichever is first
+-->
+
+⚠ **The re-based trigger is only HALF machine-checkable, and the unchecked half is the one the re-basing was for.** The 2026-09-01 check-in re-based the trigger from time to **use** — *next check-in at 5 executor classifications, backstop 2026-12-01, whichever first* — because the date trigger fired twice with nothing recorded and a use-count cannot be missed by being busy. **The schema's trigger vocabulary is `glob | path-exists | date | manual`; a use count is not expressible in it.** The block above therefore carries the **backstop only**, and the use-count half is recorded in `discriminator:` where a reader will find it.
+
+**No proxy was invented, deliberately.** The schema's own comment says `manual` exists so a deferral whose condition cannot be mechanised is *listed rather than checked*, "instead of inventing a proxy — proxies are what failed here." A `glob` over the index's table rows would have fired on any row, including the ruled and steward-instructed ones, and would have looked machine-checked while counting the wrong thing. **⇒ Until the schema can express a count, this deferral's primary condition is honoured by a human reading the index.** That is the state, stated, rather than the appearance of coverage.
+
 The block is filed with a trigger date **already in the past**, deliberately, so the drift-check reports it **DUE on the next run** rather than quietly waiting. Agenda is already written and needs nothing from the executor: `skill-harvest-fix-lane-index.md` §*Check-in agenda* carries both items, the second folded in by REVIEWED-86 Q4 (*the record is not just written, it is read*).
 
 **Consequence adopted for this session, before the finding was convenient.** Today's one harvest candidate — the `daybook-ensure.py` SKELETON missing the `## <Project>` heading `/wrap-up` §7.5 specifies — is filed as a **[PROPOSAL] in the skill-harvest register, not applied through the lane**, on the lane's own suspension rule. It would otherwise have been a clean FIX with an exact 2026-08-24 precedent.