feat(arcrun): implement arcrun MVP — open-source AI workflow engine

Phase 1-5 complete per .agents/specs/u6u-core-mvp/:

**Phase 1 — Cherry-pick & cleanup**
- Create arcrun/ from cypher-executor, credentials, builtins, registry
- Remove 9 InkStone Service Bindings (KBDB, REGISTRY, CLINIC_*, AICEO, MINI_ME)
- Rewrite component-loader: 3-layer (builtin → WASM_BUCKET R2 → error)
- Remove autoPublishMissing.ts, proxy.ts (AICEO), execution-logger.ts (KBDB)
- Clean all KV namespace IDs and InkStone internal URLs from config files

**Phase 2 — contract.yaml completeness**
- Add credentials_required to gmail, google_sheets, telegram, line_notify
- Add config_example to all 21 components with annotated field descriptions

**Phase 3 — Credential injection**
- Add credential-injector.ts: AES-GCM decrypt from CREDENTIALS_KV
- Integrate into GraphExecutor before WASM execution
- Structured errors with repair instructions when credential missing

**Phase 4 — CLI (acr)**
- cli/package.json: arcrun package, bin: acr, deps: commander/js-yaml/chalk/ora
- 8 commands: init, creds push, push, run, validate, parts, list, logs
- Standard mode: writes directly to user's CF KV via CF REST API
- acr init: interactive setup with arcrun.dev API Key registration

**Phase 5 — Open source release prep**
- README.md: 5-minute quickstart, component table, workflow YAML syntax
- CONTRIBUTING.md: TinyGo dev env, component scaffolding, submission flow
- Security audit: no InkStone internal URLs/IDs in committed files
- .gitignore: exclude credentials.yaml, .wrangler, *.wasm

https://claude.ai/code/session_01BnCdSLVH8tUed9VrrPavgT

registry/components/telegram/component.contract.yaml

@@ -0,0 +1,56 @@
+canonical_id: "telegram"
+display_name: "Telegram Bot"
+category: "api"
+version: "v1"
+wasi_target: "preview1"
+stability: "floating"
+runtime_compat:
+  - "cf-workers"
+  - "workerd"
+  - "wazero"
+constraints:
+  max_size_kb: 2048
+  max_cold_start_ms: 50
+  no_network_syscall: true
+  no_filesystem_syscall: true
+  io_model: "stdin_stdout_json"
+input_schema:
+  type: object
+  required: [chat_id, text, bot_token]
+  properties:
+    chat_id:
+      type: string
+    text:
+      type: string
+    bot_token:
+      type: string
+      description: Telegram Bot Token
+output_schema:
+  type: object
+  properties:
+    success:
+      type: boolean
+    data:
+      type: object
+      properties:
+        ok:
+          type: boolean
+gherkin_tests:
+  - scenario: "缺少 bot_token"
+    given: '{"chat_id":"123","text":"hello"}'
+    then_contains: '{"success":false'
+  - scenario: "缺少 chat_id"
+    given: '{"text":"hello","bot_token":"token"}'
+    then_contains: '{"success":false'
+tags: [integration, telegram, bot, message]
+description: "透過 Telegram Bot 發送訊息。透過 host function 呼叫 Telegram Bot API，需要 bot_token。"
+credentials_required:
+  - key: telegram_bot_token
+    type: telegram_bot_token
+    description: "Telegram Bot Token（由 @BotFather 取得）"
+    inject_as: bot_token
+config_example: |
+  send_message:                  # 節點名稱（可自訂）
+    chat_id: ""                  # Telegram Chat ID（必填）
+    text: ""                     # 訊息內文（必填）
+    # bot_token 由 credentials.yaml 的 telegram_bot_token 自動注入