feat: includeHidden — export carries every visibility tier for migration-grade canon completeness

This commit is contained in:
David Snelling 2026-07-27 11:22:25 -07:00
parent 3e4a17dcdf
commit 63c1eeb902
4 changed files with 205 additions and 27 deletions

View file

@ -61,6 +61,15 @@ to the caller today.
Migration-audit evidence, not a repair: nonzero drift is reported loudly
(`console.warn` with the counts) and nothing is auto-healed — run `brain.repairIndex()`
to reconcile the metadata index once drift is confirmed.
- **New: `export(selector, { includeHidden: true })`** (default: false — unchanged
behavior). Without it, a whole-brain/predicate export could never carry a
`visibility:'internal'` or `'system'` row, in EITHER `enumeration` mode — a real gap
for a bulk-migration fold auditing per-visibility-tier, where a hidden tier is real
user data, not noise to drop. `includeHidden` admits both tiers into candidacy in
both modes (and implies `includeSystem`; `includeSystem` alone keeps its narrower,
pre-existing meaning). **Migration-grade exports set `includeHidden: true`** — a
complete-canon export must carry every visibility tier; consumer-facing exports
leave it off.
- **Ops note (consumer-invisible): the release pipeline's forge-registry publish now runs
on CI**, triggered by the release tag, instead of PUTting the tarball from the laptop
over WAN — no change to what gets published or how a consumer installs it.