Visual overview
Use the workflow to follow the task, and the architecture map to separate responsibilities. These are conceptual maps; the guide below defines implementation details and verification limits.
- Align namespace and version
- Publish tested npm artifact
- Authenticate namespace ownership
- Publish and verify record
- Boundary 1Package metadata
- Boundary 2Registry publication
- Boundary 3Public registry record
Connected responsibilities, not a required class hierarchy or an execution trace.
The namespace is io.github.Nagarjuna2997/ios-agent-skill. mcp-server/package.json carries the matching mcpName; mcp-server/server.json declares the npm artifact and stdio transport. The existing version-sync script keeps package and registry versions aligned.
The official publication flow requires the matching npm version to be public before registry submission, plus authentication proving control of the namespace. Metadata alone does not publish a listing.
From mcp-server, after package checks and npm publication:
node scripts/sync-version.mjs --check
mcp-publisher login github
mcp-publisher publish
Keep authentication files outside the repository. Verify the returned registry record and version before claiming acceptance. Downstream directories have their own ingestion schedule; a successful registry publication does not establish a PulseMCP listing.