TraceFlow must show the runtime and static flow of application files: which
entry file starts work, which files it includes or imports, which browser assets
are loaded, which child scripts execute, and how those relationships connect
under a shared trace ID.

Yes. The package should explicitly support two kinds of flow tracing:

Runtime flow — what actually executed for a specific request or job.

Static file flow — what files reference, include, import, source, load, or link
to other files across PHP, JavaScript, CSS, Bash/sh, Python, and HTML.

The earlier package has the basic runtime tracing foundation, but the next
revision should add formal goals/requirements documentation and a non-executing
file dependency scanner.

Recommended goals document Create:

text docs/GOALS-AND-REQUIREMENTS.md

How to see runtime flow? 
Want to include php, html, js, css etc ?