[Heyykrishnna]

Summary

The Calendar Card demo no longer imposes a 512px minimum height or a second layer of desktop padding. The studio gives this demo its own small inset, allowing the existing responsive card to fit inside the phone screen.

Related Issue

Closes #79

Type of Change

• Bug Fix

Component(s) Affected

• src/components/showcase/component-studio.tsx

Engineering Quality Checklist

• Reused existing components, utilities, dependencies, and motion behavior.
• No new dependencies or source comments.

Validation

Verified the calendar fits the phone preview without a scrollbar: client and scroll height both measured 705px. Checked tablet layout.

The integrated codex/staging tree containing this PR passed npm run lint, npm run typecheck, npm run build, npm run check:lockfile, registry synchronization, and git diff --check. Individual GitHub CI checks remain the merge gate.

Integration Note

The toast-containment PR for #81 touches the adjacent Toaster line in this wrapper. Both fixes are resolved together on staging; update the remaining branch after the first PR merges.

Visual Demonstration

Screenshots were captured from integrated staging.

Review follow-up

Re-signed the Calendar-only PR history. Toast changes continue separately in #100. A temporary base change caused the existing auto-merge to merge #92 into this issue branch; that branch update was reversed, restoring this PR to its Calendar-only head a53d9fe. Both active PRs target main. Whichever merges second requires rebasing onto main to preserve the adjacent wrapper and toaster changes; staging already validates their combined result.

[vercel]

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

Project	Deployment	Actions	Updated
component-library	Ready	Preview	Oct 19, 2026 4:38am UTC

[Yash121l]

Looks good.

Heads-up: this conflicts with #92 in component-studio.tsx (both edit the calendar-card wrapper/<Toaster /> lines). Whichever merges second needs a rebase. I checked all pairs among #86–#96, and this is the only conflict.

CI checks pass. The Vercel devclubcompo failure shows up on every PR and on main ("Account is blocked"), so it is not caused by this change.

[Yash121l]

@Heyykrishnna this is approved, but main requires verified commit signatures and the commits here are unsigned, so it can't merge yet. Can you re-sign and force-push?

One-time setup (SSH signing):

git config --global gpg.format ssh
git config --global user.signingkey ~/.ssh/id_ed25519.pub
git config --global commit.gpgsign true

Add the same public key on GitHub under Settings → SSH and GPG keys → New SSH key with key type Signing Key. Also make sure the commit email (khandelwalyatharth39@gmail.com) is a verified email on your GitHub account, otherwise the signature shows as unverified.

Then on this branch:

git rebase --exec 'git commit --amend --no-edit -S' origin/main
git push --force-with-lease

Pushing dismisses the current approval (that's a ruleset setting), so I'll re-approve once the commits show Verified. Auto-merge is enabled, so it merges after that.

This PR and #92 conflict in component-studio.tsx. Whichever lands second needs the rebase anyway, and the rebase above covers it.

[Yash121l]

Re-checked after the signed push. The code is identical to what I approved. LGTM.