Support promoting a forked plugin to its own marketplace repo

[albertgwo]

Problem

When a forked plugin outgrows its embedded location in the config repo and gets published to its own GitHub repo, claude-sync has no mechanism to handle the transition. The user must manually:

1. Add a new marketplace entry in config.yaml pointing to the new repo
2. Move the plugin from plugins.forked to plugins.upstream
3. Remove the hardcoded hook path from config.yaml settings (the plugin's own hooks.json handles registration when installed from a marketplace)
4. Delete the old embedded copy from ~/.claude-sync/plugins/
5. Run claude-sync pull to regenerate settings

This is error-prone and breaks the sync workflow — other machines pulling the config will still reference the old embedded path until manually updated.

Context

Concrete case: bash-validator started as a forked plugin embedded at ~/.claude-sync/plugins/bash-validator/. After adding documentation and a skill, it was published to its own repo at ruminaider/bash-validator. The config still has:

plugins:
  forked:
    - bash-validator  # still points to embedded copy

hooks:
  PreToolUse: |
    ...
    "command": "python3 ~/.claude-sync/plugins/bash-validator/hooks/bash-validator.py"
    ...

This hardcoded path will break on any machine that doesn't have the embedded copy.

Expected Behavior

A command like claude-sync promote bash-validator --repo ruminaider/bash-validator that:

1. Registers ruminaider/bash-validator as a marketplace source
2. Moves the plugin from forked to upstream in config.yaml
3. Removes the hardcoded hook from settings (defers to the plugin's own hooks.json)
4. Cleans up the old embedded copy from ~/.claude-sync/plugins/
5. Updates settings.json so the change takes effect immediately

Related Issues

• pull should auto-register marketplaces referenced by plugins or from config.yaml marketplace section #9 (pull should auto-register marketplaces)
• fork command creates duplicate plugin source without disabling original #19 (fork creates duplicate sources)
• pull does not clone custom marketplace repos before installing plugins #5 (pull doesn't clone marketplace repos before installing)

These all touch the fork/marketplace lifecycle — this issue is the missing "unfork" direction.

[albertgwo]

Manual Migration Performed

Completed the bash-validator promotion manually. Here's the full list of changes required, which a promote command should automate:

config.yaml changes (3 edits)

1. Moved plugin from forked to upstream:

   # Before
   plugins:
     forked:
       - bash-validator
   
   # After
   plugins:
     upstream:
       - bash-validator@bash-validator-marketplace

2. Added marketplace entry:

   marketplaces:
     bash-validator-marketplace:
       source: github
       repo: ruminaider/bash-validator

3. Removed hardcoded hook — the plugin's own hooks.json registers the PreToolUse hook when installed from a marketplace. The manual hook entry (python3 ~/.claude-sync/plugins/bash-validator/hooks/bash-validator.py) had to be deleted from the hooks.PreToolUse block.

settings.json changes (2 edits)

4. Removed hardcoded PreToolUse hook for the Bash matcher (same as config.yaml change, but in the generated output).

5. Cleaned up enabledPlugins — removed "bash-validator@": false and "bash-validator@claude-sync-forks": true, kept only "bash-validator@bash-validator-marketplace": true.

Not yet done

6. Delete old embedded copy at ~/.claude-sync/plugins/bash-validator/ — still present but no longer referenced.
7. Clean stale plugin cache at ~/.claude/plugins/cache/claude-sync-forks/bash-validator/ — orphaned.
8. Update plugin-sources.yaml — already had active_source: bash-validator-marketplace so no change was needed, but a promote command should verify this.
9. Push config.yaml changes to the config repo so other machines pick up the transition.

Key insight for implementation

The hardcoded hook path is the most dangerous part of this migration. When a forked plugin has hooks defined in config.yaml settings (rather than in its own hooks.json), promoting to a marketplace plugin means those hooks silently stop working on other machines. The promote command should detect hooks referencing ~/.claude-sync/plugins/<plugin-name>/ and either remove them (if the plugin's hooks.json covers them) or warn the user.