frontend-triage: simplify and refresh the README - #6530
Merged
Conversation
The README had drifted into a narrative doc: ~30 lines explained why Searchfox permalinks resolve from the index revision rather than the checkout, duplicating the module docstring in hackbot_runtime/searchfox.py, plus similar rationale for model pinning and the read-only design. Trim that back to the terser style of the build-repair and test-repair READMEs, and fix three stale points: - The recorded comment now ends with the runtime's 👍/👎 reaction footer plus the ai-triage-* tags added by feedback_tags_hook. Needinfo is no longer the feedback channel. - BROKER_URL was missing from the inputs table, though AgentInputs requires it. - Recorded actions are applied by a human from the Hackbot UI; this agent does not set auto_apply_actions. Also note that rules/ and prompts/ live under hackbot_agents/frontend_triage/, and that the agent has no unit tests of its own.
msujaws
enabled auto-merge (rebase)
August 6, 2026 20:22
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
frontend-triageREADME had grown into a narrative doc. Roughly 30 linesexplained why Searchfox permalinks resolve from the index revision rather
than the checkout — which the module docstring in
libs/hackbot-runtime/hackbot_runtime/searchfox.pyalready covers in full —plus similar standalone rationale for model pinning and the read-only design.
This trims it toward the terser style of the
build-repairandtest-repairREADMEs and folds the safety bullets into a single section about what actually
reaches Bugzilla.
It also fixes three stale points:
runtime's 👍/👎 reaction footer or the four
ai-triage-*tags appended byfeedback_tags_hook. Every needinfo reference is gone.BROKER_URLwas missing from the inputs table even thoughAgentInputsrequires it. The table now also makes clear that
BUGZILLA_API_URL/BUGZILLA_API_KEYare consumed by the broker container only.them from the Hackbot UI.
Smaller corrections:
rules/andprompts/live underhackbot_agents/frontend_triage/, not at the agent root, which the old textleft ambiguous; and a closing line notes the agent has no unit tests of its own.
Net 65 insertions / 81 deletions, one file, prettier-clean.
Conflicts with #6439
#6439 ("Auto-apply high-confidence frontend-triage results and report them to
Slack") edits the same README section and inverts the auto-apply claim above.
Whichever lands second will need a fixup — the wording here is correct against
mastertoday, and #6439's own README hunk already describes theauto_apply_confidencebehavior that supersedes it.Verification
Documentation only. Claims were checked against
config.py,__main__.py,agent.py(feedback_tags_hook),hackbot_runtime/actions/bugzilla.py(
_COMMENT_FOOTER),compose.yml(BROKER_URL), andservices/hackbot-api/app/agents.py. The agent was not run end to end, so thefooter and tag line are confirmed by reading the hooks rather than by
inspecting a real
summary.json.