Address Holistic Review Workflow Feedback

[jeffhandley]

This draft collects and addresses feedback from the recently enabled Holistic Review automation. Maintainers are encouraged to push refinements directly to this draft while reviewing its results.

• 82c5abad5fd92186a4353353ef3fb630cd5546f2 calibrates complexity-versus-maintainability guidance, including the type of feedback expected for PR Optimize Guid formatting #125499 when its added complexity is not justified by the maintenance tradeoff.

Other feedback addressed in merged PRs

• Update code review skill guidelines for suggestions formatting #131035

Note

This PR description was generated by GitHub Copilot.

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
15 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

[Copilot]

Pull request overview

This PR refines the Holistic Review workflow guidance to more explicitly evaluate when additional complexity in a PR is justified by its goals, and updates the compiled lockfile accordingly.

Changes:

• Add explicit complexity-vs-maintainability tradeoff assessment guidance (including when to escalate to ⚠️ Needs Human Review) in the Holistic Review instructions.
• Regenerate the holistic-review.lock.yml metadata to reflect the updated workflow source.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
.github/workflows/holistic-review.md	Adds guidance instructing reviewers to explicitly assess whether added complexity is proportionate and well-justified, and when to escalate for maintainer judgment.
.github/workflows/holistic-review.lock.yml	Updates the generated lock metadata (hash) corresponding to the workflow text change.

[MihaZupan]

Is there consideration for having it not post a comment at all if it's deemed not actionable by the LLM itself? Or would you still want it to always post, but perhaps with less verbosity?

E.g. in #130802 (review) there's a whole page of text for what boils down to Detailed Findings: None.
I also don't see much value in having it restate what the PR is doing, assuming that it matches what the description says, because the Copilot reviewer already posts a similar summary as a comment anyway, e.g. #130802 (review)