This is the working repository of the W3C CSS Houdini Task Force: a collection of editor's drafts (specifications) for browser APIs that expose CSS internals to JavaScript. The content is written in Bikeshed (.bs) format and processed by a Python build pipeline (bin/build-markdown.py, bin/build-index.py, Makefiles, GitHub Actions) into the HTML specs served via GitHub Pages. The repository contains formal, normative algorithm definitions for the CSS Paint API (registerPaint), CSS Layout API (registerLayout), CSS Animation Worklet (registerAnimator), CSS Properties & Values API, CSS Typed OM, Font Metrics API, Box Tree API, and Worklets. It is not a runtime application or a data pipeline — it is documentation-as-code with build automation and small runnable examples — but it is classified as "application" because its dominant content is executable artifacts (worklet demo code, CI scripts, build tooling) rather than data assets. The highest-craft content is in the spec sources: the CSS Typed OM draft defines a complete, self-contained algebra for CSS numeric values (base types, percent hints, sum values, unit conversion, canonical units) plus a reify/serialize pair that converts between internal CSS representations and typed JavaScript objects. The CSS Layout API draft specifies a work-queue processing model, global scope selection, and structured serialization for worklet data — all reusable algorithmic patterns for browser-engine implementers and polyfill authors. The included paint-worklet demos (circle, arc, chat) are isolated, copy-pasteable examples of the registerPaint contract. Maintenance is active: the last commit is recent, the Typed OM changes section references live GitHub issues/PRs, and the CI installs pinned dependencies. However, there is notable internal drift: css-parser-api has been moved to WICG (its Overview.bs is blank), worklets/Overview.bs now redirects to the HTML Standard, scroll-customization-api remains an explainer without a formal spec, and several Typed OM reification entries are explicitly empty stubs or marked with open issue markers. The 2018 issue-list artifacts and README_old.md files add historical clutter. For engineers, the practical value is threefold: (1) reference implementations of the Houdini API surface for anyone building polyfills, browser features, or CSS tooling; (2) a clean, reusable Bikeshed-spec build/deploy pipeline (Python scripts + GitHub Action) that can be extracted to any W3C-style spec repo; and (3) minimal worklet starter examples. It is not code you deploy — it is a standards workshop, and the quality bar is standards-writing rigor rather than software architecture.