From c626cc9c1dc7db94e645d33eab3c7c7b9a860438 Mon Sep 17 00:00:00 2001 From: Noel Sabia Date: Fri, 30 Oct 2026 21:00:53 +0100 Subject: [PATCH 1/9] feat(ci): replace opencode review with PR-Agent 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. --- .gitea/workflows/pr-checker.yml | 226 --------------------- OKF_Nuxt/decisions/ai-review-setup.md | 6 +- OKF_Nuxt/decisions/index.md | 3 +- OKF_Nuxt/decisions/pr-agent.md | 106 ++++++++++ OKF_Nuxt/decisions/pr-pipeline-layering.md | 17 +- OKF_Nuxt/index.md | 3 +- OKF_Nuxt/log.md | 7 + OKF_Nuxt/open-questions.md | 3 +- deploy/pr-agent/.env.example | 25 +++ deploy/pr-agent/README.md | 53 +++++ deploy/pr-agent/docker-compose.yml | 38 ++++ 11 files changed, 251 insertions(+), 236 deletions(-) create mode 100644 OKF_Nuxt/decisions/pr-agent.md create mode 100644 deploy/pr-agent/.env.example create mode 100644 deploy/pr-agent/README.md create mode 100644 deploy/pr-agent/docker-compose.yml diff --git a/.gitea/workflows/pr-checker.yml b/.gitea/workflows/pr-checker.yml index a45ac14..97a3dd8 100644 --- a/.gitea/workflows/pr-checker.yml +++ b/.gitea/workflows/pr-checker.yml @@ -229,229 +229,3 @@ jobs: # Dockerfile/base image checks are covered by the droast job snyk code test \ --severity-threshold=high - - # -------------------------------------------------------- ai code review -- - review: - name: AI code review (opencode) - runs-on: ubuntu-latest - container: node:22-bookworm - # Draft PRs don't get a (paid) review yet. The event_name check is - # load-bearing: manual (workflow_dispatch) triggers - which exist to - # run the paused snyk job - must NOT launch a paid review, which on - # a dispatch event has no PR to post to. - if: ${{ github.event_name == 'pull_request' && !github.event.pull_request.draft }} - steps: - - uses: actions/checkout@v4 - with: - fetch-depth: 0 - - - name: Restore opencode binary - id: opencode-cache - # The installer writes to $HOME/.opencode/bin. Caching it saves the - # ~4s download+extract per run - small next to the model call, but - # free to keep. Key includes the pinned version, so bumping the - # version below invalidates the cached binary automatically. - # As above, a cache outage falls back to the installer. - continue-on-error: true - uses: actions/cache@v4.1.0 - with: - path: ~/.opencode/bin - key: opencode-v2.0.32-${{ runner.os }} - - - name: Install opencode CLI - if: steps.opencode-cache.outputs.cache-hit != 'true' - run: curl -fsSL https://opencode.ai/v2/install | bash -s -- -v 2.0.32 - # v2 installer is required: the classic /install URL ships only - # OpenCode 1.x (resolved to v1.19.3 on arm64), which cannot resolve - # model variants like "#medium" and failed with ProviderModelNotFoundError. - # Version pinned (-v 2.0.32) so a breaking v2 release cannot fail - # the job mid-PR; bump deliberately, not automatically. - - - name: Add opencode to PATH - # The installer appends the directory to $GITHUB_PATH itself, but that - # step is skipped on a cache hit. Add it unconditionally. - run: echo "$HOME/.opencode/bin" >> "$GITHUB_PATH" - - - name: Get PR diff - run: | - # lockfile changes bloat the diff (175KB here) and are pointless to - # review - pnpm audit already covers dependencies. Excluding the - # lockfile also keeps the diff small enough to hand to the model. - # The diff goes to a file IN the workspace so the agent can read it - # with its file tools (passing 190KB as a CLI argument fails with - # "Argument list too long", MAX_ARG_STRLEN is 128KiB). - git diff --merge-base "origin/${{ github.base_ref }}" \ - -- . ':(exclude)pnpm-lock.yaml' > .pr-review-diff.patch - wc -c .pr-review-diff.patch - - - name: Run opencode review - env: - OPENCODE_API_KEY: ${{ secrets.OPENCODE_API_KEY }} - run: | - # opencode-go/claude-haiku-5-5#medium: cheap ($0.10/$0.50 per M - # tokens) and, unlike deepseek-v4.1-flash, it has a #medium - # reasoning variant - flash only exposes low/high/max, so every - # review there ran at maximum effort. #medium keeps the review - # competent without paying for max reasoning on each push. - # History: deepseek-v4-pro#max -> deepseek-v4.1-flash#max -> - # haiku-5-5#medium (2026-10-20). The pro endpoint failed two - # consecutive runs with "Upstream request failed: Endpoint is - # unavailable" before the flash switch; that fallback is recorded - # in OKF_Nuxt/open-questions.md. NOTE the provider prefix must be - # "opencode-go", NOT "opencode" (Zen is a different, pay-per-call - # provider and fails with 'Insufficient account funds'). - # - # Auth is env-only: the CLI picks up OPENCODE_API_KEY from the - # environment (verified headless). Deliberately NO opencode.json: - # a config file in the checkout would hold the API key in - # plaintext, readable by the agent - a malicious PR diff could - # prompt-inject the agent into quoting the key in the review - # comment (publicly visible). Env vars are invisible to file reads. - # Permissions live in a global config OUTSIDE the checkout (no - # secrets in it, so nothing can leak). OpenCode v2 schema: the - # field is "permissions" (plural) - an ordered array of - # {action, resource, effect}; "bash" was renamed "shell" in v2. - # The singular v1 "permission" object is ignored by the v2 CLI - # (verified empirically: shell commands executed despite deny). - # Denying shell/edit/webfetch/websearch/external_directory means - # no headless permission prompts can hang or kill the run, and - # the reviewer physically cannot modify the repo or browse - # attacker-controlled URLs. - mkdir -p "$HOME/.config/opencode" - printf '{ - "$schema": "https://opencode.ai/config.json", - "permissions": [ - { "action": "edit", "resource": "*", "effect": "deny" }, - { "action": "shell", "resource": "*", "effect": "deny" }, - { "action": "webfetch", "resource": "*", "effect": "deny" }, - { "action": "websearch", "resource": "*", "effect": "deny" }, - { "action": "external_directory", "resource": "*", "effect": "deny" } - ] - }' > "$HOME/.config/opencode/opencode.json" - # --print-logs: surface auth/provider errors in the CI log instead - # of failing with an opaque exit code - EXIT_CODE=0 - opencode run \ - --print-logs \ - --model opencode-go/claude-haiku-5-5#medium \ - "You are a principal engineer performing a rigorous code review on a - pull request. You have tool access: read repo files for context when - the diff alone is ambiguous, but review ONLY code changed in this PR. - - The full PR diff is in the file .pr-review-diff.patch in the repo - root. Read it first with your file tools. - - pnpm-lock.yaml is deliberately excluded from that patch to keep it - small, not forgotten. It is committed in the PR, pnpm audit covers - the dependencies, and CI runs `pnpm install --frozen-lockfile`. - Do not report a missing lockfile or a frozen-install drift. - - ## Project context - - Stack: Nuxt 4 (Vue 3, TypeScript) SSR web app in the repo root. - Backend/API services are being added in Golang. - - Deployment target: a personal production CV website. - - Already covered by other CI jobs, do NOT repeat their findings: - ESLint (style), vue-tsc (types), gitleaks (secrets in git history), - pnpm audit (dependency CVEs), droast (Dockerfile lint). - - Your job is everything those tools CANNOT see: logic, security, - architecture, correctness. - - ## Nuxt / Vue / TypeScript focus - - SSR pitfalls: window/document/localStorage access without - or process.client guards; hydration mismatch risks - (Date.now(), Math.random(), locale formatting in render path). - - useAsyncData/useFetch: missing or colliding keys, duplicate - requests between server and client, wrong caching/refresh setup. - - Reactivity bugs: destructuring reactive objects losing reactivity, - missing await on async setup, watch on getters vs refs. - - Security: v-html with unsanitized data, user input flowing into - meta/URLs, open redirects, missing validation in /server/api and - Nitro route handlers, auth checks on both page and API level. - - Config hygiene: server-only runtime config (no NUXT_PUBLIC_ - prefix) leaking secrets into the client bundle. - - ## Golang focus (when Go code is in the diff) - - Errors: unchecked errors, errors discarded, wrapping with %w, - sentinel vs typed errors, panic in library code. - - Concurrency: goroutine leaks (missing context cancellation), - data races (shared state without mutex/channel), WaitGroup - misuse, defer in loops. - - Resources: unclosed response bodies/files/rows, missing - timeouts on http.Client, unbounded buffering. - - Correctness: slice aliasing surprises, copy vs reference - semantics, nil map writes, integer truncation. - - ## Cross-cutting - - API contract mismatches between Nuxt frontend and Go backends - (field names, nullability, status codes, date formats). - - Missing authorization checks on new endpoints or pages. - - Secrets/credentials ending up in logs or client-visible output. - - Performance on the critical render path (heavy components, - unoptimized images, blocking Nitro middleware). - - ## Output format (strict) - Review the diff in .pr-review-diff.patch. For every finding: - [BLOCKER] file:line - what and why + concrete fix suggestion - [WARN] file:line - what and why + concrete fix suggestion - [NIT] file:line - optional improvement - BLOCKER = must fix before merge (security, data loss, broken - behavior). WARN = should fix soon. NIT = optional. - If a finding cannot be localized to a file, prefix [BLOCKER-GENERAL]. - No compliments, no summaries of what the diff does, no style nits. - Keep it under 400 words unless there are more than 10 findings. - If the diff contains no reviewable code (docs/config only), say so - in one line. - - End your response with a final verdict line, exactly one of: - VERDICT: APPROVE (no BLOCKER findings) - VERDICT: REQUEST_CHANGES (at least one BLOCKER)" \ - > /tmp/review.md 2>&1 || EXIT_CODE=$? - # always show the output - never swallow the error text - cat /tmp/review.md - # The posting gate is the OUTPUT CONTRACT, not the exit code: - # a completed review always ends with a VERDICT line - error - # dumps never do. opencode can exit 1 on benign tool denials - # even after a full review, so a present verdict means post; - # anything else means the review did not complete. - # Anchored to the tail: the prompt itself contains VERDICT - # lines, so scanning the whole file could pass on echoed - # prompt text or injected quotes - only the last lines count. - if tail -n 5 /tmp/review.md | grep -qE '^VERDICT: (APPROVE|REQUEST_CHANGES)'; then - [ "$EXIT_CODE" -ne 0 ] && echo "::warning::opencode exited ${EXIT_CODE} but produced a valid verdict - posting review" - echo "Review completed with verdict." - else - # fail closed: no verdict = no review. exit 1 unconditionally - - # falling back to EXIT_CODE would exit 0 when opencode succeeded - # but produced no review, and the job would go green. - echo "::error::opencode produced no valid review (exit ${EXIT_CODE:-1}) - NOT posting this output as a review comment" - exit 1 - fi - - - name: Post review as PR comment - continue-on-error: true # token missing/expired must not fail the build - env: - GITEA_TOKEN: ${{ secrets.PR_GITEA_TOKEN }} - PR_NUMBER: ${{ github.event.pull_request.number }} - REPO: ${{ github.repository }} - # Gitea sets GITHUB_API_URL, e.g. https://gitea.example.com/api/v1 - run: | - # re-verify the output contract here: never post anything that is - # not a completed review, regardless of how the previous step ended - if ! tail -n 5 /tmp/review.md | grep -qE '^VERDICT: (APPROVE|REQUEST_CHANGES)'; then - echo "::error::no verdict in review output - nothing to post" - exit 1 - fi - # jq is not in the node image - use node for JSON encoding - BODY=$(node -e 'process.stdout.write(JSON.stringify(require("fs").readFileSync("/tmp/review.md","utf8")))') - HTTP_CODE=$(curl -s -o /tmp/comment-response.json -w "%{http_code}" \ - -X POST \ - -H "Authorization: token ${GITEA_TOKEN}" \ - -H "Content-Type: application/json" \ - -d "{\"body\": ${BODY}}" \ - "${GITHUB_API_URL}/repos/${REPO}/issues/${PR_NUMBER}/comments") - echo "POST status: ${HTTP_CODE}" - cat /tmp/comment-response.json - case "$HTTP_CODE" in - 200|201) echo "Review comment posted." ;; - *) echo "::error::Failed to post review comment (HTTP ${HTTP_CODE}) - check PR_GITEA_TOKEN scope and expiry" ;; - esac diff --git a/OKF_Nuxt/decisions/ai-review-setup.md b/OKF_Nuxt/decisions/ai-review-setup.md index 2750dc9..3ad45fe 100644 --- a/OKF_Nuxt/decisions/ai-review-setup.md +++ b/OKF_Nuxt/decisions/ai-review-setup.md @@ -3,7 +3,7 @@ type: Decision title: AI code review setup description: The review job runs opencode with a cheap medium-effort opencode-go model, env-only auth, a read-only permission set, and posts only reviews that end with a verdict line. tags: [decision, ci, ai, opencode, security] -status: draft +status: deprecated generated: { by: opencode-go/glm-5.3-flash, at: 2026-10-18T16:05:00Z } verified: { by: human:noel, at: not yet } sources: @@ -15,6 +15,10 @@ sources: title: OpenCode Go plan documentation --- +> Superseded by [PR-Agent for Gitea reviews](pr-agent.md) on 2026-10-30. +> The opencode job was removed from `pr-checker.yml`; this document remains +> as the record of the earlier setup and the failures it fixed. + # Decision The review job installs opencode v2 from the dedicated v2 installer, diff --git a/OKF_Nuxt/decisions/index.md b/OKF_Nuxt/decisions/index.md index 283681c..0787e85 100644 --- a/OKF_Nuxt/decisions/index.md +++ b/OKF_Nuxt/decisions/index.md @@ -1,7 +1,8 @@ # Decisions * [PR pipeline layering](pr-pipeline-layering.md) - What runs pre-commit, what runs in Gitea Actions, what the AI review does, and the cost rule that decides. -* [AI review setup](ai-review-setup.md) - Plan model, env-only auth against prompt injection, read-only agent, and the verdict line as the posting gate. +* [PR-Agent for Gitea reviews](pr-agent.md) - A pinned webhook server replaces the per-PR opencode job; internal-only, scoped bot, OpenCode Go model. +* [AI review setup (opencode)](ai-review-setup.md) - Superseded 2026-10-30; kept for the env-only auth and verdict-gate reasoning. * [Vulnerability audit policy](vulnerability-audit-policy.md) - Blocking audit, reviewed ignore-list for unfixable advisories, and the pnpm-11 settings home. * [Release engineering](release-engineering.md) - release-please in manifest mode, conventional commits as input, message format enforced at commit time. * [Snyk paused and secrets policy](snyk-paused-and-secrets-policy.md) - Why the job is skipped rather than deleted, and the token scopes every workflow secret needs. diff --git a/OKF_Nuxt/decisions/pr-agent.md b/OKF_Nuxt/decisions/pr-agent.md new file mode 100644 index 0000000..3cb9232 --- /dev/null +++ b/OKF_Nuxt/decisions/pr-agent.md @@ -0,0 +1,106 @@ +--- +type: Decision +title: PR-Agent for Gitea reviews +description: A pinned PR-Agent webhook server on server0 reviews pull requests through a scoped Gitea bot user, replacing the per-PR opencode job. +tags: [decision, ci, ai, gitea, pr-agent, security] +status: draft +generated: { by: opencode-go/deepseek-v4.1-flash, at: 2026-10-30T20:00:00Z } +verified: { by: human:noel, at: not yet } +sources: + - id: compose + resource: deploy/pr-agent/docker-compose.yml + title: PR-Agent compose service + - id: env-example + resource: deploy/pr-agent/.env.example + title: Environment variables, without secrets + - id: pr-checker + resource: .gitea/workflows/pr-checker.yml + title: PR Check workflow, opencode job removed + - id: install + resource: https://docs.pr-agent.ai/installation/gitea/ + title: PR-Agent Gitea installation + - id: images + resource: https://hub.docker.com/r/pragent/pr-agent + title: Published gitea_app image tags + - id: gitea-egress + resource: https://docs.gitea.com/administration/config-cheat-sheet#webhook + title: Gitea webhook egress allowlist +--- + +# Decision + +PR-Agent runs as `pragent/pr-agent:0.49.0-gitea_app` in a long-lived +container on `server0`, attached to the existing `gitea_gitea` Docker +network. It publishes no ports. Gitea delivers pull-request and comment +events to `http://pr-agent:3000/api/v1/gitea_webhooks`; the bot user +`pr-agent` posts the result with a scoped personal access token. + +The opencode review job is removed from `pr-checker.yml`. PR-Agent runs +`/describe` and `/review` on pull request open/reopen and answers slash +commands in the conversation. Push-triggered re-review is disabled, so a +PR is reviewed once when it opens, not on every push. + +The model is OpenCode Go's OpenAI-compatible endpoint: + +```text +model openai/glm-5.3-flash +fallback openai/glm-5.3 +api base https://opencode.ai/inference/go/openai/v1 +``` + +`CONFIG__CUSTOM_MODEL_MAX_TOKENS=128000` supplies the context limit the +model table does not know; PR-Agent's default `config.max_model_tokens` +still caps the review budget at 32000. + +# Why + +* One container replaces a per-PR CLI install, binary cache and prompt + wrapper. The review path is then the same code for every PR. +* PR-Agent owns the Gitea webhook and comment plumbing, including the slash + commands (`/review`, `/improve`, `/ask`) the repository previously had no + way to trigger. +* The webhook endpoint stays on the Docker network. Nothing new is exposed + to the internet, and comment links still use the public Gitea URL. +* The image tag is pinned. A new PR-Agent release is a deliberate change, + not a rollout underneath the repository. + +# Gitea configuration + +* Bot user `pr-agent` is a collaborator with write permission on + `CV_Website/CV_Site_Nuxt`. The token scopes are `read:repository`, + `write:issue` and `read:user`. Gitea has no comment-only collaborator + role, so write is the narrowest role that can post comments and labels. +* `[webhook] ALLOWED_HOST_LIST = private:3000` is required: Gitea's default + lax egress policy allows public targets but refuses private ones, and the + webhook target is a Docker-network address. The API is reached at + `http://gitea:3000`; `GITEA__WEB_URL=https://git.noelsabia.dev` keeps + published links on the public host. +* The webhook sends `push`, `issues`, `pull_request` and `issue_comment` + events. Only the last two change behaviour today; `push` is kept because + PR-Agent may handle push commands in a later configuration. +* Secrets live only in `/home/noel/self-hosted/pr-agent/.env` (mode 600) on + `server0`. The repository contains the compose file and an example env + file, never the token or webhook secret. + +# Not verified + +* The OpenCode Go API key was not present when this was committed, so no + model call and no real review have run. The first PR after the key is set + is the verification. +* Whether `glm-5.3-flash` handles PR-Agent's structured review output well + enough. `glm-5.3` is configured as the fallback. +* Whether two gunicorn workers and the 1 GB memory limit hold under + concurrent reviews. The host has roughly 2.5 GB available with Gitea and + its runner idle. +* Whether the default review prompt is specific enough for this repository. + A `.pr_agent.toml` with project instructions is deliberately absent until + the first real review shows what it misses. + +# Revisit when + +* The first review fails, returns unstructured output, or misses the kind + of finding the opencode prompt used to catch. +* A newer `gitea_app` image tag is worth taking; bump the tag and run + `docker compose up -d`. +* Review volume makes the container's memory limit tight, or Gitea adds a + role that can comment without push access. diff --git a/OKF_Nuxt/decisions/pr-pipeline-layering.md b/OKF_Nuxt/decisions/pr-pipeline-layering.md index 8127661..31402c0 100644 --- a/OKF_Nuxt/decisions/pr-pipeline-layering.md +++ b/OKF_Nuxt/decisions/pr-pipeline-layering.md @@ -26,8 +26,8 @@ Every pull request is checked by three layers, ordered by cost: in one job (one install, cached pnpm store), gitleaks over full history, pnpm audit (blocking), droast Dockerfile lint, Snyk (currently disabled). -3. **AI code review** (per PR push): opencode with a plan-covered model, - verdict-based, posted as a PR comment. +3. **AI code review** (on PR open, or on a slash command): the PR-Agent + webhook server, posted as a PR comment. The split rule: anything that finishes in seconds and auto-fixes goes in pre-commit; anything slow, network-bound or quota-bound goes in CI; anything @@ -45,15 +45,16 @@ already passed the deterministic gates. # Caching -Two caches, both served by the runner's own cache server (no external -service, entries stay on the home server): +One cache, served by the runner's own cache server (no external service, +entries stay on the home server): * **pnpm store**, keyed on the store layout version (v11) and a `sha256sum` of `pnpm-lock.yaml`. Installs hardlink from the store instead of downloading tarballs again. The key is built in a shell step because `hashFiles()` evaluates empty in this act runner. -* **opencode binary**, keyed on the pinned CLI version (`~/.opencode/bin`). - Small next to the model call, but it removes a network fetch per review. + +The opencode binary cache is gone with the opencode job. PR-Agent is a +long-running container on `server0`, so a review no longer downloads a CLI. Lint and typecheck also share one job: same image, same lockfile, same install. Splitting them duplicated the install and made both compete for @@ -71,6 +72,10 @@ exposure in the review setup — each fixed where it was cheapest. # Failure modes deliberately designed against +The opencode-specific rows are historical since the review moved to +[PR-Agent](pr-agent.md); they are kept because the failure classes still +apply to any review implementation. + | Failure seen | Guard now in place | |---|---| | Error logs posted as review comments | Posting gate is the output contract (a `VERDICT:` line), not the exit code | diff --git a/OKF_Nuxt/index.md b/OKF_Nuxt/index.md index 41f2d09..1be511f 100644 --- a/OKF_Nuxt/index.md +++ b/OKF_Nuxt/index.md @@ -19,7 +19,8 @@ config files — the configs say what, these documents say why. ## CI/CD and releases (2026-10-18) * [PR pipeline layering](decisions/pr-pipeline-layering.md) - Three layers: pre-commit for cheap deterministic checks, Gitea Actions for thorough ones, AI review for judgment. -* [AI review setup](decisions/ai-review-setup.md) - Plan model, env-only auth against prompt injection, read-only agent, verdict line as the posting gate. +* [PR-Agent for Gitea reviews](decisions/pr-agent.md) - A pinned webhook server on server0 replaces the per-PR opencode job; internal-only, scoped bot, OpenCode Go model. +* [AI review setup (opencode)](decisions/ai-review-setup.md) - Superseded 2026-10-30; kept for the env-only auth and verdict-gate reasoning. * [Vulnerability audit policy](decisions/vulnerability-audit-policy.md) - Blocking audit; reviewed ignore-list for unfixable advisories in pnpm-workspace.yaml. * [Release engineering](decisions/release-engineering.md) - release-please in manifest mode; conventional commits enforced at commit time. * [Snyk paused and secrets policy](decisions/snyk-paused-and-secrets-policy.md) - Quota-paused job kept in place; `write:issue` scope required on every workflow token. diff --git a/OKF_Nuxt/log.md b/OKF_Nuxt/log.md index f924e3a..65d59fd 100644 --- a/OKF_Nuxt/log.md +++ b/OKF_Nuxt/log.md @@ -1,5 +1,12 @@ # Update Log +## 2026-10-30 (PR-Agent replaces the opencode review job) + +* **Decision**: [PR-Agent for Gitea reviews](decisions/pr-agent.md) - a pinned `pragent/pr-agent:0.49.0-gitea_app` container on `server0` reviews PRs through the Gitea bot user `pr-agent`; the endpoint stays on the `gitea_gitea` Docker network. +* **Update**: [pr-checker.yml](../.gitea/workflows/pr-checker.yml) - removed the `review` job, the opencode installer and the verdict-posting step. PR-Agent now runs `/describe` and `/review` on PR open/reopen and answers slash commands. +* **Creation**: `deploy/pr-agent/` - compose service, example environment and operator README. The real `.env` lives only at `/home/noel/self-hosted/pr-agent/.env` (mode 600) on `server0`. +* **State**: the container is running and the webhook signature path is verified. Gitea gained `[webhook] ALLOWED_HOST_LIST = private:3000` (one restart, healthy) and the repository has a signed webhook. The OpenCode Go API key was still missing at commit time, so no model call or real review has run yet. + ## 2026-10-27 (release-please still never tagged: the deleted head branch) * **Fix**: [release-please-config.json](../release-please-config.json) gained `"changelog-host": "https://git.noelsabia.dev"` - the changelog compare links were generated against `github.com/CV_Website/CV_Site_Nuxt`, a host this repository does not live on. Root cause of the missing tags: **Gitea rewrites `head.ref` to `refs/pull//head` when the merged PR's branch is deleted**, and release-please parses that field as the release branch, so `BranchName.parse` fails and the release is dropped - silently, exit code 0. Evidence: run 143 (task 475) logs `✖ Bad branch name: refs/pull/22/head` right after `Found pull request #22`, then `Expected 1 releases, only found 0`; #22 did carry `autorelease: pending`. The repository deleted every merged branch (`default_delete_branch_after_merge: true`); it is `false` now. Four versions (1.1.0-1.4.0) were consumed by the manifest with no tag ever created, so the release baseline has to be restored by hand. See [Release engineering](decisions/release-engineering.md). diff --git a/OKF_Nuxt/open-questions.md b/OKF_Nuxt/open-questions.md index a17754c..e0e7285 100644 --- a/OKF_Nuxt/open-questions.md +++ b/OKF_Nuxt/open-questions.md @@ -16,7 +16,8 @@ generated: { by: opencode-go/glm-5.3-flash, at: 2026-10-18T12:41:52Z } | Whether these decisions stay in this bundle or fold into the sibling `OKF_CV_Website` bundle, which already describes the frontend at design level | after the production image exists | None. | | When and how often Snyk runs once re-enabled: weekly schedule, ready-for-review gate, or per-push | re-enabling the snyk job | Stay disabled. | | Whether the AI review job should gate merges (required status check on the verdict) or stay advisory | branch protection setup | Advisory. The review comment is information; blocking merges on an AI verdict is a policy choice, not a technical one. | -| How the opencode CLI version in CI gets upgraded: manually bump the pinned 2.0.32, or automate when a new major appears | first review failure after an opencode release | Manual bump. Pinning exists so upgrades are decisions. | +| ~~How the opencode CLI version in CI gets upgraded~~ - **closed** (2026-10-30): the opencode job was removed; the review path is a pinned PR-Agent container. See [PR-Agent for Gitea reviews](decisions/pr-agent.md) | done | — | +| Whether `glm-5.3-flash` through PR-Agent produces acceptable reviews on this repository | first PR after the OpenCode Go key is set | Keep it; `glm-5.3` is the configured fallback. | | ~~Whether the Go plan's per-model usage windows survive real review frequency, and which model the review should use~~ - **decided** (2026-10-20): review model is `opencode-go/claude-haiku-5-5#medium` in [pr-checker.yml](../.gitea/workflows/pr-checker.yml). Cheap per token, and it has a real `#medium` effort level; `deepseek-v4.1-flash` only exposes low/high/max, so it always paid for maximum reasoning. The earlier pro -> flash switch (two consecutive `Endpoint is unavailable` failures) is in the [log](../log.md) | done | — | | Removing the two reviewed audit ignores when `node-forge` or `braces` ship patched releases | next dependency update round | Watch for new releases. | diff --git a/deploy/pr-agent/.env.example b/deploy/pr-agent/.env.example new file mode 100644 index 0000000..7d2318b --- /dev/null +++ b/deploy/pr-agent/.env.example @@ -0,0 +1,25 @@ +# Copy to .env on server0 and fill in; never commit .env. +# chmod 600 .env + +CONFIG__GIT_PROVIDER=gitea + +# The API is reached over the Docker network; links in comments use the +# public URL instead. +GITEA__URL=http://gitea:3000 +GITEA__WEB_URL=https://git.noelsabia.dev + +# Bot user pr-agent, scoped token (read:repository, write:issue, read:user). +# Not the admin account and not a workflow secret. +GITEA__PERSONAL_ACCESS_TOKEN= + +# Secret configured on the Gitea webhook. Required: the server rejects +# unsigned webhooks with HTTP 403. +GITEA__WEBHOOK_SECRET= + +# OpenCode Go exposes an OpenAI-compatible chat-completions endpoint, so +# PR-Agent reaches it through its openai provider with a custom base URL. +CONFIG__MODEL=openai/glm-5.3-flash +CONFIG__FALLBACK_MODELS=["openai/glm-5.3"] +CONFIG__CUSTOM_MODEL_MAX_TOKENS=128000 +OPENAI__API_BASE=https://opencode.ai/inference/go/openai/v1 +OPENAI__KEY= diff --git a/deploy/pr-agent/README.md b/deploy/pr-agent/README.md new file mode 100644 index 0000000..9636cc2 --- /dev/null +++ b/deploy/pr-agent/README.md @@ -0,0 +1,53 @@ +# PR-Agent for Gitea + +PR-Agent runs as a webhook server next to Gitea on `server0`. Gitea sends +pull-request and comment events over the `gitea_gitea` Docker network; the +endpoint is not published to the internet. + +| Piece | Value | +|---|---| +| Image | `pragent/pr-agent:0.49.0-gitea_app` | +| Container | `pr-agent` | +| Webhook URL, from Gitea | `http://pr-agent:3000/api/v1/gitea_webhooks` | +| Config | `/home/noel/self-hosted/pr-agent/.env` (mode 600) | +| Logs | `docker logs -f pr-agent` | +| Upgrade | bump the image tag, then `docker compose up -d` in this directory | + +## Gitea side + +1. The bot user `pr-agent` is a collaborator on `CV_Website/CV_Site_Nuxt` with + write permission. Its personal access token is scoped to + `read:repository`, `write:issue` and `read:user`. +2. The repository webhook sends `push`, `issues`, `pull_request` and + `issue_comment` events, with JSON content type and the shared secret. +3. Gitea's `[webhook] ALLOWED_HOST_LIST` includes `private:3000`. Without it, + Gitea's default egress policy refuses webhook deliveries to private + addresses, including the Docker network. + +## AI model + +The agent uses OpenCode Go's OpenAI-compatible endpoint: + +```text +model openai/glm-5.3-flash +fallback openai/glm-5.3 +api base https://opencode.ai/inference/go/openai/v1 +``` + +`CONFIG__CUSTOM_MODEL_MAX_TOKENS` tells PR-Agent the context limit, because +the model is not in its token table. The effective review budget is still +capped by PR-Agent's default `config.max_model_tokens` of 32000. + +## First check + +Open a pull request in `CV_Website/CV_Site_Nuxt`. The server runs `/describe` +and `/review` on open/reopen; comment commands such as `/review`, `/improve` +and `/ask` are handled from the PR conversation. If nothing appears: + +```sh +docker compose logs --tail=100 pr-agent +``` + +A `403` in the Gitea webhook delivery log means the secret does not match or +`ALLOWED_HOST_LIST` is still missing; a `401` from PR-Agent means the +signature header and secret disagree. diff --git a/deploy/pr-agent/docker-compose.yml b/deploy/pr-agent/docker-compose.yml new file mode 100644 index 0000000..8142bce --- /dev/null +++ b/deploy/pr-agent/docker-compose.yml @@ -0,0 +1,38 @@ +# PR-Agent webhook server for the self-hosted Gitea instance. +# +# Runs on the existing gitea_gitea network and publishes no ports. Gitea +# reaches it as http://pr-agent:3000/api/v1/gitea_webhooks, so the webhook +# endpoint is never internet-facing. Gitea still publishes comment links with +# its own ROOT_URL (https://git.noelsabia.dev). +# +# Deployed by hand on server0 from /home/noel/self-hosted/pr-agent; see the +# README next to this file. + +services: + pr-agent: + image: pragent/pr-agent:0.49.0-gitea_app + container_name: pr-agent + restart: unless-stopped + env_file: + - .env + environment: + PORT: "3000" + # Importing the app costs roughly 250 MB. Two workers leave headroom on + # the 3.8 GB host that also runs Gitea, its runner and a web app. + GUNICORN_WORKERS: "2" + mem_limit: 1g + networks: + - gitea + healthcheck: + # The server has no HTTP health route; an open TCP socket is enough to + # distinguish a running gunicorn master from a crashed container. + test: ["CMD", "python", "-c", "import socket; socket.create_connection(('127.0.0.1', 3000), 3).close()"] + interval: 30s + timeout: 5s + retries: 3 + start_period: 30s + +networks: + gitea: + external: true + name: gitea_gitea From f5810960a8b9a11cb5cf8b636d307a4cadfbef12 Mon Sep 17 00:00:00 2001 From: Noel Sabia Date: Fri, 30 Oct 2026 21:09:19 +0100 Subject: [PATCH 2/9] chore(deploy): add least-privilege PR-Agent operator access --- deploy/pr-agent/README.md | 48 ++++++++- deploy/pr-agent/remove-noel-access.sh | 56 +++++++++++ deploy/pr-agent/setup-agent-access.sh | 135 ++++++++++++++++++++++++++ 3 files changed, 235 insertions(+), 4 deletions(-) create mode 100755 deploy/pr-agent/remove-noel-access.sh create mode 100755 deploy/pr-agent/setup-agent-access.sh diff --git a/deploy/pr-agent/README.md b/deploy/pr-agent/README.md index 9636cc2..71f3b4e 100644 --- a/deploy/pr-agent/README.md +++ b/deploy/pr-agent/README.md @@ -9,9 +9,11 @@ endpoint is not published to the internet. | Image | `pragent/pr-agent:0.49.0-gitea_app` | | Container | `pr-agent` | | Webhook URL, from Gitea | `http://pr-agent:3000/api/v1/gitea_webhooks` | -| Config | `/home/noel/self-hosted/pr-agent/.env` (mode 600) | -| Logs | `docker logs -f pr-agent` | -| Upgrade | bump the image tag, then `docker compose up -d` in this directory | +| Config | `/opt/pr-agent/.env` (root, mode 600) | +| Logs | `ssh … agent@server0 logs` | +| Deploy / restart | `ssh … agent@server0 deploy` | +| Status | `ssh … agent@server0 status` | +| Upgrade | edit the root-owned compose file, then run `deploy` | ## Gitea side @@ -24,6 +26,36 @@ endpoint is not published to the internet. Gitea's default egress policy refuses webhook deliveries to private addresses, including the Docker network. +## Operator access + +The agent does not log in as `noel`. A dedicated `agent` account has one +forced command and three actions: + +```sh +ssh -i ~/.ssh/pr_agent_control -o IdentitiesOnly=yes agent@91.99.207.62 status +ssh -i ~/.ssh/pr_agent_control -o IdentitiesOnly=yes agent@91.99.207.62 logs +ssh -i ~/.ssh/pr_agent_control -o IdentitiesOnly=yes agent@91.99.207.62 deploy +``` + +The SSH key is restricted with `restrict,command=…`; the account has no +Docker group, no general sudo, and no shell. Sudo permits only the three +root-owned helper scripts in `/usr/local/sbin`, and those helpers operate on +the fixed `/opt/pr-agent/docker-compose.yml`. The compose file, `.env` and +helpers are root-owned, so the agent cannot turn “restart” into a different +container or a host mount. + +`setup-agent-access.sh` creates the account and moves the stack to +`/opt/pr-agent`. `remove-noel-access.sh` then removes the inherited access +from `noel`: the `docker` and `sudo` groups, the keys in +`/home/noel/.ssh/authorized_keys`, and the old PR-Agent directory. Run both +on the server as root, and only run the second after the restricted command +works and you have another admin path. + +For git, use a repository-scoped deploy key instead of the personal Gitea +key: `~/.ssh/pr_agent_gitea.pub` is added as a write deploy key on +`CV_Website/CV_Site_Nuxt`. The old personal key must be removed from Gitea, +or it still grants every repository the user can see. + ## AI model The agent uses OpenCode Go's OpenAI-compatible endpoint: @@ -38,6 +70,14 @@ api base https://opencode.ai/inference/go/openai/v1 the model is not in its token table. The effective review budget is still capped by PR-Agent's default `config.max_model_tokens` of 32000. +The transfer file used during installation was empty, so set the key as +root and redeploy: + +```sh +sudoedit /opt/pr-agent/.env # set OPENAI__KEY=… +sudo /usr/local/sbin/pr-agent-deploy +``` + ## First check Open a pull request in `CV_Website/CV_Site_Nuxt`. The server runs `/describe` @@ -45,7 +85,7 @@ and `/review` on open/reopen; comment commands such as `/review`, `/improve` and `/ask` are handled from the PR conversation. If nothing appears: ```sh -docker compose logs --tail=100 pr-agent +ssh -i ~/.ssh/pr_agent_control -o IdentitiesOnly=yes agent@91.99.207.62 logs ``` A `403` in the Gitea webhook delivery log means the secret does not match or diff --git a/deploy/pr-agent/remove-noel-access.sh b/deploy/pr-agent/remove-noel-access.sh new file mode 100755 index 0000000..2036290 --- /dev/null +++ b/deploy/pr-agent/remove-noel-access.sh @@ -0,0 +1,56 @@ +#!/usr/bin/env bash +# Final step: remove the agent's inherited noel access. +# +# Run on server0 only after the agent command works: +# ssh -i ~/.ssh/pr_agent_control -o IdentitiesOnly=yes agent@91.99.207.62 status +# +# This removes noel from docker and sudo, clears noel's authorized_keys, +# and deletes the old PR-Agent directory that held the secrets. Make sure +# you have another admin path (provider console or a new key) first. + +set -euo pipefail + +if [ "$(id -u)" -ne 0 ]; then + echo "run as root" >&2 + exit 1 +fi + +cat <<'EOF' +This will: + - remove noel from the docker and sudo groups + - clear every key in /home/noel/.ssh/authorized_keys + - delete /home/noel/self-hosted/pr-agent (the /opt copy remains) +Existing noel SSH sessions keep their old groups until they log out. +Make sure you have another admin path before continuing. +EOF +read -r -p "Type REMOVE to continue: " answer +[ "$answer" = "REMOVE" ] || { echo "aborted"; exit 1; } + +if id -nG noel | tr ' ' '\n' | grep -qx docker; then + gpasswd -d noel docker +fi +if id -nG noel | tr ' ' '\n' | grep -qx sudo; then + deluser noel sudo +fi + +if [ -f /home/noel/.ssh/authorized_keys ]; then + cp -a /home/noel/.ssh/authorized_keys \ + "/root/noel-authorized_keys.$(date +%Y%m%d-%H%M%S).bak" + : > /home/noel/.ssh/authorized_keys + chown noel:noel /home/noel/.ssh/authorized_keys + chmod 600 /home/noel/.ssh/authorized_keys +fi + +rm -rf /home/noel/self-hosted/pr-agent + +cat <<'EOF' + +Done. Test the restricted path again: + + ssh -i ~/.ssh/pr_agent_control -o IdentitiesOnly=yes agent@91.99.207.62 status + +Still to do outside this script: + - remove the old personal SSH key from Gitea (Settings > SSH / GPG Keys) + - add ~/.ssh/pr_agent_gitea.pub as a write deploy key on CV_Site_Nuxt + - put the OpenCode Go key in /opt/pr-agent/.env and run the deploy helper +EOF diff --git a/deploy/pr-agent/setup-agent-access.sh b/deploy/pr-agent/setup-agent-access.sh new file mode 100755 index 0000000..70acebf --- /dev/null +++ b/deploy/pr-agent/setup-agent-access.sh @@ -0,0 +1,135 @@ +#!/usr/bin/env bash +# One-time root setup for the least-privilege PR-Agent operator account. +# +# Run on server0: +# sudo bash /home/noel/agent-access-setup.sh +# +# This creates the agent user and moves the PR-Agent stack to /opt/pr-agent. +# It does NOT remove noel's current docker/sudo access. Verify the agent +# command printed at the end first, then run remove-noel-access.sh. + +set -euo pipefail + +if [ "$(id -u)" -ne 0 ]; then + echo "run as root" >&2 + exit 1 +fi + +AGENT_USER=agent +AGENT_HOME=/home/$AGENT_USER +PR_AGENT_DIR=/opt/pr-agent +SRC_DIR=/home/noel/self-hosted/pr-agent +PUBKEY_FILE=/home/noel/.ssh/pr_agent_control.pub +DOCKER=/usr/bin/docker + +for f in "$SRC_DIR/docker-compose.yml" "$SRC_DIR/README.md" "$SRC_DIR/.env" "$PUBKEY_FILE"; do + [ -f "$f" ] || { echo "missing $f" >&2; exit 1; } +done +case "$(cat "$PUBKEY_FILE")" in + ssh-*|ecdsa-*|sk-ssh-*) ;; + *) echo "$PUBKEY_FILE does not look like an SSH public key" >&2; exit 1 ;; +esac +grep -q '^Include /etc/ssh/sshd_config.d/\*.conf' /etc/ssh/sshd_config \ + || { echo "sshd does not include sshd_config.d" >&2; exit 1; } + +if ! id "$AGENT_USER" >/dev/null 2>&1; then + useradd --create-home --shell /bin/bash "$AGENT_USER" +fi +passwd -l "$AGENT_USER" >/dev/null 2>&1 || true +chmod 700 "$AGENT_HOME" +install -d -m 700 -o "$AGENT_USER" -g "$AGENT_USER" "$AGENT_HOME/.ssh" + +# The stack must not be writable by the agent: a changed compose file would +# turn "restart the service" into arbitrary root containers. +install -d -m 755 -o root -g root "$PR_AGENT_DIR" +if [ ! -f "$PR_AGENT_DIR/docker-compose.yml" ]; then + install -m 644 -o root -g root "$SRC_DIR/docker-compose.yml" "$PR_AGENT_DIR/docker-compose.yml" +fi +install -m 644 -o root -g root "$SRC_DIR/README.md" "$PR_AGENT_DIR/README.md" +if [ ! -f "$PR_AGENT_DIR/.env" ]; then + install -m 600 -o root -g root "$SRC_DIR/.env" "$PR_AGENT_DIR/.env" +fi +if ! grep -q '^name:' "$PR_AGENT_DIR/docker-compose.yml"; then + sed -i '1i name: pr-agent' "$PR_AGENT_DIR/docker-compose.yml" +fi + +cat > /usr/local/sbin/pr-agent-deploy < /usr/local/sbin/pr-agent-logs < /usr/local/sbin/pr-agent-status < /usr/local/sbin/pr-agent-control <<'EOF' +#!/bin/sh +set -eu +case "${SSH_ORIGINAL_COMMAND:-}" in + deploy) exec sudo -n /usr/local/sbin/pr-agent-deploy ;; + logs) exec sudo -n /usr/local/sbin/pr-agent-logs ;; + status) exec sudo -n /usr/local/sbin/pr-agent-status ;; + *) echo "allowed: deploy, logs, status" >&2; exit 1 ;; +esac +EOF + +chown root:root /usr/local/sbin/pr-agent-deploy /usr/local/sbin/pr-agent-logs \ + /usr/local/sbin/pr-agent-status /usr/local/sbin/pr-agent-control +chmod 755 /usr/local/sbin/pr-agent-deploy /usr/local/sbin/pr-agent-logs \ + /usr/local/sbin/pr-agent-status /usr/local/sbin/pr-agent-control + +cat > /etc/sudoers.d/pr-agent-control <<'EOF' +agent ALL=(root) NOPASSWD: /usr/local/sbin/pr-agent-deploy, /usr/local/sbin/pr-agent-logs, /usr/local/sbin/pr-agent-status +EOF +chmod 440 /etc/sudoers.d/pr-agent-control +visudo -cf /etc/sudoers.d/pr-agent-control >/dev/null + +PUB=$(cat "$PUBKEY_FILE") +printf 'restrict,command="/usr/local/sbin/pr-agent-control" %s\n' "$PUB" \ + > "$AGENT_HOME/.ssh/authorized_keys" +chown "$AGENT_USER:$AGENT_USER" "$AGENT_HOME/.ssh/authorized_keys" +chmod 600 "$AGENT_HOME/.ssh/authorized_keys" + +cat > /etc/ssh/sshd_config.d/60-pr-agent-agent.conf <<'EOF' +Match User agent + ForceCommand /usr/local/sbin/pr-agent-control + PermitTTY no + AllowTcpForwarding no + X11Forwarding no + PermitTunnel no + AllowAgentForwarding no +EOF +chmod 644 /etc/ssh/sshd_config.d/60-pr-agent-agent.conf +if ! sshd -t; then + rm -f /etc/ssh/sshd_config.d/60-pr-agent-agent.conf + echo "sshd config test failed; removed the new file" >&2 + exit 1 +fi +systemctl reload ssh + +cd "$PR_AGENT_DIR" +"$DOCKER" compose pull +"$DOCKER" compose up -d +sleep 5 +"$DOCKER" compose ps + +cat <<'EOF' + +Agent access is ready. Test from the laptop: + + ssh -i ~/.ssh/pr_agent_control -o IdentitiesOnly=yes agent@91.99.207.62 status + +Old access is still in place. Only after that command works, run: + + sudo bash /home/noel/agent-access-remove.sh +EOF From b84d353dcb875359f39f4b272a540df5be04add9 Mon Sep 17 00:00:00 2001 From: Noel Sabia Date: Fri, 30 Oct 2026 21:11:19 +0100 Subject: [PATCH 3/9] docs(pr-agent): document the OpenCode Go session header --- OKF_Nuxt/decisions/pr-agent.md | 4 ++++ deploy/pr-agent/.env.example | 3 +++ deploy/pr-agent/README.md | 3 +++ 3 files changed, 10 insertions(+) diff --git a/OKF_Nuxt/decisions/pr-agent.md b/OKF_Nuxt/decisions/pr-agent.md index 3cb9232..542ba4b 100644 --- a/OKF_Nuxt/decisions/pr-agent.md +++ b/OKF_Nuxt/decisions/pr-agent.md @@ -52,6 +52,10 @@ api base https://opencode.ai/inference/go/openai/v1 model table does not know; PR-Agent's default `config.max_model_tokens` still caps the review budget at 32000. +OpenCode Go requires an `x-opencode-session` header. PR-Agent sends the +stable id `pr-agent` through `LITELLM__EXTRA_HEADERS`; without it the +provider rejects the request before it reaches the model. + # Why * One container replaces a per-PR CLI install, binary cache and prompt diff --git a/deploy/pr-agent/.env.example b/deploy/pr-agent/.env.example index 7d2318b..559d328 100644 --- a/deploy/pr-agent/.env.example +++ b/deploy/pr-agent/.env.example @@ -23,3 +23,6 @@ CONFIG__FALLBACK_MODELS=["openai/glm-5.3"] CONFIG__CUSTOM_MODEL_MAX_TOKENS=128000 OPENAI__API_BASE=https://opencode.ai/inference/go/openai/v1 OPENAI__KEY= + +# OpenCode Go requires a session id header; a stable id is enough here. +LITELLM__EXTRA_HEADERS={"x-opencode-session":"pr-agent"} diff --git a/deploy/pr-agent/README.md b/deploy/pr-agent/README.md index 71f3b4e..19b4029 100644 --- a/deploy/pr-agent/README.md +++ b/deploy/pr-agent/README.md @@ -70,6 +70,9 @@ api base https://opencode.ai/inference/go/openai/v1 the model is not in its token table. The effective review budget is still capped by PR-Agent's default `config.max_model_tokens` of 32000. +OpenCode Go requires an `x-opencode-session` header; PR-Agent sends the +stable id `pr-agent` through `LITELLM__EXTRA_HEADERS`. + The transfer file used during installation was empty, so set the key as root and redeploy: From 3eac73255ff5f5b34233576fc8cbcfa97a50d3dc Mon Sep 17 00:00:00 2001 From: Noel Sabia Date: Fri, 30 Oct 2026 21:14:12 +0100 Subject: [PATCH 4/9] fix(deps): sync lockfile and pin patched seroval The merge of main updated package.json to @nuxt/icon 2.6.2 without the lockfile, so frozen installs aborted. Regenerate the lockfile and force seroval 1.6.11 for GHSA-f86p-h4j2-7qgj and GHSA-9wx9-5pv9-3349. --- pnpm-lock.yaml | 115 ++++++++++++++++++++++++++++++++++++-------- pnpm-workspace.yaml | 6 +++ 2 files changed, 100 insertions(+), 21 deletions(-) diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml index 5d79ba5..fd3d6ee 100644 --- a/pnpm-lock.yaml +++ b/pnpm-lock.yaml @@ -6,6 +6,7 @@ settings: overrides: postcss-selector-parser: 7.1.6 + seroval: 1.6.11 importers: @@ -15,11 +16,11 @@ importers: specifier: ^1.2.95 version: 1.2.95 '@nuxt/icon': - specifier: 2.6.0 - version: 2.6.0(@nuxt/schema@4.6.2)(confbox@0.3.1)(dotenv@17.4.2)(giget@3.3.1)(jiti@2.7.0)(magic-string@1.4.3)(oxc-parser@0.153.0)(rolldown@1.2.14)(unplugin@3.4.0(esbuild@0.28.2)(rolldown@1.2.14)(rollup@4.64.8)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1)))(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))(vue@3.5.44(typescript@5.9.3)) + specifier: 2.6.2 + version: 2.6.2(@nuxt/schema@4.6.2)(confbox@0.3.1)(dotenv@17.4.2)(giget@3.3.1)(jiti@2.7.0)(magic-string@1.4.3)(oxc-parser@0.153.0)(rolldown@1.2.14)(unplugin@3.4.0(esbuild@0.28.2)(rolldown@1.2.14)(rollup@4.64.8)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1)))(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))(vue@3.5.44(typescript@5.9.3)) '@nuxtjs/i18n': specifier: 10.6.0 - version: 10.6.0(@nuxt/schema@4.6.2)(db0@0.3.4)(dotenv@17.4.2)(esbuild@0.28.2)(giget@3.3.1)(ioredis@5.11.1(supports-color@10.2.2))(jiti@2.7.0)(rolldown@1.2.14)(rollup@4.64.8)(supports-color@10.2.2)(typescript@5.9.3)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))(vue@3.5.44(typescript@5.9.3)) + version: 10.6.0(@nuxt/schema@4.6.2)(@vue/compiler-dom@3.5.44)(db0@0.3.4)(dotenv@17.4.2)(esbuild@0.28.2)(giget@3.3.1)(ioredis@5.11.1(supports-color@10.2.2))(jiti@2.7.0)(rolldown@1.2.14)(rollup@4.64.8)(supports-color@10.2.2)(typescript@5.9.3)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))(vue@3.5.44(typescript@5.9.3)) '@nuxtjs/seo': specifier: 6.0.1 version: 6.0.1(b12aa32157ad38cf444edd41e3e089a9) @@ -679,8 +680,8 @@ packages: '@iconify-json/material-symbols@1.2.95': resolution: {integrity: sha512-n34GNbwe8We3LPXK2N8JuQewEQkITJiRsmX/0UYJsOyKzviVl22mNfLUiGGtXLKDPqxZa17q1Hg57zdA3BYa0w==} - '@iconify/collections@1.0.754': - resolution: {integrity: sha512-5AJQgPgjBFGwsQGyDjySYvkzX2tU4GO+blKb1HExUuiha3rhvUvw5rvQxZ/WBX3YJFl4kqqV3gcjpdidsXhH/w==} + '@iconify/collections@1.0.758': + resolution: {integrity: sha512-i6z8ImaR9gH/Kj51H81JmGaX1K5OF+SuNZB4DxJwgdweZUBguMaL62EDFqIwF1V8xKfGrOJRB/tx4csYXaNl0w==} '@iconify/types@2.0.0': resolution: {integrity: sha512-+wluvCrRhXrhyOmRDJ3q8mux9JkKy5SJ/v8ol2tu4FVjyYvtEzkc/3pK15ET6RKg4b4w4BmTk1+gsCUhf21Ykg==} @@ -1027,8 +1028,8 @@ packages: vite-plugin-eslint2: optional: true - '@nuxt/icon@2.6.0': - resolution: {integrity: sha512-cMT2gOK0AS8+CFI45Upz0Erzm9wud+iJ/eX/YeWbcw9UmSdU16PjbYyHpRKSALFHoSi3E7j7WRgT/KyU7UG7iA==} + '@nuxt/icon@2.6.2': + resolution: {integrity: sha512-eNVXbKzj1fmrkzcakkix8Pn/7lpd0I1b7xG0shjrlefr2wWIG3o0DrU9EvvT1BCf9UD33MAzoLF1l2Z99CKoTg==} '@nuxt/kit@3.21.11': resolution: {integrity: sha512-0Xi3tgwN77w43Q8GCPIrvWmF1J7Peehkts44E0uKNIml9lB8WoUn8YxyUjxBv47XtVR86NWoWALAT+/IEMHJEA==} @@ -1064,6 +1065,36 @@ packages: rolldown: optional: true + '@nuxt/kit@4.6.3': + resolution: {integrity: sha512-djNup72hMvn7C9xp0/KAYeoY9uzbrPguv91SUBjEeSHh49kP/YI4BvxUVHP8sZd3kms5Ht+IZTJ6XAfm9hofKw==} + engines: {node: ^20.19.0 || >=22.12.0} + peerDependencies: + '@nuxt/schema': ^3.0.0 || ^4.0.0 || ^5.0.0-0 + confbox: '>=0.1.0' + dotenv: '*' + giget: '>=3.1.0' + jiti: ^2.0.0 + mlly: ^1.2.0 + oxc-parser: '>=0.56.0' + rolldown: '>=1.0.0' + peerDependenciesMeta: + '@nuxt/schema': + optional: true + confbox: + optional: true + dotenv: + optional: true + giget: + optional: true + jiti: + optional: true + mlly: + optional: true + oxc-parser: + optional: true + rolldown: + optional: true + '@nuxt/nitro-server@4.6.2': resolution: {integrity: sha512-mOiTpoiSG26/0UI4Nxfc4AK76UaCdpjObLPCF6NTDX9wL6Ed4/95AAVZKbEq7qxtNSla/8F+s8NSY6O1wpJ5bA==} engines: {node: ^22.22.3 || ^24.15.0 || >=26.0.0} @@ -3416,6 +3447,10 @@ packages: resolution: {integrity: sha512-/8UvqAPU9DGTI9k4mxtf49U37Isfwr8Uts96+SBHIkFxPJnHS0Ew4f00sM4Scd8V8EjM0jUNtVDdv1kPdt35lg==} engines: {node: '>= 4'} + ignore@7.0.14: + resolution: {integrity: sha512-wCBiZ77u1tuWde6G/nfOtLaCTYcFDU5yCzARzK10y+rLhzYoL7a7yEemcopcc2Mzow7gZOIjnV2ym1NYmdiJOQ==} + engines: {node: '>= 4'} + image-meta@0.2.2: resolution: {integrity: sha512-3MOLanc3sb3LNGWQl1RlQlNWURE5g32aUphrDyFeCsxBTk08iE3VNe4CwsUZ0Qs1X+EfX0+r29Sxdpza4B+yRA==} @@ -4671,8 +4706,8 @@ packages: resolution: {integrity: sha512-GL2BWwVa6JydKO6l/ljVgjAZF4QJ3S7dWDWi53s5GZT8PJzD2fNxi67HANQGKAqPrwEpL5ba7gUBGi0Ls/sEoQ==} engines: {node: '>=20.0.0'} - seroval@1.6.9: - resolution: {integrity: sha512-UeEzHwAK+yl0YLbsvROV1t5yMYEwZZ0CfKYxDvUgS2fO9Vxdf8djqVIB+OuVpuawRNPqw68LE1Du/GMsW2ZPqA==} + seroval@1.6.11: + resolution: {integrity: sha512-hpb6XnMCGN/A+79Uf8V7/iTGkyyyazNn5X0CoCAp7Uy9vT3RT8jZ9GLcnxGoVjg3P8AArbe4ZVHq6C8oT2a0kA==} engines: {node: '>=10'} serve-placeholder@2.0.2: @@ -6072,7 +6107,7 @@ snapshots: dependencies: '@iconify/types': 2.0.0 - '@iconify/collections@1.0.754': + '@iconify/collections@1.0.758': dependencies: '@iconify/types': 2.0.0 @@ -6129,11 +6164,11 @@ snapshots: '@intlify/shared@11.4.16': {} - '@intlify/unplugin-vue-i18n@11.2.7(rollup@4.64.8)(supports-color@10.2.2)(typescript@5.9.3)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))(vue-i18n@11.4.16(vue@3.5.44(typescript@5.9.3)))(vue@3.5.44(typescript@5.9.3))': + '@intlify/unplugin-vue-i18n@11.2.7(@vue/compiler-dom@3.5.44)(rollup@4.64.8)(supports-color@10.2.2)(typescript@5.9.3)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))(vue-i18n@11.4.16(vue@3.5.44(typescript@5.9.3)))(vue@3.5.44(typescript@5.9.3))': dependencies: '@intlify/bundle-utils': 11.2.7(vue-i18n@11.4.16(vue@3.5.44(typescript@5.9.3))) '@intlify/shared': 11.4.16 - '@intlify/vue-i18n-extensions': 8.0.0(@intlify/shared@11.4.16)(vue-i18n@11.4.16(vue@3.5.44(typescript@5.9.3)))(vue@3.5.44(typescript@5.9.3)) + '@intlify/vue-i18n-extensions': 8.0.0(@intlify/shared@11.4.16)(@vue/compiler-dom@3.5.44)(vue-i18n@11.4.16(vue@3.5.44(typescript@5.9.3)))(vue@3.5.44(typescript@5.9.3)) '@rollup/pluginutils': 5.4.0(rollup@4.64.8) '@typescript-eslint/scope-manager': 8.71.2 '@typescript-eslint/typescript-estree': 8.71.2(supports-color@10.2.2)(typescript@5.9.3) @@ -6147,6 +6182,7 @@ snapshots: vite: 8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1) vue-i18n: 11.4.16(vue@3.5.44(typescript@5.9.3)) transitivePeerDependencies: + - '@vue/compiler-dom' - rollup - supports-color - typescript @@ -6155,12 +6191,12 @@ snapshots: '@intlify/utils@0.14.1': {} - '@intlify/vue-i18n-extensions@8.0.0(@intlify/shared@11.4.16)(vue-i18n@11.4.16(vue@3.5.44(typescript@5.9.3)))(vue@3.5.44(typescript@5.9.3))': + '@intlify/vue-i18n-extensions@8.0.0(@intlify/shared@11.4.16)(@vue/compiler-dom@3.5.44)(vue-i18n@11.4.16(vue@3.5.44(typescript@5.9.3)))(vue@3.5.44(typescript@5.9.3))': dependencies: '@babel/parser': 7.29.9 - '@vue/compiler-dom': 3.5.44 optionalDependencies: '@intlify/shared': 11.4.16 + '@vue/compiler-dom': 3.5.44 vue: 3.5.44(typescript@5.9.3) vue-i18n: 11.4.16(vue@3.5.44(typescript@5.9.3)) @@ -6561,15 +6597,16 @@ snapshots: - vite - webpack - '@nuxt/icon@2.6.0(@nuxt/schema@4.6.2)(confbox@0.3.1)(dotenv@17.4.2)(giget@3.3.1)(jiti@2.7.0)(magic-string@1.4.3)(oxc-parser@0.153.0)(rolldown@1.2.14)(unplugin@3.4.0(esbuild@0.28.2)(rolldown@1.2.14)(rollup@4.64.8)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1)))(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))(vue@3.5.44(typescript@5.9.3))': + '@nuxt/icon@2.6.2(@nuxt/schema@4.6.2)(confbox@0.3.1)(dotenv@17.4.2)(giget@3.3.1)(jiti@2.7.0)(magic-string@1.4.3)(oxc-parser@0.153.0)(rolldown@1.2.14)(unplugin@3.4.0(esbuild@0.28.2)(rolldown@1.2.14)(rollup@4.64.8)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1)))(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))(vue@3.5.44(typescript@5.9.3))': dependencies: - '@iconify/collections': 1.0.754 + '@iconify/collections': 1.0.758 '@iconify/types': 2.0.0 '@iconify/utils': 3.1.7 '@iconify/vue': 5.0.4(vue@3.5.44(typescript@5.9.3)) '@nuxt/devtools-kit': 3.4.4(@nuxt/schema@4.6.2)(confbox@0.3.1)(dotenv@17.4.2)(giget@3.3.1)(jiti@2.7.0)(magic-string@1.4.3)(mlly@1.8.2)(oxc-parser@0.153.0)(rolldown@1.2.14)(unplugin@3.4.0(esbuild@0.28.2)(rolldown@1.2.14)(rollup@4.64.8)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1)))(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1)) - '@nuxt/kit': 4.6.2(@nuxt/schema@4.6.2)(confbox@0.3.1)(dotenv@17.4.2)(giget@3.3.1)(jiti@2.7.0)(magic-string@1.4.3)(mlly@1.8.2)(oxc-parser@0.153.0)(rolldown@1.2.14)(unplugin@3.4.0(esbuild@0.28.2)(rolldown@1.2.14)(rollup@4.64.8)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))) + '@nuxt/kit': 4.6.3(@nuxt/schema@4.6.2)(confbox@0.3.1)(dotenv@17.4.2)(giget@3.3.1)(jiti@2.7.0)(magic-string@1.4.3)(mlly@1.8.2)(oxc-parser@0.153.0)(rolldown@1.2.14)(unplugin@3.4.0(esbuild@0.28.2)(rolldown@1.2.14)(rollup@4.64.8)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))) consola: 3.4.2 + fnv1a-64: 0.1.2 local-pkg: 1.2.1 mlly: 1.8.2 ohash: 2.0.12 @@ -6682,6 +6719,39 @@ snapshots: - magic-string - unplugin + '@nuxt/kit@4.6.3(@nuxt/schema@4.6.2)(confbox@0.3.1)(dotenv@17.4.2)(giget@3.3.1)(jiti@2.7.0)(magic-string@1.4.3)(mlly@1.8.2)(oxc-parser@0.153.0)(rolldown@1.2.14)(unplugin@3.4.0(esbuild@0.28.2)(rolldown@1.2.14)(rollup@4.64.8)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1)))': + dependencies: + consola: 3.4.2 + defu: 6.1.7 + destr: 2.0.5 + errx: 0.2.2 + exsolve: 1.1.3 + ignore: 7.0.14 + klona: 2.0.6 + microdiff: 1.6.0 + nostics: 1.3.0 + package-manager-detector: 1.9.0 + pathe: 2.0.3 + rc9: 3.1.0 + scule: 1.3.0 + std-env: 4.3.0 + tinyexec: 1.3.1 + tinyglobby: 0.2.17 + unctx: 3.0.1(magic-string@1.4.3)(oxc-parser@0.153.0)(rolldown@1.2.14)(unplugin@3.4.0(esbuild@0.28.2)(rolldown@1.2.14)(rollup@4.64.8)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))) + verkit: 0.5.0 + optionalDependencies: + '@nuxt/schema': 4.6.2 + confbox: 0.3.1 + dotenv: 17.4.2 + giget: 3.3.1 + jiti: 2.7.0 + mlly: 1.8.2 + oxc-parser: 0.153.0 + rolldown: 1.2.14 + transitivePeerDependencies: + - magic-string + - unplugin + '@nuxt/nitro-server@4.6.2(6cec1558c59214081a86fad4f67b8fb1)': dependencies: '@nuxt/kit': 4.6.2(@nuxt/schema@4.6.2)(confbox@0.3.1)(dotenv@17.4.2)(giget@3.3.1)(jiti@2.7.0)(magic-string@1.4.3)(mlly@1.8.2)(oxc-parser@0.153.0)(rolldown@1.2.14)(unplugin@3.4.0(esbuild@0.28.2)(rolldown@1.2.14)(rollup@4.64.8)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))) @@ -6815,7 +6885,7 @@ snapshots: pkg-types: 2.3.3 postcss: 8.5.30 rolldown-string: 0.3.1(rolldown@1.2.14) - seroval: 1.6.9 + seroval: 1.6.11 std-env: 4.3.0 ufo: 1.6.4 unenv: 2.0.0-rc.24 @@ -6893,13 +6963,13 @@ snapshots: - rolldown - unplugin - '@nuxtjs/i18n@10.6.0(@nuxt/schema@4.6.2)(db0@0.3.4)(dotenv@17.4.2)(esbuild@0.28.2)(giget@3.3.1)(ioredis@5.11.1(supports-color@10.2.2))(jiti@2.7.0)(rolldown@1.2.14)(rollup@4.64.8)(supports-color@10.2.2)(typescript@5.9.3)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))(vue@3.5.44(typescript@5.9.3))': + '@nuxtjs/i18n@10.6.0(@nuxt/schema@4.6.2)(@vue/compiler-dom@3.5.44)(db0@0.3.4)(dotenv@17.4.2)(esbuild@0.28.2)(giget@3.3.1)(ioredis@5.11.1(supports-color@10.2.2))(jiti@2.7.0)(rolldown@1.2.14)(rollup@4.64.8)(supports-color@10.2.2)(typescript@5.9.3)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))(vue@3.5.44(typescript@5.9.3))': dependencies: '@intlify/core': 11.4.16 '@intlify/h3': 0.7.4 '@intlify/message-compiler': 11.4.16 '@intlify/shared': 11.4.16 - '@intlify/unplugin-vue-i18n': 11.2.7(rollup@4.64.8)(supports-color@10.2.2)(typescript@5.9.3)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))(vue-i18n@11.4.16(vue@3.5.44(typescript@5.9.3)))(vue@3.5.44(typescript@5.9.3)) + '@intlify/unplugin-vue-i18n': 11.2.7(@vue/compiler-dom@3.5.44)(rollup@4.64.8)(supports-color@10.2.2)(typescript@5.9.3)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))(vue-i18n@11.4.16(vue@3.5.44(typescript@5.9.3)))(vue@3.5.44(typescript@5.9.3)) '@intlify/utils': 0.14.1 '@miyaneee/rollup-plugin-json5': 1.2.0(rollup@4.64.8) '@nuxt/kit': 4.6.2(@nuxt/schema@4.6.2)(confbox@0.2.4)(dotenv@17.4.2)(giget@3.3.1)(jiti@2.7.0)(magic-string@0.30.21)(mlly@1.8.2)(oxc-parser@0.141.0)(rolldown@1.2.14)(unplugin@3.4.0(esbuild@0.28.2)(rolldown@1.2.14)(rollup@4.64.8)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))) @@ -6944,6 +7014,7 @@ snapshots: - '@vercel/blob' - '@vercel/functions' - '@vercel/kv' + - '@vue/compiler-dom' - aws4fetch - bun-types-no-globals - db0 @@ -9109,6 +9180,8 @@ snapshots: ignore@7.0.12: {} + ignore@7.0.14: {} + image-meta@0.2.2: {} import-fresh@3.3.1: @@ -10785,7 +10858,7 @@ snapshots: serialize-javascript@7.1.2: {} - seroval@1.6.9: {} + seroval@1.6.11: {} serve-placeholder@2.0.2: dependencies: diff --git a/pnpm-workspace.yaml b/pnpm-workspace.yaml index df1ce61..3913efe 100644 --- a/pnpm-workspace.yaml +++ b/pnpm-workspace.yaml @@ -21,6 +21,12 @@ overrides: # the override when tailwindcss ships >= 7.1.6 itself (or the site moves # to Tailwind v4). postcss-selector-parser: 7.1.6 + # GHSA-f86p-h4j2-7qgj and GHSA-9wx9-5pv9-3349 (moderate, 2026-10-30): + # seroval < 1.6.11 allows code/script injection through serialized output. + # Nuxt's vite-builder still resolves 1.6.9; the patched 1.6.11 is the + # smallest version that clears both advisories. Remove this when Nuxt ships + # a vite-builder that resolves >= 1.6.11 itself. + seroval: 1.6.11 minimumReleaseAgeExclude: - '@rollup/rollup-darwin-x64@4.64.8' - '@rollup/rollup-freebsd-arm64@4.64.8' From a43134ad83bece7670543e557f40407892dbf48e Mon Sep 17 00:00:00 2001 From: Noel Sabia Date: Fri, 30 Oct 2026 21:14:15 +0100 Subject: [PATCH 5/9] fix(ci): repair PR-Agent model routing OpenCode Go rejects requests without x-opencode-session, and LiteLLM needs the openai/ prefix on the fallback model. Supply the header through LITELLM__EXTRA_HEADERS, keep the prefixed fallback, and stop auto-running /improve so a PR gets one review plus /describe. --- OKF_Nuxt/decisions/pr-agent.md | 9 +++++++-- OKF_Nuxt/log.md | 7 +++++++ deploy/pr-agent/.env.example | 4 ++++ deploy/pr-agent/README.md | 8 +++++++- 4 files changed, 25 insertions(+), 3 deletions(-) diff --git a/OKF_Nuxt/decisions/pr-agent.md b/OKF_Nuxt/decisions/pr-agent.md index 542ba4b..f49cb70 100644 --- a/OKF_Nuxt/decisions/pr-agent.md +++ b/OKF_Nuxt/decisions/pr-agent.md @@ -82,6 +82,9 @@ provider rejects the request before it reaches the model. * The webhook sends `push`, `issues`, `pull_request` and `issue_comment` events. Only the last two change behaviour today; `push` is kept because PR-Agent may handle push commands in a later configuration. +* Auto commands are `/describe` and `/review`. `/improve` stays available + on demand; the default auto list would add a second model call and a + second comment to every PR. * Secrets live only in `/home/noel/self-hosted/pr-agent/.env` (mode 600) on `server0`. The repository contains the compose file and an example env file, never the token or webhook secret. @@ -89,8 +92,10 @@ provider rejects the request before it reaches the model. # Not verified * The OpenCode Go API key was not present when this was committed, so no - model call and no real review have run. The first PR after the key is set - is the verification. + model call has completed. A dummy-key call now reaches the provider's + authentication check instead of failing on the missing session header, + so the remaining blocker is the credential. The first PR after the key is + set is the real verification. * Whether `glm-5.3-flash` handles PR-Agent's structured review output well enough. `glm-5.3` is configured as the fallback. * Whether two gunicorn workers and the 1 GB memory limit hold under diff --git a/OKF_Nuxt/log.md b/OKF_Nuxt/log.md index 65d59fd..f71053c 100644 --- a/OKF_Nuxt/log.md +++ b/OKF_Nuxt/log.md @@ -1,5 +1,12 @@ # Update Log +## 2026-10-30 (PR #28: lockfile and PR-Agent routing repaired) + +* **Fix**: `pnpm-lock.yaml` - merging `main` left the lockfile at `@nuxt/icon` 2.6.0 while `package.json` asked for 2.6.2, so `pnpm install --frozen-lockfile` aborted in CI. The lockfile now resolves 2.6.2. +* **Fix**: `pnpm-workspace.yaml` - `seroval` 1.6.9 was the two moderate audit findings (GHSA-f86p-h4j2-7qgj, GHSA-9wx9-5pv9-3349). The patched 1.6.11 is forced through `overrides`; the blocking audit now reports only two low-severity advisories and passes the moderate gate. +* **Fix**: PR-Agent model routing - OpenCode Go rejects requests without `x-opencode-session`; `LITELLM__EXTRA_HEADERS` now supplies it, and the fallback keeps the `openai/` prefix. Auto commands are `/describe` and `/review`; `/improve` is on demand. A dummy-key call reaches the provider's auth check instead of failing on the missing header. +* **State**: the OpenCode Go API key is still unset, so no real review has run. The next step is the credential, then a `/review` comment on PR #28. + ## 2026-10-30 (PR-Agent replaces the opencode review job) * **Decision**: [PR-Agent for Gitea reviews](decisions/pr-agent.md) - a pinned `pragent/pr-agent:0.49.0-gitea_app` container on `server0` reviews PRs through the Gitea bot user `pr-agent`; the endpoint stays on the `gitea_gitea` Docker network. diff --git a/deploy/pr-agent/.env.example b/deploy/pr-agent/.env.example index 559d328..d956a54 100644 --- a/deploy/pr-agent/.env.example +++ b/deploy/pr-agent/.env.example @@ -26,3 +26,7 @@ OPENAI__KEY= # OpenCode Go requires a session id header; a stable id is enough here. LITELLM__EXTRA_HEADERS={"x-opencode-session":"pr-agent"} + +# Auto commands on PR open. /improve remains available as a comment command; +# leaving it in the auto list adds a second model call to every PR. +GITEA__PR_COMMANDS=["/describe","/review"] diff --git a/deploy/pr-agent/README.md b/deploy/pr-agent/README.md index 19b4029..18f107c 100644 --- a/deploy/pr-agent/README.md +++ b/deploy/pr-agent/README.md @@ -15,6 +15,10 @@ endpoint is not published to the internet. | Status | `ssh … agent@server0 status` | | Upgrade | edit the root-owned compose file, then run `deploy` | +The table describes the target state. The live stack is still at +`/home/noel/self-hosted/pr-agent` and is managed with `noel`'s SSH key until +`setup-agent-access.sh` has been run. + ## Gitea side 1. The bot user `pr-agent` is a collaborator on `CV_Website/CV_Site_Nuxt` with @@ -85,7 +89,9 @@ sudo /usr/local/sbin/pr-agent-deploy Open a pull request in `CV_Website/CV_Site_Nuxt`. The server runs `/describe` and `/review` on open/reopen; comment commands such as `/review`, `/improve` -and `/ask` are handled from the PR conversation. If nothing appears: +and `/ask` are handled from the PR conversation. `/improve` is deliberately +on demand: adding it to the auto list would make a second model call and a +second comment for every PR. If nothing appears: ```sh ssh -i ~/.ssh/pr_agent_control -o IdentitiesOnly=yes agent@91.99.207.62 logs From 636a65dd05049c37a8b232843a96c65c1f995d08 Mon Sep 17 00:00:00 2001 From: Noel Sabia Date: Fri, 30 Oct 2026 21:28:05 +0100 Subject: [PATCH 6/9] docs(pr-agent): record the first successful review The key is wired into the live server .env; glm-5.3-flash returned OK and /review on PR #28 posted a PR Reviewer Guide. --- OKF_Nuxt/decisions/pr-agent.md | 17 +++++++++-------- OKF_Nuxt/log.md | 3 ++- deploy/pr-agent/README.md | 11 ++++------- 3 files changed, 15 insertions(+), 16 deletions(-) diff --git a/OKF_Nuxt/decisions/pr-agent.md b/OKF_Nuxt/decisions/pr-agent.md index f49cb70..18b0567 100644 --- a/OKF_Nuxt/decisions/pr-agent.md +++ b/OKF_Nuxt/decisions/pr-agent.md @@ -89,21 +89,22 @@ provider rejects the request before it reaches the model. `server0`. The repository contains the compose file and an example env file, never the token or webhook secret. +# Evidence + +* 2026-10-30: a direct `glm-5.3-flash` call through the handler returned + `OK`, and `/review` on PR #28 posted a PR Reviewer Guide through the Gitea + comment API. The key is set only in the server-side `.env`. + # Not verified -* The OpenCode Go API key was not present when this was committed, so no - model call has completed. A dummy-key call now reaches the provider's - authentication check instead of failing on the missing session header, - so the remaining blocker is the credential. The first PR after the key is - set is the real verification. -* Whether `glm-5.3-flash` handles PR-Agent's structured review output well - enough. `glm-5.3` is configured as the fallback. +* Whether the model finds the same class of issues as the opencode prompt on + larger diffs. The first review found none; `glm-5.3` remains the fallback. * Whether two gunicorn workers and the 1 GB memory limit hold under concurrent reviews. The host has roughly 2.5 GB available with Gitea and its runner idle. * Whether the default review prompt is specific enough for this repository. A `.pr_agent.toml` with project instructions is deliberately absent until - the first real review shows what it misses. + a real review shows what it misses. # Revisit when diff --git a/OKF_Nuxt/log.md b/OKF_Nuxt/log.md index f71053c..1662e6b 100644 --- a/OKF_Nuxt/log.md +++ b/OKF_Nuxt/log.md @@ -5,7 +5,8 @@ * **Fix**: `pnpm-lock.yaml` - merging `main` left the lockfile at `@nuxt/icon` 2.6.0 while `package.json` asked for 2.6.2, so `pnpm install --frozen-lockfile` aborted in CI. The lockfile now resolves 2.6.2. * **Fix**: `pnpm-workspace.yaml` - `seroval` 1.6.9 was the two moderate audit findings (GHSA-f86p-h4j2-7qgj, GHSA-9wx9-5pv9-3349). The patched 1.6.11 is forced through `overrides`; the blocking audit now reports only two low-severity advisories and passes the moderate gate. * **Fix**: PR-Agent model routing - OpenCode Go rejects requests without `x-opencode-session`; `LITELLM__EXTRA_HEADERS` now supplies it, and the fallback keeps the `openai/` prefix. Auto commands are `/describe` and `/review`; `/improve` is on demand. A dummy-key call reaches the provider's auth check instead of failing on the missing header. -* **State**: the OpenCode Go API key is still unset, so no real review has run. The next step is the credential, then a `/review` comment on PR #28. +* **Evidence**: the key was wired into the live `.env`; a direct `glm-5.3-flash` call returned `OK`, and `/review` on PR #28 posted a PR Reviewer Guide (no findings). The failed-review comment was removed. +* **State**: the key is set only in the server-side `.env`; the first `/review` posted on PR #28 with no findings. ## 2026-10-30 (PR-Agent replaces the opencode review job) diff --git a/deploy/pr-agent/README.md b/deploy/pr-agent/README.md index 18f107c..59ac864 100644 --- a/deploy/pr-agent/README.md +++ b/deploy/pr-agent/README.md @@ -77,13 +77,10 @@ capped by PR-Agent's default `config.max_model_tokens` of 32000. OpenCode Go requires an `x-opencode-session` header; PR-Agent sends the stable id `pr-agent` through `LITELLM__EXTRA_HEADERS`. -The transfer file used during installation was empty, so set the key as -root and redeploy: - -```sh -sudoedit /opt/pr-agent/.env # set OPENAI__KEY=… -sudo /usr/local/sbin/pr-agent-deploy -``` +The API key lives only in the server's `.env`, never in the repo. Set +`OPENAI__KEY` in the live `/home/noel/self-hosted/pr-agent/.env` until the +`/opt` migration has run; afterwards use `/opt/pr-agent/.env` and the deploy +helper. ## First check From 723c38d2e32c0a3eb8fa96046fcf4ebb9418d54b Mon Sep 17 00:00:00 2001 From: Noel Sabia Date: Fri, 30 Oct 2026 21:35:25 +0100 Subject: [PATCH 7/9] ci(renovate): authenticate github.com release note lookups Renovate fetches changelogs and release notes from github.com. Anonymous requests are rate-limited, so the first run skipped them and printed the "no github.com credentials" warning in the PR body. RENOVATE_GITHUB_COM_TOKEN now comes from a repository secret. It is independent of RENOVATE_TOKEN: any github.com account with read-only access is enough, and no scopes are needed for public repositories. --- .gitea/workflows/renovate.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/.gitea/workflows/renovate.yml b/.gitea/workflows/renovate.yml index aab1f3a..ca8cc2f 100644 --- a/.gitea/workflows/renovate.yml +++ b/.gitea/workflows/renovate.yml @@ -7,7 +7,9 @@ name: Renovate # Manual setup: create a bot account with its full name and email set, give # it write access to this repository, and store a token with # repository read/write, issue read/write, user read and organization read -# as the RENOVATE_TOKEN Actions secret. +# as the RENOVATE_TOKEN Actions secret. Release notes also need a github.com +# token (any account, read-only, no scopes for public repositories) as the +# RENOVATE_GITHUB_COM_TOKEN secret. on: schedule: # Daily at 04:00 UTC. Gitea only schedules workflows that exist on the @@ -35,6 +37,10 @@ jobs: # default branch through this endpoint. RENOVATE_ENDPOINT: https://git.noelsabia.dev/api/v1 RENOVATE_TOKEN: ${{ secrets.RENOVATE_TOKEN }} + # github.com is only used to fetch release notes and other public + # metadata. Anonymous requests are rate-limited, which is why the + # PR body warned that release notes were skipped. + RENOVATE_GITHUB_COM_TOKEN: ${{ secrets.RENOVATE_GITHUB_COM_TOKEN }} # This workflow lives in the repository it updates, so scope the bot # to it instead of every repository its account can see. RENOVATE_REPOSITORIES: CV_Website/CV_Site_Nuxt From da288855885bb5ff63f36c6f6ec09523800e91bc Mon Sep 17 00:00:00 2001 From: Noel Sabia Date: Fri, 30 Oct 2026 21:39:31 +0100 Subject: [PATCH 8/9] refactor(deploy): run PR-Agent inside the Gitea compose stack 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. --- OKF_Nuxt/decisions/pr-agent.md | 37 +++---- OKF_Nuxt/index.md | 3 +- OKF_Nuxt/log.md | 10 +- OKF_Nuxt/pr-agent.md | 123 +++++++++++++++++++++++ deploy/pr-agent/.env.example | 32 ------ deploy/pr-agent/README.md | 99 ------------------- deploy/pr-agent/docker-compose.yml | 38 -------- deploy/pr-agent/remove-noel-access.sh | 56 ----------- deploy/pr-agent/setup-agent-access.sh | 135 -------------------------- 9 files changed, 153 insertions(+), 380 deletions(-) create mode 100644 OKF_Nuxt/pr-agent.md delete mode 100644 deploy/pr-agent/.env.example delete mode 100644 deploy/pr-agent/README.md delete mode 100644 deploy/pr-agent/docker-compose.yml delete mode 100755 deploy/pr-agent/remove-noel-access.sh delete mode 100755 deploy/pr-agent/setup-agent-access.sh diff --git a/OKF_Nuxt/decisions/pr-agent.md b/OKF_Nuxt/decisions/pr-agent.md index 18b0567..7fdd92f 100644 --- a/OKF_Nuxt/decisions/pr-agent.md +++ b/OKF_Nuxt/decisions/pr-agent.md @@ -1,18 +1,18 @@ --- type: Decision title: PR-Agent for Gitea reviews -description: A pinned PR-Agent webhook server on server0 reviews pull requests through a scoped Gitea bot user, replacing the per-PR opencode job. +description: A pinned PR-Agent service inside the Gitea compose stack reviews pull requests through a scoped Gitea bot user, replacing the per-PR opencode job. tags: [decision, ci, ai, gitea, pr-agent, security] status: draft generated: { by: opencode-go/deepseek-v4.1-flash, at: 2026-10-30T20:00:00Z } verified: { by: human:noel, at: not yet } sources: - - id: compose - resource: deploy/pr-agent/docker-compose.yml - title: PR-Agent compose service - - id: env-example - resource: deploy/pr-agent/.env.example - title: Environment variables, without secrets + - id: gitea-compose + resource: /home/noel/self-hosted/gitea/docker-compose.yml + title: Gitea compose stack, pr-agent service + - id: operations + resource: OKF_Nuxt/pr-agent.md + title: PR-Agent operations and configuration - id: pr-checker resource: .gitea/workflows/pr-checker.yml title: PR Check workflow, opencode job removed @@ -30,10 +30,13 @@ sources: # Decision PR-Agent runs as `pragent/pr-agent:0.49.0-gitea_app` in a long-lived -container on `server0`, attached to the existing `gitea_gitea` Docker -network. It publishes no ports. Gitea delivers pull-request and comment -events to `http://pr-agent:3000/api/v1/gitea_webhooks`; the bot user -`pr-agent` posts the result with a scoped personal access token. +container on `server0`, as the `pr-agent` service in the Gitea compose +stack. It attaches to the existing `gitea_gitea` Docker network and +publishes no ports. Gitea delivers pull-request and comment events to +`http://pr-agent:3000/api/v1/gitea_webhooks`; the bot user `pr-agent` +posts the result with a scoped personal access token. The service +definition lives in `/home/noel/self-hosted/gitea/docker-compose.yml`; the +operator guide is [PR-Agent operations](../pr-agent.md). The opencode review job is removed from `pr-checker.yml`. PR-Agent runs `/describe` and `/review` on pull request open/reopen and answers slash @@ -85,15 +88,15 @@ provider rejects the request before it reaches the model. * Auto commands are `/describe` and `/review`. `/improve` stays available on demand; the default auto list would add a second model call and a second comment to every PR. -* Secrets live only in `/home/noel/self-hosted/pr-agent/.env` (mode 600) on - `server0`. The repository contains the compose file and an example env - file, never the token or webhook secret. +* Secrets live only in `/home/noel/self-hosted/gitea/pr-agent.env` (mode + 600) on `server0`. The repository contains the decision and the operator + guide, never the token, webhook secret or model key. # Evidence * 2026-10-30: a direct `glm-5.3-flash` call through the handler returned `OK`, and `/review` on PR #28 posted a PR Reviewer Guide through the Gitea - comment API. The key is set only in the server-side `.env`. + comment API. The key is set only in `gitea/pr-agent.env`. # Not verified @@ -110,7 +113,7 @@ provider rejects the request before it reaches the model. * The first review fails, returns unstructured output, or misses the kind of finding the opencode prompt used to catch. -* A newer `gitea_app` image tag is worth taking; bump the tag and run - `docker compose up -d`. +* A newer `gitea_app` image tag is worth taking; bump the tag in the Gitea + compose file and run `docker compose up -d pr-agent` from that directory. * Review volume makes the container's memory limit tight, or Gitea adds a role that can comment without push access. diff --git a/OKF_Nuxt/index.md b/OKF_Nuxt/index.md index 1be511f..ca37f4e 100644 --- a/OKF_Nuxt/index.md +++ b/OKF_Nuxt/index.md @@ -11,6 +11,7 @@ config files — the configs say what, these documents say why. * [Open questions](open-questions.md) - What is still undecided for the Nuxt site. * [Backend endpoints](backend-endpoints.md) - The smallest API the frontend needs from the Go gateway: health, chapters, metrics, knockdown, events. * [Profile data](profile.md) - The LinkedIn export behind the terminal chapters, what is real vs mock, and how to refresh it. +* [PR-Agent operations](pr-agent.md) - The Gitea-side review service: configuration, commands, logs and model. * [Future updates](future-updates.md) - Pipeline improvement backlog with effort estimates, not yet decided. * [Update log](log.md) - History of changes to this bundle. @@ -19,7 +20,7 @@ config files — the configs say what, these documents say why. ## CI/CD and releases (2026-10-18) * [PR pipeline layering](decisions/pr-pipeline-layering.md) - Three layers: pre-commit for cheap deterministic checks, Gitea Actions for thorough ones, AI review for judgment. -* [PR-Agent for Gitea reviews](decisions/pr-agent.md) - A pinned webhook server on server0 replaces the per-PR opencode job; internal-only, scoped bot, OpenCode Go model. +* [PR-Agent for Gitea reviews](decisions/pr-agent.md) - A pinned review service inside the Gitea compose stack replaces the per-PR opencode job; internal-only, scoped bot, OpenCode Go model. * [AI review setup (opencode)](decisions/ai-review-setup.md) - Superseded 2026-10-30; kept for the env-only auth and verdict-gate reasoning. * [Vulnerability audit policy](decisions/vulnerability-audit-policy.md) - Blocking audit; reviewed ignore-list for unfixable advisories in pnpm-workspace.yaml. * [Release engineering](decisions/release-engineering.md) - release-please in manifest mode; conventional commits enforced at commit time. diff --git a/OKF_Nuxt/log.md b/OKF_Nuxt/log.md index 1662e6b..2fa9649 100644 --- a/OKF_Nuxt/log.md +++ b/OKF_Nuxt/log.md @@ -1,18 +1,24 @@ # Update Log +## 2026-10-30 (PR-Agent moved into the Gitea compose stack) + +* **Refactor**: the `pr-agent` service now lives in `/home/noel/self-hosted/gitea/docker-compose.yml` with `/home/noel/self-hosted/gitea/pr-agent.env`. The separate `/home/noel/self-hosted/pr-agent` stack and the unused `/opt` operator-access scripts were removed; the service is managed with the Gitea stack. +* **Docs**: the operator README moved to [PR-Agent operations](pr-agent.md). The decision, index and update log point at the new topology. +* **Evidence**: after the move, the container is healthy, a signed webhook from the Gitea container returns 200, and a direct `glm-5.3-flash` call returns `OK`. + ## 2026-10-30 (PR #28: lockfile and PR-Agent routing repaired) * **Fix**: `pnpm-lock.yaml` - merging `main` left the lockfile at `@nuxt/icon` 2.6.0 while `package.json` asked for 2.6.2, so `pnpm install --frozen-lockfile` aborted in CI. The lockfile now resolves 2.6.2. * **Fix**: `pnpm-workspace.yaml` - `seroval` 1.6.9 was the two moderate audit findings (GHSA-f86p-h4j2-7qgj, GHSA-9wx9-5pv9-3349). The patched 1.6.11 is forced through `overrides`; the blocking audit now reports only two low-severity advisories and passes the moderate gate. * **Fix**: PR-Agent model routing - OpenCode Go rejects requests without `x-opencode-session`; `LITELLM__EXTRA_HEADERS` now supplies it, and the fallback keeps the `openai/` prefix. Auto commands are `/describe` and `/review`; `/improve` is on demand. A dummy-key call reaches the provider's auth check instead of failing on the missing header. * **Evidence**: the key was wired into the live `.env`; a direct `glm-5.3-flash` call returned `OK`, and `/review` on PR #28 posted a PR Reviewer Guide (no findings). The failed-review comment was removed. -* **State**: the key is set only in the server-side `.env`; the first `/review` posted on PR #28 with no findings. +* **State**: the key is set only in `gitea/pr-agent.env`; the first `/review` posted on PR #28 with no findings. ## 2026-10-30 (PR-Agent replaces the opencode review job) * **Decision**: [PR-Agent for Gitea reviews](decisions/pr-agent.md) - a pinned `pragent/pr-agent:0.49.0-gitea_app` container on `server0` reviews PRs through the Gitea bot user `pr-agent`; the endpoint stays on the `gitea_gitea` Docker network. * **Update**: [pr-checker.yml](../.gitea/workflows/pr-checker.yml) - removed the `review` job, the opencode installer and the verdict-posting step. PR-Agent now runs `/describe` and `/review` on PR open/reopen and answers slash commands. -* **Creation**: `deploy/pr-agent/` - compose service, example environment and operator README. The real `.env` lives only at `/home/noel/self-hosted/pr-agent/.env` (mode 600) on `server0`. +* **Creation**: `deploy/pr-agent/` (later removed; the service now lives in the Gitea compose stack) - compose service, example environment and operator README. The real `.env` lived only at `/home/noel/self-hosted/pr-agent/.env` (mode 600) on `server0`. * **State**: the container is running and the webhook signature path is verified. Gitea gained `[webhook] ALLOWED_HOST_LIST = private:3000` (one restart, healthy) and the repository has a signed webhook. The OpenCode Go API key was still missing at commit time, so no model call or real review has run yet. ## 2026-10-27 (release-please still never tagged: the deleted head branch) diff --git a/OKF_Nuxt/pr-agent.md b/OKF_Nuxt/pr-agent.md new file mode 100644 index 0000000..c595747 --- /dev/null +++ b/OKF_Nuxt/pr-agent.md @@ -0,0 +1,123 @@ +--- +type: Reference +title: PR-Agent operations +description: The Gitea-side pull-request review service, its configuration in the Gitea compose stack, and the commands it answers. +tags: [pr-agent, gitea, operations, ci, ai] +status: draft +generated: { by: opencode-go/deepseek-v4.1-flash, at: 2026-10-30T20:40:00Z } +verified: { by: human:noel, at: not yet } +sources: + - id: gitea-compose + resource: /home/noel/self-hosted/gitea/docker-compose.yml + title: Gitea compose stack, pr-agent service + - id: install + resource: https://docs.pr-agent.ai/installation/gitea/ + title: PR-Agent Gitea installation + - id: gitea-egress + resource: https://docs.gitea.com/administration/config-cheat-sheet#webhook + title: Gitea webhook egress allowlist +--- + +# What runs + +PR-Agent is the `pr-agent` service inside the Gitea compose stack on +`server0`. It listens on the internal `gitea_gitea` network at +`http://pr-agent:3000`; no port is published. Gitea calls its signed +webhook at `/api/v1/gitea_webhooks`, and the bot user `pr-agent` posts the +results. + +| Piece | Value | +|---|---| +| Service | `pr-agent` in `/home/noel/self-hosted/gitea/docker-compose.yml` | +| Image | `pragent/pr-agent:0.49.0-gitea_app` | +| Config | `/home/noel/self-hosted/gitea/pr-agent.env` (mode 600) | +| Logs | `cd /home/noel/self-hosted/gitea && docker compose logs -f pr-agent` | +| Restart | `cd /home/noel/self-hosted/gitea && docker compose up -d pr-agent` | +| Upgrade | bump the image tag in the compose file, then restart the service | + +The service is managed with the same access as the rest of the Gitea +stack. The earlier plan for a separate `/opt/pr-agent` stack and a +restricted `agent` account was not applied; those scripts were removed when +the service moved into this stack. Hardening the Gitea stack's operator +access is a separate change. + +# Gitea side + +1. Bot user `pr-agent` is a collaborator with write permission on + `CV_Website/CV_Site_Nuxt`. Its personal access token is scoped to + `read:repository`, `write:issue` and `read:user`. +2. The repository webhook sends `push`, `issues`, `pull_request` and + `issue_comment` events, with JSON content type and the shared secret. +3. Gitea's `[webhook] ALLOWED_HOST_LIST` includes `private:3000`. Without + it, Gitea's default egress policy refuses deliveries to the Docker + network. + +# Commands + +| Trigger | What runs | +|---|---| +| PR opened or reopened | `/describe` and `/review` automatically | +| New push to an open PR | nothing; comment `/review` or `/review -i` | +| Comment `/review`, `/improve`, `/ask` | that command | + +`/review -i` reviews only the commits added since the previous review. +`/improve` stays on demand; adding it to the auto list would make a second +model call and a second comment on every PR. Draft PRs are not skipped. + +# Configuration + +`pr-agent.env` holds the deployment values. The repository never contains +the token, webhook secret, or API key: + +```ini +CONFIG__GIT_PROVIDER=gitea +GITEA__URL=http://gitea:3000 +GITEA__WEB_URL=https://git.noelsabia.dev +GITEA__PERSONAL_ACCESS_TOKEN=... +GITEA__WEBHOOK_SECRET=... +CONFIG__MODEL=openai/glm-5.3-flash +CONFIG__FALLBACK_MODELS=["openai/glm-5.3"] +CONFIG__CUSTOM_MODEL_MAX_TOKENS=128000 +OPENAI__API_BASE=https://opencode.ai/inference/go/openai/v1 +OPENAI__KEY=... +LITELLM__EXTRA_HEADERS={"x-opencode-session":"pr-agent"} +GITEA__PR_COMMANDS=["/describe","/review"] +``` + +OpenCode Go requires the `x-opencode-session` header. The fallback keeps +the `openai/` prefix; a bare `glm-5.3` is treated by LiteLLM as a +provider-less model. `CONFIG__CUSTOM_MODEL_MAX_TOKENS` supplies the context +limit; the effective review budget is capped by PR-Agent's default +`max_model_tokens` of 32000. + +The compose service: + +```yaml +pr-agent: + image: pragent/pr-agent:0.49.0-gitea_app + container_name: pr-agent + restart: unless-stopped + env_file: + - ./pr-agent.env + environment: + PORT: "3000" + GUNICORN_WORKERS: "2" + mem_limit: 1g + networks: + - gitea + healthcheck: + test: ["CMD", "python", "-c", "import socket; socket.create_connection(('127.0.0.1', 3000), 3).close()"] + interval: 30s + timeout: 5s + retries: 3 + start_period: 30s +``` + +# Checks + +A signed webhook from the Gitea container returns 200, and a direct +`glm-5.3-flash` call returns a completion. A `403` in the Gitea webhook +delivery log means the secret does not match or `ALLOWED_HOST_LIST` is +missing; a `401` from PR-Agent means the signature and secret disagree. +On a model failure, check `docker compose logs pr-agent` and confirm +`OPENAI__KEY` is set in `pr-agent.env`. diff --git a/deploy/pr-agent/.env.example b/deploy/pr-agent/.env.example deleted file mode 100644 index d956a54..0000000 --- a/deploy/pr-agent/.env.example +++ /dev/null @@ -1,32 +0,0 @@ -# Copy to .env on server0 and fill in; never commit .env. -# chmod 600 .env - -CONFIG__GIT_PROVIDER=gitea - -# The API is reached over the Docker network; links in comments use the -# public URL instead. -GITEA__URL=http://gitea:3000 -GITEA__WEB_URL=https://git.noelsabia.dev - -# Bot user pr-agent, scoped token (read:repository, write:issue, read:user). -# Not the admin account and not a workflow secret. -GITEA__PERSONAL_ACCESS_TOKEN= - -# Secret configured on the Gitea webhook. Required: the server rejects -# unsigned webhooks with HTTP 403. -GITEA__WEBHOOK_SECRET= - -# OpenCode Go exposes an OpenAI-compatible chat-completions endpoint, so -# PR-Agent reaches it through its openai provider with a custom base URL. -CONFIG__MODEL=openai/glm-5.3-flash -CONFIG__FALLBACK_MODELS=["openai/glm-5.3"] -CONFIG__CUSTOM_MODEL_MAX_TOKENS=128000 -OPENAI__API_BASE=https://opencode.ai/inference/go/openai/v1 -OPENAI__KEY= - -# OpenCode Go requires a session id header; a stable id is enough here. -LITELLM__EXTRA_HEADERS={"x-opencode-session":"pr-agent"} - -# Auto commands on PR open. /improve remains available as a comment command; -# leaving it in the auto list adds a second model call to every PR. -GITEA__PR_COMMANDS=["/describe","/review"] diff --git a/deploy/pr-agent/README.md b/deploy/pr-agent/README.md deleted file mode 100644 index 59ac864..0000000 --- a/deploy/pr-agent/README.md +++ /dev/null @@ -1,99 +0,0 @@ -# PR-Agent for Gitea - -PR-Agent runs as a webhook server next to Gitea on `server0`. Gitea sends -pull-request and comment events over the `gitea_gitea` Docker network; the -endpoint is not published to the internet. - -| Piece | Value | -|---|---| -| Image | `pragent/pr-agent:0.49.0-gitea_app` | -| Container | `pr-agent` | -| Webhook URL, from Gitea | `http://pr-agent:3000/api/v1/gitea_webhooks` | -| Config | `/opt/pr-agent/.env` (root, mode 600) | -| Logs | `ssh … agent@server0 logs` | -| Deploy / restart | `ssh … agent@server0 deploy` | -| Status | `ssh … agent@server0 status` | -| Upgrade | edit the root-owned compose file, then run `deploy` | - -The table describes the target state. The live stack is still at -`/home/noel/self-hosted/pr-agent` and is managed with `noel`'s SSH key until -`setup-agent-access.sh` has been run. - -## Gitea side - -1. The bot user `pr-agent` is a collaborator on `CV_Website/CV_Site_Nuxt` with - write permission. Its personal access token is scoped to - `read:repository`, `write:issue` and `read:user`. -2. The repository webhook sends `push`, `issues`, `pull_request` and - `issue_comment` events, with JSON content type and the shared secret. -3. Gitea's `[webhook] ALLOWED_HOST_LIST` includes `private:3000`. Without it, - Gitea's default egress policy refuses webhook deliveries to private - addresses, including the Docker network. - -## Operator access - -The agent does not log in as `noel`. A dedicated `agent` account has one -forced command and three actions: - -```sh -ssh -i ~/.ssh/pr_agent_control -o IdentitiesOnly=yes agent@91.99.207.62 status -ssh -i ~/.ssh/pr_agent_control -o IdentitiesOnly=yes agent@91.99.207.62 logs -ssh -i ~/.ssh/pr_agent_control -o IdentitiesOnly=yes agent@91.99.207.62 deploy -``` - -The SSH key is restricted with `restrict,command=…`; the account has no -Docker group, no general sudo, and no shell. Sudo permits only the three -root-owned helper scripts in `/usr/local/sbin`, and those helpers operate on -the fixed `/opt/pr-agent/docker-compose.yml`. The compose file, `.env` and -helpers are root-owned, so the agent cannot turn “restart” into a different -container or a host mount. - -`setup-agent-access.sh` creates the account and moves the stack to -`/opt/pr-agent`. `remove-noel-access.sh` then removes the inherited access -from `noel`: the `docker` and `sudo` groups, the keys in -`/home/noel/.ssh/authorized_keys`, and the old PR-Agent directory. Run both -on the server as root, and only run the second after the restricted command -works and you have another admin path. - -For git, use a repository-scoped deploy key instead of the personal Gitea -key: `~/.ssh/pr_agent_gitea.pub` is added as a write deploy key on -`CV_Website/CV_Site_Nuxt`. The old personal key must be removed from Gitea, -or it still grants every repository the user can see. - -## AI model - -The agent uses OpenCode Go's OpenAI-compatible endpoint: - -```text -model openai/glm-5.3-flash -fallback openai/glm-5.3 -api base https://opencode.ai/inference/go/openai/v1 -``` - -`CONFIG__CUSTOM_MODEL_MAX_TOKENS` tells PR-Agent the context limit, because -the model is not in its token table. The effective review budget is still -capped by PR-Agent's default `config.max_model_tokens` of 32000. - -OpenCode Go requires an `x-opencode-session` header; PR-Agent sends the -stable id `pr-agent` through `LITELLM__EXTRA_HEADERS`. - -The API key lives only in the server's `.env`, never in the repo. Set -`OPENAI__KEY` in the live `/home/noel/self-hosted/pr-agent/.env` until the -`/opt` migration has run; afterwards use `/opt/pr-agent/.env` and the deploy -helper. - -## First check - -Open a pull request in `CV_Website/CV_Site_Nuxt`. The server runs `/describe` -and `/review` on open/reopen; comment commands such as `/review`, `/improve` -and `/ask` are handled from the PR conversation. `/improve` is deliberately -on demand: adding it to the auto list would make a second model call and a -second comment for every PR. If nothing appears: - -```sh -ssh -i ~/.ssh/pr_agent_control -o IdentitiesOnly=yes agent@91.99.207.62 logs -``` - -A `403` in the Gitea webhook delivery log means the secret does not match or -`ALLOWED_HOST_LIST` is still missing; a `401` from PR-Agent means the -signature header and secret disagree. diff --git a/deploy/pr-agent/docker-compose.yml b/deploy/pr-agent/docker-compose.yml deleted file mode 100644 index 8142bce..0000000 --- a/deploy/pr-agent/docker-compose.yml +++ /dev/null @@ -1,38 +0,0 @@ -# PR-Agent webhook server for the self-hosted Gitea instance. -# -# Runs on the existing gitea_gitea network and publishes no ports. Gitea -# reaches it as http://pr-agent:3000/api/v1/gitea_webhooks, so the webhook -# endpoint is never internet-facing. Gitea still publishes comment links with -# its own ROOT_URL (https://git.noelsabia.dev). -# -# Deployed by hand on server0 from /home/noel/self-hosted/pr-agent; see the -# README next to this file. - -services: - pr-agent: - image: pragent/pr-agent:0.49.0-gitea_app - container_name: pr-agent - restart: unless-stopped - env_file: - - .env - environment: - PORT: "3000" - # Importing the app costs roughly 250 MB. Two workers leave headroom on - # the 3.8 GB host that also runs Gitea, its runner and a web app. - GUNICORN_WORKERS: "2" - mem_limit: 1g - networks: - - gitea - healthcheck: - # The server has no HTTP health route; an open TCP socket is enough to - # distinguish a running gunicorn master from a crashed container. - test: ["CMD", "python", "-c", "import socket; socket.create_connection(('127.0.0.1', 3000), 3).close()"] - interval: 30s - timeout: 5s - retries: 3 - start_period: 30s - -networks: - gitea: - external: true - name: gitea_gitea diff --git a/deploy/pr-agent/remove-noel-access.sh b/deploy/pr-agent/remove-noel-access.sh deleted file mode 100755 index 2036290..0000000 --- a/deploy/pr-agent/remove-noel-access.sh +++ /dev/null @@ -1,56 +0,0 @@ -#!/usr/bin/env bash -# Final step: remove the agent's inherited noel access. -# -# Run on server0 only after the agent command works: -# ssh -i ~/.ssh/pr_agent_control -o IdentitiesOnly=yes agent@91.99.207.62 status -# -# This removes noel from docker and sudo, clears noel's authorized_keys, -# and deletes the old PR-Agent directory that held the secrets. Make sure -# you have another admin path (provider console or a new key) first. - -set -euo pipefail - -if [ "$(id -u)" -ne 0 ]; then - echo "run as root" >&2 - exit 1 -fi - -cat <<'EOF' -This will: - - remove noel from the docker and sudo groups - - clear every key in /home/noel/.ssh/authorized_keys - - delete /home/noel/self-hosted/pr-agent (the /opt copy remains) -Existing noel SSH sessions keep their old groups until they log out. -Make sure you have another admin path before continuing. -EOF -read -r -p "Type REMOVE to continue: " answer -[ "$answer" = "REMOVE" ] || { echo "aborted"; exit 1; } - -if id -nG noel | tr ' ' '\n' | grep -qx docker; then - gpasswd -d noel docker -fi -if id -nG noel | tr ' ' '\n' | grep -qx sudo; then - deluser noel sudo -fi - -if [ -f /home/noel/.ssh/authorized_keys ]; then - cp -a /home/noel/.ssh/authorized_keys \ - "/root/noel-authorized_keys.$(date +%Y%m%d-%H%M%S).bak" - : > /home/noel/.ssh/authorized_keys - chown noel:noel /home/noel/.ssh/authorized_keys - chmod 600 /home/noel/.ssh/authorized_keys -fi - -rm -rf /home/noel/self-hosted/pr-agent - -cat <<'EOF' - -Done. Test the restricted path again: - - ssh -i ~/.ssh/pr_agent_control -o IdentitiesOnly=yes agent@91.99.207.62 status - -Still to do outside this script: - - remove the old personal SSH key from Gitea (Settings > SSH / GPG Keys) - - add ~/.ssh/pr_agent_gitea.pub as a write deploy key on CV_Site_Nuxt - - put the OpenCode Go key in /opt/pr-agent/.env and run the deploy helper -EOF diff --git a/deploy/pr-agent/setup-agent-access.sh b/deploy/pr-agent/setup-agent-access.sh deleted file mode 100755 index 70acebf..0000000 --- a/deploy/pr-agent/setup-agent-access.sh +++ /dev/null @@ -1,135 +0,0 @@ -#!/usr/bin/env bash -# One-time root setup for the least-privilege PR-Agent operator account. -# -# Run on server0: -# sudo bash /home/noel/agent-access-setup.sh -# -# This creates the agent user and moves the PR-Agent stack to /opt/pr-agent. -# It does NOT remove noel's current docker/sudo access. Verify the agent -# command printed at the end first, then run remove-noel-access.sh. - -set -euo pipefail - -if [ "$(id -u)" -ne 0 ]; then - echo "run as root" >&2 - exit 1 -fi - -AGENT_USER=agent -AGENT_HOME=/home/$AGENT_USER -PR_AGENT_DIR=/opt/pr-agent -SRC_DIR=/home/noel/self-hosted/pr-agent -PUBKEY_FILE=/home/noel/.ssh/pr_agent_control.pub -DOCKER=/usr/bin/docker - -for f in "$SRC_DIR/docker-compose.yml" "$SRC_DIR/README.md" "$SRC_DIR/.env" "$PUBKEY_FILE"; do - [ -f "$f" ] || { echo "missing $f" >&2; exit 1; } -done -case "$(cat "$PUBKEY_FILE")" in - ssh-*|ecdsa-*|sk-ssh-*) ;; - *) echo "$PUBKEY_FILE does not look like an SSH public key" >&2; exit 1 ;; -esac -grep -q '^Include /etc/ssh/sshd_config.d/\*.conf' /etc/ssh/sshd_config \ - || { echo "sshd does not include sshd_config.d" >&2; exit 1; } - -if ! id "$AGENT_USER" >/dev/null 2>&1; then - useradd --create-home --shell /bin/bash "$AGENT_USER" -fi -passwd -l "$AGENT_USER" >/dev/null 2>&1 || true -chmod 700 "$AGENT_HOME" -install -d -m 700 -o "$AGENT_USER" -g "$AGENT_USER" "$AGENT_HOME/.ssh" - -# The stack must not be writable by the agent: a changed compose file would -# turn "restart the service" into arbitrary root containers. -install -d -m 755 -o root -g root "$PR_AGENT_DIR" -if [ ! -f "$PR_AGENT_DIR/docker-compose.yml" ]; then - install -m 644 -o root -g root "$SRC_DIR/docker-compose.yml" "$PR_AGENT_DIR/docker-compose.yml" -fi -install -m 644 -o root -g root "$SRC_DIR/README.md" "$PR_AGENT_DIR/README.md" -if [ ! -f "$PR_AGENT_DIR/.env" ]; then - install -m 600 -o root -g root "$SRC_DIR/.env" "$PR_AGENT_DIR/.env" -fi -if ! grep -q '^name:' "$PR_AGENT_DIR/docker-compose.yml"; then - sed -i '1i name: pr-agent' "$PR_AGENT_DIR/docker-compose.yml" -fi - -cat > /usr/local/sbin/pr-agent-deploy < /usr/local/sbin/pr-agent-logs < /usr/local/sbin/pr-agent-status < /usr/local/sbin/pr-agent-control <<'EOF' -#!/bin/sh -set -eu -case "${SSH_ORIGINAL_COMMAND:-}" in - deploy) exec sudo -n /usr/local/sbin/pr-agent-deploy ;; - logs) exec sudo -n /usr/local/sbin/pr-agent-logs ;; - status) exec sudo -n /usr/local/sbin/pr-agent-status ;; - *) echo "allowed: deploy, logs, status" >&2; exit 1 ;; -esac -EOF - -chown root:root /usr/local/sbin/pr-agent-deploy /usr/local/sbin/pr-agent-logs \ - /usr/local/sbin/pr-agent-status /usr/local/sbin/pr-agent-control -chmod 755 /usr/local/sbin/pr-agent-deploy /usr/local/sbin/pr-agent-logs \ - /usr/local/sbin/pr-agent-status /usr/local/sbin/pr-agent-control - -cat > /etc/sudoers.d/pr-agent-control <<'EOF' -agent ALL=(root) NOPASSWD: /usr/local/sbin/pr-agent-deploy, /usr/local/sbin/pr-agent-logs, /usr/local/sbin/pr-agent-status -EOF -chmod 440 /etc/sudoers.d/pr-agent-control -visudo -cf /etc/sudoers.d/pr-agent-control >/dev/null - -PUB=$(cat "$PUBKEY_FILE") -printf 'restrict,command="/usr/local/sbin/pr-agent-control" %s\n' "$PUB" \ - > "$AGENT_HOME/.ssh/authorized_keys" -chown "$AGENT_USER:$AGENT_USER" "$AGENT_HOME/.ssh/authorized_keys" -chmod 600 "$AGENT_HOME/.ssh/authorized_keys" - -cat > /etc/ssh/sshd_config.d/60-pr-agent-agent.conf <<'EOF' -Match User agent - ForceCommand /usr/local/sbin/pr-agent-control - PermitTTY no - AllowTcpForwarding no - X11Forwarding no - PermitTunnel no - AllowAgentForwarding no -EOF -chmod 644 /etc/ssh/sshd_config.d/60-pr-agent-agent.conf -if ! sshd -t; then - rm -f /etc/ssh/sshd_config.d/60-pr-agent-agent.conf - echo "sshd config test failed; removed the new file" >&2 - exit 1 -fi -systemctl reload ssh - -cd "$PR_AGENT_DIR" -"$DOCKER" compose pull -"$DOCKER" compose up -d -sleep 5 -"$DOCKER" compose ps - -cat <<'EOF' - -Agent access is ready. Test from the laptop: - - ssh -i ~/.ssh/pr_agent_control -o IdentitiesOnly=yes agent@91.99.207.62 status - -Old access is still in place. Only after that command works, run: - - sudo bash /home/noel/agent-access-remove.sh -EOF From 06508be0e041c1dc60e85ee9b2077247d116c337 Mon Sep 17 00:00:00 2001 From: Noel Date: Sat, 31 Oct 2026 04:02:25 +0000 Subject: [PATCH 9/9] chore(deps): update dependency @iconify-json/material-symbols to v1.2.97 --- pnpm-lock.yaml | 24 +++++++++++------------- 1 file changed, 11 insertions(+), 13 deletions(-) diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml index fd3d6ee..08eb816 100644 --- a/pnpm-lock.yaml +++ b/pnpm-lock.yaml @@ -14,13 +14,13 @@ importers: dependencies: '@iconify-json/material-symbols': specifier: ^1.2.95 - version: 1.2.95 + version: 1.2.97 '@nuxt/icon': specifier: 2.6.2 version: 2.6.2(@nuxt/schema@4.6.2)(confbox@0.3.1)(dotenv@17.4.2)(giget@3.3.1)(jiti@2.7.0)(magic-string@1.4.3)(oxc-parser@0.153.0)(rolldown@1.2.14)(unplugin@3.4.0(esbuild@0.28.2)(rolldown@1.2.14)(rollup@4.64.8)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1)))(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))(vue@3.5.44(typescript@5.9.3)) '@nuxtjs/i18n': specifier: 10.6.0 - version: 10.6.0(@nuxt/schema@4.6.2)(@vue/compiler-dom@3.5.44)(db0@0.3.4)(dotenv@17.4.2)(esbuild@0.28.2)(giget@3.3.1)(ioredis@5.11.1(supports-color@10.2.2))(jiti@2.7.0)(rolldown@1.2.14)(rollup@4.64.8)(supports-color@10.2.2)(typescript@5.9.3)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))(vue@3.5.44(typescript@5.9.3)) + version: 10.6.0(@nuxt/schema@4.6.2)(db0@0.3.4)(dotenv@17.4.2)(esbuild@0.28.2)(giget@3.3.1)(ioredis@5.11.1(supports-color@10.2.2))(jiti@2.7.0)(rolldown@1.2.14)(rollup@4.64.8)(supports-color@10.2.2)(typescript@5.9.3)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))(vue@3.5.44(typescript@5.9.3)) '@nuxtjs/seo': specifier: 6.0.1 version: 6.0.1(b12aa32157ad38cf444edd41e3e089a9) @@ -677,8 +677,8 @@ packages: resolution: {integrity: sha512-bV0Tgo9K4hfPCek+aMAn81RppFKv2ySDQeMoSZuvTASywNTnVJCArCZE2FWqpvIatKu7VMRLWlR1EazvVhDyhQ==} engines: {node: '>=18.18'} - '@iconify-json/material-symbols@1.2.95': - resolution: {integrity: sha512-n34GNbwe8We3LPXK2N8JuQewEQkITJiRsmX/0UYJsOyKzviVl22mNfLUiGGtXLKDPqxZa17q1Hg57zdA3BYa0w==} + '@iconify-json/material-symbols@1.2.97': + resolution: {integrity: sha512-MbE4QHrH4Z4eoerBFrzFSPqHw2NwVGwwOwGZdJym5l5N5loqEUThimlQpK9VJA6mvgWvj5jl43b8bZnqzOxNRQ==} '@iconify/collections@1.0.758': resolution: {integrity: sha512-i6z8ImaR9gH/Kj51H81JmGaX1K5OF+SuNZB4DxJwgdweZUBguMaL62EDFqIwF1V8xKfGrOJRB/tx4csYXaNl0w==} @@ -6103,7 +6103,7 @@ snapshots: '@humanwhocodes/retry@0.4.3': {} - '@iconify-json/material-symbols@1.2.95': + '@iconify-json/material-symbols@1.2.97': dependencies: '@iconify/types': 2.0.0 @@ -6164,11 +6164,11 @@ snapshots: '@intlify/shared@11.4.16': {} - '@intlify/unplugin-vue-i18n@11.2.7(@vue/compiler-dom@3.5.44)(rollup@4.64.8)(supports-color@10.2.2)(typescript@5.9.3)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))(vue-i18n@11.4.16(vue@3.5.44(typescript@5.9.3)))(vue@3.5.44(typescript@5.9.3))': + '@intlify/unplugin-vue-i18n@11.2.7(rollup@4.64.8)(supports-color@10.2.2)(typescript@5.9.3)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))(vue-i18n@11.4.16(vue@3.5.44(typescript@5.9.3)))(vue@3.5.44(typescript@5.9.3))': dependencies: '@intlify/bundle-utils': 11.2.7(vue-i18n@11.4.16(vue@3.5.44(typescript@5.9.3))) '@intlify/shared': 11.4.16 - '@intlify/vue-i18n-extensions': 8.0.0(@intlify/shared@11.4.16)(@vue/compiler-dom@3.5.44)(vue-i18n@11.4.16(vue@3.5.44(typescript@5.9.3)))(vue@3.5.44(typescript@5.9.3)) + '@intlify/vue-i18n-extensions': 8.0.0(@intlify/shared@11.4.16)(vue-i18n@11.4.16(vue@3.5.44(typescript@5.9.3)))(vue@3.5.44(typescript@5.9.3)) '@rollup/pluginutils': 5.4.0(rollup@4.64.8) '@typescript-eslint/scope-manager': 8.71.2 '@typescript-eslint/typescript-estree': 8.71.2(supports-color@10.2.2)(typescript@5.9.3) @@ -6182,7 +6182,6 @@ snapshots: vite: 8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1) vue-i18n: 11.4.16(vue@3.5.44(typescript@5.9.3)) transitivePeerDependencies: - - '@vue/compiler-dom' - rollup - supports-color - typescript @@ -6191,12 +6190,12 @@ snapshots: '@intlify/utils@0.14.1': {} - '@intlify/vue-i18n-extensions@8.0.0(@intlify/shared@11.4.16)(@vue/compiler-dom@3.5.44)(vue-i18n@11.4.16(vue@3.5.44(typescript@5.9.3)))(vue@3.5.44(typescript@5.9.3))': + '@intlify/vue-i18n-extensions@8.0.0(@intlify/shared@11.4.16)(vue-i18n@11.4.16(vue@3.5.44(typescript@5.9.3)))(vue@3.5.44(typescript@5.9.3))': dependencies: '@babel/parser': 7.29.9 + '@vue/compiler-dom': 3.5.44 optionalDependencies: '@intlify/shared': 11.4.16 - '@vue/compiler-dom': 3.5.44 vue: 3.5.44(typescript@5.9.3) vue-i18n: 11.4.16(vue@3.5.44(typescript@5.9.3)) @@ -6963,13 +6962,13 @@ snapshots: - rolldown - unplugin - '@nuxtjs/i18n@10.6.0(@nuxt/schema@4.6.2)(@vue/compiler-dom@3.5.44)(db0@0.3.4)(dotenv@17.4.2)(esbuild@0.28.2)(giget@3.3.1)(ioredis@5.11.1(supports-color@10.2.2))(jiti@2.7.0)(rolldown@1.2.14)(rollup@4.64.8)(supports-color@10.2.2)(typescript@5.9.3)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))(vue@3.5.44(typescript@5.9.3))': + '@nuxtjs/i18n@10.6.0(@nuxt/schema@4.6.2)(db0@0.3.4)(dotenv@17.4.2)(esbuild@0.28.2)(giget@3.3.1)(ioredis@5.11.1(supports-color@10.2.2))(jiti@2.7.0)(rolldown@1.2.14)(rollup@4.64.8)(supports-color@10.2.2)(typescript@5.9.3)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))(vue@3.5.44(typescript@5.9.3))': dependencies: '@intlify/core': 11.4.16 '@intlify/h3': 0.7.4 '@intlify/message-compiler': 11.4.16 '@intlify/shared': 11.4.16 - '@intlify/unplugin-vue-i18n': 11.2.7(@vue/compiler-dom@3.5.44)(rollup@4.64.8)(supports-color@10.2.2)(typescript@5.9.3)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))(vue-i18n@11.4.16(vue@3.5.44(typescript@5.9.3)))(vue@3.5.44(typescript@5.9.3)) + '@intlify/unplugin-vue-i18n': 11.2.7(rollup@4.64.8)(supports-color@10.2.2)(typescript@5.9.3)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))(vue-i18n@11.4.16(vue@3.5.44(typescript@5.9.3)))(vue@3.5.44(typescript@5.9.3)) '@intlify/utils': 0.14.1 '@miyaneee/rollup-plugin-json5': 1.2.0(rollup@4.64.8) '@nuxt/kit': 4.6.2(@nuxt/schema@4.6.2)(confbox@0.2.4)(dotenv@17.4.2)(giget@3.3.1)(jiti@2.7.0)(magic-string@0.30.21)(mlly@1.8.2)(oxc-parser@0.141.0)(rolldown@1.2.14)(unplugin@3.4.0(esbuild@0.28.2)(rolldown@1.2.14)(rollup@4.64.8)(vite@8.3.4(esbuild@0.28.2)(jiti@2.7.0)(terser@5.51.2)(yaml@2.9.1))) @@ -7014,7 +7013,6 @@ snapshots: - '@vercel/blob' - '@vercel/functions' - '@vercel/kv' - - '@vue/compiler-dom' - aws4fetch - bun-types-no-globals - db0