Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/rest-typings/src/v1/subscriptionsEndpoints.ts">

<violation number="1" location="packages/rest-typings/src/v1/subscriptionsEndpoints.ts:107">
P1: Use the body Ajv instance here. `ajvQuery` enables type coercion for query strings, so this POST validator will start accepting numeric `roomId`/`_id` values by coercing them to strings.</violation>
</file>

<file name="packages/rest-typings/src/v1/chat.ts">

<violation number="1" location="packages/rest-typings/src/v1/chat.ts:3">
P2: This migration leaves three paginated GET validators on `ajv`, so `count`/`offset` query strings will now fail validation for those chat endpoints.</violation>
</file>

<file name="apps/meteor/app/authorization/server/functions/upsertPermissions.ts">

<violation number="1" location="apps/meteor/app/authorization/server/functions/upsertPermissions.ts:57">
P2: Omitting `group` here does not clear existing `group: null` / `section: null` values from stored permissions, so the intended normalization will be skipped.</violation>
</file>

<file name="packages/core-typings/src/ISetting.ts">

<violation number="1" location="packages/core-typings/src/ISetting.ts:56">
P2: Widen `section` as well; the new TODO says legacy settings can still contain `section: null`, so leaving it as `string` keeps this shared type unsound.</violation>
</file>

<file name="packages/rest-typings/src/v1/omnichannel.ts">

<violation number="1" location="packages/rest-typings/src/v1/omnichannel.ts:2353">
P2: This is a response schema, so switching it to `ajvQuery` weakens the contract by coercing mistyped output instead of failing validation.</violation>

<violation number="2" location="packages/rest-typings/src/v1/omnichannel.ts:2793">
P2: This POST body validator should keep `ajv`, not `ajvQuery`; using the query validator here will coerce invalid body fields instead of rejecting them.</violation>
</file>

<file name="apps/meteor/app/livechat/server/api/v1/integration.ts">

<violation number="1" location="apps/meteor/app/livechat/server/api/v1/integration.ts:31">
P2: This coercion runs too late to help clients affected by `coerceTypes: false`; schema validation will reject mistyped payloads before the handler executes.</violation>

<violation number="2" location="apps/meteor/app/livechat/server/api/v1/integration.ts:39">
P1: `null` timeout payloads now get stored as `undefined`, which breaks webhook retry timing and timeout handling downstream.</violation>
</file>

<file name="packages/rest-typings/src/v1/Ajv.ts">

<violation number="1" location="packages/rest-typings/src/v1/Ajv.ts:28">
P2: The format/keyword registrations are fully duplicated between `ajv` and `ajvQuery`. Extract the shared setup into a helper to avoid silent divergence when future formats or keywords are added to only one instance.

```ts
function configureAjv(instance: Ajv) {
  addFormats(instance);
  instance.addFormat('basic_email', /^[^@]+@[^@]+$/);
  instance.addFormat(
    'rfc_email',
    /^[a-zA-Z0-9.!#$%&'*+\/=?^_`{|}~-]+@[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?(?:\.[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?)*$/,
  );
  instance.addKeyword({
    keyword: 'isNotEmpty',
    type: 'string',
    validate: (_schema: unknown, data: unknown): boolean => typeof data === 'string' && !!data.trim(),
  });
}
configureAjv(ajv);
configureAjv(ajvQuery);
```</violation>
</file>

<file name="apps/meteor/client/views/banners/UiKitBanner.tsx">

<violation number="1" location="apps/meteor/client/views/banners/UiKitBanner.tsx:56">
P2: This drops the entire banner for valid `TextObject` titles. `BannerView.title` explicitly allows `string | TextObject`, so apps sending structured titles will now lose the whole banner instead of just falling back on title rendering.</violation>
</file>

<file name="apps/meteor/server/services/calendar/service.ts">

<violation number="1" location="apps/meteor/server/services/calendar/service.ts:180">
P2: This makes it impossible to reliably clear an existing `meetingUrl`, because explicit clearing values are collapsed to `undefined` before the update payload is built.</violation>
</file>

<file name="packages/rest-typings/src/v1/misc.ts">

<violation number="1" location="packages/rest-typings/src/v1/misc.ts:98">
P2: `isDirectoryProps` is compiled against a type that incorrectly requires optional query fields.</violation>
</file>

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="apps/meteor/app/livechat/server/api/v1/integration.ts">

<violation number="1" location="apps/meteor/app/livechat/server/api/v1/integration.ts:39">
P2: This truthiness check drops a valid timeout of `0`; use a null/undefined check so provided zero values are still saved.</violation>
</file>

<file name="packages/rest-typings/src/v1/omnichannel.ts">

<violation number="1" location="packages/rest-typings/src/v1/omnichannel.ts:3955">
P2: The new `| undefined` fields no longer match the Ajv schema, which still allows omitted and `null` values. That makes `isPOSTomnichannelIntegrations` narrow some valid payloads to the wrong TypeScript shape.</violation>
</file>