Jesse_ChenandClaude Opus 5.5
873fac8a5b
T6: offer True Citra and Fagan-Bradley beside Raman/Lahiri/KP/True Pushya,
engine-supported values only; widen profiles_ayanamsa_check by an additive
migration; ephemeris note names; path tests so no new value falls back to
Raman.
T7: the unlayered `button { color: inherit; }` beats Tailwind's
text-primary-foreground, so solid report buttons showed page ink (light
(light 4.85:1, dark 5.77:1), grey disabled without fade, neutral selected
preset. button.tsx and theme tokens unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
21 lines
920 B
PL/PgSQL
21 lines
920 B
PL/PgSQL
-- Widen the household ayanamsa setting from four to six values
|
|
-- (TASK-chart-types-and-report-buttons-20260928 T6): True Chitra and
|
|
-- Fagan-Bradley join Raman, Lahiri, KP and True Pushya. Every value is one the
|
|
-- engine already supports (`scripts/ayanamsa_utils.py` AYANAMSA_MODES); Djwhal
|
|
-- Khul and Sassanian stay out on purpose.
|
|
--
|
|
-- Only the CHECK changes: no column, default, grant or row is touched, so the
|
|
-- migrate-then-deploy window is safe (the deployed code only writes the old
|
|
-- four). `chart_profiles.ayanamsa` has no CHECK; the people route writes the
|
|
-- typed column directly, so the JSON fallback trigger is not on the write path.
|
|
begin;
|
|
|
|
alter table public.profiles
|
|
drop constraint if exists profiles_ayanamsa_check;
|
|
|
|
alter table public.profiles
|
|
add constraint profiles_ayanamsa_check
|
|
check (ayanamsa in ('raman', 'lahiri', 'kp', 'true_citra', 'true_pushya', 'fagan_bradley'));
|
|
|
|
commit;
|