WIQD validator rejects documented v1.8 conversation starter depends_on property

Observed with WIQD 0.12.2 on Windows.

Problem

WIQD static validation rejects conversation_starters[].depends_on, even though the property is
present in the published declarative-agent v1.8 JSON Schema and documented on the Microsoft Learn
v1.8 manifest page.

Published sources:

• Schema: https://developer.microsoft.com/json-schemas/copilot/declarative-agent/v1.8/schema.json
• Documentation: https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/declarative-agent-manifest-1.8

Steps to reproduce

1. Create a declarative-agent manifest using schema/version v1.8.

2. Add depends_on to a conversation starter following the published schema and documentation.

3. Run:

   wiqd agent validate --mode static --env local
   

Actual behavior

Validation exits with code 1 and reports the property as an error:

Unrecognized member 'depends_on'
Severity: Error

In the observed project, six starters containing the property produced six identical errors.
Removing only depends_on cleared the diagnostics; the remaining v1.8 manifest then passed static
validation.

Expected behavior

The WIQD validator should accept properties supported by the current published v1.8 schema. If the
property is intentionally unsupported by the target Microsoft 365 service, WIQD should explain the
compatibility limitation explicitly rather than reporting a documented schema member as
unrecognized.

Impact and workaround

Authoring strictly against the published v1.8 schema is not sufficient to pass WIQD validation.
The current workaround is to remove depends_on, losing the optional capability linkage on the
conversation starter.

Environment

Start by reproducing the failure with the documented v1.8 manifest and wiqd agent validate --mode static --env local. Trace the static validator's v1.8 schema handling and compare its accepted conversation-starter properties with the published schema. Done means depends_on is accepted, or the validator reports an explicit compatibility limitation instead of an unrecognized-member error.