wtclaude 40ab1ce8d2 fix(modules): bump the CLIENT half of MODULE_API_VERSION to 1.9.0 ...

The two halves version ONE contract and a test asserts they agree
(client/test/moduleRegistry.test.js). I bumped server/src/modules/version.js and
not client/src/modules/version.js, so client-build went red — the job runs the
client suite before it builds.

Nothing on the client half changed: a seed is server-side data and core's seeders
write it on the boot path. It bumps for the reason its own header gives — a
module declares one `coreApi` range against both halves, and a client claiming
1.8.0 while the server answers 1.9.0 is two answers to one question.

327 client tests green; client build clean.

Co-Authored-By: Claude <noreply@anthropic.com>

2026-09-01 01:22:00 -05:00

..

public

feat(brand): emblem behind hero text + Powered By footer with logo

2026-07-18 16:56:22 -05:00

src

fix(modules): bump the CLIENT half of MODULE_API_VERSION to 1.9.0

2026-09-01 01:22:00 -05:00

test

feat(engagement): the in-app channel, core and web (engagement Phase 7)

2026-08-31 02:07:10 -05:00

index.html

feat(theming): server-resolved theme engine and admin appearance UI

2026-08-07 19:16:23 -05:00

package-lock.json

feat(theming): wire the three navs and add the admin nav builder

2026-08-08 00:02:33 -05:00

package.json

feat(theming): wire the three navs and add the admin nav builder

2026-08-08 00:02:33 -05:00

vite.config.js

fix(security): add SPA CSP, drop x-powered-by, strengthen dedupe hash

2026-07-20 23:02:11 -05:00