The new inline-scripts CLI case asserted the external <script src> survived
by matching a "loads" edge on resolved_path alone. The fixture's package.json
also declares "main":"main.js", which produces its own "loads" edge with the
same resolved_path, so the assertion could pass through the package entrypoint
even if the HTML script edge regressed. Also require script_path === "main.js"
to pin the assertion to the HTML-derived edge, matching the reference-html case
in the same file. Tests-only.
The analyzer already reports valid HTML containing inline <script> bodies
through an explicit "parse-html-inline-scripts" unavailable scope, so an
application whose endpoints, storage, or imports live in inline scripts is
surfaced as not-analyzed rather than silently empty. That contract was asserted
only at the filesystem boundary (javascriptHtmlEntrypoints.test.ts); the public
CLI acceptance surface had no scenario proving it survives transport.
Add one acceptance case to the existing unavailable-HTML CLI suite. No source change.