The registry endpoint is the Gitea hostname itself, not a separate
registry.noelsabia.dev host. Point IMAGE, docker login and the v2
manifests check at git.noelsabia.dev and record the correction.
Move the service and its env file into the Gitea stack, remove the separate deploy directory and the unused /opt operator-access scripts, and keep the operational guide in OKF_Nuxt/pr-agent.md.
Run PR-Agent as a pinned webhook server on the Gitea Docker network and review on PR open plus slash commands. The per-PR opencode installer and verdict-posting step are removed.
The server-side .env stays outside the repository; deploy/pr-agent/ holds the compose definition and operator notes.
Applied the findings that held up against the code:
- strict vMAJOR.MINOR.PATCH guard; v[0-9]* accepted v1, v1-foo and
prereleases, all valid registry tags
- latest now follows the newest release, so replaying an older tag cannot
drag it backwards; skipped with a warning if the tag list is unavailable
- smoke test starts the built image and requires 2xx on / before pushing
- timeout-minutes: 20 on the job, so a hung build cannot hold the
capacity-1 runner indefinitely
- the decision doc records the socket's blast radius: root-equivalent,
runner-wide, only on a label PR jobs cannot use
Rejected with evidence: the .dockerignore leak (.env*, *.pem, .git are
excluded) and the Docker client/daemon API mismatch (20.10.24 client
against a 29.9.2 daemon builds over the socket).
Build Dockerfile on every v* tag push (created by release-please when the
release PR merges) and push registry.noelsabia.dev/cv_website/nuxt as the
version, sha-<12> and latest. Main pushes do not build: the registry holds
releases, not commits.
The job runs in node:22-bookworm and needs only the Docker client, so the
act_runner must expose its host socket (container.docker_host: automount);
a preflight step fails with that cause when it does not.
Conflicts:
- app/pages/index.vue: kept main's SEO setup (SITE, useSeoMeta,
titleTemplate) alongside the branch's chapters import.
- OKF_Nuxt/log.md: both sides prepended entries; kept the profile and
metrics entries above main's PR #16, SEO, favicon and icon entries.
Also takes main's @nuxtjs/seo and @nuxt/icon setup, favicon/OG assets,
site.config.mjs and the CI review changes. lint, typecheck and build pass
after a frozen-lockfile install.
Contact bar: Gmail, Heilbronn and a LinkedIn link; the phone chip is
removed. Hero: System Architect / Programmer, new pill and quote.
Feature cards: humility, learning and helpfulness instead of the
infrastructure copy.
Terminal: six chapters from the LinkedIn export (PreZero active;
Defifort, Alignerr, Outlier, freelance and 42 finished), each with a
context label. Rows use a fixed grid so names, context badges, status,
uptime and outcome line up vertically; the title bar has red/yellow/green
traffic lights and the footer pluralises its counters (1/5/14).
OKF: new profile data document for the export and chapter mapping;
backend endpoint examples and totals match the real rows.
- generate favicon.ico and favicon.svg from the header avatar; the sprite
moves to app/utils/avatar.js so component and generators share one source
- register @nuxtjs/seo with site and Person schema.org data from
site.config.mjs; canonical, robots, sitemap and llms.txt follow the routes
- title "Noel Sabia — <role>", summary_large_image, and no duplicate
"| Noel Sabia" suffix from SEO Utils
- add a committed 1200x630 OG card generated by pnpm og-image; the dynamic
OG renderer and skew protection stay off for the static deployment
- pin the Node version @nuxtjs/seo 6 requires and document the setup in the
OKF bundle
- decisions/icons-via-nuxt-icon.md: local collection, mode svg,
serverBundle collections empty, scanned client bundle; 3 icons, 1.23 kB
- linked from the bundle index and the decisions index, logged
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.
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.
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.