Jeremy Vyska 2f3e5afac1 Add retention policy knowledge to the privacy domain ... Two articles covering retention policies for extension-owned tables, the gap that lets high-volume log tables grow unbounded: - register-owned-log-tables-for-retention-policies: an extension's own log tables must be added to the allowed-tables list from install AND upgrade code, guarded by IsAllowedTable plus an upgrade tag, with a mandatory minimum retention where audit needs one. - ship-a-default-retention-policy-setup: registration only makes a table selectable; nothing is deleted until a Retention Policy Setup record exists, so ship one (disabled by default) as the platform's own Retention Policy Installer does. Each ships good/bad AL samples. Claims verified against the BC admin docs and the Retention Policy module in microsoft/BCApps. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011gvTjm746MtJEVWeRTbG46		2026-09-10 12:58:26 +02:00
..
knowledge	Add retention policy knowledge to the privacy domain	2026-09-10 12:58:26 +02:00
skills	Improve partner onboarding and documentation navigation (#174)	2026-09-09 17:31:03 +02:00