Repository navigation
refactor: rename Sentinel to toolgauge everywhere user-facing - #23
Merged
Merged
Conversation
"sentinel" collided as a PyPI import name (the `sentinel` package installs a top-level sentinel module), as a command (HashiCorp Sentinel), and as a brand (mcp-sentinel is another MCP testing project). Renames the distribution, import package, command, rule namespace (TOOLGAUGE/...), config file, environment variables, history service binary, Docker image, GitHub Action and pre-commit hook. Kept: the repository URL and Go module paths, the reference server's internal names (database, dev headers, *.sentinel.local), the frozen sentinel/approx-v1 tokenizer id, "sentinel error/value" programming terms, and historical design docs and changelog entries. Old baselines still load (sentinelVersion is read as a fallback). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Pdv7R172x4XFq6AxwmmBBF
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
sentinelcollided in three places: the PyPI packagesentinelinstalls a top-levelsentinelmodule (import clash), HashiCorp Sentinel installs asentinelcommand (PATH clash), andmcp-sentinelis a different MCP testing project (brand clash).mcplintwas considered and rejected:mcplint-clialready installs both themcplintcommand and import package and does nearly the same job.toolgaugeis free on PyPI and npm and no MCP project uses it.What changes
Distribution, import package, command, rule namespace (
TOOLGAUGE/...),toolgauge.toml,TOOLGAUGE_*env vars,toolgauge-server, Docker image, GitHub Action, pre-commit hook, docs.What deliberately does not
Repository URL and Go module paths (they change only if the repo is renamed), the reference server's internal names (database, dev headers,
*.sentinel.local), the frozensentinel/approx-v1tokenizer id, 'sentinel error/value' programming terms, historical design docs and older changelog entries. Old baselines still load; theirSENTINEL/rule ids no longer match, so recreate a baseline after upgrading (no release has shipped, so no external users are affected).Test plan
uvx --from <wheel> toolgauge demoworks; oldsentinelcommand is goneGenerated by Claude Code