Fix PR Review Panel: emit advisory comment via add_comment tool, not a shell heredoc

[Copilot]

Description

The PR Review Panel workflow's agent job terminated unexpectedly (run 27815857237, 33m / 144 turns, no comment posted). gh aw audit shows the CEO synthesizer produced a valid needs_rework recommendation, but the orchestrator then staged the rendered comment body in a temp file with a shell heredoc:

cat > /tmp/gh-aw/agent/panel-comment.md << 'COMMENT_EOF'
... correctness bugs silently kill the feature's display layer ...

The copilot engine's bash command-safety parser scans command text (heredoc bodies included) and read a word-wrapped line beginning with kill as a real command, refusing it: "Command not executed. The 'kill' command must specify at least one numeric PID." The comment never emitted and the run failed. The add_comment safe-output tool already takes the body as a structured argument, so panel prose never needs to touch the shell.

Changes (prose-only in the skill):

• apm-review-panel SKILL step 7 — mandate emitting the single comment by passing the rendered markdown directly to the add_comment tool's body argument; forbid staging/piping it through the shell (cat <<EOF, printf, echo, temp .md files), with the kill/rm/sudo parser hazard called out.
• New Gotcha documenting the failure mode and citing run 27815857237.
• Mirrored both edits into the installed .agents/skills/apm-review-panel/SKILL.md copy (kept byte-identical).
• Removed accidentally-committed gh aw audit artifacts under .github/aw/logs/ and gitignored that path.

No workflow recompile needed — the workflow imports the skill from microsoft/apm#main at runtime, so .lock.yml is unaffected.

Type of change

• Bug fix
• New feature
• Documentation
• Maintenance / refactor

Testing

• Tested locally
• All existing tests pass
• Added tests for new functionality (if applicable)

Spec conformance (OpenAPM v0.1)

If this PR changes behaviour that an OpenAPM v0.1 req-XXX covers,
confirm the three-step ritual (see CONTRIBUTING.md "Adding or
changing a normative requirement"):

• Spec edit: docs/src/content/docs/specs/openapm-v0.1.md updated
  (new/changed <a id="req-XXX"></a> anchor + prose + Appendix C
  row).
• Manifest edit: docs/src/content/docs/specs/manifests/openapm-v0.1.requirements.yml
  updated.
• Test edit: a @pytest.mark.req("req-XXX") test under
  tests/spec_conformance/ added or extended.
• CONFORMANCE.{md,json} regenerated via
  uv run --extra dev python -m tests.spec_conformance.gen_statement
  and committed.
• N/A -- this PR does not change OpenAPM-observable behaviour.

[Daniel Meppiel (danielmeppiel)]

Superseded by #2897, which preserves this proposal's distinct structured-comment safeguard.

At replacement commit 3ca8dd44efb55a66ee30b3345a65574c2b3fd374, the canonical panel skill requires complete final markdown directly in structured add_comment.body: no shell staging, wrapper, or intermediate comment file. Missing, failed, or uncertain configured safeoutputs do not authorize a direct-write fallback. Incident run 27815857237 remains documented.

The deployed skill, canonical and compatibility hashes in apm.lock.yaml, and transport/provenance regression preserve the current package authority without recreating historical mirror paths.

Replacement evidence: the final current-head advisory, exact-head CI, and published APM 0.30.0 panel-resource roundtrip. The same nine retained reviewers and final CEO synthesis are complete. Local real-process restoration preserved all 12 actual package files; hosted deterministic compatibility covers four required files. Neither local CLI advisory delivery nor those checks is presented as hosted AI safe-output execution.

Closing this superseded proposal only, under the recovered preservation-and-linking authority. #2897 is ready for human review, not accepted or merged: CODEOWNER and independent last-push approvals remain outstanding. The fresh trusted-main #2741 AI exercise remains a post-merge human rollout obligation.

Original branch copilot/sergio-sisternes-epamfeat-installation-analytics-h and commit e00f905f97eefa6347013ab7a51f83152ce9e898 remain intact. No merge or branch deletion.