sherpa

The server primarily operates locally, interacting via standard I/O (stdio) and persisting state to the user's home directory (`~/.sherpa/`). Input arguments are validated for length and type, and workflow YAML files are parsed, not executed. File operations for state persistence (`user-profile.json`, `progress-tracker.json`, `workflow-state.json`) use atomic writes (temp file + rename) and include robust error handling with retry mechanisms and graceful degradation. There are no obvious hardcoded secrets or direct network listening services exposed. The risk of `eval` or arbitrary code execution from workflow files is mitigated by parsing YAML rather than executing code. Overall, it demonstrates good security practices for a local agent-guidance tool.