Repository navigation
refactor(database): run on the bot's V7 contract with Prisma ORM 8 only - #455
Merged
Merged
Conversation
RedStar071
added this pull request to stack #456
October 10, 2026 12:41
This was referenced Oct 10, 2026
Closed
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Merging this PR will not alter performance
|
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## refactor/v3-dashboard #455 +/- ##
========================================================
Coverage ? 51.20%
========================================================
Files ? 338
Lines ? 6867
Branches ? 1398
========================================================
Hits ? 3516
Misses ? 2301
Partials ? 1050
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
RedStar071
changed the title
RedStar071
changed the title
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
|
RedStar071
marked this pull request as ready for review
October 10, 2026 15:09
|
3 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 rough edges worth a look inline.
Reviewed changes
Reviewed the full PR (4 commits, 170 files) with a focus on the server data layer, since that is where the behavioral risk sits.
- ORM 8 client and contract —
server/database/prisma.tsandcontract.prismareplace Prisma 7; the lazyurl: undefinedhandling for prerender is sound. - Settings storage —
columns.ts,storage.ts,functions.ts: the table chain creation order,upserthandling and the always-fresh read inwriteSettingsTransactionlook correct. - PATCH validation —
validation.tsplussettings.patch.ts: unknown keys and wrong types now answer 400, and the transaction opens only after validation. - Audit drain — the advisory lock key matches the bot's
0x4155444C, and the dedupe-by-hash path replaces the P2002/P2034 handling. - Log routes — the three routes moved to ORM 8 collections, with LIKE-wildcard escaping and UTC normalization of
TimestampStringvalues. - Dashboard sections — filter pages and Events removed, new V7 sections added via
useSettingsForm.
claude-sonnet-5-5 ｜ 𝕏
Contributor
There was a problem hiding this comment.
ℹ️ No critical issues — one minor suggestion on the submodule bootstrap.
Reviewed changes
Reviewed the single commit since the prior pullfrog review (618b3fc), which replaces the copied contract file with a git submodule of the bot's repository.
- Contract via submodule —
vendor/wolfstar(bot repo,V7, pinnedea661ba) replacesserver/database/contract.prisma, andprisma.config.tsnow readsvendor/wolfstar/projects/database/src/contract.prisma. - Bootstrap script —
scripts/ensure-contract.tsruns inpostinstallandprisma:generate, initializing the submodule shallowly when the contract file is missing so CI and Netlify need nosubmodules: true. - Contract pin test —
test/unit/server/database/contract-pin.spec.tscompares the emittedstorageHashwith the bot'smigrations/app/refs/db.json. - Tooling exclusions —
vendor/is excluded from oxlint, oxfmt, knip and Tailwind's@sourcescan, and Renovate getsgit-submodulesenabled. - Docs —
AGENTS.mdandREADME.mddescribe the submodule workflow; theprisma8:inferscript is removed.
The three open threads from the prior review (snowflake range, from/to validation, retired section slugs) are untouched by this commit and remain open.
claude-sonnet-5-5 ｜ 𝕏
RedStar071
force-pushed
the
refactor/v3-dashboard
branch
from
October 11, 2026 14:14
05edf71 to
41d0540
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-dashboard
branch
from
October 11, 2026 20:12
41d0540 to
129009d
Compare
Contributor
There was a problem hiding this comment.
✅ No new issues found in the new commit. Three earlier Pullfrog threads (snowflake range,
from/tovalidation, retired section slugs) and the stale-submodule thread onscripts/ensure-contract.tsare untouched by it and remain open.
Reviewed changes
Reviewed the single commit since the prior pullfrog review (fd9a16ec), a presentation-only restyle of the settings sections. The checkout's incremental range-diff also carried rebase noise from the base branch, which I disregarded in favour of the commit's own patch.
- Console card layout —
Modules.vue,Channels.vue,Roles.vue,Moderation.vueandReports.vueswapGuildSettingsSectionforDashboardPageHeaderplusconsole-cardsections. TheLOGGING_GROUPSregexes cover every key inConfigurableLoggingChannelsandConfigurableLogToggles, so no setting drops out of the page. - Row layout for selects —
SelectOneandSelectManygainlayout="row"andemptyLabel, rendering a labelled inlineUSelect/USelectMenuwithuseId()-linked label and description.SelectChanneland the other wrappers pass both props through as fallthrough attrs. - Commands accordion —
DisabledCommands.vuebecomes category rows with command tiles and an on/offrole="switch"pill. - Modules gating — the Configure button is disabled with an "Enable first" label while a module is off.
- Nav —
dashboard-nav.tsdrops the retired filter entries in favour ofautomod,channels,commands,rolesandreports, withmoduleKeywired to the sidebar state. - Tests and locales —
Sidebar,ModulesandDisabledCommandsspecs follow the new markup, and the new keys (routed_count,enable_first,groups.*and others) are added as empty placeholders in the non-English locale files.
claude-sonnet-5-5 ｜ 𝕏
RedStar071
force-pushed
the
refactor/v3-database
branch
from
October 13, 2026 15:28
4020cb8 to
369d391
Compare
Comment on lines
+125
to
128
| /** V6 settings the V7 schema has no column for, kept so old rows stay readable. */ | ||
| const LEGACY_AUDIT_FIELD_METADATA: Readonly<Record<string, AuditFieldMetadata>> = { | ||
| prefix: { label: "Prefix", type: "string", array: false }, | ||
| language: { label: "Language", type: "language", array: false }, | ||
| disabledCommands: { label: "Disabled Commands", type: "command-name", array: true }, | ||
| disabledCommandsChannels: { | ||
| label: "Disabled Commands Channels", | ||
| type: "channel", | ||
| array: true, | ||
| }, | ||
| }; |
Contributor
There was a problem hiding this comment.
The V7 registry drops labels and value types for older audit fields that have no replacement. Existing rows with messagesModerationDm now show Messages Moderation Dm: false → true instead of Message User: Disabled → Enabled. Older channel-list fields also fall back to raw IDs.
This is non-blocking, but makes saved history harder to read. Keep these fields in LEGACY_AUDIT_FIELD_METADATA; removing a setting should not remove its history formatting.
Knowledge Base Used: Guild activity and moderation logs
Artifacts
- The existing script loads exact commit sources and renders the historical audit row, preserving the executed reproduction.
- The existing wrapper records the command, working directory, captured output, and final exit code, preserving the invocation.
- The existing setup script selects system FFmpeg for browser recording, preserving the prerequisite command.
- The captured setup output includes exit code zero and the FFmpeg version, showing recording prerequisites were resolved.
- The captured initial failure identifies the missing expected FFmpeg executable, preserving the earlier setup blocker.
- The finalized command output records exit code zero and successful rendered assertions for all five commits, confirming execution completed.
- The finalized export contains 30 retrieved source records spanning all five variants, preserving the actual repository inputs.
- The completed baseline recording shows readable boolean formatting and typed channel values, establishing the before behavior.
Baseline activity and formatter poster
- The existing baseline poster captures Message User with Disabled to Enabled and resolved channel names, showing the original formatting.
- The completed PR455 recording shows the same saved row with humanized keys, raw booleans, and raw IDs, demonstrating the regression.
PR455 activity and formatter poster
- The existing PR455 poster captures the incorrect label and raw values despite known channels, showing missing legacy metadata.
- The completed PR457 recording shows the same incorrect formatting, confirming this higher head does not repair it.
PR457 activity and formatter poster
- The existing PR457 poster captures the same label and value regression, preserving the higher-head observation.
- The completed PR461 recording shows the same incorrect formatting, confirming this higher head does not repair it.
PR461 activity and formatter poster
- The existing PR461 poster captures the same label and value regression, preserving the higher-head observation.
- The finalized PR462 recording shows the same incorrect formatting, confirming this higher head does not repair it.
PR462 activity and formatter poster
- The finalized PR462 poster captures the same label and value regression, completing the existing capture set.
Prompt To Fix With AI
This is a comment left during a code review.
Path: shared/utils/audit-field-metadata.ts
Line: 125-128
Comment:
**Older history loses readable labels**
The V7 registry drops labels and value types for older audit fields that have no replacement. Existing rows with `messagesModerationDm` now show `Messages Moderation Dm: false → true` instead of `Message User: Disabled → Enabled`. Older channel-list fields also fall back to raw IDs.
This is non-blocking, but makes saved history harder to read. Keep these fields in `LEGACY_AUDIT_FIELD_METADATA`; removing a setting should not remove its history formatting.
**Knowledge Base Used:** [Guild activity and moderation logs](https://app.greptile.com/wolfstar-project/-/custom-context/knowledge-base/wolfstar-project/wolfstar.rocks/-/docs/guild-activity-and-moderation-logs.md)
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
… ORM 8 - `schema.prisma` mirrors the bot's V7 contract: `Modules` becomes the parent of the per-feature settings tables, permission nodes are restored, and mention spam, configurable roles, language, disabled commands, public/unique roles and the moderator reason come back. Migration `20260920000000_v7_contract_and_modules` creates the new shape, seeds a `Modules` row per guild and refuses to archive populated V6 tables before the bot has migrated them. - Prisma ORM 8 (`@prisma/orm-postgres`) runs beside ORM 7, per the upgrade guide: `prisma.config.ts` drives ORM 8 against `server/database/prisma8/contract.prisma` (every model `@@control(external)`, the bot owns the migrations), while the ORM 7 scripts move to `prisma7.config.ts` and the `prisma7` CLI. The three guild-log routes query through `db.orm`; `postgres-drain.ts` stays on ORM 7 because it needs `Serializable` isolation and a serialization retry to keep the audit hash chain from forking. - Log route hardening: the command log returns a JSON-safe DTO (`CommandLogEntry`) so bigints never reach the wire; free-text search escapes `%`, `_` and `\` (`containsPattern()`) so `q=_` no longer matches everything; `timestamp(3)` text is read as UTC through `timestampStringToUtcIso()`; moderation actions map V7's enum to the dashboard's numeric filter codes (`MODERATION_ACTION_CODE`). - `scripts/audit-verify.ts` reads through ORM 8 and rebuilds the structural row the verifier hashes. Known state: `pnpm typecheck` is red on this layer (356 errors). The V7 schema landed but the code that reads `GuildData` has not been ported: `Guild` no longer holds the settings, so `AdderManager.ts`, `SettingsContext.ts`, `PermissionNodeManager.ts`, the `settings/filter/*` components and the guild-settings specs all fail to compile. The port needs the bot to decide how one settings view composes across the new tables and how a PATCH routes to the right table, so it is deliberately left for a follow-up and this layer stays a draft. Co-authored-by: Claude <noreply@anthropic.com>
…th ORM 8 only Aligns the database layer with the bot's V7 branch (wolfstar-project/wolfstar#208), whose `projects/database` package is Prisma ORM 8 only. - Prisma 7 is gone: `schema.prisma`, `prisma7.config.ts`, `@prisma/client`, `@prisma/adapter-pg`, `@prisma/prisma7`, `prisma-json-types-generator`, the generated-client test stub and every `prisma:migrate:*` / `push` / `seed` / `studio` script. `prisma:generate` now runs `prisma contract emit`, so Netlify and CI keep calling the same task. - `server/database/contract.prisma` is a verbatim copy of the bot's contract, emitted to the gitignored `server/database/generated/prisma/`. It produces the storage hash the bot's `migrations/app/refs/db.json` records (c43f2589…), so both services describe the same database. Versions match the bot's: `@prisma/orm-postgres` 8.0.0-rc.13, `prisma` 8.0.0-rc.19, and `prisma-orm-extension-typed-json` rc.5 with the bot's patch and overrides. - The contract replaced the per-filter automod tables with one `GuildAutoModerationRule` table and added reports, auto-delete/purge and case data, so the committed `prisma8/` artefacts and the V6-shaped `GuildData` are replaced by the bot's own model: a flat `GuildData` whose keys map to columns of the normalized tables (`columns.ts`), read and written in one transaction (`storage.ts`). This is the decision the earlier commit on this branch was waiting on. - The audit drain moves to the ORM 8 client. Appends are serialized by the transaction-level advisory lock the bot's `AuditLogManager` takes too, instead of `Serializable` isolation plus a retry loop, which the ORM 8 façade does not expose. - Settings PATCH bodies go through `parseSettingsChanges()`: unknown keys and values of the wrong type are refused with a 400 instead of reaching the tables. - The client is constructed with `url: undefined` when `DATABASE_URL` is unset: rc.13 rejects an empty string at construction, which broke prerendering at build time. Co-authored-by: Claude <noreply@anthropic.com>
…model
The V7 contract has no command prefix, no `selfmod*` filters and no
`events*` / `messagesModeration*` settings, and renames most of what is
left (`channelsLogsMemberAdd` -> `logsMemberAdd`, …). The settings UI
follows the bot's flat `GuildData` keys.
- Sections: Home (language), Modules, Auto-moderation, Moderation,
Channels, Roles, Commands, Reports, Logs. The seven per-filter pages
and the Events page are removed; their V6 slugs from old
`/guilds/:id/manage/*` links resolve to the section that holds those
settings now. Auto-moderation rules, which replace the filter pages,
come in the next layer.
- The Modules section and the Home summary read the five flags of the
V7 `Modules` table instead of the `selfmod*Enabled` flags.
- `useSettingsForm({ one, many, toggles })` builds the state, the schema
and the change mapping of a section from the kinds of its keys, so
Channels, Roles, Moderation, Auto-moderation, Reports and Modules no
longer hand-write them. The entry types only accept keys of the right
value type. Initial roles are lists in V7, and `rolesInitialHumans` /
`rolesInitialRobots` are editable.
- Channels now shows the log channels that are already saved: the form
used to start empty whatever the settings held.
- `GuildSettingsForm` only removes its own reverted keys from the staged
draft instead of clearing the whole draft, so a section can hold two
forms (Commands: disabled channels and disabled commands).
- Audit rows written before the move keep their V6 keys;
`getAuditFieldMetadata()` aliases the renamed ones so the activity feed
still labels them.
- Locales: entries are re-keyed to the V7 names. A translation is kept
only where its English source is unchanged; everything else is an
empty placeholder.
Co-authored-by: Claude <noreply@anthropic.com>
The knip job installs and runs without a generate step, so the imports of the gitignored `server/database/generated/prisma/contract` did not resolve there. Emitting is offline and takes well under a second, so it runs on every install instead of being a step each job has to remember. Co-authored-by: Claude <noreply@anthropic.com>
…submodule The bot changes the contract and migrates the database first, so a copy of `contract.prisma` in this repository can only ever lag behind it. `vendor/wolfstar` is now a git submodule of the bot's repository (tracking `V7`), and `prisma.config.ts` reads the contract from it. - Moving to a newer database state is a submodule bump, which Renovate can open as a PR (`git-submodules` enabled). - `scripts/ensure-contract.ts` runs before every emit and initializes the submodule when it is not checked out, so plain clones and CI checkouts without `submodules: true` keep working. - `contract-pin.spec.ts` fails when the emitted storage hash is not the one the pinned bot commit records for its migrations. - The submodule is excluded from lint, format, knip and Tailwind's source scan. `prisma8:infer` is removed: this app never infers or edits the contract. Co-authored-by: Claude <noreply@anthropic.com>
The browser test job runs in a container that checks the repository out as another user, so git refused the submodule update with "dubious ownership". The script now trusts the repository and the submodule directory for that one command. Co-authored-by: Claude <noreply@anthropic.com>
Modules become cards with an icon tile and a switch, channel and role settings are grouped by what they log or assign, each setting is a row with its select beside it, and commands are an accordion of tiles with a state pill. The select components gain a row layout for this.
Auto-Delete and Auto-Purge get sidebar entries, module cards and a placeholder page marked "Coming soon": the bot has both, the dashboard has no routes for them. The overview follows the redesign's five counts, with AutoMod hits and open reports shown as dashes until something counts them, and the time zone field is shown disabled.
They follow the five counts of the redesign as a sixth and seventh card.
The online count and the server cards' action labels used the success and primary colours as text on a surface where they fall under 4.5:1.
… saved legacy sections
RedStar071
force-pushed
the
refactor/v3-database
branch
from
October 13, 2026 17:19
369d391 to
4c434a3
Compare
RedStar071
force-pushed
the
refactor/v3-dashboard
branch
from
October 13, 2026 17:19
7ef6177 to
69b75cd
Compare
RedStar071
removed this pull request from stack #456
October 13, 2026 18:13
RedStar071
added a commit
that referenced
this pull request
Oct 13, 2026
### 🔗 Linked issue Part of the stack superseding #422. Depends on #451. **Stack:** #451 foundation ← #452 header/footer ← #453 marketing ← #454 `/app` dashboard ← #455 V7 schema + Prisma ORM 8 (draft) ### 🧭 Context The header and footer had drifted from the WolfStar Web Redesign canvas. ### 📚 Description The brand lockup is unchanged apart from the Staryl wordmark's size (WolfStar keeps its logo mark, Staryl stays text only), the header is one solid surface matching the page, and the desktop nav pill gets a border, a 36px row and an open state. Features entries carry an icon and a description, Applications entries their avatar and a tagline, rendered through `UNavigationMenu` content slots. Those rows are plain links, so the panel closes itself on select or it would stay over an in-page anchor target. Desktop and mobile menus are built from the same groups in `useHeader()`. The footer badge leads with a deploy status dot and the build info is a mono status pill. Two new `nav.*_description` keys, empty in every non-English locale. > 🤖 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=78359963"><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: 5/5</h2> <!-- greptile-impact-verdict --> No merge-blocking issues are identified in the reviewed changes. <h3>Summary</h3> The PR updates the shared header and footer to match the redesign. - The header matches the redesign while keeping both app names distinct. - Desktop menus show what each feature and application offers. - The footer shows deployment and build details as compact status displays. No actionable issues remain in this review. Tests and browser checks were not run. <!-- greptile_confidence_score:5 --> <sub>Reviews (6) · Last reviewed commit: ["fix(ui): keep focus on the header menu a..."](342d868) · [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
…showcases (#453) ### 🔗 Linked issue Part of the stack superseding #422. Depends on #452. **Stack:** #451 foundation ← #452 header/footer ← #453 marketing ← #454 `/app` dashboard ← #455 V7 schema + Prisma ORM 8 (draft) ### 🧭 Context Marketing sections on `/` and `/staryl` follow the canvas. On top of the visual port from #422 this layer defers hydration of the heavy demos, which the original PR did not do. ### 📚 Description Hero briefs become cards, product proof moves to a three-card grid with an icon per step, CTAs become a centred bordered panel with a faded brand watermark. `OtherApps` renders siblings as `SurfaceCard`s and the WolfStar home shows the dashboard section before the commands demo. The three showcases below the fold (`WolfstarModerationShowcase`, `WolfstarCommandsShowcase`, `StarylCommandsShowcase`) are 600 to 1300 lines each and were already `Lazy` chunks. They now use `hydrate-on-visible`, so the SSR markup is unchanged but their JavaScript stops competing with the hero until they scroll into view. Not measured yet; happy to run Lighthouse before/after on the preview if wanted. > 🤖 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=78359978"><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: 5/5</h2> <!-- greptile-impact-verdict --> No outstanding findings block merging this PR. The approved card layout remains a maintainer-owned design-guide decision. <h3>Summary</h3> Updates the marketing pages with card-based hero briefs, proof sections, and centered closing panels. - Product proof appears as three cards with an icon for each step. - The closing calls to action sit in centered panels with faint brand marks. - Showcase demos wait to hydrate until they are near the viewport. - Hero briefs appear as filled cards with primary-color labels. - Other apps appear as cards with their details and actions. <!-- greptile_confidence_score:5 --> <sub>Reviews (6) · Last reviewed commit: ["fix(ui): preload lazy showcases early an..."](1823c81) · [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
…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
### 🔗 Linked issue Part of the stack superseding #422. Depends on #455. **Stack:** #451 foundation ← #452 header/footer ← #453 marketing ← #454 `/app` dashboard ← #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/rules` and `PATCH/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 `confusables` word 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. ###⚠️ Open questions - **The bot will not see a rule until its cache drops.** It caches rules per process and invalidates on its own shard messages. The bot already exposes these same routes behind its own auth; proxying to them would fix this, but the dashboard cannot authenticate against the bot's API today. I wrote to the database directly, as the settings routes do. If that is not acceptable, hold this PR. - I have not run this against a live V7 database. The service, validator and components are covered with mocked storage only. - Name uniqueness across processes relies on the index `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. > 🤖 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=78384596"><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: 3/5</h2> <!-- greptile-risk --> 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. <h3>Summary</h3> Adds dashboard controls to create, edit, enable, and delete auto-moderation rules. - Dashboard admins can create and manage auto-moderation rules. - Guild admins can read and change auto-moderation rules through the API. <!-- greptile_confidence_score:3 --> <sub>Reviews (14) · Last reviewed commit: ["fix(dashboard): lock rule writes across ..."](67278d5) · [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 #454. Follows the bot's V7 branch, wolfstar-project/wolfstar#208.
Stack: #451 foundation ← #452 header/footer ← #453 marketing ← #454
/appdashboard ← #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 oneGuildAutoModerationRulerow 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 everyprisma:migrate:*script are removed.prisma:generatenow runsprisma contract emit, so Netlify and CI call the same task as before.The contract comes from the bot's repository.
vendor/wolfstaris a git submodule of wolfstar-project/wolfstar trackingV7, andprisma.config.tsreadsprojects/database/src/contract.prismafrom 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-postgresrc.13,prismarc.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:The artefacts are emitted into the gitignored
server/database/generated/prisma/onpostinstall, which also initializes the submodule when a checkout left it empty, so no workflow needssubmodules: true.Settings model.
GuildDatais the bot's flat object;columns.tsmaps each key to its table and column andstorage.tsreads 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, noselfmod*filters and noevents*/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
AuditLogManagertakes.Two things I found on the way and fixed here:
url: ""when the client is constructed, which broke prerendering at build time whereDATABASE_URLis unset. The client getsundefinedinstead 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.
vendor/wolfstar/projects/database/migrations/. I keptserver/database/migrations/because20260920000000_v7_contract_and_modulesis 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.columns.ts/storage.tsimport 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. Publishingwolfstar-databaseas a package would remove the ports.shared/audit/envelope.tshere,AuditLogEnvelope.tsin the bot), sopnpm audit:verifywill flag rows the bot wrote. Not introduced here, not solved here.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.
Summary
This PR switches the dashboard to the bot’s pinned V7 contract and Prisma ORM 8.
Reviews (15) · Last reviewed commit: "feat(dashboard): name the sections Auto ..." · Reviewed by Greptile