potiuk opened a new pull request, #364: URL: https://github.com/apache/airflow-steward/pull/364
## Summary - **AGENTS.md § *Linking tracker issues and PRs*** — restructure into three subsections covering markdown surfaces (existing rule), terminal surfaces (new OSC 8 hyperlink escape sequence guidance with Python + Bash helpers and CI-log fallback), and confidentiality / editing rules. Self-check now recognises OSC 8 wrappers as already-clickable. - **10 skills** (`pr-management-triage`, `issue-fix-workflow`, `issue-reassess`, `issue-reproducer`, `security-issue-import`, `security-issue-import-from-md`, `security-issue-import-from-pr`, `security-issue-fix`, `security-issue-invalidate`, `security-issue-deduplicate`) had no explicit rule on the topic — add a Golden rule each, tailored to the skill's emission surfaces. - **3 skills** with existing markdown-only rules (`issue-triage`, `security-issue-triage`, `security-issue-sync` — the canonical formulation) — broaden to the dual-surface convention. - **`security-cve-allocate`** cross-references `security-issue-sync` GR 2 and auto-picks up the update. ## Why OSC 8 hyperlinks let terminal output stay compact — the visible text is the short `<repo>#NNN` form, the URL is wrapped invisibly, and modern terminals (iTerm2, Kitty, GNOME Terminal, WezTerm, Windows Terminal, Alacritty) render the short text as clickable. The prior rule required either markdown (only renders on GitHub) or printing the URL inline alongside the number (noisy in proposal previews). The dual-surface formulation makes the right choice per surface explicit. ## Test plan - [ ] `skill-and-tool-validate` exits 0 (verified locally; no hard violations on the touched files). - [ ] Spot-check a triage / sync / fix run and confirm clickable rendering in iTerm2 / GNOME Terminal. - [ ] Confirm the security-issue-fix cross-confidentiality reminder (clickable rendering does not relax the `<tracker>`-URL scrub for `<upstream>` PR content) still triggers the existing scrub. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
