chore: point everything at Vycari/maintainerd after the transfer - #22
Merged
Conversation
The repo now lives at Vycari/maintainerd. GitHub redirects the old slug, so nothing was broken — but every install command and metadata URL still named a location that is no longer canonical, and redirects are a courtesy, not a contract. - 29 slug sites: the root README install command, all seven plugin READMEs (install command + "Source and issues"), and `homepage`/`repository` in all seven manifests. - marketplace.json `owner` -> Vycari. **Plugin `author` blocks deliberately stay Allen Hutchison**: ownership transferred, authorship didn't. They are different claims and only one of them moved. - The worked example said `allenhutchison/pepper`; pepper is `Vycari/pepper` per its own config. Fixed, along with the two illustrative slugs in config-schema.md that would otherwise have contradicted the example file sitting next to them. Manifests edited as targeted text replacements, not a json.dumps round-trip.
Greptile SummaryUpdates repository ownership references from
Confidence Score: 5/5The PR appears safe to merge, with the ownership, metadata, documentation, and vendored examples updated consistently. The changes are limited to canonical GitHub slugs and owner metadata, preserve plugin authorship, and introduce no identified behavioral, build, schema, or security failure.
|
| Filename | Overview |
|---|---|
| .claude-plugin/marketplace.json | Updates marketplace owner identity and URL to the new Vycari organization without changing plugin registration data. |
| README.md | Updates the documented marketplace installation command to use the canonical repository slug. |
| plugins/core/references/config-schema.md | Updates both canonical repo-slug examples to Vycari/pepper; corresponding vendored copies contain the same changes. |
| plugins/core/references/example-pepper.json | Updates the worked configuration's repository field to Vycari/pepper; corresponding vendored examples remain synchronized. |
| plugins/core/.claude-plugin/plugin.json | Updates canonical homepage and repository metadata while deliberately preserving the original author attribution. |
Reviews (1): Last reviewed commit: "chore: point everything at Vycari/mainta..." | Re-trigger Greptile
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.
The repo now lives at
Vycari/maintainerd. GitHub redirects the old slug, so nothing was broken — but every install command and metadata URL still named a location that is no longer canonical, and a redirect is a courtesy rather than a contract.What changed
29 slug sites — the root README install command, all seven plugin READMEs (install command + "Source and issues"), and
homepage/repositoryin all seven manifests.marketplace.jsonowner → Vycari. The seven pluginauthorblocks deliberately stay Allen Hutchison: ownership transferred, authorship didn't. Those are different claims and only one of them moved.Two stale examples, found while checking: the worked example config said
allenhutchison/pepper, but pepper isVycari/pepperper its ownmaintainerd.json. Fixed — along with the two illustrative slugs inconfig-schema.md, which would otherwise have contradicted the example file sitting right beside them.Not in this PR
The two consuming repos still point
extraKnownMarketplacesat the old slug:~/src/pepper/.claude/settings.json~/src/obsidian-gemini/.claude/settings.jsonBoth keep working via the redirect. They're separate repos with their own review flow, so they get their own PRs rather than riding along here.
Verification
Vendored copies regenerated and in sync; links resolve in both layouts; zero references to the old slug remain anywhere in the tree;
authorintact in 7/7 manifests. Manifests edited as targeted text replacements rather than ajson.dumpsround-trip — that's what mangled two em dashes back in #14.