faf 7.14.0 → 7.15.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (12) hide show
  1. package/README.md +7 -7
  2. package/dist/cli.js +246 -246
  3. package/dist/cli.js.map +6 -5
  4. package/dist/index.d.ts +2 -0
  5. package/dist/index.js +145 -145
  6. package/dist/index.js.map +6 -5
  7. package/dist/interop/cards.d.ts +5 -77
  8. package/dist/interop/pack.d.ts +204 -0
  9. package/dist/pack.js +61 -0
  10. package/dist/pack.js.map +59 -0
  11. package/package.json +6 -2
  12. package/project.faf +3 -3
package/README.md CHANGED
@@ -132,18 +132,18 @@ faf memory etch "a durable fact" --id my-fact
132
132
  faf memory show
133
133
  ```
134
134
 
135
- ### What's New in v7.14.0 — The Passport Edition
135
+ ### What's New in v7.15.0 — The Pack Edition
136
136
 
137
- **The A2A Agent Card's FAF extension carries real agent identity now — an `agentId`, a `passport` URL, and the full FAF media-type family — not just project provenance.**
137
+ **Answer a few questions about an agent or MCP server and get every card it needs. faf-cli writes the `.fafa` from the answers and projects it onto the A2A Agent Card, the MCP Server Card, the MCP Registry `server.json`, an AI Catalog and an ARD manifest, in Node or in a browser.**
138
138
 
139
- - **The extension moved to `https://faf.one/ext/context/v1`** and its `params` gained `fafaSpecVersion`, `agentId` (from `.fafa` `agent.id`), the full `mediaTypes` family, and a `passport` URL — nested `provenance.faf`/`provenance.mediaType` replace the old flat pointer fields.
140
- - **`defaultInputModes` reflects what your skills actually cite.** Any FAF media type a capability's `cites_spec` names now shows up there, and on that skill's own `inputModes`.
141
- - **`provider` is optional again.** It's emitted only when both `agent.vendor` and `agent.homepage` are present — no longer a hard requirement.
142
- - **`capabilities.streaming` stays honest at `false`.** Having an A2A endpoint was never proof it supports streaming; this only flips once a real per-door signal exists to key off.
143
- - Breaking for anything reading the old flat A2A extension shape or the old `https://faf.one/context` URI. MCP Server Cards and registry entries are unaffected.
139
+ - **The card pack.** `answersToFafa` writes a `.fafa` from a few answers: name, short name, domain, description, version, endpoints and skills. `buildPack` / `projectPack` project it onto the A2A Agent Card, the MCP Server Card, the registry `server.json`, an AI Catalog and an ARD manifest. Facts only some cards carry (repository, icon, keywords, example requests, packages) live in the `.fafa` under `metadata.cards`, so the file stays the one source.
140
+ - **Neutral by default.** A pack card carries no extension and no FAF media type unless the caller passes one. The `.fafa` joins the catalog only with `listFafa`.
141
+ - **`faf-cli/pack`**: the pack as one browser module (`dist/pack.js`, no Node built-ins, types included). In Node, `import { buildPack } from 'faf-cli'` works too.
142
+ - The A2A card core moved into the pack as `projectA2ACard`. `buildA2ACard` and `faf cards` keep their signature and output: FAF's own A2A card is unchanged.
144
143
 
145
144
  **Recent sprint**
146
145
 
146
+ - 🎴 [7.15.0](https://github.com/Wolfe-Jam/faf-cli/releases/tag/v7.15.0) The Pack Edition
147
147
  - 🛂 [7.14.0](https://github.com/Wolfe-Jam/faf-cli/releases/tag/v7.14.0) The Passport Edition
148
148
  - 🛡️ [7.13.1](https://github.com/Wolfe-Jam/faf-cli/releases/tag/v7.13.1) security: detection reads stay inside the project
149
149
  - 🤝 [7.13.0](https://github.com/Wolfe-Jam/faf-cli/releases/tag/v7.13.0) The Co-Author Edition