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>

openspec/changes/agntcy-alignment-docs/.openspec.yaml

@@ -0,0 +1,2 @@
+schema: spec-driven
+created: 2026-03-28

openspec/changes/agntcy-alignment-docs/design.md

@@ -0,0 +1,13 @@
+## Context
+AGNTCY is the Linux Foundation open standard for AI agent identity, interoperability, and governance. AgentIdP implements the non-human identity model defined by AGNTCY. This document makes that alignment explicit and verifiable.
+
+## Goals
+- Engineers and architects can verify AGNTCY compliance without reading the full standard
+- The mapping is explicit: each AGNTCY concept is matched to a specific AgentIdP API feature
+- Both compliant and pending/out-of-scope items are documented honestly
+
+## Folder: docs/agntcy/
+Separate from developers/ and devops/ — this is a standards alignment reference, not a how-to guide.
+
+## Open Questions
+*(none)*

openspec/changes/agntcy-alignment-docs/proposal.md

@@ -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

openspec/changes/agntcy-alignment-docs/specs/alignment/spec.md

@@ -0,0 +1,4 @@
+## ADDED Requirements
+
+### Requirement: AGNTCY alignment docs exist at docs/agntcy/
+The system SHALL provide documentation in `docs/agntcy/` explaining the AGNTCY standard and how AgentIdP implements its non-human identity model, with explicit feature-by-feature mapping.

openspec/changes/agntcy-alignment-docs/tasks.md

@@ -0,0 +1,17 @@
+## 1. docs/agntcy/README.md
+
+- [x] 1.1 Write intro: what AGNTCY is (Linux Foundation, AI agent interoperability standard)
+- [x] 1.2 Write why it matters: standardised agent identity, cross-system interoperability
+- [x] 1.3 Link to alignment.md
+
+## 2. docs/agntcy/alignment.md
+
+- [x] 2.1 Write AGNTCY core concepts section: non-human identity, agent registry, credential management, lifecycle, audit
+- [x] 2.2 Write AgentIdP implementation mapping table: each AGNTCY concept → AgentIdP feature → API endpoint
+- [x] 2.3 Write compliance status section: what is implemented (Phase 1), what is pending (Phase 2+)
+- [x] 2.4 Write interoperability section: how AgentIdP-registered agents can be identified by other AGNTCY-compliant systems
+
+## 3. QA
+
+- [x] 3.1 Verify all API endpoints referenced in the mapping table exist
+- [x] 3.2 Verify compliance status is honest — no overclaiming