pi-superwhisper-paste 0.1.14 → 0.1.15

package/CHANGELOG.md

@@ -4,6 +4,12 @@ All notable changes to this project will be documented in this file.
 
 This project follows semantic versioning.
 
+## [0.1.15] - 2026-06-05
+
+### Changed
+
+- Remove stale template-maintenance docs (`github-template.md`, `repository-settings.md`, `typescript.md`) from the published package.
+
 ## [0.1.14] - 2026-06-05
 
 ### Changed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-superwhisper-paste",
-  "version": "0.1.14",
+  "version": "0.1.15",
   "description": "Superwhisper clipboard bridge for Pi on Windows.",
   "type": "module",
   "license": "MIT",

package/docs/github-template.md

@@ -1,43 +0,0 @@
-# GitHub Template Repository
-
-Enable template mode on the source repository:
-
-```txt
-GitHub repo → Settings → General → Template repository
-```
-
-Create a public repository from the template:
-
-```bash
-gh repo create OWNER/new-pi-extension \
-  --public \
-  --template OWNER/pi-extension-template \
-  --clone
-```
-
-Create a private repository from the template:
-
-```bash
-gh repo create OWNER/new-pi-extension \
-  --private \
-  --template OWNER/pi-extension-template \
-  --clone
-```
-
-Include all branches if needed:
-
-```bash
-gh repo create OWNER/new-pi-extension \
-  --public \
-  --template OWNER/pi-extension-template \
-  --include-all-branches \
-  --clone
-```
-
-After creation:
-
-```bash
-cd new-pi-extension
-npm install
-npm run ci
-```

package/docs/repository-settings.md

@@ -1,40 +0,0 @@
-# Repository Settings
-
-Use this file after creating a real repository from the template.
-
-## GitHub About
-
-Suggested fields:
-
-- Description: Bridge Superwhisper clipboard dictation into the Pi TUI editor on Windows.
-- Website: npm package URL or project docs URL
-- Topics:
-  - `pi`
-  - `pi-package`
-  - `pi-extension`
-  - `superwhisper`
-  - `clipboard`
-  - `windows`
-  - `typescript`
-
-## Template mode
-
-This repository is a concrete package, not a template. Do not enable template mode unless it is intentionally turned into a reusable starter.
-
-## Branch protection
-
-Recommended for public packages:
-
-- Require pull request before merging
-- Require status checks to pass
-- Require `CI` workflow
-- Block force pushes on the default branch
-
-## npm package page
-
-After first publish:
-
-- Confirm README renders correctly
-- Confirm package provenance appears
-- Confirm package contents are intentional
-- Add npm URL to GitHub About and README

package/docs/typescript.md

@@ -1,75 +0,0 @@
-# TypeScript Guide
-
-This is a TypeScript-first Pi package template.
-
-## Layout
-
-```txt
-extensions/*.ts      Pi extension entrypoints
-lib/*.ts             Shared TypeScript helpers
-skills/*/SKILL.md    Agent Skills
-prompts/*.md         Prompt templates
-themes/*.json        Themes
-tests/*.test.mjs     Smoke tests
-tests/*.test.ts      Optional TypeScript tests if you add a TS test runner
-```
-
-Pi loads TypeScript extensions directly, so no build step is required for normal use.
-
-## Strict mode
-
-`tsconfig.json` keeps `strict: true`. Prefer fixing types over loosening compiler options.
-
-## Extension entrypoints
-
-Two entrypoint styles are shown:
-
-- `extensions/hello.ts`: single-file extension
-- `extensions/index.ts`: index-style extension that imports shared code from `lib/`
-
-For larger packages, keep entrypoints thin and put reusable logic in `lib/`.
-
-## TypeBox schemas
-
-Use TypeBox schemas for custom tool parameters.
-
-```ts
-import { Type } from "typebox";
-
-const parameters = Type.Object({
-  name: Type.String({ description: "Name to greet" }),
-});
-```
-
-## String enums
-
-For string choices, use the local `StringEnum` helper from `lib/schema.ts`.
-
-```ts
-import { StringEnum } from "../lib/schema.ts";
-
-const mode = StringEnum(["short", "friendly"], {
-  description: "Greeting style",
-});
-```
-
-This emits a JSON Schema `enum`, which is friendlier to model providers than a union of string literals.
-
-## Runtime dependencies vs peer dependencies
-
-Pi bundles core packages for extension authors. Keep Pi-provided packages as `peerDependencies` and also install them as `devDependencies` for local typechecking.
-
-Use `peerDependencies` for:
-
-- `@earendil-works/pi-coding-agent`
-- `@earendil-works/pi-ai`
-- `@earendil-works/pi-tui`
-- `typebox`
-
-Use `dependencies` for runtime packages your extension imports that Pi does not provide.
-
-Use `devDependencies` for local-only tools such as TypeScript, test runners, and linters.
-
-## Package contents
-
-Control npm package contents with `package.json` `files`. Prefer this over `.npmignore` so the published package stays explicit.