Migrate DOMStack to mine.css v11

[dependabot]

Summary

• upgrade the bundled and example styles from mine.css v10 to v11
• replace removed JavaScript theme switching with browser-controlled color preferences
• establish and document the recommended mine, domstack.global, domstack.layout, and domstack.page cascade pattern
• migrate global, layout, and page styles in examples and test fixtures to the matching layers
• load light and dark Highlight.js themes with prefers-color-scheme
• add Playwright coverage for the computed mine → global → layout → page cascade
• document downstream migration requirements for DOMStack v12

Downstream changes

DOMStack v12 consumers using the bundled default stylesheet inherit mine.css v11's intentional visual, motion, form, table, media, and browser-support changes.

Customized or ejected sites should follow docs/v12-migration.md and the upstream mine.css v11 migration guide.

Custom stylesheets are encouraged to follow this pattern:

@layer mine, domstack.global, domstack.layout, domstack.page;

@layer domstack.global {
  /* global rules */
}

Layout and page styles should opt into domstack.layout and domstack.page respectively.
DOMStack loads global styles first so the complete order is declared before layout and page layer blocks are encountered.

Validation

• npm test
• npm run build
• Playwright cascade test in Chromium
• full stylesheet scope audit
• git diff --check

Notes

• mine.css v11 requires Node.js 22+ and npm 10+ for installation.
• Published mine.css uses native CSS nesting.
• The temporary DOMStack fragment-offset override was removed after mine.css changed its default from 3rem to 2rem upstream in 2140f6f.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​playwright/​test@​1.61.1

View full report

[coveralls]

Coverage Report for CI Build 29620826912

Warning

No base build found for commit 09bdc51 on master.
Coverage changes can't be calculated without a base build.
If a base build is processing, this comment will update automatically when it completes.

Coverage: 91.885%

Details

• Patch coverage: 1 of 1 lines across 1 file are fully covered (100%).

Uncovered Changes

No uncovered changes found.

Coverage Regressions

Requires a base build to compare against. How to fix this →

---

Coverage Stats

Relevant Lines:	4293
Covered Lines:	4042
Line Coverage:	94.15%
Relevant Branches:	747
Covered Branches:	589
Branch Coverage:	78.85%
Branches in Coverage %:	Yes
Coverage Strength:	73.97 hits per line

---

💛 - Coveralls

[dependabot]

A newer version of mine.css exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.