A cross-layer workflow passes unit tests but breaks when client, API, and persistence state arrive in a different order. The affected area is feature flags.
Repair the feature flags cache lifecycle implementation so it separates purge, refresh, and escalation actions by staleness and risk.
Evidence
- Affected surface: Full-stack frontend focus / feature flags.
- Observed failure family: plan cache invalidation.
- Scope policy: zoneState must equal healthy.