Skip to content

chore(landing): remove dead dashboard-shell component cluster - #408

Open
EfeDurmaz16 wants to merge 2 commits into
mainfrom
chore/prune-dead-landing-cluster
Open

chore(landing): remove dead dashboard-shell component cluster#408
EfeDurmaz16 wants to merge 2 commits into
mainfrom
chore/prune-dead-landing-cluster

Conversation

@EfeDurmaz16

Copy link
Copy Markdown
Owner

Removes app-shell.tsx and the components it composed (app-sidebar, app-header, command-palette, keyboard-shortcuts) plus empty-state and page-transition — dashboard-template scaffolding imported by nothing (~1.3k LOC). Verified zero references across app/ and components/.

From the ponytail×deslop minimization audit. framer-motion (now unused) and the now-dead components/ui/ primitives are left for a careful follow-up (the ui prune needs verification beyond grep).

app-shell.tsx and the components it composed (app-sidebar, app-header,
command-palette, keyboard-shortcuts), plus empty-state and page-transition,
were dashboard-template scaffolding imported by nothing — the marketing
pages use inline-styled layouts. ~1.3k LOC of dead code; verified no
remaining references. (framer-motion is now unused; left for a follow-up
that also prunes the now-dead ui/ primitives.)
@vercel

vercel Bot commented Jun 14, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sardis Ready Ready Preview, Comment Jun 14, 2026 1:07pm

Request Review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 660e7d281a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".


Use `sardis_spend` only after a successful `sardis_check_policy` result.

Use `sardis_pay_invoice` for invoice-shaped requests instead of manually constructing a payment when invoice metadata is available.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Require policy checks before invoice payments

When the request includes invoice metadata, this tells the agent to call sardis_pay_invoice, but the explicit preflight rule above only applies to sardis_spend. In the actual tool surface, sardis_pay_invoice is a money-moving path (payments.executeMandate or client.pay(...) in packages/sardis-agent-tools/src/tools/verbs.ts:186-201) and is classified alongside sardis_spend (packages/sardis-agent-tools/src/classify.ts:55-62), so under-threshold invoice payments can skip the sardis_check_policy step in the exact invoice flow this skill recommends.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant