chore(graphify): commit codebase knowledge graph + project integration

[altaskur]

Make Graphify's knowledge graph part of the repo so collaborators (and their AI assistants) get it with zero setup:

• Commit the generated graph under graphify-out/ (graph.json, interactive graph.html, GRAPH_REPORT.md, manifest.json). 1439 nodes / 2274 edges, built locally from the code (AST, no API cost).
• Add a ## graphify section to CLAUDE.md so AI assistants query the graph before grepping and refresh it after code changes.
• Document the one-time, per-machine CLI setup (uv tool install graphifyy) and graphify update . refresh in CONTRIBUTING.md — the tool is global, not an npm dependency, so reading the graph needs nothing but regenerating needs the CLI.
• .gitignore the per-machine internals (graphify-out/cache/, dotfiles) and .claude/settings.json (graphify writes machine-specific absolute paths and per-tool hooks there — kept local, not shared).
• .gitattributes marks the graph outputs as generated / no-diff so PRs stay readable; .prettierignore and eslint ignore graphify-out/ so the committed outputs don't trip the lint hooks.

Description

Goal

Key Changes

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📝 Documentation update
• 🎨 Style/UI changes
• ♻️ Refactoring (no functional changes)
• ⚡ Performance improvement
• ✅ Test updates
• 🔧 Build/configuration changes

Impact Assessment

Database Impact

• No database changes
• New migration(s) included
• Existing data migration required

Backup Impact

• No impact on backups
• Backup format changed
• Restore compatibility maintained

Testing

How Has This Been Tested?

• Unit tests
• Integration tests
• Manual testing
• Tested with SonarQube analysis

Test Steps

Test Configuration

• Node version:
• npm version:
• Platform tested:

UI Changes

Before

After

Checklist

• My code follows the project's coding standards
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings or errors
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have run npm run lint and fixed any issues
• I have run npm test and all tests pass
• I have run npm run test:electron and all tests pass
• I have run npm run sonar:check and the analysis passes
• Any dependent changes have been merged and published

Breaking Changes

• This PR contains breaking changes

Related Issues

Closes #
Related to #

Additional Context

Reviewer Notes