`gh aw add` omits grader evaluator files from packages

[mnkiefer]

Summary

gh aw add installs a packaged workflow and its normal dependencies, but omits an evaluator script referenced by the workflow grader configuration:

graders:
  operational-value:
    run: .github/graders/example-operational-value.sh

The compiler validates and freezes this evaluator when compiling from the package source checkout. After package installation into a clean consumer, however, .github/graders/example-operational-value.sh is absent, so the installed workflow cannot compile or run its grader.

Reproduction

1. In a package repository, add an executable evaluator at .github/graders/example-operational-value.sh.
2. Register it from an included workflow using the configuration above.
3. Compile the workflow from the source checkout. This succeeds.
4. Install the package in a clean temporary Git repository:

gh aw add OWNER/REPO
test -f .github/graders/example-operational-value.sh
gh aw compile

Actual behavior

The packaged workflow is installed, but the referenced .github/graders/*.sh file is not. The file check fails and compilation rejects the missing evaluator path.

Expected behavior

Package dependency discovery should treat each grader run target as a package-owned file. gh aw add should install it at the registered relative path, and gh aw update should restore or update it consistently with other package-owned assets.

Impact

This blocks distribution of grader-enabled workflow packages. A direct source checkout works, so source compilation can pass while the package delivered to consumers is unusable.

Environment

• Observed against operational-value merge commit 5cd744cc263a9d1ec5660fbf5604eaceb6f83430.
• The locally built CLI reports v0.87.6.
• Reproduced in a clean temporary Git repository on macOS.

Acceptance criteria

• gh aw add installs evaluator files referenced by packaged workflows.
• gh aw update updates or restores those evaluator files.
• A clean consumer can compile the installed grader-enabled workflow.
• Package lifecycle coverage verifies the evaluator file contract.

[pelikhan]

@copilot ensure these scripts are included in resources