Missing or uncertain in State Hub by simple name/remote matching:
-`audit-core`
-`binect-chrome`
-`binect-js`
-`coordination-engine`
-`direkt-vermittlung-de`
-`polycode-sim`
-`ralph-workplan`
-`repo-seed`
-`shard-wiki`
-`tele-mcp`
-`testdrive-jsui`
-`timeline-svg`
-`vantage-point`
These may be intentionally unregistered, registered under aliases, or outside
current State Hub ownership. They need review before cutover so no repository is
lost or left with an untracked remote.
## Feature Classification
| Feature | Observed state | Migration class |
| --- | --- | --- |
| Git repositories | 49 public repos in `coulomb` org | Automatic plus verification clone/push for sample repos. |
| Issues | Enabled on all visible repos; open issues at least on `markitect-main`, `kaizen-agentic`, `binect-chrome` | Must preserve or explicitly classify unsupported. |
| Wiki | Enabled on all visible repos | Must verify actual wiki content per repo with credentialed or git-based check. |
| Releases | Enabled on all visible repos | Must preserve release records and assets where present. |
| Packages | Enabled on most repos; disabled on a few older/template repos | Must verify actual package data with authenticated API or storage inspection. |
| Actions | Enabled on most repos; disabled on `repo-seed` | Must verify whether workflows/runners are actually in use. |
| Pull requests/projects | API reports pull requests and projects enabled on visible repos | Must include in migration drill result matrix. |
| Users/org/team membership | Not safely inventoried from public API in this pass | Requires authenticated admin inventory. |
| Deploy keys/SSH keys/tokens/webhooks | Not inspected | Requires authenticated admin inventory; cannot be inferred from public repo fields. |
| LFS/attachments | Not inspected | Requires authenticated API/storage inventory and restore drill. |
| SMTP/account recovery | Not inspected | Covered by T06; requires approved test account and mail path. |
## Immediate Gaps Before Probe or Cutover
1. Resolve WP-0005 T02 production choices before creating durable Forgejo
manifests.
2. Complete an authenticated Gitea admin inventory for users, teams, deploy
keys, SSH keys, access tokens, webhooks, packages, LFS, attachments, and
actual wiki/release asset contents.
3. Decide whether the 13 missing/uncertain Gitea repos should be registered in
State Hub, archived, or explicitly excluded from migration.
4. Fix host preflight drift observed by `make status`:
-`CoulombCore` UFW reported inactive.
- Both `CoulombCore` and `Railiance01` reported `PasswordAuthentication yes`.
5. Establish a backup target and restore drill before migrating any production
repository data.
6. Keep legacy Gitea as source of truth until Forgejo probe and restore checks
pass.
## Current T01 Status
This first pass satisfies the public and infrastructure metadata part of T01.
T01 should remain open until the authenticated admin inventory and missing repo
