test-server.mjs spawns 'docker compose --profile test up postgres-test'
but compose validates env interpolation across ALL services before
filtering by profile. The unused pgadmin service's PGADMIN_PASSWORD:?
check fires and aborts the call. Set a dummy value in the job env.
Node's ESM bare-specifier resolver walks up from the script's
directory and ignores NODE_PATH (that's CJS-only). Create
scripts/node_modules with symlinks to @prisma, @node-rs, and
.prisma from packages/db/node_modules so setup-admin.mjs's imports
resolve on the first step up.
E2E: rename service hosts postgres/redis to e2epg/e2eredis — the
gitea_gitea network has multiple containers answering to 'postgres'
(Gitea core + concurrent job services), causing split-brain where
prisma db push and db:seed connected to different databases and
audit_logs ended up missing.
docker-compose.ci.yml: stop attaching postgres/redis to gitea_gitea
for the docker-deploy-test job — only the app needs cross-network
reachability; the compose services talk to each other on the
internal default network.
Docker Deploy: setup-admin.mjs imports @prisma/client and
@node-rs/argon2 which only live in packages/db/node_modules. Node
resolves bare specifiers from the script's directory (/app/scripts),
not cwd, so pnpm --filter wrappers did not help. Set NODE_PATH to
packages/db/node_modules as a fallback resolution root.
- e2e: install psql; dump 'getent hosts postgres' (suspect two hosts
answer to 'postgres' on gitea_gitea) and the table list after push.
Fail loudly when audit_logs is missing so we see the true state at
push time instead of later at seed time.
- docker-deploy: setup-admin.mjs imports @prisma/client via bare
specifier, which only resolves inside packages/db in pnpm workspaces.
Run the script through `pnpm --filter @capakraken/db exec` so Node
walks the right node_modules.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- docker-compose.ci.yml: attach app/postgres/redis to the external
gitea_gitea network so the act_runner job container (which lives on
gitea_gitea) can reach the compose services by name. Otherwise
'localhost:3100' from the job container resolves to the job container
itself, not the compose-network app — all health checks and smoke
tests were hitting nothing.
- ci.yml: switch health/smoke URLs from localhost to http://app:3100
and expose PLAYWRIGHT_BASE_URL so the smoke config can override.
- ci.yml: run E2E playwright directly via pnpm --filter, bypassing
turbo which strict-filters PLAYWRIGHT_DATABASE_URL and friends.
- playwright.ci.config.ts: honour PLAYWRIGHT_BASE_URL env override.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- e2e: switch schema reset + sanity check from psql (not installed in
act_runner's catthehacker/ubuntu image) to `prisma db execute --stdin`
which is already a dev dep.
- docker-deploy: after `db push` the schema matches schema.prisma but
_prisma_migrations is empty, so the follow-up `migrate deploy` fails
with P3005. Baseline each migration directory as applied via
`prisma migrate resolve --applied` before deploy; the migrations
themselves are idempotent supplements, so marking-as-applied is safe.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- e2e: prisma db push --force-reset claimed success but audit_logs
ended up missing. Switch to explicit DROP SCHEMA public CASCADE via
psql, then push, then sanity-check with to_regclass before seeding.
- docker-deploy: add docker compose down -v before starting, so the
postgres volume is empty each run. A failed migration entry in
_prisma_migrations from a previous run was blocking migrate deploy
with P3009.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- e2e: use prisma db push --force-reset so the job starts from a
guaranteed clean schema (previous runs hit missing audit_logs
even though push reported in-sync; suspected stale service volume).
- docker-deploy: run prisma db push before db:migrate:deploy in
app-dev-start.sh. The migrations/*.sql files are idempotent
supplements (IF NOT EXISTS guards) that assume base tables already
exist; a fresh container has no tables, so the first incremental
migration's FK on "users" fails. db push creates the baseline,
migrate deploy then layers on the incremental additions.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
After the db-target guard unblocked db:push, the Playwright webServer
bootstrap in apps/web/e2e/test-server.mjs now fails with
"PLAYWRIGHT_DATABASE_URL or DATABASE_URL_TEST must be configured for
E2E runs." Set it to the same capakraken_test DSN already used for
DATABASE_URL.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
E2E was failing at `pnpm db:push` because scripts/prisma-with-env.mjs
refuses to run when DATABASE_URL's database name doesn't match the
expected target ("capakraken"). CI uses capakraken_test. Set
CAPAKRAKEN_EXPECTED_DB_NAME=capakraken_test on the e2e job.
Fresh-Linux Docker Deploy was failing because docker-compose.yml's dev
bind mount `.:/app` doesn't work under docker-outside-of-docker on the
Gitea act_runner — the host daemon can't see the job container's
/workspace/... path, so the mount masks the image's baked-in files and
the CMD fails with `cannot open ./tooling/docker/app-dev-start.sh`.
Added docker-compose.ci.yml that resets `app.volumes` and layered it
onto every `docker compose` invocation in the deploy job.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
upload-artifact@v4 and download-artifact@v4 are not supported on
Gitea Actions (GHES), so coverage + Playwright report uploads fail
the whole job even when every test passes. Mark those three upload
steps as continue-on-error so test success is not gated on artifact
persistence — the artifacts are still useful locally via act / the
job logs, just not retained server-side.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Unit Tests fix: when REDIS_URL is set but Redis briefly drops, the rate
limiter switches to a degraded in-memory backend with max/10 limits and
accumulates state across test files, breaking ~120 api router tests with
"Rate limit exceeded". Setting RATE_LIMIT_BACKEND=memory pins the limiter
to the full-capacity memory backend for unit tests (which don't need
distributed counters anyway).
Build fix: next build collects page data for /api/auth routes, which
validates AUTH_SECRET at boot. CI_AUTH_SECRET comes from a Gitea secret
that isn't configured, so it was empty and builds aborted. Use a
placeholder string ≥32 chars inline — the real secret is only required
in deploy workflows, not here.
On the self-hosted QNAP runner, restoring the pnpm store from actions/cache
produces ~260 "Cannot change mode to rwxr-xr-x: Bad address" tar errors,
leaving the store partially extracted. pnpm install still reports success but
produces broken symlinks (e.g. @vitest/coverage-v8 missing at runtime), which
crashes the engine test suite with ERR_LOAD_URL.
QNAP runner disk persists across runs anyway; the cache layer only adds risk.
CI unit-test runs vitest run --coverage in each workspace package, but only
apps/web declared the coverage-v8 dep. In pnpm workspaces deps aren't
hoisted across packages, so engine/staffing/api/application/shared need it
directly.
The build job also needs REDIS_URL because collecting page data for
/api/perf imports a module that throws if REDIS_URL is missing under
NODE_ENV=production. A placeholder value satisfies the check (no actual
Redis connection is made at build time).
act_runner sometimes checks out moving tag @v4 without the built dist/
output, breaking all jobs with MODULE_NOT_FOUND on setup/index.js.
Pinning to a tagged release avoids the incomplete checkout.
- Remove host port mappings from postgres/redis services in ci.yml;
QNAP runner already occupies 5432. Use service DNS names
(postgres/redis) instead of localhost for DB/Redis URLs.
- Track packages/api/src/lib/read-only-prisma.ts which was imported
by assistant-tools.ts but never committed, breaking check:imports.
Collapses ci.yml, release-image.yml, and deploy-test.yml from three
parallel push-triggered workflows into one orchestrated pipeline:
- release-image.yml: converted to reusable workflow (workflow_call +
workflow_dispatch). No longer triggers on push directly.
- deploy-test.yml: deleted, content inlined into ci.yml as the
docker-deploy-test job with needs: [build].
- ci.yml: adds docker-deploy-test job and release-images job. The
release-images job calls release-image.yml via uses: and is gated
to push events on main, so PRs do not publish images.
- check-architecture-guardrails.mjs: updated to enforce the new
reusable-workflow shape (workflow_call trigger, ci.yml chains
release-image.yml, main-push gating).
One run per commit, clear Success/Failure status, no wasted image
builds when CI fails.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Adds paths-ignore filters so changes under docs/, .gitea/, *.md, and
LICENSE don't trigger the full CI matrix, image builds, or test-deploy
on Gitea Actions. Saves ~30+ minutes per docs commit.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add pnpm audit --audit-level=high to CI guardrails job so vulnerable
packages are caught before merge, not just in nightly scans
- Add CODEOWNERS for review routing on infra, schema, and auth changes
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Move CI_AUTH_SECRET from plaintext to ${{ secrets.CI_AUTH_SECRET }}
- Wrap password reset (update + session kill + token mark) in $transaction
to prevent stale sessions on partial failure (CWE-613)
- Rate limiter Redis fallback now uses stricter degraded limits
(maxRequests/10) and logs at error level instead of warn
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Install husky v9 + lint-staged: pre-commit runs eslint --fix and prettier on staged files
- Tighten ESLint base config: no-console→error, ban-ts-comment (ts-ignore banned, ts-expect-error with description allowed), reportUnusedDisableDirectives→error
- Migrate web app from deprecated `next lint` to `eslint src/` with flat config and react-hooks plugin
- Convert all 5 @ts-ignore to @ts-expect-error with descriptions, remove stale disable comments
- Add NEXT_PUBLIC_SENTRY_DSN to docker-compose.prod.yml and .env.example
- Add coverage artifact upload step to CI test job
- Pre-existing violations (102 warnings) downgraded to warn in web config for Phase 2 cleanup
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Allocation bars that have active optimistic overrides (post-drag,
awaiting server confirmation) now pulse subtly via animate-pulse.
The pending set is derived from the existing optimisticAllocations
map keys, requiring no additional state.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Hartmut