Problem
gitnexus cypher forwards backend error payloads to stdout but leaves the process exit code at zero. Automation therefore treats invalid Cypher, including LadybugDB binder failures, as success.
Reproduction
Against a valid disposable index:
gitnexus cypher "MATCH ()-[r:CodeRelation]->() RETURN r.id" -r openclaw
Observed payload:
{"error":"Prepare failed: Binder exception: Cannot find property id for r."}
Observed process status: 0.
Acceptance
- A backend result containing a non-empty
error sets process.exitCode = 1 after printing the structured payload.
- Successful tabular and array results remain exit zero.
- Existing
--limit behavior remains unchanged.
- A focused unit test proves both error and success paths.
- Exact-head remote CI is green.
Parent epic: #39
Tracking ID: R21a-cypher-exit
Problem
gitnexus cypherforwards backend error payloads to stdout but leaves the process exit code at zero. Automation therefore treats invalid Cypher, including LadybugDB binder failures, as success.Reproduction
Against a valid disposable index:
gitnexus cypher "MATCH ()-[r:CodeRelation]->() RETURN r.id" -r openclawObserved payload:
{"error":"Prepare failed: Binder exception: Cannot find property id for r."}Observed process status:
0.Acceptance
errorsetsprocess.exitCode = 1after printing the structured payload.--limitbehavior remains unchanged.Parent epic: #39
Tracking ID:
R21a-cypher-exit