@anthodev/pi-tools-style 0.1.3 → 0.1.4

package/README.md

@@ -25,7 +25,7 @@ Built-in tools, MCP integrations, AFT, and third-party extensions keep control o
 
 ## Installation
 
-The current release targets Pi `0.84.x` and requires Node.js 22 or newer.2
+This checkout targets Pi `1.0.x`, verified with `1.0.0`, and requires Node.js `>=22.19.0`.
 
 To install it, use the following command:
 
@@ -135,7 +135,7 @@ Borders resolve their color from the active Pi theme on every render. Switching
 
 ## How it works
 
-Pi `0.84.x` does not expose public render middleware around `ToolExecutionComponent` and `BashExecutionComponent`. `pi-tools-style` therefore installs a narrow wrapper around their existing `render()` methods.
+Pi `1.0.x` does not expose public, composable render middleware covering both tools and direct shell commands. `pi-tools-style` therefore installs a narrow wrapper around the existing `render()` methods of `ToolExecutionComponent` and `BashExecutionComponent`.
 
 The wrapper asks the previous renderer to draw at the frame's inner width, removes only paired outer horizontal rules, and then adds ANSI-aware chrome. It does not call `pi.registerTool()`, replace tool definitions, or intercept execution.
 
@@ -143,12 +143,13 @@ Configuration and animation state live behind `Symbol.for()` keys. Reloading upd
 
 ## Compatibility and limits
 
-- Pi `0.84.x` is the supported target. Private TUI internals may change in later releases.
+- Pi `1.0.x` is the supported target, verified with `1.0.0` in both `fullscreen` and `regular` TUI modes. Pi `0.84.x` is no longer a supported target. Private TUI internals may change in later releases.
 - The render wrapper is necessarily unsupported until Pi exposes public, composable render middleware.
 - Kitty, iTerm2, and Sixel image output remains unboxed by design.
 - Slash commands remain outside the current scope because their transcript output has no uniform component.
 - Another extension can replace this wrapper if it overwrites component rendering without composing with the previous renderer.
 - Unsupported renderer shapes fail open rather than affecting tool execution.
+- Frame characters remain selectable text and are included in copied output. Excluding decorative cells would require Pi/TUI integration for fullscreen selection; no portable exclusion path has been identified for native terminal selection in regular mode.
 
 ## Development
 
@@ -160,10 +161,36 @@ npm run check
 npm pack --dry-run --json
 ```
 
-`npm run check` runs TypeScript validation and the Vitest suite. Tests cover frame width, ANSI output, terminal images, native and AFT rule removal, category colors, icon modes, persisted settings, spinner lifecycle, real `ToolExecutionComponent` integration, render composition, reload idempotence, fail-open behavior, and the no-`registerTool()` contract.
+`npm run check` runs TypeScript validation and the Vitest suite. Tests cover frame width, ANSI output, terminal images, native and AFT rule removal, category colors, icon modes, persisted settings, spinner lifecycle, real `ToolExecutionComponent` and `BashExecutionComponent` integration, third-party renderer composition, decorator toggling and reinstallation, reload idempotence, fail-open behavior, and the no-`registerTool()` contract.
+
+Release-note tests cover exact version sections, Markdown fences and whitespace, duplicate or missing sections, tagged Git snapshots, annotated and lightweight tags, and CLI failure paths.
 
 `--legacy-peer-deps` avoids an npm 10.9.8 Arborist failure observed while resolving the development peer dependency graph.
 
+## Releases
+
+Releases are triggered only by stable `vX.Y.Z` tag pushes. `.github/workflows/publish.yml` validates the tagged commit on Node.js `22.19.0` and `24.x`, packages one npm tarball, publishes it to npm, then creates the GitHub release with that tarball and `SHA256SUMS` as assets.
+
+`CHANGELOG.md` is the source of release notes. CI extracts the exact version section from the tagged commit, not the working tree, and preserves its summary, lists, links, and Markdown. Invalid tags, mismatched revisions, or missing, empty, or duplicate sections fail before publication. CI neither generates notes from commit subjects nor edits the changelog.
+
+To prepare a release:
+
+1. Update `package.json` and regenerate `package-lock.json`. Move the release entries from `Unreleased` into a dated `## [X.Y.Z] - YYYY-MM-DD` section, preserving verified commit or PR references and the full changelog comparison link.
+2. Run `PI_CODING_AGENT_DIR="$(mktemp -d)" npm run check` and `npm run pack:check`.
+3. Seal and push the release-preparation commit on `develop`. With jj, use the sealed commit's explicit SHA, never an empty working-copy `@`.
+4. Set `VERSION` to the prepared package version and `RELEASE_SHA` to that commit's full SHA, then validate the notes before pushing the tag:
+
+```bash
+jj tag set "v${VERSION}" -r "$RELEASE_SHA"
+notes="$(mktemp)"
+node scripts/generate-release-notes.ts "v${VERSION}" "$RELEASE_SHA" "$notes"
+jj git push --tag "v${VERSION}"
+```
+
+The workflow requires the tag to match the package and lockfile versions and to belong to `develop`. npm publication uses OIDC Trusted Publishing on a GitHub-hosted runner with the protected `npm` environment. Keep the `publish.yml` filename and environment aligned with the trusted publisher configuration. Concurrent release tags are serialized.
+
+Publication is not an idempotent update. An already-published npm version or existing GitHub release makes a rerun fail. npm publication precedes GitHub release creation, so a failure in the latter can leave the package already published. Do not move a published tag or delete a release to make a rerun succeed.
+
 ## License
 
 MIT

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@anthodev/pi-tools-style",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "description": "Presentation-only boxes for Pi tool calls and shell commands",
   "keywords": [
     "pi-package",
@@ -40,12 +40,12 @@
     "access": "public"
   },
   "peerDependencies": {
-    "@earendil-works/pi-coding-agent": "0.84.x",
-    "@earendil-works/pi-tui": "0.84.x"
+    "@earendil-works/pi-coding-agent": "1.0.x",
+    "@earendil-works/pi-tui": "1.0.x"
   },
   "devDependencies": {
-    "@earendil-works/pi-coding-agent": "0.84.1",
-    "@earendil-works/pi-tui": "0.84.1",
+    "@earendil-works/pi-coding-agent": "1.0.0",
+    "@earendil-works/pi-tui": "1.0.0",
     "@types/node": "24.12.0",
     "typescript": "5.9.3",
     "vitest": "4.1.9"