Epic: Execution Planner

[cscheid]

In our TypeScript codebase, we need a source of truth for which input files produce which output files (and which temporaries).

Potential wins once we have this:

• parallelization
• change output locations (including slugs, etc)
• safer parameterized reports
• avoid file overwriting

Issues:

• [ ] #6472
• [ ] #6116
• [ ] #5861
• [ ] #4730
• [x] #4802
• [ ] #690
• [ ] #906
• [ ] #1152
• [ ] #1294
• [ ] #1666
• [ ] #2065
• [ ] #2216
• [ ] #2375
• [ ] #2363
• [ ] #6809
• [ ] #6045
• [ ] #4583
• [ ] #6392
• [ ] #8367
• [ ] #8373

Notes

Lockfiles

When fixing #6472, we should consider a design for lockfiles, so that different instances of running quarto (which happens often when running a VS code preview and a command-line render, like in our test suite) don't step on each other's toes.

• [ ] #8626 (.quarto should be versioned)

• [ ] #4632

Other things to do

• when doing notebook embedding, we currently do a lot of this kind of "file exists" reasoning. That should be a part of this planner instead.
• this is also involved in getting multiple versions of a same page to be rendered (dark + light, mobile + desktop, etc)

[mcanouil]

Discussions that would be addressed by this epic (Maybe worth opening explicitly an issue out of them)

• 3674

• 2171

• 2372

• 6944 (https://github.com/quarto-dev/quarto-cli/issues/10463)

Slightly related:

• 5273

---

• 2795

• 6793

• 6848

• 3568

---

PS: don't hide, simply edit/remove^^