Document dashboard-owned connection status route

[kriptoburak]

Documents the account connection-attempt status endpoint as dashboard-owned so the public skill matches the canonical API without exposing it as an agent workflow. Tests and reproducibility checks pass.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

Note

Document GET /x/account-connection-attempts/{id} endpoint in X accounts API reference

Adds the GET /x/account-connection-attempts/{id} route to the API endpoint list in api-endpoints-x-accounts.md. This documents the dashboard-owned connection status route that was previously undocumented.

^{Macroscope summarized 94f0225.}

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}

[furkanerday]

DCO blocker: human-authored commit 871de11 has no author-matching Signed-off-by trailer. The contributor must amend and re-push that commit with their own valid sign-off; a later commit cannot cure it.

[kriptoburak]

Rewrote the PR commits without changing the patch to add exact author-matching DCO trailers, and rebased onto the current base branch. Fresh hosted checks can now validate the rewritten history.

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[coderabbitai]

Warning

Review limit reached

@kriptoburak, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 49 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: bf638743-4140-4a37-86b3-94b5a07566c7

📥 Commits

Reviewing files that changed from the base of the PR and between 7b8780f and 94f0225.

📒 Files selected for processing (1)

• skills/x-twitter-scraper/references/api-endpoints-x-accounts.md

---

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

Dismissed after verifying every affected commit on the current head has an exact author-matching Signed-off-by trailer. Independent re-review remains requested.

[furkanerday]

Reviewed the complete current diff, description, commit history, checks, discussion, repository policy, relevant contracts and tests, dependency and release integrity, licensing, DCO, and public-safety implications. Required checks are green and no actionable review threads remain.

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.