[Summary] Next issues and PRs to solve, prioritized

[danielmeppiel]

FIX-NOW execution status (board-authorized waves) -- WAVE 2 COMPLETE

Wave	PR	Status	Notes
1	#635	CLOSED	Author missed CLA window. Replaced by #1068.
1	#947	MERGED	Lint + 3 Copilot findings + UX audit folded in single PR.
1	#991	MERGED	Admin-override squash-merge. CI green.
1	#931	CLOSED-OBSOLETE	Already on main via #1020.
1	#1055	MERGED	Admin-override squash-merge. CI green.
1	#1065	MERGED	Consolidated retro-fix (Copilot review on #1055/#991/#1065 itself).
2	#937	MERGED	Maintainer-pushed fix: 2 remaining InstallScope.USER guards now allow absolutes; E2E asserts deployment (closes the test gap that let the bug ship). 6858 unit + 20 E2E pass.
2	#608	CLOSED-WONTFIX	Stale author-branch merges deleted ~10 panel/agent infra files. Issue #605 stays valid but deprioritized.
2	#1068	MERGED	Successor to #635: 15 open() sites across 5 modules get encoding="utf-8" + 9 CJK round-trip tests + Copilot review (raw CJK literals -> \uXXXX escapes per repo encoding rule) folded.

Cumulative outcome: 7 PRs merged (#947, #991, #1055, #1065, #937, #1068, plus tracked #931). 2 closed-obsolete/wontfix (#931, #608). 1 successor opened+merged (#1068).

Plan-v4 inputs captured for wave 3:

1. Last-pusher rule (wave 1): orchestrator must NOT both push lint commits AND approve final SHA -- branch protection rejects with "Waiting on 1 reapproval". Board admin-merge is the only safe path when orchestrator pushes.
2. Fold-not-followup (wave 1): Copilot review findings + UX-audit recommendations fold into the open PR (or one consolidated retro PR if source already merged).
3. Copilot-review gate (wave 1): mandatory pre-merge for all PRs even when dissenting lens approves.
4. Parallel UX subagent (wave 1): when a fix touches user-facing surface, spawn devx-ux-expert in parallel; findings fold into the same PR.
5. Real-asset reproduction is required as merge-evidence (wave 2): unit/E2E tests can pass against broken behavior if they assert the wrong thing. The fix(install): allow local packages at --global scope; fix broken tests #937 deployment-vs-manifest gap is the canonical example.
6. Maintainer-push when author silent (wave 2): for fork PRs where author is non-responsive, orchestrator pushes via gh-authenticated SSH to the fork (Co-authored-by credit). Worked on fix(install): allow local packages at --global scope; fix broken tests #937. Successor PR pattern (close + replace from microsoft/apm) only when fork-push impossible (the Standardize Unicode encodings to explicitly use UTF-8 #635 -> fix: extend explicit UTF-8 encoding to 5 remaining open() call sites #1068 path).

[github-actions]

Triage Panel Verdict -- Issue #1064

Summary: Synthesized planning summary generated by an agentic CEO+DevX panel run. Documents the outcome of a "FIX-NOW" PR merge wave (4 merged, 1 closed-obsolete, 2 returned to authors) and provides a ranked backlog of 33 open PRs for maintainer action. Operational/informational artifact, not a user-reported bug or feature request.

Panel findings

DevX UX Expert: This is a useful maintainer reference document. The PR ranking table (MERGE NOW / MERGE SOON / NEEDS WORK / DOCS-AUTO / HOLD) provides clear action guidance. No UX changes implied; this is a tracking artifact.

Supply Chain Security Expert: The HOLD section correctly flags #691 (URL-based marketplace, 3634L, needs design) and #881 (marketplace pinning doctor, supply-chain concern). These are already in the right bucket. No new supply-chain issues introduced.

APM CEO: Good synthesis artifact. The strategic flags are accurate -- 6 of 11 FIX-NOW issues have zero PR coverage, and the Codex-asymmetry bug (#1062, already filed and triaged this sweep) is correctly called out. Maintainers should use this as a reference for sprint planning. Consider closing once the described wave is fully resolved to avoid stale planning docs accumulating.

Triage decision

Dimension	Decision
Type	type/automation
Area	area/ci-cd
Priority	None (planning artifact)
Milestone	None
Status	status/triaged

Suggested next action: Use this as a reference for PR prioritization. Close the issue once the FIX-NOW wave described in the body is resolved (all MERGE-NOW items addressed).

---

Triage status: agentic proposal pending human ratification.
Silence is approval. Maintainers can:

• Override any label or milestone above by editing it directly --
  human edits are authoritative and will not be reverted on
  subsequent runs.
• Re-trigger triage by applying the status/needs-triage label, or
  by removing status/triaged to enroll the issue in the next
  daily sweep.

Posted by the Triage Panel workflow. See .apm/skills/apm-triage-panel for the panel skill.

Note

🔒 Integrity filter blocked 43 items

The following items were blocked because they don't meet the GitHub integrity level.

• [FEATURE] Extended MCP Server Configuration in apm.yml #20 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• [FEATURE] Allow install to download and unpack a GitHub release automatically #514 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• [FEATURE] Skills from .well-known URIs #554 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• Feature: per-target agent frontmatter transformation during deployment #581 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• bug: apm run start picks wrong runtime — system PATH stub takes priority over APM-managed binary, codex v0.116+ incompatible with GitHub Models #605 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• [FEATURE] Add ability to specify a different configuration file name or path #612 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• bug: apm install plugin@marketplace validation bypasses registry proxy #615 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• [FEATURE] Renovate supporting apm.yml #639 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• [FEATURE] MCP install target for Claude Code (project + user scope) #643 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• Align CONTRIBUTING, Python formatting (Black/isort), and CI #645 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• [FEATURE] Copilot CLI user-scope instructions: can apm install -g write copilot-instructions.md #650 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• Marketplace add source parity with the Anthropic spec #676 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• [FEATURE] PEP 8 Support #690 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• [FEATURE] URL-based marketplace work Extension #692 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• [FEATURE] Create root AGENTS.md documenting all CI-enforced rules for coding agents #695 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• [FEATURE] Kiro Support #702 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• ... and 27 more items

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Triage Panel · ● 796.9K · ◷