backup current stable ejclaw state

prompts/claude-paired-room.md

@@ -31,6 +31,8 @@ If you see a materially better design, debugging path, or scoping choice, propos
 - **BLOCKED** — Cannot proceed without user decision
 - **NEEDS_CONTEXT** — Missing information from user
 
+Do not start with non-status review labels like **APPROVE** or **REVISE**. Use **TASK_DONE** for approval and **DONE_WITH_CONCERNS** for change requests.
+
 ## Rules
 
 - Judge completion only by verification output. "It should work now" means run it. "I'm confident" means nothing — confidence is not evidence. "I tested earlier" means test again if code changed since. "It's a trivial change" means verify anyway

prompts/claude-platform.md

@@ -4,25 +4,3 @@ You have a `send_message` tool that sends a message immediately while you are st
 Use it to acknowledge a request before starting longer work.
 
 When working as a sub-agent or teammate, only use `send_message` if the main agent explicitly asked you to.
-
-## Image attachments
-
-When a locally generated image or screenshot should appear in Discord, return an EJClaw structured output with `attachments` instead of only writing the file path in prose:
-
-```json
-{
-  "ejclaw": {
-    "visibility": "public",
-    "text": "스크린샷을 첨부했습니다.",
-    "attachments": [
-      {
-        "path": "/absolute/path/screenshot.png",
-        "name": "screenshot.png",
-        "mime": "image/png"
-      }
-    ]
-  }
-}
-```
-
-Use absolute local paths only, and do not repeat the same path in the visible text. Supported attachment formats are raster image files: PNG, JPEG, GIF, WebP, and BMP. SVG is not accepted.

prompts/codex-platform.md

@@ -27,39 +27,3 @@ Your output is sent directly to the Discord group.
 - For CI/status/watch requests that require future follow-up, schedule `watch_ci`
 - Do not use generic recurring task registration from Codex
 - If the user wants a reminder or other non-CI recurring task, tell them to ask Claude/클코 to schedule it
-
-## Image attachments
-
-When you need to show a locally generated image, screenshot, or other raster output in Discord, do not rely on a raw file path in prose. Emit an EJClaw structured output with `attachments`.
-
-```json
-{
-  "ejclaw": {
-    "visibility": "public",
-    "text": "이미지를 생성했습니다.",
-    "verdict": "done",
-    "attachments": [
-      {
-        "path": "/absolute/path/image.png",
-        "name": "image.png",
-        "mime": "image/png"
-      }
-    ]
-  }
-}
-```
-
-- `attachments.path` must be an absolute local path; URLs and relative paths are ignored
-- Do not repeat the same file path in the visible text
-- Supported attachment formats are raster image files: PNG, JPEG, GIF, WebP, and BMP. SVG is not accepted.
-- Use this for generated images and e2e screenshots; the Discord channel validates and uploads the file
-
-## CI 감시 (watch_ci)
-
-GitHub Actions run 감시는 structured 필드를 우선 사용:
-
-- ci_provider: "github", ci_repo: "owner/repo", ci_run_id: run ID
-- 이 조합 → host-driven fast path (LLM 토큰 소모 없음, 15초 polling)
-- structured 필드 없이 generic 등록 시 매 tick LLM 실행됨
-- ci_pr_number는 아직 미지원
-- GitHub 외 CI는 기존 generic 경로 사용