Bug: Free tier still allows creating more than 10 articles

[taha-abbasi]

Bug (reported by Hasnat via #70)

Free version still allows creating more than 10 articles.

Context

• Bug: Article limit enforcement on free tier #25 was closed as fixed but the issue persists
• Per Taha: Free plan = 10 instant articles + 5/month. First month = 15 total, then 5/month.
• Dashboard does not clearly show these limits

Related

• Bug: Article limit enforcement on free tier #25 (previously closed)
• UX: Show upgrade popup when article limit reached #26 (upgrade popup when limit reached)

Priority

P1 — directly impacts monetization

[taha-abbasi]

Update: Generate button still active after limit reached

The 'Summon Your Scribe' button remains clickable even when the free tier limit is hit. Screenshot shows Cena Roofing at 12/10 articles with the warning banner visible, but the generate button is still active in the UI.

Current behavior: Warning banner shows 'Article limit reached (10 for free tier). Upgrade to generate more.' but the Summon button is not disabled — clicking it fails silently or errors out.

Expected behavior: The 'Summon Your Scribe' button should be disabled/grayed out once the plan limit is reached, with a clear visual state pointing users to upgrade.

This is a UX gap on top of the backend enforcement issue — even if the backend blocks it, the button shouldn't invite the click.

[taha-abbasi]

Update: Generate button still active after limit reached

The 'Summon Your Scribe' button remains clickable even when the free tier limit is hit. Screenshot shows Cena Roofing at 12/10 articles with the warning banner visible, but the generate button is still active in the UI.

Current behavior: Warning banner shows 'Article limit reached (10 for free tier). Upgrade to generate more.' but the Summon button is not disabled — clicking it fails silently or errors out.

Expected behavior: The 'Summon Your Scribe' button should be disabled/grayed out once the plan limit is reached, with a clear visual state pointing users to upgrade.

This is a UX gap on top of the backend enforcement issue — even if the backend blocks it, the button shouldn't invite the click.