⭐ Package Manifests

All 43 package.json files, each individually inspected and transformed — not scripted blind. That's 40 real Yarn workspace members (directus, app, api, sdk, packages/*, tests/* — the exact set yarn workspaces list resolves) plus the root manifest plus 2 non-workspace test fixtures nested under tests/blackbox/extensions/ (real files, not Yarn-resolved). Full detail: todo.md's "Package manifest migration" section.

Group	Count	Packages
Core runtime	3	sdk, api (~130 catalog: refs alone), app
Extension system	4	extensions, extensions-registry, extensions-sdk, create-directus-extension
Storage drivers	7	storage + azure/cloudinary/gcs/local/s3/supabase
Core shared utilities	19	ai, composables, constants, env, errors, format-title, memory, pressure, schema, schema-builder, specs, stores, system-data, themes, types, update-check, utils, validation, visual-editing
Remaining tooling	2	create-directus-project, release-notes-generator
Test projects	6	blackbox (+ its 2 non-workspace extension-fixture manifests), e2e, mock-license-server, sandbox
CLI (full source, not just manifest)	1	directus

Attribution sweep, done twice — the first pass used a placeholder GitHub username (terrence-daniels) that turned out not to be the real authenticated account (caught via gh auth status before anything was pushed); corrected across 48 files to Terrence721. author/maintainers/contributors fields (28 files) swept to this fork's own attribution — the MSCL license's Copyright ... Monospace Inc. text was deliberately left as-is.