docs(ai): improve onboarding steps (agent)

- Fix Tailwind build warning by using pixel units for screens in `tailwind.config.cjs`.
- Update `CONTRIBUTING.md` to recommend sharded unit tests to avoid timeouts.
- Add `docs/onboarding-audit-20260128.md` with full audit report.

Co-authored-by: PR0M3TH3AN <[email protected]>

docs/onboarding-audit-20260128.md

@@ -0,0 +1,61 @@
+# Onboarding Audit Report - 2026-01-28
+
+## Executive Summary
+
+This report documents the results of a "fresh checkout" onboarding audit for the bitvid repository. The audit simulated the experience of a new developer setting up the project for the first time, following the instructions in `README.md` and `CONTRIBUTING.md`.
+
+**Overall Status**: ✅ Success (with minor adjustments)
+
+All core onboarding steps (`npm ci`, `npm run build`, `npm run format`) completed successfully. One build warning was identified and resolved. Documentation was updated to better manage expectations regarding unit test execution times.
+
+## Audit Environment
+
+- **Date**: 2026-01-28
+- **OS/Environment**: Linux (Simulated CI/Sandboxed Environment)
+- **Node Version**: v22 (matching `.devcontainer` and `package.json` expectations)
+
+## Step-by-Step Verification
+
+### 1. Dependency Installation
+**Command**: `npm ci`
+**Result**: ✅ Success
+- Installed 314 packages.
+- No vulnerabilities found.
+
+### 2. Build Process
+**Command**: `npm run build` (alias for `npm run build:css`)
+**Result**: ⚠️ Success with Warning (Resolved)
+- **Initial Outcome**: The build succeeded, but Tailwind emitted a warning:
+  > `warn - The min-* and max-* variants are not supported with a screens configuration containing mixed units.`
+- **Root Cause**: `tailwind.config.cjs` defined custom screens using `rem` units (`xs: "30rem"`, `compact: "25rem"`) while extending the default `px`-based configuration.
+- **Fix Applied**: Converted custom screen definitions to pixels (`xs: "480px"`, `compact: "400px"`) in `tailwind.config.cjs`.
+- **Verification**: Re-running `npm run build:css` produced a clean output with no warnings.
+
+### 3. Formatting
+**Command**: `npm run format`
+**Result**: ✅ Success
+- Prettier ran successfully on CSS, tokens, HTML, and Markdown files.
+
+### 4. Unit Tests
+**Command**: `npm run test:unit`
+**Result**: ⚠️ Timeout (Expected/Known Issue)
+- **Observation**: The full unit test suite timed out in the resource-constrained test environment.
+- **Action**: Updated `CONTRIBUTING.md` to explicitly recommend running tests in shards (e.g., `npm run test:unit:shard1`) for local development, consistent with CI practices.
+
+## Dev Container Verification
+
+The repository includes a `.devcontainer` configuration that appears robust and follows best practices:
+- **Base Image**: `mcr.microsoft.com/devcontainers/javascript-node:22` (Matches project Node requirement).
+- **Features**: Includes GitHub CLI.
+- **Post-Create Command**: Automates `npm ci`, `npm run build`, and `npx playwright install`.
+- **Extensions**: Pre-installs relevant VS Code extensions (Prettier, Tailwind, Stylelint).
+
+**Conclusion**: No changes were needed for the devcontainer configuration.
+
+## Summary of Changes
+
+1.  **Code**: Modified `tailwind.config.cjs` to use consistent pixel units for screen breakpoints, eliminating build warnings.
+2.  **Documentation**: Updated `CONTRIBUTING.md` to:
+    - Warn about potential timeouts when running the full unit test suite.
+    - Recommend `npm run test:unit:shard1` as a faster alternative for local verification.
+    - Update the PR submission checklist to reflect these testing options.