- Add `$GITHUB_JOB` to the ## heading in all build and promote summaries so jobs sharing the same action are distinguishable
- Add missing `generate-summary` input to build-gradle, build-npm, build-poetry, build-yarn (was already present in build-maven). Generalize #222
- Fix bug: build-npm/poetry/yarn summary checked non-existent output `should-deploy`; corrected to `deployed`. Fix #136
- Fix build-yarn: missing blank lines before outputs: and summary step

Update README for workflow summary changes

- Document `generate-summary` input in build-maven, build-gradle, build-npm, build-poetry, and build-yarn Inputs tables
- Add "GitHub workflow job summary" entry to Features sections for build-maven, build-gradle, build-npm, build-yarn, and promote

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Remove all ### Features sections that were either redundant with the action description or contained generic boilerplate. Rescue the
branch-strategy information from build-maven as a proper Deployment Strategy table, and rescue the build-gradle gradlew fallback note
into the action description.

Move Deployment Strategy to standalone section and fix inaccuracies

Move the deployment strategy table out of build-maven into a shared standalone section (grouped with Provenance Attestation) since it applies
to all build actions.

Fix inaccuracies verified against implementation:
- feature/long/* branches DO deploy (was incorrectly marked as no)
- "master" renamed to "Default branch" (configured via DEFAULT_BRANCH)
- Remove Maven-specific "Notes" column that did not apply to other actions
- Add build-gradle exception: sonar analysis not branch-filtered in Gradle

Note build-gradle sonar branch filtering as a known bug

Add a TODO comment in build-gradle/build.sh and update the README to flag that sonar analysis is not filtered by branch type in build-gradle,
unlike all other build actions. Should add a should_scan() guard to skip sonar on dogfood/other branches consistently.

Fix deploy input verification: document inconsistencies and add TODOs

- Fix README Deployment Strategy table: long-lived feature branches only deploy for build-maven and build-gradle, not for build-npm/build-yarn/build-poetry
- Add note that deploy:'false' override is only supported by build-maven and build-gradle
- Add TODO comments to build-npm, build-yarn, build-poetry noting the missing DEPLOY env var support and long-lived feature branch deploy discrepancy

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Convert all echo >&2 error/warning messages to use GitHub Actions
workflow commands (::error and ::warning) so they appear as annotations
at the top of the run page instead of being invisible in log output.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>