[raphaelnz]

Why

With plugin.json at the plugin root, omp's agent-plugins provider claims the package and skips every skill whose frontmatter has disable-model-invocation, icon, color, or globs. On omp 18.12.2 that is 54 of 56 skills, so skill://poteto-mode and /skill:how are unknown. Without the manifest, the omp-plugins provider loads the plugin's skills/ directory.

Closes #21. Closes #22.

What changed

• lib.sh no longer extracts or copies pstack/plugin.json, and sync-upstream.sh no longer writes its version.
• The plugin manifest check now fails when plugins/pstack/plugin.json exists.
• Delete plugins/pstack/plugin.json and record the reason in PORTING.md.

Scope

• Keeps the skill frontmatter as upstream wrote it.
• Other tools that read Agent Plugins manifests lose this manifest. The port targets omp.
• agent-plugins validator drops 54 of 56 skills when plugin.json is present #22 says that omp-plugins reads package.json omp.skills. That is wrong. It reads the skills/ directory, and PORTING.md says so.

Tradeoffs

A rules.sed rule could strip the four fields so the manifest passes validation. Then every hidden skill would become model-invocable.

Blast Radius

This affects marketplace installs and upgrades. Users who deleted plugin.json by hand see no change. #23 regenerates plugin.json at 0.15.30, so whichever PR merges second needs a rebase that deletes that file.

Verification

• In a clean HOME on omp 18.12.2, an install from main prints 54 Skipping skill warnings in omp skill list and lists neither poteto-mode nor how. An install from this branch prints none and lists both.
• bash omp-port/check-port.sh exits 0 in an Alpine container, with plugin manifest PASS and reproducible PASS.