feat: plugin template + create-plugin scaffold

[kayodebristol]

Adds a complete plugin template and scaffolding script. Usage: ./scripts/create-plugin.sh my-plugin 'My Plugin' author. Encodes the .px-first development pattern. Equivalent to svelte-tauri-template for plugin-scoped development.

[Copilot]

Pull request overview

Adds a new template/ directory intended to serve as the starting point for pares-radix plugins, plus a scripts/create-plugin.sh scaffolder that copies the template into plugins/<id> and substitutes placeholders.

Changes:

• Introduces a plugin template containing a manifest, TypeScript entry/handlers, .px examples, and .px-based tests.
• Adds scripts/create-plugin.sh to scaffold a new plugin from the template and replace placeholders.
• Adds template documentation describing the plugin architecture and publishing flow.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 9 comments.

Show a summary per file

File	Description
template/tests/plugin.px	Adds an example executable .px test procedure.
template/src/index.ts	Adds a template plugin entrypoint and lifecycle hooks.
template/src/handlers/index.ts	Adds an example action handler and handler map.
template/README.md	Documents the template structure, workflow, and publishing steps.
template/px/main.px	Adds example .px procedures and trigger documentation.
template/px/constraints.px	Adds example constraint documentation for .px.
template/manifest.json	Adds a template plugin manifest with placeholders.
scripts/create-plugin.sh	Adds a scaffold script to copy the template and substitute placeholders.

Comments suppressed due to low confidence (3)

template/src/index.ts:32

• console.log in the plugin lifecycle entrypoint conflicts with the repo’s platform guidance to avoid manual console logging for business events (see plures/no-manual-logging). Since this file is intended to be copied into plugins/, it will introduce lint warnings in new plugins; prefer removing it or routing through the platform’s structured/contract-based observability mechanism.

    // .px files in the px/ directory are automatically compiled and
    // registered by pares-radix. You don't need to do anything here
    // for .px procedures to work — just drop .px files in px/.

    console.log(`[{{plugin-id}}] loaded`);
  },

template/src/index.ts:40

• onActivate and onDeactivate declare a ctx parameter that isn't used. In this repo ESLint enforces @typescript-eslint/no-unused-vars as an error for plugin sources, so scaffolded plugins will fail lint unless the param is used or renamed (e.g. _ctx) / removed.

  async onActivate(ctx: PluginContext) {
    // Plugin activated — start any background work, subscriptions, etc.
  },

  async onDeactivate(ctx: PluginContext) {
    // Plugin deactivated — clean up subscriptions, timers, etc.
  },

template/src/handlers/index.ts:23

• The example handler destructures params via a type assertion without runtime validation. If a procedure calls hello with a non-object/null payload, this will throw at runtime. Since this is the scaffolded starting point, it’s better to demonstrate safe parsing/validation (or at least guard typeof params === 'object' && params !== null).

const hello: ActionHandler = async (params: unknown) => {
  const { name } = params as { name: string };
  return { greeting: `Hello, ${name}!` };
};

[kayodebristol]

Closing: CI uses npm but package.json has workspace:* deps (requires pnpm). Stale since May 20. Will recreate with corrected CI config when plugin template work resumes.