Project 4: Web Action SDK Task Automation
Build a resilient web action flow that survives minor UI and session changes.
Quick Reference
| Attribute | Value |
|---|---|
| Difficulty | Level 3 (Advanced) |
| Time Estimate | 1-2 weeks |
| Main Programming Language | TypeScript |
| Alternative Programming Languages | Python, JavaScript |
| Key Topics | Selector stability, commit guards, step tracing |
1. Learning Objectives
- Design robust selector strategies and fallback paths.
- Separate navigation actions from final commit actions.
- Implement phase-based telemetry for debugging.
2. All Theory Needed (Per-Concept Breakdown)
Concept A: UI Drift Resilience
- Prefer semantic anchors and role-based targeting.
- Maintain fallback selectors for critical elements.
Concept B: Commit Safety
- Introduce explicit confirmation checkpoint before final submit.
- Prevent silent high-impact actions.
3. Architecture and Build Plan
- Break flow into deterministic phases.
- Add phase-level timeout and heartbeat logs.
- Simulate DOM changes and validate fallback selectors.
4. Validation and Testing
- All phases emit start/end logs.
- Commit requires explicit confirmation token.
- Session-expiry path recovers gracefully.
5. Troubleshooting
- Symptom: action stalls silently.
- Fix: add timeout and fail-fast phase telemetry.
6. Deliverables
- Phase diagram.
- Selector fallback matrix.
- Commit safety checklist.
7. Stretch Goals
- Add nightly regression against snapshot variants.