Remove top-level project: field in favor of explicit safe-outputs configuration

[Copilot]

Remove Top-Level project: Field

The top-level project: field automatically configured update-project and create-project-status-update safe-outputs. This removes it in favor of explicit configuration.

Changes

• Schema: Removed top-level project property (323 lines), marked project as required in safe-outputs
• Code: Removed automatic injection logic, clarified that each safe-output must explicitly configure its own project URL (916 lines net deletion)
• Documentation: Removed legacy references, marked project: as required in all docs
• Examples: Migrated 4 workflows to explicit safe-outputs configuration
• Error Messages: Updated to reference safe-outputs configuration instead of frontmatter

Migration Guide

Before:

project: https://github.com/orgs/myorg/projects/123
safe-outputs:
  create-issue: {}

After:

safe-outputs:
  create-issue: {}
  update-project:
    project: https://github.com/orgs/myorg/projects/123  # required
    max: 10
  create-project-status-update:
    project: https://github.com/orgs/myorg/projects/123  # required
    max: 1

Validation

• Schema validation enforces project as required - workflows won't compile if missing
• No cross-fallback between safe-output types - each must explicitly configure its own project URL
• Agent messages can optionally override the configured project URL per-message

Original prompt

Remove top-level project: feature, we will stick to the standard url decladation in safe-outputs: update-project: url: etc.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[mnkiefer]

@copilot Update the docs accordingly. Don't include legacy, deprecated with respect to top-level project: feature, just update individual project related safe outputs, ensuring they now have the project: property required.

[Copilot]

@copilot Update the docs accordingly. Don't include legacy, deprecated with respect to top-level project: feature, just update individual project related safe outputs, ensuring they now have the `pr...

Updated in commit 2fcff7f:

• Removed all references to the legacy top-level project: field from documentation
• Marked project: property as required in both update-project and create-project-status-update safe-outputs configurations (in schema and docs)
• Updated safe-outputs.md to clarify that project is required in the configuration (agent messages can optionally override it)
• Regenerated frontmatter-full.md from the updated schema - project field now shows without "(optional)" marker

The project: property is now consistently documented as required in safe-outputs configuration throughout all docs.

[mnkiefer]

@copilot There should be no default project value to fallback on when user forgets to add project to it's update-project, etc. safe outputs.

[Copilot]

@copilot There should be no default project value to fallback on when user forgets to add project to it's update-project, etc. safe outputs.

Addressed in commit 58754c9:

• Schema validation enforces project as required - workflows fail to compile if users forget to add it
• Updated code comments to clarify that each safe-output must explicitly configure its own project URL (no cross-fallback between update-project and create-project-status-update)
• Updated error messages in handlers to reference "safe-outputs configuration" instead of "frontmatter"
• Updated test expectations to match the new messaging

The GH_AW_PROJECT_URL environment variable is still set from the configured project URL (for use by agent messages that choose to omit the project field), but there is no default fallback if the configuration is missing - the schema validation prevents compilation.