Support auto-generation of agentics-maintenance.yml for target repository in SideRepoOps pattern

[yskopets]

Summary

When using the SideRepoOps pattern, the hosting repository manages agentic workflows that operate on a separate target repository. gh aw init / gh aw upgrade auto-generates agentics-maintenance.yml for the hosting repository, but there is no equivalent auto-generated maintenance workflow for the target repository.

Current Situation

In a SideRepoOps setup:

• agentics-maintenance.yml is auto-generated for the hosting repo ✅
• A maintenance workflow for the target repo must be created and maintained manually ❌

The target-repo maintenance workflow needs the same operations (disable, enable, update, upgrade, safe_outputs, create_labels, validate) but must:

• Use the GitHub App credentials to authenticate against the target repository
• Configure checkout to clone the target repository
• Set target-repo on all safe-outputs
• Use workflow_call so it can be invoked from the hosting repo

Currently this has to be hand-rolled and kept in sync with upstream agentics-maintenance.yml changes manually — which means it lags behind every gh aw upgrade cycle.

Proposed Solution

gh aw init / gh aw upgrade should detect when a SideRepoOps configuration is present (e.g. a TARGET_REPOSITORY env var or a checkout block pointing at an external repo in any workflow) and auto-generate a <prefix>-agentics-maintenance.yml variant pre-wired for the target repository, similar to how agentics-maintenance.yml is generated for the hosting repo.

Alternatively, expose a flag or config field (e.g. target-repo in the repository-level gh-aw config) that triggers generation of the target-repo maintenance workflow alongside the hosting-repo one.

Why It Matters

Without this, every gh aw upgrade cycle requires manually diffing agentics-maintenance.yml against the hand-rolled target-repo variant and porting changes across. This is error-prone and easy to forget, leading to the target repo's maintenance workflow falling behind.

---

Reported by Claude Sonnet 4.6

[pelikhan]

@copilot automatically infer the side repos from the checkout current sections in agentic workflows and generate the agentic maintenance workflows for the target-repo