The classic installer (opencode.ai/install) ships only OpenCode 1.x
- v1.19.3 on arm64 - which cannot resolve model variants and failed
with ProviderModelNotFoundError for deepseek-v4-pro#max. Use the v2
installer (currently v2.0.32, same version as local dev); verified
working in a fresh arm64 container with key-only auth.
The dockerfile-lint job skipped on every PR despite Dockerfiles
existing: the act runner's hashFiles() evaluation returned empty.
Replace it with an explicit file-discovery step. Also run the droast
binary in node:22-bookworm (arch-aware install) instead of the
vendor image, which ships no node and would fail actions/checkout
with exit 127 - same failure mode as the gitleaks image.
The headless CI container has no stored credentials, so auth depends
entirely on the injected key. Generate an opencode.json at runtime
that binds OPENCODE_API_KEY to the opencode-go provider explicitly,
removing any dependence on env-var-to-provider mapping behavior.
- audit no longer runs with continue-on-error: a failed audit must
turn the pipeline red, not pass silently
- opencode review runs with --print-logs so auth and provider errors
(e.g. invalid API key vs missing Go subscription) appear in the job
log instead of an opaque exit 1
main changed the review model to the default thinking budget; keep
opencode-go/deepseek-v4-pro#max (plan-included, max effort) which
supersedes both earlier variants.
The 'opencode' provider prefix points at OpenCode Zen (pay-per-call,
no funds), which failed every review run with 'Insufficient account
funds'. The opencode-go $10 plan covers deepseek-v4-pro with high
and max variants - use opencode-go/deepseek-v4-pro#max.
The 'opencode' provider prefix points at OpenCode Zen (pay-per-call,
no funds). The opencode-go $10 plan covers deepseek-v4-pro with high
and max variants - use opencode-go/deepseek-v4-pro#max.
Replace the inline 'release-type: simple' with references to
release-please-config.json and .release-please-manifest.json so the
manifest-driven release strategy is used.
- release-please-config.json: node release type, root package,
plain v-tags, default versioning (fix->patch, feat->minor,
BREAKING CHANGE->major)
- .release-please-manifest.json: track current version (1.0.0)
- package.json: add version field required by the node release type
#max exceeded the available opencode account funds; the default
thinking budget keeps the flagship model at lower cost. #max remains
available by re-adding the variant.
Passing the PR diff as a command-line argument exceeded
MAX_ARG_STRLEN (128KiB per single argument; the diff was 190KB,
mostly pnpm-lock.yaml). The shell failed with E2BIG ('Argument list
too long') and the tee pipeline masked the failure, so the raw error
log got posted as a 'review' comment.
- exclude pnpm-lock.yaml from the review diff (pnpm audit covers deps)
- write the diff to .pr-review-diff.patch in the workspace; the agent
reads it with file tools
- redirect output instead of piping through tee and fail the job when
opencode fails, so errors are never posted as review comments
- model: opencode/deepseek-v4-pro#max (requires funds on the opencode
account; flash fallback documented in a comment)
- review prompt rewritten: SSR/hydration/reactivity pitfalls, Nuxt
server-route security, runtime config leaks, Go error handling,
concurrency and resource hygiene, frontend/backend contract checks
- strict output format with [BLOCKER]/[WARN]/[NIT] severities mapped
to the approve/request-changes verdict
- Snyk job disabled via 'if: false': free plan only has ~100 test
credits/month and the job runs 2 tests per PR push
- PR comment step no longer fails silently: curl prints the HTTP
status and response body, making token/URL errors visible
Dockerfile linting is already covered by the droast job; the second
Snyk step now scans our own source for code vulnerabilities (XSS,
injection, unsafe patterns) instead of the base image.
The pnpm-workspace.yaml makes Snyk treat the project as a package
workspace; without --all-projects it aborts with SNYK-CLI-0000
(422 Unprocessable Entity).
The snyk/snyk:node image is amd64-only and cannot start on an arm64
runner. Install the Snyk CLI through npm (supports linux/arm64) in
the multi-arch node:22-bookworm image instead.
Replace anthropic/claude-sonnet-4-5 with opencode/deepseek-v4-pro for
a large cost reduction while keeping thorough, high-effort reviews.
Documented cheaper fallback: deepseek-v4.1-flash(-free).
The gitleaks container image ships no node binary, so node-based
actions like actions/checkout fail with exit code 127. Install the
gitleaks v8.28.0 binary in the standard node:22-bookworm image
instead.
gitleaks is not published on Docker Hub, so the container image pull
failed with 'pull access denied'. Use ghcr.io/gitleaks/gitleaks and
pin v8.28.0 for reproducible scans.
pnpm 9 treats the config-only pnpm-workspace.yaml (allowBuilds, no
packages field) as a workspace definition and fails with 'packages
field missing or empty'. Pin the same major version as local dev.
The Gitea repo CV_Website/CV_Site_Nuxt checks out to a workspace that
already is the app root, so working-directory CV_Site_Nuxt resolved to
a doubled, non-existent path.
Runs on every pull request:
- ESLint and vue-tsc typecheck
- gitleaks secret scan over full history
- pnpm dependency audit (advisory)
- droast Dockerfile lint (skips until a Dockerfile exists)
- Snyk dependency and base image scan
- opencode AI code review posted as PR comment
Record the design decisions behind the Nuxt site as an OKF v0.2 bundle: dev
container shape, build layer order, build context filter, repository and
compose layout, and the mockup layout, plus the open questions.
Conformant per the spec: every concept carries a non-empty type, the reserved
index and log files follow their structures, and every internal link resolves.