2.9.0 release target; current-source Windows candidate evidence
Package applicability is under review; follow the stated version and platform limits.
Choose separate names
The diagnostic says that input and output file names are the same. Write the result to a distinct CSV path.
josim-pro-cli -o results.csv circuit.cirCheck the result
In the Windows 2.9.0 check, the exact-path collision exited with code 1 and left the input bytes unchanged. The corrected valid example completed. This checks that specific guard; it is not a general recovery guarantee for every filesystem alias or failure.
The recorded native Windows candidate also rejected the exact source path configured as a buffered numerical output destination, reporting [IO] Output collision. Restoring the normal output options allowed the JTL run to complete; the input bytes were unchanged. This run-output guard is separate from the Plot export studio Save dialog and does not qualify every filesystem alias or export failure.
Sources and verification details
Recorded inputs/builds only. Complete walkthrough and final-package acceptance remain separate.
VAL-010 · Installed JoSIM®-Pro 2.9.0 Windows
CLI input preservation
One exact input/output-path collision; no general filesystem recovery claim.
VAL-011 · JoSIM®-Pro 2.9.0 Windows review CLI, built 3 November 2026
Packaged AND/base_cells CLI run, missing-include rejection/restoration, main/include output-collision rejection and absolute-input resolution from another working directory
CLI recovery and input/output integrity only. GUI recovery, numerical accuracy/convergence and final-package checks remain pending.
VAL-016 · JoSIM®-Pro 2.9 current-source Windows candidate with matching freshly built runtime; not the final distributed package
Production GUI controls, normal licensed JTL and AND runs, missing-include restoration, exact input/output collision rejection and operator-assisted CSV/All traces export. Explicitly reopening saved JTL and rerunning also passed
Automatic session restoration failed (KB-GUI-007). File opening was supplied at the production OpenFile boundary; folder-picker input, cancellation, retry, other export formats, physical accuracy and final-package acceptance remain unverified. CSV/CLI differences were at most one ULP in this example, not an accuracy or regression tolerance. The Clang-built runtime does not close the separate MSVC/OpenMP finding KB-BUILD-001. External Computer Use capture remains unqualified.
- josim-pro:docs/manual_source/sections/troubleshooting.tex · Command-line launch exits immediately
- validation:windows-cli-20261102 · VAL-010 exact-path collision check
- owner:technical-review-20261102 · JoSIM®-Pro 2.9 chosen as the public starting path; release availability must be checked before publication
- validation:windows-workflows-20261103 · VAL-011/VAL-012; exact route, runtime and evidence limits
- validation:josim-native-windows-20261103 · VAL-016; exact native actions, independent output checks, operator Save and failed automatic-restoration boundary
- Owner technical review and any unrecorded release/platform walkthroughs remain pending. Historical advice is not current-release qualification.