fix hook context output - Fixes #533

[danielmorozoff]

Summary

• Fix PreToolUse hook output to emit top-level systemMessage instead of unsupported hookSpecificOutput.additionalContext.
• Add a regression test covering unsupported hook fields.
• Ignore local assistant artifacts in .gitignore.

Why

Newer CLI versions reject hook output containing additionalContext with:

PreToolUse hook returned unsupported additionalContext

The generated hook had regressed to a Claude-specific output shape.

Validation

• .venv/bin/pip install -e '.[all]'
• .venv/bin/pip check
• env HOME=/tmp/graphify-pytest-home .venv/bin/python -m pytest -q
• .venv/bin/graphify update .
• Smoke-tested the platform install and verified the generated hook output contains systemMessage and no additionalContext.

Fixes #533
Resolves #533

[qodo-ai-reviewer]

Hi, test_codex_agents_install_writes_supported_hook_output only asserts substrings on str(hooks) and never validates the JSON that the hook command actually echoes at runtime, so malformed/invalid echo output can ship while tests still pass. This undermines the regression coverage for the Codex CLI schema error this PR is trying to prevent.

Severity: remediation recommended | Category: correctness

How to fix: Parse and validate echoed JSON

Agent prompt to fix - you can give this to your LLM of choice:

Issue description

The regression test verifies only stringified Python structures from hooks.json, not the actual JSON emitted by the hook command at runtime.

Issue Context

The Codex hook is a shell command that echos a JSON object; Codex rejects unsupported fields at runtime. The test should validate the command’s emitted JSON (at least syntactically, ideally also schema-wise for allowed keys).

Fix Focus Areas

• tests/test_install.py[132-145]
• graphify/main.py[704-717]

Suggested approach

• In the test, locate the hook command string (e.g., hooks[0]["hooks"][0]["command"]).
• Extract the echoed JSON literal and json.loads(...) it, then assert the resulting dict contains only supported keys (e.g., {"systemMessage"}) and explicitly does not contain additionalContext, hookSpecificOutput, permissionDecision.
• Optionally, execute the command via subprocess.run(..., shell=True, cwd=tmp_path, check=False) with a created graphify-out/graph.json to ensure the && branch runs, and then parse stdout as JSON.

---

Found by Qodo code review