diff --git a/workplans/RREG-WP-0006-rename-to-repo-scoping-and-integrate.md b/workplans/RREG-WP-0006-rename-to-repo-scoping-and-integrate.md
index 41b4e69..e9bbd48 100644
--- a/workplans/RREG-WP-0006-rename-to-repo-scoping-and-integrate.md
+++ b/workplans/RREG-WP-0006-rename-to-repo-scoping-and-integrate.md
@@ -4,7 +4,7 @@ type: workplan
 title: "Rename to repo-scoping and Full Custodian Integration"
 domain: capabilities
 repo: repo-registry
-status: todo
+status: active
 owner: codex
 topic_slug: foerster-capabilities
 created: "2026-04-30"
@@ -36,7 +36,7 @@ Depends on: CUST-WP-0034 (delegation infrastructure), RREG-WP-0005
 
 ```task
 id: RREG-WP-0006-T01
-status: todo
+status: done
 priority: high
 state_hub_task_id: "55341e24-f936-4c74-86e4-fa084ab4a25c"
 ```
@@ -57,11 +57,15 @@ git -C /home/worsch/repo-registry push --dry-run
 Acceptance: `git -C /home/worsch/repo-registry remote -v` shows the new URL;
 a dry-run push succeeds.
 
+Implementation note 2026-04-30: The server-side Gitea repository was renamed,
+the local `origin` remote now points to `gitea-remote:coulomb/repo-scoping.git`,
+and `git push --dry-run` succeeds.
+
 ## T02: Update state-hub registration and repo path
 
 ```task
 id: RREG-WP-0006-T02
-status: todo
+status: done
 priority: high
 state_hub_task_id: "8a803b12-d991-48c7-8640-8876320815b1"
 ```
@@ -84,11 +88,17 @@ Acceptance: `GET /repos/repo-scoping/` returns the managed repo record;
 `GET /repos/repo-registry/` returns 404; `make fix-consistency` reports no
 slug-mismatch issues.
 
+Implementation note 2026-04-30: The State Hub managed repo record now uses
+slug/name `repo-scoping`, remote URL `gitea-remote:coulomb/repo-scoping.git`,
+and the existing local path `/home/worsch/repo-registry`. `GET
+/repos/repo-scoping/` returns the record, `GET /repos/repo-registry/` returns
+404, and the consistency checker passes via the State Hub virtualenv.
+
 ## T03: Update all references in the-custodian
 
 ```task
 id: RREG-WP-0006-T03
-status: todo
+status: done
 priority: high
 state_hub_task_id: "4b630593-cfd7-4313-b774-5f7eeed819ec"
 ```
@@ -116,11 +126,18 @@ Acceptance: `grep -r "repo-registry" /home/worsch/the-custodian/` returns no
 hits that refer to this repository (hits inside this workplan file are
 acceptable as historical references).
 
+Implementation note 2026-04-30: Updated Custodian workplan references in
+`CUST-WP-0034` and `CUST-WP-0033` from `repo-registry` to `repo-scoping`, and
+verified `/home/worsch/the-custodian` has no remaining `repo-registry` hits
+outside excluded generated/dependency directories. The State Hub capability
+catalog entries for `scope.generate` and `scope.update` now have provider
+`repo-scoping`.
+
 ## T04: Run first full ecosystem SCOPE.md refresh
 
 ```task
 id: RREG-WP-0006-T04
-status: todo
+status: in_progress
 priority: high
 state_hub_task_id: "3f25317f-5d4e-464c-8c76-80f61d6724d3"
 ```
@@ -146,6 +163,14 @@ Log each write as a progress event on the custodian workstream.
 Acceptance: `make check-doi` across all reachable repos reports no C5a
 failures; C5b/C5c warns are reduced to repos genuinely awaiting curator input.
 
+Implementation note 2026-04-30: Blocked for a full ecosystem refresh. The
+State Hub DoI engine still reports C5 only as file presence, so the required
+C5b/C5c structure baseline from CUST-WP-0034 is not available yet. Also,
+repo-scoping currently has approved-characteristic data for only three repos,
+so most State Hub managed repos cannot yet be generated without first being
+registered and analyzed in repo-scoping. Diff checks confirmed reachable
+curator-owned SCOPE.md files should not be overwritten wholesale.
+
 ## T05: Validate full DoI C5 pass and run consistency sync
 
 ```task
@@ -173,7 +198,7 @@ pre-workplan baseline.
 
 ```task
 id: RREG-WP-0006-T06
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "1f5ecca9-1c73-4f30-b0e7-4a065146deeb"
 ```
@@ -194,3 +219,8 @@ Then review and apply any curator-owned sections manually.
 
 Acceptance: `SCOPE.md` at repo root passes all three C5a/b/c checks; the
 one-liner accurately describes the repo-scoping utility.
+
+Implementation note 2026-04-30: Rewrote root `SCOPE.md` in the canonical
+section structure for `repo-scoping`, preserving the curated utility story,
+State Hub relationship, and `scope.generate` / `scope.update` capability
+blocks. The local `ScopeValidator` reports the file as valid.