Maurice 39f27ef55d chore(plugin-sdk): make it npm-publishable so npx resolves for authors ...

The docs told authors to run `npx create-trek-plugin` / `npx trek-plugin`,
but nothing published under those names, so npx couldn't resolve them.

- Ship one package, `trek-plugin-sdk`, with a bin that matches the package
  name (`trek-plugin-sdk`) so `npx trek-plugin-sdk <command>` resolves with
  zero install. The dispatcher gained a `create` subcommand, so every step
  (create/validate/pack/entry/release) runs through that one entry point.
  The short `trek-plugin` / `create-trek-plugin` bins still work once
  installed.
- Package hardening for publish: repository+directory (monorepo subdir),
  homepage/bugs/author/engines, publishConfig public, a prepublishOnly that
  builds + tests, and a LICENSE file.
- A publish workflow: pushing a `plugin-sdk-v*` tag builds and publishes with
  the NPM_TOKEN repo secret.
- Docs (SDK README + the four wiki pages) now use `npx trek-plugin-sdk <cmd>`,
  the invocation that actually resolves.

2026-07-04 19:11:23 +02:00

..

ISSUE_TEMPLATE

docs: add Proxmox VE LXC install guide and update CI ignore paths

2026-04-27 00:14:50 +02:00

workflows

chore(plugin-sdk): make it npm-publishable so npx resolves for authors

2026-07-04 19:11:23 +02:00

FUNDING.yml

add funding

2026-03-26 17:28:05 +01:00

PULL_REQUEST_TEMPLATE.md

docs: document wiki-only PR exemption from branch enforcement

2026-05-03 18:48:39 +02:00