mirror of
https://github.com/Memo-2023/mana-monorepo.git
synced 2026-05-14 21:01:08 +02:00
fix(branding): drop who module's required tier from beta to public
The initial requiredTier='beta' was an arbitrary RFC default — when I first wired it up I was matching the status='beta' badge. But the beta tier in this app means "early access via founder invite", not "the feature is in beta". A signed-in standard user landing on /who hit the AuthGate lock screen with "Standard < Beta required" instead of being able to play the game. Drop to 'public', which means "any signed-in user". The module is still labeled status='beta' in the launcher (so it's flagged as new + unfinished), and the LLM calls behind it are credit-gated by the existing chat-style consume flow — those are the actual gates that matter for cost control. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
e3029ef80b
commit
b8bfc4d775
1 changed files with 6 additions and 1 deletions
|
|
@ -715,7 +715,12 @@ export const MANA_APPS: ManaApp[] = [
|
|||
color: '#a855f7',
|
||||
comingSoon: false,
|
||||
status: 'beta',
|
||||
requiredTier: 'beta',
|
||||
// Open to all signed-in users (Standard / public tier and up).
|
||||
// The initial 'beta' here was an arbitrary RFC default — it
|
||||
// matched the status='beta' badge but the gate was more friction
|
||||
// than value while the module is finding its audience. The LLM
|
||||
// calls behind it are credit-gated server-side regardless.
|
||||
requiredTier: 'public',
|
||||
},
|
||||
];
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue