v0.1.1 — bug-fix bundle

v0.1.1 — bug-fix bundle (2026-05-24)

Four bug fixes surfaced during post-merge smoke testing of v0.1.0 and an external LLM review of the live /llms.txt output. No new features, no schema changes, no data migration. Drop-in upgrade.

Fixes

• /llms.txt regen now fires reliably after Context Profile saves on low-traffic sites. Previously, Service::schedule_regen() could leave a stale past-timestamp event sitting in the cron queue (common on wp-env without traffic), and subsequent saves silently failed to re-schedule because wp_schedule_single_event de-duped against the stale entry. Now the scheduler splits the coalesce check: future event → noop (debounce intact); past event → clear and re-schedule. (#103 · PR #107)

• Schema_Emitter now emits per-content JSON-LD for custom CPTs. v0.1.0 only emitted Article on post and WebPage on page; custom CPTs like lesson, product, recipe got only the site-identity nodes. v0.1.1 defaults: post → Article, page and every other CPT → WebPage (the safe semantic generic). New filter agentready_schema_type_for_cpt($default, $cpt, $post_id) lets plugin/theme authors specialize (e.g. flip lesson → Article for blog-shaped CPTs, or return null to suppress per-content emit). v0.1.2 will add dedicated builders for Recipe / Course / Product / Event / Person. Design captured in AgDR-0040. (#104 · PR #108)

• /llms.txt entry links now point at the .md form when Markdown Views is enabled. v0.1.0's /llms.txt linked at canonical HTML — agents fetched 50–100 KB per page including header, nav, footer. v0.1.1 transforms pretty permalinks (/lessons/foo/) to <slug>.md (~4–8 KB clean Markdown). Plain permalinks (/?p=42) fall through to ?format=md so the same Handler serves them. When markdown_views_enabled is false, the canonical permalink is preserved (because the .md URL would 404). (#105 · PR #109)

• HTML entities no longer leak into the plain-text /llms.txt body. WordPress's wptexturize filter and the block editor HTML-encode typographic characters (Architect's → Architect’s). v0.1.0 served those entity codes literally to the consumer because /llms.txt is text/plain, not HTML. v0.1.1's composer decodes entities at the bottom of the escape pipeline so every text surface (site name, tagline, section label, entry title, description) is clean. (#106 · PR #110)

Upgrade

• wp.org Plugin Directory: v0.1.0 is currently in review. v0.1.1 will be staged to SVN once v0.1.0 is approved by the reviewer — there's nothing to do on your end through the directory yet.
• GitHub release ZIP (this page): drop the attached ai-readiness-kit-0.1.1.zip into wp-content/plugins/, replacing your existing ai-readiness-kit/ folder. Then activate. WordPress handles the rest — no migration step required (the bug fixes preserve every option key, hook name, custom table, and capability slug from v0.1.0).

Compatibility

• WordPress 6.9+ (tested up to 7.0)
• PHP 7.4+

What's next (v0.1.2)

• Dedicated node builders for the common schema.org types (Recipe, Course, Product, Event, Person) so the agentready_schema_type_for_cpt filter can honor any return value.
• Polish items surfaced during Rex reviews: a static-front-page regression test, the same wp_next_scheduled pattern check in Context_Score's Service.php, parameterised plain+pretty permalink tests, and minor docblock fills.

Verifying this release

After upgrading, run:

wp ai-readiness-kit llms-txt regen
wp ai-readiness-kit context-score recompute

…and confirm /llms.txt reflects your current Context Profile, with .md-suffixed entry links and no entity codes. On a site with custom CPTs, view source on a singular custom-CPT URL and confirm a WebPage (or Article if you wired the filter) JSON-LD node now appears alongside the site-identity nodes.