fix(search): verify Atlassian access and clarify source setup

[waleedlatif1]

Summary

• Require current Confluence site access under the reader's own identity, preserve it across search, document, file, and count paths, and keep checks bounded.
• Use Jira project keys consistently without changing workflow selectors. Prevent stale OAuth attempts and loading states from showing incorrect connection errors.
• Clarify product-specific token permissions, trim setup guides, refresh focused screenshots, and add missing Slack credential placeholders.
• Repair integration fixtures for current authorization and provider behavior, and run workspace suites with their dedicated setup.

Type of Change

• Bug fix

Testing

• Fresh live connection, indexing, update, permission-removal/restoration, and cited-answer checks with synthetic Atlassian content.
• CI test shard 2 passed locally: 15,225 tests. Additional regressions cover pending OAuth response order, final v1 access denial, and Confluence-filtered candidate authorization.
• Full knowledge integration passed: 337 tests plus 27 SQL tests; dedicated workspace integration passed 28 tests. Required PostgreSQL suites passed with both schema push and versioned migrations. Existing opt-in live/scale suites remain skipped.
• App and docs type checks, cleanup review, lint, API boundary validation, all 46 repository audits, block registry, and generated-artifact checks passed.
• Additional existing credential and Slack component tests passed; current setup screenshots verified against the rendered UI.
• Final parallel audit accounts for every changed file. No local build ran for this review round. The new site-access guard used mocked provider responses and still needs deployed verification.

Checklist

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

[vercel]

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

Project	Deployment	Actions	Updated
docs	Ready	Preview	Sep 10, 2026 11:12am UTC

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

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

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge; no outstanding behavioral, security, or repository-rule violations were identified.

Summary

• Verifies current Confluence site access under each reader’s identity with bounded, concurrent credential alternatives.
• Carries live knowledge authorization through search, document, file, and count paths.
• Prevents stale OAuth attempts and connector polling responses from presenting incorrect UI state.
• Batches knowledge-base and tag reference reads while preserving caller-visible semantics.
• Updates Jira selectors, Atlassian setup documentation, Slack credential guidance, and focused integration coverage.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[Knowledge request] --> B[Resolve principal access]
  B --> C[Collect candidate connectors and documents]
  C --> D{Confluence-backed source?}
  D -- No --> E[Apply stored access predicate]
  D -- Yes --> F[Group readers by Atlassian identity]
  F --> G[Verify current site access with bounded alternatives]
  G --> H[Create site-scoped reader grants]
  H --> E
  E --> I[Return only currently readable results]

Loading

_{Reviews (2) · Last reviewed commit: "fix(search): close authorization races a..."}

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

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