Repository navigation
feat(dashboard): replace /guilds/:id/manage with a single /app page - #454
Merged
Merged
Conversation
This was referenced Oct 10, 2026
Closed
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 12:44
|
3 findings · reviewed 🟠
|
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## refactor/v3-marketing #454 +/- ##
=========================================================
+ Coverage 48.43% 50.43% +2.00%
=========================================================
Files 326 344 +18
Lines 7041 7392 +351
Branches 1399 1470 +71
=========================================================
+ Hits 3410 3728 +318
- Misses 2543 2546 +3
- Partials 1088 1118 +30
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
Merging this PR will not alter performance
|
![pullfrog[bot]](https://avatars.githubusercontent.com/in/1768019?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Important
The "toggle a module, then Configure" flow hits the unsaved-changes dialog and forces a Discard. A persisted bad guild can also trap /app. Details inline.
Reviewed changes
I read the full diff and cross-checked the layout, useUnsavedChanges, and GuildSettingsForm against it.
- Single
/apppage —app/pages/app.vuerenders the picker, section components and logs panel insidedashboard.vue; legacy/guilds/:id/manage|logspages become client-side redirect shims. - Active guild state —
useActiveGuild()+active-guild.client.tshold and persist guild, section and logs tab;useDashboardNavigation()parks switches behind the unsaved-changes dialog. - Per-guild stores —
useGuildData,useGuildSettingsanduseGuildSettingsChangesbecome per-guild maps;submitChanges()captures the guild id before awaiting. - New UI —
ServerRail,Picker,ModulesSummary,settings/Modules.vue, grouped sidebar nav, restyled Events/Moderation/General sections, and theGUILD_MODULESregistry withModulesSettingsSchema. - Config and housekeeping —
/approute rules, sitemap exclusion,robots: falseon/guilds/**,@vueuse/routerremoval, new i18n keys across locales (untranslated locales correctly use""placeholders), tests and AGENTS.md notes.
Note: 3 inline comment(s) dropped because they did not anchor to lines inside the PR diff:
app/layouts/dashboard.vue:277(RIGHT) — line 277 (RIGHT) is not inside a diff hunkapp/layouts/dashboard.vue:537(RIGHT) — line 537 (RIGHT) is not inside a diff hunkapp/layouts/dashboard.vue:211(RIGHT) — line 211 (RIGHT) is not inside a diff hunk
claude-sonnet-5-5 ｜ 𝕏
Contributor
|
Three findings from my review couldn't be attached inline because they sit on lines outside the diff hunks of
The active guild is saved to ℹ️ The guild-switch reset watcher now clears the wrong guild's draft ( When the watcher runs, ℹ️
|
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
This was referenced Oct 10, 2026
RedStar071
force-pushed
the
refactor/v3-marketing
branch
from
October 11, 2026 14:14
93bbe07 to
75468ed
Compare
RedStar071
force-pushed
the
refactor/v3-dashboard
branch
from
October 11, 2026 14:14
05edf71 to
41d0540
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.
Important
Two flows are still broken: staged edits make every section change open the Discard dialog, and a persisted guild that fails to load traps /app. The inline comments for both on the previous review were dropped for landing off-hunk, so they are re-anchored here.
Reviewed changes
I read the new console-shell commit in full against the existing /app page and traced the navigation, guild-state and layout paths it touches.
- Console shell —
dashboard.vuebecomes a rail, sidebar, title bar and docked save bar, with a phone drawer andDashboardBottomNav. The phone drawer resolves the earlier "no guild switcher belowlg" gap. - Grouped navigation —
DASHBOARD_NAVdrives the sidebar, tab bar and page title, anduseDashboardNavPrefsadds browser-local pins, recents and folded groups. - Overview —
General.vuenow shows stat cards, a 7-day moderation chart (bucketModerationActivity) andGuildModulesSummary. - Restyled sections —
Events.vue,ActivitySection.vue,logs/Panel.vueandcard.vuemove toconsole-card;Events.vuelinks tochannelsviagoToSection. - Tests — new specs for the sidebar, bottom nav, server rail, modules, nav list and activity bucketing. I confirmed the
ts()andlabelKeykeys used by the new components exist inen.
claude-sonnet-5-5 ｜ 𝕏
RedStar071
force-pushed
the
refactor/v3-marketing
branch
from
October 12, 2026 11:47
75468ed to
b6ce98c
Compare
RedStar071
force-pushed
the
refactor/v3-dashboard
branch
from
October 12, 2026 11:47
129009d to
6b014bd
Compare
Contributor
There was a problem hiding this comment.
✅ No new issues in this commit. The six open threads from the previous review are untouched by it, so they still stand (same-guild
goToSectionparking, persisted guild not cleared on a failed load, and the four informational notes).
Reviewed changes
I reviewed the one commit pushed since the last review, 6b014bda, and checked it against the section components' declared props and the layout.
- Landmarks —
app/pages/app.vuenow renders a<main>, so the title bar<header>sits inside it and is no longer a banner. The sidebar's server-name<header>became a<div>, leaving a single banner. - Valid stat markup — the stat notes in
settings/General.vueare<dd>elements, so the<dl>is valid. - Names and contrast —
GuildIcon'srole="img"now has anaria-label. The picker description usestext-toned, and the active logs tab trigger usestext-highlighted. - Section props —
sectionPropspasseslanguagesonly to the Overview andcommandsonly tocommands, which removes the extraneous-attribute warnings. This matches thedefinePropsofGeneral.vueandDisabledCommands.vue.
claude-sonnet-5-5 ｜ 𝕏
RedStar071
force-pushed
the
refactor/v3-marketing
branch
from
October 12, 2026 12:30
b6ce98c to
f609904
Compare
RedStar071
force-pushed
the
refactor/v3-dashboard
branch
from
October 12, 2026 12:30
6b014bd to
411dc26
Compare
Contributor
|
Run failed. View the logs →
|
| <component | ||
| :is="renderComponent" | ||
| v-else | ||
| :key="`${activeGuildId}:${section}`" |
Contributor
There was a problem hiding this comment.
Switching sections preserves drafts but remounts the settings form. Modules initializes its controls from the merged draft, and GuildSettingsForm then treats those drafted values as its saved baseline.
For example, enable Bad words, visit Roles, return to Modules, and enable Capitals. The first toggle now matches originalState, so removeChange() drops it from the draft. Settings synchronization restores Bad words to false; saving sends Bad words disabled and Capitals enabled, silently losing the first edit.
Build the comparison baseline from persisted settings while displaying the merged draft, and test editing after returning to a section. This needs to be fixed before merging. The higher PR heads retain this failure: #455 removes whole-draft clearing but leaves the incorrect baseline and per-field removal.
Artifacts
Completed corrected browser run
- Records the executed command, working directory, exit code, passing current-head reproduction, observed PATCH, and higher-head harness blocker.
Completion check and corrected source citation
- Records the completed-run status, actual Modules defaults lines, and higher-head form helper source, confirming the citation correction and static assessment.
Corrected harness server execution record
- Records the harness command and its intentional termination after browser capture, showing the server run ended.
Supplied revisions and higher-stack source inspection
- Contains executed numbered source and caller inspection across the supplied revisions, supporting the finding and higher-stack assessment.
Full executed browser test source
- Retains the complete Chromium interaction, assertions, save interception, screenshots, and video capture source.
Authored browser harness source
- Retains the revision extraction and isolated component server used by the completed run.
Authored state mocks and save interaction source
- Retains the realistic state mocks and live evidence panel used with the real production components.
- Retains the harness startup and browser commands with output-capture logic, making the execution record reproducible.
Executed source-inspection commands
- Retains the revision and caller inspection commands used without changing checkout.
- Retains the browser entry document and evidence-panel styling used for the captures.
Authored unrelated-section mock
- Retains the mock section that allows the actual Modules component to unmount and remount.
- Retains the guild route binding used by the supplied-base harness.
- Retains the telemetry stub used to isolate the selected interaction from external reporting.
▶ Supplied base has no Modules page
- Records section navigation at the supplied base, showing that an equivalent Modules page is absent.
Supplied-base recording poster
- Captures the supplied base’s absent Modules section, documenting the comparison limitation.
▶ Current-head toggle loss and save consequence
- Records both toggles, navigation away and back, and Save, showing the first intended enable saved as false.
Current-head draft after the second toggle
- Captures the live draft after enabling Capitals, showing the earlier Bad words enable was lost.
Current-head PATCH and saved response
- Captures the request and mock persisted response, showing Bad words false and Capitals true.
Prompt To Fix With AI
This is a comment left during a code review.
Path: app/pages/app.vue
Line: 44
Comment:
**Earlier edits silently disappear**
Switching sections preserves drafts but remounts the settings form. Modules initializes its controls from the merged draft, and `GuildSettingsForm` then treats those drafted values as its saved baseline.
For example, enable Bad words, visit Roles, return to Modules, and enable Capitals. The first toggle now matches `originalState`, so `removeChange()` drops it from the draft. Settings synchronization restores Bad words to `false`; saving sends Bad words disabled and Capitals enabled, silently losing the first edit.
Build the comparison baseline from persisted settings while displaying the merged draft, and test editing after returning to a section. This needs to be fixed before merging. The higher PR heads retain this failure: #455 removes whole-draft clearing but leaves the incorrect baseline and per-field removal.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
Contributor
There was a problem hiding this comment.
ℹ️ No critical issues — one dead-code cleanup inline.
Reviewed changes
I reviewed the two commits since the last pullfrog review (411dc2603, 77d21632f) and checked the earlier open threads against them. All six were already resolved by the fixes in 411dc2603, and the code at each anchor matches the author's replies.
- Same-guild section switches —
goToSectionno longer parks behind the dialog, so staged edits follow the admin between sections; onlygoToGuildparks. - Rejected servers cleared — the layout error watcher calls
selectGuild(null)for every non-401 failure, anddiscardAndLeaveresets the draft on the route-leave path too. - URL hygiene —
?refresh=trueis stripped after the first successful load, and server-card links carry?guild=<id>, which the layout moves into state and removes. - Plural category note — the Overview uses
tc()with a plural form. - Floating save card — the save bar is a
role="region"card, in flow above the tab bar on phones and floating fromsmup with extra bottom padding on.console-content. The newunsaved_barkey is added across locales and the schema.
claude-sonnet-5-5 ｜ 𝕏
| if (pending.guildId !== undefined) { | ||
| selectGuild(pending.guildId); | ||
| } | ||
| if (pending.section !== undefined) { |
Contributor
There was a problem hiding this comment.
ℹ️ goToSection no longer writes pendingNavigation, so pending.section is never set and this branch is dead. Drop it and the section field from PendingDashboardNavigation in useActiveGuild.ts, and update the "guild/section switch" comment above leaveDialogOpen in dashboard.vue.
RedStar071
force-pushed
the
refactor/v3-dashboard
branch
from
October 13, 2026 14:45
77d2163 to
a878bef
Compare
RedStar071
force-pushed
the
refactor/v3-marketing
branch
from
October 13, 2026 14:45
f609904 to
c0a76c7
Compare
The dashboard becomes one client-rendered page that keeps the active guild in state instead of the URL. - `app/pages/app.vue` renders the picker, the section components and the logs panel inside `layouts/dashboard.vue`, which gains a server rail (`GuildServerRail`), a Modules summary card and grouped sidebar navigation. `useActiveGuild()` owns `activeGuildId`, `section` and `logsTab`; `useDashboardNavigation()` routes every switch through the "unsaved changes" dialog when edits are staged. - `useGuildData()`, `useGuildSettings()` and `useGuildSettingsChanges()` are keyed by the active guild (one `useState` map per store), and the save handler captures the guild id before awaiting so a response that lands after a switch cannot touch another guild's draft. - `plugins/active-guild.client.ts` mirrors the selection to the `wolfstar-active-guild` localStorage key so a reload lands back on the same server and section. - New Modules section (`settings/Modules.vue`) and summary card read the module registry in `shared/utils/guild-modules.ts`; the schema in `shared/schemas/modules.ts` is derived from it. - `/guilds/:id/manage/*` and `/guilds/:id/logs/*` stay as thin shims that record the guild and section into state and forward to `/app`. - Route rules: `/app` is `ssr: false`, never prerendered and `robots: false`; `/guilds/**` is `robots: false` too. `/app` is excluded from the sitemap and classified as `route-dashboard` for view transitions. - `@vueuse/router` is no longer used anywhere and is removed. - New `dashboard.*` and `guild_settings.modules.*` keys, added to every locale as empty placeholders; AGENTS.md documents the `/app` model. Co-authored-by: Claude <noreply@anthropic.com>
Give /app the layout of the redesign: a server rail, a sidebar with the sections grouped under Modules and Records (with pinned sections and the ones opened last), a title bar with the unsaved-changes pill, and a tab bar plus a drawer on phones. Surfaces come from the design system's ink scale, so the rail, the sidebar, the cards and the page are four tones. The overview shows the server's counts, the moderation actions of the last seven days as a chart, the module list and the activity feed in cards. The unsaved-changes bar is docked under the page instead of floating over it.
The page had no main landmark and two banner landmarks: the title bar is now a header inside main, and the sidebar's server name is a plain block. The stat notes are dd elements so the list is a valid dl, the server icon has a name, and the picker text and the active log tab meet the contrast ratio. Sections are handed only the props they declare, which silences Vue's extraneous-attribute warning on each of them.
…d link cards to their server
RedStar071
force-pushed
the
refactor/v3-dashboard
branch
from
October 13, 2026 17:19
7ef6177 to
69b75cd
Compare
RedStar071
force-pushed
the
refactor/v3-marketing
branch
from
October 13, 2026 17:19
c0a76c7 to
1823c81
Compare
| v-if="guild.wolfstarIsIn && guild.manageable" | ||
| :to="`/guilds/${guild.id}/manage`" | ||
| :to="{ path: '/app', query: { guild: guild.id } }" | ||
| @click="goToGuild(guild.id)" |
Contributor
There was a problem hiding this comment.
Ctrl-clicking or Command-clicking a server card opens another tab but also runs goToGuild() in the current tab. With no staged edits, this changes its selected server and resets its saved section. The router skips navigation for these clicks, but the added handler does not. Both server-card links have this behavior.
Only call goToGuild() for an ordinary left-click. Let other clicks follow the guild-specific link without changing local state.
Prompt To Fix With AI
This is a comment left during a code review.
Path: app/components/guild/card.vue
Line: 140
Comment:
**New tabs change this tab**
Ctrl-clicking or Command-clicking a server card opens another tab but also runs `goToGuild()` in the current tab. With no staged edits, this changes its selected server and resets its saved section. The router skips navigation for these clicks, but the added handler does not. Both server-card links have this behavior.
Only call `goToGuild()` for an ordinary left-click. Let other clicks follow the guild-specific link without changing local state.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
Comment on lines
+298
to
+307
| const { entries: moderationEntries, total: moderationTotal } = useModerationLog({ | ||
| guildId: guildData.value.id, | ||
| limit: CHART_ENTRY_LIMIT, | ||
| filters: computed(() => ({ from: activityFrom.value })), | ||
| }); | ||
| const { total: commandTotal } = useCommandLog({ | ||
| guildId: guildData.value.id, | ||
| limit: 1, | ||
| filters: computed(() => ({ from: activityFrom.value })), | ||
| }); |
Contributor
There was a problem hiding this comment.
The new overview reads the log entries and totals but ignores each request’s status and errors. If a request fails, its fallback total is 0, so the page reports no cases or commands instead of saying the count is unavailable. A failed moderation request also produces seven empty bars. Admins cannot tell a quiet server from a failed request.
This is a non-blocking display issue. Show a loading or unavailable state until each request succeeds, and offer a retry on failure.
Artifacts
- Recorded the base component with populated, failing and empty endpoint configurations; the original overview has no activity counts or chart.
- 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
- Captured the rendered base component with populated endpoints available; it does not display moderation or command activity.
Base overview with failed activity endpoints configured
- 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
- Captured the rendered base component with empty endpoints available; its activity presentation remains absent.
Head overview after populated successful requests
- Captured the head after successful requests settled; DOM assertions verified six cases, twelve commands and nonzero chart activity.
Head overview after activity requests failed
- 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
- Captured the head after successful empty responses; its counts and chart accessibility text match the failed-request condition.
- Executed this uniquely named test against both snapshots; it asserts the observed success, failure and empty-response presentations.
- Used this configuration to run the component test and capture browser observations; unrelated agent tests were not included.
- Exported the exact base component using git show and imported it into the browser test; no checkout was needed.
- Exported the exact head component using git show and imported it into the browser test; its activity failure behavior was exercised directly.
- Captured the successful base test command and observed DOM output; the original overview has no activity counts, chart or activity requests.
- Captured the successful head test command, request queries, error messages and equality assertions; failed activity is displayed exactly like empty activity.
- Repeated the head test and captured rendered text, dimensions and visible ancestors alongside request results; the failure presentation exists in the rendered browser layout.
- Captured 19 git show and diff commands with line-numbered output; all four higher snapshots retain the activity status/error omission.
Prompt To Fix With AI
This is a comment left during a code review.
Path: app/components/guild/settings/General.vue
Line: 298-307
Comment:
**Failed counts look empty**
The new overview reads the log entries and totals but ignores each request’s status and errors. If a request fails, its fallback total is `0`, so the page reports no cases or commands instead of saying the count is unavailable. A failed moderation request also produces seven empty bars. Admins cannot tell a quiet server from a failed request.
This is a non-blocking display issue. Show a loading or unavailable state until each request succeeds, and offer a retry on failure.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
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
…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 #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 #453.
Stack: #451 foundation ← #452 header/footer ← #453 marketing ← #454
/appdashboard ← #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.vuerenders 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:
/appisssr: false, not prerendered, out of the sitemap androbots: false;/guilds/**isrobots: falseas well (new here, the auth-gated shims were indexable before).@vueuse/routerhas 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.
wolfstar-dashboard-nav) and never reach the server.app/utils/dashboard-nav.tsis the single list the sidebar, the tab bar and the page title read.--ink-*, added next to the spectrum tokens) in the dark theme and white with a tinted rail in the light one.console-cardandconsole-labelare 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
/profilelinks for the preferences dialog.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.
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.
T-Rex evidence
Evidence from the check
Evidence from the check
Evidence from the check
Command output from the check
Command output from the check
Command output from the check
After: Pr454 Failed Counts Success
After: Pr454 Failed Counts Failure
After: Pr454 Failed Counts Empty
▶ page@b1577e3ac2036f8690dfae10f2d355d0.webm
Before: Pr454 Failed Counts Success
Before: Pr454 Failed Counts Failure
Before: Pr454 Failed Counts Empty
▶ page@db1d5220ce2e59a5e6a32fafa94e0c50.webm
▶ Recording of the check
▶ Recording of the check
Base overview with populated activity endpoints configured
Base overview with failed activity endpoints configured
Base overview with empty activity endpoints configured
Head overview after populated successful requests
Head overview after activity requests failed
Head overview after successful empty requests
Evidence from the check
Evidence from the check
Evidence from the check
Evidence from the check
Command output from the check
Command output from the check
Command output from the check
Command output from the check
Evidence from the check
Evidence from the check
Evidence from the check
Command output from the check
Command output from the check
Command output from the check
▶ Recording of the check
▶ Recording of the check
Base overview with populated activity endpoints configured
Base overview with failed activity endpoints configured
Base overview with empty activity endpoints configured
Head overview after populated successful requests
Head overview after activity requests failed
Head overview after successful empty requests
Evidence from the check
Evidence from the check
Evidence from the check
Evidence from the check
Command output from the check
Command output from the check
Command output from the check
Command output from the check
Summary
Replaces guild-specific dashboard pages with a client-rendered
/apppage./appdashboard.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.
Reviews (9) · Last reviewed commit: "fix(dashboard): keep a single hover high..." · Reviewed by Greptile