chore(deps): upgrade cssnano 7.1.9 → 8.0.1

[pftg]

Summary

• Bumps cssnano devDependency from ^7.1.9 to ^8.0.1.
• v8's only breaking change relevant to a default preset config is the removal of cssDeclarationSorter. Our postcss.config.js never enabled it, so the only behavioral change is that minified CSS now preserves source declaration order instead of alphabetizing.
• Sub-plugins all bumped to v8.x in lockstep (postcss-merge-longhand@8, postcss-minify-selectors@8.0.1, etc.); none of the option keys we pass (discardComments, mergeLonghand, svgo: false, zindex: false, …) were renamed.

Equivalence verification

Check	Result
All 17 production CSS bundles, byte size	Identical (Δ=0 each)
Token-sorted MD5 of v7 vs v8 per bundle	17/17 match → pure declaration reordering
Cascade flip risk from reordering	None: discardDuplicates: true already removes same-property duplicates within rules
bin/dtest (Linux/Docker visual regression)	42 runs, 116 assertions, 0 failures, 0 errors; snap_diff: 84 screenshots compared, no failures
Hugo production build	Clean (1012 pages, 28.9s)

Hugo content hashes change (different bytes → different fingerprints), so all CSS asset URLs rotate on first deploy. Expected and harmless.

Test plan

• Production build: ENVIRONMENT=production bin/hugo-build → clean
• CSS diff vs master: 17/17 bundles token-equivalent
• bin/dtest Linux/Docker visual regression: 0 failures, 84 screenshots clean
• CI green on this branch before merge

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation

  • Simplified and streamlined LinkedIn post content for improved clarity and engagement.

• Chores

  • Updated development and production dependencies to latest versions.

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR updates a LinkedIn post draft about vibe-coding and maintenance code to a simplified third revision, tightening the call-to-action, notes, opening, and closing. It also bumps three npm package versions to newer releases for improved tooling.

Changes

Content and Dependency Maintenance

Layer / File(s)	Summary
Backlog Post Refinement linkedin-posts/icp-validation/backlog-vibe-coding-disposable.md	Front-matter CTA is shortened. The notes section is rewritten from a detailed "second pass" reframing narrative into a concise "third pass" opener and voice guidance. Body paragraphs are tightened: "Three founders messaged me" is replaced with "For the last 3 months", maintenance explanation is condensed, and the closing becomes a two-part "what did you keep / what did you throw away?" question.
NPM Dependency Updates package.json	cssnano bumped from ^7.1.9 to ^8.0.1, lighthouse from ^13.2.0 to ^13.3.0, and caniuse-lite from ^1.0.30001791 to ^1.0.30001792.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A rabbit hops through revisions three,
Trimming words with clarity,
Snipping tales that don't belong,
Dependencies dance along—
Simpler drafts, fresher tools, strong! 🐰✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title focuses on cssnano upgrade but the changeset also includes lighthouse and caniuse-lite updates, plus a markdown content update.	Update the title to reflect all significant changes, e.g., 'chore(deps): upgrade cssnano, lighthouse, and caniuse-lite' or include the markdown update if it's a primary change.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/upgrade-cssnano-v8

---

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 and usage tips.}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

linkedin-posts/icp-validation/backlog-vibe-coding-disposable.md (1)

1-43: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

PR scope mismatch: this content change does not align with the dependency-upgrade objective.

On Line 1 through Line 43, this PR modifies a LinkedIn draft post, while the stated objective is a cssnano dependency bump. Please move this markdown edit to a separate content PR (or update PR title/objectives to reflect mixed scope) so release risk and review intent stay clear.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@linkedin-posts/icp-validation/backlog-vibe-coding-disposable.md` around lines
1 - 43, This PR accidentally includes a content change (the LinkedIn draft with
frontmatter including "week: 1-extra" and the post opening "For the last 3
months I've gotten...") that doesn't match the repo's stated objective of a
cssnano dependency bump; move the markdown edit out of this dependency PR into a
separate content PR (or adjust this PR's title/description to explicitly include
the content change) so reviewers and release tooling only see related changes
together; ensure the file edit to the draft (the markdown block starting with
the frontmatter keys like hypothesis: H3, H4 and the post body) is removed from
this branch/commit or split into a new branch/PR before merging.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@linkedin-posts/icp-validation/backlog-vibe-coding-disposable.md`:
- Around line 1-43: This PR accidentally includes a content change (the LinkedIn
draft with frontmatter including "week: 1-extra" and the post opening "For the
last 3 months I've gotten...") that doesn't match the repo's stated objective of
a cssnano dependency bump; move the markdown edit out of this dependency PR into
a separate content PR (or adjust this PR's title/description to explicitly
include the content change) so reviewers and release tooling only see related
changes together; ensure the file edit to the draft (the markdown block starting
with the frontmatter keys like hypothesis: H3, H4 and the post body) is removed
from this branch/commit or split into a new branch/PR before merging.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: d14a5f0b-5b93-4c52-8156-58b679268adc

📥 Commits

Reviewing files that changed from the base of the PR and between f05e171 and 1ed484d.

⛔ Files ignored due to path filters (1)

• bun.lockb is excluded by !**/bun.lockb

📒 Files selected for processing (2)

• linkedin-posts/icp-validation/backlog-vibe-coding-disposable.md
• package.json