@lenylvt/pi-coding-agent 0.64.0

package/docs/prompt-templates.md

@@ -0,0 +1,67 @@
+> pi can create prompt templates. Ask it to build one for your workflow.
+
+# Prompt Templates
+
+Prompt templates are Markdown snippets that expand into full prompts. Type `/name` in the editor to invoke a template, where `name` is the filename without `.md`.
+
+## Locations
+
+Pi loads prompt templates from:
+
+- Global: `~/.pi/agent/prompts/*.md`
+- Project: `.pi/prompts/*.md`
+- Packages: `prompts/` directories or `pi.prompts` entries in `package.json`
+- Settings: `prompts` array with files or directories
+- CLI: `--prompt-template <path>` (repeatable)
+
+Disable discovery with `--no-prompt-templates`.
+
+## Format
+
+```markdown
+---
+description: Review staged git changes
+---
+Review the staged changes (`git diff --cached`). Focus on:
+- Bugs and logic errors
+- Security issues
+- Error handling gaps
+```
+
+- The filename becomes the command name. `review.md` becomes `/review`.
+- `description` is optional. If missing, the first non-empty line is used.
+
+## Usage
+
+Type `/` followed by the template name in the editor. Autocomplete shows available templates with descriptions.
+
+```
+/review                           # Expands review.md
+/component Button                 # Expands with argument
+/component Button "click handler" # Multiple arguments
+```
+
+## Arguments
+
+Templates support positional arguments and simple slicing:
+
+- `$1`, `$2`, ... positional args
+- `$@` or `$ARGUMENTS` for all args joined
+- `${@:N}` for args from the Nth position (1-indexed)
+- `${@:N:L}` for `L` args starting at N
+
+Example:
+
+```markdown
+---
+description: Create a component
+---
+Create a React component named $1 with features: $@
+```
+
+Usage: `/component Button "onClick handler" "disabled support"`
+
+## Loading Rules
+
+- Template discovery in `prompts/` is non-recursive.
+- If you want templates in subdirectories, add them explicitly via `prompts` settings or a package manifest.

package/docs/providers.md

@@ -0,0 +1,98 @@
+# Providers
+
+This fork keeps four built-in providers only:
+
+- `anthropic`
+- `github-copilot`
+- `openai-codex`
+- `openrouter`
+
+Pi resolves credentials from the local auth store, environment variables, or OAuth login depending on the provider.
+
+## OAuth Providers
+
+Use `/login` in interactive mode, or use the standalone login helper:
+
+```bash
+bunx @lenylvt/pi-ai login
+```
+
+Built-in OAuth providers:
+
+- `anthropic`
+- `github-copilot`
+- `openai-codex`
+
+Tokens are stored in `~/.pi/agent/auth.json` and refreshed automatically when supported by the provider.
+
+### Notes
+
+- `anthropic`: supports both OAuth subscription access and `ANTHROPIC_API_KEY`.
+- `github-copilot`: accepts OAuth login or token-based auth through `COPILOT_GITHUB_TOKEN`, `GH_TOKEN`, or `GITHUB_TOKEN`.
+- `openai-codex`: requires ChatGPT Plus or Pro.
+
+## API Key Providers
+
+`openrouter` is API-key only in this fork:
+
+```bash
+export OPENROUTER_API_KEY=...
+pi
+```
+
+`anthropic` also supports direct API key auth:
+
+```bash
+export ANTHROPIC_API_KEY=...
+pi
+```
+
+## Auth File
+
+Credentials are stored in `~/.pi/agent/auth.json`.
+
+Example:
+
+```json
+{
+  "anthropic": { "type": "api_key", "key": "sk-ant-..." },
+  "openrouter": { "type": "api_key", "key": "sk-or-..." }
+}
+```
+
+The file is created with `0600` permissions. Auth file credentials take priority over environment variables.
+
+### Key Resolution
+
+The `key` field supports three formats:
+
+- Shell command:
+  ```json
+  { "type": "api_key", "key": "!security find-generic-password -ws 'anthropic'" }
+  ```
+- Environment variable name:
+  ```json
+  { "type": "api_key", "key": "MY_OPENROUTER_KEY" }
+  ```
+- Literal value:
+  ```json
+  { "type": "api_key", "key": "sk-ant-..." }
+  ```
+
+OAuth credentials are stored in the same file after `/login`.
+
+## Resolution Order
+
+When resolving credentials for a provider:
+
+1. CLI `--api-key`
+2. `auth.json`
+3. Environment variables
+4. Custom provider keys from `models.json`
+
+## Custom Providers
+
+Built-in providers are limited to the four listed above. Custom providers are still possible through:
+
+- [`models.md`](./models.md) for OpenAI-compatible or Anthropic-compatible endpoints
+- [`custom-provider.md`](./custom-provider.md) for extensions that register custom APIs or auth flows

package/docs/release.md

@@ -0,0 +1,40 @@
+# Release
+
+GitLab CI is the only release path for this fork.
+
+## Local Preparation
+
+```bash
+bun run release:patch
+# or
+bun run release:minor
+```
+
+Set an explicit version when needed:
+
+```bash
+bun run release:set -- 0.65.0
+```
+
+Validate the workspace before tagging:
+
+```bash
+bun run release:verify
+```
+
+## GitLab CI/CD
+
+- Every push and merge request runs install, build, and checks.
+- The `publish:packages` job runs only for tags matching `vX.Y.Z`.
+- The job verifies that the tag matches the workspace version before publishing.
+
+## Registry Publishing
+
+Create a masked GitLab CI/CD variable named `NPM_TOKEN`.
+
+The publish job builds, checks, verifies lockstep versions, then publishes only:
+
+- `@lenylvt/pi-ai`
+- `@lenylvt/pi-agent-core`
+- `@lenylvt/pi-tui`
+- `@lenylvt/pi-coding-agent`