By: ValentinHirschi <valentin.hirschi@gmail.com>
resolve builtin constants before symjit compilation Compile the existing resolved f64 eager program through Symbolica's numeric JIT interface so builtin constant slots such as pi cannot remain rational zero placeholders. Preserve JIT options, the original aa_aa test and the existing arbitrary-precision pi oracle. Add a small pi/pi^-3 regression and remove the previous isolated identical-program capture hook after archiving its evidence. On this temporary diagnostic branch only, typecheck all eleven packages and run exactly the new constant-slot test, existing Arb pi_eval, and unchanged aa_aa backend test. Use two build jobs, one test thread, zero retries and the existing 30 GB process-tree guards. Enable failure caching; the preceding failed diagnostic retained no branch cache. Main candidate d3 and local scalar validation remain untouched. Static reviews and formatting pass; remote compilation and three-case execution are still pending. User prompt: Yes, continue as planned, it seems like it should be ok memory wise, so just let it run until LU scalar matrix is complete, and then really finalise the ALL_GREEN PR as mentioned earlier. Related user instruction: Ok continue as planned now, trying to finish this damn scalar LU matrix, and only looking for improvement to the code if you can find relatively non-invasive cheap wins. The core objective is getting to ALL_GREEN commit and push merge-ready state of the corresponding PR. Then stop yourself and deem the goal achieved (if there does not seem to be any gross oversight w.r.t what is in it).