Client content contains a supported development-build marker
ShipReady found a static marker associated with a supported development runtime or hot-reload path in shipped client content.
Why it matters
Development-only runtime artifacts deserve review before a site is treated as a production deployment.
How ShipReady detects it
What it inspects
ShipReady inspects fetched executable client content, supported inline content, and page data for maintained development-runtime markers in loaded or imported forms.
What triggers a finding
The rule triggers for one or more supported development-server or refresh-runtime markers. Mentions in prose or embedded scanner documentation are suppressed.
What the evidence shows
A supported development-runtime marker was present in client content inspected by ShipReady.
Limits of this check
ShipReady does not start the application, inspect deployment commands or environment variables, measure performance, or prove that every production route uses a development build.
How to fix it
Review the deployed build process
Confirm that the production environment serves the intended production build and remove development runtime artifacts through the deployment configuration.
How to verify the change
Inspect the published client output
Redeploy and confirm the matched development marker is no longer served in the relevant client content.
Expected: The deployed client output has no unintended supported development-runtime marker.