architecture-bootstrapping

To debug Madoc TS startup failures, inspect the primary entrypoints starting with index.ts to trace the bootstrap flow, then follow server.ts and app.ts to identify where server composition or wiring breaks during initialization.

SSR wiring in Madoc TS is configured through server.ts, app.ts, and router.ts, which connect frontend and server entry points while preserving SSR tokens. You must inspect these files and SSR templates to validate integration.

To introduce top-level middleware in Madoc TS, modify the server composition in app.ts or server.ts, ensuring you preserve existing middleware order. Trace the bootstrap flow from index.ts first to understand the current wiring sequence.

Yes, you can wire new services at boot in Madoc TS by modifying the startup flow. Inspect index.ts for the bootstrap sequence and adjust routing and SSR integration points in router.ts to safely connect the new service.

The best way to trace request flow in Madoc TS is to review router.ts for routing setup, then follow the connection to app.ts and server.ts. This maps the server composition and shows how requests move through the SSR entry points.

Changing middleware order breaks SSR integration because Madoc TS boot-time wiring depends on a specific sequence in server.ts and app.ts. Preserving middleware order ensures SSR tokens remain valid across frontend and server entry points.