abode

The postgres importer inserts records sequentially with FK enforcement live,
so it depends on records arriving in dependency order. That requirement was
implicit in each backend's export table list; make it explicit and enforced.

- Add EXPORT_KIND_ORDER (user, abode, resident, apikey, note) as a documented
  single source of truth, with the FK dependency chain spelled out on its doc
  comment, and note the ordering guarantee on the ExportEnvelope wire-format
  doc. Derive the isExportKind set from it.
- Both backends' export() now iterate EXPORT_KIND_ORDER via a loader map
  (postgres omits note by leaving it out of the map), so emission order is
  tied to the constant and can't drift.
- Tests: a change-detector on EXPORT_KIND_ORDER, plus assertions that both the
  sqlite and postgres (fake) exports emit record kinds grouped in FK-safe
  order (kind rank non-decreasing down the stream, after the leading meta).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-23 00:14:15 +00:00

authenticate.test.ts

ci: add pull request quality gates

2026-07-22 21:50:29 +00:00

convertError.test.ts

ci: add pull request quality gates

2026-07-22 21:50:29 +00:00

export-import.test.ts

docs: codify the FK-safe stream ordering as a wire-format invariant

2026-07-23 00:14:15 +00:00

hash.test.ts

feat(tests): add unit and integration test suite (node:test)