[cursor]

Summary

Combustion verification and throttle-up did not read actuator status after the ignition pre-check. Fuel and oxidizer are already open in those states. A valve that reported Fault, Error, Disabled, Unknown, Moving, or AtPosition stayed at its last open command. A Ready operating chamber pressure then declared the engine running, and the running state does not command those valves again.

The same Ready gate used before each open now runs again after the spark pulse, during combustion verification, and before throttle-up can finish or keep ramping. A valve that is not Ready fail-closes on that pass. An abort that already won is left as abort. A Ready operating pressure with every actuator still Ready still declares the engine running and does not command the valves.

Related issues

None. Found in the daily safety scan.

Type of change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation only
• Refactor / chore (no behavior change)

How to test

1. dotnet test Tests/HelloblueGK.Tests.csproj -c Release --filter FullyQualifiedName~StartupSequenceControllerTests
2. Confirm a faulted valve during the spark pulse, combustion verification, or throttle-up ends in Error with every valve commanded shut, and does not reach Running.
3. Confirm Ready actuators and an operating chamber pressure still reach Running without a valve command.

Checklist

• I read CONTRIBUTING.md and followed the development workflow
• dotnet build succeeds locally (or I ran the equivalent CI steps)
• dotnet test Tests/HelloblueGK.Tests.csproj passes (or tests are not applicable)
• I added or updated tests for behavior changes
• I updated documentation when behavior, APIs, or setup changed
• My commit messages are clear and descriptive
• I did not commit secrets, credentials, or .env files
• First PR / docs-only work stays out of Certification/ unless the issue asked for it

Screenshots / logs (optional)

Release suite: 1604 passed, 0 failed. Startup sequence filter: 99 passed. dotnet list package --vulnerable --include-transitive reported no vulnerable packages for HelloblueGK, HelloblueGK.WebAPI, and HelloblueGK.Tests. That is a dependency audit of those three projects.

  

---

Note

High Risk
Changes engine startup safety logic while propellant valves may be open; incorrect gating could spuriously abort or miss a faulted valve.

Overview
Extends actuator Ready gating so propellant valves cannot stay open while the sequence advances—or after it reaches Running—when fuel, oxidizer, or igniter is no longer Ready.

After the igniter spark pulse, the sequence re-runs RequireStartupActuatorsReadyAsync before entering combustion verification. The same check runs at the start and end of combustion verification (including after sensor reads), before and after throttle-up pressure logic, and at the end of the throttle ramp delay instead of only calling ContinueSequenceAsync. The control loop no longer treats Running as a no-op: each pass verifies actuators are still Ready and fail-closes if not.

Unit tests cover faults during spark, combustion wait, throttle-up, and while Running, plus the happy path where Ready actuators and operating pressure still reach Running without extra valve commands.

^{Reviewed by Cursor Bugbot for commit 9942b67. Bugbot is set up for automated code reviews on this repo. Configure here.}