@dforge-core/dforge-mcp 0.1.7 → 0.1.9

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.
package/CHANGELOG.md CHANGED
@@ -4,6 +4,28 @@ All notable changes to `@dforge-core/dforge-mcp`. This project uses semver-ish
4
4
  `0.1.0-rc.N` pre-release tags; the published version is set at publish time via
5
5
  the release workflow, so committed `package.json` versions are placeholders.
6
6
 
7
+ ## 0.1.8
8
+
9
+ ### Added
10
+ - **`dforge_module_validate` now flags a grid-style data view over an entity
11
+ with no visible column.** Errors when a column-rendering view (grid, list,
12
+ kanban, calendar, gallery, tree-grid, master-detail, or the default) draws an
13
+ own-module entity that has no *visible scalar column* — a field whose `flags`
14
+ include `V` and whose `columnType` isn't a set (`S`). Without one the view
15
+ renders the runtime empty state *"No visible columns configured for this
16
+ entity."* This mirrors the server's install-time `DataViewVisibleColumnValidator`,
17
+ so authors catch it pre-flight instead of at pack/install. Column-agnostic view
18
+ types (`diagram`, `matrix`, `library`) are exempt; cross-module entities are
19
+ skipped; the check runs after trait expansion so a trait-contributed `V` field
20
+ counts.
21
+
22
+ ### Skill
23
+ - `dforge-mcp-author`: documented the **visible-column requirement** for
24
+ column-rendering data views. `references/data-views.md` gains a "the entity
25
+ needs a visible column" rule (visibility is entity-driven via the `V` flag, not
26
+ the view's `columns` array) plus common-mistake bullets, and
27
+ `references/validation-checklist.md` gains matching checklist/red-flag entries.
28
+
7
29
  ## 0.1.7
8
30
 
9
31
  ### Changed