2 Commits

Include renames

Author	SHA1	Message	Date
jcoffey-dev	820ef5df2c	Schema: each expression field says which values and variables it accepts ... The registry knows, for every expression field, the constants it may evaluate to and the variables its conditions may read, and enforces both. The schema served to INBUXA Admin described every one as a bare x:Expression, so the console could offer nothing better than free text. tools/fork/expr-schema.py reads those contexts from the generated registry code and writes them onto each field's type as expression: {constants, variables}. All 124 expression fields are covered. CI runs it with --check so the schema can't drift from the registry.	2026-09-28 10:36:43 -07:00
jcoffey-dev	a8dde68800	Add the personal-data catalog and the check that keeps it true ... Phase 2 of the personal-data catalog spec. resources/privacy/catalog.toml classifies every object in the schema (316) and inbuxa's own JMAP objects (12): each property that can hold personal data, with its categories, and for objects that hold any, whose data it is, where it lives, its scope and what bounds its retention (a named setting where there is one). Twenty sources that are no object -- the log file, exporters, webhooks, spam lookups, the Explain cache, relays and hooks, push, legacy-use records -- carry the same facts plus the settings that turn them on, whether the data leaves the host, and the code that writes it. Classifications of objects that hold data about people are from the spec's source map; the rest are typed from the schema alone (address, IP, secret). tools/fork/privacy-check.py fails CI when an object or inbuxa object has no entry, when a property the schema types as an address, IP or secret is left to its object's default, when an entry names an object, property, setting or code path that is gone, or when it uses a word outside the catalog's vocabulary. --unlisted prints starting entries. strip.py's report gains "Unclassified in the privacy catalog": objects and fields new in an import and not classified, informational like the Enterprise flags. Tested: 13 unit tests (tools/fork/tests): the check passes on this tree; fails on an unclassified object, an address hidden behind a default, a secret in a set or object reference, stale properties, objects, settings and code paths, an unlisted inbuxa object and a word outside the vocabulary; --unlisted's entries; and the strip report on a synthetic import. The check and the tests run in the fork-checks job.	2026-09-28 06:54:34 -07:00