Promote staging to production

[DecisionNerd]

Release inventory

• PR Fix docs logo placement #20: restore native DocSlime header text with the compact slime mark, move the responsive SVG wordmark above the hero, widen both SVG canvases, and regenerate the unclipped 2736x768 PNG
• PR docs: suggest release conventions #21: suggest Semantic Versioning and Conventional Commits as optional publishing practices while preserving existing team workflows and requiring agreement before enforcement

Staging evidence

• staging commit: f92aeae
• staging push CI: passed CLI, site, agent skills, and branch policy
• Vercel preview: Ready; build logs confirm Branch staging and Commit f92aeae with 16 generated pages
• authenticated smoke: homepage and publishing routes returned 200
• homepage retains native DocSlime title, adds the compact slime mark, and includes light/dark hero SVGs
• deployed SVG assets match source byte-for-byte
• deployed PNG is 2736x768 and matches source SHA-256 a626b221ab4f71529da0427aff02b54aa267c03573cee7e35aaebc3be68cade6
• publishing page presents SemVer and Conventional Commits as suggestions rather than requirements

Local gates

• cargo fmt --check
• cargo test (23 tests)
• cargo clippy --all-targets -- -D warnings
• npm ci
• npm run build (16 pages)

Production smoke plan

• tie Vercel production deployment to the final main merge commit
• verify homepage header/hero behavior and publishing guidance
• verify light/dark SVGs and PNG type, dimensions, and exact hash
• verify core routes, sitemap, and robots.txt

Note

Promote staging to production with optional SemVer/Conventional Commits guidance

• Adds FR-22 across requirements, skill guidance, lifecycle docs, and templates, framing Semantic Versioning and Conventional Commits as optional recommendations rather than enforced standards.
• Updates docs/engineering/PUBLISHING.md and templates/engineering/PUBLISHING.md with a dedicated section explaining both conventions and explicitly prohibiting enforcement or history rewrites without team agreement.
• Adds a new integration test in tests/cli.rs asserting that generated publishing docs and the fill skill present these conventions as optional.
• Replaces the logo config block in docmd.config.json with a custom CSS entry, and adds docs/assets/styles/docslime.css with sidebar icon styles, hero wordmark classes, and dark-mode handling.

^{Macroscope summarized f92aeae.}

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
docslime	Ready	Preview, Comment	Jul 14, 2026 5:50pm

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 32 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

Run ID: b3432174-14d2-4fd8-8d28-4fe569993b0d

📥 Commits

Reviewing files that changed from the base of the PR and between 0294401 and f92aeae.

⛔ Files ignored due to path filters (3)

• docs/assets/images/docslime-wordmark-dark.svg is excluded by !**/*.svg
• docs/assets/images/docslime-wordmark.png is excluded by !**/*.png
• docs/assets/images/docslime-wordmark.svg is excluded by !**/*.svg

📒 Files selected for processing (11)

• .agents/skills/docslime-fill/SKILL.md
• docmd.config.json
• docs/REQUIREMENTS.md
• docs/assets/styles/docslime.css
• docs/engineering/PUBLISHING.md
• docs/engineering/TESTING.md
• docs/index.md
• docs/lifecycle.md
• templates/README.md
• templates/engineering/PUBLISHING.md
• tests/cli.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch staging

---

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