feat(core): authoritative agents.manifest.json + optional contract description#112
Merged
Conversation
…t description OTAIP had four overlapping notions of "which agents exist" (discovery, count-agents, docs/agents.md, the contract registry). This adds one generated source of truth. - scripts/generate-manifest.ts (`pnpm gen:manifest`) writes committed agents.manifest.json: every discovered agent with has_contract first-class, plus action_type + input/output JSON Schema (via the same zodToJsonSchema the tool catalog uses) for the 18 contracted agents. `--check` mode fails if the committed file is stale; wired into CI. - Add optional `description` to AgentContract; the catalog/describe_agent generator uses it (falling back to the previous string). Authors fill it as agents graduate — no bulk, domain-inventing schema generation. This is the OTAIP-honest answer to "one schema for every agent": the two-tier model is made queryable rather than papered over. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Field feedback flagged two related things: overlapping/ambiguous notions of "which agents exist", and wanting one machine-readable schema per agent. OTAIP's honest version: make the two-tier model first-class and queryable rather than mechanically forcing loose, domain-inventing contracts onto ~60 stub agents.
What
scripts/generate-manifest.ts(pnpm gen:manifest) → committedagents.manifest.json: all 75 agents withid/name/stage/version/contract_status/has_contract/source_path, plusaction_type+ input/output JSON Schema (samezodToJsonSchemaas the tool catalog) for the 18 contracted agents.--checkmode fails if the committed file is stale — wired into CI after build.descriptiontoAgentContract; the catalog/describe_agentgenerator uses it, falling back to the priorOTAIP agent <id> (<actionType>)string. Authors fill descriptions as agents graduate — no bulk schema generation that would invent domain behavior (per CLAUDE.md).Deliberately NOT done
count-agents.tsat the manifest: both already derive from the samediscoverAgents()root, so they can't drift on the roster, and repointing would costcount-agentsits build-free property. The freshness check covers the manifest.docs/agents.mdauto-generation is left as a follow-up.🤖 Generated with Claude Code