Context
Final step to close ConductionNL/.github#33 (OpenRegister retrofit DoD).
The retrofit cohort cleanup PRs are landing this session:
After those merge, the OpenRegister retrofit cohort frontmatter (`retrofit:` / `retrofit_extensions:` on master specs) needs to be synced to Specter's `app_specs` table so dashboards filter the retrofit cohort correctly.
What to do
Wait for the three PRs above to merge, then on a machine that has the `concurrentie-analyse` repo cloned and a working Specter DB connection:
```bash
cd ~/concurrentie-analyse # or wherever it is cloned
python3 scripts/sync_spec_content.py openregister
```
Expected: exit 0, non-zero row count printed.
If sync fails with a missing-column error, run the migration first (idempotent):
```bash
python3 scripts/migrate_app_specs_retrofit.py
```
Then re-run the sync.
Verification
After the sync runs, query Specter to confirm openregister has cohort flags populated. The 9 capabilities that received new retrofit-derived REQs should appear in `app_specs.retrofit_extensions` (or `app_specs.retrofit` for cluster-style retrofits):
| Capability |
Cohort flag |
| approval-workflow |
`retrofit: true` |
| archival-destruction-workflow |
`retrofit_extensions: [REQ-009]` |
| calendar-integration |
`retrofit: true` |
| chat-ai |
`retrofit: true` |
| content-versioning |
`retrofit_extensions: [REQ-017]` |
| oas-generation |
`retrofit: true` |
| object-lifecycle |
`retrofit: true` |
| tenant-lifecycle |
`retrofit_extensions: [REQ-005]` |
| actions |
`retrofit: true` |
Three retrofit ghost changes are documentation-only patches and intentionally do not add cohort frontmatter (no new REQs):
- `retrofit-2026-04-28-notificatie-engine` (cross-cap to existing REQ-001)
- `retrofit-2026-04-28-schema-hooks` (private-helper inheritance, parent annotate tasks)
- `retrofit-2026-04-28-tenant-isolation-audit` (scanner-misclassification cleanup, methods belong to tenant-lifecycle / tenant-quotas)
So the expected post-sync state is 9 retrofit-flagged capabilities for openregister in Specter.
After sync succeeds
Comment on `#33` with the row count + sync timestamp, then close that issue.
Context
Final step to close
ConductionNL/.github#33(OpenRegister retrofit DoD).The retrofit cohort cleanup PRs are landing this session:
openregister#1425— naming convention + .opsx-ignore + archive consolidationhydra#223— `/opsx-verify --app` mode + skill updates.github#38— playbook updatesAfter those merge, the OpenRegister retrofit cohort frontmatter (`retrofit:` / `retrofit_extensions:` on master specs) needs to be synced to Specter's `app_specs` table so dashboards filter the retrofit cohort correctly.
What to do
Wait for the three PRs above to merge, then on a machine that has the `concurrentie-analyse` repo cloned and a working Specter DB connection:
```bash
cd ~/concurrentie-analyse # or wherever it is cloned
python3 scripts/sync_spec_content.py openregister
```
Expected: exit 0, non-zero row count printed.
If sync fails with a missing-column error, run the migration first (idempotent):
```bash
python3 scripts/migrate_app_specs_retrofit.py
```
Then re-run the sync.
Verification
After the sync runs, query Specter to confirm openregister has cohort flags populated. The 9 capabilities that received new retrofit-derived REQs should appear in `app_specs.retrofit_extensions` (or `app_specs.retrofit` for cluster-style retrofits):
Three retrofit ghost changes are documentation-only patches and intentionally do not add cohort frontmatter (no new REQs):
So the expected post-sync state is 9 retrofit-flagged capabilities for openregister in Specter.
After sync succeeds
Comment on `#33` with the row count + sync timestamp, then close that issue.