Run sync_spec_content.py for openregister retrofit cohort

[WilcoLouwerse]

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 consolidation
• hydra#223 — `/opsx-verify --app` mode + skill updates
• .github#38 — playbook updates

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.

[WilcoLouwerse]

Context — closing OpenRegister retrofit DoD

This issue is the final hand-off step to close ConductionNL/.github#33. The 2026-05-04 audit + cleanup work landed today across three PRs that are pending review:

Repo	PR	Scope
openregister	#1425	Naming convention rename to retrofit-{YYYY-MM-DD}-{descriptor} + .opsx-ignore + archive consolidation
hydra	#223	/opsx-verify --app mode + cohort classifier + skill updates
.github	#38	Playbook updates: naming, .opsx-ignore, App Mode, documentation-only retrofits

Sequence:

1. Wait for openregister#1425 to merge — that's the one that puts the OpenRegister retrofit cohort into its final on-disk shape (renamed folders, standardised frontmatter, etc.).
2. Pull development locally; the master specs at openspec/specs/{cap}/spec.md should now carry the cohort flags listed in the table above.
3. Run the sync (your machine has the concurrentie-analyse repo cloned):

   cd ~/concurrentie-analyse
   python3 scripts/sync_spec_content.py openregister

4. Confirm Specter app_specs.retrofit_extensions populated for the 9 retrofitted capabilities (8 from the table above + chat-ai which carries retrofit: true).
5. Comment on Complete Openregister retrofit — Tier 1 Bucket 2a reverse-specs #33 with the row count + sync timestamp, then close Complete Openregister retrofit — Tier 1 Bucket 2a reverse-specs #33. This issue (Run sync_spec_content.py for openregister retrofit cohort #39) closes alongside.

The 3 documentation-only retrofits (notificatie-engine, schema-hooks, tenant-isolation-audit) intentionally don't have cohort frontmatter — they add no new REQs to their capability. Specter should not flag them as cohort. If the sync output shows entries for those three, something's wrong; otherwise expect exactly 9 cohort rows for openregister.

No code or documentation changes are needed in this issue — pure operational hand-off.

[rubenvdlinde]

Closing as effectively done. Parent #33 (Openregister retrofit Tier-1 Bucket 2a) was closed 2026-05-07, and the retrofit cohort cleanup landed via openregister#1350 (Bucket 2a/2b reverse-spec + annotate, 16 commits / ~380 methods). If a separate sync_spec_content.py run is still genuinely outstanding, please reopen with a fresh checklist.