ADR-0055/revenue/009 local-only owner result, coordinator01a0e095-f279-7fd0-a8ef-92ce8f9547fc/local. Both008 failed stages remain retained with zero aliases. OriginalDjpz/source5417 remains production with allsix original aliases, five enabled cron schedules and38business environment/settings preserved. Recovery packet008 includes naturally scheduled baseline reservation-job HTTP200 after restoration, no triggered cron/business request.
Concrete cause: generated Turbopack external package aliases were present in source-build .next/node_modules symlinks, but absent in artifact entries and function maps. Actual compiled code imports pg-587764f78a6c7a9c, @prisma/client-2c3a283f134fdcb6 and, for diagnostic, @prisma/adapter-pg-994324666b79ccf3. Production008 observed missing pg on the signed diagnostic POST500 and an existing scheduled cleanup cron500. Local original entrypoint isolation independently reproduces missing generated aliases.
Minimal correction changes only function filePathMap configuration in local copies, assigning each generated alias file to its existing canonical package target. All original008 regular bytes and symlinks remain preserved, compiled/source/shared runtime bytes unchanged, actual fivecrons preserved. Cleanup requires two generated aliases, diagnostic three, verified against actual source-build symlinks.
Native Linux ARM64 Node24.13.0: two negative original compiled initialization cases (cleanup entrypoint and diagnostic lazy backend) fail on omitted aliases; six corrected positives (diagnostic and allfive existing cleanup cron entrypoints) load with44 compiled Prisma models, null error and no ancestor dependency fallback/outside resolutions or network attempts. No route handler or SQL invocation. This is package initialization proof, not production serving readiness or business validation.
Evidence docs/adr0055/serving-alias-fix-009 includes exact original/corrected manifests, configuration deltas, native cases, provenance and harnesses. Root sole publisher/indexer. No009 deployment, production mutation, key, signature or canonical diagnostic POST. Original008 one-request HTTP500 result remains unchanged and integrated004 remains held pending coordinator disposition.