Context

Closes part of #18481 — gh-aw in forks.

The agentics-maintenance workflow (.github/workflows/agentics-maintenance.md / .lock.yml) runs on a schedule every 2 hours. When a repo with gh-aw installed is forked, this workflow is automatically copied to the fork and runs without the necessary secrets, causing noisy failures.

Objective

Add a fork detection step at the very beginning of the agentics-maintenance workflow that exits early with an informational message when running inside a fork.

Approach

1. Add a step at the top of agentics-maintenance.md (or directly in the compiled lock file if more appropriate) that checks github.event.repository.fork.
2. If true, print an info message explaining that agentic maintenance is skipped in forks and exit the job cleanly (exit 0 / continue-on-error or a conditional job guard).
3. Recompile: make recompile
4. Validate the compiled .lock.yml contains the fork guard step.

Acceptance Criteria

• agentics-maintenance workflow has a fork-detection step as its first step
• When github.event.repository.fork == true, the workflow logs a clear info message and skips all subsequent steps
• The compiled lock file reflects the change
• No regression in normal (non-fork) operation
  Related to Using gh-aw in forks of repositories #18481

Generated by Plan Command for issue #18481

• expires on Feb 28, 2026, 4:18 PM UTC