Q, the AI assistant in the portal

A chat window in the bottom-right corner, shown on Home when chat is enabled.
New "AI Assistant" tab in Settings. All settings are in one property, x_gass2_intghub.q.settings. The customer token is in x_gass2_intghub.q.customer_token.
Q shows the remaining quota without spending a question. The free version allows 5 questions per day per IP.
Attachments need a customer token: up to 5 files and 6 MB in total. Without a token you can still attach, but you get an error message straight away.

Other new features

All durations are shown in readable units (ms, s, min, h, d, w) instead of large second or ms counts. This covers queue records, dashboards, Live executions, Explorer, Live Map and Queue Analytics.
Find callers now lives in one new script include, ApiUsageFinder. The button is hidden when the IntegronQ utility is not enabled.
Request preview tells you when the transform script returns the wrong thing, for example nothing, a string or an exception.
On a timeout or connection failure (status 0), the actual cause is shown, for example DNS or SSL. Credentials and the query string are removed from the text. This applies to outbound calls and Test connection.
Error Intelligence has a new failure category, "Field value has the wrong type", and more reliable grouping of failures (FailureInsightsAnalyzer).
Related-record suggestions understand table hierarchies, for example a reference to task when the parent is incident.

Text

The help text for HTTP method said PATCH is outbound only.
The choice mapping hint said "sends", which was wrong on GET.
The import list shows the actual reason instead of "Upsert failed.".
Action function errors show the thrown error instead of "failed. undefined".
Long URLs in Request preview now wrap instead of being cut off.
Settings shows a message when the settings can't be loaded, instead of throwing a ReferenceError.

Table API proxy

POST returns 201 with a Location header. PUT and PATCH return 200.
The table check no longer needs read access to sys_db_object. Before, ordinary callers got "Table does not exist" for valid tables.
Field and query ACLs are now enforced:
- Fields the caller can't read are left out.
- Writing to a protected field returns 403.
- X-Total-Count is counted with ACLs applied.
Only active inbound configurations are used as a proxy.
New support for name-value filters (?active=true), dot-walking in sysparm_fields, links on reference fields and sysparm_query_category.

Table API behaviour changes (call these out in the notes)

DELETE returns 204 with no body. Before, it returned 200 with {sys_id, deleted}.
Pagination uses the Link and X-Total-Count headers. X-Offset, X-Limit, X-Has-More, the meta object in the body and sysparm_count are gone.
The default limit is 10000 records. Before, it was 100, with a cap of 5000.
Unknown sysparm_ parameters return 400. This includes sysparm_view and sysparm_choice.
System fields in the request body return 400 instead of being silently ignored. A {result:{...}} wrapper is no longer unwrapped.

Outbound

GET and HEAD never send a body. DELETE sends a body only when the payload is not empty.
depends_on now links to the latest send for the record, not to any send. An old failure can no longer cause a 424.
A synchronous on-demand call could send twice. The fix needs the run_on_demand column on the data queue, listed below.

Editor, import and publishing

An API can't be activated if the form has unpublished changes, or if the published configuration is missing required values, such as the Request URL. This applies in both the editor and Explorer.
$payload works with or without quotes. The runtime, the editor and import all follow the same rule.
POST with "Use value from record" is now blocked on save, import and publish. Before, it gave a 400 on every create.
Post-scripts on an inbound Run Action are skipped with a warning. The editor clears them and import rejects them.
When an import updates an existing API, the change goes through a draft and review. It goes live only after approval.
Import checks that the referenced Script Includes and their functions exist, including those used for attachments.
Export includes the integration key of each referenced API, and import matches on that key.
Publishing runs the CSDM step before the API is saved. If it fails, nothing goes live, so the live configuration and the version history can't drift apart.
Failed CSDM relationships and associations are now reported. Before, they were reported as successful.
If v1 can't be saved when an API is created, the new API is rolled back.
If retiring older versions or pointing the API at the new version fails, it's reported instead of being hidden.
Saving an inactive API used to delete its related-record rules. That's fixed, and failures to save the rules are now reported.