safe-global / safe-client-gateway / 29342194939 / 2

88%

main: 88%

push

github

chore: rename zerionBalancesEnabled flag to zerion (#3157)

* chore: rename zerionBalancesEnabled flag to zerionEnabled

Renames the features.zerionBalancesEnabled feature flag to features.zerionEnabled and drops the legacy FF_ZERION_BALANCES_CHAIN_IDS env var fallback (and its .env.sample/devcontainer entries). The flag now gates Zerion as a whole rather than balances specifically.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* fix: parse FF_ZERION_ENABLED as a strict boolean

Align the flag with the other FF_* env vars: only the literal string
'true' (case-insensitive) enables it. Previously any non-empty value
- including 'false' or a legacy chain-id list - enabled the flag.

Also mark the flag optional in .env.sample.json (matching the unset
default) and drop the dead features.zerionEnabled mocks from the
balances API manager spec, which never reads that key.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* chore: use bare boolean for FF_ZERION_ENABLED sample default

Matches the dominant defaultValue style in .env.sample.json.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* chore: rename features.zerionEnabled to features.zerion

Config key only — the FF_ZERION_ENABLED env var is unchanged (already
provisioned on staging and production). Internal boolean names such as
SafesV2Service#zerionEnabled keep the -Enabled suffix.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2422 of 4444 branches covered (54.5%)

Branch coverage included in aggregate %.

7209 of 10618 relevant lines covered (67.89%)

370.56 hits per line