v0.5.5
First-run and pip-only-user fixes surfaced by a fresh-install audit, plus a re-landed review fix. No engine behavior, schema, policy, or dependency changes.
- Friendly input errors (#69).
check,run,generic-check,generic-run,hermes-check, andcodex-checkno longer dump a raw traceback (and the user's path) when given a missing file, invalid JSON, or an inline string instead of a file path. They now print a one-line error with a payload example and exit non-zero, and the positional file arguments carry--helpdescriptions with an example schema. doctorpath consistency and no CWD litter (#71).agent-sudo doctorno longer creates a.agent-sudo/directory in the current working directory. It probes the single home state root (~/.agent-sudo) for both the audit-log and delegation-store writability checks, so it reports one consistent location.- No repo-relative examples in docs or setup output (#67). Documented commands and the
agent-sudo setupverify steps (hermes/openclaw) no longer referenceexamples/*.jsonfiles that apip/pipxinstall does not have. Each is now self-contained (an inline payload written to a temp file, oragent-sudo eval), so every documented command works from a clean install with no repository checkout. Thedemoclosing line now points atagent-sudo eval. - Improved
agent-sudo-mcp --help(#72).--audit-log,--delegations-file, and--pending-approvals-filenow have descriptions, and the server help carries a description and an epilog pointing atagent-sudo evalandagent-sudo setup. - Test isolation (#84). The MCP gateway tests no longer depend on the developer's ambient
~/.agent-sudo/config.jsonworkspace (orAGENT_SUDO_WORKSPACE), so they behave the same locally as on a clean CI runner. - Re-landed missed PR #90 review fixes (#95). PR #90 was squash-merged without its review-fix commit; this restores it: the demo shell executor reports
executed=False(notTrue) when the host fails to spawn a process (OSError), and the Windows file-lock retry filter replaces magic numbers(13, 33)with named errno/winerror sets via an_is_lock_busy()helper. Adds the regression tests whose absence let the fix silently drop. - Compatibility. No breaking changes, no schema changes, no policy-behavior changes, no new runtime dependencies. Docs, CLI help/error text, test isolation, and the
executedflag on a (rare) demo-executor spawn failure are the only user-visible changes.