P2 — Hermes-ready: typed tool-manifest per engine + documented artifact ABI

[gnanirahulnutakki]

Part of the content-flow redesign — see design doc ardur-pipeline/docs/redesign-content-flow-2026-06.md (#14).

P2 — Hermes-ready: typed tool-manifest per engine + documented artifact ABI

Each engine is already a pure JSON-in/JSON-out CLI. Make that machine-discoverable for a Hermes agent (design doc §9).

Scope

• Add tool-manifest.json to each engine repo: { name, description, inputSchema, outputSchema, cli } where schemas reference @ardurai/contracts (generate from the Zod schemas).
• Document the published artifact ABI (manifest.json + latest/*.json, schema-versioned) as the Hermes hand-off contract in docs/.
• Confirm orchestration parity: a Hermes agent can call the same CLIs (or an MCP shim) in order with the same assertCompatibleArtifact gate; engines hold no session state and are idempotent per cycle.id.

Acceptance

• A manifest exists per engine and validates against its actual CLI I/O.
• The artifact ABI doc lets an external orchestrator consume a cycle without reading engine source.

Depends on: C1.