TASK-001C: Simulator Boundary and Seeded Data

• Status: Ready
• Parent: TASK-001
• Spec: SLICE-001
• Depends on: TASK-001A, TASK-001B

Goal

Create the fake vendor-like simulator boundary and the seeded data needed for the first slice without yet implementing the full application workflow.

Scope

• define simulator-facing interfaces behind an infrastructure boundary
• implement seeded recipe source with at least one valid recipe
• implement fake connection, homing, and move primitives with realistic delays
• expose machine signals and fault injection hooks needed for later tasks

Non-Scope

• full workflow orchestration
• UI projection logic
• end-to-end streaming consumption
• final run summary behavior

AI Execution Profile

• Model class: Balanced
• Reasoning effort: Medium
• Use this on: your default strong coding model
• This task is mostly interface and simulator shaping, not deep orchestration

Files Or Areas Expected To Change

• Infrastructure fake vendor SDK abstractions and implementations
• seeded recipe source
• motion and connection simulation primitives
• fault injection hooks or simulator controls

Acceptance Targets

• the rest of the app can depend on abstractions rather than simulator internals
• connection and motion primitives have time-based behavior
• seeded recipe data satisfies first-slice minimums
• later tasks have a believable simulator boundary to build on

Copy/Paste Prompt

Implement only TASK-001C: Simulator Boundary and Seeded Data in this repository.

Read first:
- docs/requirements.md
  Focus on Sections 6.1 through 6.6, 7.2, 7.3, 7.4, 7.9, 9.4, and 10.5
- docs/specs/SLICE-001-first-strong-vertical-slice.md
  Focus on Connection, Recipe Loading, Homing, and Layer Boundaries
- docs/tasks/slice-001/TASK-001C-simulator-boundary-and-seeded-data.md

Goal:
- Create the fake vendor-like simulator boundary and seeded machine data needed for the first slice.

Scope:
- Define infrastructure interfaces for simulated machine capabilities.
- Implement a seeded recipe source with at least one recipe containing 3 or more ordered scan points.
- Implement fake connection behavior with delay and possible failure.
- Implement homing and move primitives with time-based motion rather than instant jumps.
- Expose safety signals and fault injection hooks needed later.

Do not:
- Implement full workflow orchestration
- Implement final UI behavior
- Implement full telemetry/frame consumption in the application layer
- Create duplicate domain contracts outside the shared model

Verification:
- Build if possible
- Summarize the simulator interfaces and implementations added
- Note any simplifying assumptions used for the first slice

Important:
- Implement only this task
- Do not preemptively implement later tasks