dashtaste 0.0.0-stage → 0.0.1

package/docs/usage.md

@@ -0,0 +1,126 @@
+# Usage
+
+Build with Node 20.19 or newer and pnpm:
+
+```sh
+pnpm install
+pnpm build
+npx dashtaste --help
+```
+
+## Check options
+
+```sh
+npx dashtaste check options.json --pack global
+npx dashtaste check first.json second.json --pack cn --format json
+npx dashtaste check options.json --pack cn --mode dark --max-warnings 0
+```
+
+Input may be one ECharts option, an array of options, or a page facts envelope:
+
+```json
+{
+  "charts": [{ "id": "orders", "option": { "series": [] } }],
+  "page": { "background": "#FFFFFF", "deltaColors": "red-up" }
+}
+```
+
+Page facts may also contain texts, gradients, shadows, kpis, deltas, and emojis.
+An option-only input cannot test computed page typography or CSS decoration.
+See the exported types for each fact shape.
+
+Defaults are the global pack, light mode, text output, and unlimited warnings.
+Errors always fail. `--max-warnings 0` also fails on any warning.
+Informational findings lower the score but do not fail a check.
+
+## Check rendered pages
+
+```sh
+CHROME_PATH=/path/to/chromium npx dashtaste check dashboard.html --pack cn
+CHROME_PATH=/path/to/chromium npx dashtaste check http://localhost:3000 --pack global
+```
+
+HTML mode needs Playwright's core package and a Chromium executable.
+It reads mounted ECharts instances through `window.echarts` after network idle
+and a 500ms settling interval. Render charts before that point.
+It collects visible text, composited backgrounds, decoration, KPIs, and deltas.
+Use `data-kpi`, `data-delta`, and `data-direction="up|down|flat"` for explicit facts.
+Set `data-delta-colors="red-up|green-up"` on the document element to override
+one page's comparison convention. Keep every directional delta consistent.
+The extractor inspects visible DOM text; canvas text is checked through options.
+
+## Flags and exit codes
+
+| Flag             | Commands      | Values                         |
+| ---------------- | ------------- | ------------------------------ |
+| `--pack`         | all           | `global`, `cn`                 |
+| `--mode`         | check, tokens | `light`, `dark`                |
+| `--format`       | check, rules  | `text`, `json`                 |
+| `--format`       | tokens        | `json`, `css`                  |
+| `--max-warnings` | check         | non-negative integer           |
+| `--only`         | check         | comma-separated rule IDs       |
+| `--disable`      | check         | comma-separated rule IDs       |
+| `--background`   | check         | three- or six-digit hex colour |
+| `--help`         | all           | command-specific usage         |
+
+`--disable` takes precedence over `--only`. Unknown rule IDs are input errors.
+`--background` overrides chart, page, and pack backgrounds for contrast checks.
+`tokens` requires an explicit `--pack`.
+
+Exit 0 means no errors and warnings within the selected limit.
+Exit 1 means errors or too many warnings.
+Exit 2 means invalid arguments, unreadable input, or unavailable extraction.
+Set `NO_COLOR` to suppress ANSI colour in text output.
+JSON output contains version, pack, per-input findings and scores, and summary.
+Each finding contains ruleId, severity, message, path, and fix.
+Score starts at 100: subtract 10 per error, 3 per warning, and 1 per info.
+The minimum score is zero.
+
+## Inspect metadata and tokens
+
+```sh
+npx dashtaste rules --pack cn --format json
+npx dashtaste tokens --pack global --mode light
+npx dashtaste tokens --pack cn --mode dark --format css
+```
+
+The cn pack includes screen composition settings for a 1920×1080 artboard.
+Screen composition uses dark tokens and `--mode dark`; it is not a third CLI mode.
+Pack objects also expose numberSystem, limits, typography, and spacing.
+Token output contains only colours for the selected light or dark mode.
+
+## Library and formatting
+
+```ts
+import { check, summarize } from 'dashtaste';
+import { formatCompact, formatPercent, formatDelta, formatDate } from 'dashtaste/format';
+
+const findings = check({ series: [] }, { pack: 'cn', mode: 'light' });
+const summary = summarize(findings);
+const amount = formatCompact(12300, 'cn'); // 1.23万
+const percent = formatPercent(0.125); // 12.5%
+const delta = formatDelta(110, 100, 'cn'); // render text and color together
+const date = formatDate(new Date(2026, 9, 21), 'cn'); // 2026-10-21
+```
+
+The date helper returns local calendar dates in YYYY-MM-DD form for both packs.
+Use an explicit display adapter for global long dates such as Oct 21, 2026.
+See each skill's numbers reference for exact comparison and rounding rules.
+
+## Skills and development
+
+Choose skills/dashtaste-global or skills/dashtaste-cn for the intended audience.
+Each skill links tokens, chart examples, numbers, layout, and patterns to avoid.
+Use the matching pack when checking the examples or a generated dashboard.
+Layout and copy still need visual review; the rule checker does not prove usability.
+
+```sh
+pnpm format
+pnpm format:check
+pnpm typecheck
+pnpm build
+pnpm test
+```
+
+The tests cover rule contracts, pack differences, colour contrast and vision,
+CLI behavior, formatting, skill consistency, every chart JSON example, and browser extraction.

package/package.json

@@ -1,6 +1,76 @@
 {
   "name": "dashtaste",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
-}
+  "version": "0.0.1",
+  "description": "Dashboard taste for coding agents: two style-pack skills (global and cn) plus a dashtaste check linter for ECharts configs and rendered dashboards.",
+  "keywords": [
+    "dashboard",
+    "echarts",
+    "chart",
+    "lint",
+    "linter",
+    "data-visualization",
+    "dataviz",
+    "design",
+    "agent-skills",
+    "skills",
+    "ai-agents",
+    "cli"
+  ],
+  "author": "Felix Fang (https://github.com/FelixFangX)",
+  "homepage": "https://github.com/FelixFangX/dashtaste#readme",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/FelixFangX/dashtaste.git"
+  },
+  "bugs": {
+    "url": "https://github.com/FelixFangX/dashtaste/issues"
+  },
+  "license": "MIT",
+  "type": "module",
+  "bin": {
+    "dashtaste": "dist/cli.js"
+  },
+  "files": [
+    "dist",
+    "skills",
+    "docs",
+    "README.md",
+    "LICENSE"
+  ],
+  "engines": {
+    "node": ">=20"
+  },
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js"
+    },
+    "./format": {
+      "types": "./dist/format.d.ts",
+      "import": "./dist/format.js"
+    }
+  },
+  "scripts": {
+    "build": "tsc",
+    "typecheck": "tsc --noEmit",
+    "test": "vitest run",
+    "lint-skills": "vitest run test/skills.test.ts",
+    "format": "prettier --write .",
+    "format:check": "prettier --check .",
+    "gallery": "pnpm build && node gallery/build.mjs",
+    "prepublishOnly": "npm run build"
+  },
+  "devDependencies": {
+    "@fontsource-variable/geist-mono": "^5.3.0",
+    "@fontsource-variable/instrument-sans": "^5.3.0",
+    "@fontsource-variable/inter": "^5.3.0",
+    "@types/node": "^20.19.0",
+    "echarts": "^6.1.0",
+    "prettier": "^3.9.10",
+    "typescript": "~5.9.3",
+    "vitest": "~3.2.4"
+  },
+  "optionalDependencies": {
+    "playwright-core": "^1.56.0"
+  }
+}

package/skills/dashtaste-cn/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: dashtaste-cn
+description: Build or review readable Chinese-market dashboards with concrete layout, chart, colour, and number defaults.
+---
+
+# Dashboard workflow
+
+Use for dashboard pages, chart options, KPI strips, rankings, and dashboard reviews.
+For a global audience use dashtaste-global.
+
+1. Pick the cn pack and light or dark mode before choosing colours.
+2. Read [tokens](references/tokens.md) for exact colours and sizes.
+3. Read [layout](references/layout.md) for page structure and controls.
+4. Read [charts](references/charts.md) for the chart types you need.
+5. Read [numbers](references/numbers.md) for units, dates, and comparisons.
+6. Build the page with real data, explicit units, and clear hierarchy.
+7. Run `npx dashtaste check options.json --pack cn --max-warnings 0`.
+   For a rendered page, check its URL with a browser available through `CHROME_PATH`.
+8. Fix errors and warnings; inspect informational findings. Recheck after edits.
+   Read [avoid](references/avoid.md) when replacing a flagged pattern.
+
+## Ten rules to apply first
+
+- DT001: Set explicit series colours from the selected pack.
+- DT002: Keep at most five categorical colours; group the tail as Other.
+- DT003: Draw straight line segments; smoothing invents intermediate values.
+- DT004: Hide line symbols above 12 points.
+- DT005: Use ranked bars for shares; no donuts in KPI boards.
+- DT007: Use flat two-dimensional marks.
+- DT009: Put units in value-axis names.
+- DT010: Start bar value axes at zero and disable scale.
+- DT013: Use red-up and green-down deltas throughout the page.
+- DT015: Meet 4.5:1 text contrast, or 3:1 for large text.
+
+## Layout explains itself
+
+Use no helper labels, explanatory captions, or “this chart shows” text.
+Put units in axis names. Titles may state the finding, such as
+“Returns fell for three weeks”. Labels identify data and controls directly.
+Keep definitions in an accessible detail view when needed, outside chart captions.
+
+## Chinese copy
+
+Use full-width punctuation in Chinese prose. Add a space between Hanzi and
+Latin text or digits in prose; keep `1.23万` and `12%` intact.
+Use no uppercase or tracked labels and no serif page title.
+Keep CJK text at least 12px, or 16px on screens. Use the numeral face
+and CJK fallback specified in references/numbers.md.
+
+Use one hero metric, one sheet, hairlines, and direct labels.
+Use the measured defaults in the references for all KPI boards.

package/skills/dashtaste-cn/references/avoid.md

@@ -0,0 +1,135 @@
+# Patterns to avoid
+
+Use this list when reviewing a page or replacing a flagged pattern.
+Rule checks cover observable facts; inspect layout and copy manually as well.
+
+## DT001: default-palette
+
+Multiple series need explicit colours. Any default palette colour is flagged.
+Replace it: set option.color to the pack palette (dashtaste tokens --pack <pack>).
+
+## DT002: rainbow-palette
+
+More than 6 distinct categorical colours or more than 5 saturated 60-degree hue buckets.
+Replace it: use the pack palette and group remaining categories as Other.
+
+## DT003: smooth-line
+
+Line smoothing greater than zero draws values that do not exist.
+Replace it: use straight segments: smooth: false.
+
+## DT004: symbols-everywhere
+
+Line symbols are noisy above 12 points; ECharts shows symbols by default.
+Replace it: set showSymbol: false.
+
+## DT005: pie-slices
+
+Maximum 5 slices; cn rose charts allow 8.
+Replace it: use horizontal bars or combine small parts into Other.
+
+## DT006: pie-overuse
+
+More than one pie per page or radius ratio above 0.75 warns. A global pie is informational.
+Replace it: prefer horizontal bars; keep donut radius ratio at most 0.75.
+
+## DT007: three-d
+
+3D series, axes, coordinates, and pseudo-3D pie decoration distort comparisons.
+Replace it: use flat 2D charts.
+
+## DT008: dual-axis
+
+Multiple value axes obscure comparisons, including mixed bar and line charts.
+Replace it: use one value axis or aligned small multiples.
+
+## DT009: missing-unit
+
+Value axes need a name, formatter, unit metadata, or units in rendered ticks.
+Replace it: put units in axis names, rendered ticks, or formatter metadata.
+
+## DT010: bar-baseline
+
+Bar value axes must start at zero; positive min and scale: true distort lengths.
+Replace it: set min: 0 and scale: false.
+
+## DT011: raw-large-numbers
+
+At data maximum magnitude 10000 or above, axis, visible data label, and tooltip channels need formatters.
+Replace it: format compact units: cn 万/亿; global K/M.
+
+## DT012: unit-system
+
+String formatter templates must use the selected compact unit system.
+Replace it: use cn 万/亿 or global K/M/B consistently.
+
+## DT013: delta-convention
+
+Directional deltas must follow one page convention: global green-up; cn red-up by default.
+Replace it: apply one deltaColors convention to the whole page.
+
+## DT014: delta-colour-only
+
+Directional colour must be accompanied by an arrow or signed number.
+Replace it: add ▲/▼ or an explicit sign.
+
+## DT015: low-contrast-text
+
+Text needs 4.5:1; at least 24px or 18.66px bold needs 3:1. Chart label defaults use 4.5:1.
+Replace it: increase text contrast against its background.
+
+## DT016: thin-line-contrast
+
+Line colours need at least 3:1 against the chart background.
+Replace it: darken light-mode lines or lighten dark-mode lines.
+
+## DT017: gradient-decoration
+
+Card/page gradients and linear or radial chart fills add decoration.
+Replace it: use solid backgrounds and fills.
+
+## DT018: glow
+
+Coloured CSS shadows with blur at least 12px, or chart shadowBlur at least 10, create glow.
+Replace it: remove glow and use hairline borders.
+
+## DT019: kpi-overload
+
+More than 6 global or 8 cn KPI tiles weakens priority.
+Replace it: keep only primary KPIs in the first view.
+
+## DT020: kpi-rainbow
+
+Three or more distinct accent colours on KPI values or tiles distract. Neutral greys and pack text/background tokens are excluded.
+Replace it: use ink for values and reserve colour for deltas.
+
+## DT021: emoji-icons
+
+Emoji in headings, KPI labels, and rankings add inconsistent iconography.
+Replace it: use plain text and plain numerals for rankings.
+
+## DT022: cjk-min-size
+
+CJK text must be at least 12px.
+Replace it: set CJK text to at least 12px.
+
+## DT023: legend-single-series
+
+An explicitly visible legend on one series repeats context.
+Replace it: hide the legend or label the series directly.
+
+## Manual layout review
+
+Helper labels and explanatory captions repeat visible structure; no automatic rule yet.
+Decorative icon tiles distract from values; no automatic rule yet.
+Tracked labels and serif titles impair dense CJK reading; no automatic rule yet.
+
+## Measured anti-patterns
+
+DT024: uncapped bars and bars wider than 24px (32px on screens).
+DT025: legends for two to four lines without direct end labels.
+DT026: decorative line strokes above 3px or below 1px.
+DT027: proportional numerals in KPI values.
+DT028: several equally sized KPIs without a clear hero.
+Avoid donuts on KPI boards, dual axes, repeated boxed cards, and empty quadrants.
+Avoid helper sentences, uppercase tracking, and in-flow shadows.

package/skills/dashtaste-cn/references/charts.md

@@ -0,0 +1,122 @@
+# Chart defaults
+
+These complete light-mode options use small values so no compact formatter is needed.
+Copy an option into a JSON file and check with `--pack cn`.
+For dark mode replace all foreground and surface colours using tokens.md; check with `--mode dark`.
+For large values, convert data to display units and name the unit in the axis.
+Keep raw values separately for accessible detail views.
+
+## Line
+
+Use for change over time. Keep straight segments. Use filled 3–4px dots on series of at most 31 points. A 240px plot is a useful starting height.
+
+<!-- prettier-ignore -->
+```json
+{"color": ["#141414"], "xAxis": {"type": "category", "data": ["Mon", "Tue", "Wed"]}, "yAxis": {"type": "value", "name": "Orders"}, "series": [{"type": "line", "smooth": false, "showSymbol": true, "data": [12, 18, 16], "lineStyle": {"width": 1.5, "color": "#141414"}, "symbol": "circle", "symbolSize": 4, "markPoint": {"symbol": "circle", "symbolSize": 7, "itemStyle": {"color": "#3E6A88"}, "label": {"show": true, "position": "top", "formatter": "{c}"}, "data": [{"coord": [2, 16]}]}}]}
+```
+
+## Bar
+
+Compare amounts. Start at zero. Use horizontal bars for long category labels and at most 12px bar thickness on desktop.
+
+<!-- prettier-ignore -->
+```json
+{"color": ["#141414"], "xAxis": {"type": "value", "name": "Orders", "min": 0, "scale": false}, "yAxis": {"type": "category", "data": ["East", "West", "North"]}, "series": [{"type": "bar", "barMaxWidth": 12, "data": [24, 18, 12]}]}
+```
+
+## Combo
+
+Use aligned panels for different units. Keep comparison series on one shared axis.
+
+<!-- prettier-ignore -->
+```json
+{"color": ["#141414"], "xAxis": {"type": "category", "data": ["Mon", "Tue", "Wed"]}, "yAxis": {"type": "value", "name": "Orders", "min": 0}, "series": [{"name": "Orders", "type": "bar", "data": [24, 18, 12], "barMaxWidth": 12}, {"name": "Prior orders", "type": "line", "showSymbol": true, "smooth": false, "data": [12, 15, 18], "lineStyle": {"width": 1.5, "color": "#141414"}, "symbol": "circle", "symbolSize": 4}]}
+```
+
+## Share / pie / donut
+
+No donuts or pies in KPI boards. Use a ranked bar list or a single 100% stacked bar with direct labels. The option below is for isolated composition analysis.
+
+<!-- prettier-ignore -->
+```json
+{"color": ["#141414"], "series": [{"type": "pie", "radius": ["35%", "60%"], "label": {"show": true, "formatter": "{b}: {d}%"}, "data": [{"name": "New", "value": 60}, {"name": "Repeat", "value": 40}]}]}
+```
+
+## Funnel
+
+Use for ordered process stages with a shared population. Keep one colour, descending values, and visible stage labels.
+
+<!-- prettier-ignore -->
+```json
+{"color": ["#141414"], "series": [{"type": "funnel", "sort": "descending", "label": {"show": true, "formatter": "{b}: {c}"}, "data": [{"name": "Started", "value": 90}, {"name": "Qualified", "value": 60}, {"name": "Completed", "value": 30}]}]}
+```
+
+## Table
+
+Use a semantic HTML table in production: left-align labels, right-align amounts, use 36px rows and hairline separators. This static ECharts graphic is a portable option example.
+
+<!-- prettier-ignore -->
+```json
+{"graphic": [{"type": "text", "left": 16, "top": 16, "style": {"text": "Region        Orders", "fill": "#1D2433", "fontSize": 14}}, {"type": "text", "left": 16, "top": 52, "style": {"text": "East                 24", "fill": "#1D2433", "fontSize": 14}}]}
+```
+
+## KPI
+
+Use real text with tabular figures. One 52–64px hero, 22–26px secondary values, 11px uppercase tracked mono labels for Latin, 13px CJK labels; weights 400 and 500.
+
+<!-- prettier-ignore -->
+```json
+{"graphic": [{"type": "text", "left": 16, "top": 16, "style": {"text": "Orders", "fill": "#5F6B7E", "fontSize": 14}}, {"type": "text", "left": 16, "top": 44, "style": {"text": "124", "fill": "#1D2433", "fontSize": 32}}]}
+```
+
+## Ranking / TOP N
+
+Sort descending. Default to TOP 5; use TOP 10 only with room. Use muted tabular ranks without medals. Show the cutoff in the title.
+
+<!-- prettier-ignore -->
+```json
+{"title": {"text": "Top 3 regions by orders"}, "color": ["#141414"], "xAxis": {"type": "value", "name": "Orders", "min": 0}, "yAxis": {"type": "category", "inverse": true, "data": ["1 East", "2 West", "3 North"]}, "series": [{"type": "bar", "barMaxWidth": 12, "data": [24, 18, 12]}]}
+```
+
+## Map
+
+Use only for geographic questions, otherwise use ranking bars. Register a matching GeoJSON map as regions before setOption. Keep roam off and use a sequential scale with units.
+
+<!-- prettier-ignore -->
+```json
+{"visualMap": {"min": 0, "max": 100, "text": ["Orders", "0"], "inRange": {"color": ["#141414"]}}, "series": [{"type": "map", "map": "regions", "roam": false, "data": [{"name": "East", "value": 24}, {"name": "West", "value": 18}]}]}
+```
+
+## Shared interaction defaults
+
+Use tooltip trigger axis for time series and item for isolated marks.
+Use one explicit colour for a single series; do not rely on theme defaults.
+Hide the legend for one series. For comparisons, hide legends and use short annotations with thin 1px leader lines.
+Do not use decorative gradients, shadows, 3D marks, or emoji in titles.
+Keep missing observations missing; do not replace them with zero.
+Use stable ordering for categories unless ranking is the question.
+Keep controls outside the plotting rectangle.
+Provide keyboard access and a table or textual data alternative.
+Use a finding title only when the data supports it after filtering.
+A unit belongs in the axis name, not in a helper caption.
+
+## Measured defaults
+
+Main lines use 1.5px ink; comparisons use 1px dashed mid-grey.
+Long series hide symbols. Short series use small ink dots; comparisons or incomplete values use hollow dots.
+Use straight segments, horizontal grid lines, and no y-axis line.
+Bars use at most 65% of their category band; keep value labels outside.
+Use one accent mark and neutral context; reserve red and green for deltas.
+Small multiples use 1.5px lines without axes and a shared scale per row.
+No area gradients, glow, or decorative heavy strokes.
+
+Exactly one accent mark per chart: a filled 7px latest or peak dot and its value label.
+Never use the accent on another chart element. Bars may highlight one bar instead.
+Only latest and extreme values may have labels.
+Use markLine, markPoint or graphic for leader-line annotations.
+Thin ink bars are at most 12px; negative bars are mid-grey.
+Inline table bars use ink at 20% opacity; the top row uses solid ink.
+
+Use story-bearing data in examples. Annotate one event per chart with a leader line, a hollow ink dot, and a short label in empty space. Keep the latest point as the single accent.
+
+Use one signature element per board. Place it alongside the main metric so it reinforces the data story.

package/skills/dashtaste-cn/references/layout.md

@@ -0,0 +1,78 @@
+# Layout
+
+Use one hero to establish the reading order.
+The hero is 52–64px on desktop and 112–128px on a screen.
+The hero is at least 2.2 times the next KPI.
+Use weight 500 and letter spacing −0.02em for the hero.
+Secondary KPIs use 22–26px, or 32–40px on screens.
+Labels use 12–13px and weight 500.
+Use sentence case without uppercase tracking.
+Titles name the metric or state a supported finding.
+Do not add helper text or explanatory sentences.
+
+## Surface
+
+Use one white sheet with a 12px radius on the warm neutral page.
+Separate sections with hairlines and whitespace.
+Avoid repeated boxed cards.
+Inner radii are at most 6px.
+Do not use in-flow shadows, gradients, glow, or glass effects.
+Dark screens use hairlines rather than luminous panel borders.
+
+## Density
+
+Fill the viewport with relevant information.
+Size the plot after reserving space for titles and direct labels.
+Keep all content inside the viewport.
+Use a main trend and a compact right rail.
+Place categorical detail beneath the trend.
+Keep date ranges in the header.
+Align section headings and plot edges.
+Align numeric baselines across the rail.
+Reserve room for the longest label.
+Avoid empty quadrants and decorative whitespace.
+
+## Tables
+
+Use semantic tables with 13px text and 36px rows.
+Use 11px muted mono column headers for Latin; CJK headers stay at least 12px.
+Right-align numbers with tabular figures.
+Use hairline row separators.
+Do not use zebra stripes or vertical rules.
+Show share with a 4px inline bar.
+The maximum share uses the accent; context uses a tint.
+Use muted tabular ranks without medals.
+Keep row names left aligned.
+Show units consistently within a column.
+Keep decimal precision consistent.
+
+## Screen
+
+Use a 1920×1080 viewport.
+The minimum CJK size is 16px.
+Use a 112–128px hero and a secondary KPI strip.
+Use twelve regional small multiples instead of coloured tiles.
+Use the same scale across regional sparklines.
+Keep the current time visible in the header.
+Mark the current hour with a vertical hairline.
+Progress bars are 4px flat fills.
+Use ink for the numerator and muted for the denominator.
+
+## Checks
+
+Check overflow at the exact target viewport.
+Inspect every exported image for clipping and overlap.
+Wait for local fonts before rendering.
+Render at a device scale factor of two.
+Keep tooltips out of the captured state.
+Check contrast on every surface.
+Keep at most three font weights, never above 600.
+
+Header: a 20px, weight 500 title left and date range right.
+Omit breadcrumbs, identity lines, helper lines and footer captions.
+Use at most one hairline below the header.
+Create breathing room with margins; avoid half-empty panels.
+
+Use story-bearing data in examples. Annotate one event per chart with a leader line, a hollow ink dot, and a short label in empty space. Keep the latest point as the single accent.
+
+Use one signature element per board. Place it alongside the main metric so it reinforces the data story.