@dforge-core/metadata 0.0.41 → 0.0.43

package/CHANGELOG.md

@@ -5,7 +5,40 @@ All notable changes to `@dforge-core/metadata` are documented here.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this package adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [Unreleased]
+## [0.0.43] — 2026-10-19
+
+### Added
+
+- **`registers.schema.json`, `analyticTotals`:** an `accounting` register's second per-period cache,
+  keyed by the analytic slots as well as the account, cached dimensions and period, for the accounts
+  the chart flags (`accountFlag`). It sits beside `totals` in an entity of its own. Declares `entity`,
+  `period`, `periodField`, `accountField`, `accountFlag`, `analyticFields`, `resources` and optional
+  `dimensions`; balance, turnover and information registers refuse it.
+- **`entity.schema.json`, `lineDateField`:** an `A` column that posts from lines names a line column
+  dating each line's movement instead of `dateField`. Needs `lineEntity`; an `L` column refuses it.
+  Its period is judged by the stamped date (after `dateTrunc`); `recordChangesOnly` info registers take
+  one line per key. Pack-time check also refuses it with `periodDimField`, or missing from
+  `lockedLineFields` / `groupLinesBy`.
+
+## [0.0.42] — 2026-10-15
+
+### Added
+
+- **`entity.schema.json`, `periodGuards`:** closed-period locks for a document that posts to no
+  register — a period entity, the date the period follows from, the column that references it, and
+  `lockedFields` (with `lineEntity` / `lineField` / `lockedLineFields` for lines). Not allowed on an
+  extension.
+- **`entity.schema.json`, partial and unique indexes:** an entry in `indexes` takes `unique` and
+  `where` (a SQL condition, so uniqueness holds among the rows it selects).
+- **`roles.schema.json`, rights keys are checked for their prefix:** `propertyNames` accepts a bare
+  entity code, `module.entity`, `action:<code>`, and `sp:` / `report:` with an optional module
+  qualifier, so an editor flags `"post_invoice": "E"` (which install would drop) as it is typed.
+- **`RegisterSource`** type is exported from the package root.
+
+### Changed
+
+- **DSL builtins `getAccountBalance` / `getAccountTurnover`:** the signatures and hints show the new
+  last `options` argument — `groupBy`, `exclude` and (balance only) `before`.
 
 ## [0.0.41] — 2026-10-13
 

package/dist/dsl/index.js

@@ -805,15 +805,15 @@ var BUILTINS = [
   },
   {
     name: "getAccountBalance",
-    signature: "getAccountBalance(register, account, filter?, asOf?)",
+    signature: "getAccountBalance(register, account, filter?, asOf?, options?)",
     returns: "object",
-    doc: "Balance of one account of an accounting register: `{debit, credit, net}` per resource. `filter` narrows by a dimension, or by an analytic kind the ACCOUNT declares \u2014 an analytic takes the key alone, or `{ entity, value }` to name one entity of a kind that is a union of several."
+    doc: "Balance of one account of an accounting register: `{debit, credit, net}` per resource. `filter` narrows by a dimension, or by an analytic kind the ACCOUNT declares \u2014 an analytic takes the key alone, or `{ entity, value }` to name one entity of a kind that is a union of several. `options`: `groupBy` (a name or array \u2014 returns an array, a row per combination with a non-zero balance), `exclude: { entity, key }` (leaves out that document's postings) and `before` (a moment, exclusive, in place of `asOf`)."
   },
   {
     name: "getAccountTurnover",
-    signature: "getAccountTurnover(register, account, filter, from, to)",
+    signature: "getAccountTurnover(register, account, filter, from, to, options?)",
     returns: "object",
-    doc: "What moved through one account over an interval: `{debit, credit, net}` per resource. `filter` narrows as in `getAccountBalance` and may be `null`; `from` and `to` are both required."
+    doc: "What moved through one account over an interval: `{debit, credit, net}` per resource. `filter` narrows as in `getAccountBalance` and may be `null`; `from` and `to` are both required. `options` takes `groupBy` and `exclude` as in `getAccountBalance`; a grouped turnover has a row per combination that moved."
   },
   {
     name: "getCorrespondence",