Implement create-project safe output for campaigns

[Copilot]

Plan: Implement create-project safe output for campaigns

• Create new create-project safe output type
  • Add Go backend configuration
  • Create JavaScript implementation
  • Add schema validation
  • Add tool definitions
  • Wire up to compiler
• Update campaign-generator.md to use create-project
• Update agent instructions
• Test compilation
• Run campaign tests
• Remove hardcoded organization (make flexible for user/org projects)

Implementation Complete

Created a new create-project safe output that creates empty GitHub Projects V2 boards. This is distinct from:

• copy-project: Copies from a template project (preserves all fields/views)
• update-project: Updates/creates projects (smart management)
• create-project: Creates new empty projects (campaigns)

The distinction clarifies the use case: campaign-generator creates new empty projects, while campaign orchestrators update existing projects with items and fields.

Flexibility: The campaign generator now dynamically determines the project owner using github.owner, allowing it to work with any repository owner (organization or user) based on the provided token permissions.

---

💡 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.

[pelikhan]

You want update or create project?

[mnkiefer]

You want update or create project?

Here, we create_project (campaign generator). The campaign itself does update_project for adding items to the board, filling fields, etc. (campaign orchestrator).

[mnkiefer]

@copilot: Use create_project, not update-project.

[Copilot]

@copilot: Use create_project, not update-project.

Done! Created a new create-project safe output (commit 13f2356).

The distinction is now clear:

• create-project: Creates new empty project boards (campaign generator)
• update-project: Updates existing projects with items/fields (campaign orchestrators)

Campaign generator now uses create_project() to create empty boards instead of copying from a template.

[mnkiefer]

@copilot: Depending on the token provided, we can create user-owned or org-owned projects. Remove hardcoded org "githubnext".

[Copilot]

@copilot: Depending on the token provided, we can create user-owned or org-owned projects. Remove hardcoded org "githubnext".

Done! Removed hardcoded "githubnext" organization (commit c9c37fb).

Changes:

• Removed target-owner: "githubnext" from frontmatter
• Agent now uses ${{ github.owner }} to dynamically determine project owner
• Supports both user-owned and org-owned projects based on token permissions
• Item URL constructed from allowed expressions: ${{ github.server_url }}/${{ github.repository }}/issues/${{ github.event.issue.number }}

The workflow is now flexible and works with any repository owner.