[enmand]

Closes #19.

Documents the now-implemented retained-parent-ancestry rule across the knowledge base and closes the adoption tracking issue.

Changes

• dwn/protocols.md — new "Parent ancestry" subsection: a child's structural parent is proven by the parent's retained initial write in the expected protocol, not current liveness; a soft delete does not remove ancestry; prune removes it and is terminal; roles/grants stay current-state. New common trap for soft-deleted ancestry.
• enbox/records.md — new "Parent ancestry and deletes" section for current TypeScript and Rust behavior, including that a pruned parent's rejected descendant settles terminally (superseded, no dead letter).
• conformance/protocols-and-authorization.md — checklist items: retained-initial-write ancestry for soft-deleted parents, terminal rejection for pruned parents, and arrival-permutation equality.
• decisions/0007-retained-parent-ancestry.md — status now "implemented in Enbox #1685 and Rust #304"; the parity-divergence note is closed; references dwn-spec#70.
• implementation/dependency-resolution.md — resolution section updated to reflect that both implementations retain ancestry and that the interim terminal classification for soft deletes is superseded.

Adopters

• fix(dwn-sdk-js): preserve parent ancestry after soft deletes enbox#1685 — TypeScript implementation
• Retained parent ancestry: a soft delete does not remove ancestry; prune does (ADR 0007) enbox-rust-core#304 — Rust implementation
• enboxorg/dwn-spec#70 — clarification that "exist"/ancestry means the retained write and that prune removes ancestry

Issue #19 checklist

• ADR 0007 recorded
• implementation/dependency-resolution.md updated
• DWN-REC-004 sources/related updated
• Retained-ancestry rule documented in dwn/protocols.md and enbox/records.md
• Conformance checklist items added
• dwn-spec clarification filed (enboxorg/dwn-spec#70)
• Upstream Enbox implementation landed (fix(dwn-sdk-js): preserve parent ancestry after soft deletes enbox#1685)