meadow markdown export type -- published to site as zip file

^ link not tracked -- published to site as .zip file

Changes from the original source graph's markdown:

• SRS
  • In meadow workflow -- SRS markdown to SRS interactive elements on the published site then the SRS modification to markdown removes the SR comments from the markdown which affects this markdown
• Avoid sensitive stuff
  • link not tracked

Things that should not be changed from the original source graph's markdown

• no link not tracked markdown files should be in the markdown. Those are only needed for supporting link not tracked of tag-like pages, for navigation.

Process verification

These two things are complex enough that we bias towards link not tracked. First, we export the resultant markdown to a link not tracked, so that we can use it to do a git changes test against golden-set test in the system tests (and also to do quick manual inspections). That directory gives a kind of link not tracked with just enough of the intermediate process state exposed to make it testable, so we can be confident that we're not link not tracked.

After that, that directory's content is what is actually zipped up to make the final .zip that it adds to the link not tracked. That ought to make careful testing easier. Again, the strong emphasis on clear verification here is because of the high link not tracked.