DP-002: Resolve GitHub Actions runner startup failure

[altmanAI]

Summary

GitHub Actions is creating workflow runs for PR #3, but jobs fail before any workflow step executes.

Evidence

Run 1

• Run ID: 29259034440
• Workflow: DailyPilot Engine CI
• Jobs: Python 3.10 and Python 3.12
• Result: both failed
• Connector returned no steps and job logs were unavailable

Run 2

• Run ID: 29259157659
• Workflow: DailyPilot Engine CI
• External actions were removed and replaced with shell-only public checkout
• Result: job failed before execution
• Connector again returned no steps or job logs

Because two materially different workflow definitions failed before step execution, the evidence points to a repository/account runner, Actions policy, billing, or platform startup condition rather than a Python code or test failure.

Independent validation

The PR #3 implementation was reconstructed in an isolated local environment and validated with:

• Python compilation
• python -m pytest -q: 6 passed
• python dailypilot_cli.py sample_day.json --profile worker_double_shift: completed successfully and wrote a local run log

Required action

Review GitHub Actions availability and settings for altmanAI/DailyPilot-Engine, including:

• whether Actions are enabled;
• allowed-actions policy;
• account or repository billing/spending restrictions;
• runner availability;
• any startup restriction shown in the GitHub Actions UI.

Merge gate

PR #3 should remain open until the hosted CI runner executes successfully or an attributable exception is approved with the infrastructure limitation documented.

Authorization context

The implementation is authorized under ALL CLEAR FOR IMPACT, but authorization does not waive validation or accurate reporting.