[chriskinal]

Part of #547, after #831 and #832. A job keeps the machine it was worked with: the vehicle's hitch points and the chain of tools on them.

Changes

• JobRig (Models/Job), stored in job.json as rig:

  • vehicle: profile name, type, coupling type (DDI 157), and its drawbar, rear 3-point and front 3-point hitch points from the rear axle.
  • tools: in order from the vehicle. Each tool names its connector: one of the vehicle's hitch points, or PreviousTool (the rear connector of the tool before it). It also has its mount, its distances from that connector, and its offset, length, width and section widths.

  As ISO 11783-10 chains a tractor's connectors and each implement's elements, every part is measured from what it hangs on. It is a copy, not a profile name: a profile can be edited or deleted later.

• When it is written: MainViewModel hands the job service the loaded vehicle and tool when a job starts or resumes, and whenever a profile is loaded or saved. Closing a settings panel saves it. JobService.RecordRig writes job.json only when the machine changed, and never writes a newer build's job.

• One tool in practice: the web client works with one tool, so AgOpenWeb writes a chain of one. The format takes more, and the spec says a reader should accept more.

  • A reopened job gets the machine loaded at that moment, so a longer chain from another program is replaced by the tool that paints from then on.
  • No geometry for a chain of tools yet.

• Format: rig is a new member, so schemaVersion stays 1. Since Field, job and coverage files: a format version, and what this build doesn't read is kept #825 an older build keeps members it doesn't know. A job saved before this change has no rig and gets none until it is opened.

• Spec: Docs/FIELD_FILE_FORMATS.md describes rig.

Tests

• JobRigTests (9):
  • the copy for each tool type, with only the distances that type uses;
  • a two-tool chain read back as written, with the member names and enum strings other programs read;
  • an older job;
  • writing only on a change;
  • no active job;
  • a newer build's job left alone.
• JobRigRecordingTests (3): the view model records the machine on job start and on profile load and save. Two of them fail on develop's MainViewModel; the third, nothing recorded without a job, passes either way.
• Models 472, Services 2451 (2 skipped), ViewModels 642, RemoteServer 44, all passing. The licence check passes.

Runner (this branch vs develop)

Harness	Result
Update scenarios: old releases' jobs read back, rollback	0 new, 0 gone; both passed
Field jobs J1, J7 (3 turns)	0 new, 0 gone

🤖 Generated with Claude Code