db-optimize: support filtering by specific table names #108

Problem

db-optimize always optimizes ALL database tables, ignoring user intent to target specific tables.

• "optimize the database table wp_options" → optimizes all 115 tables (db-optimize ability should handle specific table(s) instead of optimizing all tables #69)
• "optimize the WooCommerce tables" → should only optimize WooCommerce-specific tables (db-optimize tool should understand "optimize the WooCommerce tables" #73)

Tool selection works correctly (verified in PR #102 tests), but the ability lacks a tables input parameter.

Current behavior

The PHP backend (includes/abilities/db-optimize.php) runs SHOW TABLES and optimizes every table unconditionally. The input_schema has no properties — it accepts no parameters.

Proposed fix

PHP: Add tables input parameter

'input_schema' => array(
    'type'       => 'object',
    'default'    => array(),
    'properties' => array(
        'tables' => array(
            'type'        => 'array',
            'items'       => array( 'type' => 'string' ),
            'description' => 'Specific table names to optimize. If empty, optimizes all tables.',
        ),
    ),
    'additionalProperties' => false,
),

In the execute callback:

• If tables is provided, validate each name exists, then optimize only those
• If tables is empty/missing, optimize all (current behavior)
• Security: validate table names against actual database tables to prevent SQL injection

JS: Extract table names from user message

The execute function should extract table names from the user message and pass them as the tables parameter. This could be done via:

1. LLM args — the LLM already receives the user message and could populate args.tables if the system prompt describes the parameter
2. JS-side extraction — regex to pull table names (anything matching wp_* patterns)

WooCommerce awareness (#73)

For "optimize the WooCommerce tables", the ability should know which tables belong to WooCommerce. Options:

• Hardcode common WooCommerce table patterns (wp_wc_*, wp_woocommerce_*)
• Or detect dynamically: any table matching {prefix}wc_* or {prefix}woocommerce_*
• Consider HPOS vs non-HPOS table sets (see db-optimize tool should understand "optimize the WooCommerce tables" #73 for the full list)

Example user queries

• "optimize the database table wp_options" → optimize only wp_options
• "optimize wp_posts and wp_postmeta" → optimize those two
• "optimize the WooCommerce tables" → optimize all WC-related tables
• "optimize the database" → optimize all (current behavior, unchanged)

Files to modify

• includes/abilities/db-optimize.php — add tables param, filter logic
• src/extensions/abilities/db-optimize.js — extract table names or rely on LLM args

Refs

Closes #69, closes #73