feat: forward row counts / status_note / ext_refs in job_update and job_close

[Kydoimos97]

Feature Updates

• job_update and job_close can now carry the data the jobs API already accepts. Both helpers gain four optional keyword-only parameters — input_rows, output_rows, status_note, ext_refs — sent in the request payload only when provided. Until now the client had no parameters for these, so no service using the standard helpers could record how many rows a job processed/produced, a status note, or external references on a running or closing job. This is the client half of the datastore.processing_events write-contract fix (the API/DB half lands in AiAxis); together they stop job rows from coming out with random gaps.

Fixes

• None (purely additive; existing calls are unchanged and all four fields default to omitted).

Resolved Incidents

Datadog

None — proactive observability enablement, not an incident fix.

GitHub

None.

References

• Pairs with AiAxis PR #3625 (processing_events targeting columns + hardening).
• Backward compatible: new params are optional and keyword-only. Ship via a patch tag (v6.2.x) so services pinned to wrenchcl~=6.2.0 pick it up without a pin change.
• Follow-up: per-service call-site sweep so producers actually pass row counts / progress once this version is published.

End-user impact

No direct user-facing change. Enables reliable per-job throughput and status reporting across pipeline services, which downstream powers correct job/progress UX in the app.

[Wrench-Review-Bot]

PR Review — APPROVE

Adds input_rows, output_rows, status_note, ext_refs as optional keyword-only params to job_update() and job_close(), forwarding them to the existing API fields the server already accepts.

Nits

• Nit: tests/test_wrench_notify.py — TestJobClose has test_job_close_includes_all_lifecycle_fields but no symmetric test_job_close_omits_lifecycle_fields_when_not_provided. TestJobUpdate has both. Not a concern given the pattern is identical and the include paths are tested, but adding the omit test would make the two classes fully parallel.
• Nit: WrenchCL/Wrench/_notify.py:220 — ext_refs: Optional[dict] is unbound; Optional[Dict[str, Any]] is more informative (requires from typing import Dict, Any).

Context

Diff: 2 files, +110/−0 · Prior reviews: none · Related: AiAxis #3625 (OPEN — DB persistence half; API already accepts the new fields so this ships safely first)

— Claude

[Wrench-Review-Bot]

PR Review — APPROVE

Adds input_rows, output_rows, status_note, ext_refs as optional keyword-only params to job_update() and job_close(), forwarding them to the existing API fields the server already accepts.

Nits

• Nit: tests/test_wrench_notify.py — TestJobClose has test_job_close_includes_all_lifecycle_fields but no symmetric test_job_close_omits_lifecycle_fields_when_not_provided. TestJobUpdate has both. Not a concern given the pattern is identical and the include paths are tested, but adding the omit test would make the two classes fully parallel.
• Nit: WrenchCL/Wrench/_notify.py:220 — ext_refs: Optional[dict] is unbound; Optional[Dict[str, Any]] is more informative (requires from typing import Dict, Any).

Context

Diff: 2 files, +110/−0 · Prior reviews: none · Related: AiAxis #3625 (OPEN — DB persistence half; API already accepts the new fields so this ships safely first)

— Claude

[Wrench-Review-Bot]

✅ PR Review complete — APPROVED. Full review ↗