@flowstack-ui/agent-tools 0.1.0-bootstrap.0

package/public/packages/theme/0.1.1/docs/troubleshooting.txt

@@ -0,0 +1,53 @@
+# Public document: troubleshooting
+
+Source: @flowstack-ui/theme@0.1.1
+
+# Troubleshooting
+
+## Contract revision is unsupported
+
+Install a Brick release whose `theme-contract.json` has revision 2 or newer.
+Do not edit or snapshot the installed contract to bypass this check.
+
+## Brick version is incompatible
+
+Either install a Brick version accepted by `compatibility.brick` or review and
+update the theme's compatibility range after qualifying it against the newer
+contract.
+
+## Atomic family is incomplete
+
+Supply every member of the named family for that appearance, or remove all
+overrides for the family to inherit Brick's complete default.
+
+## Contrast is insufficient
+
+The diagnostic names the appearance, foreground, background, raw ratio, and
+required threshold. Adjust the semantic family while reviewing rest, hover,
+pressed, soft, and foreground values together. Do not round the ratio or add a
+local component patch.
+
+## Contrast is unverifiable
+
+Brick-declared contrast participants must resolve to opaque sRGB hex or
+`rgb()` values. Convert the accepted color to one of those exact forms.
+Transparent colors, gradients, images, color mixing, and final composition
+still require browser-level accessibility review.
+
+## A portal has the wrong appearance
+
+Render it into a container under the intended boundary or place an explicit
+theme and appearance boundary on the portal root. React context alone cannot
+transfer CSS ancestry.
+
+## The font falls back
+
+Read `theme.manifest.json` requirements and verify the application loads the
+declared family or CSS variable on the active theme boundary. Theme does not
+load font assets.
+
+## Generated files drift
+
+Compile with the same Theme version and installed Brick contract used by CI.
+Keep only one generation owner: committed artifacts plus a drift check, or CI
+generation from source.

package/public/packages/theme/0.1.1/guides/theme-system.txt

@@ -0,0 +1,340 @@
+# FLOWSTACK Theme system
+
+Source: @flowstack-ui/theme@0.1.1
+Kind: guide
+ID: theme-system
+
+# FLOWSTACK Theme system
+
+## Purpose
+
+Author, compile, and integrate a project theme without changing Brick component meaning or moving application runtime ownership into Theme.
+
+## Decision order
+
+1. Identify brand and product colors as project palettes and roles before mapping any value to Brick.
+2. If using Colors, review its candidate explicitly and scaffold selected families through the serialized file interchange.
+3. Install a released Brick version whose theme contract revision is supported by Theme.
+4. Map only UI meanings Brick owns into brick.light and brick.dark; keep charts, syntax, editorial, and campaign colors in project roles or namespaced extensions.
+5. Use appearanceRoles for optional project or package meanings that vary between light and dark, and declare their maintained foreground/background relationships explicitly.
+6. Override a complete atomic Brick family or inherit that entire family from Brick defaults.
+7. Use only Brick-declared component theme inputs and treat their closed values as project-wide policy with component props remaining available for local exceptions.
+8. Compile at build time, review the contrast report and static artifacts, then ship the CSS rather than the compiler.
+9. Let the application own activation, saved preference, fonts, assets, portals, and first-paint behavior.
+
+## Selection map
+
+- **Author a deterministic theme source:** use defineTheme with the flowstack.theme.v1 schema and JSON-compatible values.
+- **Check a theme definition before compatibility work:** use validateThemeDefinition for diagnostics or assertThemeDefinition for a throwing boundary.
+- **Qualify Theme against Brick:** use load and assert the theme-contract.json belonging to the exact installed Brick version.
+- **Start from generated Colors candidates:** use the serialized, explicitly reviewed Colors candidate and scaffold mapping handoff.
+- **Resolve semantic values and prove completeness and contrast:** use compileTheme against the selected installed Brick contract.
+- **Produce files for an application build:** use compileThemeFiles and writeThemeArtifacts for the complete deterministic CSS, token, manifest, and report set.
+- **Validate, scaffold, or compile from automation:** use the flowstack-theme CLI with explicit JSON, contract, mapping, and output paths.
+- **Activate a compiled theme or choose product-specific brand direction:** use application-owned runtime and authorized project inputs after Theme emits static artifacts.
+
+## Rules
+
+- **MUST:** Keep theme definitions JSON-compatible and deterministic; do not use functions, DOM state, environment-dependent values, or runtime callbacks.
+- **MUST:** Compile against the theme-contract.json exported by the installed Brick package and do not maintain a copied semantic-token list.
+- **MUST:** Treat Colors as optional serialized file input; never add a Colors runtime dependency or map an unreviewed candidate.
+- **MUST:** When one member of an atomic Brick color family changes, provide the complete family for that appearance or inherit the complete Brick default.
+- **MUST:** Map values by semantic UI meaning; never misuse warning, danger, success, or information merely to obtain a desired hue.
+- **MUST:** Keep unlimited non-Brick brand, visualization, syntax, editorial, and product colors in palettes, roles, or namespaced extensions.
+- **MUST:** Treat insufficient or unprovable Brick-declared and project-declared contrast pairs as build failures; do not round a failing ratio into a pass.
+- **MUST:** Define every appearance-aware project role for every supported appearance, keep its logical meaning stable, and do not duplicate the same path in invariant roles.
+- **MUST:** Ship compiled static CSS and keep @flowstack-ui/theme in build tooling unless a separately qualified runtime adapter is introduced.
+- **MUST:** Keep theme selection, persistence, pre-paint setup, font and asset loading, and portal-container coordination in the application.
+- **MUST:** Do not add theme breakpoints expecting them to recompile Brick media queries; Brick component breakpoints and application layout policy have separate owners.
+- **SHOULD:** Use components only for inputs explicitly audited in the Brick contract; honor closed allowed values and their conditional validation, and keep local component token overrides local.
+
+## Ownership
+
+### Brick
+
+- accessible default values
+- semantic UI roles and component recipes
+- atomic families, contrast pairs, and approved component inputs
+
+### Theme
+
+- serializable project values and mappings
+- compatibility, completeness, alias, and contrast validation
+- appearance-aware project roles and explicit project relationships
+- deterministic CSS, token, manifest, and report artifacts
+
+### Application
+
+- activation and saved preference
+- font and asset loading
+- first paint, portals, routes, and product art direction
+
+## Native and application fallback
+
+1. Check whether the task is deterministic Theme authoring, validation, compatibility, compilation, artifact writing, or CLI automation before using this package.
+2. Use application-owned integration for runtime activation, persistence, first paint, fonts, assets, portal placement, routes, and product-specific art direction.
+3. Report a Theme or Brick contract gap instead of copying semantic tokens, weakening validation, inventing brand decisions, or shipping the compiler in the browser.
+
+## Validation checklist
+
+- Validate the definition envelope before compiling.
+- When using Colors interchange, confirm the candidate review and scaffold report identify the intended families and semantic jobs.
+- Compile against the exact installed Brick contract revision and review every diagnostic.
+- When a categorical component input activates conditional validation, confirm every resulting contrast pair passes in every supported appearance.
+- Confirm every appearance role is complete and every declared project relationship passes in every supported appearance.
+- Confirm theme.report.json contains one passing result for every declared pair and supported appearance.
+- Verify generated artifacts are byte-stable and committed only when the application owns committed build output.
+- Build the production application and verify explicit light, dark, nested appearance, portal, first-paint, and forced-colors behavior where applicable.
+- Confirm the browser bundle does not contain the Theme compiler.
+
+## Related guidance
+
+- `theme-definition (operation)`
+- `theme-validation (operation)`
+- `brick-contract-compatibility (operation)`
+- `colors-interchange (operation)`
+- `theme-compilation (operation)`
+- `theme-artifacts (operation)`
+- `theme-cli (operation)`
+- `application-theme-runtime (native/application)`
+
+## Machine record
+
+```json
+{
+  "schema": "flowstack.agent-guide.v1",
+  "id": "theme-system",
+  "name": "FLOWSTACK Theme system",
+  "package": "@flowstack-ui/theme",
+  "layer": "theme",
+  "kind": "guide",
+  "purpose": "Author, compile, and integrate a project theme without changing Brick component meaning or moving application runtime ownership into Theme.",
+  "decisionOrder": [
+    "Identify brand and product colors as project palettes and roles before mapping any value to Brick.",
+    "If using Colors, review its candidate explicitly and scaffold selected families through the serialized file interchange.",
+    "Install a released Brick version whose theme contract revision is supported by Theme.",
+    "Map only UI meanings Brick owns into brick.light and brick.dark; keep charts, syntax, editorial, and campaign colors in project roles or namespaced extensions.",
+    "Use appearanceRoles for optional project or package meanings that vary between light and dark, and declare their maintained foreground/background relationships explicitly.",
+    "Override a complete atomic Brick family or inherit that entire family from Brick defaults.",
+    "Use only Brick-declared component theme inputs and treat their closed values as project-wide policy with component props remaining available for local exceptions.",
+    "Compile at build time, review the contrast report and static artifacts, then ship the CSS rather than the compiler.",
+    "Let the application own activation, saved preference, fonts, assets, portals, and first-paint behavior."
+  ],
+  "selection": [
+    {
+      "intent": "Author a deterministic theme source",
+      "use": "defineTheme with the flowstack.theme.v1 schema and JSON-compatible values",
+      "destinations": [
+        {
+          "kind": "operation",
+          "id": "theme-definition"
+        }
+      ]
+    },
+    {
+      "intent": "Check a theme definition before compatibility work",
+      "use": "validateThemeDefinition for diagnostics or assertThemeDefinition for a throwing boundary",
+      "destinations": [
+        {
+          "kind": "operation",
+          "id": "theme-validation"
+        }
+      ]
+    },
+    {
+      "intent": "Qualify Theme against Brick",
+      "use": "load and assert the theme-contract.json belonging to the exact installed Brick version",
+      "destinations": [
+        {
+          "kind": "operation",
+          "id": "brick-contract-compatibility"
+        }
+      ]
+    },
+    {
+      "intent": "Start from generated Colors candidates",
+      "use": "the serialized, explicitly reviewed Colors candidate and scaffold mapping handoff",
+      "destinations": [
+        {
+          "kind": "operation",
+          "id": "colors-interchange"
+        }
+      ]
+    },
+    {
+      "intent": "Resolve semantic values and prove completeness and contrast",
+      "use": "compileTheme against the selected installed Brick contract",
+      "destinations": [
+        {
+          "kind": "operation",
+          "id": "theme-compilation"
+        }
+      ]
+    },
+    {
+      "intent": "Produce files for an application build",
+      "use": "compileThemeFiles and writeThemeArtifacts for the complete deterministic CSS, token, manifest, and report set",
+      "destinations": [
+        {
+          "kind": "operation",
+          "id": "theme-artifacts"
+        }
+      ]
+    },
+    {
+      "intent": "Validate, scaffold, or compile from automation",
+      "use": "the flowstack-theme CLI with explicit JSON, contract, mapping, and output paths",
+      "destinations": [
+        {
+          "kind": "operation",
+          "id": "theme-cli"
+        }
+      ]
+    },
+    {
+      "intent": "Activate a compiled theme or choose product-specific brand direction",
+      "use": "application-owned runtime and authorized project inputs after Theme emits static artifacts",
+      "destinations": [
+        {
+          "kind": "native-application",
+          "id": "application-theme-runtime"
+        },
+        {
+          "kind": "native-application",
+          "id": "application-art-direction"
+        }
+      ]
+    }
+  ],
+  "rules": [
+    {
+      "id": "theme-serializable",
+      "level": "must",
+      "statement": "Keep theme definitions JSON-compatible and deterministic; do not use functions, DOM state, environment-dependent values, or runtime callbacks."
+    },
+    {
+      "id": "theme-installed-contract",
+      "level": "must",
+      "statement": "Compile against the theme-contract.json exported by the installed Brick package and do not maintain a copied semantic-token list."
+    },
+    {
+      "id": "theme-colors-interchange",
+      "level": "must",
+      "statement": "Treat Colors as optional serialized file input; never add a Colors runtime dependency or map an unreviewed candidate."
+    },
+    {
+      "id": "theme-complete-family",
+      "level": "must",
+      "statement": "When one member of an atomic Brick color family changes, provide the complete family for that appearance or inherit the complete Brick default."
+    },
+    {
+      "id": "theme-semantic-mapping",
+      "level": "must",
+      "statement": "Map values by semantic UI meaning; never misuse warning, danger, success, or information merely to obtain a desired hue."
+    },
+    {
+      "id": "theme-extra-colors",
+      "level": "must",
+      "statement": "Keep unlimited non-Brick brand, visualization, syntax, editorial, and product colors in palettes, roles, or namespaced extensions."
+    },
+    {
+      "id": "theme-contrast",
+      "level": "must",
+      "statement": "Treat insufficient or unprovable Brick-declared and project-declared contrast pairs as build failures; do not round a failing ratio into a pass."
+    },
+    {
+      "id": "theme-appearance-roles",
+      "level": "must",
+      "statement": "Define every appearance-aware project role for every supported appearance, keep its logical meaning stable, and do not duplicate the same path in invariant roles."
+    },
+    {
+      "id": "theme-static-runtime",
+      "level": "must",
+      "statement": "Ship compiled static CSS and keep @flowstack-ui/theme in build tooling unless a separately qualified runtime adapter is introduced."
+    },
+    {
+      "id": "theme-application-ownership",
+      "level": "must",
+      "statement": "Keep theme selection, persistence, pre-paint setup, font and asset loading, and portal-container coordination in the application."
+    },
+    {
+      "id": "theme-breakpoints",
+      "level": "must",
+      "statement": "Do not add theme breakpoints expecting them to recompile Brick media queries; Brick component breakpoints and application layout policy have separate owners."
+    },
+    {
+      "id": "theme-component-inputs",
+      "level": "should",
+      "statement": "Use components only for inputs explicitly audited in the Brick contract; honor closed allowed values and their conditional validation, and keep local component token overrides local."
+    }
+  ],
+  "ownership": {
+    "brick": [
+      "accessible default values",
+      "semantic UI roles and component recipes",
+      "atomic families, contrast pairs, and approved component inputs"
+    ],
+    "theme": [
+      "serializable project values and mappings",
+      "compatibility, completeness, alias, and contrast validation",
+      "appearance-aware project roles and explicit project relationships",
+      "deterministic CSS, token, manifest, and report artifacts"
+    ],
+    "application": [
+      "activation and saved preference",
+      "font and asset loading",
+      "first paint, portals, routes, and product art direction"
+    ]
+  },
+  "nativeFallback": {
+    "check": "Check whether the task is deterministic Theme authoring, validation, compatibility, compilation, artifact writing, or CLI automation before using this package.",
+    "use": "Use application-owned integration for runtime activation, persistence, first paint, fonts, assets, portal placement, routes, and product-specific art direction.",
+    "report": "Report a Theme or Brick contract gap instead of copying semantic tokens, weakening validation, inventing brand decisions, or shipping the compiler in the browser."
+  },
+  "validation": [
+    "Validate the definition envelope before compiling.",
+    "When using Colors interchange, confirm the candidate review and scaffold report identify the intended families and semantic jobs.",
+    "Compile against the exact installed Brick contract revision and review every diagnostic.",
+    "When a categorical component input activates conditional validation, confirm every resulting contrast pair passes in every supported appearance.",
+    "Confirm every appearance role is complete and every declared project relationship passes in every supported appearance.",
+    "Confirm theme.report.json contains one passing result for every declared pair and supported appearance.",
+    "Verify generated artifacts are byte-stable and committed only when the application owns committed build output.",
+    "Build the production application and verify explicit light, dark, nested appearance, portal, first-paint, and forced-colors behavior where applicable.",
+    "Confirm the browser bundle does not contain the Theme compiler."
+  ],
+  "related": [
+    {
+      "kind": "operation",
+      "id": "theme-definition"
+    },
+    {
+      "kind": "operation",
+      "id": "theme-validation"
+    },
+    {
+      "kind": "operation",
+      "id": "brick-contract-compatibility"
+    },
+    {
+      "kind": "operation",
+      "id": "colors-interchange"
+    },
+    {
+      "kind": "operation",
+      "id": "theme-compilation"
+    },
+    {
+      "kind": "operation",
+      "id": "theme-artifacts"
+    },
+    {
+      "kind": "operation",
+      "id": "theme-cli"
+    },
+    {
+      "kind": "native-application",
+      "id": "application-theme-runtime"
+    }
+  ]
+}
+```

package/public/packages/theme/0.1.1/index.txt

@@ -0,0 +1,31 @@
+# @flowstack-ui/theme@0.1.1
+
+Archive SHA-256: `fcdc32692843076c0fe313af837660c93b7f69537c663005b9a8d78e493dea5b`
+Coverage: 121/121 public surfaces; zero failures.
+
+## document
+
+- [agent-knowledge](/packages/theme/0.1.1/docs/agent-knowledge.txt)
+- [appearances-and-portals](/packages/theme/0.1.1/docs/appearances-and-portals.txt)
+- [architecture](/packages/theme/0.1.1/docs/architecture.txt)
+- [authoring](/packages/theme/0.1.1/docs/authoring.txt)
+- [colors-interchange](/packages/theme/0.1.1/docs/colors-interchange.txt)
+- [fonts](/packages/theme/0.1.1/docs/fonts.txt)
+- [installation](/packages/theme/0.1.1/docs/installation.txt)
+- [migration](/packages/theme/0.1.1/docs/migration.txt)
+- [testing](/packages/theme/0.1.1/docs/testing.txt)
+- [troubleshooting](/packages/theme/0.1.1/docs/troubleshooting.txt)
+
+## guide
+
+- [FLOWSTACK Theme system](/packages/theme/0.1.1/guides/theme-system.txt)
+
+## operation
+
+- [Brick contract compatibility](/packages/theme/0.1.1/operations/brick-contract-compatibility.txt)
+- [Colors interchange](/packages/theme/0.1.1/operations/colors-interchange.txt)
+- [Theme artifacts](/packages/theme/0.1.1/operations/theme-artifacts.txt)
+- [Theme CLI](/packages/theme/0.1.1/operations/theme-cli.txt)
+- [Theme compilation](/packages/theme/0.1.1/operations/theme-compilation.txt)
+- [Theme definition](/packages/theme/0.1.1/operations/theme-definition.txt)
+- [Theme validation](/packages/theme/0.1.1/operations/theme-validation.txt)

package/public/packages/theme/0.1.1/operations/brick-contract-compatibility.txt

@@ -0,0 +1,35 @@
+# Brick contract compatibility
+
+Source: @flowstack-ui/theme@0.1.1
+Kind: operation
+ID: brick-contract-compatibility
+Guide: [theme-system](/packages/theme/0.1.1/guides/theme-system.txt)
+
+## Covered public surfaces
+
+- `.#BRICK_THEME_CONTRACT_SCHEMA`
+- `.#BrickAtomicColorFamily`
+- `.#BrickComponentThemeAssignment`
+- `.#BrickComponentThemeInput`
+- `.#BrickContractToken`
+- `.#BrickContrastCondition`
+- `.#BrickContrastContract`
+- `.#BrickContrastKind`
+- `.#BrickContrastPair`
+- `.#BrickThemeContract`
+- `.#BrickTokenClassification`
+- `.#BrickTokenDeprecation`
+- `.#assertBrickThemeContract`
+- `.#loadBrickThemeContract`
+- `./schema#BRICK_THEME_CONTRACT_SCHEMA`
+- `./schema#BrickAtomicColorFamily`
+- `./schema#BrickComponentThemeAssignment`
+- `./schema#BrickComponentThemeInput`
+- `./schema#BrickContractToken`
+- `./schema#BrickContrastCondition`
+- `./schema#BrickContrastContract`
+- `./schema#BrickContrastKind`
+- `./schema#BrickContrastPair`
+- `./schema#BrickThemeContract`
+- `./schema#BrickTokenClassification`
+- `./schema#BrickTokenDeprecation`

package/public/packages/theme/0.1.1/operations/colors-interchange.txt

@@ -0,0 +1,35 @@
+# Colors interchange
+
+Source: @flowstack-ui/theme@0.1.1
+Kind: operation
+ID: colors-interchange
+Guide: [theme-system](/packages/theme/0.1.1/guides/theme-system.txt)
+
+## Covered public surfaces
+
+- `.#COLORS_CANDIDATE_SCHEMA`
+- `.#COLORS_THEME_SCAFFOLD_REPORT_SCHEMA`
+- `.#COLORS_THEME_SCAFFOLD_SCHEMA`
+- `.#ColorsPaletteProfile`
+- `.#ColorsThemeScaffoldError`
+- `.#ColorsThemeScaffoldIssue`
+- `.#ColorsThemeScaffoldIssueCode`
+- `.#ColorsThemeScaffoldPaletteReport`
+- `.#ColorsThemeScaffoldReport`
+- `.#ColorsThemeScaffoldRequest`
+- `.#ColorsThemeScaffoldResult`
+- `.#ColorsThemeSemanticTarget`
+- `.#scaffoldThemeFromColors`
+- `.#scaffoldThemeFromColorsFiles`
+- `.#writeColorsThemeScaffold`
+- `./schema#COLORS_CANDIDATE_SCHEMA`
+- `./schema#COLORS_THEME_SCAFFOLD_REPORT_SCHEMA`
+- `./schema#COLORS_THEME_SCAFFOLD_SCHEMA`
+- `./schema#ColorsPaletteProfile`
+- `./schema#ColorsThemeScaffoldIssue`
+- `./schema#ColorsThemeScaffoldIssueCode`
+- `./schema#ColorsThemeScaffoldPaletteReport`
+- `./schema#ColorsThemeScaffoldReport`
+- `./schema#ColorsThemeScaffoldRequest`
+- `./schema#ColorsThemeScaffoldResult`
+- `./schema#ColorsThemeSemanticTarget`

package/public/packages/theme/0.1.1/operations/theme-artifacts.txt

@@ -0,0 +1,19 @@
+# Theme artifacts
+
+Source: @flowstack-ui/theme@0.1.1
+Kind: operation
+ID: theme-artifacts
+Guide: [theme-system](/packages/theme/0.1.1/guides/theme-system.txt)
+
+## Covered public surfaces
+
+- `.#THEME_MANIFEST_SCHEMA`
+- `.#THEME_REPORT_SCHEMA`
+- `.#ThemeCompilationReport`
+- `.#ThemeManifest`
+- `.#compileThemeFiles`
+- `.#writeThemeArtifacts`
+- `./schema#THEME_MANIFEST_SCHEMA`
+- `./schema#THEME_REPORT_SCHEMA`
+- `./schema#ThemeCompilationReport`
+- `./schema#ThemeManifest`

package/public/packages/theme/0.1.1/operations/theme-cli.txt

@@ -0,0 +1,10 @@
+# Theme CLI
+
+Source: @flowstack-ui/theme@0.1.1
+Kind: operation
+ID: theme-cli
+Guide: [theme-system](/packages/theme/0.1.1/guides/theme-system.txt)
+
+## Covered public surfaces
+
+- `bin:flowstack-theme`

package/public/packages/theme/0.1.1/operations/theme-compilation.txt

@@ -0,0 +1,23 @@
+# Theme compilation
+
+Source: @flowstack-ui/theme@0.1.1
+Kind: operation
+ID: theme-compilation
+Guide: [theme-system](/packages/theme/0.1.1/guides/theme-system.txt)
+
+## Covered public surfaces
+
+- `.#CompiledThemeToken`
+- `.#ThemeCompilation`
+- `.#ThemeCompilationError`
+- `.#ThemeCompilationIssue`
+- `.#ThemeCompilationIssueCode`
+- `.#ThemeContrastPairResult`
+- `.#ThemeProjectContrastPairResult`
+- `.#compileTheme`
+- `./schema#CompiledThemeToken`
+- `./schema#ThemeCompilation`
+- `./schema#ThemeCompilationIssue`
+- `./schema#ThemeCompilationIssueCode`
+- `./schema#ThemeContrastPairResult`
+- `./schema#ThemeProjectContrastPairResult`

package/public/packages/theme/0.1.1/operations/theme-definition.txt

@@ -0,0 +1,36 @@
+# Theme definition
+
+Source: @flowstack-ui/theme@0.1.1
+Kind: operation
+ID: theme-definition
+Guide: [theme-system](/packages/theme/0.1.1/guides/theme-system.txt)
+
+## Covered public surfaces
+
+- `.#JsonPrimitive`
+- `.#JsonValue`
+- `.#THEME_DEFINITION_SCHEMA`
+- `.#ThemeAppearance`
+- `.#ThemeAppearanceRoles`
+- `.#ThemeAppearances`
+- `.#ThemeCompatibility`
+- `.#ThemeData`
+- `.#ThemeDefaultAppearance`
+- `.#ThemeDefinition`
+- `.#ThemeMetadata`
+- `.#ThemeProjectContrastPair`
+- `.#ThemeRelationships`
+- `.#defineTheme`
+- `./schema#JsonPrimitive`
+- `./schema#JsonValue`
+- `./schema#THEME_DEFINITION_SCHEMA`
+- `./schema#ThemeAppearance`
+- `./schema#ThemeAppearanceRoles`
+- `./schema#ThemeAppearances`
+- `./schema#ThemeCompatibility`
+- `./schema#ThemeData`
+- `./schema#ThemeDefaultAppearance`
+- `./schema#ThemeDefinition`
+- `./schema#ThemeMetadata`
+- `./schema#ThemeProjectContrastPair`
+- `./schema#ThemeRelationships`

package/public/packages/theme/0.1.1/operations/theme-validation.txt

@@ -0,0 +1,19 @@
+# Theme validation
+
+Source: @flowstack-ui/theme@0.1.1
+Kind: operation
+ID: theme-validation
+Guide: [theme-system](/packages/theme/0.1.1/guides/theme-system.txt)
+
+## Covered public surfaces
+
+- `.#ThemeValidationError`
+- `.#ThemeValidationIssue`
+- `.#ThemeValidationIssueCode`
+- `.#ThemeValidationResult`
+- `.#assertThemeDefinition`
+- `.#isThemeDefinition`
+- `.#validateThemeDefinition`
+- `./schema#ThemeValidationIssue`
+- `./schema#ThemeValidationIssueCode`
+- `./schema#ThemeValidationResult`

package/public/tasks/data.txt

@@ -0,0 +1,39 @@
+# FLOWSTACK task: data
+
+Select tables, grids, lists, trees, feeds, status, and technical-data owners.
+
+Load only the routes required for the current job and preserve their exact package versions.
+
+## Default: finished interface
+
+Use Brick for an ordinary finished data interface. Do not import Atom directly.
+
+- [brick/guide/layer-selection](/packages/brick/0.1.11/guides/layer-selection.txt)
+- [brick/guide/interface-composition](/packages/brick/0.1.11/guides/interface-composition.txt)
+- [brick/component/data-grid](/packages/brick/0.1.11/components/data-grid.txt)
+- [brick/component/data-list](/packages/brick/0.1.11/components/data-list.txt)
+- [brick/component/feed](/packages/brick/0.1.11/components/feed.txt)
+- [brick/component/list](/packages/brick/0.1.11/components/list.txt)
+- [brick/component/progress](/packages/brick/0.1.11/components/progress.txt)
+- [brick/component/progress-circle](/packages/brick/0.1.11/components/progress-circle.txt)
+- [brick/component/reorderable-list](/packages/brick/0.1.11/components/reorderable-list.txt)
+- [brick/component/status](/packages/brick/0.1.11/components/status.txt)
+- [brick/component/table](/packages/brick/0.1.11/components/table.txt)
+- [brick/component/tree](/packages/brick/0.1.11/components/tree.txt)
+- [brick/component/tree-grid](/packages/brick/0.1.11/components/tree-grid.txt)
+
+## Explicit exception: headless behavior
+
+Use Atom only when the task explicitly requires reusable headless data behavior without Brick's finished visual contract.
+
+- [atom/guide/layer-selection](/packages/atom/0.24.0/guides/layer-selection.txt)
+- [atom/guide/behavior-composition](/packages/atom/0.24.0/guides/behavior-composition.txt)
+- [atom/component/data-grid](/packages/atom/0.24.0/components/data-grid.txt)
+- [atom/component/feed](/packages/atom/0.24.0/components/feed.txt)
+- [atom/component/list](/packages/atom/0.24.0/components/list.txt)
+- [atom/component/listbox](/packages/atom/0.24.0/components/listbox.txt)
+- [atom/component/progress](/packages/atom/0.24.0/components/progress.txt)
+- [atom/component/reorder](/packages/atom/0.24.0/components/reorder.txt)
+- [atom/component/table](/packages/atom/0.24.0/components/table.txt)
+- [atom/component/tree](/packages/atom/0.24.0/components/tree.txt)
+- [atom/component/tree-grid](/packages/atom/0.24.0/components/tree-grid.txt)