WPPilot 1.15.1 — name what blocks MCP, mask emails in change records, read more SEO plugins

• Fixed: with Wordfence active, every MCP call made with an Application Password returned 401 and nothing said why. Wordfence switches Application Passwords off by default (its "Disable WordPress application passwords" setting), and the Connection Doctor, Diagnostics and the Connect screen only said "a plugin or code". They now name Wordfence and the exact setting to uncheck, name any other plugin that switches Application Passwords off by the file its filter lives in, and point to OAuth or an access token, which do not need Application Passwords.
• Fixed: change records showed email addresses in full. wppilot/get-change, wppilot/export-changes, the Changes screen and its download redacted secrets by key name only, so an address typed into an excerpt or a comment came back as written, and get-change returned before-images with no redaction at all. Email addresses in the input, the result, the before-image and the undo verification are now masked when a record is read (j***@e***.com), and before-images get the key-name redaction too. What is stored is unchanged, so undo still restores the exact original.
• Fixed: the content audit and wppilot/read-content only knew Yoast, Rank Math, SEOPress and AIOSEO (read-content not even SEOPress), so on a site using The SEO Framework, Slim SEO or SmartCrawl the audit said no SEO plugin was found and read-content reported no SEO title or description. Their meta is now read, Slim SEO's single settings array included. With WPPilot Pro active the audit reads the active SEO plugins through Pro's own readers, and suggests each plugin's update ability only when it is registered.
• Changed: the Pro upsell names the integrations Pro adds for UpdraftPlus, Duplicator, BackWPup, Wordfence, Solid Security, The SEO Framework, Slim SEO, SmartCrawl, Forminator, WS Form, Kadence Blocks patterns and FunnelKit when one of them is active.
• Kits: kit.json can declare another plugin's storage (vendor_storage) and the kits a kit needs exported with it (requires.kits); the coexistence check honours the first and the exporter the second. No abilities were added or changed, and existing connections keep working.