feat: Phase 1 P1 — Dockerfile, AGNTCY alignment docs, Node.js SDK
Three remaining Phase 1 P1 deliverables: 1. Dockerfile — multi-stage build (builder + production), node:18-alpine, non-root USER node, .dockerignore excluding secrets and dev artifacts 2. AGNTCY alignment docs (docs/agntcy/) — README and alignment.md mapping all 6 AGNTCY domains to AgentIdP features with Phase 2/3 pending items noted 3. Node.js SDK (@sentryagent/idp-sdk) — TypeScript strict, zero any, native fetch (Node 18+), TokenManager with 60s auto-refresh, service clients for all 14 endpoints (agents, credentials, tokens, audit), AgentIdPError typed error hierarchy, full README All three changes tracked under openspec/changes/ with tasks marked complete. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
11
openspec/changes/agntcy-alignment-docs/proposal.md
Normal file
11
openspec/changes/agntcy-alignment-docs/proposal.md
Normal file
@@ -0,0 +1,11 @@
|
||||
## Why
|
||||
AGNTCY alignment documentation is a Phase 1 P1 deliverable. SentryAgent.ai positions itself as AGNTCY-compliant, but there is no document explaining what AGNTCY is, how AgentIdP maps to its model, and what that means for developers and operators adopting the platform.
|
||||
|
||||
## What Changes
|
||||
- New `docs/agntcy/` folder
|
||||
- `alignment.md` — formal mapping of AgentIdP concepts to AGNTCY standard concepts
|
||||
- `README.md` — entry point explaining what AGNTCY is and why it matters
|
||||
|
||||
## What Does Not Change
|
||||
- No source code changes
|
||||
- No API changes
|
||||
Reference in New Issue
Block a user