[plan] Document tool restrictions in included_file_schema.json

[github-actions]

Objective

Add schema descriptions explaining why only 4 of 13 tools are available in included files, or expand tool support if the restriction is unintentional.

Context

Priority: MODERATE
Category: Feature Parity / Documentation

Currently:

• Main Schema: 13 tool configuration properties
• Included Schema: 4 tool configuration properties (bash, cache-memory, github, repo-memory)

Missing Tools: agentic-workflows, edit, playwright, safety-prompt, serena, startup-timeout, timeout, web-fetch, web-search

It's unclear if this restriction is intentional design or an oversight, and there's no documentation explaining the limitation.

Approach

Option 1: If restriction is intentional

1. Add description field to the tools property in included_file_schema.json
2. Document why included files have restricted tool access
3. Explain which tools are available and why others are excluded

Option 2: If restriction is unintentional

1. Add missing 9 tool properties to included_file_schema.json
2. Copy tool definitions from main_workflow_schema.json
3. Test that all tools work correctly in included files

Decision Criteria:

• Review codebase to determine if there's a technical reason for the restriction
• Check if included files have access to tool implementations
• Consult with maintainers if needed

Files to Modify

• Update: pkg/parser/schemas/included_file_schema.json
  • Add description to tools property (Option 1)
  • OR add 9 missing tool properties (Option 2)

Acceptance Criteria

• Tool restrictions are clearly documented in schema
• OR all 13 tools are available in included files
• Decision rationale is captured in commit message
• Schema validates correctly
• No breaking changes to existing workflows

Research Questions

Before implementing, investigate:

1. Are there technical limitations preventing tool use in included files?
2. Is this a security boundary (included files as untrusted)?
3. Are the 9 missing tools actually used in the codebase?

---

AI generated by Planning Assistant
Related to #7944

AI generated by Plan Command for discussion #7935