ingitdb / dalgo2ingitdb4local / 28701449711

99%

push

github

fix: encode dal.Key parent chain into record path (per-parent scoping) (#1)

The adapter mapped a dal.Key to an on-disk record path using only the leaf
collection + record id, dropping the key's parent chain. Two keys sharing a
leaf but under different parents — spaces/family/contacts/c1 and
spaces/work/contacts/c1 — resolved to the same file and clobbered each other.

Add resolveScopedCollection (mirrors the dalgo2ingitdb and dalgo2ingitdb4github
siblings): walk key.Parent() and interleave each ancestor record id with its
subcollection name into the DirPath (spaces/<spaceID>/contacts/...). Top-level
keys are unchanged. Both readonlyTx.Get and the shared resolveCollection (now
hoisted onto readonlyTx and reused by readwriteTx) route through it so reads and
writes agree.

Also completes go.sum with the go.mod hashes for dal-go/dalgo and x/sys that
were missing (a fresh checkout could not build without them).

Regression tests: same-leaf keys under different parents map to DISTINCT paths;
deep-nesting + error branches; end-to-end filesystem round-trip proving no
cross-parent clobber.


Claude-Session: https://claude.ai/code/session_01FV3pbooAc9UPpNdiaJuKve

Co-authored-by: Alexander Trakhimenok <alex@Alexanders-MacBook-Pro.local>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

57 of 63 new or added lines in 2 files covered. (90.48%)

740 of 746 relevant lines covered (99.2%)

1.14 hits per line