chiltepin 0.47.8 → 0.47.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chiltepin",
-  "version": "0.47.8",
+  "version": "0.47.10",
   "description": "Documentation-as-code CLI: write Markdown with typed YAML blocks for API docs, architecture & system design (C4, ERDs, sequence diagrams), frontend & design systems, ADRs and decision records, planning, and slide presentations. Validate like code with `chiltepin check`, export to HTML, slides, or PDF. AI-native — one-command agent skill (npx skills add jdiejim/chiltepin -y) and a visual Studio.",
   "license": "MIT",
   "type": "module",
@@ -25,9 +25,9 @@
     "picocolors": "^1.1.1",
     "react": "^18.3.1",
     "yaml": "^2.6.1",
+    "chiltepin-render": "0.34.2",
     "chiltepin-core": "0.25.0",
-    "chiltepin-render": "0.34.0",
-    "chiltepin-studio": "0.16.4"
+    "chiltepin-studio": "0.16.6"
   },
   "optionalDependencies": {
     "playwright": "^1.49.0"

package/templates/skill/SKILL.md

@@ -92,6 +92,7 @@ content. Rewrite the whole document only when the user requests a rewrite.
 | What is this made of? | `anatomy` · `composition` · `erd` · `layers` | labeled parts of a string → anatomy; proportions → composition |
 | What causes this? | `fishbone` · `matrix` | one effect, branching causes → fishbone |
 | Why did we decide this? | `options` · `proscons` · `scqa` · `takeaways` · `callout` | the ADR shape → `reference/recipes.md`; the decision alone → callout |
+| Is it a table, or a table with a job? | `table` · `statustable` · `matrix` · `heatmap` · `benchmark` · `scorecard` · `glossary` · `changelog` · `inventory` · `audit` · `checklist` · `journey` | `table` only when every cell is a plain fact. A status per row → statustable; two axes with a mark or permission → matrix; a value grid read by intensity → heatmap; measured numbers compared → benchmark; scores you gave → scorecard; term — definition → glossary; releases → changelog; components with a maturity → inventory; findings with evidence → audit; a standard applied → checklist; touchpoints per stage → journey; API params → endpoint |
 | What does the API accept and return? | `endpoint` · `code` · `packet` · `table` | HTTP surface → endpoint; wire format → packet; error codes → table |
 | How does the AI workflow run end to end? | `flow` · `swimlane` · `block` · `cycle` · `sequence` | agents, models, tools, humans and memory as `flow` nodes with `kind: agent / llm / tool / human / memory` — a RAG pipeline, a router, a multi-agent hand-off, a generate-check-repair loop; several owners per step → swimlane; the deployment around it → block; an improve-and-re-evaluate loop → cycle; one turn's timing → sequence. Draw the workflow the request describes; `agentloop` is only the fixed single-agent frame |
 | How does one agent's loop behave? | `agentloop` · `trace` · `prompt` · `context` | the loop → agentloop; one real run → trace; the contract → prompt; window contents → context |
@@ -140,6 +141,9 @@ existing fence only to silence the `W_ALIAS_TYPE` warning.
   `code` block (`kind: compare` for before / after); terms are a
   `glossary`; questions a reader will ask are a `faq`; a runbook is
   `steps`; side-by-side snippets or nested diagrams are a `gallery`.
+  Before writing `table`, read the "table with a job" row: a grid whose
+  rows carry a status, score, definition, release, or finding has its own
+  block, and that block draws the status chips and derived values for you.
 - Diagram data (node names, messages, labels, values) is never trimmed to
   fit. Split a dense diagram into two; `chiltepin check` warns at the caps.
 - Every arrow says what crosses it, as a verb phrase, never "uses". A `c4`

package/templates/skill/reference/blocks/tables-data.md

@@ -9,13 +9,18 @@ Structure & emphasis for headline numbers, targets, and code as evidence
 (`stats`, `slo`, `code`).
 **Answers**: What are the exact values? How big, fast, or reliable is it,
 as measured?
-**Not this family**:
+**Not this family** — a table with a job has its own block:
 
 - cells are permission levels → `matrix` (business.md)
 - a value grid read by intensity → `heatmap` (charts-overviews.md)
 - the numbers move over time → `chart` (charts-overviews.md)
 - scores you invented rather than measured → `scorecard` or `harvey`
   (business.md)
+- a status per row → `statustable` (planning.md); components with a
+  maturity → `inventory` (design-system.md)
+- term — definition → `glossary`; releases → `changelog`; findings with
+  evidence → `audit`; a standard applied → `checklist` (quality.md)
+- touchpoints per stage → `journey`; API params / responses → `endpoint`
 
 ### Tables & metrics
 
@@ -52,4 +57,6 @@ table; when the change is the point, `kind: compare` or `kind: diff`.
 `highlight: "3-5, 8"` bands the lines that matter; `lines: true` numbers
 them; `cols: 2` sets snippets side by side (request / response); `kind:
 compare` is before / after under eyebrows; `kind: terminal` is a `session`.
+`lang: text` for prompts and plain notes (no highlighting); `lang: markdown`
+for Markdown source.
 `steps` for a runbook with prose between commands; `gallery` for a card grid.