note: bump version here, in mix.exs, and npm/package.json too

BUILD ========

Manual npm Publish Path (No CI Token Dependency) ------------------------------------------------

This guide handles the exact case where npm i -g graphonomous fails because the expected GitHub release asset does not exist yet.

Error pattern:

• npm postinstall tries to download:

https://github.com/c-u-l8er/graphonomous/releases/download/vX.Y.Z/graphonomous-vX.Y.Z-linux-x64.tar.gz

• install fails with HTTP 404 when release/tag/assets are missing.

Prerequisites -------------

• You are in this repo: ProjectAmp2/graphonomous

• gh auth status is valid for the target GitHub account/org

• npm whoami is valid for the npm publisher account

• Local toolchain is installed (Elixir/OTP, Node/npm, git, tar)

1. Set version once (important)

Pick one version and use it consistently in all commands below.

VERSION="0.1.1"
TAG="v${VERSION}"
TARGET="linux-x64"
ASSET="graphonomous-v${VERSION}-${TARGET}.tar.gz"

1. Ensure local project version matches

Confirm versions:

• mix.exs -> version: "0.1.1"

• npm/package.json -> "version": "0.1.1"

Quick checks:

grep -n 'version:' mix.exs
node -p "require('./npm/package.json').version"

2. Build OTP release and package asset

cd /home/travis/ProjectAmp2/graphonomous
MIX_ENV=prod mix release --overwrite
mkdir -p dist
tar -czf "dist/${ASSET}" --exclude='*/priv/beam' -C _build/prod/rel graphonomous
ls -lh "dist/${ASSET}"

Sanity check the release command:

_build/prod/rel/graphonomous/bin/graphonomous version
_build/prod/rel/graphonomous/bin/graphonomous eval "Graphonomous.CLI.main(System.argv())" --help

3. Create tag if missing and push it

Check if the tag exists locally/remotely:

git tag --list "${TAG}"
git ls-remote --tags origin "${TAG}"

If missing locally:

git tag "${TAG}"

Push tag (safe if already present remotely; it will fail noisily if conflicting):

git push origin "${TAG}"

4. Create GitHub release if missing

Your previous error release not found means this step is required.

Create release and upload first asset in one command:

gh release create "${TAG}" "dist/${ASSET}" \
  --title "${TAG}" \
  --notes "Manual release assets upload"

If release already exists, upload (or replace) asset:

gh release upload "${TAG}" "dist/${ASSET}" --clobber

Verify release + assets:

gh release view "${TAG}"
gh release view "${TAG}" --json assets --jq '.assets[].name'

5. Re-test npm install

npm i -g graphonomous
graphonomous --help

If global install was partially broken earlier, clean and retry:

npm uninstall -g graphonomous
npm cache verify
npm i -g graphonomous

6. Optional: Quick runtime smoke test

mkdir -p ~/.graphonomous
graphonomous --db ~/.graphonomous/knowledge.db --embedder-backend fallback

(Stop with Ctrl+C after startup confirmation.)

If release creation still fails -------------------------------

A) gh release create ... says tag is missing

Push the tag first:

git push origin "${TAG}"

B) Permission error on release create/upload

Check GitHub auth/account:

gh auth status
gh repo view

Ensure you have write access to c-u-l8er/graphonomous.

C) npm still fails with 404

Confirm asset naming exactly matches what installer expects:

echo "Expected: ${ASSET}"
gh release view "${TAG}" --json assets --jq '.assets[].name'

Name must match exactly: graphonomous-vX.Y.Z-linux-x64.tar.gz

D) Zed shows "context server request timeout"

This can occur if your runtime is using older stdio transport behavior from upstream Anubis MCP (decoded message list handling / stdio response write issues).

Graphonomous production path uses a vendored Anubis patch:

• dependency is pinned to vendor/anubis_mcp

• stdio transport fixes are in:

• vendor/anubis_mcp/lib/anubis/server/transport/stdio.ex

Verify your runtime is actually using vendored dependency code (not stale compiled deps):

cd /home/travis/ProjectAmp2/graphonomous
mix deps.get
mix clean
rm -rf _build deps
mix deps.get
mix compile --warnings-as-errors
mix test test/mcp_integration_test.exs

If timeout persists in Zed:

1. Restart Zed completely.

2. Confirm your MCP command points at the expected graphonomous binary/version.

3. Run graphonomous --help in shell from the same environment as Zed launch.

4. Re-check npm package version and release source:

• npm view graphonomous version

• npm ls -g --depth=0 graphonomous

Multi-platform publishing (later) ---------------------------------

For broader support, repeat asset build/upload on each target machine:

• linux-x64

• linux-arm64

• darwin-x64

• darwin-arm64

Asset names must follow:

• graphonomous-vX.Y.Z-linux-x64.tar.gz

• graphonomous-vX.Y.Z-linux-arm64.tar.gz

• graphonomous-vX.Y.Z-darwin-x64.tar.gz

• graphonomous-vX.Y.Z-darwin-arm64.tar.gz

Minimal command checklist -------------------------

# note: bump version here, in mix.exs, and npm/package.json too
# then git push with version as commit name after running:
cd /home/travis/ProjectAmp2/graphonomous
VERSION="0.1.10"; TAG="v${VERSION}"; TARGET="linux-x64"; ASSET="graphonomous-v${VERSION}-${TARGET}.tar.gz"
MIX_ENV=prod mix release --overwrite
mkdir -p dist
tar -czf "dist/${ASSET}" --exclude='*/priv/beam' -C _build/prod/rel graphonomous
git tag "${TAG}" 2>/dev/null || true
git push origin "${TAG}"
gh release create "${TAG}" "dist/${ASSET}" --title "${TAG}" --notes "Manual release assets upload" || gh release upload "${TAG}" "dist/${ASSET}" --clobber
npm i -g graphonomous
graphonomous --help
cd ./npm
npm publish