Run the test suite against both deployment modes (full and lean) in CI

[CarsonDavis]

What this does

MMGIS ships in two shapes from one codebase, selected by MMGIS_DEPLOYMENT_MODE: the full application, and a lean deployment that turns a set of server features off (geodata management, drawing, the bundled sidecar services, the on-disk mission filesystem, the link shortener, server-side raster utilities) and the dashboard publish flow on. Today CI exercises essentially one of those shapes — a change that breaks the other can pass CI and reach production.

This runs the e2e/boot suite once per shape and adds checks that verify the right features are present or absent in each mode, so a change that breaks either shape fails CI before merge. It's also the safety net for the planned (separate) gating-consolidation refactor, whose "no behavior change" claim is only trustworthy if the tests already run both modes.

Implements #151. Stacked on #149 → #150.

Changes

CI / test / docs only — no application or runtime source changed.

• CI matrix. Split the workflow into a single hermetic unit job (Vitest, no DB/browser — it already covers both modes via require-cache busting, so it isn't matrixed) and a matrixed e2e job over mode: [full, lean]. The mode is written into .env and surfaced in the job name (e2e (full) / e2e (lean)) and per-mode artifact names.
• Present/absent check (tests/e2e/deployment-mode.spec.js). A hand-written feature inventory (independent of any capability table — that independence is the point) asserting each full-only feature is reachable in full and gone in lean, and the lean-only dashboard publish flow the reverse. One loop covers both directions. Discriminator: a mounted route answers non-404; an unmounted one falls through to the catch-all 404. This step has no continue-on-error, so mis-gating a feature turns the leg red.
• Tables-exist check (tests/ci/assert-gated-tables.js). Features gated off in a mode still have their DB tables (model sync is unconditional; only route mounts are gated), so a later mode flip needs no data migration. Asserted via the same getBackendSetups + sync path the server uses.
• Honest lean leg. The lean leg disables the sidecar WITH_* flags so init-db and boot succeed without the services lean doesn't deploy (no sidecars, no spatial-catalog DB).
• Short contributor note in README.md + AGENTS.md: two modes exist; author in full first, then confirm lean.

Verification

Booted both modes locally and ran the new checks:

Check	full	lean
present/absent spec (8 features)	✅ 8/8	✅ 8/8
app boots	✅	✅ (sidecar spawner + proxy disabled, no STAC DB)
gated tables exist	✅	✅ (6 table groups, fresh DB)

Full-only routes return non-404 in full / 404 in lean; /api/deployments (publish flow) is the reverse. npx vitest run stays green (669/669).

Notes for reviewers

• One focused CI/test-coverage PR; it carries no application-code change of its own. It is the prerequisite for the separate gating-consolidation refactor (not included here).
• Merge order: stacks on Fix the stale unit tests revealed by the jsdom test-environment migration #149 → Run unit tests in a jsdom environment via Vitest #150. Merge those first.
• The legacy smoke/eventbus e2e specs keep their pre-existing continue-on-error (non-gating); only the new mode-shape and tables checks gate the build.

[amarouane-ABDELHAK]

Can we upgrade this version?

[CarsonDavis]

Question: what are the ramifications of having the lean tests be the baseline tests and then the full tests import them? will that be cleaner than the current strategy?