docs: marketplace-first install, first-party plugin sections, palette comment fixes#13
Open
fielding wants to merge 2 commits into
Open
docs: marketplace-first install, first-party plugin sections, palette comment fixes#13fielding wants to merge 2 commits into
fielding wants to merge 2 commits into
Conversation
Five of the eight base24 slot comments described roles the templates don't actually use (base12 said strings; strings are base17, etc.). Align the comments with the real assignments in the VS Code template and the README palette table. No hex changes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Xan5eRiAXvcnAVvXHejdTz
The README still told people to build the VS Code extension from
source with a version pinned at 1.0.0, while the extension has been
on the Marketplace and Open VSX since January. Lead with the
one-line install instead.
The first-party Neovim plugin, vanilla Vim colorscheme, and Zed
extension shipped in v1.5/v1.6 but the README never mentioned them
('Vim / Neovim — via tinty' was the only trace). Add install
sections for all three — the lazy.nvim snippet is headless-verified
— and update the app table and site app cards to match.
Also switch the marker example to lead with the sigils rather than
the legacy TODO/NOTE aliases, and align the base13 role in the
palette table with actual usage (diff added, CSS classes).
README.md regenerated via make build; make check passes.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Xan5eRiAXvcnAVvXHejdTz
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.
What
A fresh-eyes writing pass on the README and palette.
.vsixpinned at 1.0.0; the extension has been on the VS Code Marketplace and Open VSX since January (verified live before writing). Now leads withcode --install-extension fielding.human-plus-plus.colorscheme humanplusplus+setup()both load). Zed gets dev-extension instructions since the registry query comes back empty — no false availability claims.!!??>>) instead of the legacy TODO/NOTE aliases it's supposed to be replacing.Verification
make checkpasses (palette valid, build clean, analysis passes)make build— no driftnvim --headlessinstall-path smoke test passes🤖 Generated with Claude Code
https://claude.ai/code/session_01Xan5eRiAXvcnAVvXHejdTz