Summary
Quinn's A2A endpoint is failing on all skill invocations with:
Error: expected str, bytes or os.PathLike object, not NoneType
This affects all skills (bug_triage, pr_review, board_audit, etc.).
Impact
bug_triage: 24% success rate (25 failures / 33 attempts)
auto-triage-sweep: 0% success rate across 23 outcomes
- 25 items stuck in
error state on the workstacean flow board
- Every
fix_ci remediation dispatched by pr-remediator to Quinn silently fails
- Quinn is effectively offline for all A2A skill calls
Reproduction
Invoke Quinn via A2A JSON-RPC with any skill — response is always the NoneType path error.
Likely Cause
A file path variable (config path, workspace path, or repo clone path) is None when Quinn tries to use it. Candidates:
- Missing environment variable for workspace/temp directory
- Repo path not resolved before use in skill handler entry point
- Config file path refactored but not updated
Quinn's own auto-triage confirmed: "this is a runtime/deployment issue, not a build failure. CI is green across all recent runs on dev."
Cross-reference from workstacean side:
Suggested Fix
- Check Quinn's skill handler entry point for
Path() or open() calls receiving args from config/env
- Add null guards before path operations
- Verify all required env vars in Quinn's deployment config (especially workspace/temp dirs)
Priority
Critical — this blocks all automated triage and QA workflows across the fleet.
Summary
Quinn's A2A endpoint is failing on all skill invocations with:
This affects all skills (bug_triage, pr_review, board_audit, etc.).
Impact
bug_triage: 24% success rate (25 failures / 33 attempts)auto-triage-sweep: 0% success rate across 23 outcomeserrorstate on the workstacean flow boardfix_ciremediation dispatched by pr-remediator to Quinn silently failsReproduction
Invoke Quinn via A2A JSON-RPC with any skill — response is always the NoneType path error.
Likely Cause
A file path variable (config path, workspace path, or repo clone path) is
Nonewhen Quinn tries to use it. Candidates:Quinn's own auto-triage confirmed: "this is a runtime/deployment issue, not a build failure. CI is green across all recent runs on
dev."Cross-reference from workstacean side:
Suggested Fix
Path()oropen()calls receiving args from config/envPriority
Critical — this blocks all automated triage and QA workflows across the fleet.