document the automatic retry of transient transaction failures
note that a transactional save refreshes its tracking at the commit
correct and dry the whole page set
Genericize examples: no explicit references to consumer services Present all examples with neutral domain types (the running Cat/Cats sample, plain User/Order/Team) instead of naming or attributing the Etherna consumer services. Document the rule in the wiki AGENTS.md. Library/driver references (Etherna.MongoDB.*, Etherna.MongODM.*, the org repo) are unchanged.
Add Advanced & reference section; normalize internal links - Execution contexts: ambient per-flow state, automatic wiring, opening one on background threads - Exclusive access: RunWithExclusiveAccessAsync, lockout semantics, when to use it - Best practices and pitfalls: scopes/captive dependencies, no-cache scans, atomic writes, compare-by-Id, cross-context references, background-thread contexts — with real service examples - Exceptions reference: the Mongodm* exceptions and what triggers each - Complete the sidebar with all six sections - Convert custom-text wiki links to unambiguous Markdown links and document the convention
Add Change tracking and saving + Transactions pages - Change tracking and saving: proxy auditing, [PropertyAlterer], member-level atomic saves guarded by schema id, save-as-sync-point, per-member concurrency, implicit transaction, denormalized dependency updates - Transactions: ExecuteInTransactionAsync usage, enlistment, requirements/limits, vs implicit saves, when to prefer atomic single-document operations