Files
CV_Site_Nuxt/OKF_Nuxt/open-questions.md
T
Noel Sabia 9b0f89ef38
PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / ESLint (pull_request) Successful in 36s
PR Check / Typecheck (pull_request) Successful in 44s
PR Check / Secret scan (gitleaks) (pull_request) Successful in 6s
PR Check / Dependency audit (pull_request) Successful in 9s
PR Check / Dockerfile lint (droast) (pull_request) Successful in 5s
PR Check / AI code review (opencode) (pull_request) Successful in 5m12s
fix(ci): switch review model to deepseek-v4.1-flash, pause snyk via workflow_dispatch
2026-10-20 20:36:54 +02:00

3.5 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.
decision
open
draft
by at
opencode-go/glm-5.3-flash 2026-10-18T12:41:52Z
Question Needed by Default if nobody decides
Shape of the production image - decided: runnable Node server, see production image done —
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 decided: 11.26.0, same as dev (production image) done
How the gateway serves the site now that the production image is an SSR Node server (proxy to the server, instead of embedding static files) updating the sibling OKF_CV_Website decision static-nuxt-in-gateway Proxy to the server.
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) - decided (2026-10-20): review model is opencode-go/deepseek-v4.1-flash#max; the pro endpoint failed two consecutive review runs with Upstream request failed: Endpoint is unavailable (~10 min apart), so the recorded default was applied done —
Removing the two reviewed audit ignores when node-forge or braces ship patched releases next dependency update round Watch for new releases.

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_modules directory 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.