Three real bugs found live against production api.scribase.com (`scripts/verify-live.php`), all blocking `scribase_memory_task` end-to-end:
1. `ensureMemoryTable()` hid `CREATE POLICY` inside a `DO $$ ... $$` block for idempotency; Scribase's own migration linter only scans top-level statements for `ENABLE ROW LEVEL SECURITY` + `CREATE POLICY`, so every bootstrap tripped `missing_rls` and `store` failed with `sql_blocked_by_lint` before a single memory was ever written.
2. Making the policy literal then tripped the linter's separate `permissive_policy` rule on `USING (true) WITH CHECK (true)` — correctly, since that predicate would authorise Supabase's `anon`/`authenticated` roles too if this table were ever exposed via PostgREST. Fixed by denying those two roles by name instead.
3. A `DROP POLICY IF EXISTS` (added for idempotency) and `memoryForget()`'s plain `DELETE` are both classified destructive by `database/execute` and silently no-op with `{"status":"confirmation_required"}`, HTTP 200, no `error` key — this client checked only the HTTP status, so `forget` always reported `not_found` while deleting nothing. Fixed: `ensureMemoryTable()` now does a cheap read-only existence check and only ever runs its one-time bootstrap script once (no `DROP` needed at all); `memoryForget()` now sends `confirm: true` (safe — its `DELETE` is already scoped to one caller-supplied id + the current scope, exactly the explicit single-purpose action `confirm` exists for). Both paths also now check for `confirmation_required` explicitly instead of inferring success from HTTP status alone.
Full 9-step `scripts/verify-live.php` suite (every tool, store/recall/search/isolation/forget, a real copy-on-write branch) now passes end-to-end against a fresh production temporary project — re-confirmed on two separate runs.
Also added `scripts/toolbox-check.php`: a live, zero-setup verification that the official Symfony AI MCP bridge (`ClientToolset`+`McpToolbox`) really spawns this package's MCP server and lists its real tools — closing half of the previous `class_exists()`-only verification gap on `examples/symfony-ai-agent-demo.php`. It also surfaces a real, confirmed-live naming quirk: `McpToolbox`'s `prefix: ''` is its own default sentinel for `<toolset-name>_`, not a "no prefix" override, so tools list as `scribase_scribase_<tool>`. The other half — the Agent loop actually calling a tool via a live LLM — still needs an owner-gated `OPENAI_API_KEY` not available in this environment; every constructor/method call in that demo was instead checked against the real installed symfony/ai-* source (exact signature matches, not just class_exists()), and this is disclosed plainly in the script and README rather than faked.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The caelum0x GitHub account is flagged and github.com/caelum0x/* 404s
publicly now. The sibling-repo link in the README and the User-Agent
self-reference in scripts/verify-live.php both pointed at the dead
GitHub host. Rithub (git.ereboslab.com) is the real, publicly-clonable
host for this repo and its siblings.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>