v0.8.41: library, coda connector, connector sync engine hardening

[waleedlatif1]

• fix(http): substitute path parameters only by their whole name (fix(http): substitute path parameters only by their whole name #7914)
• improvement(insights): default to the last 30 days (improvement(insights): default to the last 30 days #7916)
• feat(coda): add permission-aware knowledge connector (feat(coda): add permission-aware knowledge connector #7915)
• feat(library): AI Agent Examples by Department and Industry: A Practical Roundup (feat(library): AI Agent Examples by Department and Industry: A Practical Roundup #7919)
• docs(library): update n8n-alternatives (docs(library): update n8n-alternatives #7921)
• fix(knowledge): bound permission pagination and member cleanup (fix(knowledge): bound permission pagination and member cleanup #7918)
• fix(search): isolate Google crawl failures and bound embedding writes (fix(search): isolate Google crawl failures and bound embedding writes #7920)
• fix(knowledge): preserve permission warnings in combined notices (fix(knowledge): preserve permission warnings in combined notices #7923)
• feat(library): AI-Native Workflow Automation vs Traditional Automation Platforms (feat(library): AI-Native Workflow Automation vs Traditional Automation Platforms #7925)
• fix(search): require explicit Calendar access failure reasons (fix(search): require explicit Calendar access failure reasons #7924)
• fix(knowledge): preserve permission notices and fixture isolation (fix(knowledge): preserve permission notices and fixture isolation #7926)

[vercel]

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

Project	Deployment	Actions	Updated
docs	Ready	Preview	Sep 17, 2026 8:21am UTC

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge; no concrete correctness, security, or repository-rule violation remains.

Summary

This PR adds a permission-aware Coda connector and supporting documentation, strengthens connector pagination, directory synchronization, Google Workspace failure isolation, document lifecycle processing, and embedding writes, changes Insights to default to 30 days, and updates library content.

• Registers Coda for workspace and organization Search with bounded listing, deferred hydration, source ACL mirroring, and Enterprise directory support.
• Persists bounded per-user Google listing failures so unaffected users continue syncing without unsafe deletion reconciliation.
• Hardens Confluence permission pagination and external-group synchronization against partial, repeated, or stale provider results.
• Batches embedding inserts and member-document lifecycle writes while retaining transaction and lease guards.
• Fixes HTTP path-parameter substitution so only complete parameter names are replaced.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Connector sync starts] --> B[Refresh mirrored directory]
    A --> C[List source documents]
    B --> D{Directory complete?}
    D -->|Yes| E[Replace verified memberships]
    D -->|Partial| F[Keep failed groups stale and record warning]
    C --> G[Persist listing checkpoint]
    G --> H[Hydrate changed content]
    H --> I[Resolve source ACLs]
    I --> J{Permissions verified?}
    J -->|Yes| K[Persist ACLs]
    J -->|No| L[Fail closed and record incomplete permissions]
    K --> M[Reconcile missing documents if listing is authoritative]
    L --> N[Hold deletion reconciliation]
    F --> N
    M --> O[Complete sync]
    N --> O

Loading

_{Reviews (1) · Last reviewed commit: "fix(search): isolate Google crawl failur..."}

[cubic-dev-ai]

1 issue found across 69 files

Confidence score: 3/5

• apps/sim/connectors/google-workspace/api-errors.ts can treat a matching Calendar events.list error with no reason entries as universally forbidden, suppressing 403 failures that may have other causes and misleading callers about the underlying error. Ensure reasonsComplete is only set when reasons are actually present or preserve the original error when the list is empty.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="apps/sim/connectors/google-workspace/api-errors.ts">

<violation number="1" location="apps/sim/connectors/google-workspace/api-errors.ts:89">
P2: When a Calendar `events.list` response has a matching `code` but no reason entries, this marks `reasonsComplete` true. `userListingFailure` then treats the empty array as all `forbidden` and suppresses any 403, including global failures; require a nonempty `forbidden` reason before isolating the user.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[waleedlatif1]

@cubic review

[cubic-dev-ai]

@cubic review

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

[cubic-dev-ai]

No issues found across 75 files

Confidence score: 5/5

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

_{Re-trigger cubic}