Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 5 additions & 6 deletions .github/AGENT-FLOWS-REDESIGN.md
Original file line number Diff line number Diff line change
Expand Up @@ -121,9 +121,9 @@ agent — which, per §1.1, does not exist.
(group by `SourceContext` + message prefix).
- Vahter's legacy tables (`message`, `user`, `banned`, `banned_by_bot`, `callback`,
`vahter_actions`, `llm_triage`) froze at **2026-04-02** during the event-sourcing cutover
(Flyway V23). Any agent querying them gets four-month-stale data that looks live.
`DB.fs:866 GetVahterStats` is dead code; `DB.fs:896 GetVahterActionStats` reading `event`
is the live path.
(Flyway V23), were renamed to `deprecated_*` by V41 (2026-08-12, #362), and are being
dropped by V50 (#494). Query `event` / `snapshot_message` / `snapshot_user` only —
`GetVahterActionStats` reading `event` is the live path.
- Nothing said in the vahters' private moderator channel (`ADMIN_CHANNEL_ID
= -1001170325774`) is persisted. `Bot.fs:1533-1550` — recognized `/vahter` commands are
dispatched without `InsertMessage`; free-form discussion falls through the
Expand Down Expand Up @@ -202,9 +202,8 @@ bots:
traffic_class: high # drives baseline windows + alert sensitivity
query_set: vahter # -> scripts/queries/vahter/*.sql
notes: |
Legacy tables (message, user, banned, banned_by_bot, callback, vahter_actions,
llm_triage) FROZEN at 2026-04-02 (event-sourcing cutover, Flyway V23).
Query `event` / `snapshot_message` / `snapshot_user` only.
Legacy tables renamed to deprecated_* by V41 (2026-08-12, #362); dropped by
V50 (#494). Query `event` / `snapshot_message` / `snapshot_user` only.
coupon:
display_name: CouponHubBot
argocd_app: coupon-bot
Expand Down
5 changes: 2 additions & 3 deletions .github/bots.yml
Original file line number Diff line number Diff line change
Expand Up @@ -38,9 +38,8 @@ bots:
query_set: vahter # -> scripts/queries/vahter/*.sql
community_hashes: []
notes: |
Legacy tables (message, user, banned, banned_by_bot, callback, vahter_actions,
llm_triage) FROZEN at 2026-04-02 (event-sourcing cutover, Flyway V23).
Query `event` / `snapshot_message` / `snapshot_user` only.
Legacy tables renamed to deprecated_* by V41 (2026-08-12, #362); dropped by
V50 (#494). Query `event` / `snapshot_message` / `snapshot_user` only.

coupon:
display_name: CouponHubBot
Expand Down
5 changes: 2 additions & 3 deletions .github/prompts/project.md
Original file line number Diff line number Diff line change
Expand Up @@ -108,9 +108,8 @@ perform these checks and say in your summary which you ran and what you saw:
bot lists that omit a bot in `.github/bots.yml`.
3. Config drift: `bot_setting` keys referenced in code but absent from docs, or documented but
unreferenced; workflow inputs/secrets declared but never consumed.
4. Dead code: functions or files with no remaining callers (a recent event-sourcing cutover in
VahterBanBot left known examples — `DB.fs:866 GetVahterStats` is dead; the live path is
`GetVahterActionStats`).
4. Dead code: functions or files with no remaining callers — confirm with a repo-wide grep for
callers before filing; a symbol that only appears in its own definition is dead.

"I found nothing" without naming what you looked at is not a clean day — it is an unverified
claim, and it is exactly how this role silently became a no-op before.
Expand Down
Loading