fix: correct project limit warnings for multi-organization users

[HarshMN2345]

What does this PR do?

Fixes issue where users with multiple organizations (Free/Pro/Scale)
saw incorrect project limit warnings and "Manage projects" modal
showing projects from other organizations.

Test Plan

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

yes

[appwrite]

Console

Project ID: 688b7bf400350cbd60e9

Sites (2)

Site	Status	Logs	Preview	QR
console-qa 688b7cf6003b1842c9dc	Ready	View Logs	Preview URL
console-cloud 688b7c18002b9b871a8f	Ready	View Logs	Preview URL

Note

You can use Avatars API to generate QR code for any text or URLs.

[ItzNotABug]

do also not have this same thing on upper level +layout.ts? lets see which one we can avoid. this is massive data :\

[ItzNotABug]

instead of the free plan check, lets see if the currentPlan.projects or whatever the variable is. We need to avoid hardcoded billing plan name/id checks.

[Copilot]

Pull Request Overview

This PR fixes project limit warnings for users with multiple organizations, ensuring that project limits and related UI elements display correctly based on the current organization's plan rather than showing incorrect information from other organizations.

• Updates project limit validation to use organization-specific project counts instead of global counts
• Modifies the project selection modal to only show projects from the current organization
• Dynamically displays correct project limits in UI messages based on the current plan

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/routes/(console)/organization-[organization]/+page.svelte	Updates alert condition to compare against actual plan project limit instead of hardcoded value
src/routes/(console)/+layout.svelte	Adds organization-specific project count validation before calling limit check
src/lib/stores/billing.ts	Modifies project limit check to accept optional organization project count parameter
src/lib/layout/createProject.svelte	Dynamically displays project limit from current plan instead of hardcoded "2 projects"
src/lib/components/billing/alerts/selectProjectCloud.svelte	Filters projects to only show those from current organization and uses dynamic limit text

[Copilot]

Early return when projectCount is undefined may silently skip important project limit checks. Consider logging this condition or providing a fallback mechanism to fetch the project count when it's not provided.

Suggested change

	if (projectCount === undefined) return;
	if (projectCount === undefined) {
	console.warn('checkForProjectsLimit: projectCount is undefined, attempting to fetch project count for org', org?.$id);
	try {
	// Attempt to fetch the project count as a fallback
	const projectsList = await sdk.forConsole.projects.list([Query.equal('organizationId', org.$id)]);
	projectCount = projectsList?.total ?? projectsList?.projects?.length ?? 0;
	} catch (err) {
	console.error('checkForProjectsLimit: Failed to fetch project count for org', org?.$id, err);
	return;
	}
	}

[Copilot]

[nitpick] The ternary operator condition could be clearer. Consider extracting this logic into a well-named variable or function to improve readability and make the organization filtering intent more explicit.

Suggested change

	page.data.currentOrgId === currentOrgId ? page.data.allProjects?.projects || [] : [];
	const isCurrentOrganizationSelected = page.data.currentOrgId === currentOrgId;
	projects =
	isCurrentOrganizationSelected ? page.data.allProjects?.projects || [] : [];