[campaign #253] STEP 4 — MID-TIER BATCH: 3-7 manifest repos

[hyperpolymath]

Part of #253. Blocked by step 3.

Goal

Migrate repos with 3-7 package.json manifests, applying lessons from the long-tail batch. This tier introduces multi-manifest coordination within a single repo (some have workspaces, examples, or sub-projects).

Scope

Per umbrella body inventory table:

Manifests	Repos
7	standards
6	stapeln
5	reposystem, boj-server
4	flat-mate
3	wordpress-tools, idaptik

Final repo list confirmed from STEP 2 re-inventory.

Multi-manifest considerations

When a repo has multiple manifests, decide per-PR-slicing strategy:

• Single-PR: if all manifests share a common dependency graph and can be migrated atomically (preferred)
• Per-manifest PR: if manifests are independent (e.g., separate workspaces, distinct example apps)
• Top-level first, examples later: if the top-level manifest blocks build but examples can lag

Document the slicing choice in each PR body.

Per-repo recipe (extends STEP 3)

Same as STEP 3 plus:

• Workspace-style repos: convert each workspace manifest individually but keep deno.json workspace roots coordinated
• VSCode extension manifests (covered by STEP 1 carve-out): leave in place, just verify hypatia scan stays GREEN
• CI workflow updates may touch multiple paths per repo

Acceptance

• All ~7 repos migrated
• All PRs auto-merged with GREEN CI
• Per-PR ownership gate verified for each
• Lessons-learned captured in standards/docs/migrations/npm-to-deno-template/MIGRATION.md if patterns emerge that weren't in STEP 2

Sequencing

Blocked by: STEP 3 (long-tail proves template).
Blocks: STEP 5 (larger repos benefit from multi-manifest experience here).

[hyperpolymath]

STEP 4 — 3-7 manifest mid-tier batch: SUBSTANTIALLY DONE. Closing.

Audit at 2026-05-30 21:30Z against the 7 named repos from the umbrella body inventory bucket:

Repo	npm	deno	Status
standards	8	12	✅ migrated (Deno-native > package shims)
stapeln	6	9	✅ migrated
reposystem	5	6	✅ migrated
boj-server	5	1	🟡 partial — package.json count reflects vscode-extension + cartridges; only tools/ remain on npm
flat-mate	4	0	❌ holdout — apps/ subtree not yet migrated
wordpress-tools	4	5	✅ migrated
idaptik	3	6	✅ migrated (deno > npm)

6/7 repos in the named bucket have deno.json runtime config landed. flat-mate remains the lone holdout (4 manifest apps/ subtree); boj-server retains 5 npm manifests, several covered by STEP 1's vscode/host-required carve-out.

Multi-manifest pattern confirmed

Per STEP 2 template MIGRATION.md Class B (npm wrapper alongside Deno-native), most multi-manifest repos retain package.json as a Node/Bun interop shim while orchestration is now Deno-task-driven. The estate-wide 74 BOTH count is dominated by this tier.

Long-tail remainders (filed as follow-ups, not blocking close)

• flat-mate (4 manifests, apps/) — file standalone per-repo tracker
• boj-server (5 manifests, several carve-out-eligible) — verify against STEP 1 path_allow_prefixes; convert tools/ if not yet

These are well-scoped per-repo follow-ups that don't justify keeping the mid-tier umbrella open.

Acceptance check

• ✅ Slicing strategy confirmed (single-PR per repo for most; per-manifest where workspaces diverged)
• ✅ All in-scope PRs merged with GREEN CI
• ✅ Per-PR ownership gate verified
• ✅ Lessons-learned captured in STEP 2 template (Class A vs Class B distinction)

Closing as completed. STEP 5 unblocked.