Files
CV_Site_Nuxt/OKF_Nuxt/index.md
T
Noel Sabia 15cf091ddf
PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / ESLint (pull_request) Successful in 38s
PR Check / Typecheck (pull_request) Successful in 44s
PR Check / Secret scan (gitleaks) (pull_request) Successful in 5s
PR Check / Dependency audit (pull_request) Failing after 9s
PR Check / Dockerfile lint (droast) (pull_request) Successful in 5s
PR Check / AI code review (opencode) (pull_request) Failing after 1m36s
docs(okf): add frontend API contract for the gateway
2026-10-20 20:20:32 +02:00

3.0 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.

  • Open questions - What is still undecided for the Nuxt site.
  • Backend endpoints - The smallest API the frontend needs from the Go gateway: health, chapters, knockdown, events.
  • Future updates - Pipeline improvement backlog with effort estimates, not yet decided.
  • Update log - History of changes to this bundle.

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.