Finalize repo-scoping runtime rename

workplans/RREG-WP-0017-finalize-repo-scoping-rename.md

@@ -0,0 +1,98 @@
+---
+id: RREG-WP-0017
+type: workplan
+title: "Finalize Repo-Scoping Rename"
+domain: capabilities
+repo: repo-scoping
+status: done
+owner: codex
+topic_slug: foerster-capabilities
+created: "2026-05-15"
+updated: "2026-05-15"
+state_hub_workstream_id: "dbeae3c5-74fc-46c0-be61-1bd8d81e65df"
+---
+
+# Finalize Repo-Scoping Rename
+
+The repo has already moved from the old `repo-registry` product name to
+repo-scoping, but the implementation still exposes several legacy names. That
+leaked into self-registration: metadata extraction preferred package metadata,
+so a checkout could still be registered as `repo-registry` even when the
+repository path and current project identity are `repo-scoping`.
+
+Because this repository has not entered production use, there is no need to keep
+old names as compatibility aliases. This workplan removes the legacy runtime
+names and makes repo identity follow the repository source first.
+
+## T01: Prefer Repository Source Identity
+
+```task
+id: RREG-WP-0017-T01
+status: done
+priority: high
+state_hub_task_id: "2e0dbb87-e095-4e46-a37e-b54860b1f14d"
+```
+
+Repository registration should derive the default repository name from the
+submitted checkout path or URL before falling back to package metadata.
+
+Acceptance criteria:
+- A local checkout under `repo-scoping` registers as `repo-scoping` by default.
+- Package names still provide a fallback when the source path has no meaningful
+  repository identity.
+- Regression coverage protects the priority order.
+
+Implementation note 2026-05-15: metadata extraction now uses a non-generic
+checkout path or URL slug before package and README names. This prevents a
+source checkout named `repo-scoping` from being registered as an old package
+name, while still allowing package metadata to fill generic temporary checkout
+names such as `repo` or `checkout`.
+
+## T02: Remove Legacy Runtime Names
+
+```task
+id: RREG-WP-0017-T02
+status: done
+priority: high
+state_hub_task_id: "d7fefaa5-1dc0-4817-a13c-2bada32a86c7"
+```
+
+Rename the package, environment variables, default database path, commands,
+documentation, and non-historical implementation references from
+`repo-registry` / `repo_registry` / `REPO_REGISTRY` to
+`repo-scoping` / `repo_scoping` / `REPO_SCOPING`.
+
+Acceptance criteria:
+- The import package is `repo_scoping`.
+- Runtime configuration uses `REPO_SCOPING_*` environment variables.
+- The default local database is `var/repo-scoping.sqlite3`.
+- No compatibility shim remains for the old pre-production name.
+
+Implementation note 2026-05-15: renamed the source package to `repo_scoping`,
+updated imports, CLI entry points, settings, self-scoping release metadata,
+candidate source seeds, and docs. The local editable install now exposes the
+`repo-scoping` distribution and the `repo-scoping` console script imports
+`repo_scoping.cli`.
+
+## T03: Validate And Capture The Rename
+
+```task
+id: RREG-WP-0017-T03
+status: done
+priority: medium
+state_hub_task_id: "70b29772-67ac-4074-988a-4caf2411b7b1"
+```
+
+Update tests, docs, and self-scoping fixtures affected by the rename, then run
+the relevant regression suite.
+
+Acceptance criteria:
+- The full test suite passes.
+- The State Hub sync accepts the workplan and task status.
+- Remaining historical `repo-registry` references are limited to completed
+  historical records or old assessment artifacts.
+
+Implementation note 2026-05-15: full regression suite passed with 190 tests.
+The only remaining tracked old-name reference outside historical assessment and
+workplan records is a deliberate metadata regression fixture proving that the
+new source-identity priority overrides an old package name.