px_agentic_trust_enabled and px_agentic_trust_mcp_endpoint_path configurationspx_snippet_injection_enabled and px_create_custom_snippet configurationspx_proxy_url configurationpx_data_enrichment_header_name configurationpx_async_timeout configurationpx_await_async_http_requests configurationpx_enrich_response_custom_parameters"/^\/path$/i") in route and user-agent filter configurations (px_sensitive_routes, px_monitored_routes, px_enforced_routes, px_graphql_routes, px_filter_by_route, px_filter_by_user_agent, px_graphql_keywords, px_sensitive_graphql_operation_names)px_filter_by_user_agentorig_cookie_vid field added to all Enforcer activitiesis_sensitive_route field added to risk API and async activitiespx_enrich_response_custom_parameters)perimeterx-js-core to v0.37.1update_reason field now reflects the reason for telemetry (command or risk) and includes a request_id fieldpx_graphql_keywords) and custom function (px_extract_graphql_keywords)px_bypass_monitor_header changed from empty string to “x-px-block”px_sensitive_graphql_operation_names expanded to include regular expressions and applies to extracted GraphQL keywords as well_pxvid value was added to the captcha pagetest() due to global flagBodyLoginSuccessfulParser bug by implementing text() method in OutgoingResponse\\/ with / in the telemetry regex fields valuerisk_start_time and enforcer_start_time fields to enforcer activitiespx_filter_by_route, px_monitored_routes, px_enforced_routes, px_sensitive_routes, px_graphql_routes configs to be Array<string | RegExp>cookie headerx-px-cookies