cli.package_unreadable

A file given to jadpo package import isn't there, can't be read, or isn't JSON.

Area 14, Tools; not declinable; the next step is usually the agent's.

Why Jadpo refuses it

jadpo package import openapi <file> turns a provider's OpenAPI document into a package of the app's own, in shared/providers/. It reads the whole document before it writes anything, so a file it can't find or can't read as JSON writes nothing: half a package would check against an API the provider doesn't have.

It reads JSON only for now. A YAML document is refused rather than guessed at.

What it looks like

A project importing Tidepool's API from the YAML its documentation links:

cat > tidepool.yaml <<'DOC'openapi: 3.1.0info:  title: Tidepool  version: "1"paths: {}DOCjadpo package import openapi tidepool.yaml

(agent) at the end of the next: line means your coding agent can make the fix itself.

A path with no file at it is refused too:

jadpo package import openapi tidepool.json

How to fix it

If the provider publishes JSON too, download that document and import it:

jadpo package import openapi tidepool.json

The package is written in shared/providers/tidepool/v1/, and the screen lists its operations and types.

If it publishes only YAML, convert the document to JSON with a YAML tool, then import the JSON:

yq -o=json tidepool.yaml > tidepool.jsonjadpo package import openapi tidepool.json

The import reads the JSON as it would the provider's own.

Related

• jadpo package import
• Commands for packages