v1.2.3

v1.2.3 — npm publish fix (correct username)

The 1.2.2 attempt chose @maxisoft-git/instantcms-mcp. That scope does not exist in the npm registry (404 Scope not found).

Verified via npm whoami: the maintainer's npm account is maxisoft (not maxisoft-git), and the matching scope that already has publish rights via the existing repository NPM_TOKEN (March 2026) is @maxisoft — there's already an @maxisoft/figma-mcp-bridge published to it.

This release renames the package and bumps the version:

Aspect	v1.2.2	v1.2.3
package.json name	@maxisoft-git/instantcms-mcp	@maxisoft/instantcms-mcp
version	1.2.2	1.2.3
Code / tests	—	unchanged (1.2.1 test-harness expansion applies verbatim)
GitHub Release ZIP	✅	✅
npm install (after token rotation)	—	✅

Install — works today (no token rotation needed for this part)

# GitHub Release ZIP — pinned to v1.2.3 artifact
curl -L -O https://github.com/instantcms-dev/instantcms-mcp/releases/download/v1.2.3/instantcms-mcp-v1.2.3.zip
unzip instantcms-mcp-v1.2.3.zip && cd instantcms-mcp-*/release
npm install --production
node dist/index.js

# GitHub tarball install
npm install --save github:instantcms-dev/instantcms-mcp#v1.2.3

Install — npm install (after Publish to npm job is fixed)

The npm-publish CI job still fails because the repository NPM_TOKEN is a publish-token for the original instantcms-mcp@1.0.0 package from March 2026, and npm does not allow that token to create new packages in the @maxisoft scope. To make npm install @maxisoft/instantcms-mcp resolve, do one of:

1. Regenerate an automation token at https://www.npmjs.com/settings/tokens with the right "Allow publishing packages that don't already exist" flag, then replace the NPM_TOKEN repository secret at https://github.com/instantcms-dev/instantcms-mcp/settings/secrets/actions. Re-tag v1.2.3 to retrigger the workflow.

2. Manual npm publish from a local shell:

   npm install --no-save
   npm run build
   npm publish --access public

   Works immediately because you are logged in as maxisoft.

What's preserved from earlier work

• All 451 tests pass (8→21 suites, +179), property-based coverage in serialization/pagination, scaffold-addon round-trip for all 5 types, project workflow edge cases, knowledge lookups, artifact ZIP handling, db-tool invocations, MCP integration smoke, performance baselines.
• defineTool and defineToolWithManualResult helpers in src/utils/define-tool.ts.
• find-tool.ts token-based matching with priority scoring.
• publishConfig.access: "public" so plain npm publish works without the CLI flag.

Validation

npm run check       # green
npm run lint        # zero warnings
npm test --runInBand # 451 passed, 17 skipped, 0 failed (~15 s)

CI matrix on the v1.2.3 commit (Node 18, 20, 22, 24) all green.