feat: add SHA256 content hashing to agent registry #14
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.
Summary
Add
contentHash(SHA256) to agent versions to supportagent.lock.jsonon the CLI side.Changes
Shared Types (
packages/shared/src/types/agent.types.ts)latestContentHashtoAgentDocumentinterfacecontentHashtoAgentVersionDocumentinterfacelatestContentHashtoAgentDetailUiResponseinterfacecontentHashtoAgentVersionUiResponseand versions array inAgentDetailUiResponseCollection Schemas
latestContentHashto agents collection schemacontentHashto agent_versions collection schemaAgent Service (
packages/backend/src/services/agent.service.ts)computeContentHashhelper function using Node.jscryptomoduleResponse Mappers (
packages/backend/src/utils/agent-response.mapper.ts)latestContentHashinmapAgentToDetailResponsecontentHashinmapAgentVersionToResponseRoute Handlers
POST /api/agents: ReturncontentHashin publish responseGET /api/agents/:owner/:name: ReturnlatestContentHashand includecontentHashin versions arrayAPI Changes
POST
/api/agents(Publish){ "success": true, "agent": { "name": "my-agent", "owner": "username", "version": "2025-12-01", "contentHash": "a1b2c3d4e5f6789...", "visibility": "public", "publishedAt": "2025-12-01T12:00:00Z" } }GET
/api/agents/:owner/:name{ "success": true, "data": { "latestContentHash": "a1b2c3d4e5f6789...", "versions": [ { "version": "2025-12-01", "contentHash": "a1b2c3d4e5f6789...", "isLatest": true } ] } }Benefits
Migration Notes
Existing agents/versions won't have
contentHash. A migration script can be run to backfill existing documents. The CLI should handle missing hashes gracefully.Related
specs/update-publish-endpoints.md