[willwashburn]

Summary

• restore visible disc markers for unordered lists in docs articles
• color unordered-list markers with the docs primary blue token
• restore decimal markers for ordered lists

Why

Tailwind's reset removes the browser's default list styles. The docs article styles added indentation but did not restore marker types, which made lists look like disconnected paragraphs.

Impact

Lists are visually distinct and scannable across core and product docs pages, while navigation and table-of-contents lists remain unchanged.

Validation

• npm --workspace web run test — 21 tests passed
• npm run build — passed
• visually verified /docs/messaging and /docs/loop/introduction

---

Summary by cubic

Restore visible list markers in docs articles: disc bullets (styled with the docs primary blue) for unordered lists and decimals for ordered lists. Improves readability in article content while leaving navigation and table-of-contents lists unchanged.

^{Written for commit 9d13b9f. Summary will update on new commits.}

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 51 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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0732a5a1-422d-4a6d-859b-3f365049c171

📥 Commits

Reviewing files that changed from the base of the PR and between 6f1d77d and 9d13b9f.

📒 Files selected for processing (1)

• web/components/docs/docs.module.css

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch agent/docs-list-markers

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[github-actions]

Preview deployed!

Environment	URL
Web	https://cdec08f5-agentrelay-web.agent-workforce.workers.dev

This is a Cloudflare Workers preview version of this PR's build.

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}