{"version":3,"file":"chrome-density.d.ts","sourceRoot":"","sources":["../../src/core/chrome-density.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAEH,sEAAsE;AACtE,eAAO,MAAM,gBAAgB,sCAAuC,CAAC;AAErE,MAAM,MAAM,aAAa,GAAG,CAAC,OAAO,gBAAgB,CAAC,CAAC,MAAM,CAAC,CAAC;AAE9D,wBAAgB,eAAe,CAAC,KAAK,EAAE,OAAO,GAAG,KAAK,IAAI,aAAa,CAEtE","sourcesContent":["/**\n * The chrome dial's stops.\n *\n * Lives in `core` next to `tool-output-view.ts` for the same reason that one\n * does: the settings manager has to read and validate the value, and the\n * settings manager must not reach up into `modes/interactive`. The policy that\n * turns a stop into a layout is up there, in `interactive/chrome.ts`, where it\n * belongs — this file is only the vocabulary they share.\n */\n\n/** In the order the dial steps through them, most chrome to least. */\nexport const CHROME_DENSITIES = [\"full\", \"compact\", \"bare\"] as const;\n\nexport type ChromeDensity = (typeof CHROME_DENSITIES)[number];\n\nexport function isChromeDensity(value: unknown): value is ChromeDensity {\n\treturn typeof value === \"string\" && (CHROME_DENSITIES as readonly string[]).includes(value);\n}\n"]}