Add @pins header, trim oversized preset descriptions - #61
Merged
Conversation
Descriptions had grown into multi-paragraph essays — mcp-litellm was 1363 chars — and they render in full on the install confirm, the batch preview and `list -l`. Trim the ten over 450 chars to one or two sentences; leave the eleven that were already short alone. Promote pinned third-party versions out of prose into `@pins: name version`, a repeatable optional header shown on the install confirm and in `list -l`, so you can see what a preset drags in before saying yes. Applied to the four presets that install something third-party. Two tests guard the metadata against drift: every @pins version must appear in the body or @fetch it describes, and every @fetch dest must be referenced by the body or @path — so a version bump can't land on one side only. A third caps descriptions at 450 chars so they can't regrow.
Merged
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.
Why
Preset
@descriptionblocks had grown into multi-paragraph essays —mcp-litellmwas 1363 chars. That text renders in full in three places (install confirm, batch preview,list -l), so every install prompt was a wall of prose. Meanwhile the one fact worth scanning — which third-party version a preset pins — was buried in that prose or visible only inside the JSON body.Descriptions
Trimmed the ten presets whose description exceeded 450 chars to one or two sentences. There was a clean gap in the data at that line (480 → 420), so it splits the catalogue without argument; the other eleven were already short and are untouched.
mcp-litellmmcp-vscodemcp-playwrightplugin-litellm-pricingmcp-litellm-passthroughprovider-litellmpermissions-build-toolspermissions-container-infopermissions-shell-safeplugin-superpowers@pinsNew optional, repeatable header recording a third-party artifact installed at an exact version:
// @pins: @playwright/mcp 0.0.78Shown on the install confirmation (
Pins : @playwright/mcp @ 0.0.78) and underlist -l. Applied to the four presets that install something third-party:jdtls-lombok(lombok 1.18.46),mcp-playwright,plugin-litellm-pricing(0.2.0),plugin-superpowers(tag v6.2.0).Drift guards
Metadata that duplicates a version rots when only one side gets bumped. Two tests close that:
@pinsversion must appear in the body or@fetchline it describes@fetchdest must be referenced by the body or@path— catches bumping@fetchto lombok 1.18.47 while the-javaagentflag still points at 1.18.46, which would boot jdtls against a jar that was never downloadedA third test caps descriptions at 450 chars so they can't regrow.
Also
README.mddocuments@pins; the built-in preset table lists pinned versionsAGENTS.mdgains@pinsand the description rule, and is trimmed 6748 → 5280 chars@versionbumps — prose-only edits don't change a preset's payload109 tests pass.