benbalter/wordpress-static-site-exporter

The performance-monitoring example in docs/examples/optimization-examples.php:95-112 hooks jekyll_export_complete, but the plugin never fires that action. The only one it fires is jekyll_export, at the start (jekyll-exporter.php:715). Anyone who copies the example never gets the log line and is left with a stray option in wp_options. Pointer: fire it right after $this->cleanup() in export() (L727). That runs on both the browser-download path and the WP-CLI path. On the download path the zip has already been sent, so wrap the call in ob_start() / ob_end_clean() the way the jekyll_export call is wrapped (L714-721). Fire it inside the try block so a failed export never reaches it. Acceptance criteria: the action fires once after a successful export on both paths and doesn't fire when the export fails. A test covers it, the docs list the hook, and readme.txt is regenerated if docs/ changes.

Several per-post filters receive only the value being filtered, not the post it came from, so you can't customize output per post. The affected filters are: jekyll_export_meta (jekyll-exporter.php:280) jekyll_export_terms (L318) jekyll_export_markdown and jekyll_export_content (L495-496) jekyll_export_html and jekyll_export_content in html_fallback() (L506-509) Only jekyll_export_post_meta passes $post today (L532). Adding $post as a second argument is backward compatible: WordPress only passes it to callbacks registered with accepted_args of 2 or more. Acceptance criteria: each filter above receives $post as its second argument, and html_fallback() takes $post from its caller. PHPUnit tests show that a two-argument callback gets the right post. docs/custom-fields.md:9 is updated, and readme.txt is regenerated with script/build-readme.