chore: ignore the generated graphify knowledge graph

[UsamaSadiq]

Description

Adds graphify-out/ to the committed .gitignore.

The generated knowledge graph was previously ignored only via .git/info/exclude, which is local to a single clone and never shared. On any other machine the directory is untracked and unignored, so a broad git add commits it.

This is prevention, not a fix: this sandbox was never at risk, because the local exclude was in place here. The gap is real elsewhere, though. It let 5,503 graphify files (51.6 MiB, graph.json at 823,266 lines) into Pressingly/zammad foss-sandbox, which had no exclude entry. Committing the rule makes the protection travel with the repo.

outline and foss-server-bundle already carry this line.

Testing

git ls-files | grep -i graphify returns nothing, so no tracked path is affected. git check-ignore -v graphify-out/ confirms the new line is the matcher. The pattern is unanchored, so it also catches the stray nested graphify-out/ directories at any depth.

[github-actions]

	Fails
🚫	node failed.

Log

Details

�[31mError: �[39m SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
    at JSON.parse (<anonymous>)
�[90m    at parseJSONFromBytes (node:internal/deps/undici/undici:4394:19)�[39m
�[90m    at successSteps (node:internal/deps/undici/undici:7048:27)�[39m
�[90m    at readAllBytes (node:internal/deps/undici/undici:5965:13)�[39m
�[90m    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)�[39m
danger-results://tmp/danger-results-ddab2bbd.json

Generated by 🚫 dangerJS against 491089f