Skip to content

hardening: G13 usage visibility and automation block reasons#26

Merged
DevCalebR merged 2 commits intomainfrom
hardening/g13-usage-visibility
Mar 2, 2026
Merged

hardening: G13 usage visibility and automation block reasons#26
DevCalebR merged 2 commits intomainfrom
hardening/g13-usage-visibility

Conversation

@DevCalebR
Copy link
Copy Markdown
Owner

Summary

  • add shared usage visibility helpers for tier/usage formatting and automation blocked reasons
  • surface plan tier + current period usage in leads and billing UI
  • add explicit blocked reason messaging with upgrade/billing CTA using reusable upgrade banner patterns
  • add focused presenter/helper tests for usage visibility logic
  • update production readiness changelog marking G13 done

Verification

  • npm test
  • npm run lint
  • npm run build
  • npm run typecheck
  • npm run env:check

@vercel
Copy link
Copy Markdown

vercel bot commented Mar 2, 2026

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

Project Deployment Actions Updated (UTC)
callbackcloser Ready Ready Preview, Comment Mar 2, 2026 5:14am

Request Review

@DevCalebR DevCalebR force-pushed the hardening/g13-usage-visibility branch from 63a8fc7 to c3095c1 Compare March 2, 2026 05:13
@DevCalebR DevCalebR merged commit 2edb965 into main Mar 2, 2026
3 checks passed
@DevCalebR DevCalebR deleted the hardening/g13-usage-visibility branch March 2, 2026 05:22
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