Enforce AI feature dependency checks for feature flags and assistant-…

[cstns]

Description

Important

This PR is part of a nested merge list, do not merge it until its target is main

Note

The ai platform feature flag defaults to true when not set (implemented in #7317, commit 93900f4), so this is not a breaking change. AI features remain enabled by default; operators who want to disable them must explicitly set ai to false.

All AI feature flags now respect the ai flag introduced in the previous PR. If ai is disabled at either the platform or team type level, all downstream AI features are disabled.

Platform level (forge/ee/lib/index.js):

• generatedSnapshotDescription and assistantInlineCompletions now require ai.enabled in addition to assistant configuration
• expertAssistant and expertInsights now require ai.enabled in addition to their own config

Frontend (frontend/src/stores/account-settings.js):

• Added dependsOn support to FEATURE_CONFIGS and buildFeatureChecks
• isGeneratedSnapshotDescriptionFeatureEnabled and isExpertAssistantFeatureEnabled depend on isAiFeatureEnabled

Backend endpoints:

• Added ai team feature property check to snapshot description endpoints (device.js, project.js)
• Added ai team feature property check to the FIM inline completions endpoint (assistant.js)
• Device and instance settings responses now report assistant.enabled: false and disable inline completions when ai is disabled for the team (deviceLive.js, project.js)

Related Issue(s)

closes #7312

Checklist

• I have read the contribution guidelines
• Suitable unit/system level tests have been added and they pass
• Documentation has been updated
  • Upgrade instructions
  • Configuration details
  • Concepts
• Changes flowforge.yml?
  • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
  • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production
• Link to Changelog Entry PR, or note why one is not needed.

Labels

• Includes a DB migration? -> add the area:migration label

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.69%. Comparing base (4810241) to head (225bff9).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7319      +/-   ##
==========================================
+ Coverage   76.66%   76.69%   +0.02%     
==========================================
  Files         409      409              
  Lines       20798    20804       +6     
  Branches     5034     5039       +5     
==========================================
+ Hits        15945    15955      +10     
+ Misses       4853     4849       -4     

Flag	Coverage Δ
backend	76.69% <100.00%> (+0.02%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[hardillb]

Caution

The ai platform feature flag must be enabled across pre-staging, staging, production, and on-premise installations before this PR is merged. Without it, all AI features will be disabled since ai.enabled defaults to false. See https://github.com/FlowFuse/CloudProject/issues/1349

We can't ship a breaking change like this, it's going to have to default to on and allow opt out

I suggest we discuss this in the Eng meeting today

[cstns]

The description needs updating, sorry for the confusion. The ai feature flag actually defaults to true when not set, so this isn't a breaking change. The only configuration operators need to make explicit is the opt-out (setting ai to false).

That default was implemented in #7317 (commit 93900f4). I'll update the description now to reflect this.

[cstns]

the failed BE test seems to be unrelated to this change.. re-reunning