bug(plans): Account global filter on Plans page is non-functional (plans-have-no-account)

[cristim]

Account chip on the Plans page is visible but selecting an account doesn't filter the plan list — frontend/src/plans.ts:32-78 loadPlans applies only providerFilter and explicitly skips account (the inline comment notes 'backend has no top-level provider field'). Plans live above accounts and reference accounts via the plan_accounts join table.

Fix direction

Filter via the join: backend api.getPlans() accepts ?account_ids= and JOINs plan_accounts. Mirror the pattern from recommendations.ts. Alternative: hide the Account chip on the Plans page when no per-plan account filter is implementable. First option preserves the affordance and matches user expectations.

Surfaced by QA spreadsheet rows 2.4 and 2.5.

[cristim]

QA verification still failing after PR #715 merged

Re-tested rows 2.4 and 2.5 (Plans page global filter, spreadsheet rows 325-326). Both still fail:

2.4 (Account filter): "When an Account is selected, the Plan where this account is set is shown. But, Plans where no account is specified are excluded. Based on the info in the New Purchase Plan modal > Target Account, when the field is left empty all accounts from this provider are targeted."

So a plan with target_account=NULL represents "all accounts of this provider", but the Account filter is excluding those plans rather than including them. The filter logic needs to treat a NULL/empty target_account as matching any account of the corresponding provider.

2.5 (Provider + Account): Same root cause as 2.4.

Reopening this thread - please re-investigate the filter predicate.

[cristim]

Verified shipped: PR #715 (commit 5abf40b, merged 2026-05-25) is in feat/multicloud-web-frontend. Plans page now passes account_ids query param via plan_accounts JOIN to backend; backend handler_plans.go and store_postgres.go updated accordingly. Tests added in plans.test.ts and handler_plans_test.go.