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.
Below lg the chapter rows show only the context badge and the status, so
the terminal no longer needs 760px on a phone; the desktop grid is
unchanged. The contact bar stacks the email full width and puts LinkedIn
and the location side by side.
Contact values truncate instead of forcing the bar wider. Also fixes the
"someone we pull" typo in the third feature card and lets the hero quote
use the wider column.
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.
The diff filter drops pnpm-lock.yaml to keep the patch small; the model read
that as an uncommitted lockfile and raised a BLOCKER on PR #16. Say so in the
prompt instead of widening the diff.
Compose pages/index.vue from the desktop homepage mockup: decorative
backdrop scoped to the hero but not clipped at its bottom edge, hero with
status pill, quote and contact chips with copy buttons, terminal panel fed
by a chapter array with derived counters, and the three feature cards.
Split into app/components/home/ (auto-imported with the Home* prefix) and
keep the chapter data in app/data/chapters.ts so GET /api/chapters can
replace the mockup values later.
- 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
- AppBottomNav: fixed bar below md with Overview, Life Map and Dev View
- default.vue mounts it and carries pb-16 md:pb-0 so the footer stays clear
- AppFooter is hidden below md, where the bar takes over
- icons come from @nuxt/icon (mode svg, scanned client bundle) with the
Material Symbols collection installed locally, replacing the webfont
- deletes the 3.9 MiB Material Symbols woff2 and its @font-face
- review model: opencode-go/claude-haiku-5-5#medium instead of
deepseek-v4.1-flash#max; flash has no medium variant
- merge lint and typecheck into one job with a single pnpm install
- cache the pnpm store and opencode binary via actions/cache@v4.1.0,
keyed on a sha256 of the lockfile (hashFiles is empty on this runner)
- update the decision records and log
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.
The 401 in run 89 was the final isomorphic-git push inside
code-suggester's createPullRequest, not an API call: tree, commit and
local ref update all ran through the token-authenticated octokit API,
then 'git push' used the git-username/git-password inputs - unset in
our workflow, so the push was anonymous. The remote branch
release-please--branches--main still sat at an old commit, proving the
push never landed. Pass the account name and the same token.
Validated from review comment 82 on this PR: the 'bash -c' wrapper
consumed the first staged filename as $0 and the command never
referenced $@, so eslint received zero file arguments and linted the
whole repo - --fix silently rewrote unstaged files and WIP lint errors
blocked unrelated commits. The entry now receives filenames directly
from pre-commit (empirically verified with an arg probe); documented
the re-stage loop for --fix and dropped the redundant 'types: [file]'
filter.
The dedicated RELEASE_PLEASE_TOKEN_CV_SITE_NUXT secret authenticated for
reads but threw when creating the release PR (exit 1, releases_created
false, no PR created): it lacks write:repository / write:issue. Use the
proven PR_GITEA_TOKEN instead, per the one-well-scoped-token policy in
OKF_Nuxt/decisions/snyk-paused-and-secrets-policy.md.
Findings validated from review comments 71 and 75:
- [BLOCKER] the no-verdict branch exited \${EXIT_CODE:-1} which is 0
when opencode succeeded without a verdict - job went green and the
post step published non-review output. The else branch now exits 1
unconditionally, the verdict is anchored to the last five lines (the
prompt itself contains VERDICT lines), and the post step re-verifies
the contract before posting.
- [BLOCKER] the v1 'permission' object is ignored by the opencode v2
CLI - shell commands executed in both review runs despite deny. The
config now uses the v2 'permissions' array with 'shell' as the
action name, denying edit/shell/webfetch/websearch/external_directory.
- hygiene: droast linting prunes node_modules, audit comment names the
exact key to re-add, shell blocks verified with sh -n.
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.