oasf_not_exportable

GET /v1/agents/{agentpeer_id}/oasf.json answers 409 oasf_not_exportable

Symptom: the OASF export of an otherwise-public card fails with 409 oasf_not_exportable.

Cause: none of the card's declared capabilities are in the reviewed AgentPeer-capability → OASF-skill mapping (packages/contracts/oasf/capability_skill_map.json), or the card declares no capabilities at all. OASF's record object requires a non-empty skills list; rather than submit a padded or empty list, or guess a nearest-sounding skill, the export refuses. This is deliberate, not a bug: fabricating a skill would misrepresent what the card actually declares.

Fix: publish the card with at least one capability that has a reviewed mapping (see the mapped list in capability_skill_map.json), or treat the card as not yet OASF-exportable. This is a card-content limitation, not something the caller of the export route can work around.