[chubes4]

Fixes #3685

Root cause

Data Machine registered two filters that Markdown Database Integration no longer applies:

• CanonicalPersistencePolicy declared partition_by identities for datamachine_jobs and datamachine_logs through markdown_db_table_persistence_policy. The only consumer was MDI's canonical-persistence write engine, which was removed in Remove dead code left by the backend retirements Automattic/markdown-database-integration#456. mdi-native now folds the legacy partitions into ordinary snapshots (Fold legacy row-partitioned tables into snapshots Automattic/markdown-database-integration#459).
• LogPersistencePolicy limited the Action Scheduler log snapshot through markdown_db_persistent_table_query. Only MDI's retired SQLite mirror applied that filter. git grep in MDI main finds no references.

Change

Deleted both classes, their two smoke tests, and the two register() calls in AlwaysOnServiceProvider. The datamachine_action_scheduler_log_persistence_row_budget filter goes with them; nothing in Data Machine or its sibling plugins uses it.

Action Scheduler still prunes its own logs through its retention cleanup.

Verification

• php -l passes on the changed file.
• Grep shows no remaining references in inc/, tests/, data-machine-business, intelligence or a8c-intelligence.
• End to end on a disposable copy of a live mdi-native site running this branch:
  • WordPress boots with neither class nor filter present.
  • A wp_datamachine_jobs insert succeeds (id 296207).
  • Action Scheduler tables read normally, and MDI doctor reports healthy.

---

AI assistance: implemented and verified by Claude (Claude Code, Franklin) for @chubes4: code removal, consumer search and end-to-end run.