v0.4.0

Makes DocSift usable from Copilot Studio, Power Automate and n8n.

docsift openapi --format swagger2 -o docsift-connector.json

Swagger 2.0 export. Power Platform custom connectors do not accept the OpenAPI 3.1 document the service serves at /openapi.json. This command emits the Swagger 2.0 they need, with host and scheme taken from DOCSIFT_PUBLIC_URL.

Optional API key. Set DOCSIFT_API_KEY and every route except /health, /version, /openapi.json, /docs and /redoc requires an X-API-Key header. Off by default — a deployment that sets nothing behaves as before. This is one shared secret, not per-user identity.

Agent-oriented API descriptions. Every operation now carries a summary and a description written for tool selection, including when to prefer search over retrieving a whole document.

Examples. examples/n8n/ has an importable workflow (upload → poll → search) with failure and timeout branches; examples/copilot-studio/ covers connector setup; examples/power-automate/ documents the Do until flow that waits for conversion.

A Copilot Studio action cannot poll. Search works as a direct connector call. Uploading needs a Power Automate flow, because an action calls a connector once and conversion can take minutes. The guides explain the split rather than pretending one action can wait.

Upgrading from 0.3.0. No behaviour change unless you set the new variables. The OpenAPI document now advertises a servers entry only when DOCSIFT_PUBLIC_URL is set, so existing clients are unaffected.

Known limitations. No per-user identity, rate limiting or multi-tenancy. The bundled Dockerfile is still not build-tested. The connector file has been validated against the Swagger 2.0 schema but not yet imported into a live Power Platform tenant.