2.1 KiB
2.1 KiB
Rust-Only Acceptance Checklist
Scope
This checklist covers the Rust-side work that can be verified before the SuperRPA browser repository is available locally.
Covered:
- pipe handshake and protocol baseline
- task-level message types
- HMAC canonical string alignment
- Phase 1 rule-based Baidu search planner
- DeepSeek provider scaffolding
- provider-backed minimal Agent runtime with fallback to planner mode
Not covered yet:
SgClawProcessHostPipeListenerCommandRouterreuse in SuperRPA- FunctionsUI bridge integration
Required Commands
Run from the feature worktree:
cd /home/zyl/projects/sgClaw/.worktrees/superrpa-browser-control
cargo test -q
Optional focused checks:
cargo test --test task_protocol_test -q
cargo test --test planner_test -q
cargo test --test runtime_task_flow_test -q
cargo test --test deepseek_provider_test -q
cargo test --test agent_runtime_test -q
Pass Criteria
init -> init_acktests passsubmit_task,task_complete, andlog_entryserialize correctly- HMAC output is based on newline-delimited canonical string with stable JSON ordering
- Planner turns
打开百度搜索天气intonavigate -> type -> click - Runtime mock flow emits browser commands and finishes with
task_complete - DeepSeek settings load from environment with default model
deepseek-chat - DeepSeek request body matches OpenAI-compatible chat completion shape
Runtime Configuration
The provider-backed path is enabled only when DEEPSEEK_API_KEY is present.
Environment variables:
DEEPSEEK_API_KEYDEEPSEEK_BASE_URLoptional, defaults tohttps://api.deepseek.comDEEPSEEK_MODELoptional, defaults todeepseek-chat
Without DEEPSEEK_API_KEY, sgClaw falls back to the Phase 1 rule-based planner.
Current Branch Milestones
b9773d4— task pipe protocol and HMAC alignment1ab0012— Phase 1 task planner flow0d0097b— DeepSeek provider scaffolding9979b1f— provider-backed Agent runtime
Next Dependency
To continue beyond Rust-only acceptance, the local SuperRPA / Chromium repository path is required so Tasks 3, 4, and 5 can be implemented and verified.