runtime-behavior-probe

Runtime behavior probes investigate real-world interactions by executing disposable TypeScript scripts against a validation matrix to surface edge cases and drift. This approach observes actual execution without modifying your repository.

Runtime investigations are safely executed using disposable probes outside git-tracked paths within a restricted temporary workspace. This method enforces manual invocation and restricts write access to prevent unintended modifications to your codebase.

Runtime behavior probes are planned and executed by creating a temporary TypeScript file, typechecking it against the repository, and running it across an explicit validation matrix. This generates a findings-first report detailing observations and methods.

Runtime probing uses disposable TypeScript probes outside git-tracked paths, ensuring your repository remains unmodified. It restricts write access to a temporary workspace and records metadata and results as an audit artifact.

Runtime behavior probes enforce manual invocation and restrict write access entirely to a temporary workspace. You must run disposable TypeScript scripts outside tracked paths, meaning automated continuous integration execution is not the intended use case.