@pzy560117/codex-harness 0.1.0 → 0.1.1

package/package-source/docs/codex-harness-engineering/templates/package-assets/skills/celery-tasks/SKILL.md

@@ -0,0 +1,95 @@
+---
+name: celery-tasks
+description: Celery 异步任务开发指南
+---
+
+# Celery 异步任务开发指南
+
+## 配置位置
+
+```
+WHartTest_Django/
+├── wharttest_django/celery.py  # Celery 应用配置
+├── requirements/tasks.py        # 需求处理任务
+└── testcases/tasks.py           # 测试执行任务
+```
+
+## 任务定义
+
+```python
+from celery import shared_task
+from celery.utils.log import get_task_logger
+
+logger = get_task_logger(__name__)
+
+@shared_task(bind=True, max_retries=3)
+def my_async_task(self, param1, param2):
+    """
+    异步任务说明
+    
+    Args:
+        param1: 参数1说明
+        param2: 参数2说明
+    """
+    try:
+        # 任务逻辑
+        result = process_data(param1, param2)
+        return result
+    except Exception as exc:
+        logger.error(f"Task failed: {exc}")
+        raise self.retry(exc=exc, countdown=60)
+```
+
+## 任务调用
+
+```python
+# 异步调用
+result = my_async_task.delay(param1, param2)
+
+# 带参数调用
+result = my_async_task.apply_async(
+    args=[param1, param2],
+    countdown=10,  # 延迟10秒执行
+    expires=3600   # 1小时后过期
+)
+
+# 获取结果
+if result.ready():
+    data = result.get()
+```
+
+## 定时任务 (Beat)
+
+```python
+# wharttest_django/celery.py
+app.conf.beat_schedule = {
+    'cleanup-every-hour': {
+        'task': 'myapp.tasks.cleanup_task',
+        'schedule': crontab(minute=0),
+    },
+}
+```
+
+## Docker 环境
+
+```bash
+# 查看 Celery 日志
+docker-compose logs -f backend | grep celery
+
+# 手动触发任务
+docker-compose exec backend python -c "
+from requirements.tasks import my_task
+my_task.delay(1, 2)
+"
+```
+
+## 监控
+
+```bash
+# 查看活跃任务
+docker-compose exec backend celery -A wharttest_django inspect active
+
+# 查看注册的任务
+docker-compose exec backend celery -A wharttest_django inspect registered
+```
+

package/package-source/docs/codex-harness-engineering/templates/package-assets/skills/checkpoint/SKILL.md

@@ -0,0 +1,79 @@
+---
+name: checkpoint
+description: Workflow skill from checkpoint.md
+---
+
+# Checkpoint Command
+
+Create or verify a checkpoint in your workflow.
+
+## Usage
+
+`/checkpoint [create|verify|list] [name]`
+
+## Create Checkpoint
+
+When creating a checkpoint:
+
+1. Run `/verify quick` to ensure current state is clean
+2. Create a git stash or commit with checkpoint name
+3. Log checkpoint to `.claude/checkpoints.log`:
+
+```bash
+echo "$(date +%Y-%m-%d-%H:%M) | $CHECKPOINT_NAME | $(git rev-parse --short HEAD)" >> .claude/checkpoints.log
+```
+
+4. Report checkpoint created
+
+## Verify Checkpoint
+
+When verifying against a checkpoint:
+
+1. Read checkpoint from log
+2. Compare current state to checkpoint:
+   - Files added since checkpoint
+   - Files modified since checkpoint
+   - Test pass rate now vs then
+   - Coverage now vs then
+
+3. Report:
+```
+CHECKPOINT COMPARISON: $NAME
+============================
+Files changed: X
+Tests: +Y passed / -Z failed
+Coverage: +X% / -Y%
+Build: [PASS/FAIL]
+```
+
+## List Checkpoints
+
+Show all checkpoints with:
+- Name
+- Timestamp
+- Git SHA
+- Status (current, behind, ahead)
+
+## Workflow
+
+Typical checkpoint flow:
+
+```
+[Start] --> /checkpoint create "feature-start"
+   |
+[Implement] --> /checkpoint create "core-done"
+   |
+[Test] --> /checkpoint verify "core-done"
+   |
+[Refactor] --> /checkpoint create "refactor-done"
+   |
+[PR] --> /checkpoint verify "feature-start"
+```
+
+## Arguments
+
+$ARGUMENTS:
+- `create <name>` - Create named checkpoint
+- `verify <name>` - Verify against named checkpoint
+- `list` - Show all checkpoints
+- `clear` - Remove old checkpoints (keeps last 5)

package/package-source/docs/codex-harness-engineering/templates/package-assets/skills/cicd/SKILL.md

@@ -0,0 +1,167 @@
+---
+name: cicd
+description: CI/CD 指南
+---
+
+# CI/CD 指南
+
+## 触发条件
+流水线、GitHub Actions、自动化部署、持续集成
+
+## GitHub Actions 基础模板
+
+```yaml
+# .github/workflows/ci.yml
+name: CI
+
+on:
+  push:
+    branches: [main, develop]
+  pull_request:
+    branches: [main]
+
+jobs:
+  build-and-test:
+    runs-on: ubuntu-latest
+    
+    steps:
+      - uses: actions/checkout@v4
+      
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          cache: 'npm'
+      
+      - name: Install dependencies
+        run: npm ci
+      
+      - name: Lint
+        run: npm run lint
+      
+      - name: Type check
+        run: npm run type-check
+      
+      - name: Test
+        run: npm run test -- --coverage
+      
+      - name: Build
+        run: npm run build
+```
+
+## 部署流水线
+
+```yaml
+# .github/workflows/deploy.yml
+name: Deploy
+
+on:
+  push:
+    branches: [main]
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    environment: production
+    
+    steps:
+      - uses: actions/checkout@v4
+      
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          cache: 'npm'
+      
+      - name: Install and Build
+        run: |
+          npm ci
+          npm run build
+      
+      - name: Deploy to Server
+        uses: appleboy/ssh-action@v1
+        with:
+          host: ${{ secrets.SERVER_HOST }}
+          username: ${{ secrets.SERVER_USER }}
+          key: ${{ secrets.SSH_PRIVATE_KEY }}
+          script: |
+            cd /var/www/app
+            git pull origin main
+            npm ci --production
+            pm2 restart app
+```
+
+## Docker 构建发布
+
+```yaml
+name: Docker Build
+
+on:
+  push:
+    tags: ['v*']
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    
+    steps:
+      - uses: actions/checkout@v4
+      
+      - name: Login to Registry
+        uses: docker/login-action@v3
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+      
+      - name: Build and Push
+        uses: docker/build-push-action@v5
+        with:
+          context: .
+          push: true
+          tags: |
+            ghcr.io/${{ github.repository }}:${{ github.ref_name }}
+            ghcr.io/${{ github.repository }}:latest
+```
+
+## 缓存优化
+
+```yaml
+- name: Cache node modules
+  uses: actions/cache@v4
+  with:
+    path: ~/.npm
+    key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
+    restore-keys: |
+      ${{ runner.os }}-node-
+```
+
+## 环境变量和密钥
+
+```yaml
+env:
+  NODE_ENV: production
+  API_URL: ${{ secrets.API_URL }}
+
+# 在 Settings > Secrets and variables > Actions 中配置
+```
+
+## 条件执行
+
+```yaml
+- name: Deploy
+  if: github.ref == 'refs/heads/main' && github.event_name == 'push'
+  run: npm run deploy
+
+- name: Skip CI
+  if: contains(github.event.head_commit.message, '[skip ci]')
+  run: echo "Skipping CI"
+```
+
+## 最佳实践
+- 使用 `npm ci` 而非 `npm install`
+- 缓存依赖加速构建
+- 敏感信息使用 Secrets
+- PR 和 main 分支使用不同流水线
+- 部署前确保所有测试通过
+

package/package-source/docs/codex-harness-engineering/templates/package-assets/skills/claude-openrouter-clash-debug/SKILL.md

@@ -0,0 +1,100 @@
+---
+name: claude-openrouter-clash-debug
+description: Diagnose Claude Code failures on Windows when OpenRouter, Clash Verge, and a local Hysteria/SOCKS node disagree about the real egress region or auth path. Use when Claude Code returns `403 This model is not available in your region`, when `ANTHROPIC_BASE_URL` points to OpenRouter, when a node label says Japan but external services still see Hong Kong or another region, or when `openrouter.ai`, `anthropic.com`, and `claude.ai` need explicit Clash routing and validation.
+---
+
+# Claude OpenRouter Clash Debug
+
+## Overview
+
+Use this skill to debug the full Claude Code -> OpenRouter -> Clash Verge -> local Hysteria route on this Windows machine.
+Prefer the bundled scripts for repeated checks; use the reference playbook when you need the exact files, commands, and the known-good 2026-05-03 fix.
+
+## Quick Start
+
+1. Run the diagnostic script:
+
+```powershell
+powershell -ExecutionPolicy Bypass -File .\.agents\skills\claude-openrouter-clash-debug\scripts\diagnose-openrouter-route.ps1
+```
+
+2. If the output says `openrouter.ai` is missing an explicit Clash rule, add it:
+
+```powershell
+powershell -ExecutionPolicy Bypass -File .\.agents\skills\claude-openrouter-clash-debug\scripts\ensure-openrouter-rule.ps1 -GroupName AI-GitHub-HY2 -RestartMihomo
+```
+
+3. Re-run the diagnostic script.
+
+4. Confirm Claude Code itself works:
+
+```powershell
+claude -p "Reply with ok." --output-format json
+```
+
+## Workflow
+
+### 1. Validate Claude/OpenRouter auth mapping
+
+- Read `C:\Users\pzy666\.claude\settings.json`.
+- When `ANTHROPIC_BASE_URL` is `https://openrouter.ai/api`, the OpenRouter key should live in `ANTHROPIC_AUTH_TOKEN`.
+- Blank `ANTHROPIC_API_KEY` for this path. If the key remains there, Claude Code often stays on the wrong auth mode.
+- Check `claude auth status` before changing network rules.
+
+### 2. Compare the three egress layers
+
+- Direct or TUN egress: what the machine exposes by default.
+- Clash mixed-port egress: what flows through `127.0.0.1:7897`.
+- Dedicated Hysteria SOCKS egress: what the JP node at `127.0.0.1:1082` exposes.
+- If the dedicated SOCKS node is `JP` but the mixed port or default path is `HK`, the server is fine and Clash routing is the likely problem.
+
+### 3. Inspect Clash group and rule selection
+
+- Find the group used by `openai.com` or the intended AI traffic.
+- In this machine's verified case, `openai.com` routes through `AI-GitHub-HY2`.
+- If `openrouter.ai` has no explicit rule, it will usually fall through to `MATCH`.
+- Read the selected groups in `profiles.yaml` before changing anything.
+
+### 4. Apply the narrow fix first
+
+- Update the rules template and the active generated config together:
+  - `C:\Users\pzy666\AppData\Roaming\io.github.clash-verge-rev.clash-verge-rev\profiles\rPQ84LOFBWXy.yaml`
+  - `C:\Users\pzy666\AppData\Roaming\io.github.clash-verge-rev.clash-verge-rev\clash-verge.yaml`
+- Add:
+
+```text
+DOMAIN-SUFFIX,openrouter.ai,<target-group>
+```
+
+- Prefer reusing the same group that already carries `openai.com`.
+- Reload or restart `verge-mihomo` after the edit.
+
+### 5. Validate the actual OpenRouter path
+
+- Probe `https://openrouter.ai/api/v1/chat/completions`.
+- A healthy fix changes the response from `403 region` to `200 OK`.
+- A Japan POP often shows `CF-RAY: ...-NRT` after the fix, but trust the status code first.
+- Only after the API probe succeeds should you spend Claude Code tokens on `claude -p`.
+
+## Resources
+
+- `scripts/diagnose-openrouter-route.ps1`
+  - Reads Claude/OpenRouter settings.
+  - Compares direct, Clash mixed-port, and dedicated SOCKS geolocation.
+  - Checks whether `openrouter.ai` has an explicit rule.
+  - Probes OpenRouter through Clash mixed-port and the dedicated SOCKS node.
+
+- `scripts/ensure-openrouter-rule.ps1`
+  - Adds `DOMAIN-SUFFIX,openrouter.ai,<group>` to the rules template and active generated config.
+  - Makes timestamped backups before edits.
+  - Can restart `verge-mihomo` in place.
+
+- `references/windows-openrouter-clash-playbook.md`
+  - Contains the verified 2026-05-03 incident, machine paths, command checklist, and expected results.
+
+## Guardrails
+
+- Back up `settings.json`, `rPQ84LOFBWXy.yaml`, and `clash-verge.yaml` before edits.
+- Do not trust node labels such as `jp`; trust GeoIP and API probes.
+- Do not widen the default `MATCH` group before trying the narrow `openrouter.ai` rule.
+- If `claude auth status` is still in API key mode after switching to OpenRouter, fix auth mapping before changing proxy groups.

package/package-source/docs/codex-harness-engineering/templates/package-assets/skills/claude-openrouter-clash-debug/references/windows-openrouter-clash-playbook.md

@@ -0,0 +1,94 @@
+# Windows Claude OpenRouter Clash Playbook
+
+## Verified Incident
+
+Date: `2026-05-03`
+
+Symptom:
+
+```text
+Please run /login · API Error: 403
+{"error":{"message":"This model is not available in your region.","code":403}}
+```
+
+What was true on this machine:
+
+- `C:\Users\pzy666\.claude\settings.json` pointed `ANTHROPIC_BASE_URL` to OpenRouter.
+- The OpenRouter key initially lived in `ANTHROPIC_API_KEY` instead of `ANTHROPIC_AUTH_TOKEN`.
+- The dedicated Hysteria node at `127.0.0.1:1082` exited in `JP` as `207.148.115.43`.
+- The generic Clash mixed-port path at `127.0.0.1:7897` still exited in `HK` as `192.142.4.97`.
+- `anthropic.com` and `claude.ai` already had explicit rules, but `openrouter.ai` did not.
+- `openrouter.ai` therefore fell through to `MATCH,狗狗加速.com`, whose selected group was a Hong Kong node.
+
+## Known-Good Fix
+
+1. In `C:\Users\pzy666\.claude\settings.json`:
+   - Keep `ANTHROPIC_BASE_URL=https://openrouter.ai/api`
+   - Move the OpenRouter key to `ANTHROPIC_AUTH_TOKEN`
+   - Blank `ANTHROPIC_API_KEY`
+2. Add `DOMAIN-SUFFIX,openrouter.ai,AI-GitHub-HY2` to:
+   - `C:\Users\pzy666\AppData\Roaming\io.github.clash-verge-rev.clash-verge-rev\profiles\rPQ84LOFBWXy.yaml`
+   - `C:\Users\pzy666\AppData\Roaming\io.github.clash-verge-rev.clash-verge-rev\clash-verge.yaml`
+3. Restart `verge-mihomo`
+4. Re-probe OpenRouter and then run `claude -p`
+
+Expected result after the fix:
+
+- OpenRouter returns `200 OK`
+- `CF-RAY` often ends with `NRT`
+- `claude -p "Reply with ok." --output-format json` succeeds
+
+## Important Paths
+
+- Claude settings:
+  - `C:\Users\pzy666\.claude\settings.json`
+- Clash Verge state:
+  - `C:\Users\pzy666\AppData\Roaming\io.github.clash-verge-rev.clash-verge-rev\profiles.yaml`
+  - `C:\Users\pzy666\AppData\Roaming\io.github.clash-verge-rev.clash-verge-rev\profiles\rPQ84LOFBWXy.yaml`
+  - `C:\Users\pzy666\AppData\Roaming\io.github.clash-verge-rev.clash-verge-rev\clash-verge.yaml`
+- Local Hysteria JP client:
+  - `C:\Users\pzy666\AppData\Roaming\hysteria\config-jp.yaml`
+
+## Command Checklist
+
+Inspect Claude auth mode:
+
+```powershell
+claude auth status
+```
+
+Inspect direct or TUN egress:
+
+```powershell
+curl.exe -s https://ipinfo.io/json
+```
+
+Inspect Clash mixed-port egress:
+
+```powershell
+curl.exe -s --proxy http://127.0.0.1:7897 https://ipinfo.io/json
+```
+
+Inspect dedicated JP Hysteria egress:
+
+```powershell
+curl.exe -s --socks5-hostname 127.0.0.1:1082 https://ipinfo.io/json
+```
+
+Probe OpenRouter through Clash mixed-port:
+
+```powershell
+curl.exe -sS --proxy http://127.0.0.1:7897 -D - -X POST https://openrouter.ai/api/v1/chat/completions ...
+```
+
+Probe OpenRouter through the dedicated JP Hysteria SOCKS node:
+
+```powershell
+curl.exe -sS --socks5-hostname 127.0.0.1:1082 -D - -X POST https://openrouter.ai/api/v1/chat/completions ...
+```
+
+## Interpretation Rules
+
+- If the JP SOCKS node shows `JP` but the generic mixed-port path shows `HK`, the server is not the problem; the route selection is.
+- If `openrouter.ai` has no explicit rule, expect it to fall through to the default group.
+- If OpenRouter succeeds through the dedicated JP SOCKS node but fails through the mixed-port path, fix the Clash rule before changing providers or rotating keys.