The .NET wiki service now covers everything the Python wiki-index did, verified: same recall on the 40-query labelled set (hit rate 0.85/0.875 at 5/10 through wiki-index.renner.uno), the notes webhook (hook 17) syncs it, and bin/wiki_ask.py/wiki_rank.py on the workstation and in CI use it (wiki_ask.py now calls POST /api/v1/ask, local fallback kept).
Removed: kubernetes/apps/wiki-index, its Flux Kustomization, ci/images/wiki-index and the build-wiki-index step, its CNP in ai-ns.yaml, the ai/wiki-index entry in openbao-ns.yaml, the Gitea egress entry, the OpenBao policy file. Flux prunes the Deployment, PVC, Service, ServiceAccount, Middleware and ExternalSecret with the Kustomization. The OpenBao keys apps/ai/wiki-index and apps/ai/wiki-index-basic-auth stay: the wiki service's ExternalSecrets read them.
After merge, done live: delete auth/kubernetes/role/wiki-index and policy wiki-index in OpenBao, delete Gitea webhook 9 on k.renner/notes.
The .NET wiki service now covers everything the Python `wiki-index` did, verified: same recall on the 40-query labelled set (hit rate 0.85/0.875 at 5/10 through `wiki-index.renner.uno`), the notes webhook (hook 17) syncs it, and `bin/wiki_ask.py`/`wiki_rank.py` on the workstation and in CI use it (`wiki_ask.py` now calls `POST /api/v1/ask`, local fallback kept).
Removed: `kubernetes/apps/wiki-index`, its Flux Kustomization, `ci/images/wiki-index` and the `build-wiki-index` step, its CNP in `ai-ns.yaml`, the `ai/wiki-index` entry in `openbao-ns.yaml`, the Gitea egress entry, the OpenBao policy file. Flux prunes the Deployment, PVC, Service, ServiceAccount, Middleware and ExternalSecret with the Kustomization. The OpenBao keys `apps/ai/wiki-index` and `apps/ai/wiki-index-basic-auth` stay: the wiki service's ExternalSecrets read them.
After merge, done live: delete `auth/kubernetes/role/wiki-index` and policy `wiki-index` in OpenBao, delete Gitea webhook 9 on k.renner/notes.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The .NET wiki service has parity (same recall on the labelled set), serves
wiki-index.renner.uno and the notes webhook, and the workstation scripts
use it. Removes the app, its Flux Kustomization, image source and build
step, its CNP entries and the OpenBao policy file. The OpenBao role and
the old Gitea webhook are removed live after the merge.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
🤖Automated review — model CLI default (complexity: complex), commit 419cbed395a438367b68ba4b2c345e70c7e042d5.
Advisory review by the review-bot pipeline. It never approves; a human merges. Push new commits to get a fresh review.
Summary
Pure deletion PR that retires the Python wiki-index service now that the .NET wiki service covers /rank//ask. It removes the CI image build step, the Kubernetes Deployment/Ingress/Kustomization/Flux Kustomization, the two CiliumNetworkPolicy grants (ai-ns egress-to-openbao, openbao-ns ingress-from-wiki-index), the Gitea webhook egress entry, and the OpenBao policy file, while correctly leaving the OpenBao secret data and the wiki-index.renner.uno hostname (now routed to the wiki Service per kubernetes/apps/wiki/ingress.yaml) in place. I traced every deleted resource and found no dangling references left behind, and the edited network-policy YAML files still end cleanly (no orphaned document separators). No blocking issues.
🟡 Suggestions
kubernetes/PROPOSAL-wiki-web-api.md's "Where we are" section (top of file) still describes wiki-index (Python) as the live sync/rank service. The doc's own migration plan (step 3, near the bottom) explicitly anticipates this retirement ("Then the Python service is retired and the wiki-index hostname points at the new one"), so this isn't a surprise, but the "Where we are" summary is now stale and could mislead a future reader who only skims the top.
ci/agents/wiki-maintenance/settings.json:3 — the comment says "...and the wiki-index client credential..." referring to the WIKI_INDEX_BASIC_AUTH secret used for ~/.config/wiki-index/basic-auth. That's just a local config-path name (harmless, still accurate to the file path), but worth a pass if you're otherwise renaming things — it now authenticates to the .NET wiki service, not the retired Python one.
Tests
No tests added or removed beyond the deletion of ci/images/wiki-index/test_wiki_index.py, which is correct since the module it tested is gone. Nothing else in this diff needs test coverage — it's all deletions of build/deploy config.
Recommendation
Looks reasonable — no blocking issues; comments above are optional.
🤖 **Automated review** — model `CLI default` (complexity: complex), commit `419cbed395a438367b68ba4b2c345e70c7e042d5`.
> Advisory review by the `review-bot` pipeline. It never approves; a human merges. Push new commits to get a fresh review.
---
## Summary
Pure deletion PR that retires the Python `wiki-index` service now that the .NET wiki service covers `/rank`/`/ask`. It removes the CI image build step, the Kubernetes Deployment/Ingress/Kustomization/Flux Kustomization, the two CiliumNetworkPolicy grants (ai-ns egress-to-openbao, openbao-ns ingress-from-wiki-index), the Gitea webhook egress entry, and the OpenBao policy file, while correctly leaving the OpenBao secret data and the `wiki-index.renner.uno` hostname (now routed to the `wiki` Service per `kubernetes/apps/wiki/ingress.yaml`) in place. I traced every deleted resource and found no dangling references left behind, and the edited network-policy YAML files still end cleanly (no orphaned document separators). No blocking issues.
## 🟡 Suggestions
- `kubernetes/PROPOSAL-wiki-web-api.md`'s "Where we are" section (top of file) still describes `wiki-index` (Python) as the live sync/rank service. The doc's own migration plan (step 3, near the bottom) explicitly anticipates this retirement ("Then the Python service is retired and the `wiki-index` hostname points at the new one"), so this isn't a surprise, but the "Where we are" summary is now stale and could mislead a future reader who only skims the top.
- `ci/agents/wiki-maintenance/settings.json:3` — the comment says "...and the wiki-index client credential..." referring to the `WIKI_INDEX_BASIC_AUTH` secret used for `~/.config/wiki-index/basic-auth`. That's just a local config-path name (harmless, still accurate to the file path), but worth a pass if you're otherwise renaming things — it now authenticates to the .NET wiki service, not the retired Python one.
## Tests
No tests added or removed beyond the deletion of `ci/images/wiki-index/test_wiki_index.py`, which is correct since the module it tested is gone. Nothing else in this diff needs test coverage — it's all deletions of build/deploy config.
## Recommendation
Looks reasonable — no blocking issues; comments above are optional.
<!-- pr-review:sha=419cbed395a438367b68ba4b2c345e70c7e042d5 -->
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.
The .NET wiki service now covers everything the Python
wiki-indexdid, verified: same recall on the 40-query labelled set (hit rate 0.85/0.875 at 5/10 throughwiki-index.renner.uno), the notes webhook (hook 17) syncs it, andbin/wiki_ask.py/wiki_rank.pyon the workstation and in CI use it (wiki_ask.pynow callsPOST /api/v1/ask, local fallback kept).Removed:
kubernetes/apps/wiki-index, its Flux Kustomization,ci/images/wiki-indexand thebuild-wiki-indexstep, its CNP inai-ns.yaml, theai/wiki-indexentry inopenbao-ns.yaml, the Gitea egress entry, the OpenBao policy file. Flux prunes the Deployment, PVC, Service, ServiceAccount, Middleware and ExternalSecret with the Kustomization. The OpenBao keysapps/ai/wiki-indexandapps/ai/wiki-index-basic-authstay: the wiki service's ExternalSecrets read them.After merge, done live: delete
auth/kubernetes/role/wiki-indexand policywiki-indexin OpenBao, delete Gitea webhook 9 on k.renner/notes.🤖 Generated with Claude Code
🤖 Automated review — model
CLI default(complexity: complex), commit419cbed395a438367b68ba4b2c345e70c7e042d5.Summary
Pure deletion PR that retires the Python
wiki-indexservice now that the .NET wiki service covers/rank//ask. It removes the CI image build step, the Kubernetes Deployment/Ingress/Kustomization/Flux Kustomization, the two CiliumNetworkPolicy grants (ai-ns egress-to-openbao, openbao-ns ingress-from-wiki-index), the Gitea webhook egress entry, and the OpenBao policy file, while correctly leaving the OpenBao secret data and thewiki-index.renner.unohostname (now routed to thewikiService perkubernetes/apps/wiki/ingress.yaml) in place. I traced every deleted resource and found no dangling references left behind, and the edited network-policy YAML files still end cleanly (no orphaned document separators). No blocking issues.🟡 Suggestions
kubernetes/PROPOSAL-wiki-web-api.md's "Where we are" section (top of file) still describeswiki-index(Python) as the live sync/rank service. The doc's own migration plan (step 3, near the bottom) explicitly anticipates this retirement ("Then the Python service is retired and thewiki-indexhostname points at the new one"), so this isn't a surprise, but the "Where we are" summary is now stale and could mislead a future reader who only skims the top.ci/agents/wiki-maintenance/settings.json:3— the comment says "...and the wiki-index client credential..." referring to theWIKI_INDEX_BASIC_AUTHsecret used for~/.config/wiki-index/basic-auth. That's just a local config-path name (harmless, still accurate to the file path), but worth a pass if you're otherwise renaming things — it now authenticates to the .NET wiki service, not the retired Python one.Tests
No tests added or removed beyond the deletion of
ci/images/wiki-index/test_wiki_index.py, which is correct since the module it tested is gone. Nothing else in this diff needs test coverage — it's all deletions of build/deploy config.Recommendation
Looks reasonable — no blocking issues; comments above are optional.