Corsen Context

1.5.16 – 2026-09-03

• Agent conduct policy states what an agent may do, not only what it must not: for a product whose agentPurchase is allowed, an agent acting for its user may complete the store’s ordinary checkout, including creating the customer account it requires; everything outside those explicit per-product permissions stays human-only, and the agent is told to stop and report the page URL to its user. The same sentence is rendered in llms.txt, the [corsen_agent_policy] page, the machine-readable policy JSON, the get_product description, and the default per-product reason.

1.5.15 – 2026-09-03

• “Hide user enumeration” now flips anonymous author archives to 404 on pre_handle_404, inside WP::main() and before the wp action, instead of on template_redirect. The previous hook returned the right status but SEO plugins and wp_get_document_title() had already resolved the author, so the 404 page’s <title> and Open Graph tags still printed the author’s nicename and archive URL. The queried user is also dropped from the main query, and the integration test now asserts the document title, is_author(), and the queried object.

1.5.14 – 2026-09-02

• get_structured_data now uses WordPress’s safe HTTP transport, refuses redirects, and caps the loopback response while downloading it. Stored markup is capped before parsing, JSON-LD clips stay valid UTF-8, multi-type entities are counted correctly, duplicate blocks no longer create a false truncation flag, and every returned block now stays within the documented byte budget.
• WordPress Abilities output schemas now match the executor: search_site declares rank, sitemap fields reflect its actual payload, nullable product values are explicit, and the section and structured-data schemas include their real optional fields.
• All WordPress extension readers now honor the same membership and visibility veto filter as the four core tools. Section ids reserve the synthetic top entry and ignore heading-like lines inside fenced code. The expert handoff requires an owner-configured same-origin form URL, and uninstall/purge removes the complete private expert inbox (including trashed requests), agent-access snapshot, lock, and product policy metadata.
• Extension input schemas now match their validators (required URIs, exact slug-or-URI product selection, and bounded section offsets), including Unicode-aware string limits. The agent-access check validates real llms.txt/MCP response shapes and is described honestly as a same-site loopback using representative bot User-Agent strings, not a full external-agent test.
• Product purchase policy can be managed on every WooCommerce product edit screen as well as the first 50-product quick editor. Invalid stored states fail closed, policy summaries honor every owner visibility veto, and human-handoff copy no longer claims that Corsen Context intercepts browser form submissions.

1.5.13 – 2026-09-01

• Policy honesty + hardening (second independent review): the REST meta auth_callback no longer calls edit_post_meta (which re-entered itself for registered protected meta) and checks edit_post instead, as Core documents. The agent head banner renders only when the MCP channel is actually enabled — a disabled channel is never advertised. Long owner reasons are truncated without requiring mbstring. llms.txt opens with “START HERE for AI agents” and its policy block now distinguishes the server-enforced expert handoff (human_only) from the per-product agentPurchase contract instruction; the plugin exposes no purchase tool and never intercepts human checkout. The human-only form notice is generated from the same table ([corsen_human_only_notice]), so the form copy is the wire copy.

1.5.12 – 2026-09-01

• Governed-agent policy: one server-side policy table composes the relevant MCP/WebMCP descriptions, llms.txt, an HTML head banner for parsers, and the [corsen_agent_policy] page. request_expert_call becomes human-only by policy: it stays advertised so an agent can read the rule, but every schema-valid invocation is refused with error code human_only plus a handoff URL before any throttle or storage side effect. get_product output carries agentPurchase (allowed|forbidden) and agentPurchaseReason from owner-set product meta, and the tool description states that a forbidden product must be handed to a human, never checked out by the agent. OPTIONS preflight matching also tolerates rest_route and atypical permalink prefixes.

1.5.11 – 2026-09-01

• tools/list now emits WebMCP annotations (readOnlyHint per tool; request_expert_call is explicitly readOnlyHint: false) on the MCP transport, so SECURITY.md’s claim is backed on the wire and not only in the in-page bridge. get_sections documents "top" and now always lists and resolves it, even as a zero-byte intro. When “Hide user enumeration” is on, /?author=N and /author/{login} archives also answer 404 to anonymous visitors instead of leaking logins through the classic doors. The MCP route’s OPTIONS preflight is answered by the plugin (POST, OPTIONS, no credentials) instead of core advertising every verb.