feat: use lifecycles API

[kyle-ssg]

Conform the project lifecycle page to the new backend API (#7789):

• Add lifecycle-status-counts RTK query for sidebar counts in one call
• Add lifecycle_stage + evaluation_period_days params to getProjectFlags and a lifecycle_stage field on ProjectFlag
• Each section now fetches only its own stage, classified server-side
• Remove client-side tag/code-reference/evaluation classification, the per-flag EvaluationChecker and useEvaluationCounts hook
• Single environment (name-matched "prod" by default, switchable in the left nav, persisted per project in a new redux slice) and a single evaluation_period_days replace the multi-env + dual-period controls
• Drop the non-functional "LIFECYCLE STAGES" sidebar header/Add button

Thanks for submitting a PR! Please check the boxes below:

• I have read the Contributing Guide.
• I have added information to docs/ if required so people know about the feature.
• I have filled in the "Changes" section below.
• I have filled in the "How did you test this code" section below.

Changes

Hooks up API for feature lifecycle

How did you test this code?

Go to lifecycle page as in the Flagsmith project

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
flagsmith-frontend-preview	Ready	Preview, Comment	Jul 8, 2026 12:56pm
flagsmith-frontend-staging	Ready	Preview, Comment	Jul 8, 2026 12:56pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Ignored	Preview	Jul 8, 2026 12:56pm

[github-actions]

Docker builds report

Image	Build Status	Security report
ghcr.io/flagsmith/flagsmith-api-test:pr-7793	Finished ✅	Skipped
ghcr.io/flagsmith/flagsmith-e2e:pr-7793	Finished ✅	Skipped
ghcr.io/flagsmith/flagsmith-api:pr-7793	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith:pr-7793	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith-private-cloud:pr-7793	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith-frontend:pr-7793	Finished ✅	Results ✅

[github-actions]

Playwright Test Results (oss - depot-ubuntu-latest-16)

 1 passed

Details

 1 test across 1 suite
 39.5 seconds
 a369ed5
 🔄 Run: #17534 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-arm-16)

 1 passed

Details

 1 test across 1 suite
 37.2 seconds
 a369ed5
 🔄 Run: #17534 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-16)

 4 passed

Details

 4 tests across 4 suites
 10.5 seconds
 a369ed5
 🔄 Run: #17534 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-arm-16)

 3 passed

Details

 3 tests across 3 suites
 1 minute, 10 seconds
 a369ed5
 🔄 Run: #17534 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-16)

 5 passed

Details

 5 tests across 4 suites
 43.3 seconds
 c890063
 🔄 Run: #17980 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-arm-16)

 3 passed

Details

 3 tests across 2 suites
 12 seconds
 c890063
 🔄 Run: #17980 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-16)

 4 passed

Details

 4 tests across 3 suites
 41.4 seconds
 8923106
 🔄 Run: #17981 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-arm-16)

 4 passed

Details

 4 tests across 3 suites
 44.8 seconds
 8923106
 🔄 Run: #17981 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-16)

 2 passed

Details

 2 tests across 2 suites
 53.4 seconds
 c890063
 🔄 Run: #17980 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-arm-16)

 5 passed

Details

 5 tests across 4 suites
 19.8 seconds
 8923106
 🔄 Run: #17981 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-16)

 5 passed

Details

 5 tests across 5 suites
 3.7 seconds
 8923106
 🔄 Run: #17981 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-16)

 3 passed

Details

 3 tests across 3 suites
 42.3 seconds
 bf57a38
 🔄 Run: #17982 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-arm-16)

 4 passed

Details

 4 tests across 3 suites
 39.8 seconds
 bf57a38
 🔄 Run: #17982 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-arm-16)

 1 failed
 1 passed

Details

 2 tests across 2 suites
 57.7 seconds
 c890063
 📦 Artifacts: View test results and HTML report
🔄 Run: #17980 (attempt 1)

Failed tests

firefox › tests/environment-permission-test.pw.ts › Environment Permission Tests › Environment-level permissions control access to features, identities, and segments @enterprise

### Playwright Test Results (private-cloud - depot-ubuntu-latest-16)

 4 passed

Details

 4 tests across 4 suites
 33.2 seconds
 bf57a38
 🔄 Run: #17982 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-arm-16)

 3 passed

Details

 3 tests across 2 suites
 12.5 seconds
 bf57a38
 🔄 Run: #17982 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-16)

 4 passed

Details

 4 tests across 3 suites
 42 seconds
 06ac488
 🔄 Run: #17983 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-arm-16)

 4 passed

Details

 4 tests across 3 suites
 45.4 seconds
 06ac488
 🔄 Run: #17983 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-16)

 6 passed

Details

 6 tests across 5 suites
 34.4 seconds
 06ac488
 🔄 Run: #17983 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-arm-16)

 4 passed

Details

 4 tests across 3 suites
 12.2 seconds
 06ac488
 🔄 Run: #17983 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-16)

 3 passed

Details

 3 tests across 3 suites
 41.3 seconds
 ac8d1a3
 🔄 Run: #17997 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-arm-16)

 4 passed

Details

 4 tests across 3 suites
 11.9 seconds
 ac8d1a3
 🔄 Run: #17997 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-arm-16)

 5 passed

Details

 5 tests across 4 suites
 42.1 seconds
 ac8d1a3
 🔄 Run: #17997 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-16)

 5 passed

Details

 5 tests across 4 suites
 10.8 seconds
 ac8d1a3
 🔄 Run: #17997 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-16)

 4 passed

Details

 4 tests across 3 suites
 41.6 seconds
 5cf7e38
 🔄 Run: #17998 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-arm-16)

 3 passed

Details

 3 tests across 3 suites
 4.3 seconds
 5cf7e38
 🔄 Run: #17998 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-16)

 5 passed

Details

 5 tests across 4 suites
 41.3 seconds
 5cf7e38
 🔄 Run: #17998 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-arm-16)

 5 passed

Details

 5 tests across 4 suites
 36.1 seconds
 5cf7e38
 🔄 Run: #17998 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-arm-16)

 4 passed

Details

 4 tests across 3 suites
 45.5 seconds
 0fe0f62
 🔄 Run: #18000 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-16)

 5 passed

Details

 5 tests across 3 suites
 43.1 seconds
 0fe0f62
 🔄 Run: #18000 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-arm-16)

 5 passed

Details

 5 tests across 4 suites
 18.8 seconds
 0fe0f62
 🔄 Run: #18000 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-16)

 5 passed

Details

 5 tests across 3 suites
 38.4 seconds
 0fe0f62
 🔄 Run: #18000 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-16)

 2 passed

Details

 2 tests across 2 suites
 50.8 seconds
 34e3478
 🔄 Run: #18001 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-arm-16)

 3 passed

Details

 3 tests across 3 suites
 45.6 seconds
 34e3478
 🔄 Run: #18001 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-16)

 4 passed

Details

 4 tests across 4 suites
 32.2 seconds
 34e3478
 🔄 Run: #18001 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-arm-16)

 2 passed

Details

 2 tests across 2 suites
 59.6 seconds
 34e3478
 🔄 Run: #18001 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-16)

 3 passed

Details

 3 tests across 3 suites
 41.1 seconds
 94fcab4
 🔄 Run: #18076 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-arm-16)

 4 passed

Details

 4 tests across 3 suites
 45.2 seconds
 94fcab4
 🔄 Run: #18076 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-16)

 5 passed

Details

 5 tests across 4 suites
 18.1 seconds
 94fcab4
 🔄 Run: #18076 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-arm-16)

 5 passed

Details

 5 tests across 5 suites
 36.2 seconds
 94fcab4
 🔄 Run: #18076 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-16)

 4 passed

Details

 4 tests across 3 suites
 42.9 seconds
 9b69c08
 🔄 Run: #18096 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-arm-16)

 4 passed

Details

 4 tests across 3 suites
 45.3 seconds
 9b69c08
 🔄 Run: #18096 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-arm-16)

 4 passed

Details

 4 tests across 3 suites
 36.7 seconds
 9b69c08
 🔄 Run: #18096 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-16)

 5 passed

Details

 5 tests across 4 suites
 43 seconds
 9b69c08
 🔄 Run: #18096 (attempt 1)

[github-actions]

Visual Regression

19 screenshots compared. See report for details.
View full report

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR replaces client-side feature lifecycle evaluation and counting with backend-driven lifecycle counts and stage classification. It adds lifecycle request/response types, a new lifecycle counts query, a persisted per-project environment selection slice and hook, and refactors the feature lifecycle page and section components to use environment-scoped data. It also adds row click handling and a feature usage modal, and updates the lifecycle sidebar and labels.

Estimated code review effort: 4 (Complex) | ~60 minutes

---

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 5

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

frontend/web/components/pages/feature-lifecycle/components/FeatureUsageModal.tsx (1)

1-44: 📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win

New component doesn't follow the mandated folder structure.

FeatureUsageModal.tsx is a brand-new component placed flat in components/, rather than in its own FeatureUsageModal/FeatureUsageModal.tsx with a co-located barrel index.ts.

As per coding guidelines, "Each new component must live in its own folder with a barrel index.ts, a ComponentName/ComponentName.tsx file, co-located ComponentName.scss, any subcomponents, and imports should use the component folder path rather than the inner file."

#!/bin/bash
# Description: Verify current placement/structure of the new component.
fd FeatureUsageModal frontend/web/components/pages/feature-lifecycle

Source: Coding guidelines

♻️ Duplicate comments (1)

frontend/web/components/pages/feature-lifecycle/hooks/useLifecycleData.ts (1)

52-90: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Duplicated FeatureListStore subscribe/unsubscribe block across both hooks.

The identical useEffect wiring FeatureListStore.on/off('saved'|'removed', refetch) is repeated verbatim in useLifecycleCounts and useLifecycleSectionFlags. This is also the direct-store-coupling pattern previously flagged as making the hook hard to test (no seam to inject/mock the event source). Extracting a small shared hook (e.g. useRefetchOnFeatureListEvents(refetch)) would remove the duplication and provide the seam needed for testability.

♻️ Proposed refactor

+function useRefetchOnFeatureListEvents(refetch: () => void) {
+  useEffect(() => {
+    FeatureListStore.on('saved', refetch)
+    FeatureListStore.on('removed', refetch)
+    return () => {
+      FeatureListStore.off('saved', refetch)
+      FeatureListStore.off('removed', refetch)
+    }
+  }, [refetch])
+}
+
 export function useLifecycleCounts({
   environmentId,
 }: {
   environmentId: number | undefined
 }) {
   const query = useGetLifecycleStatusCountsQuery(
     environmentId ? { environment: environmentId } : skipToken,
     { refetchOnMountOrArgChange: true },
   )

-  const { refetch } = query
-  useEffect(() => {
-    FeatureListStore.on('saved', refetch)
-    FeatureListStore.on('removed', refetch)
-    return () => {
-      FeatureListStore.off('saved', refetch)
-      FeatureListStore.off('removed', refetch)
-    }
-  }, [refetch])
+  useRefetchOnFeatureListEvents(query.refetch)

Apply the equivalent replacement in useLifecycleSectionFlags.

Also applies to: 93-132

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 79bdbfe8-b1bb-4457-8851-b653e1dfa56e

📥 Commits

Reviewing files that changed from the base of the PR and between 5c55544 and 94fcab4.

📒 Files selected for processing (23)

• frontend/common/lifecycleEnvironmentSlice.ts
• frontend/common/services/useProjectFlag.ts
• frontend/common/store.ts
• frontend/common/types/requests.ts
• frontend/common/types/responses.ts
• frontend/web/components/feature-summary/ProjectFeatureRow.tsx
• frontend/web/components/pages/feature-lifecycle/FeatureLifecyclePage.tsx
• frontend/web/components/pages/feature-lifecycle/components/EvaluationChecker.tsx
• frontend/web/components/pages/feature-lifecycle/components/FeatureUsageModal.tsx
• frontend/web/components/pages/feature-lifecycle/components/LifecycleSidebar.tsx
• frontend/web/components/pages/feature-lifecycle/components/LiveSection.tsx
• frontend/web/components/pages/feature-lifecycle/components/MonitorSection.tsx
• frontend/web/components/pages/feature-lifecycle/components/NewSection.tsx
• frontend/web/components/pages/feature-lifecycle/components/PermanentSection.tsx
• frontend/web/components/pages/feature-lifecycle/components/RemoveSection.tsx
• frontend/web/components/pages/feature-lifecycle/components/SectionShell.tsx
• frontend/web/components/pages/feature-lifecycle/components/StaleSection.tsx
• frontend/web/components/pages/feature-lifecycle/constants.tsx
• frontend/web/components/pages/feature-lifecycle/hooks/predictProdEnvironment.ts
• frontend/web/components/pages/feature-lifecycle/hooks/useEvaluationCounts.ts
• frontend/web/components/pages/feature-lifecycle/hooks/useLifecycleData.ts
• frontend/web/components/pages/feature-lifecycle/hooks/useLifecycleEnvironment.ts
• frontend/web/components/pages/feature-lifecycle/types.ts

💤 Files with no reviewable changes (3)

• frontend/web/components/pages/feature-lifecycle/components/EvaluationChecker.tsx
• frontend/web/components/pages/feature-lifecycle/types.ts
• frontend/web/components/pages/feature-lifecycle/hooks/useEvaluationCounts.ts

[talissoncosta]

Looks good on my view! Thanks for addressing the feedback.

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

frontend/common/services/useProjectFlag.ts (1)

142-150: 🚀 Performance & Scalability | 🔵 Trivial | 💤 Low value

Consider scoping LifecycleCounts tag per environment.

providesTags/invalidatesTags use a single global 'LifecycleCounts' tag rather than one keyed by environment id. This is consistent between the query and the mutations, so it's not a bug, but any flag mutation in one project/environment will invalidate cached counts for every environment currently held in the cache, causing extra refetches for unrelated environments in multi-tab or multi-environment scenarios.

♻️ Optional: scope the tag by environment id

       getLifecycleStatusCounts: builder.query<
         Res['lifecycleStatusCounts'],
         Req['getLifecycleStatusCounts']
       >({
-        providesTags: ['LifecycleCounts'],
+        providesTags: (_res, _err, req) => [
+          { id: req.environment, type: 'LifecycleCounts' },
+        ],
         query: ({ environment }) => ({
           url: `environments/${environment}/feature-lifecycle-counts/`,
         }),
       }),

Note: this would also require updating the invalidatesTags arrays on createProjectFlag, updateProjectFlag, and removeProjectFlag to target the relevant environment id (if available in their args/response) instead of the bare tag type.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 27595980-170d-45e1-b285-0e26d5542aae

📥 Commits

Reviewing files that changed from the base of the PR and between 94fcab4 and 9b69c08.

📒 Files selected for processing (3)

• frontend/common/services/useProjectFlag.ts
• frontend/web/components/feature-summary/ProjectFeatureRow.tsx
• frontend/web/components/pages/feature-lifecycle/components/RemoveSection.tsx