Claude
2707fca32b
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
61 lines
1.7 KiB
YAML
61 lines
1.7 KiB
YAML
canonical_id: "gmail"
|
||
display_name: "Gmail 發信"
|
||
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: [to, subject, body, access_token]
|
||
properties:
|
||
to:
|
||
type: string
|
||
description: 收件人 Email
|
||
subject:
|
||
type: string
|
||
body:
|
||
type: string
|
||
access_token:
|
||
type: string
|
||
description: Google OAuth access token
|
||
output_schema:
|
||
type: object
|
||
properties:
|
||
success:
|
||
type: boolean
|
||
data:
|
||
type: object
|
||
properties:
|
||
message_id:
|
||
type: string
|
||
gherkin_tests:
|
||
- scenario: "缺少 access_token"
|
||
given: '{"to":"test@example.com","subject":"test","body":"hello"}'
|
||
then_contains: '{"success":false'
|
||
- scenario: "缺少 to"
|
||
given: '{"subject":"test","body":"hello","access_token":"token"}'
|
||
then_contains: '{"success":false'
|
||
tags: [integration, google, gmail, email, oauth]
|
||
description: "透過 Gmail API 發送 Email。透過 host function 呼叫，需要 Google OAuth access_token。"
|
||
credentials_required:
|
||
- key: gmail_token
|
||
type: google_oauth
|
||
description: "Google OAuth access token（gmail.send scope）"
|
||
inject_as: access_token
|
||
config_example: |
|
||
send_email: # 節點名稱（可自訂）
|
||
to: "" # 收件人 Email（必填）
|
||
subject: "" # 主旨（必填）
|
||
body: "" # 內文（必填）
|
||
# access_token 由 credentials.yaml 的 gmail_token 自動注入
|