@dforge-core/dforge-mcp 0.2.44 → 0.2.45

package/skills/dforge-mcp-author/references/validation-checklist.md

@@ -162,8 +162,8 @@ For each action:
 
 ## Translations
 
-- [ ] `translations/en-US.json` exists
-- [ ] Has `entities` section with `label`, `desc`, and `fields` for every entity
+- [ ] **No** `translations/en.json` / `en-*.json` — install skips them. English is each definition's own short label (entity/field/role/setting `description`, view/menu/action/report `label`)
+- [ ] Each `translations/<locale>.json` (one per `supportedLocales` entry) has an `entities` section with `label`, `desc`, and `fields` for every entity
 - [ ] Every field (including trait-provided: `created_date`, `last_updated`, etc.) has a `label`
 - [ ] Has `views` section with labels for every data view
 - [ ] Has `menus` section matching the `ui/menus.json` structure
@@ -172,7 +172,6 @@ For each action:
 - [ ] (Optional) Constraint messages localized under `entities.<e>.constraints.<c>.message` — opt-in; a missing override for a declared `supportedLocales` entry warns (surfaced by `dforge_module_validate` and at install) but does not fail install
 - [ ] Has `settings` section with labels for every setting (if settings exist)
 - [ ] Has `folders` section with label for the root folder
-- [ ] Additional language files (if any) have the same structure as `en-US.json`
 - [ ] Manifest `supportedLocales` lists every non-English locale that has a `translations/<locale>.json` file (English is not listed)
 
 ## Versioning

package/skills/dforge-module-build/SKILL.md

@@ -36,12 +36,15 @@ flags, or column patterns.
 | Suggest a value when another field is edited (a reaction), incl. from a bridge module | `dforge://reference/reactions` | `dforge://schema/entity`, `dforge://schema/deps` |
 | Add a trait | `dforge://reference/traits` | — |
 | Add a number sequence | `dforge://reference/number-sequences` | — |
+| Add an accumulation register (`A` column, `registers.json`) | `dforge://reference/registers` | `dforge://schema/registers` |
+| Edit the manifest (version, `supportedLocales`, dependencies, `entities` map) | `dforge://reference/manifest` | `dforge://schema/manifest` |
 | Add a grid / list view | `dforge://reference/data-views`, `dforge://example/ui/data_views.json` | — |
 | Add a matrix (pivot) view | `dforge://reference/data-views` (§Matrix), `dforge://example/matrix-budget/ui/data_views.json`, `dforge://example/matrix-budget/entities/budget_line.json` | — |
 | Add kanban / calendar / tree-grid / master-detail | `dforge://reference/data-views` | `dforge://schema/data-views` |
 | Hide columns from a user type (column-level security) | `dforge://reference/security` (§Column-level security), `dforge://example/column-security/entities/product.json`, `dforge://example/column-security/ui/folders.json` | — |
 | Add a menu | `dforge://reference/menus`, `dforge://example/ui/menus.json` | — |
 | Add an action | `dforge://reference/action-dsl`, `dforge://example/logic/actions/mark_done.dsl`, `dforge://example/ui/actions.json` | `dforge://docs/dsl` |
+| Email a file the script builds, or ship saved values / a PDF preview for an action's dialog | `dforge://reference/action-dsl` (§Email and §PDF and file output: `sendEmail` attachments, `attachText`, `attachBase64`; §Registering the action: `paramSets`, `previewTemplate`) | `dforge://docs/dsl` |
 | Share helpers between actions, or call another module's functions | `dforge://reference/action-dsl` (§Function libraries): `logic/functions/*.dsl`, imports in `deps/<module>.json` | `dforge://schema/deps` |
 | Add a trigger | — | `dforge://schema/triggers`; condition syntax in `dforge://docs/dsl` |
 | Add a scheduled job | `dforge://reference/jobs` | `dforge://schema/jobs` |
@@ -115,6 +118,10 @@ Enough to author inline; load the linked reference for the full detail.
 - **Manifest:** non-English locales go in `supportedLocales` (`ll-CC`, never
   `en`/`en-US`); there is no `translations` manifest key. `security` has both
   `roles` and `folders`. → `manifest`
+- **English is the definitions' text:** install skips `translations/en*.json`, so
+  never create one. Give every entity, field, role and setting a short
+  `description` and every view, menu, action and report a short `label` — that
+  is what the English UI shows. → `translations`
 - **Seed data:** explicit numeric PKs under `{entity}_id`; parents before
   children via the `NN-` prefix. Use `dforge_seed_add`.
 
@@ -160,6 +167,7 @@ approval, then patch. Reach for the **composite tools first**:
 - roll-up total → `dforge_entity_rollup_add`
 - status column → `dforge_entity_status_add`
 - plain scalar → `dforge_entity_field_add`
+- change an existing field (label, flags, type, …) → `dforge_entity_field_modify`
 
 **Field batching rule** — the only Phase 1 exception to one-at-a-time. A field
 is batchable only if ALL of: scalar primitive (string/integer/decimal/boolean/
@@ -285,7 +293,8 @@ stated trigger; every report's params sit on a dataset.
 ## Phase 4 — Polish (mostly optional)
 
 - **Settings** — `dforge_setting_add` per configurable value the user asked for.
-- **Translations** — run **`dforge_translation_sync`**. It generates every
+- **Translations** — only for the locales in `supportedLocales`; English needs
+  no file. Run **`dforge_translation_sync`**. It generates every
   required key from the module's own contents, never overwrites existing
   translated text, and fills the **role labels that are completeness-enforced at
   install**. Run it after any entity/view/role change, and always before Phase 6.

package/skills/dforge-module-ship/SKILL.md

@@ -78,9 +78,9 @@ formula column shape; flags letters (`V I E M H` only); every entity has a
 default grid and `dataSources` at root with `"order"` as a string array; menu
 leaves use `dataViewCode` and bare icon names; every entity in at least one
 role's rights; action `script` values are bare filenames; seed PKs numeric with
-parents first; a `translations/<locale>.json` for every `supportedLocales` entry
-**plus** the `en-US` base, each carrying a label for every trait-provided field
-and every role.
+parents first; a `translations/<locale>.json` for every `supportedLocales` entry,
+each carrying a label for every trait-provided field and every role. No English
+file — install skips `en*.json`; English is the definitions' own short labels.
 
 If translations are thin, run **`dforge_translation_sync`** now rather than
 hand-patching — it fills exactly the keys install requires.
@@ -156,6 +156,34 @@ package — fix the referenced files, report what changed, and immediately re-ru
 validate → pack → install. Keep sign-off for product/design choices or genuinely
 ambiguous fixes.
 
+**If install hangs, or fails with a bare HTTP 500 or 400 "deadlock":** look for
+a lock before touching the module. An install's `ALTER TABLE` waits behind any
+open transaction on the module's tables — an idle `psql` session, an ad hoc
+read left open, a script that never commits — and waits without a message,
+for an hour or more. Check `pg_stat_activity` for a blocked `ALTER` and the
+session holding it. Never install while scripts hold transactions on the
+module's tables; run ad hoc scripts in autocommit.
+
+**If install times out on the client while rebuilding a register cache:** the
+server goes on and finishes (an analytic cache over 1.5 million postings took
+about 18 minutes). Check the server log or the cache before installing again.
+
+**Same version installed "successfully" but nothing changed:** a re-install of
+the same `version` is skipped (`isEmpty: true`). Bump the version, or pass
+`--force` on a dev tenant.
+
+**Local dev stack pitfalls:**
+- After installing into a local docker setup, restart `dforge-api` if the UI
+  still shows the old metadata; its cache can stay stale.
+- The tenant URL is `http://<tenant>._.localhost:5179`. `<tenant>.localhost`
+  and `<tenant>_.localhost` sign into **another** tenant.
+- "no token for tenant X": the CLI session expired (a token lasts about an
+  hour). Run `dforge-cli auth login --url <tenant url>`.
+- "tenant at db_schema_version … is ahead of this binary" after rebuilding the
+  platform: install through the server with `--url`.
+- Don't keep scaffold copies of a module (same `code`, another `moduleId`)
+  anywhere a folder publish can pick them up.
+
 **If install fails on auth (401/403) or connectivity (refused):** that is
 credentials/connectivity, NOT a module defect. Tell the user to verify
 `DFORGE_URL` and `DFORGE_TOKEN`. **Do not backtrack** to earlier phases.

package/skills/dforge-mcp-author/examples/column-security/translations/en-US.json

@@ -1,35 +0,0 @@
-{
-	"entities": {
-		"product": {
-			"label": "Product",
-			"fields": {
-				"name": { "label": "Product Name" },
-				"sku": { "label": "SKU" },
-				"quantity": { "label": "Quantity On Hand" },
-				"cost_price": { "label": "Cost Price" },
-				"sale_price": { "label": "Sale Price" },
-				"margin": { "label": "Margin" }
-			}
-		}
-	},
-	"folders": {
-		"warehouse": { "label": "Warehouse" },
-		"finance": { "label": "Finance" }
-	},
-	"roles": {
-		"column_security.storekeeper": { "label": "Storekeeper" },
-		"column_security.accountant": { "label": "Accountant" }
-	},
-	"views": {
-		"product_grid": { "label": "Products" }
-	},
-	"menus": {
-		"product_menu": {
-			"label": "Products",
-			"items": {
-				"catalog": { "label": "Catalog" },
-				"all_products": { "label": "Products" }
-			}
-		}
-	}
-}