Wire @keisei/mcp-server publish to the author-operated keigit.com Forgejo npm registry. Verified live: keigit.com → 45.77.41.204 (Vultr, public DNS), Caddy → Forgejo 9.0.3, TLS valid, /api/v1/version=200. Why keigit, not GitHub Packages or npm.org: - keigit IS the canonical npm registry for the @keisei scope (operator runs it; no separate vendor account needed) - npm scope @keisei stays @keisei (no rename to match a github org) - Public DNS resolves from any client; auth via per-user PAT - One auth surface for both the git remote and the npm registry Files changed (7): - _ts_packages/packages/mcp-server/package.json · removed `private: true` (was blocking ALL publish, including ours) · added publishConfig.registry = https://keigit.com/api/packages/keisei/npm/ so accidental `npm publish` cannot route to npm.org · added repository field (provenance link to KeiSeiKit-1.0) · added license: Apache-2.0 - README.md (2 hunks): maturity row + install section say "published to keigit.com", show ~/.npmrc setup - PLUGIN.md (3 hunks): same updates referencing keigit - .claude-plugin/mcp-template.json: _comment updated - docs/encyclopedia/substrate-overview.md (1 hunk): MCP row says "alpha" not "stable" + clarifies registry+scope - .github/workflows/release.yml: npm-publish job rewired: · KEIGIT_TOKEN secret instead of NPM_TOKEN as gate · Two-row .npmrc temp-write: @keisei → keigit.com (always when KEIGIT_TOKEN set), npm.org auth as optional fallback · .npmrc cleanup via `if: always()` step - .gitignore: _ts_packages/.npmrc + .npmrc excluded (RULE 0.8) Verification: - node -e 'require("./.../package.json")' parses clean, publishConfig pinned to keigit, private:false [REAL: ran in session] - `npm run build --workspace=@keisei/mcp-server` → tsc -b exit 0, dist/index.js produced [REAL: built in session] - Server starts: `node dist/index.js` lives >1s, doesn't throw, reports expected `[adapters] not installed` for un-built siblings - keigit.com reachable from this machine: HTTP 200 root + Forgejo 9.0.3 version endpoint [REAL: curl ran in session] Required user-side setup before first publish: 1. Create user/org `keisei` on keigit.com (web UI; currently /keisei → 404) 2. Generate a keigit PAT with write:package scope 3. Add as github repo secret KEIGIT_TOKEN 4. Push tag v0.14.1+ → release workflow's npm-publish job picks it up History note: - Earlier in this session a github-packages-scope-rename variant (commita6f1c72) was pushed; reverted by542a0a8because keigit is the right registry. Current commit lands the keigit wiring on top of the revert. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
68 lines
1 KiB
Text
68 lines
1 KiB
Text
_primitives/_rust/target/
|
|
**/target/
|
|
.DS_Store
|
|
|
|
# Agent worktrees — ephemeral orchestrator scratch dirs, never commit.
|
|
.claude/worktrees/
|
|
**/.claude/worktrees/
|
|
.claude/forks/
|
|
_forks/
|
|
|
|
# kei-spawn agent task-scratch dirs (transient ledger artefacts, RULE 0.12)
|
|
tasks/ag-edit-shared-*/
|
|
|
|
# kei-fork internal markers (should never leak into main)
|
|
.DONE
|
|
.KEI_FORK_META.toml
|
|
_archive/forks/
|
|
|
|
# Secrets
|
|
.env
|
|
.env.*
|
|
!.env.example
|
|
!.env.template
|
|
secrets/
|
|
**/secrets/
|
|
.claude/secrets/
|
|
|
|
# Keys and certs
|
|
*.pem
|
|
*.key
|
|
*.pfx
|
|
*.p12
|
|
*.jks
|
|
id_rsa
|
|
id_rsa.*
|
|
id_ed25519
|
|
id_ed25519.*
|
|
*.gpg
|
|
|
|
# Credentials / config with values
|
|
credentials.json
|
|
.netrc
|
|
.authinfo
|
|
.aws/credentials
|
|
.ssh/
|
|
|
|
# Locks (per-project policy — leave as existing if already tracked)
|
|
# Do not add: Cargo.lock (tracked per RULE 0.1 for reproducibility)
|
|
|
|
# OS + editor junk
|
|
Thumbs.db
|
|
*.swp
|
|
*.swo
|
|
.idea/
|
|
.vscode/
|
|
*.iml
|
|
|
|
# Build
|
|
node_modules/
|
|
dist/
|
|
build/
|
|
__pycache__/
|
|
*.pyc
|
|
var/
|
|
|
|
# RULE 0.8 — auth tokens; CI temp-creates _ts_packages/.npmrc per-job
|
|
_ts_packages/.npmrc
|
|
.npmrc
|