@weatherboard/gyde-design 0.4.1 → 0.4.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/agentdocs.mjs +6 -1
  2. package/package.json +1 -1
package/agentdocs.mjs CHANGED
@@ -122,6 +122,9 @@ export function agentDoc({
122
122
  * requirements rather than as facts about the implementation.
123
123
  */
124
124
  verified = true,
125
+ // An older Gyde-emitted set may predate the app theme controller. Its
126
+ // component metadata is verified, but this optional capability is absent.
127
+ themeChoice = verified,
125
128
  } = {}) {
126
129
  const closure = verified
127
130
  ? `**Never pass \`className\` or \`style\` to a design-system component.** They do not
@@ -191,7 +194,9 @@ brand — do **not** reach for inline styles. Spread \`themeVars(theme)\` onto a
191
194
  element you already own and set the component's tone to \`themed\`. It returns
192
195
  CSS custom properties only, which is why it is not an escape hatch.
193
196
 
194
- ## App theme choice
197
+ ` : ""}
198
+
199
+ ${themeChoice ? `## App theme choice
195
200
 
196
201
  The design-system package supplies \`src/theme-bootstrap.js\` and exports
197
202
  \`${systemPackage}/theme-choice\`. The product must wire both into its app shell:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@weatherboard/gyde-design",
3
- "version": "0.4.1",
3
+ "version": "0.4.2",
4
4
  "private": false,
5
5
  "description": "Scaffolds a design system into a product repository, then keeps auditing it.",
6
6
  "type": "module",