4ef5b9519c
Recommended lives on the plan family, not a version: it is a stance about
the product line ("which plan we point a visitor towards"), not a
capability that changes with a price, and freezing it per version would
make the mark silently vanish every time a new version publishes.
Setting a plan recommended clears whichever other plan carried the mark,
inside one transaction locking the whole table — two operators
recommending two different plans at once must not both win. The public
price sheet already had the highlighted-card treatment for this (it was
driven by a hardcoded "team" constant); it now reads the family instead.
|
||
|---|---|---|
| .. | ||
| components | ||
| errors | ||
| layouts | ||
| livewire | ||
| partials | ||
| vendor/wire-elements-modal | ||
| coming-soon.blade.php | ||
| landing.blade.php | ||
| legal.blade.php | ||
| status.blade.php | ||
| welcome.blade.php | ||