fix(web): align settings page widths

[diegoarff]

What Changed

Use the default readable settings container width for the Providers and Connections pages instead of the wide variant.

Why

These pages expanded beyond the content width used by the other settings pages, causing the content column to shift and grow when navigating between sections.

Both current layouts fit within the shared readable width. The Providers page retains its existing container query, so it still switches between split and stacked layouts based on the available space.

UI Changes

Providers

Before	After

Connections

Before	After

Verification

• Checked both pages at 1440x900 and 1024x768
• Confirmed the Providers responsive layout still switches correctly
• Confirmed neither page introduces horizontal overflow
• Confirmed the new Storage page already uses the readable settings container
• vp fmt --check
• vp lint
• pnpm --filter @t3tools/web typecheck

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for the UI changes
• No video is needed because this is a static layout change

Implemented with gpt-5.6-sol through the Codex harness.

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This small UI change narrows the Connections and Providers pages from the wide container to the readable default, with the Providers responsive layout still subject to the narrower available width. Because it changes the product's default rendered settings layout, human review is warranted.

No code changes detected at ce36464. Prior analysis still applies.

^{You can add or adjust custom eligibility rules. Learn more.}

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: pingdotgg/t3code/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: cac464a0-27ee-4272-b087-e3169dc2159c

📥 Commits

Reviewing files that changed from the base of the PR and between f33f6e1bb9a6701ef9d92ee470ed86312ba30bbc and ce36464.

📒 Files selected for processing (2)

• apps/web/src/components/settings/ConnectionsSettings.tsx
• apps/web/src/components/settings/ProviderSettingsPanel.tsx

Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review.

---

📝 Walkthrough

Walkthrough

Changes

Settings container width

Layer / File(s)	Summary
Use default settings container width apps/web/src/components/settings/ConnectionsSettings.tsx, apps/web/src/components/settings/ProviderSettingsPanel.tsx	Both components no longer pass width="wide" to SettingsPageContainer. They now use the container's default width.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Bug fix

Suggested reviewers: stienswout

Merge Risk: ⚪ Minimal · up to ce364

This change aligns the Providers and Connections settings layouts without affecting their behavior. No actionable merge-blocking risk remains.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 2 functions across 2 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: aligning the settings page widths.
Description check	✅ Passed	The description explains what changed, why it changed, the UI impact, verification performed, and checklist completion. It includes before-and-after screenshots for the UI changes.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

---

_{Comment @coderabbitai help to get the list of available commands.}