fix: remove reports/user-test-sarah, and fetch the merge-tag artifact on deploy

Two unrelated corrections, both consequences of the same mistake.

`git add -A` in the previous merge-tags commit swept in work that had nothing to
do with it: reports/user-test-sarah/ (a user-test writeup and 11 screenshots)
and additions to AGENTS.md, published to main under a commit message about the
merge-tag fetcher. Removing the reports directory at Zack's direction. It
remains in history at 5637c2f, so this does not unpublish it; a copy was also
taken outside the repo before removal. The AGENTS.md notes are left in place --
they are accurate documentation and belong here regardless of how they arrived.

The fetch now runs as its own deploy step with MERGE_TAGS_TOKEN, rather than
chained into docs:generate where it took the whole site build down when the
secret did not exist yet. The script still fails hard on a bad fetch: an empty
catalog would render as a product with no merge tags, which reads as a fact
rather than a broken build.

Author: zackkatz

.github/workflows/deploy.yml

@@ -51,6 +51,15 @@ jobs:
       - name: Generate hooks documentation
         run: npm run docs:generate
 
+      # Kept as its own step rather than chained into docs:generate, so a fetch problem is
+      # attributable and cannot take the rest of the site's build down with it by accident.
+      # The script itself still fails hard on a bad fetch: an empty catalog would render as a
+      # product with no merge tags, which reads as a fact rather than a broken build.
+      - name: Fetch the merge-tag artifact
+        env:
+          MERGE_TAGS_TOKEN: ${{ secrets.MERGE_TAGS_TOKEN }}
+        run: npm run merge-tags:generate
+
       - name: Generate relationship graphs for LLMs
         run: npm run relations:generate