source-academy / frontend / 35699500511

46%

push

github

chore: pin conductor.enable for the production deployment (#4403)

Instead of letting any user toggle conductor.enable from the
Feature Flags page, this pins it via REACT_APP_CONDUCTOR_ENABLE in
build-development.yml — the workflow that actually builds and
deploys sourceacademy.org. Someone who wants a non-Conductor
frontend now needs to build their own with this env var unset or
FALSE, rather than being able to flip it at runtime on the official
deployment.

The mechanism itself already existed: Constants.ts's conductorConfig
already read this env var, flagConductorEnable.ts already wired it
in as the flag's lockedValue, and setFlag/resetFlag already no-op
for a locked flag. This just activates it for the one deployment
that matters, as step one of deprecating the non-Conductor path
(js-slang#2069, js-slang#2062).

Deliberately scoped to conductor.enable alone — the sibling
directory.language.url/directory.plugin.url/directory.modules.url
flags stay user-togglable, since which directory to fetch from is a
separate concern from whether Conductor is used at all.

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>

3190 of 7902 branches covered (40.37%)

Branch coverage included in aggregate %.

7194 of 14688 relevant lines covered (48.98%)

31.93 hits per line