The helper the five linked-card cursors share memoized its result per board, to spare them the duplicate queries the five copies of that preamble used to make. That is wrong: publishComposite re-runs a child’s find() when the parent document changes, and a cache living for the whole subscription then serves the ids computed the FIRST time forever - a linked card added later would never be published, and one removed would go on being published.

The five cursors each ran these same queries before the helper existed, so computing per call is exactly the cost they always had, and it is correct. The guard that pinned the memoization now pins its absence, with the reason, so the next reader does not put it back.

The one red suite in the full test run, and it was right twice over.

The commit that replaced Update git with a git pull and a git push that finish the job added both to build.sh’s menu and left build.bat behind, so build.bat git-pull answered nothing. It answers to both names now, with its own :gitpull / :gitpush labels - the ones its interactive menu already used.

The guard also had to learn what a ! entry is. It marks something build.sh runs ITSELF rather than by executing a file in releases/. Most are raw commands and the .bat runs those the same way, so those still compare as before; the exception is an entry naming a build.sh FUNCTION, which is shell the .bat has no way to call. Comparing those as scripts is what made the suite fail the moment Update git was replaced. A function entry is exempt from the script comparison now and checked separately: build.bat must implement a label of the same name, so one dropping out of a menu still fails.