PNEX-IN-0001 closed: source inventory key flex-auth -> access-engine

The inventory resolves sources as sibling checkouts named by key; the checkout is
now access-engine. Four metadata-pending dispositions and four ADR-review rulings
re-keyed; no published lineage references the old key.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: sonnet
Assistant-Process: 101414@bnt-lap001
Assistant-Session: 60b5a221-d435-42b9-b778-983c90c7eed6

intakes/intakes.md

@@ -6,7 +6,7 @@
 id: PNEX-IN-0001
 kind: intake
 title: "flex-auth → access-engine repository rename: source-inventory remote URL"
-status: open
+status: closed
 origin: cross-repo
 origin_ref: FLEX-WP-0020
 priority: low
@@ -32,3 +32,13 @@ tests pass; `source-audit` fails on 11 unreviewed sources from other repos
 flex-auth/access-engine, so it is not caused by this change. A full re-ingest
 (`source_inventory.py refresh`) would pull in those dispositions for review, so it
 stays open until that review is done.
+
+**Closed 2026-09-30:** source inventory now keys the repository as `access-engine`
+(config key, 4 `source-inventory.json` dispositions, 4 `docs/adr-review/rulings.json`
+rulings), because the tool resolves each source as a sibling checkout named by its key
+and `~/flex-auth` was removed. No published document names `flex-auth` as `source_repo`
+(all four ADRs are `metadata-pending`), so no release or lineage is rewritten. Evidence:
+25 unit tests pass and everything compiles; `source_inventory.py check` fails only on the
+same 11 unreviewed sources from net-kingdom (7), railiance-platform (2), railiance-master
+(1) and the-custodian (1), none from flex-auth/access-engine. Those belong to policy-nexus's
+own review backlog.