PR Check / Dockerfile lint (droast) (pull_request) Skipped
PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / ESLint (pull_request) Successful in 36s
PR Check / Typecheck (pull_request) Successful in 38s
PR Check / Secret scan (gitleaks) (pull_request) Successful in 5s
PR Check / Dependency audit (pull_request) Successful in 9s
PR Check / AI code review (opencode) (pull_request) Failing after 13s
Four new decision documents covering the pipeline work: layering, AI review setup (provider prefix, v2 CLI, env-only auth, verdict gate), release engineering (release-please manifest mode), and the Snyk pause with the token scope policy. Index grouped, log extended, open questions updated.
3.0 KiB
3.0 KiB
type, title, description, tags, status, generated
| type | title | description | tags | status | generated | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Open Questions | Open questions | Decisions still to make for the Nuxt site, with what needs each answer. |
|
draft |
|
| Question | Needed by | Default if nobody decides |
|---|---|---|
Shape of the production image: a runnable Node server, or static .output/public/ files for the gateway to embed |
the next Dockerfile step | None. The empty Dockerfile stays empty — and until it holds real instructions, the droast job will fail on it. |
How the compose service mounts the source: the whole repository plus a volume for node_modules, or only the directories that get edited |
finishing Local_Development/docker-compose.yml |
None. The compose file is not yet valid. |
| Which pnpm version the production image pins | writing the production image | The same as dev, 11.26.0. |
Whether these decisions stay in this bundle or fold into the sibling OKF_CV_Website bundle, which already describes the frontend at design level |
after the production image exists | None. |
| When and how often Snyk runs once re-enabled: weekly schedule, ready-for-review gate, or per-push | re-enabling the snyk job | Stay disabled. |
| Whether the AI review job should gate merges (required status check on the verdict) or stay advisory | branch protection setup | Advisory. The review comment is information; blocking merges on an AI verdict is a policy choice, not a technical one. |
| How the opencode CLI version in CI gets upgraded: manually bump the pinned 2.0.32, or automate when a new major appears | first review failure after an opencode release | Manual bump. Pinning exists so upgrades are decisions. |
Whether the Go plan's per-model usage windows ($3 per 5 hours for DeepSeek V4 Pro) survive real review frequency, or the review model must move to deepseek-v4.1-flash ($80 window) |
first quota-limited review | Switch to flash. |
The mount trade-off, in detail
Measured on the whole-repository mount:
- An anonymous volume is created once. After a dependency change the stale contents persist unless the volume is renewed, and the renewal command has not been tested.
- Docker creates an empty, root-owned
node_modulesdirectory in the repository on the first run, unless that directory already exists.
The alternative — mounting only the directories that get edited — removes the
volume, the renewal step and the root-owned directory entirely, and keeps .nuxt
inside the container rather than in the working tree. It costs one compose line
per top-level directory, so a new directory silently fails to appear in the
container until the compose file is updated.
Related
The Nuxt frontend is described at design level in OKF_CV_Website, in
architecture/frontend.md and decisions/static-nuxt-in-gateway.md. Those
documents state that the site is generated to static files and embedded in the
gateway image, which is an input to the production-image question above.