@maxiaochao/pi-toolkit 0.2.0 → 0.2.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,3 +1,8 @@
1
+ ## 2026-09-02 - v0.2.1
2
+
3
+ - update global agent instructions for harness-native file editing
4
+ - remove the HTML artifact output preference from the global instructions
5
+
1
6
  ## 2026-09-02 - v0.2.0
2
7
 
3
8
  - bundle the Apache-2.0 `web-browser` skill for Chrome/Chromium CDP automation
package/global/AGENTS.md CHANGED
@@ -100,11 +100,10 @@ After each significant step:
100
100
  2. Does the standard library cover it? Use it.
101
101
  3. Only then: write the minimum code that works.
102
102
 
103
- ---
103
+ ## 9. Use Available Editing Tools
104
104
 
105
+ **Follow the current harness's tool surface; do not assume a shell patch helper exists.**
105
106
 
106
- ## Output Format Preference
107
-
108
- For complex explanations, prefer a runnable HTML artifact over a long Markdown-only response when the content benefits from visual structure or interaction. This includes workflows, code/module relationships, state machines, event/data flows, architecture maps, timelines, comparisons, dashboards, and interactive demonstrations. Keep ordinary prose, short answers, diffs, and focused code reviews in Markdown.
109
-
110
- When using HTML, create a self-contained, responsive artifact in the project's established output location, or `.cache/html/<descriptive-name>.html` when no convention exists. Use semantic HTML, accessible controls, escaped code blocks, and small useful interactions. Return a concise Markdown summary with a clickable local file path; if a preview/server tool is available, start it and return the preview URL only after verifying the page is not blank and its assets load.
107
+ - Use the native file-editing tools exposed by the current environment. In pi, use `edit` for precise replacements and `write` for new files or complete rewrites.
108
+ - Do not run `apply_patch` as a shell command unless `command -v apply_patch` confirms that executable is available.
109
+ - If the harness exposes `apply_patch` as a dedicated tool rather than a command, invoke it only through that tool interface.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@maxiaochao/pi-toolkit",
3
- "version": "0.2.0",
3
+ "version": "0.2.1",
4
4
  "description": "Personal pi coding agent toolkit: /todos, /btw, /cache_export extensions, browser automation, and bundled theme/skills.",
5
5
  "type": "module",
6
6
  "keywords": [