Files
CV_Site_Nuxt/OKF_Nuxt/index.md
T
Noel Sabia f32ad07648
PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / ESLint (pull_request) Canceled after 28s
PR Check / Typecheck (pull_request) Canceled after 0s
PR Check / Secret scan (gitleaks) (pull_request) Canceled after 0s
PR Check / Dependency audit (pull_request) Canceled after 0s
PR Check / Dockerfile lint (droast) (pull_request) Canceled after 0s
PR Check / AI code review (opencode) (pull_request) Canceled after 0s
fix: unblock the release PR - real production image, reviewed audit ignores
The release PR (chore: release main) failed two checks, both verified
locally before pushing:

- droast: the empty production Dockerfile failed DF071 (no
  instructions). The new Dockerfile is a runnable Node server (SSR):
  multi-stage, manifests-first layers, digest-pinned node:26-slim (same
  digest as the dev container), non-root uid 1000, node-fetch
  HEALTHCHECK. Measured: docker build succeeds in-image, container
  serves HTTP 200 and reports healthy; droast reports 0 errors.
- audit: two high advisories with NO patched release anywhere
  (node-forge <=1.4.0 and braces <=3.0.3 are the newest npm versions;
  both build-time-only paths under nitropack). Recorded as
  auditConfig.ignoreGhsas in pnpm-workspace.yaml with the reason and
  removal condition - the audit output still names what it skipped.
  pnpm 11 ignores the pnpm field in package.json (caught locally via
  the WARN before pushing); settings live in pnpm-workspace.yaml.

OKF_Nuxt: recorded the production-image and audit-policy decisions,
updated log, indexes and open questions.
2026-10-18 21:14:12 +02:00

2.8 KiB

okf_version
okf_version
0.2

Start here

This bundle explains the Nuxt repository: how it is developed, checked, released, and what was learned getting there. It is the "why" behind the config files — the configs say what, these documents say why.

Decisions

CI/CD and releases (2026-10-18)

  • PR pipeline layering - Three layers: pre-commit for cheap deterministic checks, Gitea Actions for thorough ones, AI review for judgment.
  • AI review setup - Plan model, env-only auth against prompt injection, read-only agent, verdict line as the posting gate.
  • Vulnerability audit policy - Blocking audit; reviewed ignore-list for unfixable advisories in pnpm-workspace.yaml.
  • Release engineering - release-please in manifest mode; conventional commits enforced at commit time.
  • Snyk paused and secrets policy - Quota-paused job kept in place; write:issue scope required on every workflow token.

Docker and development environment

  • Dev container shape - The source is bind-mounted into a container that already holds the dependencies, and the dev server runs as the image's node user.
  • Build layer order - Why the manifests are copied before the source, and what invalidates what.
  • Build context filter - What .dockerignore may exclude, and the one thing it must never exclude.
  • Production image shape - Multi-stage, digest-pinned, non-root runnable Node server - measured build and serve.
  • Repository and compose layout - The Dockerfiles live with the app; the stack is assembled in Local_Development.
  • Mockup layout - One DESIGN.md per screen, with the screenshot and the source embedded.

The one-paragraph history

The repository started as the Nuxt app shell. Docker development (dev container, layer order, context filter) came first, then a single day of CI/CD work built the PR pipeline layer by layer — lint, typecheck, secret scan, dependency audit, Dockerfile lint, AI review — fixing one real failure per layer as it appeared (wrong provider account, wrong CLI major version, arm64-hostile vendor images, a silently-skipping hashFiles, a prompt-injectable credential file), then wired releases via release-please and locked the message format with pre-commit hooks. The pipeline now fails loudly, posts only real reviews, and needs no human faith to operate.