/*
 * What Tailwind's utilities do not cover, in ten files.
 *
 * Still one <link> in the page: the browser resolves these imports itself, and keeping the entry
 * point single means the load order is stated here rather than left to the order the tags happen
 * to be in. base.css comes first because it defines the tokens the others read.
 *
 * Why plain CSS at all, and why the tokens are repeated here rather than read from Tailwind's
 * @theme, is explained at the top of base.css.
 */
@import "./css/base.css";
/* Second, and before anything that draws a form: base.css defines the tokens a field reads, and
   every file below this one either uses .field or wraps something in .field-box. */
@import "./css/fields.css";
@import "./css/run.css";
@import "./css/prose.css";
@import "./css/chrome.css";
@import "./css/sidebar.css";
@import "./css/composer.css";
@import "./css/detail.css";
@import "./css/knowledge.css";
/* After detail.css and knowledge.css: Customize builds on the record card's vocabulary and ties
   with both on specificity, so it has to be the later rule where the two meet. */
@import "./css/customize.css";
@import "./css/busy.css";