fix: declare run_shell_command in board-meeting agent frontmatter

[xiaolai]

Automated: drive-by fix from NLPM, an NL artifact linter. Reviewed and reproduced before submission.

Bug: Phase 5 of agents/board-meeting.md explicitly instructs run_shell_command mkdir -p conductor/tracks/{trackId}/.message-bus/board/ but run_shell_command is absent from the frontmatter tools list — only read_file and write_file are declared; the mkdir call is unauthorized at runtime and fails silently.

Evidence: grep -n "run_shell_command" agents/board-meeting.md → line 89 confirms the call; frontmatter tools (lines 5–7) list only read_file and write_file.

Fix: Added run_shell_command to the tools list in the frontmatter.

[gemini-code-assist]

Code Review

This pull request adds the run_shell_command tool to the board-meeting.md agent configuration. A review comment suggests also including the Task tool in the tools list, as it is utilized in the agent's workflow for dispatching assessments but was missing from the declaration.

[gemini-code-assist]

The Task tool is also used in Phase 1 (lines 33-37) to dispatch assessments to the directors, and it is explicitly referred to as the "Task tool" in the board-of-directors skill definition (line 35 of skills/board-of-directors/SKILL.md). Similar to run_shell_command, it should be declared in the tools list to ensure the agent has the necessary permissions to invoke it at runtime.

Suggested change

	- run_shell_command
	- run_shell_command
	- Task