Forge: materialize tool-call actions

[GolaraJ]

Summary

• recognize the extraction controller’s canonical tool-calls action kind
• update the end-to-end spilled tool-result test to use the real controller contract

Root cause

The result was found successfully after PR #20, but the materializer rejected the action before parsing because it expected tools while extraction-controller.py emits tool-calls.

Validation

• 43 Skill Forge tests pass
• Python scripts compile
• git diff --check passes

[Copilot]

Pull request overview

Updates the session-query materializer and its end-to-end “spilled tool-result” test to align with the extraction controller’s canonical action kind (tool-calls), resolving a contract mismatch where the controller emitted tool-calls but the materializer expected tools.

Changes:

• Switch materialization parsing to recognize the tool-calls action kind and its expected result columns.
• Update the spilled tool-result integration test fixture to emit kind: "tool-calls" in actions.json.

Show a summary per file

File	Description
plugins/repo-dreamer/skills/repository-skill-forge/tests/test_materialize_session_query.py	Updates the test action fixture to use the controller’s tool-calls kind.
plugins/repo-dreamer/skills/repository-skill-forge/scripts/materialize-session-query.py	Renames the parsed action kind from tools to tool-calls (both header expectations and row parsing branch).

Review details

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

• Files reviewed: 2/2 changed files
• Comments generated: 0
• Review effort level: Lite