[lilyshen0722]

Written by Wren, a Commonly agent — https://commonly.me/v2/pods/6a8f6dc7a1dccf2e02f31015

Summary

Draft fallback for the v3.0.0 freeze. The 11 first-touch claims on the connectors page are still unwalked on prod, so they are not shown as TRUE. The cut for these rows moves to the freeze. If a row is still unwalked or FALSE at the freeze, this PR is the cut. Do not merge before then.

• docs-site/concepts/connectors.mdx becomes a claim-free stub.
• docs/audits/claim-table.md: the 11 rows change to CUT. Dates are unchanged.

The other six connector CUT rows were already removed from the pages by #2817.

If a row is walked before the freeze

Its row changes to the walked verdict with the walk evidence, and its sentence goes back on the page in the same PR.

Copy review

The stub wording is the whole page:

• title: Connectors
• description: This page is being rewritten.
• body: This page is being rewritten.

🤖 Generated with Claude Code

[coderabbitai]

No actionable comments were generated in the recent review.

Recent review info

Run configuration

• Source mode: Auto
• Repository: Team-Commonly/commonly
• Branch: wren/connectors-mdx-stub-draft
• File: .coderabbit.yaml
• Commit: 7816939
• Layers: Repository YAML
• Review profile: QUIET
• Plan: Advanced
• Run ID: 00a15417-e6cd-47d8-844a-86998b5450f2

Commits

Reviewing files that changed from the base of the PR and between 9823d2b and 7816939.

Files selected for processing: 2

• docs-site/concepts/connectors.mdx
• docs/audits/claim-table.md

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 8 remain after this review.

Walkthrough

The connectors page now displays a rewrite notice instead of connector descriptions and links. The audit table marks specified connector claims as CUT and records that they were not walked by the v3.0.0 freeze.

Changes: Connector documentation and audit

Layer / File(s)	Summary
Update connector page and claim status docs/audits/claim-table.md, docs-site/concepts/connectors.mdx	The page replaces connector descriptions and links with a rewrite notice. The audit rows mark specified claims as CUT and state that they were not walked by the v3.0.0 freeze.

Priority: Low

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Other

Possibly related PRs

• Team-Commonly/commonly#2817: Introduced the connector page claims and audit rows updated here.
• Team-Commonly/commonly#2501: Introduced the connectors overview and sentences removed here.
• Team-Commonly/commonly#2777: Defines the audit rules applied to these connector claims.

Merge Risk: Minimal · up to 78169

The documentation fallback is internally consistent and presents no actionable merge risk.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title clearly identifies the documentation change, the connectors page, the fallback stub, and the v3.0.0 freeze.
Description check		The description directly explains the fallback stub, the 11 claim-table changes, the freeze condition, and the draft merge restriction.
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}

[lilyshen0722]

GTM copy review. The stub is fine as a cut. Two edits and one dependency.

1. Give a launch-day reader somewhere to go. "This page is being rewritten." shows up in search and in the description, and it's a dead end. A claim-free version:

• title: Connectors
• description: Connecting a pod to other services.
• body: This page is being updated and will be back after the v3.0.0 release. To ask about a specific service in the meantime, [open an issue on GitHub](https://github.com/Team-Commonly/commonly/issues).

No claim about what connects or how. It just says the page is coming back and where to ask.

2. The same cut has to reach two other surfaces, or they'll claim what this page drops. If the "Tools let an agent read or act in another service after the connection owner grants access" row is CUT at the freeze:

• frontend/src/content/landing-faq.json FAQ 6 ends "a connector grant lets an agent use the tools you pick, through your account, without handing over your keys". That clause would need to go in the same PR (I'll send the copy).
• The launch clip v3 VO "Then give the pod the tools it needs" and its connectors crop. Launch would drop the line and the crop.

If the rows are walked TRUE after tonight's deploy, none of this applies.

Otherwise ok.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MDs9DQ4A4V1Vdp54isbxo5

[lilyshen0722]

wren, here are the TASK-014 walk results for connectors.mdx, for your keep-or-cut call by 17:00 PT. GTM walked them read-only on prod 4fd217a (Deploy Dev 08:33Z), signed in as a non-author walk account. Notes and 1440/390 shots are in the operator's walk folder; CTO has them.

Walked and passing (keep):

• rows 1 (Open Connectors), 4 (channels vs tools), 7 (an admin installs the GitHub App) and 11 (the grants guide covers limits and revoke)
• rows 3, 9 and 10 (the Linear tools grant, connect, and read grant to an eligible pod), via the D146 Linear walk

Not walked, so cut them or mark them unavailable, the same as the earlier CUT rows:

• Row 2: channels carry messages between a pod and an outside chat. No live Slack or Telegram connection was run.
• Row 5: Telegram, binding a private chat. The pod picker shows, but the bind wasn't run.
• Row 6: Slack, authorizing a workspace. The Add button shows, but OAuth wasn't started.
• Row 8: GitHub App, the connection owner grants tools. The app isn't installed for the walk account.

Airtable (from CTO): cut any Airtable row, or mark it unavailable. It fails before its consent screen (TASK-318), and its hide (#2898) reaches prod in tonight's batch. Prod 4fd217a still lists it under Tools.

So the page can keep Linear (connect, then grant read access to an invite-only pod) as the one walked tool, plus the Connectors page layout. Don't use any "any app" wording.

[lilyshen0722]

Superseded by #2899, which cuts connectors.mdx from today's walk evidence instead of shipping the freeze stub.