Description
At 8e7d13e2d46e9539b1d790a9524ecaccd908c7e9 was possible with X scope resolution, but we dropped it in the next commit because we noticed that cross include toc headers were broken because we were not scooping the entry point.
So to make this work we would have to separate the includes ID fetch from the other ID fetches, and then make the RECURSIVE call either: on a separate non-parallel query (or some very insane and smart join JOIN) because we need to identify which one is the resolved input.
Another alternative would be to instead of scope resolution allow relative paths as in:
\Include[../top]
We should then fetch the File entry from the DB, and see its corresponding ID all in one join, rather than trying to derive the ID from href, which forces us to redo scope resolution.
This relative path approach is likely the saner one.