Files
secs-gem/data/process_job_state.yaml
raphael 90c177b7ce E40 Process Jobs + E94 Control Jobs + E30 communication state
GEM300 layer: SEMI E40-0705 Process Job and E94-0705 Control Job
state machines, plus the E30 §6.1 communication-state machine that
sits between HSMS SELECT and full GEM communication. Data-driven
via data/process_job_state.yaml and data/control_job_state.yaml,
mirroring the existing control_state.yaml pattern.

Wire coverage:
  S14F9/F10   CreateObject (CJ)              host -> equipment
  S14F11/F12  DeleteObject (CJ)              host -> equipment
  S16F5/F6    PRJobCommand                   host -> equipment
  S16F9       PRJobAlert                     equipment -> host
  S16F11/F12  PRJobCreate (simplified body)  host -> equipment
  S16F13/F14  PRJobDequeue                   host -> equipment
  S16F27/F28  CJobCommand                    host -> equipment

Process Job FSM exposes 8 states matching PRJOBSTATE bytes (E40 §10.3.2);
HOQ is reorder-aware (move-to-head against an insertion-order vector);
Stop/Abort on a Queued PJ routes through ABORTING so the host observes
PRJOBSTATE=7 on the wire (§6.3); alert_enabled is settable per-PJ for
PRALERT control; FSM dispatches through ProcessJobStore::on_change_
dynamically so a late set_state_change_handler() reaches existing PJs.

Hardening: loader rejects NoState (sentinel) as initial/from/to and
rejects `on: created` rows; static_asserts pin enum values to wire
bytes; ProcessJobStore is non-movable to keep the per-PJ this-capture
safe.

Server simulator cascades the full CJ -> PJ lifecycle on CJSTART so
the wire trace exercises every legal state. CEIDs 400/401 fire on CJ
state changes via the existing event-report pipeline.

Tests: 60+ new assertions across test_process_jobs, test_control_jobs,
test_communication_state, test_hsms_connection, plus loader and
messages round-trip coverage.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-06-07 21:00:32 +02:00

58 lines
2.7 KiB
YAML

# E40 §6 Process Job state model — encoded as a transition table.
#
# Each row is a (from, on) -> (to [, ack]) tuple, mirroring the encoding
# in data/control_state.yaml. Events are the lower-snake-case verbs the
# loader maps to ProcessJobEvent: start / pause / resume / stop / abort /
# hoq / select / setup_complete / process_complete / abort_complete /
# created. Host-initiated events (start, pause, resume, stop, abort,
# hoq) carry an `ack` when the row should override the default
# HostCmdAck::Accept (e.g. a row that only validates an event without
# changing state).
#
# Wire reference: S16F9 PRJOBSTATE byte (E40-0705 §10.3.2):
# 0 Queued, 1 SettingUp, 2 WaitingForStart, 3 Processing,
# 4 ProcessComplete, 5 Paused, 6 Stopping, 7 Aborting.
#
# Process-Complete is terminal — deletion happens out-of-band via the
# ProcessJobStore (CJ cleanup or explicit S16F13 while still QUEUED).
initial: Queued
transitions:
# --- QUEUED ----------------------------------------------------------
# PJSTOP/PJABORT on a Queued PJ routes through Aborting so the host
# observes PRJOBSTATE=7 on the wire (E40-0705 §6.3). PJDELETE / S16F13
# is the dequeue-without-state-change path.
- {from: Queued, on: select, to: SettingUp}
- {from: Queued, on: hoq} # reorder only, no state change
- {from: Queued, on: stop, to: Aborting}
- {from: Queued, on: abort, to: Aborting}
# --- SETTING-UP -------------------------------------------------------
- {from: SettingUp, on: setup_complete, to: WaitingForStart}
- {from: SettingUp, on: stop, to: Stopping}
- {from: SettingUp, on: abort, to: Aborting}
# --- WAITING-FOR-START -----------------------------------------------
- {from: WaitingForStart, on: start, to: Processing}
- {from: WaitingForStart, on: stop, to: Stopping}
- {from: WaitingForStart, on: abort, to: Aborting}
# --- PROCESSING -------------------------------------------------------
- {from: Processing, on: pause, to: Paused}
- {from: Processing, on: stop, to: Stopping}
- {from: Processing, on: abort, to: Aborting}
- {from: Processing, on: process_complete, to: ProcessComplete}
# --- PAUSED ----------------------------------------------------------
- {from: Paused, on: resume, to: Processing}
- {from: Paused, on: stop, to: Stopping}
- {from: Paused, on: abort, to: Aborting}
# --- STOPPING --------------------------------------------------------
- {from: Stopping, on: process_complete, to: ProcessComplete}
- {from: Stopping, on: abort, to: Aborting}
# --- ABORTING --------------------------------------------------------
- {from: Aborting, on: abort_complete, to: ProcessComplete}