[HARDENING] PENDING-171: provenance marker, per the jurist ruling §6

The item and commit 5ba5842 were filed by a worker the daemon respawned after
the upgrade, with no human in the loop. Marked, not voided — the findings are
checkable on the substrate and PENDING-173 already relies on one. The item is
not to be ruled while the marker is absent.

Declares two things rather than performing them silently: the commit cannot
carry its own marker without rewriting history (PENDING-164's subject), so the
register carries it; and four sibling blocks from the same unattended run remain
unmarked, which is misleading in the same direction and is owed a word.

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

PENDING.md

@@ -6467,6 +6467,12 @@ Two things follow, and they point opposite ways. **The check fired correctly**
 ## PENDING-171 — The prior-art census cannot see three of the steward's repos, and its positive controls could not have caught it
 **Date:** 2026-08-31
 **Tag:** [HARDENING]
+
+**⚠ PROVENANCE — inserted 2026-08-31 by the executor, under the jurist ruling of 2026-08-31 (REVIEWED-131 draft §6), per no-silent-revision. Nothing else in this item is altered.** This item, and commit `5ba5842` which it describes, were filed by session `b7e7eb39` / background job `acaabadf` — **a worker the daemon respawned after a binary upgrade, which took its turn with no human in the loop.** The mechanism is PENDING-172. The ruling directs **provenance-mark, not void**: the findings here are checkable against the substrate independently of who filed them, and PENDING-173 has already relied on one of them. **This item is not to be ruled while this marker is absent** — an unmarked record does not say on its face what it is, which is PENDING-110's complaint at a new site.
+
+**⚠ The commit cannot carry its own marker.** Amending `5ba5842`'s message means rewriting history, which is PENDING-164's own subject. The register carries the marker on the commit's behalf, and that substitution is declared here rather than performed silently.
+
+**⚠ THE SIBLINGS ARE UNMARKED, AND THAT IS NOW MISLEADING.** The same session, in the same unattended run, also filed **PENDING-164 AMENDMENT 2** (L6431), **PENDING-168 ADDENDUM 1** (L6504) and **PENDING-104 ADDENDUM 2** (L6533), and wrote `MEMORY.md`'s Active Session block and `session-2026-08-31-the-270-got-read-and-the-population-was-wrong.md`. The ruling names only this item and the commit. Marking one block of five leaves a reader to infer the other four were human-in-loop, which is **worse than marking none**. The executor has not marked them, because editing placed records beyond what was directed is not its call; this is filed as the gap it is, and is owed a steward or jurist word.
 **Summary:** `prior-art.py`'s `owned_repos()` decides ownership by testing each repo's remotes against `OWNED_HOSTS = ("github.com/davidglidden", "davidglidden/", "git.skemantix.com")`. That matches an account name *inside a remote path*, which is not the relation it claims to compute. `_Dev/CapableMind-AI`, `_Dev/BetterMemories.io` and `_Dev/be` all fail it. **The census population is 362, not the 270 AMENDMENT 1 reported.**
 
 **Measured 2026-08-31:**