Rename backlog to docs/TODO.md and fix references

Match the uppercase convention of the other top-level docs; includes the new
Scheduled-work and sanity-check items, and repoints references in STATUS.md and
the /review-repo command.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
sjat 2026-05-30 19:01:22 +02:00
parent b33130eea9
commit de38d1c68b
3 changed files with 6 additions and 2 deletions

View file

@ -80,7 +80,7 @@ dimension/severity; auto-fixes applied (with file list); open findings (prioriti
grouped by dimension, each with location + suggested fix + new/recurring tag); and a
generated, copy-pasteable **follow-up prompt**. See `docs/reviews/README.md`.
## Headless / cron (future — `docs/todo.md` "Scheduled work")
## Headless / cron (future — `docs/TODO.md` "Scheduled work")
When run non-interactively (`claude -p`, e.g. a fortnightly cron): **report only**
do not apply fixes or push to `main`. Write the report artifact and email its summary

View file

@ -19,7 +19,7 @@ _Last reviewed: 2026-05-30._
| `git` | Initialized, trunk-based on `main`, pushed to `origin` (`forgejo.nyumbani.baobab.band:7577`). |
| Pre-commit hooks | Configured: lint, gitleaks, vault-encryption guard. Activate with `pre-commit install` after `make setup`. |
| Vault password client | `scripts/vault-pass-client.sh` fetches the master password from Vaultwarden via `rbw` (wired as `vault_password_file`). Requires `rbw` installed + `rbw unlock`. |
| `/review-repo` | Repo audit: `scripts/repo-scan.py` (Phase 0) + `.claude/commands/review-repo.md`, reports to `docs/reviews/`. On-demand only; cron + email deferred (`docs/todo.md`). |
| `/review-repo` | Repo audit: `scripts/repo-scan.py` (Phase 0) + `.claude/commands/review-repo.md`, reports to `docs/reviews/`. On-demand only; cron + email deferred (`docs/TODO.md`). |
| Terraform HCL (`terraform/`) | Written (proxmox VM module + envs) — but never run; see below |
## Scaffolded but empty — NOT implemented

View file

@ -38,3 +38,7 @@
- [ ] shell setup
- What does it matter in relations to the AIs work on the control node?
- What should we set up on the hosts, if i'll rarely go there?
- [ ] Scheduled work
- /review-repo maybe as claude -p via cron every two weeks?
- Sanity checks: does a photoprism have its pictures? are email services recieving and sending?