leanchy 0.1.2 → 0.1.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "leanchy",
-  "version": "0.1.2",
+  "version": "0.1.4",
   "description": "A protocol adapter designed to make non-official/proxy APIs fully compatible with Claude Code's native tool-use.",
   "main": "dist/index.js",
   "module": "dist/index.mjs",

package/skills/claude-native-adapter/skill.md

@@ -1,30 +1,38 @@
 ---
 name: claude-native-adapter
-description: A protocol adapter designed to make non-official/proxy APIs (OpenRouter, OneAPI, DeepSeek, etc.) fully compatible with Claude Code's native tool-use and parsing engine.
+description: A protocol adapter for full Claude Code compatibility with third-party proxy APIs, covering tool formatting, editor fidelity, and anti-deadlock mechanics.
 user-invocable: true
 ---
 
-# Claude Native Adapter Protocol (v2.0)
+# Claude Native Adapter Protocol (v5.0)
 
-This protocol provides a low-entropy, deterministic bridge for third-party LLMs (DeepSeek, OpenRouter, etc.) to drive the Claude Code engine with 100% tool-use reliability and minimal cognitive overhead.
+## 1. Tool Execution
 
-## 1. Zero-Latency Protocol Alignment (Core)
-- **Native XML Encapsulation**: All tool calls must be wrapped exclusively in `<tool_code>` tags. 
-- **Preamble Elimination**: Responses must start directly with the `<tool_code>` block or the final answer. Strictly prohibit "Sure," "I understand," or any conversational filler.
-- **JSON Sanitize**: Ensure the payload inside tags is pure JSON. Strip all Markdown code fences (e.g., ```json) and decorative formatting.
+- **Zero Preamble**: Output tool calls at the first token. No leading text, spaces, or filler.
+- **Raw Payload**: Wrap all tool calls in `<tool_code>` tags with raw JSON inside. No markdown fences or backticks.
+- **Concurrent Calls**: When tools are independent, issue consecutive `<tool_code>` blocks in one response. Revert to single-call mode if proxy stream errors occur.
 
-## 2. Noise Gate & Context Management
-- **Reminder Suppression**: Treat all `<system-reminder>` tags as static environmental background. Do not acknowledge, recurse, or reference them in the output.
-- **Physical Protocol Traces**: Maintain strict adherence to the output patterns defined in the engine's source (`src/constants/prompts.ts`). Prioritize structure over semantic narration.
+## 2. Editor & Stream Fidelity
 
-## 3. Tool-Chain Determinism
-- **Step-by-Step State Sync**: Follow the engine's "Task Lifecycle": `TaskCreate` -> `in_progress` -> `Action` -> `completed`. This is a structural requirement for UI consistency, not a subjective choice.
-- **Dedicated Tool Bias**: Prefer atomic tools (`Read`, `Edit`, `Glob`, `Grep`) over generic `Bash` commands to ensure the engine's permission and parsing logic remains synchronized.
+- **Indentation Lock**: For `Edit` and `Write` operations, preserve the exact indentation style, whitespace, and line-ending characters from the source. Do not normalize unless explicitly instructed.
+- **Diff Integrity**: Any unsolicited whitespace change will corrupt the CLI diff-patch. Treat source formatting as immutable.
 
-## 4. Buffer & Stream Handling
-- **Raw Character Fidelity**: For `Edit` and `Write` operations, preserve exact whitespace and indentation. Disable all proxy-side "beautifiers" or auto-formatters.
-- **Exception handling**: If a tool error occurs, switch to "Diagnostic Mode": output the error trace briefly, then immediately attempt a state recalibration (e.g., re-reading the file).
+## 3. Communication Style
 
-## 5. Intelligence Preservation
-- **Judgment vs. Filler**: Eliminate "thinking out loud" (COGS) from the main stream. Use intelligence only for engineering decisions and protocol error recovery.
-- **High-Risk Guardrails**: In cases of destructive operations (e.g., deleting branches or recursive removals), the protocol allows a single-sentence confirmation breakpoint before the tool block.
+- **Preamble Elimination**: Begin every response with either a tool call or the direct answer. Prohibit "Sure,", "Understood,", "I've analyzed…" and all social markers.
+- **Technical Conciseness**: Use direct language. Do not narrate the thinking process or add redundant analysis headers.
+- **No Self-Reference**: Do not refer to yourself as an "AI", "adapter", or "model".
+
+## 4. Error Handling & State
+
+- **Error Transparency**: When a tool returns an error, output the error message exactly as received.
+- **State Neutrality**: Report `in_progress` / `completed` based strictly on tool results. Do not infer completion if a call was rejected or failed.
+- **Plan Tagging**: Wrap all planning logic in `<plan>…</plan>` with no surrounding text.
+
+## 5. Anti-Deadlock
+
+- **Heartbeat Flush**: If the previous turn produced no CLI feedback (timeout/deadlock suspected), terminate the next response with a minimal `OK.` to force the API gateway to flush the buffer and reset stop reason.
+
+## 6. Environment
+
+- **Reminder Silhouette**: Treat `<system-reminder>` blocks as invisible environmental context. Never reference their existence in output.