Support Seer Agent for orgs with Open Team Membership disabled

Seer Agent currently requires Open Team Membership (organization.flags.allow_joinleave) to be enabled at the org level. Organizations with this setting disabled cannot access Seer Agent at all, regardless of their Seer subscription status.

Current behavior

When Open Team Membership is disabled, Seer Agent is gated off entirely. The restriction was introduced because Seer's org-wide context engine indexes data across all projects, and with closed membership it cannot safely assume a given user has access to every project in that index.

Gap

Closed Team Membership is a deliberate access control choice — not a misconfiguration. Common reasons organizations disable it include:

• Contractors and external collaborators scoped to only specific projects
• Compliance and data separation requirements between teams or business units
• Enterprise security policies that require explicit team membership for project visibility

These organizations have a legitimate need for Seer Agent but are completely blocked by this prerequisite. The current behavior treats a valid security posture as an incompatibility rather than a constraint to work within.

Options

• Project-scoped context: Build context using only the projects the requesting user has access to, rather than org-wide indexing. This is the correct long-term fix and removes the membership dependency entirely.
• Opt-in with caveats: Allow Seer Agent for closed-membership orgs with a reduced feature set (e.g. no org-wide context, query tools only), surfacing a warning that context quality may be limited.

No files, tests, or entry points are named. First determine whether the project will use project-scoped context or an opt-in reduced feature set, then locate the existing Open Team Membership gate and related Seer Agent access checks. Done means closed-membership organizations can use the chosen supported behavior without exposing projects the requesting user cannot access.