fix(builder): correct PR template test command, alerts, branch scopes

[iap]

Summary

Three defects in .github/pull_request_template.md, each verified against repo reality:

• Test command skipped 21 tests. python -m pytest -q -k "not adapter" deselects everything matching adapter, including test_adapter_sse_parses_via_openai_sdk (the SSE wire-contract guard). Measured: 242 collected full suite vs 221 with the filter. Replaced with the canonical python3 -m pytest tests/ -q (integration tests self-skip without hermes-agent).
• Alert markers could not render. Bare [!IMPORTANT] / [!WARNING] render as literal text per GitHub docs; converted to the blockquote alert form.
• Branch prefixes contradicted AGENTS.md scopes. bugs/ and feature/ are not Conventional Commits-lite scopes and feat/ was missing; aligned to feat/fix/sec/refactor/test/docs/chore.

Branch

Opened from fix/pr-template-commands-alerts (matches the corrected scope list).

Note

Markdown-only change; no code, no behavior, no secrets touched.

Checklist

• Tests pass: python3 -m pytest tests/ -q (241 passed, 1 skipped — suite untouched by this change)
• verify.py is green
• No raw tokens/secrets in code, logs, or tool output
• Adapter stays loopback-only unless an explicit guard is added
• Updated docs/README if user-facing behavior changed (N/A — template only)

Confidence Score: 5/5

Safe to merge.

Findings

1.  Feature Labels Are Skipped ▶

Summary

• This update aligns pull-request guidance with automatic labeling by documenting supported branch prefixes and mapping feat/ and docs/ branches to their corresponding labels.

_{Reviews (4) · Last reviewed commit: "docs: template references Conventional C..."}

[greptile-apps]

Feature Labels Are Skipped

The template directs contributors to use feat/…, but the branch-label workflow only maps feature/ to the enhancement label. Pull requests opened from the documented prefix therefore receive no feature label, leaving them incorrectly categorized for triage. This is a non-blocking concern, but the template and workflow should use the same prefix set.

Artifacts

Evidence from the check

• A Node.js harness was authored to parse the workflow label map and exercise its exact prefix-matching behavior for documented and workflow-only branch prefixes; it provides the reproducible check.

Command output from the check

• The executed harness completed with exit code 0 and shows `feat/deterministic-check` matched no prefix, invoked no label action, and received no enhancement label; the documented path is broken.

_{Ran code and verified through T-Rex}