fix: hyphen title, 17,000+ count, live smoke gates publish (v0.1.1) - #11
Merged
Conversation
vreshch
marked this pull request as ready for review
July 17, 2026 23:27
- Replace em dash in SERVER_TITLE with hyphen (house rule + parity with the upstream proxy title) - Bump 12,000+ server-count claims to 17,000+ (true catalog size) - Tighten live-smoke test to the new mcp_* tool names only, drop TODO - Run live smoke (LIVE_SMOKE=1) in publish.yml before npm publish - Bump version 0.1.0 -> 0.1.1
vreshch
force-pushed
the
feature/polish-0-1-1
branch
from
July 17, 2026 23:33
54d7b31 to
3f0ffa2
Compare
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
1 participant
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.
Launch-readiness polish pass, 3 items:
Em dash bug -
SERVER_TITLEinsrc/server/create-find-proxy.tsused an em dash; house rule bans them and the proxied HTTP endpoint's own serverInfo title uses a hyphen. Fixed to'Find MCP - Agentage MCP Directory'. Repo-wide grep for em dashes now returns nothing.Count upgrade - all "12,000+" server-count claims bumped to "17,000+" (true synced catalog size ~17.3k):
package.jsondescription,README.md(banner alt text + 2 body mentions),docs/banner.svg(3 text nodes). Test fixtures (test/proxy.test.ts,test/fixtures/mock-upstream.ts) that carried the arbitraryio.agentage/totalmeta value of12000bumped to17300for consistency.Un-skip live smoke in release verify -
test/live-smoke.test.tspreviously accepted either the old (catalog__*) or new (mcp_*) tool names behind a TODO; tightened to require exactlymcp_categories/mcp_get/mcp_search, TODO dropped..github/workflows/publish.ymlnow runsLIVE_SMOKE=1 npm test -- test/live-smoke.test.tsagainst the real endpoint right beforenpm publish, so a publish cannot ship against a dead/renamed endpoint. Defaultnpm testbehavior is unchanged (still skipped withoutLIVE_SMOKE=1).Also: version bumped 0.1.0 -> 0.1.1 (patch: copy + title fix).
mcpName(io.agentage/find-mcp) unchanged, noserver.jsonin this repo.Verify evidence
npm run verify(type-check + lint + format:check + test + build): all green, 26 passed / 2 skipped (live-smoke skipped locally as expected).LIVE_SMOKE=1 npm test -- test/live-smoke.test.tsrun manually against the realcatalog.agentage.io/mcpendpoint: 2/2 passed - confirms the live endpoint serves exactlymcp_categories/mcp_get/mcp_searchandmcp_categoriesresponds successfully.