Interface HonuaOgcProcessesOptions

Raw endpoint path prefix (defaults to the Honua facade /ogc/processes).

How hard to gate on server declarations.

• "advertised" (default) — gate on declarations already in hand (conformance, a describe()/list() already performed on this handle, or an explicit jobControlOptions), and fall back to the Core-mandated route templates when a server advertises no link. No extra requests. What was read counts, including silence: a description this handle has seen that carries no jobControlOptions advertises no execution mode, and an explicit mode against it is refused. Only a process this handle has never read is treated as unknown rather than undeclared. Sources are ranked, not merged: a full description outranks a listing summary, so a later list() never downgrades what describe() established.
• "strict" — resolve the conformance declaration and the process description first (both through the metadata cache) and refuse anything the server has not declared, including a /conformance document that declares no Core class, a description that declares no execution mode, a cancel() nothing declared as dismiss, and a job lifecycle whose status and results routes are not advertised as links.

The server's advertised conformance classes. Supply the discoverOgcProcesses() result (or a /conformance response) to gate execution and dismissal against what the server actually declares. Omitted under the default policy, nothing is gated on conformance.

Default polling budget applied to results() on jobs created by this handle. Per-call JobResultsOptions win field by field.