---
id: REUSE-WP-ADHOC-2026-10-16
type: workplan
title: "Refuse owner/index drift in the existing native registry validator"
domain: infotech
repo: reuse-surface
status: finished
owner: codex
created: "2026-10-16"
updated: "2026-10-16"
flavor: implementation
state_hub_workstream_id: "803c5bb3-12c5-51be-9852-c6719f7c80fd"
---

## Refuse owner/index drift in the existing native registry validator

```task
id: REUSE-WP-ADHOC-2026-10-16-T01
status: done
priority: medium
state_hub_task_id: "63c0e025-f7aa-5849-ac2f-61128ceb7a0e"
```

The existing strict validator accepted stale index metadata and duplicate IDs/paths. Extend its existing parity warnings and add native CLI regression tests, including malformed frontmatter/index shape without tracebacks. Existing mandatory Forgejo validation consumes this source; fleet adoption and hosted freshness are unverified.

Completed 2026-10-16 under the founder's NetKingdom target implementation demand
(CUST-WP-0080, TSA-11). Source review and exact before/after native CLI evidence:
`the-custodian/docs/changes/netkingdom-target-2026-10-16/improvement-loop-next/`.
The current 60-provider cohort has all 70 reviewed IDs exactly once; 3 field
mismatches across 2 capabilities become zero with the source corrections.
Native hosted refresh/readback and the accepted Activity/rein schedule remain
separate gates. No production change, model call, credential access or external
message was performed.

Validation and publication checkpoint, 2026-10-16: 23 new native CLI cases
passed, covering projected fields, duplicate ID/path, vector whitespace,
malformed frontmatter and unvalidated index row shapes. Root independently
reviewed source and passed all 30 parity/native-registry cases across its
initial run and three required filesystem-approved reruns. The failed sandbox
writes remain failed observations, not source defects. All three affected owner
strict validations pass. Source commit `dd00b27` was published by the normal
`statehub fix-consistency` backlog push; no manual push was used. Its automatic
brief-only writeback was refused by the unchanged generated-only guard. This
source record retains the issued workstream/task bindings; generated artifacts
are not bundled to evade that refusal. Hosted readback remains outstanding.