self-checkup

Run a full control-plane health audit of Dark Flow. You are running this from the Dark Flow repo (/Users/vampire/code/darkflow) as the maintainer. This is NOT a per-project command — it inspects this repo's own consistency AND every project registered in the central Postgres database.

Do the eight audits below in order, collect findings as you go, then synthesize the recommendations grouped by priority. Print the whole report to the console — do not write any file.

Язык вывода: весь отчёт и рекомендации печатай на русском языке. Команды, SQL-запросы, имена полей БД, имена лейблов (status:approved и т.п.) и пути к файлам оставляй как есть — не переводи их. Переводи только пояснения, заголовки разделов, описания проблем и действия.

---

Step 0 — Setup

• Read DATABASE_URL from webapp/.env (default postgresql://darkflow:darkflow@localhost:5432/darkflow). Run all DB queries with:

  psql "$DATABASE_URL" -At -c '<SQL>'
  

  If Postgres is unreachable, print a clear note and still run Step 1 (static, no DB) and Step 5 (git worktrees, filesystem-only). Every other step needs the DB (Step 6 now reads the task store from Postgres, not GitHub) — note them as skipped. Suggest make up to start Postgres.
• Read the current version from VERSION — this is the source of truth for "outdated".
• gh is no longer required to run this audit — Step 6 now reads the task store via df/ psql, not gh issue. gh auth status only matters for the Step 2 token check below (which covers vulnerability-check, the one remaining routine that calls gh api for security alerts).

---

Step 1 — Prompt ↔ settings consistency (this repo, static)

Cross-check that the repo's own pieces don't contradict each other. Report every mismatch.

• Routines: every routine in the catalog webapp/src/lib/routines.ts (ALL_ROUTINES) must have (a) a command template at templates/.claude/commands/darkflow/<name>.md and (b) a reference doc at routines/<name>.md. List any catalog routine missing either, and any command/doc with no catalog entry. (Schedule + per-project overrides live in the DB; there is no routines.yml anymore.)
• Commands: every command in install.sh's ALL_DF_COMMANDS array must have an existing template at templates/.claude/commands/darkflow/<name>.md, and vice-versa. Flag any command listed with no template file, and any template with no array entry.
• Task field values: install.sh no longer provisions any label taxonomy (task queue moved to the Issue table's status/priority/source/action/needsHuman columns — there's nothing left to "create"). Grep the command templates and routines/ docs for df task create --status/--priority/--source/--action values and flag any that drift from the canonical set below (typo or a routine inventing a new value the webapp/UI doesn't render): action: fix, reply; priority: critical, high, medium, low; source: ads, build, ci, code-health, design, gsc, mailbox, manual, openpanel, security-review, seo, signoz, uptime, user-feedback; status: proposed, approved, rejected, in-progress, none.
• Modules: the _module_active() case statement in install.sh must list every MOD_* module flag defined in the script (a known past gotcha — docs-audit and product-overview were once missing from it). Diff the two sets.
• Version: VERSION must equal the most recent ## [X.Y.Z] heading in CHANGELOG.md.