Add Agentic Workflow Portfolio Yield workflow Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>

[mnkiefer]

• Inspect the reviewed import-handling code and current branch state
• Check recent workflow runs/logs for any relevant CI failures
• Run targeted existing tests to baseline the AWY scripts
• Restrict workflow import normalization to safe in-repo paths
• Run targeted tests for the modified code
• Reply to the addressed PR comment with the fixing commit hash
• Run final validation and summarize any remaining issues

[github-actions]

✅ smoke-ci: safeoutputs CLI comment + comment-memory run (25635492621)

Generated by Smoke CI for issue #31363 · ◷

[github-actions]

Comment Memory

CI lights the path
Green checks bloom at dawn
Quiet bots still sing

Note

This comment is managed by comment memory.

It stores persistent context for this thread in the code block at the top of this comment.
Edit only the text inside the backtick fences; workflow metadata and the footer are regenerated automatically.

Learn more about comment memory

Generated by Smoke CI for issue #31363 · ◷

[Copilot]

Pull request overview

Adds an “Agentic Workflow Portfolio Yield” workflow that deterministically scores and analyzes the repository’s agentic workflows (yield, overlap/drag, governance signals) and then produces an issue report, with optional OTel-backed evidence.

Changes:

• Introduces deterministic precompute/postcompute Python scripts to generate portfolio metrics and a markdown report.
• Adds a new scheduled/dispatchable agentic workflow that runs the scripts and creates a single report issue via safe outputs.
• Adds shared OTel observability import and initial unit tests for the scoring/parsing logic.

Show a summary per file

File	Description
scripts/aw_yield_precompute.py	New deterministic precompute: workflow discovery, frontmatter parsing, scoring, overlap detection, portfolio metrics.
scripts/aw_yield_postcompute.py	New deterministic postcompute: clamps scores, validates agent recommendations, generates report markdown + safe output payload.
tests/test_aw_yield_precompute.py	Unit tests for discovery/frontmatter parsing/import handling/scoring math/overlap clustering.
tests/test_aw_yield_postcompute.py	Unit tests for clamping, recommendation validation, and malformed agent-output handling.
.github/workflows/aw-portfolio-yield.md	New agentic workflow definition that runs weekly and on demand, producing a portfolio report issue.
.github/workflows/shared/otel-observability.md	Shared import that configures OTLP env/observability and an otel MCP server.
.github/workflows/aw-portfolio-yield.lock.yml	Compiled lockfile for the new workflow.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 7/7 changed files
• Comments generated: 3

[mnkiefer]

@copilot Restrict imports as suggested.

[Copilot]

Implemented in 4829ec1.

[github-actions]

Hey @mnkiefer 👋 — great work adding the Portfolio Yield agentic workflow! The implementation looks well-structured with the pre/post compute scripts, the lock workflow, and matching test coverage for both scripts. One thing that would really help reviewers:

• Add a PR description — the body currently contains only the agent's task checklist. A short human-readable summary explaining what the Portfolio Yield workflow does, why it's being added, and any relevant design decisions (e.g. the OTel observability additions in shared/otel-observability.md) would make this much easier to review and understand in the git history.

If you'd like a hand drafting it, you can assign this prompt to your coding agent:

Replace the PR body for github/gh-aw#31363 with a proper description. The description should:
1. Summarize what the Portfolio Yield agentic workflow does (precompute and postcompute stages, what metric/signal it computes).
2. Explain why this workflow is being added to the gh-aw portfolio.
3. Briefly note any notable implementation decisions, including the OTel observability integration added in scripts/shared/otel-observability.md.
4. List the key files added and their roles.
Keep it concise — 150–250 words is ideal.

Generated by Contribution Check · ● 5.7M · ◷