[aw-daily] GAP-5: gh-aw-architecture.md missing SideRepoOps context documentation (workflowRepo vs eventRepo)

[github-actions]

Gap Details

Type: missing (priority 3)
File: .claude/skills/gh-aw-report/references/gh-aw-architecture.md
Section: gh-aw CLI Extension or Safe-Outputs System

Current Content

The architecture file does not document the SideRepoOps context concept (workflowRepo vs eventRepo distinction) used in gh-aw comment scripts and workflow operations.

Expected Change

Add documentation about SideRepoOps context:

SideRepoOps Context (workflowRepo vs eventRepo)

gh-aw provides a native SideRepoOps context that distinguishes between:

• workflowRepo: The repository where the gh-aw workflow is defined
• eventRepo: The repository that triggered the event (may differ in cross-repo scenarios)

This context is used internally for comment scripts and is particularly relevant for cross-repository safe-output operations. The distinction matters when using target-repo or allowed-repos in safe-outputs, or when writing workflows that operate across repositories.

Note: SideRepoOps was refactored for native context in gh-aw PR #26953 (2026-04-18).

Source

• github/gh-aw@029129a (Refactor comment scripts for native SideRepoOps context)

Acceptance Criteria

• SideRepoOps context documented in gh-aw-architecture.md
• workflowRepo and eventRepo distinction explained
• Cross-repo implications noted

Generated by Daily Intelligence Pipeline · ● 4.3M · ◷

[github-actions]

⚠️ Assignment failed: Failed to assign copilot coding agent to this issue.

Error: copilot coding agent is not available for this repository