JavaScript runtime mode compatibility\n//\n// # Pass-Through Field Validation\n//\n// Several workflow frontmatter fields are \"pass-through\" fields - they are extracted\n// from frontmatter and passed directly to GitHub Actions without modification:\n// - concurrency: Workflow concurrency control\n// - container: Container configuration for jobs\n// - environment: GitHub environment configuration\n// - env: Environment variables\n// - runs-on: Runner selection\n// - services: Service containers\n//\n// These fields ARE validated during frontmatter parsing using JSON Schema validation\n// (see pkg/parser/schemas/main_workflow_schema.json). The schema catches:\n// - Invalid data types (e.g., array when object expected)\n// - Missing required properties (e.g., container missing 'image')\n// - Invalid additional properties (e.g., unknown fields in concurrency)\n// - Structure violations (e.g., runs-on as number instead of string/array/object)\n//\n// Schema validation happens in pkg/parser/schema_validation.go during frontmatter\n// parsing, so errors are caught at compile time rather than GitHub Actions runtime.\n// See pkg/parser/schema_passthrough_validation_test.go for comprehensive test coverage.\n//\n// # When to Add New Validation\n//\n// Add validation to existing domain files when:\n// - It fits the domain (e.g., package validation → pip_validation.go)\n// - It extends existing functionality\n//\n// Create a new validation file when:\n// - It represents a distinct validation domain\n// - It has multiple related validation functions\n// - It requires its own caching or state management\n//\n// # Validation Patterns\n//\n// The validation system uses several patterns:\n// - Schema validation: JSON schema validation with caching\n// - External resource validation: Docker images, npm/pip packages\n// - Size limit validation: Expression sizes, file sizes\n// - Feature detection: Repository capabilities\n// - Security validation: Permission restrictions, expression safety\n\npackage workflow\n","numLines":71,"startLine":1,"totalLines":71}}}

Failed to process file /tmp/gh-aw/mcp-logs/safeoutputs.log: EACCES: permission denied, open '/tmp/gh-aw/mcp-logs/safeoutputs.log'

Failed to process file /tmp/gh-aw/mcp-logs/mcpscripts.log: EACCES: permission denied, open '/tmp/gh-aw/mcp-logs/mcpscripts.log'

Failed to process file /tmp/gh-aw/mcp-logs/mcp-gateway.log: EACCES: permission denied, open '/tmp/gh-aw/mcp-logs/mcp-gateway.log'

GitHub MCP guard policy automatically applied for public repository. min-integrity='approved' and repos='all' ensure only approved-integrity content is accessible.

MCP Scripts Server Startup Log