Repository navigation
feat(dashboard): manage auto-moderation rules from the dashboard - #457
Merged
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Contributor
Lunaria Status Overview🌕 This pull request will trigger status changes. Learn moreBy default, every PR changing files present in the Lunaria configuration's You can change this by adding one of the keywords present in the Tracked Files
Warnings reference
|
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## refactor/v3-database #457 +/- ##
========================================================
- Coverage 51.20% 50.53% -0.67%
========================================================
Files 338 354 +16
Lines 6867 7365 +498
Branches 1398 1530 +132
========================================================
+ Hits 3516 3722 +206
- Misses 2301 2478 +177
- Partials 1050 1165 +115
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
RedStar071
force-pushed
the
refactor/v3-automod
branch
from
October 10, 2026 14:52
32986ed to
3723214
Compare
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
RedStar071
force-pushed
the
refactor/v3-automod
branch
from
October 10, 2026 17:56
3723214 to
f6f32a8
Compare
RedStar071
force-pushed
the
refactor/v3-automod
branch
from
October 10, 2026 19:19
f6f32a8 to
75550b2
Compare
RedStar071
force-pushed
the
refactor/v3-automod
branch
from
October 11, 2026 14:14
75550b2 to
b846545
Compare
RedStar071
force-pushed
the
refactor/v3-database
branch
from
October 11, 2026 14:14
0476800 to
0999956
Compare
RedStar071
force-pushed
the
refactor/v3-database
branch
from
October 11, 2026 20:12
0999956 to
fd9a16e
Compare
RedStar071
force-pushed
the
refactor/v3-automod
branch
from
October 11, 2026 20:12
b846545 to
7de534f
Compare
RedStar071
force-pushed
the
refactor/v3-automod
branch
2 times, most recently
from
October 12, 2026 08:28
8db6fea to
260a60f
Compare
RedStar071
marked this pull request as ready for review
October 12, 2026 10:48
|
5 findings · reviewed 🟠
|
![pullfrog[bot]](https://avatars.githubusercontent.com/in/1768019?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
ℹ️ No critical issues — three minor suggestions inline.
Reviewed changes
I read the server routes, utilities, storage layer, composable, components, draft helpers and the service tests in full. I skipped the generated locale JSON and the lockfile.
- Rule routes —
GET/POST/PATCH/DELETEunderautomod/rules, wrapped handlers,authorizehook, audit events and rate limits all follow the repo traps. - Write queue and validator — per-guild
AsyncQueue, PATCH validated against the row read inside the queue, bot-ported validation withconfusables. - Storage — ORM 8 reads and writes with
BigIntbinds, scoped byguildId. - Dashboard UI —
useAutomodRules, rule cards, editor modal, duration input, embedded inAutomod.vue.
ℹ️ Bot will not see changes until its cache drops
This is the open question the PR already raises, so I only restate it as a decision for a human. Until the bot invalidates its per-process cache, a rule saved here does nothing, and the dashboard toasts success. I couldn't check the bot side from this repo. Please confirm that is acceptable, or that the UI should say so.
ℹ️ Unique-index handling is unverified
isUniqueNameError in server/utils/automod/rules.ts matches on the index name inside the error message. The index isn't declared in the contract, and the only test for it uses a hand-written mock error. I couldn't confirm that ORM 8 puts the constraint name in message or cause. If either is wrong, the cross-process name race surfaces as a 500 instead of nameTaken. The in-process queue still holds, so this only matters for the bot-versus-dashboard race. A test against a real database would settle it.
claude-sonnet-5-5 ｜ 𝕏
RedStar071
force-pushed
the
refactor/v3-database
branch
from
October 12, 2026 11:47
f87d014 to
00f9386
Compare
RedStar071
force-pushed
the
refactor/v3-automod
branch
from
October 12, 2026 11:47
260a60f to
2457b9e
Compare
Contributor
There was a problem hiding this comment.
Important
The new commit leaves the generated i18n schema out of date, which fails a CI gate. The three open threads from the prior review are not yet addressed.
Reviewed changes
Re-reviewed the branch since the prior pullfrog review (head 260a60f, now rebased away), which amounts to the show auto-moderation rules as cards commit.
- Rule cards —
Rules.vuerenders each rule as a card with a type icon, threshold, action, on-hit summary and resolved exemptions, backed byAUTOMOD_TYPE_ICONSandformatCompactDuration. - Automod page layout —
Automod.vuegets aDashboardPageHeader, a module-switch header card (modulesAutomodjoins the staged-changes toggles) and a "Module settings" card. - Locales — ten new
guild_settings.automod.*keys, added as empty placeholders in every non-enlocale.
⚠️ i18n/schemas/guilds.schema.json was not regenerated for the new keys
The commit adds module_hint, module_settings and eight rules.* keys (action, first_infraction, nothing, on_hit, soft_alert_short, soft_delete_short, soft_log_short, threshold) to i18n/locales/*/guilds.json, but i18n/schemas/guilds.schema.json has none of them. The CI step "Check i18n schema is up to date" runs vp run i18n:schema followed by git diff --exit-code i18n/schema.json i18n/schemas i18n/locales, so it will fail on this head.
Technical details
# Regenerate the i18n schema
## Affected sites
- i18n/schemas/guilds.schema.json — missing `guild_settings.automod.module_hint`, `module_settings`, and `rules.{action,first_infraction,nothing,on_hit,soft_alert_short,soft_delete_short,soft_log_short,threshold}`
- .github/workflows/ci.yml:368-371 — the gate that diffs the regenerated schema
## Required outcome
- `vp run i18n:schema` produces no diff against the committed `i18n/schemas/`.
## Suggested approach
- Run `pnpm vp run i18n:schema` and commit the result.The three earlier threads (guild-switch race in useAutomodRules, the 20-digit isSnowflake, and the top-level hardAction === "Timeout" check) are unchanged by the new commit and stay open. Rules.spec.ts still fits the card markup, but nothing yet covers thresholdLabel, onHitLabel, exemptions or formatCompactDuration.
claude-sonnet-5-5 ｜ 𝕏
RedStar071
force-pushed
the
refactor/v3-automod
branch
from
October 12, 2026 12:30
2457b9e to
31a1623
Compare
RedStar071
force-pushed
the
refactor/v3-database
branch
from
October 12, 2026 12:30
00f9386 to
0cb61e3
Compare
Contributor
There was a problem hiding this comment.
ℹ️ No critical issues — one minor wording suggestion inline.
Reviewed changes
Re-reviewed the branch since the prior pullfrog review (head 2457b9e), which amounts to the lock rule writes across instances and keep rule edits on their own server commit. The three earlier threads and the stale i18n/schemas/guilds.schema.json are all resolved by it.
- Cross-instance write lock —
write()inserver/utils/automod/rules.tsnow reads the rules and writes inside one transaction that first takespg_advisory_xact_lock(namespace, guildKey), and the storage functions take the transaction'sorm. This mirrors the audit drain's lock and keeps the per-processAsyncQueuein front. - Guild-switch race —
useAutomodRulesroutes create, update and delete throughpatchRules, which drops the answer when the active guild changed during the request. - Snowflake bound —
validation.tsuses the sharedisSnowflake(17 to 19 digits, withinBIGINT). - Timeout rule action —
RuleEditor.vueblocks a rule whose own action isTimeoutwith no duration, not just escalation steps. - Smaller fixes —
structuredClone(toRaw(...))for rules held in aref, exact fractional seconds insplitDuration,/escaped in the audit key, regenerated i18n schema, and tests for each.
claude-sonnet-5-5 ｜ 𝕏
|
|
||
| const actionError = computed(() => | ||
| submitted.value && draft.hardAction === "Timeout" && draft.hardActionDuration <= 0 | ||
| ? ts("guild_settings.automod.rules.errors.timeoutNeedsDuration") |
Contributor
There was a problem hiding this comment.
This reuses timeoutNeedsDuration, whose copy reads "A timeout step needs a duration." Here the field belongs to the rule's own action, not an escalation step, so the message points at the wrong thing. A separate key (for example timeoutActionNeedsDuration) would read correctly.
Comment on lines
+95
to
+101
| if (body.hardActionDuration !== undefined) { | ||
| const { minimum, maximum } = AutoModerationRuleLimits.hardActionDuration; | ||
| // Zero and `null` both make the hard action permanent: | ||
| if (body.hardActionDuration === null || body.hardActionDuration === 0) | ||
| data.hardActionDuration = null; | ||
| else if (isInteger(body.hardActionDuration, minimum, maximum)) | ||
| data.hardActionDuration = body.hardActionDuration; |
Contributor
There was a problem hiding this comment.
POST /api/guilds/:guild/automod/rules accepts hardAction: "Timeout" without a duration, leaving hardActionDuration: null. This validator also accepts an explicit zero or null duration. The bot skips these timeouts, so the API reports a successful save for a rule that never applies its punishment.
Check the final action and duration together before writing. Include PATCH requests that change only the action or duration. Fix this before merging.
Artifacts
Executable timeout contract harness
- Loads actual repository modules from the requested Git revision and makes localhost requests with mocked external boundaries, providing the executed reproduction source.
- Runs the contract harness and saves its observed output with command, working directory, and exit code, making the captures reproducible.
Focused source and related repository inspection commands
- Checks the relevant source locations, higher-stack ancestry and changes, and shared-contract references in related repositories without modifying product code.
Timeout save and bot behavior at PR457 head
- Runs POST and PATCH against the supplied head and captures successful null-duration writes followed by zero timeout calls, confirming the finding.
Timeout contract behavior at PR461 head
- Repeats the focused request and bot-consumer matrix at PR461 and captures the same ineffective Timeout states, showing that this higher-stack head does not fix the defect.
Timeout contract behavior at PR462 head
- Repeats the focused request and bot-consumer matrix at PR462 and captures the same ineffective Timeout states, showing that this higher-stack head does not fix the defect.
Relevant code and related contract usage checks
- Captures executed source inspection and narrow repository searches, showing unchanged higher-stack contract code, the actual bot skip, no blog/CDN matches, and an empty product diff.
Prompt To Fix With AI
This is a comment left during a code review.
Path: server/utils/automod/validation.ts
Line: 95-101
Comment:
**Saved timeout does nothing**
`POST /api/guilds/:guild/automod/rules` accepts `hardAction: "Timeout"` without a duration, leaving `hardActionDuration: null`. This validator also accepts an explicit zero or null duration. The [bot skips these timeouts](https://github.com/wolfstar-project/wolfstar/blob/HEAD/projects/bot/src/lib/moderation/structures/ModerationMessageListener.ts), so the API reports a successful save for a rule that never applies its punishment.
Check the final action and duration together before writing. Include PATCH requests that change only the action or duration. Fix this before merging.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
RedStar071
force-pushed
the
refactor/v3-database
branch
from
October 12, 2026 18:19
0cb61e3 to
1e5e4b4
Compare
RedStar071
force-pushed
the
refactor/v3-automod
branch
2 times, most recently
from
October 13, 2026 11:58
0c3bcdd to
490089f
Compare
Comment on lines
+290
to
+291
| const { type: _type, ...changes } = body; | ||
| const result = target ? await updateRule(target.id, changes) : await createRule(body); |
Contributor
There was a problem hiding this comment.
Saving an edit sends every field, including fields the admin did not change. If two admins open the same rule, one can save new exemptions, then the other can rename it and save. The second request restores the old exemptions. The database lock orders the requests, but it cannot tell which values came from an old editor.
Send only fields changed since the editor opened, or reject saves based on an older version.
Prompt To Fix With AI
This is a comment left during a code review.
Path: app/components/guild/automod/Rules.vue
Line: 290-291
Comment:
**Edits undo saved changes**
Saving an edit sends every field, including fields the admin did not change. If two admins open the same rule, one can save new exemptions, then the other can rename it and save. The second request restores the old exemptions. The database lock orders the requests, but it cannot tell which values came from an old editor.
Send only fields changed since the editor opened, or reject saves based on an older version.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
RedStar071
force-pushed
the
refactor/v3-automod
branch
2 times, most recently
from
October 13, 2026 14:45
6ea199d to
e7d1080
Compare
RedStar071
force-pushed
the
refactor/v3-database
branch
from
October 13, 2026 14:45
7f1312e to
4020cb8
Compare
RedStar071
force-pushed
the
refactor/v3-automod
branch
from
October 13, 2026 15:28
e7d1080 to
ad4f6c4
Compare
RedStar071
force-pushed
the
refactor/v3-database
branch
from
October 13, 2026 15:28
4020cb8 to
369d391
Compare
The V7 contract stores auto-moderation as one `GuildAutoModerationRule` row per rule instead of per-filter columns, so the seven filter pages removed in the previous layer come back as a rule list and editor. - `GET/POST /api/guilds/:guild/automod/rules` and `PATCH/DELETE …/rules/:rule`, gated by an `authorize` hook that resolves the guild and member once and audits a refusal. Every change is audited under `automodRule.<name>`. - Request bodies go through the bot's own validator, ported with its limits and its `confusables` word normalization, so a rule written here is one the bot's API would have accepted. A PATCH is validated against the rule the database has inside a per-guild write queue, so two requests changing different options do not restore each other's value. - Names are unique per guild whatever the case; the unique index is what holds across processes and maps to a 409. - `useAutomodRules()` writes each change at once (rules are rows, not `GuildData` keys, so they skip the staged-changes bar) and patches the list with the server's answer. - The editor covers every rule type from the type's default options: thresholds, soft actions, punishment and duration, escalation steps, and ignored roles and channels. Co-authored-by: Claude <noreply@anthropic.com>
Each rule is a card with its type icon, threshold, punishment and what happens on a hit, and the module gets its own header card with the switch.
… on their own server
RedStar071
force-pushed
the
refactor/v3-database
branch
from
October 13, 2026 17:19
369d391 to
4c434a3
Compare
RedStar071
force-pushed
the
refactor/v3-automod
branch
from
October 13, 2026 17:19
ad4f6c4 to
67278d5
Compare
RedStar071
added a commit
that referenced
this pull request
Oct 13, 2026
…454) ### 🔗 Linked issue Part of the stack superseding #422. Depends on #453. **Stack:** #451 foundation ← #452 header/footer ← #453 marketing ← #454 `/app` dashboard ← #455 V7 schema + Prisma ORM 8 (draft) ### 🧭 Context The dashboard becomes one client-rendered page that keeps the active guild in state instead of the URL. Unlike #422 this layer does not depend on the V7 schema: it runs against the current database and typechecks. ### 📚 Description `app/pages/app.vue` renders the picker, the section components and the logs panel inside the dashboard layout, which gains a server rail, a Modules summary card and grouped sidebar navigation. `useActiveGuild()` holds guild, section and logs tab; `useDashboardNavigation()` parks any switch behind the unsaved-changes dialog while edits are staged. The three guild stores are keyed per guild, and the save handler captures the guild id before awaiting so a late PATCH response cannot clear another guild's draft. The selection is mirrored to localStorage so a reload lands on the same server. `/guilds/:id/manage/*` and `/guilds/:id/logs/*` stay as shims that record the target into state and forward to `/app`. Route rules: `/app` is `ssr: false`, not prerendered, out of the sitemap and `robots: false`; `/guilds/**` is `robots: false` as well (new here, the auth-gated shims were indexable before). `@vueuse/router` has no remaining usage and is removed; the lockfile diff is limited to that package. Open question: the shims render a spinner on the server and redirect in the browser because the guild id has to land in client state. A route middleware would be cleaner but cannot write that state. Fine with the current shape unless someone has a better idea. ### 🎨 Console layout The dashboard now follows the console redesign (rail, sidebar, title bar, cards), with the phone, foldable and tablet variants. - **Shell.** A server rail, a sidebar whose sections are grouped under Modules and Records, a 48px title bar with the unsaved-changes pill, and a docked save bar. On phones the sidebar and the rail move into a drawer and the main sections get a tab bar. - **Sidebar.** Sections can be pinned and the ones opened last appear as shortcuts. Both are browser-local (`wolfstar-dashboard-nav`) and never reach the server. `app/utils/dashboard-nav.ts` is the single list the sidebar, the tab bar and the page title read. - **Overview.** Counts of the server, the moderation actions of the last seven days as a chart, the module list and the activity feed in cards. Everything shown is read from the existing log and guild routes; the chart is bucketed in the browser from one page of the moderation log (its total is the log's own, so it stays exact past 100 actions and the chart says so). - **Surfaces.** Rail, sidebar, cards and page use the design system's ink scale (`--ink-*`, added next to the spectrum tokens) in the dark theme and white with a tinted rail in the light one. `console-card` and `console-label` are the shared utilities. Later layers adapt what they own: #455 lays the settings sections out as cards, #457 the auto-moderation rules, #461 swaps the `/profile` links for the preferences dialog. ###⚠️ Not in the design The mockup also has Auto-Delete and Auto-Purge pages, a "Prisma 8 contract" badge and an open-reports count. Auto-Delete and Auto-Purge are not here: the tables exist in the contract but the dashboard has no routes for them, so they need their own layer. The badge and the open-reports count are mock data with nothing behind them. > 🤖 AI disclosure: [Wolfstar Agent Kit](https://github.com/wolfstar-project/wolfstar-agent-kit) modified this description. [My AI open-source policy](https://harlanzw.com/blog/ai-in-open-source). <!-- greptile_comment --> <!-- greptile_summary --> <h2><a href="https://app.greptile.com/api/retrigger?id=78359990"><picture><source media="(prefers-color-scheme: dark)" srcset="https://greptile-static-assets.s3.amazonaws.com/badges/RetriggerDark.svg?v=2"><source media="(prefers-color-scheme: light)" srcset="https://greptile-static-assets.s3.amazonaws.com/badges/Retrigger.svg?v=2"><img alt="Retrigger" src="https://greptile-static-assets.s3.amazonaws.com/badges/Retrigger.svg?v=2" align="right"></picture></a>Confidence Score: 4/5</h2> <!-- greptile-risk --> Do not merge until the outstanding settings-edit loss in previous comment 1 is fixed; the two new navigation and activity-display concerns are non-blocking. <h2>T-Rex evidence</h2> **[Evidence from the check](https://app.greptile.com/trex/artifacts/747f3009-3e3d-45fe-bf44-75536b9ebbe8)** - The component test exercises both real card variants with Ctrl, Meta, and ordinary clicks using actual composables; its latest event-observation revision still needs execution. **[Evidence from the check](https://app.greptile.com/trex/artifacts/dd50729a-d872-4d2b-bb7a-bb04b6ddcd5c)** - The configuration launches Chromium through Playwright and supplies click, viewport, video, and poster capture commands; the latest commands still need a completed run. **[Evidence from the check](https://app.greptile.com/trex/artifacts/10446552-fa3f-41b7-a293-b53f0b1f41f4)** - The card was extracted with git show from the specified base and rendered without editing tracked source; this is the executed baseline component. **[Command output from the check](https://app.greptile.com/trex/artifacts/616e8d30-a318-4665-8720-c9f50d4504f9)** - The last completed base run captured unchanged original-tab guild, section, and route after Ctrl-click, then failed because no new tab was observed; this proves only the baseline state behavior. **[Command output from the check](https://app.greptile.com/trex/artifacts/5ae81b80-790f-48a6-87ca-3418dc486b4d)** - Git show captured numbered card and composable source from head and all four requested higher snapshots; the inspected paths retain the unconditional click handler. **[Command output from the check](https://app.greptile.com/trex/artifacts/a0076d94-fec5-4a45-9d22-791ac7467f71)** - The initial Chromium run failed because the real tooltip lacked its provider; the harness subsequently added the provider and reached the click path. **[After: Pr454 Failed Counts Success](https://app.greptile.com/trex/artifacts/293fa0c1-8663-459f-9a98-12b5a00f1c55)** - What the screen looked like at this point in the check. **[After: Pr454 Failed Counts Failure](https://app.greptile.com/trex/artifacts/60997d03-470a-470f-be48-710650912213)** - What the screen looked like at this point in the check. **[After: Pr454 Failed Counts Empty](https://app.greptile.com/trex/artifacts/4979ecb2-b282-4ef4-9013-99f5024e6b98)** - What the screen looked like at this point in the check. **[▶ page@b1577e3ac2036f8690dfae10f2d355d0.webm](https://app.greptile.com/trex/artifacts/b8ad8f63-abf6-4366-ae6b-f57d29efc060)** - The flow T-Rex ran, recorded end to end. **[Before: Pr454 Failed Counts Success](https://app.greptile.com/trex/artifacts/56846c8e-03bc-40ae-ab99-7b8aea18bcd8)** - What the screen looked like at this point in the check. **[Before: Pr454 Failed Counts Failure](https://app.greptile.com/trex/artifacts/9f43d5fc-5383-4dd3-9125-d44291742d2a)** - What the screen looked like at this point in the check. **[Before: Pr454 Failed Counts Empty](https://app.greptile.com/trex/artifacts/90962557-d069-410a-bd12-46842b9a2c3b)** - What the screen looked like at this point in the check. **[▶ page@db1d5220ce2e59a5e6a32fafa94e0c50.webm](https://app.greptile.com/trex/artifacts/64e81fbb-b1cd-46b3-ac38-b081bc7137b7)** - The flow T-Rex ran, recorded end to end. **[▶ Recording of the check](https://app.greptile.com/trex/artifacts/b8ad8f63-abf6-4366-ae6b-f57d29efc060)** - Recorded the base component with populated, failing and empty endpoint configurations; the original overview has no activity counts or chart. **[▶ Recording of the check](https://app.greptile.com/trex/artifacts/64e81fbb-b1cd-46b3-ac38-b081bc7137b7)** - Recorded each condition for approximately six seconds with the real composables; failed requests present the same zero activity as successful empty responses. **[Base overview with populated activity endpoints configured](https://app.greptile.com/trex/artifacts/56846c8e-03bc-40ae-ab99-7b8aea18bcd8)** - Captured the rendered base component with populated endpoints available; it does not display moderation or command activity. **[Base overview with failed activity endpoints configured](https://app.greptile.com/trex/artifacts/9f43d5fc-5383-4dd3-9125-d44291742d2a)** - Captured the rendered base component with failing endpoints available; it has no activity counts or chart to misrepresent those failures. **[Base overview with empty activity endpoints configured](https://app.greptile.com/trex/artifacts/90962557-d069-410a-bd12-46842b9a2c3b)** - Captured the rendered base component with empty endpoints available; its activity presentation remains absent. **[Head overview after populated successful requests](https://app.greptile.com/trex/artifacts/293fa0c1-8663-459f-9a98-12b5a00f1c55)** - Captured the head after successful requests settled; DOM assertions verified six cases, twelve commands and nonzero chart activity. **[Head overview after activity requests failed](https://app.greptile.com/trex/artifacts/60997d03-470a-470f-be48-710650912213)** - Captured the head after both requests reached error status; DOM assertions verified zero counts and seven zero-height bars without failure copy. **[Head overview after successful empty requests](https://app.greptile.com/trex/artifacts/4979ecb2-b282-4ef4-9013-99f5024e6b98)** - Captured the head after successful empty responses; its counts and chart accessibility text match the failed-request condition. **[Evidence from the check](https://app.greptile.com/trex/artifacts/8912b975-e7f7-4bb3-bbdb-498446d0f2d8)** - Executed this uniquely named test against both snapshots; it asserts the observed success, failure and empty-response presentations. **[Evidence from the check](https://app.greptile.com/trex/artifacts/560c70bd-12ce-4505-94a8-1f50ce5516b7)** - Used this configuration to run the component test and capture browser observations; unrelated agent tests were not included. **[Evidence from the check](https://app.greptile.com/trex/artifacts/c4c41f0a-8c42-44d2-b8be-2c55bac4ef3c)** - Exported the exact base component using git show and imported it into the browser test; no checkout was needed. **[Evidence from the check](https://app.greptile.com/trex/artifacts/23cc6a71-ac8b-4cc5-b7cd-d0c78b7a7146)** - Exported the exact head component using git show and imported it into the browser test; its activity failure behavior was exercised directly. **[Command output from the check](https://app.greptile.com/trex/artifacts/1ab25530-22b0-47c1-b5a8-b6709be2f0d1)** - Captured the successful base test command and observed DOM output; the original overview has no activity counts, chart or activity requests. **[Command output from the check](https://app.greptile.com/trex/artifacts/9a6296ab-fe1d-479b-a603-7d5bfc9151c0)** - Captured the successful head test command, request queries, error messages and equality assertions; failed activity is displayed exactly like empty activity. **[Command output from the check](https://app.greptile.com/trex/artifacts/70438c94-ff0c-4686-a05d-440c3264c8f2)** - Repeated the head test and captured rendered text, dimensions and visible ancestors alongside request results; the failure presentation exists in the rendered browser layout. **[Command output from the check](https://app.greptile.com/trex/artifacts/bdf87b92-0d78-4e3c-baaa-e4d828c058d4)** - Captured 19 git show and diff commands with line-numbered output; all four higher snapshots retain the activity status/error omission. **[Evidence from the check](https://app.greptile.com/trex/artifacts/747f3009-3e3d-45fe-bf44-75536b9ebbe8)** - The component test exercises both real card variants with Ctrl, Meta, and ordinary clicks using actual composables; its latest event-observation revision still needs execution. **[Evidence from the check](https://app.greptile.com/trex/artifacts/dd50729a-d872-4d2b-bb7a-bb04b6ddcd5c)** - The configuration launches Chromium through Playwright and supplies click, viewport, video, and poster capture commands; the latest commands still need a completed run. **[Evidence from the check](https://app.greptile.com/trex/artifacts/10446552-fa3f-41b7-a293-b53f0b1f41f4)** - The card was extracted with git show from the specified base and rendered without editing tracked source; this is the executed baseline component. **[Command output from the check](https://app.greptile.com/trex/artifacts/616e8d30-a318-4665-8720-c9f50d4504f9)** - The last completed base run captured unchanged original-tab guild, section, and route after Ctrl-click, then failed because no new tab was observed; this proves only the baseline state behavior. **[Command output from the check](https://app.greptile.com/trex/artifacts/5ae81b80-790f-48a6-87ca-3418dc486b4d)** - Git show captured numbered card and composable source from head and all four requested higher snapshots; the inspected paths retain the unconditional click handler. **[Command output from the check](https://app.greptile.com/trex/artifacts/a0076d94-fec5-4a45-9d22-791ac7467f71)** - The initial Chromium run failed because the real tooltip lacked its provider; the harness subsequently added the provider and reached the click path. **[▶ Recording of the check](https://app.greptile.com/trex/artifacts/b8ad8f63-abf6-4366-ae6b-f57d29efc060)** - Recorded the base component with populated, failing and empty endpoint configurations; the original overview has no activity counts or chart. **[▶ Recording of the check](https://app.greptile.com/trex/artifacts/64e81fbb-b1cd-46b3-ac38-b081bc7137b7)** - Recorded each condition for approximately six seconds with the real composables; failed requests present the same zero activity as successful empty responses. **[Base overview with populated activity endpoints configured](https://app.greptile.com/trex/artifacts/56846c8e-03bc-40ae-ab99-7b8aea18bcd8)** - Captured the rendered base component with populated endpoints available; it does not display moderation or command activity. **[Base overview with failed activity endpoints configured](https://app.greptile.com/trex/artifacts/9f43d5fc-5383-4dd3-9125-d44291742d2a)** - Captured the rendered base component with failing endpoints available; it has no activity counts or chart to misrepresent those failures. **[Base overview with empty activity endpoints configured](https://app.greptile.com/trex/artifacts/90962557-d069-410a-bd12-46842b9a2c3b)** - Captured the rendered base component with empty endpoints available; its activity presentation remains absent. **[Head overview after populated successful requests](https://app.greptile.com/trex/artifacts/293fa0c1-8663-459f-9a98-12b5a00f1c55)** - Captured the head after successful requests settled; DOM assertions verified six cases, twelve commands and nonzero chart activity. **[Head overview after activity requests failed](https://app.greptile.com/trex/artifacts/60997d03-470a-470f-be48-710650912213)** - Captured the head after both requests reached error status; DOM assertions verified zero counts and seven zero-height bars without failure copy. **[Head overview after successful empty requests](https://app.greptile.com/trex/artifacts/4979ecb2-b282-4ef4-9013-99f5024e6b98)** - Captured the head after successful empty responses; its counts and chart accessibility text match the failed-request condition. **[Evidence from the check](https://app.greptile.com/trex/artifacts/8912b975-e7f7-4bb3-bbdb-498446d0f2d8)** - Executed this uniquely named test against both snapshots; it asserts the observed success, failure and empty-response presentations. **[Evidence from the check](https://app.greptile.com/trex/artifacts/560c70bd-12ce-4505-94a8-1f50ce5516b7)** - Used this configuration to run the component test and capture browser observations; unrelated agent tests were not included. **[Evidence from the check](https://app.greptile.com/trex/artifacts/c4c41f0a-8c42-44d2-b8be-2c55bac4ef3c)** - Exported the exact base component using git show and imported it into the browser test; no checkout was needed. **[Evidence from the check](https://app.greptile.com/trex/artifacts/23cc6a71-ac8b-4cc5-b7cd-d0c78b7a7146)** - Exported the exact head component using git show and imported it into the browser test; its activity failure behavior was exercised directly. **[Command output from the check](https://app.greptile.com/trex/artifacts/1ab25530-22b0-47c1-b5a8-b6709be2f0d1)** - Captured the successful base test command and observed DOM output; the original overview has no activity counts, chart or activity requests. **[Command output from the check](https://app.greptile.com/trex/artifacts/9a6296ab-fe1d-479b-a603-7d5bfc9151c0)** - Captured the successful head test command, request queries, error messages and equality assertions; failed activity is displayed exactly like empty activity. **[Command output from the check](https://app.greptile.com/trex/artifacts/70438c94-ff0c-4686-a05d-440c3264c8f2)** - Repeated the head test and captured rendered text, dimensions and visible ancestors alongside request results; the failure presentation exists in the rendered browser layout. **[Command output from the check](https://app.greptile.com/trex/artifacts/bdf87b92-0d78-4e3c-baaa-e4d828c058d4)** - Captured 19 git show and diff commands with line-numbered output; all four higher snapshots retain the activity status/error omission. <a href="https://app.greptile.com/trex/runs/31698547/artifacts?artifact=747f3009-3e3d-45fe-bf44-75536b9ebbe8"><picture><source media="(prefers-color-scheme: dark)" srcset="https://greptile-static-assets.s3.amazonaws.com/badges/ViewArtifactsDark.svg?v=4"><source media="(prefers-color-scheme: light)" srcset="https://greptile-static-assets.s3.amazonaws.com/badges/ViewArtifacts.svg?v=4"><img alt="View artifacts" src="https://greptile-static-assets.s3.amazonaws.com/badges/ViewArtifacts.svg?v=4"></picture></a> <h3>Summary</h3> Replaces guild-specific dashboard pages with a client-rendered `/app` page. - Server settings and logs now open inside one `/app` dashboard. - The dashboard adds a grouped sidebar, server rail, and phone navigation. - The dashboard brings server stats, module settings, and logs into sections. - New dashboard and server-setting labels appear across the supported languages. ### T-Rex validation blocked The server-card modifier-click check could not complete because its browser validation session reached its execution limit before running the current-card comparison. The completed baseline run does not establish or contradict the current-card behavior. <!-- greptile_confidence_score:4 --> <sub>Reviews (9) · Last reviewed commit: ["fix(dashboard): keep a single hover high..."](69b75cd) · [Reviewed by Greptile](https://www.greptile.com/?utm_source=greptile_expert&utm_medium=github&utm_campaign=code_reviews&utm_content=wolfstar-project/wolfstar.rocks)</sub> <!-- /greptile_comment -->
RedStar071
added a commit
that referenced
this pull request
Oct 13, 2026
…ly (#455) ### 🔗 Linked issue Part of the stack superseding #422. Depends on #454. Follows the bot's V7 branch, wolfstar-project/wolfstar#208. **Stack:** #451 foundation ← #452 header/footer ← #453 marketing ← #454 `/app` dashboard ← #455 V7 contract + ORM 8 only ← #457 auto-moderation rules ### 🧭 Context The bot's V7 branch runs on Prisma ORM 8 only and reshaped the database: settings live in normalized tables under `Modules`, and auto-moderation is one `GuildAutoModerationRule` row per rule instead of per-filter columns. The first commit on this branch followed an earlier snapshot of that contract, kept Prisma 7 next to ORM 8, and left typecheck red because nobody had decided how one settings view maps onto the new tables. The bot has decided since, so this PR copies its answer. ### 📚 Description **Prisma 7 is gone.** `schema.prisma`, `prisma7.config.ts`, `@prisma/client`, the pg adapter, the generator and every `prisma:migrate:*` script are removed. `prisma:generate` now runs `prisma contract emit`, so Netlify and CI call the same task as before. **The contract comes from the bot's repository.** `vendor/wolfstar` is a git submodule of wolfstar-project/wolfstar tracking `V7`, and `prisma.config.ts` reads `projects/database/src/contract.prisma` from it. The bot changes the contract and migrates first; this app follows by bumping the submodule, which Renovate can open as a PR. Versions match the bot's (`@prisma/orm-postgres` rc.13, `prisma` rc.19, the typed-JSON extension with its patch). A unit test compares the emitted storage hash with the one the pinned bot commit records for its migrations: ``` "storageHash":"c43f2589cd8e65306a24f8c685dddf640e494f3301c6087bfe5da06da7e4412c" ``` The artefacts are emitted into the gitignored `server/database/generated/prisma/` on `postinstall`, which also initializes the submodule when a checkout left it empty, so no workflow needs `submodules: true`. **Settings model.** `GuildData` is the bot's flat object; `columns.ts` maps each key to its table and column and `storage.ts` reads and writes the tables in one transaction. The settings UI moves to those keys: Home, Modules, Auto-moderation, Moderation, Channels, Roles, Commands, Reports. V7 has no prefix, no `selfmod*` filters and no `events*` / `messagesModeration*` settings, so the seven filter pages and the Events page are removed here; #457 brings auto-moderation back as rules. **Audit drain on ORM 8.** The façade exposes no isolation level, so appends are serialized with the advisory lock the bot's `AuditLogManager` takes. Two things I found on the way and fixed here: - Channels always opened empty, whatever was saved. It now shows the saved channels. - rc.13 rejects `url: ""` when the client is constructed, which broke prerendering at build time where `DATABASE_URL` is unset. The client gets `undefined` instead and connects lazily. Settings PATCH bodies used to be written as sent. They now go through a validator that refuses unknown keys and wrong value types with a 400. ###⚠️ Things a reviewer should decide - **Migrations belong to the bot now**, and its ORM 8 migrations are visible under `vendor/wolfstar/projects/database/migrations/`. I kept `server/database/migrations/` because `20260920000000_v7_contract_and_modules` is still the only DDL for the tables the contract marks `@@control(external)`; nothing here applies it. It should move to the bot's repo, after which the directory can go. - **Only the contract is shared.** The bot's `columns.ts` / `storage.ts` import its own build output, so they are ported here by hand and have to follow a submodule bump manually; typecheck catches a column that disappeared. Publishing `wolfstar-database` as a package would remove the ports. - **The bot caches settings per process** and only drops the cache on its own writes. A dashboard save reaches the database at once but the bot acts on it only after its cache is invalidated. Same as before this PR, more visible now that both sides share one model. - **The two services hash audit rows differently** (`shared/audit/envelope.ts` here, `AuditLogEnvelope.ts` in the bot), so `pnpm audit:verify` will flag rows the bot wrote. Not introduced here, not solved here. - Locale files: a translation is kept only where its English source did not change, everything else is an empty placeholder. > 🤖 AI disclosure: [Wolfstar Agent Kit](https://github.com/wolfstar-project/wolfstar-agent-kit) modified this description. [My AI open-source policy](https://harlanzw.com/blog/ai-in-open-source). <!-- greptile_comment --> <!-- greptile_summary --> <h2><a href="https://app.greptile.com/api/retrigger?id=78360005"><picture><source media="(prefers-color-scheme: dark)" srcset="https://greptile-static-assets.s3.amazonaws.com/badges/RetriggerDark.svg?v=2"><source media="(prefers-color-scheme: light)" srcset="https://greptile-static-assets.s3.amazonaws.com/badges/Retrigger.svg?v=2"><img alt="Retrigger" src="https://greptile-static-assets.s3.amazonaws.com/badges/Retrigger.svg?v=2" align="right"></picture></a>Confidence Score: 4/5</h2> <!-- greptile-risk --> The unresolved settings-column mismatch blocks merging safely for databases built from the supplied migrations; the duplicate-user validation and older-history formatting concerns are non-blocking. <h3>Summary</h3> This PR switches the dashboard to the bot’s pinned V7 contract and Prisma ORM 8. - The dashboard builds its database client from the bot’s V7 contract. - Dashboard settings map to the bot’s normalized tables. - The dashboard’s settings pages follow the bot’s V7 sections. - Dashboard audit writes share the bot’s lock for the audit chain. - Log pages and API queries use the ORM 8 database contract. - Settings controls use the V7 keys and show saved values. - Locale text and schemas match the V7 dashboard settings. <!-- greptile_confidence_score:4 --> <sub>Reviews (15) · Last reviewed commit: ["feat(dashboard): name the sections Auto ..."](4c434a3) · [Reviewed by Greptile](https://www.greptile.com/?utm_source=greptile_expert&utm_medium=github&utm_campaign=code_reviews&utm_content=wolfstar-project/wolfstar.rocks)</sub> <!-- /greptile_comment -->
RedStar071
added a commit
that referenced
this pull request
Oct 13, 2026
### 🔗 Linked issue Part of the stack superseding #422. Depends on #457. **Stack:** #451 foundation ← #452 header/footer ← #453 marketing ← #454 `/app` dashboard ← #455 V7 contract + ORM 8 only ← #457 auto-moderation rules ← #461 deprecate `/profile` ### 🧭 Context Since #454 the dashboard lists the servers you manage itself, so `/profile` was a second server list with a different layout. It was also the only place to change theme, language and reduced motion, which is why it could not simply be deleted: guests use those controls too, and `/app` is sign-in only. ### 📚 Description `/profile` and `/account` now answer with a 301 to `/app`: ``` /profile -> 301 http://localhost:5678/app /account -> 301 http://localhost:5678/app ``` The preferences moved into a dialog opened from the header's Settings button (guests) and from the user menus (signed in), so nobody needs a page for them. Sign-in lands on `/app`, which shows the server picker when no server is selected. ###⚠️ What this removes - **Search, sort and the "manageable only" toggle on the server list.** The picker in `/app` shows every server you can manage, sorted with the ones WolfStar is in first. If someone manages enough servers to need search, it should be added to the picker rather than kept on a second page. - **Servers you cannot manage** are no longer listed anywhere. `/profile` showed them when the toggle was off. - **The profile header**: avatar, username and the copy-user-id button. - `/profile` was indexable and had an OG image. It is now `robots: false` and out of the sitemap. I used 301 because the page is not coming back; say so if you would rather keep it temporary while the stack is in review. > 🤖 AI disclosure: [Wolfstar Agent Kit](https://github.com/wolfstar-project/wolfstar-agent-kit) modified this description. [My AI open-source policy](https://harlanzw.com/blog/ai-in-open-source). <!-- greptile_comment --> <!-- greptile_summary --> <h2><a href="https://app.greptile.com/api/retrigger?id=78706812"><picture><source media="(prefers-color-scheme: dark)" srcset="https://greptile-static-assets.s3.amazonaws.com/badges/RetriggerDark.svg?v=2"><source media="(prefers-color-scheme: light)" srcset="https://greptile-static-assets.s3.amazonaws.com/badges/Retrigger.svg?v=2"><img alt="Retrigger" src="https://greptile-static-assets.s3.amazonaws.com/badges/Retrigger.svg?v=2" align="right"></picture></a>Confidence Score: 4/5</h2> <!-- greptile-risk --> The settings-dialog copy requirements must be satisfied before merging; clipped activity descriptions, stale dates, and incorrect context-menu labels are non-blocking usability concerns. <h2>T-Rex evidence</h2> **[▶ Recording of the check](https://app.greptile.com/trex/artifacts/2e06d5fd-c8bc-44c9-a9bf-ba955fb11453)** - Chromium renders long activity entries at two desktop panel widths and scrolls the narrow table fully right, showing that the original descriptions wrap and remain readable. **[▶ Recording of the check](https://app.greptile.com/trex/artifacts/43922602-d54d-4492-a1a9-9e6c011d9f2e)** - Chromium renders the same entries and exercises scrolling and hover, showing that long descriptions remain clipped without a full-text disclosure. **[Original activity table at maximum horizontal scroll](https://app.greptile.com/trex/artifacts/72ca460a-a115-4bdf-9c7a-7041eda5188e)** - The pre-conversion table is captured at the narrow desktop width after scrolling fully right, showing wrapped action descriptions. **[PR461 activity table at maximum horizontal scroll](https://app.greptile.com/trex/artifacts/5efec520-4094-4d09-b7f3-1ba142c372a2)** - The PR461 table is captured at the same width and scroll position, showing that horizontal scrolling does not recover clipped action text. **[Command output from the check](https://app.greptile.com/trex/artifacts/6087bbe7-5ff0-4aaa-b7bc-f155a36e9878)** - The successful command captured measured cell widths, computed styles, scroll limits, hover results, and checkout checks, confirming the same clipping in both PR heads. **[Evidence from the check](https://app.greptile.com/trex/artifacts/3067230c-b098-4609-9918-8e7d0bac829f)** - The script loads component source directly from local commits and captures runtime measurements and recordings; its final declaration-generation option adjustment was not rerun. **[Evidence from the check](https://app.greptile.com/trex/artifacts/a7b38dd3-b67f-48d5-a6fd-61af2520ae41)** - The harness mounts the selected commit’s activity component with real Nuxt UI components and application CSS, exercising the desktop rendering path. **[Evidence from the check](https://app.greptile.com/trex/artifacts/17ed5882-d56e-49c9-9e6b-8800cb2ba214)** - The fixtures supply long resolved role and channel names plus a short control entry, reproducing clipping without database or authentication access. **[Evidence from the check](https://app.greptile.com/trex/artifacts/1768f28b-a235-43ec-99ed-cf3800440a60)** - The shell command launches the Chromium validation with the installed browser cache and records command, working directory, and exit code in the execution log. **[▶ Recording of the check](https://app.greptile.com/trex/artifacts/2e06d5fd-c8bc-44c9-a9bf-ba955fb11453)** - Chromium renders long activity entries at two desktop panel widths and scrolls the narrow table fully right, showing that the original descriptions wrap and remain readable. **[▶ Recording of the check](https://app.greptile.com/trex/artifacts/43922602-d54d-4492-a1a9-9e6c011d9f2e)** - Chromium renders the same entries and exercises scrolling and hover, showing that long descriptions remain clipped without a full-text disclosure. **[Original activity table at maximum horizontal scroll](https://app.greptile.com/trex/artifacts/72ca460a-a115-4bdf-9c7a-7041eda5188e)** - The pre-conversion table is captured at the narrow desktop width after scrolling fully right, showing wrapped action descriptions. **[PR461 activity table at maximum horizontal scroll](https://app.greptile.com/trex/artifacts/5efec520-4094-4d09-b7f3-1ba142c372a2)** - The PR461 table is captured at the same width and scroll position, showing that horizontal scrolling does not recover clipped action text. **[Command output from the check](https://app.greptile.com/trex/artifacts/6087bbe7-5ff0-4aaa-b7bc-f155a36e9878)** - The successful command captured measured cell widths, computed styles, scroll limits, hover results, and checkout checks, confirming the same clipping in both PR heads. **[Evidence from the check](https://app.greptile.com/trex/artifacts/3067230c-b098-4609-9918-8e7d0bac829f)** - The script loads component source directly from local commits and captures runtime measurements and recordings; its final declaration-generation option adjustment was not rerun. **[Evidence from the check](https://app.greptile.com/trex/artifacts/a7b38dd3-b67f-48d5-a6fd-61af2520ae41)** - The harness mounts the selected commit’s activity component with real Nuxt UI components and application CSS, exercising the desktop rendering path. **[Evidence from the check](https://app.greptile.com/trex/artifacts/17ed5882-d56e-49c9-9e6b-8800cb2ba214)** - The fixtures supply long resolved role and channel names plus a short control entry, reproducing clipping without database or authentication access. **[Evidence from the check](https://app.greptile.com/trex/artifacts/1768f28b-a235-43ec-99ed-cf3800440a60)** - The shell command launches the Chromium validation with the installed browser cache and records command, working directory, and exit code in the execution log. <a href="https://app.greptile.com/trex/runs/31709122/artifacts?artifact=2e06d5fd-c8bc-44c9-a9bf-ba955fb11453"><picture><source media="(prefers-color-scheme: dark)" srcset="https://greptile-static-assets.s3.amazonaws.com/badges/ViewArtifactsDark.svg?v=4"><source media="(prefers-color-scheme: light)" srcset="https://greptile-static-assets.s3.amazonaws.com/badges/ViewArtifacts.svg?v=4"><img alt="View artifacts" src="https://greptile-static-assets.s3.amazonaws.com/badges/ViewArtifacts.svg?v=4"></picture></a> <h3>Summary</h3> The PR redirects `/profile` and `/account` to `/app` and moves browser preferences into a shared settings dialog. - Old profile links lead to the dashboard, while settings open in a dialog. - The dashboard picker lists manageable servers and reports load errors. - Dashboard logs use a shared toolbar, responsive rows, and tab counts. - Guild settings and selection controls are updated for the dashboard. <!-- greptile_confidence_score:4 --> <sub>Reviews (14) · Last reviewed commit: ["fix(dashboard): narrow the pager item be..."](aaaf549) · [Reviewed by Greptile](https://www.greptile.com/?utm_source=greptile_expert&utm_medium=github&utm_campaign=code_reviews&utm_content=wolfstar-project/wolfstar.rocks)</sub> <!-- /greptile_comment -->
RedStar071
added a commit
that referenced
this pull request
Oct 13, 2026
### 🔗 Linked issue Part of the stack superseding #422. Depends on #461. **Stack:** #451 foundation ← #452 header/footer ← #453 marketing ← #454 `/app` dashboard ← #455 V7 contract + ORM 8 only ← #457 auto-moderation rules ← #461 deprecate `/profile` ← this PR ### 🧭 Context `/commands` was the last public page still on the pre-redesign look: nested Nuxt UI accordions, heavy borders, and a heading that the layout's top glow painted over. This rebuilds it on the Claude Design mockup for the commands page. ### 📚 Description - **Layout.** Centred heading and subtitle, a 52px search field next to the Refresh button, and a single 900px panel holding the category cards. - **Categories.** Each card shows its name and a command count. One category is open at a time and Moderation opens first when the bot reports it. While searching, every category with a match is expanded. - **Commands.** Each command is its own collapsible row: mono name, truncated description, then usage, extended help, explained usage, possible formats, examples, reminder and pill badges for permission level, server-only and guarded commands. - **Search.** The result count is now visible under the field instead of screen-reader only. Matching still goes through Fuse on name, description and category. - **Copy.** Every string on the page moved to `marketing.commands.*`; the page was hardcoded English before. Other locales get empty placeholders, as usual. - **Components.** `CommandSubCategory` is gone. `CommandCategory` is one card, `CommandItem` is one command row, `CommandBase` renders the details and `CommandChips` the badges. ### 🧪 Verification - `test/nuxt/pages/commands.spec.ts` covers the default open category, single-open behaviour, search expansion and count, the no-match state and the retry state. - Checked in a local dev server with sample commands in dark, light and at 390px wide. - Lint, typecheck, knip, i18n check/report, the colour guardrail tests and `build:test` pass locally. ###⚠️ Deviations from the mockup - The mockup's Refresh resets the page state. Here it keeps refetching the command list from the bot, as before. - The mockup shows a note saying details are "pulled live from the bot" on commands without help. Details are already live here, so that note reads "This command takes no arguments and has no extra notes." - Surfaces use the app's own tokens (`base-100`, `base-content` tints, `--home-*`) rather than the mockup's hex values, so the cards sit on the page colour instead of one step lighter in the dark theme. - The loading skeleton, the "no commands available" retry state, the Possible Formats and Reminder blocks and the "Cannot be disabled" badge are not in the mockup. They are kept and restyled to match. > 🤖 AI disclosure: [Wolfstar Agent Kit](https://github.com/wolfstar-project/wolfstar-agent-kit) modified this description. [My AI open-source policy](https://harlanzw.com/blog/ai-in-open-source). <!-- greptile_comment --> <!-- greptile_summary --> <h2><a href="https://app.greptile.com/api/retrigger?id=78748592"><picture><source media="(prefers-color-scheme: dark)" srcset="https://greptile-static-assets.s3.amazonaws.com/badges/RetriggerDark.svg?v=2"><source media="(prefers-color-scheme: light)" srcset="https://greptile-static-assets.s3.amazonaws.com/badges/Retrigger.svg?v=2"><img alt="Retrigger" src="https://greptile-static-assets.s3.amazonaws.com/badges/Retrigger.svg?v=2" align="right"></picture></a>Confidence Score: 4/5</h2> <!-- greptile-risk --> The remaining concerns are explicit repository design and copy requirements; both must be satisfied before merging. <h3>Summary</h3> This PR rebuilds `/commands` with category cards, expandable command rows, visible search counts, and translated labels. - Command categories open one at a time and expand to show search matches. - Each command opens to show its help and badges. - The commands page gets translation keys for its labels and help text. - Czech plural forms and English fallback text use the right rules. The design and copy requirements must be satisfied before merging. <!-- greptile_confidence_score:4 --> <sub>Reviews (15) · Last reviewed commit: ["fix(ui): derive command details from the..."](a98bf3a) · [Reviewed by Greptile](https://www.greptile.com/?utm_source=greptile_expert&utm_medium=github&utm_campaign=code_reviews&utm_content=wolfstar-project/wolfstar.rocks)</sub> <!-- /greptile_comment -->
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
![https://greptile-static-assets.s3.amazonaws.com/badges/RetriggerDark.svg?v=2"><source](https://greptile-static-assets.s3.amazonaws.com/badges/RetriggerDark.svg?v=2"><source){kind=link}
![https://greptile-static-assets.s3.amazonaws.com/badges/Retrigger.svg?v=2"><img](https://greptile-static-assets.s3.amazonaws.com/badges/Retrigger.svg?v=2"><img){kind=link}
![https://greptile-static-assets.s3.amazonaws.com/badges/ViewArtifactsDark.svg?v=4"><source](https://greptile-static-assets.s3.amazonaws.com/badges/ViewArtifactsDark.svg?v=4"><source){kind=link}
![https://greptile-static-assets.s3.amazonaws.com/badges/ViewArtifacts.svg?v=4"><img](https://greptile-static-assets.s3.amazonaws.com/badges/ViewArtifacts.svg?v=4"><img){kind=link}
![https://greptile-static-assets.s3.amazonaws.com/badges/ViewArtifacts.svg?v=4"></picture></a](https://greptile-static-assets.s3.amazonaws.com/badges/ViewArtifacts.svg?v=4"></picture></a){kind=link}
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔗 Linked issue
Part of the stack superseding #422. Depends on #455.
Stack: #451 foundation ← #452 header/footer ← #453 marketing ← #454
/appdashboard ← #455 V7 contract + ORM 8 only ← #457 auto-moderation rules🧭 Context
V7 stores auto-moderation as one row per rule (type, thresholds, actions, JSON options). #455 removed the seven V6 filter pages because their columns no longer exist; without this layer the dashboard cannot configure auto-moderation at all.
📚 Description
A rule list and editor in the Auto-moderation section, backed by
GET/POST /api/guilds/:guild/automod/rulesandPATCH/DELETE …/rules/:rule. Rules are rows rather than settings keys, so they skip the staged-changes bar and save when confirmed.Request bodies go through the bot's own validator, ported with its limits and its
confusablesword normalization, so a rule written here is one the bot's API would accept. The editor covers all 21 rule types from the type's default options, plus thresholds, soft actions, punishment, escalation steps and exemptions.GuildAutoModerationRule_guild_id_name_key, whose name I took from the bot's code. The contract does not declare it, so I could not confirm it exists.Do not merge until the two outstanding issues are fixed: a successful API save can leave a Timeout that the bot skips, and saving an older editor can silently undo another admin’s saved configuration.
Summary
Adds dashboard controls to create, edit, enable, and delete auto-moderation rules.
Reviews (14) · Last reviewed commit: "fix(dashboard): lock rule writes across ..." · Reviewed by Greptile