feat( protocol-designer, step-generation): timeline errors for flex stacker steps

[rclarke0]

Overview

Timeline errors for flex stacker steps

Test Plan and Hands on Testing

• Unit tests for all error types added
• smoke testing will be done in future PRS

Changelog

• Added error types and checking for HOPPER_EMPTY, SHUTTLE_EMPTY, SHUTTLE_FULL and MISMATCHED_LABWARE
• Added utils to check for labware on the shuttle and for determining if the labware being stored matched what is inside the hopper

Review requests

Risk assessment

• low

Partially closes EXEC-2083 and EXEC-2084 until it can be tested in the UI

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 25.77%. Comparing base (62d016d) to head (f2f0b12).
⚠️ Report is 9 commits behind head on edge.

Additional details and impacted files

@@            Coverage Diff             @@
##             edge   #20317      +/-   ##
==========================================
- Coverage   25.78%   25.77%   -0.02%     
==========================================
  Files        3625     3636      +11     
  Lines      301800   303125    +1325     
  Branches    42290    42430     +140     
==========================================
+ Hits        77827    78118     +291     
- Misses     223944   224978    +1034     
  Partials       29       29              

Flag	Coverage Δ
protocol-designer	19.35% <7.89%> (+0.05%)	⬆️
step-generation	5.59% <100.00%> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
.../src/commandCreators/atomic/flexStackerRetrieve.ts	100.00% <100.00%> (ø)
...ion/src/commandCreators/atomic/flexStackerStore.ts	100.00% <100.00%> (ø)
step-generation/src/errorCreators.ts	71.20% <100.00%> (+1.97%)	⬆️
step-generation/src/types.ts	100.00% <ø> (ø)
step-generation/src/utils/misc.ts	61.88% <100.00%> (+0.48%)	⬆️

... and 31 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ncdiehl11]

All good either way, but do you plan to wire up this error in this PR? I think we can create a utility in step-generation/src/utils/misc.ts that accesses the module's state. Something like:

export const getLabwareIdOnShuttle = (
  stackerState: FlexStackerModuleState
): string | null => {
  return stackerState.labwareOnShuttle?.primaryLabwareId ?? null
}

[jerader]

thanks Nick. ya, up to you Rhyann! you can address multiple timeline errors in this PR if you want. But if you wire this up, can you also add a unit test for it?

[rclarke0]

on it!

[jerader]

nit: this isn't a valid stack, it should include the labwareId itself in it. so something like this: this means mockLabwareId is directly on the slot.

Suggested change

	stack: ['D2'],
	stack: [mockLabwareId, 'D2'],

[jerader]

cool thanks for adding all the error types in here 😄