Prepares phase 4 (Wiki PR: POST /api/v1/facts). The service's note store used the Python service's read-only token; deposited facts are created as raw/<date>-<slug>.md through the Gitea contents API and need write. New claude-bot token wiki-service-write-2026-09-24 (write:repository) stored in OpenBao apps/ai/wiki-service, field gitea_token; the wiki-gitea ExternalSecret maps it. Commits by the service show as Claude Bot; captured_by in the frontmatter names the API key that deposited the fact.
Prepares phase 4 (Wiki PR: `POST /api/v1/facts`). The service's note store used the Python service's read-only token; deposited facts are created as `raw/<date>-<slug>.md` through the Gitea contents API and need write. New claude-bot token `wiki-service-write-2026-09-24` (`write:repository`) stored in OpenBao `apps/ai/wiki-service`, field `gitea_token`; the `wiki-gitea` ExternalSecret maps it. Commits by the service show as Claude Bot; `captured_by` in the frontmatter names the API key that deposited the fact.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
🤖Automated review — model CLI default (complexity: complex), commit 64fdb568b4a51f45e2378b1aff4579c5094d8586.
Advisory review by the review-bot pipeline. It never approves; a human merges. Push new commits to get a fresh review.
Summary
Repoints the wiki-gitea ExternalSecret's Wiki__NoteStore__Gitea__Token field from OpenBao apps/ai/wiki-index to apps/ai/wiki-service (a new write:repository claude-bot token), so the wiki service can create raw/<date>-<slug>.md fact files via the Gitea contents API. This is a minimal, well-scoped one-line functional change plus an updated comment; the webhook secret's remoteRef (still apps/ai/wiki-index) is correctly left untouched. No blocking issues found.
🟡 Suggestions
kubernetes/apps/wiki/externalsecrets.yaml:20 — this change is only correct if the OpenBao secret apps/ai/wiki-service with field gitea_token already exists (per the PR body, it's the new token wiki-service-write-2026-09-24). That's outside this repo's diff and can't be verified from the checkout; worth confirming the OpenBao entry is in place before/at merge so external-secrets doesn't fail to sync and break the existing (read-only) token in the live wiki-gitea Secret.
Since the token scope is widening from read-only to write:repository, it may be worth a brief note (here or in the linked proposal) on what happens if fact deposits ever hit an unintended repo/path — i.e., confirming the token is scoped to only the notes repo, not a broader org-wide grant. Not blocking since token scoping is managed in Gitea/OpenBao, not in this file.
Tests
No tests apply — this is a one-field ExternalSecret change with no accompanying application code in the diff. Consistent with how the surrounding file's other ExternalSecret entries are handled (untested YAML).
Recommendation
Looks reasonable — no blocking issues; comments above are optional.
🤖 **Automated review** — model `CLI default` (complexity: complex), commit `64fdb568b4a51f45e2378b1aff4579c5094d8586`.
> Advisory review by the `review-bot` pipeline. It never approves; a human merges. Push new commits to get a fresh review.
---
## Summary
Repoints the `wiki-gitea` ExternalSecret's `Wiki__NoteStore__Gitea__Token` field from OpenBao `apps/ai/wiki-index` to `apps/ai/wiki-service` (a new `write:repository` claude-bot token), so the wiki service can create `raw/<date>-<slug>.md` fact files via the Gitea contents API. This is a minimal, well-scoped one-line functional change plus an updated comment; the webhook secret's `remoteRef` (still `apps/ai/wiki-index`) is correctly left untouched. No blocking issues found.
## 🟡 Suggestions
- `kubernetes/apps/wiki/externalsecrets.yaml:20` — this change is only correct if the OpenBao secret `apps/ai/wiki-service` with field `gitea_token` already exists (per the PR body, it's the new token `wiki-service-write-2026-09-24`). That's outside this repo's diff and can't be verified from the checkout; worth confirming the OpenBao entry is in place before/at merge so `external-secrets` doesn't fail to sync and break the existing (read-only) token in the live `wiki-gitea` Secret.
- Since the token scope is widening from read-only to `write:repository`, it may be worth a brief note (here or in the linked proposal) on what happens if fact deposits ever hit an unintended repo/path — i.e., confirming the token is scoped to only the notes repo, not a broader org-wide grant. Not blocking since token scoping is managed in Gitea/OpenBao, not in this file.
## Tests
No tests apply — this is a one-field ExternalSecret change with no accompanying application code in the diff. Consistent with how the surrounding file's other `ExternalSecret` entries are handled (untested YAML).
## Recommendation
Looks reasonable — no blocking issues; comments above are optional.
<!-- pr-review:sha=64fdb568b4a51f45e2378b1aff4579c5094d8586 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Prepares phase 4 (Wiki PR:
POST /api/v1/facts). The service's note store used the Python service's read-only token; deposited facts are created asraw/<date>-<slug>.mdthrough the Gitea contents API and need write. New claude-bot tokenwiki-service-write-2026-09-24(write:repository) stored in OpenBaoapps/ai/wiki-service, fieldgitea_token; thewiki-giteaExternalSecret maps it. Commits by the service show as Claude Bot;captured_byin the frontmatter names the API key that deposited the fact.🤖 Generated with Claude Code
🤖 Automated review — model
CLI default(complexity: complex), commit64fdb568b4a51f45e2378b1aff4579c5094d8586.Summary
Repoints the
wiki-giteaExternalSecret'sWiki__NoteStore__Gitea__Tokenfield from OpenBaoapps/ai/wiki-indextoapps/ai/wiki-service(a newwrite:repositoryclaude-bot token), so the wiki service can createraw/<date>-<slug>.mdfact files via the Gitea contents API. This is a minimal, well-scoped one-line functional change plus an updated comment; the webhook secret'sremoteRef(stillapps/ai/wiki-index) is correctly left untouched. No blocking issues found.🟡 Suggestions
kubernetes/apps/wiki/externalsecrets.yaml:20— this change is only correct if the OpenBao secretapps/ai/wiki-servicewith fieldgitea_tokenalready exists (per the PR body, it's the new tokenwiki-service-write-2026-09-24). That's outside this repo's diff and can't be verified from the checkout; worth confirming the OpenBao entry is in place before/at merge soexternal-secretsdoesn't fail to sync and break the existing (read-only) token in the livewiki-giteaSecret.write:repository, it may be worth a brief note (here or in the linked proposal) on what happens if fact deposits ever hit an unintended repo/path — i.e., confirming the token is scoped to only the notes repo, not a broader org-wide grant. Not blocking since token scoping is managed in Gitea/OpenBao, not in this file.Tests
No tests apply — this is a one-field ExternalSecret change with no accompanying application code in the diff. Consistent with how the surrounding file's other
ExternalSecretentries are handled (untested YAML).Recommendation
Looks reasonable — no blocking issues; comments above are optional.