@pithyjs/pidl-catalog 0.1.0-beta.1 → 0.1.0-beta.2

package/dist/specs/atoms/data/stacked-bar.pidl.json

@@ -0,0 +1,341 @@
+{
+    "kind": "component",
+    "id": "ui.stacked-bar",
+    "name": "StackedBar",
+    "displayName": "Stacked Bar Chart",
+    "version": "0.1.0",
+    "level": "atom",
+    "domain": "data",
+    "bidi": true,
+    "description": "A single horizontal bar divided into proportional parts of one whole, with a colour key beneath. The same statement a Donut makes, drawn straight — better wherever the chart has to sit in a band rather than a square, and wherever the parts are lopsided, because a 2% slice of a ring is a wedge too narrow to see at its point while 2% of a bar is a stripe of constant height. Rendered in DOM as a flex row of segments, not SVG. The drawing and the key are aria-hidden; a visually-hidden data table carries every exact value and share and is the chart's accessible representation. Loading, empty (including an all-zero stack), and error states are first-class.",
+    "props": [
+        {
+            "name": "label",
+            "label": "Accessible name",
+            "type": "string",
+            "required": true,
+            "placeholder": "Budget by department",
+            "description": "Captions the visually-hidden data table screen readers read instead of the graphic. Required — it is the chart's accessible name."
+        },
+        {
+            "name": "segments",
+            "label": "Segments",
+            "type": "StackedBarSegment[] | Signal<StackedBarSegment[]>",
+            "required": true,
+            "reactive": true,
+            "placeholder": [
+                { "label": "Engineering", "value": 420 },
+                { "label": "Marketing", "value": 260 },
+                { "label": "Operations", "value": 130 }
+            ],
+            "description": "Parts in stack order. A value must be a finite number >= 0; anything else is counted as zero, warned about in DEV, and still listed in the accessible table.",
+            "itemSchema": {
+                "label": {
+                    "type": "string",
+                    "required": true,
+                    "description": "Category name. Appears in the colour key and as the row header in the accessible table."
+                },
+                "value": {
+                    "type": "number",
+                    "required": true,
+                    "description": "The quantity. Finite and >= 0."
+                },
+                "color": {
+                    "type": "string",
+                    "editor": { "type": "token-color" },
+                    "enum": [
+                        "primary",
+                        "secondary",
+                        "tertiary",
+                        "success",
+                        "info",
+                        "warning",
+                        "danger",
+                        "categorical-1",
+                        "categorical-2",
+                        "categorical-3",
+                        "categorical-4",
+                        "categorical-5",
+                        "categorical-6"
+                    ],
+                    "description": "Design-token name for this part. Omit to take the categorical palette slot for the segment's index — the correct default for identity encoding."
+                }
+            }
+        },
+        {
+            "name": "total",
+            "label": "Whole",
+            "type": "number | Signal<number>",
+            "reactive": true,
+            "placeholder": 1000,
+            "description": "The whole the parts are parts OF — a NUMBER, and the denominator every share is taken of. Note this is not DonutProps.total, which is a display string for the middle of the ring: a donut can only ever show the whole it was given, while a bar can show a whole the parts do not reach. Omit it and the parts fill the bar exactly. Pass one and any shortfall stays visible as unfilled track — '70 of a budget of 100' is a different statement from '70, which is all there is', and only this prop can tell them apart. Parts that overrun it are scaled to fill the bar exactly and DEV-warned; a value that is not a finite number greater than zero is DEV-warned and the sum is used instead."
+        },
+        {
+            "name": "legend",
+            "label": "Colour key",
+            "editor": { "tab": "layout" },
+            "type": "enum",
+            "enum": ["end", "bottom", "none"],
+            "default": "bottom",
+            "description": "Where the colour key sits. 'bottom' (the default) puts it under the bar as a wrapping line, which is where a wide, short drawing wants it. 'end' places it beside the bar, wrapping underneath when the row cannot hold both — intrinsically, with no breakpoint deciding. 'none' removes it, and is only correct when the colour-to-category mapping is carried elsewhere: a one-segment bar, or a stack of bars under one shared key."
+        },
+        {
+            "name": "size",
+            "label": "Size",
+            "editor": { "tab": "layout" },
+            "type": "enum",
+            "enum": ["sm", "md", "lg"],
+            "default": "md",
+            "description": "Sets the bar's thickness. It does NOT cap the chart's width, unlike the circular charts: a bar's inline extent is its SCALE rather than its size. The chart fills its column and stays intrinsically fluid, with no breakpoints."
+        },
+        {
+            "name": "loading",
+            "label": "Loading",
+            "editor": { "tab": "settings" },
+            "type": "boolean | Signal<boolean>",
+            "default": false,
+            "reactive": true,
+            "description": "Hides the drawing and the table, shows a pulsing skeleton reserving exactly the bar's own height, and sets aria-busy on the drawing's wrapper. The colour key keeps its box and loses its text, so the chart does not resize when data arrives. Outranks every other state."
+        },
+        {
+            "name": "error",
+            "label": "Error",
+            "editor": { "tab": "settings" },
+            "type": "boolean | Signal<boolean>",
+            "default": false,
+            "reactive": true,
+            "description": "Hides the drawing and the table and shows the error message. Outranks the empty state — a failed fetch usually leaves an empty array behind it."
+        },
+        {
+            "name": "errorMessage",
+            "label": "Error message",
+            "editor": { "tab": "settings" },
+            "type": "string | Signal<string>",
+            "default": "Chart data unavailable",
+            "reactive": true,
+            "description": "Copy shown in the error state."
+        },
+        {
+            "name": "emptyMessage",
+            "label": "Empty message",
+            "editor": { "tab": "settings" },
+            "type": "string",
+            "default": "No data to display",
+            "description": "Copy shown when there are no segments, or when every segment is zero."
+        },
+        {
+            "name": "loadingLabel",
+            "label": "Loading message",
+            "editor": { "tab": "settings" },
+            "type": "string",
+            "default": "Loading chart…",
+            "description": "Copy shown in the loading state."
+        },
+        {
+            "name": "id",
+            "label": "ID",
+            "editor": { "tab": "settings" },
+            "type": "string",
+            "description": "Explicit element ID on the <figure> root."
+        }
+    ],
+    "events": [],
+    "slots": [],
+    "tokens": {
+        "track.background": "--color-surface-variant",
+        "track.border": "--color-border at --border-width-thin",
+        "track.radius": "--radius-sm",
+        "segment.background": "--color-categorical-1 … --color-categorical-6, or any semantic colour",
+        "segment.background.fallback": "--color-text-muted (segments past the last categorical slot)",
+        "segment.emphasis.outline": "--color-text at --border-width-thick",
+        "segment.motion.duration": "--motion-duration-slow",
+        "segment.motion.easing": "--motion-easing-emphasized",
+        "legend.swatch.background": "--color-categorical-1 … --color-categorical-6 (the same token the swatch's own segment takes)",
+        "legend.name.color": "--color-text-muted",
+        "legend.value.color": "--color-text",
+        "legend.value.font": "--font-family-mono",
+        "legend.size": "--font-size-sm",
+        "status.color": "--color-text-muted",
+        "status.error.color": "--color-danger",
+        "placeholder.background": "--color-surface-variant",
+        "placeholder.radius": "--radius-sm",
+        "forced-colors.border": "--border-width-thin, --border-width-hairline"
+    },
+    "spacing": {
+        "internal": {
+            "bar-to-legend": {
+                "relationship": "friends",
+                "token": "md",
+                "note": "Stacked, the key reads as a caption of the drawing rather than as a separate block."
+            },
+            "legend-entry-to-entry": {
+                "relationship": "friends",
+                "token": "md",
+                "note": "Separate items scanned across one wrapping line, so they need more air between them than a swatch and its own name do."
+            },
+            "swatch-to-name": {
+                "relationship": "lovers",
+                "token": "xs",
+                "note": "A swatch means nothing apart from its name."
+            },
+            "graphic-to-status": { "relationship": "close_friends", "token": "sm" }
+        }
+    },
+    "constraints": [
+        "Use logical properties only — no left/right, no width/height where inline-size/block-size applies",
+        "Colour is a design-token NAME, never a CSS value — there is no prop through which a hex code can reach a stylesheet",
+        "No function-valued props. Every prop has to be editable and serialisable through PIDL, so there is no formatValue callback; numbers are formatted by the kit's own formatter, which the key and the data table both go through so the two cannot disagree",
+        "Rendered in DOM, not SVG: a stacked bar is a row of rectangles, so the browser lays them out, no viewBox scaling stands between the reader's font size and the key beside it, and rounding both ends of the bar is one overflow: hidden rather than clipped paths",
+        "The graphic is aria-hidden — the visually-hidden data table is the accessible representation, so `label` is required",
+        "No title attribute on a segment. The design source used one; a title tooltip has no keyboard and no touch equivalent and is not reliably announced, so a mapping living there is a mapping some readers never get",
+        "The chart is width-agnostic: it fills its column and `size` sets thickness instead",
+        "Segments are flex: none — exactly their share, never grown to fill a remainder and never shrunk to make room. A shortfall under an explicit `total` is supposed to stay visible as unfilled track, and flex: 1 would quietly close it",
+        "A non-zero segment too small to see is widened to a minimum visible width, and that width is given back FIRST by any unfilled track and then by the leaders — levelled off the top of the stack, tallest down, rather than charged to any one segment. Segments are adjacent, so a floor that is not paid for pushes the last one off the end of the track. Levelling keeps the distortion where a given absolute width is the smallest relative error AND cannot reverse rank: charging the single largest could push it below the runner-up, so the bar said the opposite of its own table",
+        "If the floor cannot be satisfied at all — more real categories than the track has room to give each one its minimum — it is abandoned wholesale rather than applied to an arbitrary prefix of them, and the exact proportions stand",
+        "A value of zero is drawn at no width at all. Nothing is not a sliver, and a zero segment still appears in the table and the key",
+        "Parts that sum past an explicit total are scaled proportionally to fill the bar exactly, and DEV-warned. Relative sizes survive the rescale; the table still reports the true values",
+        "The drawn parts can never exceed the track: after the floor and its rebalance a final proportional rescale guarantees it, so the invariant is total rather than argued",
+        "An all-zero stack, a stack with no segments, and a sum that overflows to Infinity all render the empty state; the geometry never divides by zero",
+        "The drawing and the data table are hidden together in every non-ready state so the two cannot disagree about whether there is data. The KEY is not hidden with them — it keeps its box and loses its text to skeleton bars, so it states nothing while reserving the space it will need",
+        "The whole is a <tfoot> row in the data table. Under an explicit `total` it is NOT the sum of the body rows, and that gap is the shortfall the bar draws as unfilled track",
+        "An empty or whitespace-only segment label is a MISSING label and becomes 'Series N' — a blank row header is a category a reader can neither name nor look up",
+        "Segment colour defaults to the categorical palette slot for the segment index; past the sixth slot the segment is painted neutral rather than repeating slot 1",
+        "A multi-segment bar must carry a colour key — its own, or one shared on the page. Colour is the only thing identifying a segment (WCAG 1.4.1), and there is no room inside a 34px band for a label. legend: 'none' opts out of the built-in key, not out of the requirement",
+        "One colour resolution feeds both the segment and its swatch; a key painted by a second call is a key that can disagree with the graphic, and disagree quietly",
+        "Hover emphasis adds an inset ring rather than dimming the other segments — dimming a mark lowers its contrast against its surround, and WCAG 1.4.11 asks for 3:1 from every one of them",
+        "The segment width transition is inside a motion-safe block, and its width custom property defaults to 0% — an unset segment must take no room, never share it out"
+    ],
+    "a11y": [
+        "The drawing carries aria-hidden='true' — it is a picture of the table beside it",
+        "A <table class='u-sr-only'> carries every exact value and share, captioned with the required `label` prop",
+        "Table headers are scoped: <th scope='col'> in the head, <th scope='row'> per segment",
+        "The shares in the table are the EXACT ones, never the drawn widths — the visibility floor and the overflow rescale have both had their hands on those, which is why the table and not the bar is the reading of record",
+        "Zero-value segments and segments widened by the floor both appear in the table at their true values",
+        "A share that is greater than zero but rounds to zero reads '<0.1%', never '0%'",
+        "The whole is a <tfoot> row, and under an explicit `total` it is the only place a screen reader can find the figure the shortfall is a shortfall against",
+        "The legend is aria-hidden: the table already carries every category, value and share, and exposing both would read the dataset twice, the second time in a flatter form. Nothing inside the legend is focusable, which is what makes that safe",
+        "No title tooltips on the segments — unreachable by keyboard and touch, and not reliably announced",
+        "Status messages live in a role='status' region present from first render — a live region inserted when it gains content is often not announced",
+        "aria-busy='true' while loading goes on the drawing's wrapper (.ui-chart-body), NEVER on the root. The role='status' region is a child of the root, and a live region inside an aria-busy subtree has its changes DEFERRED until busy clears — which happens in the same call that blanks the region, so the announcement an AT ends up processing is 'empty'",
+        "forced-color-adjust: none on the segments and the track, restated here because the shared partial's rule selects '.ui-chart-graphic > svg' and this chart has no SVG. In a chart the colour IS the data. Segments also gain a hairline CanvasText divider, so the divisions stay readable when a forced palette has collapsed the hues",
+        "Hover emphasis carries no information — every category and share is already in the key — so it is free to be pointer-only; no keyboard or touch reader loses anything by never triggering it",
+        "The segment growth animation is inside a prefers-reduced-motion: no-preference block"
+    ],
+    "ai": {
+        "synonyms": [
+            "stacked bar",
+            "stacked bar chart",
+            "progress bar chart",
+            "composition bar",
+            "parts of a whole",
+            "share of total",
+            "breakdown bar",
+            "segmented bar",
+            "100% stacked bar",
+            "colour key",
+            "color key"
+        ],
+        "avoid": [
+            "Passing a CSS colour — the color field takes a design-token name",
+            "Using it to compare independent categories — that is Bars. Everything here is a part of one whole",
+            "More than six uncoloured segments — fold the tail into an explicit 'Other' bucket",
+            "Encoding meaning with the semantic palette for arbitrary categories (danger for 'category 3' says category 3 is bad)",
+            "Setting legend='none' on a multi-segment bar with no other key on the page — that leaves colour as the sole carrier of meaning, and unlike Bars there is no room for a label inside the band",
+            "Asking for title tooltips on the segments — unreachable by touch and by keyboard, and the key is already on screen",
+            "Hand-rolling a key beside the component: the swatch has to resolve its token exactly as the segment does, and a separately built key can drift from the graphic",
+            "Passing a display string to `total` — it is a number, the denominator. DonutProps.total is the string one",
+            "Reading the drawn widths as exact: the visibility floor and the overflow rescale both bend them, and the table is the exact record"
+        ],
+        "patterns": [
+            "Basic: <StackedBar label=\"'Budget by department'\" segments=\"departments\" />",
+            "With a visible shortfall: <StackedBar label=\"'Budget'\" segments=\"spend\" total=\"100\" />",
+            "Explicit colours: segments=[{ label: 'Passed', value: 900, color: 'success' }]",
+            "Live: <StackedBar label=\"'Mix'\" segments=\"() => mix()\" loading=\"isFetching\" />",
+            "Key beside the bar in a wide row: <StackedBar label=\"'Mix'\" segments=\"mix\" legend=\"'end'\" />",
+            "Key suppressed because one is shared across a stack of bars: <StackedBar label=\"'Mix'\" segments=\"mix\" legend=\"'none'\" />"
+        ]
+    },
+    "examples": [
+        {
+            "id": "basic",
+            "title": "Three parts of one whole",
+            "pithy": "<StackedBar label=\"'Budget by department'\" segments=\"departments\" />",
+            "assertions": [
+                "figure.ui-chart.ui-stacked-bar with data-status='ready'",
+                "one .ui-stacked-bar-track holding one .ui-stacked-bar-segment per datum",
+                "the segments' widths sum to 100%",
+                "data-color runs categorical-1, categorical-2, categorical-3",
+                "no <svg> and no title attribute anywhere",
+                "no axe violations"
+            ]
+        },
+        {
+            "id": "shortfall",
+            "title": "An explicit whole the parts do not reach",
+            "pithy": "<StackedBar label=\"'Budget'\" segments=\"[{label:'Spent',value:40},{label:'Committed',value:30}]\" total=\"100\" />",
+            "assertions": [
+                "segments render at 40% and 30%",
+                "30% of the track is left unfilled",
+                "the <tfoot> reads 'Total, 100, 100%' while the body rows sum to 70"
+            ]
+        },
+        {
+            "id": "overflow",
+            "title": "Parts that overrun the stated total",
+            "pithy": "<StackedBar label=\"'Budget'\" segments=\"[{label:'A',value:80},{label:'B',value:60}]\" total=\"100\" />",
+            "assertions": [
+                "the drawn widths sum to exactly 100%",
+                "their relative sizes survive the rescale",
+                "DEV warns that the segments exceed the total",
+                "the table still reports 80 and 60"
+            ]
+        },
+        {
+            "id": "long-tail",
+            "title": "A segment too small to see",
+            "pithy": "<StackedBar label=\"'Long tail'\" segments=\"[{label:'Bulk',value:100000},{label:'Speck',value:1}]\" />",
+            "assertions": [
+                "the tiny segment is widened to the minimum visible width",
+                "the largest segment gives that width back, so the parts still fit the track",
+                "the table reports the tiny segment's share as <0.1%"
+            ]
+        },
+        {
+            "id": "zero-total",
+            "title": "Every segment is zero",
+            "pithy": "<StackedBar label=\"'Budget'\" segments=\"allZero\" />",
+            "assertions": [
+                "data-status='empty' — the parts are shares of a whole that is zero, so there is no segment to draw and the key would name nothing. This deliberately differs from Bars, whose rows label themselves and so stay 'ready'",
+                "no NaN or Infinity anywhere in the markup"
+            ]
+        },
+        {
+            "id": "legend-default",
+            "title": "The colour key is on by default, under the bar",
+            "pithy": "<StackedBar label=\"'Budget by department'\" segments=\"departments\" />",
+            "assertions": [
+                "the figure carries data-legend='bottom'",
+                "one .ui-chart-legend-item per segment, in mark order",
+                "each swatch's data-color equals its own segment's data-color",
+                "the legend is aria-hidden='true', and the table still carries the numbers once"
+            ]
+        },
+        {
+            "id": "loading",
+            "title": "Loading",
+            "pithy": "<StackedBar label=\"'Budget'\" segments=\"departments\" loading=\"true\" />",
+            "assertions": [
+                "aria-busy='true' on .ui-chart-body, and absent from the root",
+                "graphic and table both hidden, the key still present",
+                "role='status' region reads 'Loading chart…'"
+            ]
+        }
+    ],
+    "designGuidance": {
+        "surface": "No background of its own — the bar sits on whatever surface hosts it. The track uses --color-surface-variant with a --color-border hairline, so an unfilled remainder reads as a defined container rather than as empty page, which is what makes a shortfall legible as a shortfall.",
+        "depth": "Flat. No shadow: the segments already read as one object because the track clips them, and a drop shadow on a band this short muddies the boundary between neighbouring segments.",
+        "borders": "One hairline around the track, which is what gives an unfilled remainder an edge. Segments have no borders between them in normal rendering — adjacent categorical hues separate themselves. In forced-colors both the track and the segments opt out of colour substitution and the segments gain a hairline CanvasText divider, since a forced palette may have collapsed the hues that were doing the separating.",
+        "interactivity": "Hover pairs a key row with its segment, in both directions: the segment takes an inset ring, the row takes a surface-variant background. That is emphasis, not disclosure — it restates what the key already says, which is precisely why it may be pointer-only. It earns its place here more than on a donut, because adjacent stripes of similar colour are genuinely hard to match to a key by eye. An inset ring rather than dimming the neighbours: dimming is the one treatment that lowers a mark's contrast against its surround, and WCAG 1.4.11 asks 3:1 of every one of them.",
+        "bestPractices": "Use it for parts of one whole in a band — under a heading, along the top of a card, or wherever a square would waste the column. Prefer it over a Donut when the parts are lopsided: a 2% wedge tapers to nothing at its point, while a 2% stripe keeps its full height. Keep to six or fewer categories and fold the rest into 'Other' — the categorical palette guarantees separation for six. Order the segments so the meaning runs one way (best to worst, oldest to newest); a stacked bar in arbitrary order is harder to read than a list. Pass `total` whenever the shortfall is the point, and leave it off whenever it is not — an unfilled bar with no explanation reads as broken. Keep the key: it is the only thing that turns a colour into a category, and the palette's CVD work guarantees the slots are DISTINGUISHABLE from each other, never that any one of them is identifiable. Always give a specific `label`: it is the caption a screen-reader user hears."
+    }
+}

package/dist/src/mutation-vocabulary.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"mutation-vocabulary.d.ts","sourceRoot":"","sources":["../../src/mutation-vocabulary.ts"],"names":[],"mappings":"AAAA,uHAAuH;AAEvH;;;;;;;;;GASG;AAEH,eAAO,MAAM,mBAAmB,QAsDxB,CAAC"}
+{"version":3,"file":"mutation-vocabulary.d.ts","sourceRoot":"","sources":["../../src/mutation-vocabulary.ts"],"names":[],"mappings":"AAAA,uHAAuH;AAEvH;;;;;;;;;GASG;AAEH,eAAO,MAAM,mBAAmB,QA6DxB,CAAC"}

package/dist/src/mutation-vocabulary.js

@@ -15,7 +15,7 @@ export const MUTATION_VOCABULARY = `
 You can modify the site using these operations:
 
 ### Page Operations
-- \`page.create\` — Create a new page. Include \`title\`, \`path\`, and — whenever you will add blocks to this page in the same response — an explicit \`id\` (a short kebab-case slug, e.g. "about", "contact").
+- \`page.create\` — Create a new page. Include \`title\`, \`path\`, and ALWAYS an explicit \`id\` (a short kebab-case slug, e.g. "about", "contact"). The \`id\` is not conditional: every page you create must be populated in the same response, and the blocks need the id to target.
 - \`page.delete\` — Delete a page by ID
 - \`page.reorder\` — Change the order of pages
 
@@ -30,6 +30,12 @@ Therefore, to build a NEW page with content:
 
 NEVER reference a page you have not created (e.g. a \`block.add\` with \`"pageId": "about"\` when no page "about" exists and no \`page.create\` with \`"id": "about"\` precedes it). Do not invent page ids — only use ids you created or that already exist.
 
+### Every Created Page Must Be Populated AND Linked
+A \`page.create\` on its own is never a complete answer. In the SAME \`mutations\` array, also:
+
+1. **Populate it** — one \`block.add\` per section, each using the pinned \`id\` as its \`pageId\`. A page with no blocks renders as a blank screen; creating one and stopping there gives the user nothing.
+2. **Link it** — put the new page's \`path\` into the site's navigation. \`hasNavigation\` tells you which case you are in — it reports a \`ui.navbar\`, not a footer. When it is \`false\`, \`block.add\` a \`ui.navbar\` with \`"index": 0\` onto a page visitors already reach, listing the new page and every existing one except the not-found page (\`/404\`); \`label\` is a REQUIRED prop and the whole response is discarded without it. A \`ui.footer-section\` link group added the same way works too. When it is \`true\` you cannot add to the existing navbar here — \`block.update\` replaces props wholesale and you are not given its current \`items\` — so say in your \`summary\` that the page still needs linking. Nothing links to a page you only created, so no visitor can ever reach it.
+
 ### Block Operations
 - \`block.add\` — Add a new block (component) to a page
 - \`block.remove\` — Remove a block by ID
@@ -56,11 +62,12 @@ Single-mutation \`mutations\` value (valid, parseable JSON):
 ]
 \`\`\`
 
-Multi-page \`mutations\` value — note the explicit \`page.create.id\` reused as \`block.add.pageId\` (valid, parseable JSON):
+Multi-page \`mutations\` value — note the explicit \`page.create.id\` reused as \`block.add.pageId\`, and the third mutation adding a navbar that routes to the new path (valid, parseable JSON):
 \`\`\`json
 [
   { "op": "page.create", "id": "about", "title": "About", "path": "/about" },
-  { "op": "block.add", "pageId": "about", "component": "ui.hero-section", "props": { "heading": "About Me" } }
+  { "op": "block.add", "pageId": "about", "component": "ui.hero-section", "props": { "heading": "About Me" } },
+  { "op": "block.add", "pageId": "home", "index": 0, "component": "ui.navbar", "props": { "label": "Primary", "brand": "Studio", "items": [{ "label": "Home", "href": "/" }, { "label": "About", "href": "/about" }] } }
 ]
 \`\`\`
 `.trim();

package/dist/src/mutation-vocabulary.js.map

@@ -1 +1 @@
-{"version":3,"file":"mutation-vocabulary.js","sourceRoot":"","sources":["../../src/mutation-vocabulary.ts"],"names":[],"mappings":"AAAA,uHAAuH;AAEvH;;;;;;;;;GASG;AAEH,MAAM,CAAC,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAsDlC,CAAC,IAAI,EAAE,CAAC"}
+{"version":3,"file":"mutation-vocabulary.js","sourceRoot":"","sources":["../../src/mutation-vocabulary.ts"],"names":[],"mappings":"AAAA,uHAAuH;AAEvH;;;;;;;;;GASG;AAEH,MAAM,CAAC,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6DlC,CAAC,IAAI,EAAE,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pithyjs/pidl-catalog",
-  "version": "0.1.0-beta.1",
+  "version": "0.1.0-beta.2",
   "description": "Machine-readable component contracts for PithyJS — props, types, defaults, slots and a11y guarantees as JSON.",
   "type": "module",
   "files": [