fix(selectors): resolve shared environment references server-side

[BillLeoutsakosvl346]

Summary

Adds the shared, authorized infrastructure for dependent selectors whose context may contain environment-secret references. This PR contains no Jira, Confluence, JSM, Slack, CloudWatch, or IMAP selector migration; those are independent sibling PRs stacked on this branch.

The browser carries literals or opaque exact {{KEY}} references only. Authorized resolution happens server-side, and resolved shared-secret plaintext never enters selector query keys, responses, or client state.

Shared infrastructure in this PR:

• serverResolvedContextFields metadata and exact-reference preservation
• Principal-based workflow/credential authorization
• active readable workflow scope, delegated executor scope, and session-only workflowless credential scope
• canonical workspace derivation and workflow/credential workspace agreement
• effective environment resolution with workspace-over-personal precedence and existing shared-secret membership filtering
• credential provider matching before token or service-account secret access
• cache partitioning by workspace, workflow, and opaque dependency revision
• knowledge-connector cache revisions derived only from each selector server-resolved dependency fields, so unrelated connector edits do not churn selector identity
• successful personal/workspace environment mutations refresh their environment query first, then invalidate primary selectors, canvas detail labels, and workflow-search selector caches without changing opaque query keys
• successful Copilot personal-secret updates refresh both personal and workspace-environment queries; Copilot workspace-secret updates refresh the canonical workspace query before the same selector invalidation
• complete selector-query reset during user-data reset
• shared Atlassian credential binding, sanitized discovery mode, provider-error mapping, and provider-owned selector contract map composition used by the Jira/Confluence and JSM children

Slack report: https://sim-ai.slack.com/archives/C093DF8MA21/p1786822370070229

Security invariant

• Route adapters authenticate before parsing and reuse the authenticated session or executor principal.
• Workflow selectors require an active workflow the principal may read.
• Workflowless selectors require a session principal and an authorized credential; direct-secret selectors still require a workflow.
• Credential-backed requests use existing credential-use authorization and enforce workflow/credential workspace agreement.
• Provider compatibility is checked before token refresh or service-account secret access.
• Only exact whole-value references resolve; missing and inaccessible references return the same sanitized error.
• Resolved values never return to the browser or enter logs/query keys.
• Atlassian provider response bodies are neither returned nor logged; sanitized non-2xx bodies are best-effort cancelled without inspection.
• Personal environment writes immediately evict the server's effective-environment cache; failed browser mutations do not invalidate selector caches.

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation
• Other: ___________

Focused coverage

• Literal passthrough; exact personal/shared references; workspace precedence; missing/inaccessible equivalence; exact-reference-only behavior.
• Active/archived workflow authorization, delegated scope, workflowless credential scope, workflow/credential workspace agreement, and direct-secret workflow enforcement.
• OAuth and Atlassian service-account provider binding plus mismatch denial before secret/provider access.
• Direct database-adapter coverage for OAuth, Atlassian and Slack service accounts, incompatible providers, and owner-scoped legacy accounts.
• One real QueryClient suite for opaque revisions, workspace/workflow separation, plaintext exclusion, and unchanged legacy keys.
• Real QueryClient mutation coverage for personal saves, workspace upserts/removals, all four selector cache families, unrelated-query isolation, and failed-mutation behavior.
• Immediate personal effective-environment cache eviction after the database write.
• User-data reset removes the entire selector query namespace.
• Server adapter authentication success/failure and the sim:selectors delegation audience.
• Exact public provider-error mappings without incidental implementation assertions.

Verification

Verified after rebuilding on the latest origin/staging:

• Focused shared Vitest: 15 files, 95 tests passed.
• Provider-focused combined selector suites: 15 files, 75 tests passed.
• Full root suite on the final combined head: 19/19 tasks; app 2,368 files passed, 3 skipped; 34,842 tests passed, 46 skipped.
• App and root type-checks passed.
• Root lint:check and format:check passed. Lint reports one unrelated existing unused-suppression warning in shell-layout.test.ts.
• Strict API validation passed: 1,213/1,213 routes Zod-backed.
• Client-boundary and React Query audits passed.
• git diff --check passed.

The final review follow-up adds behavior-level regressions for connector dependency-scoped cache identity, Copilot personal/workspace secret-update invalidation, and sanitized Atlassian response cancellation without duplicating provider matrices.

Combined browser acceptance

• Jira, Confluence, JSM, CloudWatch, Slack, and IMAP selector forms preserved literals and exact personal/shared references across the browser boundary.
• Existing Slack OAuth loaded real channel options in both a workflow and a workflowless knowledge connector.
• Changing between two deterministic invalid Slack direct tokens produced separate requests; an exact runtime block reference produced no selector request.
• CloudWatch and IMAP deterministic invalid inputs reached their dedicated selector routes and returned sanitized failures without echoing secrets.
• No selector-specific console warnings appeared and no plaintext secret values appeared in keys, responses, or server logs.
• Disposable workflow and knowledge-base data were deleted afterward; the existing Slack workflow was restored.
• Freshness follow-up smoke sent an exact missing Jira domain reference to the dedicated Project/Issue routes and surfaced only the sanitized Credential not found response. The temporary blocks and values were undone, and reload confirmed the workflow returned to its original Start-only state.
• The exact mounted same-reference mutation is covered by the real QueryClient regression because this local account cannot edit Secrets through the UI.

Intentional scope

• Exact whole-value references only; embedded interpolation is unchanged.
• Runtime tool routes, block definitions, database schemas, runtime environment resolution, and chained resource-ID selectors are unchanged.
• Provider selector migrations remain in independent child PRs.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No selector-specific warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Stacked children

Each child is a draft sibling based directly on this PR's tip. Review each diff against fix/server-resolved-selector-context; do not merge a child until #7095 lands and that child is rebased and retargeted to staging.

• fix(atlassian): resolve Jira and Confluence selector contexts server-side #7122 — Jira Project/Issue and Confluence Space/Page selectors
• fix(jsm): resolve selector contexts server-side #7114 — JSM Service Desk and Request Type selectors
• fix(slack): resolve direct-token selector contexts server-side #7115 — Slack Channel/User selectors and direct-token handling
• fix(cloudwatch): resolve selector credentials server-side #7116 — CloudWatch Log Group/Stream selectors
• fix(imap): resolve mailbox selector contexts server-side #7117 — IMAP Mailbox selector

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Aug 27, 2026 12:31am

[greptile-apps]

Greptile Summary

This PR adds shared infrastructure for resolving authorized selector environment references server-side while keeping secret values out of browser query keys and state.

• Adds principal-, workflow-, workspace-, and credential-aware selector context authorization.
• Introduces opaque browser cache partitions and environment-mutation invalidation across selector query families.
• Adds sanitized Atlassian credential discovery, provider binding, and provider-error handling.
• Clears server-state queries during user-data reset and refreshes the effective environment cache after personal environment writes.

Confidence Score: 5/5

The PR appears safe to merge; no concrete changed-code failure remains reachable in the reviewed changes.

The authorization path derives canonical scope before environment resolution, credential-backed requests enforce workspace agreement, and browser caches are partitioned and invalidated without exposing resolved secret values.

Important Files Changed

Filename	Overview
apps/sim/lib/selectors/application/resolve-authorized-context.ts	Adds the central authorized application operation for canonical workspace derivation, credential checks, delegated scope enforcement, and exact environment-reference resolution.
apps/sim/lib/selectors/application/credential-provider.ts	Adds provider compatibility checks before credential secret access; the helper is not yet reached by a production caller in this changeset.
apps/sim/hooks/selectors/context-resolution.ts	Preserves server-resolved references and creates stable opaque cache revisions without exposing raw dependency values in query keys.
apps/sim/hooks/selectors/use-selector-query.ts	Partitions opted-in selector caches by canonical workspace, workflow, and opaque dependency scope while retaining legacy keys for other selectors.
apps/sim/hooks/queries/environment.ts	Refreshes environment queries first and then invalidates selector-dependent caches after successful environment mutations.
apps/sim/lib/atlassian/discovery.ts	Adds a sanitized discovery mode that excludes provider-controlled response bodies from errors and separates sanitized and standard cache entries.
apps/sim/stores/index.ts	Expands user-data reset from environment-only removal to clearing the complete React Query cache.

Sequence Diagram

sequenceDiagram
    participant Browser
    participant Route as Selector route
    participant Auth as Principal authorization
    participant Env as Effective environment
    participant Provider
    Browser->>Route: "Opaque context with exact {{KEY}} reference"
    Route->>Auth: Authenticate principal and authorize workflow/credential
    Auth-->>Route: Canonical workspace and credential scope
    Route->>Env: Resolve authorized exact references
    Env-->>Route: Resolved server-only context
    Route->>Provider: Fetch selector options
    Provider-->>Route: Provider result
    Route-->>Browser: Sanitized selector options
    Note over Browser: Query key contains workspace/workflow/opaque revision, not plaintext

Loading

_{Reviews (1): Last reviewed commit: "fix(selectors): refresh caches after env..." | Re-trigger Greptile}

[cubic-dev-ai]

All reported issues were addressed across 37 files

<sub>Tip: cubic can generate docs of your entire codebase and keep them up to date. Try it here.

Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 40 files

<sub>Tip: cubic can generate docs of your entire codebase and keep them up to date. Try it here.

Re-trigger cubic</sub>

[BillLeoutsakosvl346]

Addressed the latest Cubic P2 in eb0d42e. Successful personal Copilot secret updates now invalidate both the personal environment query and the workspace-environment prefix before invalidating the four selector cache namespaces, matching the regular personal-save mutation. The focused stream suite (13 tests), app/root type-checks, lint, format, strict API validation, client-boundary, React Query audit, and diff check all pass on the rebuilt combined stack.

[BillLeoutsakosvl346]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@BillLeoutsakosvl346 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 40 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Tip: cubic can generate docs of your entire codebase and keep them up to date. Try it here.

Re-trigger cubic</sub>