feat(db,rest,ui)!: per-consumer table + slug-scoped REST routes (v2.0.0 — BREAKING)

[raftaar1191]

⚠️ Breaking change

AccessControlManager now requires a second constructor argument — a per-consumer table slug. Every embedding plugin gets its own database table, object-cache group, and REST route prefix.

// Before (v1.x)
$manager = new AccessControlManager( 'my_plugin_access_control_providers' );

// After (v2.0.0)
$manager = new AccessControlManager(
    'my_plugin_access_control_providers',
    'my_plugin'  // slug: ^[a-z0-9_]{1,32}$
);

Existing v1.x consumers that pass only the providers filter tag will fail with ArgumentCountError immediately on upgrade. Slugs that don't match the pattern throw \InvalidArgumentException at construction time.

Why

Previously every consumer wrote into the single shared {prefix}wpb_access_control table and registered the same /wpb-ac/v1/... routes. Two plugins embedding the library on the same WordPress install collided on:

• Storage — both wrote rows into one table; namespace conflicts were the only thing keeping them apart.
• Cache — single wpb_access_control object-cache group meant wp_cache_set() writes from Plugin A clobbered Plugin B's reads.
• REST routes — last-loaded-wins; only one manager's handler actually served /wpb-ac/v1/rules/....

v2.0.0 fixes all three at the source: each consumer's slug becomes the table name, the cache group, the transient prefix, and the REST route prefix.

Migration

1. Manager constructor — add the slug (see snippet above).
2. wpbAcConfig — add 'pluginSlug' => 'my_plugin'.
3. REST URLs — /wpb-ac/v1/rules/... → /wpb-ac/v1/{slug}/rules/... (and same for /providers, /users, /namespaces).
4. Optional one-off SQL copy from {prefix}wpb_access_control to the new per-slug table — see README.md § "Upgrading from 1.x". The library does NOT auto-migrate.

Changes

• src/Slug.php (NEW) — Slug::sanitize() validates ^[a-z0-9_]{1,32}$ and throws on invalid input. Used consistently by RuleTable, RuleQuery, and AccessControlManager.
• src/Database/Rule/RuleTable.php — ctor accepts $table_slug; sets $name and $db_version_key per instance.
• src/Database/Rule/RuleQuery.php — ctor accepts $table_slug; sets $table_name and $cache_group; replaces single static $table_setup flag with per-slug registry; folds slug into the transient_key hash so cached payloads cannot collide.
• src/AccessControlManager.php — second required ctor arg $table_slug; new get_table_slug() getter; threads slug into RuleQuery + RulesController.
• src/RestApi/RulesController.php — accepts the slug; every register_rest_route call now uses '/{slug}/...'.
• js/AccessControl.js + js/components/UserSearchPanel.js + js/index.js — new required pluginSlug prop / wpbAcConfig field; every apiFetch URL carries the slug segment. The auto-render path bails with a clear console.error when pluginSlug is missing.
• Tests — new SlugTest (17 cases), new RuleQueryConstructorTest (8 cases including two-instance isolation), 2 new register_routes tests in RulesControllerTest verifying the slug prefix appears on every route group and distinct slugs produce distinct paths.

Test plan

• composer test — 190 tests / 267 assertions, all green (was 160/218)
• npm run build — wp-scripts compiles cleanly with the new pluginSlug prop wiring
• Two-plugin smoke test: install two consumers with different slugs; confirm two tables exist, rules don't bleed across them, and REST GETs return empty for the other plugin's namespace
• Cache-isolation check: PUT a rule via Plugin A, GET it via Plugin B's slug — expect empty (not A's cached payload)
• Verify new AccessControlManager('x', '') / 'Has-Caps' / '../etc/passwd' all throw with a readable message
• CI matrix passes on PHP 8.1 – 8.5

🤖 Generated with Claude Code