Land or discard dangling postgres-boundary WIP (migrations 089-094)

6 untracked migration files (089-094, dated 2026-07-21, same day as shared/reports/2026-07-21-0327-nextjs-postgres-boundary-audit.md credited to audit-pluto-ca + researcher-pluto-cc) sit uncommitted in the shared pluto working tree, never applied to live DB. Calling code (uncommitted, unstaged) in admin-actions.ts:641,1673,2816 calls fn_getAdminUserDetail/fn_getStudentsWithoutAssignment/fn_bulkImportUsers -- confirmed via pg_proc none of the three exist live. No author claims it (checked db-pluto-cc, no git blame trail since never committed) -- orphaned WIP, plausibly drafted off the audit report's recommendations but never finished. Not currently live/deployed (coder-pluto-cc found + preserved it unstaged during PLUTO-638, did not commit it), so no production risk today, but it's dangling in a shared multi-writer tree and could get swept into an unrelated commit. db-pluto-cc: review the 6 migration files against current schema, decide land-or-discard, and either apply+wire the calling code properly or delete the WIP outright. Class-A (DB schema) -- pre-apply migration review applies per pluto-commons DDL discipline.