fix(jobs): enumerate the interrupted error code

The code reaches an operator through `ob audit` but was not in the registry,
so the generated error reference could not document it. The enumeration test
missed it because it matches the struct-literal form and the assignment was a
tuple; written as separate statements it is now covered by that test too.

Claude-Session: https://claude.ai/code/session_01JaxHfqFZk8GdrBNbtQZ6c2

Author: vishr

internal/engine/job.go

@@ -117,7 +117,10 @@ func (e *Engine) RunJobWithJournalID(ctx context.Context, request JobRunRequest)
 		// a failure, so the reason has to ride on ErrorCode.
 		journalContext := ctx
 		if interruptedRun(ctx, runErr) {
-			record.Status, record.ErrorCode = "fail", "interrupted"
+			record = journal.Record{
+				Phase: "job", Event: "finish", Status: "fail", ErrorCode: "interrupted",
+				OperationKind: "job_run", Service: job,
+			}
 			var cancel context.CancelFunc
 			journalContext, cancel = context.WithTimeout(context.Background(), journalCleanupTimeout)
 			defer cancel()

internal/onebox/operation_errors.go

@@ -119,6 +119,13 @@ var operationFailureDefinitions = map[string]OperationFailure{
 		Message: "this host is owned by a different Onebox application, and one host has one owner",
 		Command: "ob preflight --output json",
 	},
+	"interrupted": {
+		// Not a failure of the job and not an incomplete operation: the client
+		// went away, and what the job did is unknown unless it journaled a
+		// result first. Reconciliation on the next operation writes this.
+		Message: "the operation's client went away before its outcome could be recorded",
+		Command: "ob audit --output json",
+	},
 	"job_plan_failed": {
 		Message: "the one-shot job plan could not be produced",
 		Command: "ob job plan <job> --output json",

site/src/content/docs/reference/errors.mdx

@@ -136,6 +136,7 @@ step to complete rather than a line to run verbatim.
 | `finalize_refused` | the release cannot be finalized because the recorded activation evidence disagrees with the live host | diagnostic | `ob status --output json` |
 | `host_environment_mismatch` | this host is claimed by a different environment of the same application, which would share its container and volume names | diagnostic | `ob preflight --output json` |
 | `host_owner_mismatch` | this host is owned by a different Onebox application, and one host has one owner | diagnostic | `ob preflight --output json` |
+| `interrupted` | the operation's client went away before its outcome could be recorded | diagnostic | `ob audit --output json` |
 | `job_plan_failed` | the one-shot job plan could not be produced | next | `ob job plan <job> --output json` |
 | `logs_failed` | log retrieval failed | diagnostic | `ob status --output json` |
 | `manifest_invalid` | a release manifest is not valid closed JSON for its schema | diagnostic | `ob status --output json` |