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
72 lines
1.8 KiB
YAML
72 lines
1.8 KiB
YAML
canonical_id: "validate_json"
|
|
display_name: "JSON 格式驗證器"
|
|
category: "logic"
|
|
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:
|
|
- json_string
|
|
properties:
|
|
json_string:
|
|
type: string
|
|
description: "待驗證的 JSON 字串"
|
|
|
|
output_schema:
|
|
type: object
|
|
required:
|
|
- valid
|
|
properties:
|
|
valid:
|
|
type: boolean
|
|
description: "是否為合法 JSON"
|
|
error:
|
|
type: string
|
|
description: "驗證失敗時的錯誤訊息（valid=false 時存在）"
|
|
|
|
gherkin_tests:
|
|
- scenario: "合法 JSON 物件通過驗證"
|
|
given: '{"json_string":"{\"key\":\"value\"}"}'
|
|
then_contains: '{"valid":true}'
|
|
|
|
- scenario: "合法 JSON 陣列通過驗證"
|
|
given: '{"json_string":"[1,2,3]"}'
|
|
then_contains: '{"valid":true}'
|
|
|
|
- scenario: "非法 JSON 字串回傳錯誤"
|
|
given: '{"json_string":"not-json"}'
|
|
then_contains: '{"valid":false,"error":'
|
|
|
|
- scenario: "空字串回傳錯誤"
|
|
given: '{"json_string":""}'
|
|
then_contains: '{"valid":false,"error":"json_string is required"}'
|
|
|
|
- scenario: "缺少 json_string 欄位回傳錯誤"
|
|
given: '{}'
|
|
then_contains: '{"valid":false,"error":"json_string is required"}'
|
|
|
|
tags:
|
|
- "validation"
|
|
- "json"
|
|
- "utility"
|
|
- "logic"
|
|
|
|
description: "驗證輸入字串是否為合法 JSON 格式。輸入 json_string 欄位，回傳 valid（布林值）與 error（失敗時的錯誤訊息）。"
|
|
config_example: |
|
|
my_validate_json: # 節點名稱（可自訂）
|
|
json_string: '{"key":"value"}' # 待驗證的 JSON 字串（必填）
|