pi-short-links 0.1.0 → 0.2.0

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 0.2.0
+
+- Align repo with the pi-extension-template generated-package shape: canonical README, sibling-matching CI/publish/auto-release workflows, and docs cleanup.
+- Remove template placeholders: `example-skill`, `example` prompt, `example-theme`, greeting/dashboard/bridge/layout extensions, the `create-pi-extension` workspace, and bootstrap docs.
+- CI now publishes to npm via Trusted Publishing on version bump (version push to main -> tag -> GitHub Release -> publish workflow).
+
 ## 0.1.0
 
 - Initial release: force OSC 8 for Orca/`FORCE_HYPERLINK`, shorten long assistant URLs and paths to pane-fitting markdown links.

package/README.md

@@ -1,46 +1,120 @@
 # Pi Short Links
 
-Shorten long URLs and absolute file paths in Pi assistant output so clickable links fit the terminal pane.
+[![Join dotfield.xyz on Discord](https://img.shields.io/badge/Join%20dotfield.xyz%20on%20Discord-5865F2?logo=discord&logoColor=white)](https://discord.gg/4945dXZVW5)
 
-## Why
+[![CI](https://github.com/eiei114/pi-short-links/actions/workflows/ci.yml/badge.svg)](https://github.com/eiei114/pi-short-links/actions/workflows/ci.yml)
+[![Publish](https://github.com/eiei114/pi-short-links/actions/workflows/publish.yml/badge.svg)](https://github.com/eiei114/pi-short-links/actions/workflows/publish.yml)
+[![npm version](https://img.shields.io/npm/v/pi-short-links.svg)](https://www.npmjs.com/package/pi-short-links)
+[![npm downloads](https://img.shields.io/npm/dm/pi-short-links.svg)](https://www.npmjs.com/package/pi-short-links)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
+[![Pi package](https://img.shields.io/badge/pi-package-purple.svg)](https://pi.dev/packages)
+[![Trusted Publishing](https://img.shields.io/badge/npm-Trusted%20Publishing-blue.svg)](docs/release.md)
+<a href="https://buymeacoffee.com/ekawano114m"><img src="https://cdn.buymeacoffee.com/buttons/v2/default-yellow.png" alt="Buy Me A Coffee" width="217" height="60"></a>
 
-Long bare URLs wrap across lines. Terminals that only detect text URLs (or terminals Pi does not yet mark as OSC 8-capable) open only the first wrapped line. This package:
+> Shorten long URLs and file paths in Pi assistant output so links fit the pane and stay clickable.
 
-1. Forces OSC 8 hyperlinks when `FORCE_HYPERLINK=1` or `TERM_PROGRAM=Orca`
-2. Rewrites assistant text that exceeds the pane width into short markdown links (`[host/…tail](full-url)`, `[~/dir/…/file](file://…)`)
-3. Leaves fenced code blocks untouched
+## What this is
+
+Pi Short Links is a TypeScript Pi package that rewrites long bare `http(s)` URLs and absolute/`~/` paths in assistant text into short markdown links (`[host/…tail](full-url)`, `[~/dir/…/file](file://…)`). When `FORCE_HYPERLINK=1` or `TERM_PROGRAM=Orca`, it also forces Pi TUI OSC 8 hyperlinks on. Fenced code blocks are left untouched.
+
+## Features
+
+- Pane-width-aware shortening for bare `http(s)` URLs.
+- Absolute / `~/` path shortening with `file://` targets.
+- Forces OSC 8 hyperlinks when `FORCE_HYPERLINK=1` or `TERM_PROGRAM=Orca`.
+- Skips content inside fenced code blocks.
+- Does not rewrite existing markdown links' destinations.
 
 ## Install
 
+Install the published npm package with Pi:
+
 ```bash
 pi install npm:pi-short-links
-# or local dogfood
-pi install /path/to/pi-short-links
 ```
 
-Add to project `.pi/settings.json` `packages`:
+Pin a specific version when you want reproducible installs:
 
-```json
-"../../OSS/pi-short-links"
+```bash
+pi install npm:pi-short-links@0.2.0
 ```
 
-## Features
+Install into the current project instead of your user Pi settings:
+
+```bash
+pi install npm:pi-short-links -l
+```
+
+Or install from GitHub:
+
+```bash
+pi install git:github.com/eiei114/pi-short-links
+```
+
+Try it without permanently installing:
+
+```bash
+pi -e npm:pi-short-links
+```
+
+## Quick start
 
-- Pane-width-aware shortening for bare `http(s)` URLs
-- Absolute / `~/` path shortening with `file://` targets
-- Skips content inside ` ``` ` fences
-- Does not rewrite existing markdown links' destinations
+Try the local checkout without permanently installing it:
 
-## Non-goals
+```bash
+FORCE_HYPERLINK=1 pi -e .
+```
+
+Then send a message containing a long URL or absolute file path and confirm it renders as a short clickable link.
 
-- Orca-specific wrap-join fixes
-- Public URL shorteners
-- Rewriting tool-result bodies (assistant text only in v0.1)
+## Package contents
+
+| Path | Purpose |
+|---|---|
+| `extensions/short-links.ts` | Assistant-text shortening hook and OSC 8 force |
+| `lib/shorten.ts` | URL/path shortening logic |
+| `docs/release.md` | Trusted Publishing and release flow |
+| `README.md` | GitHub and npm package entrypoint |
+| `CHANGELOG.md` | Versioned release notes |
+| `LICENSE` | MIT license |
 
 ## Development
 
 ```bash
 npm install
-npm test
-npm run typecheck
+npm run ci
+npm pack --dry-run
+FORCE_HYPERLINK=1 pi -e .
+```
+
+## Release
+
+This package is set up for npm Trusted Publishing, so no `NPM_TOKEN` is required.
+
+```bash
+npm version minor
+git push
 ```
+
+See [`docs/release.md`](docs/release.md) for setup details.
+
+## Docs
+
+- [`docs/release.md`](docs/release.md) — Trusted Publishing and automated release details
+- [`ROADMAP.md`](ROADMAP.md) — current status and planned work
+
+## Security
+
+Pi packages can execute code with your local permissions. Review extensions before installing third-party packages.
+
+For vulnerability reporting, see [`SECURITY.md`](SECURITY.md).
+
+## Links
+
+- npm: https://www.npmjs.com/package/pi-short-links
+- GitHub: https://github.com/eiei114/pi-short-links
+- Issues: https://github.com/eiei114/pi-short-links/issues
+
+## License
+
+MIT

package/docs/release.md

@@ -1,108 +1,36 @@
 # Release
 
-This repository publishes **`create-pi-extension`** to npm using Trusted Publishing with GitHub Actions OIDC.
+`pi-short-links` publishes to npm through GitHub Actions Trusted Publishing.
 
-The root `pi-extension-template` package is the **template source** and is not published to npm. Only `packages/create-pi-extension` is published.
+## Initial bootstrap publish
 
-Do not add `NPM_TOKEN` or long-lived npm tokens to GitHub Secrets.
-
-## One-time npm setup
-
-On npmjs.com, configure Trusted Publishing for **`create-pi-extension`**:
-
-- Publisher: GitHub Actions
-- Repository: `eiei114/pi-extension-template`
-- Workflow filename: `publish.yml`
-- Permissions: publish (and stage publish if used)
-
-Remove or update any Trusted Publisher entry that still targets the legacy root package name `pi-extension-template`.
-
-## Publish
+npm only allows Trusted Publisher configuration after the package exists. Publish `0.1.0` once from a maintainer machine using interactive `npm login`:
 
 ```bash
-npm version patch
-git push
-```
-
-On `main`, `.github/workflows/auto-release.yml` checks the root `package.json` **repository version**. If `v<version>` does not exist yet, it creates the tag, creates the GitHub Release, then explicitly dispatches `.github/workflows/publish.yml` for that tag.
-
-The `v*.*.*` tag also triggers `.github/workflows/publish.yml`, which syncs the bundled template, runs CI, and publishes `create-pi-extension@<version>` to npm when tags are pushed manually.
-
-Publishing also runs when a GitHub Release is published, and can be run manually from GitHub Actions with `workflow_dispatch`.
-
-`publish.yml` runs `npm run sync:template` before publish so the tarball includes the current **Bundled template** under `packages/create-pi-extension/template/`.
-
-The workflow skips `create-pi-extension@<version>` if that exact package version already exists on npm.
-
-### Rerun and manual dispatch
-
-`publish.yml` checks the public npm registry API before `setup-node` configures OIDC auth. That keeps already-published reruns green:
-
-- `workflow_dispatch` on an existing tag/ref
-- duplicate `publish.yml` runs for the same `v<version>`
-- auto-release handoff retries after a successful publish
-
-When the version already exists, the job still runs validation but logs `publish intentionally skipped` and exits without calling `npm publish`.
-
-Do not use `npm view` after `setup-node` with `registry-url` for this guard. Trusted Publishing OIDC can make authenticated metadata reads look like `404`, which leads to duplicate `E403` publish failures.
-
-See also `docs/publish-rerun-rollout.md` for downstream rollout notes.
-
-### First publish / Trusted Publisher not configured
-
-`publish.yml` logs two different situations before `npm publish`:
-
-| Registry check | Meaning | Workflow behavior |
-| --- | --- | --- |
-| `GET /create-pi-extension` returns **404** | Package name is **not registered** on npm yet | Continues to publish; logs Trusted Publisher setup guidance |
-| `GET /create-pi-extension/<version>` returns **200** | That exact version is **already published** | Logs `publish intentionally skipped` and exits green without `npm publish` |
-| Package exists, version returns **404** | New version for an existing package | Continues to publish |
-
-If Trusted Publisher is missing or still targets the legacy `pi-extension-template` package, `npm publish` fails with:
-
-```text
-npm error code E404
-npm error 404 Not Found - PUT https://registry.npmjs.org/create-pi-extension - Not found
+npm ci
+npm run ci
+npm publish --access public
 ```
 
-That `E404` is **not** the rerun skip path. It means npm rejected the publish because the package name is not registered under your account yet, or OIDC Trusted Publishing is not authorized for `create-pi-extension` + `publish.yml`.
-
-Fix (human-owned, one-time on npmjs.com):
-
-1. Open **create-pi-extension** on npm (or create the package name under your npm org/user if npm allows pre-registration).
-2. Add **Trusted Publisher**: GitHub Actions, repository `eiei114/pi-extension-template`, workflow filename `publish.yml`, permissions **publish** (and stage publish if used).
-3. Remove or update any Trusted Publisher entry that still targets the legacy root package `pi-extension-template`.
-4. Re-run `publish.yml` via `workflow_dispatch` on the release tag/ref (for example `v0.1.7`).
-
-Do not add `NPM_TOKEN` to GitHub Secrets; this repository uses OIDC Trusted Publishing only.
-
-## Workflow guardrail
+Immediately after the package exists, configure Trusted Publishing below. Do not store the interactive login token in GitHub Secrets. Revoke the local token after setup when it is no longer needed.
 
-Do not ship a new Pi OSS package or version bump with only `package.json` changes.
-The repository must include the release workflow pair:
+## One-time Trusted Publishing setup
 
-- `.github/workflows/auto-release.yml` creates `v<version>` tags and GitHub Releases from `main` version bumps.
-- `.github/workflows/publish.yml` syncs the template and publishes `create-pi-extension` through Trusted Publishing.
+Configure npm Trusted Publishing for:
 
-Important: tags or releases created by `GITHUB_TOKEN` do not reliably fan out into another workflow through normal `push.tags` or `release.published` triggers. The template keeps publishing reliable by having `auto-release.yml` explicitly dispatch `publish.yml` after creating the tag/release. If you change the release flow, keep one explicit handoff path: `workflow_dispatch` from auto-release, `repository_dispatch`, or `workflow_run` on the auto-release workflow.
+- Package: `pi-short-links`
+- Provider: GitHub Actions
+- Owner: `eiei114`
+- Repository: `pi-short-links`
+- Workflow: `publish.yml`
 
-## GitHub Actions requirements
+Do not add `NPM_TOKEN` or `NODE_AUTH_TOKEN` to repository workflows or secrets.
 
-- `permissions: id-token: write`
-- `permissions: actions: write` on auto-release so it can dispatch `publish.yml`
-- `auto-release.yml` must call `gh workflow run publish.yml --ref "$TAG" -f ref="$TAG"`, or `publish.yml` must have an equivalent explicit handoff trigger such as `workflow_run`
-- GitHub-hosted runner
-- Node.js 24, so the release job uses a current npm CLI for Trusted Publishing
-- Bun (for `sync:template` before publish)
-- No `NPM_TOKEN`
-- `npm publish` from `packages/create-pi-extension` in the configured workflow file
+## Automated release flow
 
-## First release checklist
+1. Update `package.json` and `CHANGELOG.md` in the same PR.
+2. Merge the PR to `main`.
+3. `auto-release.yml` detects the version change, creates `v<version>` and a GitHub Release, then dispatches `publish.yml`.
+4. `publish.yml` validates and publishes the root package with provenance.
 
-- [ ] Root `package.json` version is final (synced into `create-pi-extension` on publish)
-- [ ] `packages/create-pi-extension/package.json` name is `create-pi-extension`
-- [ ] `repository.url` points to the real GitHub repository
-- [ ] npm Trusted Publisher targets `create-pi-extension` + `publish.yml`
-- [ ] `npm run ci` passes
-- [ ] `npm pack --dry-run` in `packages/create-pi-extension` contains `template/`
-- [ ] CHANGELOG.md has the release date
+Reruns skip versions already present on npm.

package/package.json

@@ -1,56 +1,57 @@
-{
-  "name": "pi-short-links",
-  "version": "0.1.0",
-  "description": "Shorten long URLs and file paths in Pi assistant output so OSC 8 / click targets fit the pane width.",
-  "type": "module",
-  "license": "MIT",
-  "author": "eiei114",
-  "keywords": [
-    "pi-package",
-    "pi",
-    "pi-extension",
-    "osc8",
-    "hyperlink",
-    "typescript"
-  ],
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/eiei114/pi-short-links.git"
-  },
-  "bugs": {
-    "url": "https://github.com/eiei114/pi-short-links/issues"
-  },
-  "homepage": "https://github.com/eiei114/pi-short-links#readme",
-  "files": [
-    "extensions/",
-    "lib/",
-    "docs/",
-    "README.md",
-    "LICENSE",
-    "CHANGELOG.md"
-  ],
-  "scripts": {
-    "typecheck": "tsc --noEmit",
-    "test": "node --test tests/shorten.test.mjs",
-    "pack:check": "npm pack --dry-run",
-    "ci": "npm run typecheck && npm test && npm run pack:check"
-  },
-  "pi": {
-    "extensions": [
-      "./extensions/short-links.ts"
-    ]
-  },
-  "publishConfig": {
-    "access": "public"
-  },
-  "peerDependencies": {
-    "@earendil-works/pi-coding-agent": "*",
-    "@earendil-works/pi-tui": "*"
-  },
-  "devDependencies": {
-    "@earendil-works/pi-coding-agent": "^0.84.1",
-    "@earendil-works/pi-tui": "^0.84.1",
-    "@types/node": "^26.0.0",
-    "typescript": "^7.0.2"
-  }
-}
+{
+  "name": "pi-short-links",
+  "version": "0.2.0",
+  "description": "Shorten long URLs and file paths in Pi assistant output so OSC 8 / click targets fit the pane width.",
+  "type": "module",
+  "license": "MIT",
+  "author": "eiei114",
+  "keywords": [
+    "pi-package",
+    "pi",
+    "pi-extension",
+    "osc8",
+    "hyperlink",
+    "typescript"
+  ],
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/eiei114/pi-short-links.git"
+  },
+  "bugs": {
+    "url": "https://github.com/eiei114/pi-short-links/issues"
+  },
+  "homepage": "https://github.com/eiei114/pi-short-links#readme",
+  "files": [
+    "extensions/",
+    "lib/",
+    "docs/",
+    "README.md",
+    "LICENSE",
+    "CHANGELOG.md"
+  ],
+  "scripts": {
+    "typecheck": "tsc --noEmit",
+    "test": "node --test tests/*.test.mjs",
+    "pack:check": "npm pack --dry-run",
+    "ci": "npm run typecheck && npm test && npm run publish:guard && npm run pack:check",
+    "publish:guard": "node scripts/check-no-npm-token.mjs"
+  },
+  "pi": {
+    "extensions": [
+      "./extensions/short-links.ts"
+    ]
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "peerDependencies": {
+    "@earendil-works/pi-coding-agent": "*",
+    "@earendil-works/pi-tui": "*"
+  },
+  "devDependencies": {
+    "@earendil-works/pi-coding-agent": "^0.84.1",
+    "@earendil-works/pi-tui": "^0.84.1",
+    "@types/node": "^26.0.0",
+    "typescript": "^7.0.2"
+  }
+}

package/docs/examples.md

@@ -1,134 +0,0 @@
-# Examples
-
-This template ships examples for each Pi package resource type and several extension API patterns.
-
-These source files (`extensions/`, `skills/`, `prompts/`, `themes/`) are the **single source of truth**:
-the `sync:template` script copies them into the `create-pi-extension` CLI bundle before publish.
-To update what the CLI generates, edit these files and re-run `bun run sync:template`.
-Scaffold a new project to get a copy of the latest examples:
-
-```bash
-bunx create-pi-extension my-pi-package
-```
-
-Then try the examples in your scaffolded project with `pi -e .`.
-
-For a full walkthrough, see the [README](../README.md).
-
-For maintainers, see [`docs/template-sync-checklist.md`](template-sync-checklist.md) for the sync procedure before publish.
-
-## Extension
-
-`extensions/hello.ts` registers:
-
-- `/template-hello`
-- `/template-status` (TUI-only custom entry via `appendEntry` + `registerEntryRenderer`)
-- session, turn, and tool lifecycle event handlers
-- a small session status indicator
-
-Try it with:
-
-```bash
-pi -e .
-```
-
-Then run:
-
-```txt
-/template-hello YourName
-/template-status Package ready
-?template
-```
-
-## Agent Skill (package manifest)
-
-`skills/example-skill/SKILL.md` demonstrates a minimal Agent Skill. Its
-frontmatter uses the required `name` and `description` fields plus the optional
-`license` field, following the Agent Skills spec that Pi validates against
-(see `docs/skills.md`).
-
-Replace it with your real workflow instructions.
-
-## Agent Skill (extension `resources_discover`)
-
-`extensions/skill-bridge/` contributes `template-skill-bridge` at runtime:
-
-- `index.ts` returns `skillPaths` from the `resources_discover` event
-- `SKILL.md` lives beside the extension entrypoint
-
-Commands:
-
-```txt
-/template-skill-info
-/skill:template-skill-bridge
-```
-
-Use this pattern when a skill should ship with an extension instead of the top-level `skills/` directory.
-
-## Typed custom tool
-
-`extensions/index.ts` registers:
-
-- `/template-info`
-- `template_greet` custom tool
-
-The tool demonstrates:
-
-- `pi.registerTool()` with TypeBox object parameters
-- a string enum schema via `StringEnum`
-- `prepareArguments()` for legacy argument compatibility before schema validation
-- custom `renderCall` / `renderResult` rendering
-- shared logic imported from `lib/greeting.ts`
-- TUI `renderCall` / `renderResult` via `Text`
-
-## TUI component composition
-
-`extensions/tui-dashboard.ts` demonstrates composing `@earendil-works/pi-tui` primitives:
-
-- `Box` for padded, themed containers
-- `Loader` for spinner-style progress feedback
-- column-aligned tables built with shared `lib/format-table.ts` and rendered via `Text`
-
-Command:
-
-```txt
-/template-dashboard
-```
-
-`pi-tui` does not ship a dedicated `Table` or `Spinner` component; this example uses `Loader` for spinners and a small table formatter for aligned columns.
-
-## Multi-file extension layout
-
-`extensions/package-layout/` demonstrates a subdirectory extension with local modules:
-
-- `lib/config.ts` — typed configuration defaults
-- `lib/stats.ts` — resource metadata helpers
-- imports from package-wide `lib/format-table.ts`
-
-Commands:
-
-```txt
-/template-layout
-/template-layout-clear
-```
-
-## Prompt template
-
-`prompts/example.md` demonstrates a tiny prompt template with one positional
-argument (`/example <topic>`). Pi expands templates with `$1`, `$@`, and
-`${1:-default}` — it does not support Mustache-style `{{var}}` placeholders.
-
-## Theme
-
-`themes/example-theme.json` ships a complete, loadable dark theme as a starting
-point. Pi requires every theme to define all 51 color tokens, so edit the
-palette in place rather than trimming tokens. Remove `themes/` (and the
-`pi.themes` manifest entry) if your package does not ship themes.
-
-## Shared library helpers
-
-| File | Purpose |
-|---|---|
-| `lib/greeting.ts` | Greeting helpers used by `template_greet` |
-| `lib/format-table.ts` | Monospace table formatter for widgets and TUI examples |
-| `lib/config-contract.ts` | Schema-derived runtime config validation with valid/invalid contract tests |

package/docs/github-template.md

@@ -1,63 +0,0 @@
-# GitHub Template Repository
-
-> **Template bootstrap doc.** Use while setting up a new repo from this template. Delete this file or merge any project-specific steps into README / Vault notes once setup is done, unless it still adds maintainer value.
-
-## Recommended development flow
-
-After generating a repo from this template, use this default order:
-
-```txt
-Vault notes -> PRD -> Issues -> implement -> ci/check -> release -> save learnings
-```
-
-In practice:
-
-1. Create Vault notes under `4_Project/<ProjectName>/`.
-2. Add `CONTEXT.md`, `README.md`, `ROADMAP.md`, `Docs/`, `Issues/`, and `Progress/`.
-3. Write the PRD in `Docs/`.
-4. Split approved issue files into `Issues/`.
-5. Implement in the OSS repo created from this template.
-6. Run CI and package checks before release.
-7. Save release notes and follow-up decisions back to the Vault project.
-
-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
-```\n

package/docs/publish-rerun-rollout.md

@@ -1,26 +0,0 @@
-# Publish rerun guard rollout
-
-Template fix: `publish.yml` now checks `https://registry.npmjs.org/<package>/<version>` before `setup-node` configures OIDC auth. Reruns for an already-published version exit green and log `publish intentionally skipped`.
-
-## Why downstream repos need this
-
-Older template copies used `npm view` after `setup-node` with `registry-url`. With npm Trusted Publishing, authenticated metadata reads can return `404` even when the version exists, so the guard misses and `npm publish` fails with `403 Forbidden - You cannot publish over the previously published versions`.
-
-## Rollout list
-
-Apply the updated `publish.yml` skip step (or merge the latest `pi-extension-template` workflow) in:
-
-- [ ] `pi-startup-picker` — failed run `28704558891` on `v0.2.2`
-- [ ] `pi-git-delegate` — failed run `28704535034` on `0.2.2`
-- [ ] `pi-baton` — failed run `28704529442` on `0.7.2`
-- [ ] `pi-widget-host` — failed run `28704568448` on `0.3.3`
-- [ ] `pi-widget-core` — failed run `28704566953` on `0.1.2`
-- [ ] `pi-handoff-clipboard` — failed run `28704536299`
-- [ ] `pi-scheduled-router` — failed run `28704552385`
-
-## Verification after rollout
-
-1. Open Actions → `Publish to npm`.
-2. Run `workflow_dispatch` on the tag for a version that is already on npm.
-3. Confirm logs contain `publish intentionally skipped`.
-4. Confirm the run is green and `npm publish` did not run.

package/docs/repository-settings.md

@@ -1,43 +0,0 @@
-# Repository Settings
-
-> **Template bootstrap doc.** Use while configuring GitHub About, topics, and branch protection after generating a repo. Delete this file or merge needed settings into README once setup is done, unless it still adds maintainer value.
-
-Use this file after creating a real repository from the template.
-
-## GitHub About
-
-Suggested fields:
-
-- Description: one-line pitch for the Pi package
-- Website: npm package URL or project docs URL
-- Topics:
-  - `pi`
-  - `pi-package`
-  - `agent-skill`
-  - `typescript`
-
-## Template mode
-
-If this repository itself should be reusable as a template:
-
-```txt
-Settings → General → Template repository
-```
-
-## 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