v0.17.8 — backend image that could not boot (fix)

Fix for v0.17.7

The v0.17.7 backend image could not start. It failed with:

Error: Cannot find module '/app/server/dist/server/src/app.js'

Production was rolled back to 0.17.6. If you pulled slimatic/zakapp-backend:0.17.7, it does not run — use 0.17.8.

What happened

Nothing in the build configuration changed. server/tsconfig.json leaves rootDir unset, so TypeScript derives the output layout from the longest common path of the compiled sources:

• Through v0.17.6, server/src/routes/zakat.ts imported ../../../shared/src/constants, which pulled a shared directory into the program. The common root was therefore the repo root, and output landed at dist/server/src/app.js — where npm start looks for it.
• The API-honesty fix pointed that import at the @zakapp/shared package. The shared directory left the program, the common root became server/src, and output silently moved to dist/src/app.js.

A one-line import correction relocated a build artifact, and the container failed at startup with a module-resolution error rather than a build failure.

The fix

rootDir: ".." pins what was previously emergent and reproduces the v0.17.6 layout exactly. The build now asserts the entry point exists, so this class of break fails the build instead of producing an image that cannot boot.

Everything from v0.17.7 is included

The export data-loss fix, the API validation fixes, session revocation on logout, and the restore fix all carry forward unchanged. If you exported your data on a version between the value rename and v0.17.7, re-export after upgrading — asset values were omitted from those files.