Cosmetic follow-up (one of the loose ends). The seed→apps handoffs are done, so the prune: disabled comments on the folded CNPG DB objects shouldn't read "ahead of the … handoff" (future tense) anymore.
Normalizes 17 comments across authentik/immich/paperless/woodpecker/influxdb to standing-guard/past tense ("— a standing guard kept from the … handoff"). Comment-only — no manifest changes; all affected app kustomizations still build.
Closes the tense-normalization item I flagged on the immich fold (#405).
Cosmetic follow-up (one of the loose ends). The seed→apps handoffs are done, so the `prune: disabled` comments on the folded CNPG DB objects shouldn't read "ahead of the … handoff" (future tense) anymore.
Normalizes 17 comments across authentik/immich/paperless/woodpecker/influxdb to standing-guard/past tense ("— a standing guard kept from the … handoff"). **Comment-only — no manifest changes**; all affected app kustomizations still build.
Closes the tense-normalization item I flagged on the immich fold (#405).
The seed->apps ownership handoffs are complete, so the prune: disabled comments
on the folded CNPG DB objects no longer read 'ahead of the ... handoff' (future
tense). Normalize the 17 comments across authentik/immich/paperless/woodpecker/
influxdb to standing-guard/past tense. Comment-only; no manifest changes.
Closes the tense-normalization item flagged on the immich fold review (#405).
Co-Authored-By: Claude Bot <claude-bot@renner.uno>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
🤖Automated review — model claude-haiku-4-5-20251001 (complexity: trivial), commit 1550256d5f9a655afcf0941cf823914eab0e57cf.
Advisory review by the review-bot pipeline. It never approves; a human merges. Push new commits to get a fresh review.
Summary
This PR updates 17 prune-guard comments across 16 YAML files (authentik, immich, paperless, woodpecker, influxdb) to normalize their tense from future ("ahead of the ... handoff") to past/present ("a standing guard kept from the ... handoff"). All changes are cosmetic comment-only updates; no manifest configuration is altered. The grep confirms all instances of the old phrasing have been replaced.
🟢 Observations
All YAML files remain syntactically valid after the comment changes; the kustomize.toolkit.fluxcd.io/prune: disabled annotations and resource specifications are untouched.
The updated comments are clearer and more accurately reflect the current state (handoff is complete, not future).
The influxdb comment (lines 7–8 of externalsecret.yaml) is reworded more substantially but improves clarity: "a standing guard on the bootstrap Secret (admin token)" is more direct than the original multi-line explanation.
Consistency is high across all changes; the new phrasing pattern is uniform.
Tests
No tests are required or affected by comment-only changes.
Recommendation
Looks reasonable — no blocking issues; this is a clean, thorough cosmetic follow-up that closes a documentation loose end.
🤖 **Automated review** — model `claude-haiku-4-5-20251001` (complexity: trivial), commit `1550256d5f9a655afcf0941cf823914eab0e57cf`.
> Advisory review by the `review-bot` pipeline. It never approves; a human merges. Push new commits to get a fresh review.
---
## Summary
This PR updates 17 prune-guard comments across 16 YAML files (authentik, immich, paperless, woodpecker, influxdb) to normalize their tense from future ("ahead of the ... handoff") to past/present ("a standing guard kept from the ... handoff"). All changes are cosmetic comment-only updates; no manifest configuration is altered. The grep confirms all instances of the old phrasing have been replaced.
## 🟢 Observations
- All YAML files remain syntactically valid after the comment changes; the `kustomize.toolkit.fluxcd.io/prune: disabled` annotations and resource specifications are untouched.
- The updated comments are clearer and more accurately reflect the current state (handoff is complete, not future).
- The influxdb comment (lines 7–8 of `externalsecret.yaml`) is reworded more substantially but improves clarity: "a standing guard on the bootstrap Secret (admin token)" is more direct than the original multi-line explanation.
- Consistency is high across all changes; the new phrasing pattern is uniform.
## Tests
No tests are required or affected by comment-only changes.
## Recommendation
Looks reasonable — no blocking issues; this is a clean, thorough cosmetic follow-up that closes a documentation loose end.
<!-- pr-review:sha=1550256d5f9a655afcf0941cf823914eab0e57cf -->
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.
Cosmetic follow-up (one of the loose ends). The seed→apps handoffs are done, so the
prune: disabledcomments on the folded CNPG DB objects shouldn't read "ahead of the … handoff" (future tense) anymore.Normalizes 17 comments across authentik/immich/paperless/woodpecker/influxdb to standing-guard/past tense ("— a standing guard kept from the … handoff"). Comment-only — no manifest changes; all affected app kustomizations still build.
Closes the tense-normalization item I flagged on the immich fold (#405).
🤖 Automated review — model
claude-haiku-4-5-20251001(complexity: trivial), commit1550256d5f9a655afcf0941cf823914eab0e57cf.Summary
This PR updates 17 prune-guard comments across 16 YAML files (authentik, immich, paperless, woodpecker, influxdb) to normalize their tense from future ("ahead of the ... handoff") to past/present ("a standing guard kept from the ... handoff"). All changes are cosmetic comment-only updates; no manifest configuration is altered. The grep confirms all instances of the old phrasing have been replaced.
🟢 Observations
kustomize.toolkit.fluxcd.io/prune: disabledannotations and resource specifications are untouched.externalsecret.yaml) is reworded more substantially but improves clarity: "a standing guard on the bootstrap Secret (admin token)" is more direct than the original multi-line explanation.Tests
No tests are required or affected by comment-only changes.
Recommendation
Looks reasonable — no blocking issues; this is a clean, thorough cosmetic follow-up that closes a documentation loose end.