feat: implement server platform externalization plan

[Copilot]

• Step 1: Create libs/server-platform and move server composition from apps/api/src/app/app.ts
• Step 2: Introduce ServerPlatformPlugin contract and plugin registry
• Step 3: Refactor apps/api/src/main.ts to bootstrap-only host
• Step 4: Extract pages routes and store into libs/plugins/pages/server
• Step 5: Add paired WebPlatform extension in libs/plugins/pages/ui
• Step 6: Move pages migrations to plugin package
• Step 7: Keep auth/session store (including store.ts) in core package
• Step 8: Add contract tests for pages DTOs and error responses
• Fix: Remove .js extensions from relative imports in libs/server-platform and libs/plugins/pages/server (switched to moduleResolution: "bundler" + module: "esnext" in lib tsconfigs)
• Fix: Loosen pinned fastify version to ^5.8.3 in apps/api and libs/server-platform; remove "type": "module" (CJS) from new server libs

[ksojecki]

Dependencies in applications and libraries should have loose version to avoid problems with reusing packages

[Copilot]

Fixed in 06a28ae — fastify now uses ^5.8.3 in apps/api/package.json and libs/server-platform/package.json. All other external deps in the new packages also use caret (^) ranges.

[ksojecki]

I do not like imports with .js. You can try to adapt this library to be compliant only with node. Or find other solution

[Copilot]

Fixed in 06a28ae — switched the new server-side libs (libs/server-platform, libs/plugins/pages/server) to "module": "esnext" + "moduleResolution": "bundler" in their tsconfig.lib.json. This removes the NodeNext requirement for explicit .js extensions on relative imports. Also removed "type": "module" from their package.json so they are treated as CommonJS at runtime.

[ksojecki]

I preferred to have type instead of type.js

[Copilot]

Fixed in 06a28ae — all .js suffixes removed from relative imports across libs/server-platform and libs/plugins/pages/server (including the ./types.js side-effect import in session/index.ts).

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/FiloSottile/mkcert/releases/latest
  • Triggering command: /opt/hostedtoolcache/node/24.14.1/x64/bin/node /opt/hostedtoolcache/node/24.14.1/x64/bin/node /home/REDACTED/work/rod-manager/rod-manager/node_modules/mkcert-cli/cli.js -o .cert -k localhost-key.pem -c localhost-cert.pem --host localhost --host 127.0.0.1 --host ::1 (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)