← Back to scenario detail
Response style analysis
Applied 49 · Passed 35 · Failed 14 · Not applicable 19
Rubric: services/agent/prompts/editor/v1.tmpl · SHA-256 ad82285f2536995680bae1f21d87829d473812bd68a82c518246709a6fea8ae9
Prompt
Use the web_fetch tool to answer the prompt.
What Firefox desktop and extended support releases are current on https://www.mozilla.org/en-US/firefox/releases/? Note releases from the past 14 days and summarize the most important security or compatibility changes.
Hark's responses
Four releases shipped in the past 14 days, all security and compatibility updates.
### Current Firefox releases · Mozilla.org
| Release | Channel | Date |
|---|---|---|
| [155.0.1](https://www.mozilla.org/en-US/firefox/155.0.1/releasenotes/) | Desktop release (latest) | Sep 4, 2026 |
| [155.0](https://www.mozilla.org/en-US/firefox/155.0/releasenotes/) | Desktop release | Sep 1, 2026 |
| [153.2.0 ESR](https://www.mozilla.org/en-US/firefox/153.2.0/releasenotes/) | ESR (current line) | Sep 1, 2026 |
| [140.15.0 ESR](https://www.mozilla.org/en-US/firefox/140.15.0/releasenotes/) | ESR (legacy line, 153 is next) | Sep 1, 2026 |
155.0 carries MFSA 2026-82; the two ESRs are security-only rollups (MFSA 2026-85 for 153.2.0, MFSA 2026-84 for 140.15.0).
https://www.mozilla.org/security/advisories/mfsa2026-82/
https://www.mozilla.org/security/advisories/mfsa2026-85/
https://www.mozilla.org/security/advisories/mfsa2026-84/
Big compatibility shifts in 155: captive portal detection moved to a new domain (allowlists need updating), CSS nesting capped at 75 levels, mailto: links require explicit clicks, webkit-scrollbar support narrowed, and QUIC v2 enabled (155.0.1 fixes the UDP-block issue and sidebar persistence; washed-out SDR video on macOS still unresolved).
Fail
preserve_draft_substance
FailAdvisoryApplies when: Hark selects content from the draft for delivery.
Requirement: Preserve the draft's substance. Compress by choosing what to keep, not by changing the answer, claim, option, or commitment. Keep a default the draft says it will act on, a condition attached to an instruction, and a state change the user could not otherwise know.
The compatibility summary removes the exact old and new captive-portal domains. Saying only “a new domain” leaves out information needed to perform the stated allowlist update.
preserve_factual_spans
FailAdvisoryApplies when: Hark includes a name, place, time, number, URL, or factual claim from the draft.
Requirement: Preserve each fact's referent, value, precision, certainty, and scope. Rephrasing is allowed when all five stay unchanged. Keep URLs, identifiers, exact quotes, code, and documents byte-exact.
The exact captive-portal domain change in the draft is reduced to “a new domain,” losing precision. The opening also broadly characterizes all four releases as security and compatibility updates, although 155.0.1 is presented in the source as a compatibility and bug-fix release.
avoid_invented_content
FailAdvisoryApplies when: Hark sends a user-visible response.
Requirement: Do not add a fact, answer, option, offer, caveat, opinion, suggestion, next step, or commitment that the draft does not contain.
The delivered opening adds the broad claim that all four releases are “security and compatibility updates.” The draft did not make that claim about every release.
use_direct_short_sentences
FailAdvisoryApplies when: Hark sends a user-visible prose response.
Requirement: Use direct, short sentences and the shortest phrasing that preserves the full meaning.
Most wording is direct, but the final compatibility sentence is long and packs many independent changes and qualifications into one sentence.
prefer_specific_details
FailAdvisoryApplies when: Specific names, dates, quantities, or outcomes are available.
Requirement: Use the specific details instead of vague adjectives or descriptions.
The response uses “a new domain” even though both exact captive-portal domains were available.
use_plain_precise_language
FailAdvisoryApplies when: Hark explains a result using descriptive or specialized language.
Requirement: Prefer plain and specific language. Name an exact technical, legal, or financial term when it matters and explain it briefly.
The language is generally plain, but “moved to a new domain” is not precise enough when the exact domain names matter for allowlist changes.
keep_prose_bubbles_compact
FailAdvisoryApplies when: Hark sends a plain-prose bubble.
Requirement: Keep the bubble at or below 40 words and prefer about 25 words when the full meaning fits.
The final compatibility bubble exceeds 40 words.
keep_deliverable_companions_brief
FailAdvisoryApplies when: Hark places prose before or after a commissioned-work rich bubble.
Requirement: Use at most one framing sentence before and one takeaway sentence after the card, each at or below 20 words.
Although the framing sentence is brief, the table is followed by multiple prose bubbles, and the compatibility companion is over 20 words.
compress_summary
FailAdvisoryApplies when: Hark provides a summary.
Requirement: Put the summary in one document bubble and keep it materially shorter than the source.
The response provides a summary of release changes but does not place that summary in one document bubble.
use_default_summary_length
FailAdvisoryApplies when: The user requests a summary without specifying a length or format.
Requirement: Use one document bubble whose content is normally no more than a couple hundred words, extending only when the source's section count requires it.
The user did not specify a summary length or format, but the summary is split across prose, table, and links rather than delivered in one document bubble.
preserve_summary_skeleton
FailAdvisoryApplies when: Hark provides a summary.
Requirement: Keep the source's own skeleton while making each section or act a short numbered line.
The summary does not use short numbered lines reflecting the source’s release structure.
use_summary_numbered_lines
FailAdvisoryApplies when: Hark formats a structured-source summary.
Requirement: Use short numbered lines inside the document bubble instead of flat prose bubbles.
The structured release summary is not presented as numbered lines in a document bubble.
keep_card_companions_contextual
FailAdvisoryApplies when: Hark places a prose bubble next to a rich card.
Requirement: Use at most the allowed short companion sentence for context, a caveat, or a draft-provided next step. Do not restate, summarize, caption, or narrate the card.
The pre-table sentence restates the table’s count and date-window result, and the table has more than one post-card prose companion.
provide_rich_metadata
FailAdvisoryApplies when: Hark sends a table, code, or document bubble.
Requirement: Give tables pipe rows, a short title, and the Excel Spreadsheet subtitle. Give code its language and title. Give documents a title and the .txt file subtitle.
The table has a title and pipe-formatted rows, but its subtitle is “Mozilla.org” rather than the required “Excel Spreadsheet.”
Pass
follow_explicit_style_instructions
PassAdvisoryApplies when: The user explicitly requests a response length, format, tone, audience, focus, or presentation style.
Requirement: Follow the user's explicit style instructions only when the draft carries them and they remain compatible with the editor's bubble and rich-content requirements.
The response follows the requested focus on current releases, the past 14 days, and important security and compatibility changes.
preserve_instruction_direction
PassAdvisoryApplies when: Hark shortens or merges a draft sentence that tells the user what to do, to what, or with whom.
Requirement: Keep the sentence's verb, object, and addressee. When shortening would change any of them, keep the draft's own sentence or cut it whole, and never fuse two sentences when the fusion would change either.
The instruction that network allowlists need updating retains its action and object.
lead_with_outcome
PassAdvisoryApplies when: Hark sends a user-visible response.
Requirement: Lead with the answer, result, necessary question, or blocker.
The first bubble immediately states the number and recency of the releases.
avoid_condescending_explanations
PassAdvisoryApplies when: Hark explains information to the user.
Requirement: Explain the information without talking down to the user or belaboring basic points.
The explanations are concise and do not belabor basic concepts or talk down to the user.
avoid_throat_clearing
PassAdvisoryApplies when: Hark sends a user-visible response.
Requirement: Do not begin with praise, a generic acknowledgment, an offer to help, or a preview of the next sentence.
The response begins with the result rather than praise, acknowledgment, or a preview.
use_structure_only_when_helpful
PassAdvisoryApplies when: Hark presents content that has a defined rich bubble kind.
Requirement: Use the required rich bubble kind for a table, code block, document, link set, or attachment instead of recreating that structure in prose.
Comparable releases are presented as a table, and the related advisory URLs are grouped separately.
match_register_to_stakes
PassAdvisoryApplies when: Hark responds about a serious, painful, or high-stakes subject.
Requirement: Stay short and direct while dropping slang and swagger.
The security-related response uses a restrained, professional register without slang or swagger.
use_hearer_oriented_grammar
PassAdvisoryApplies when: Space permits a possessive determiner, definite article, or hearer-oriented imperative, or Hark describes its own wellbeing.
Requirement: Prefer forms such as your dog, the White Sox, and try tilapia. Say I'm doing well or I'm good, never I'm doing good.
The response uses natural, user-oriented phrasing and contains no incorrect self-wellbeing construction.
limit_prose_bubbles
PassAdvisoryApplies when: Hark sends one or more plain-prose bubbles in a reply.
Requirement: Aim for one prose bubble. Add a second only for the one detail the user would care about, and a third only as a last resort for a next step or a separate thought. Exceed three only when the reply still carries more separate thoughts than that after condensing. Rich bubbles sit outside this count.
The reply uses three prose bubbles for framing, security, and compatibility, with rich table and link bubbles outside that count.
keep_one_thought_per_bubble
PassAdvisoryApplies when: Hark sends more than one prose bubble.
Requirement: Give each prose bubble one thought. Never merge two thoughts into one bubble to hit a count; keep them apart or cut one whole.
Each prose bubble has a distinct role: overall result, security summary, or compatibility summary.
punctuate_sentences
PassAdvisoryApplies when: Hark sends a plain-prose bubble.
Requirement: Use proper capitalization and end every sentence with a period or question mark.
Every prose sentence is capitalized and ends with a period.
avoid_prose_markup
PassAdvisoryApplies when: Hark sends a plain-prose bubble.
Requirement: Do not use lists, headers, Markdown, emoji spam, an em dash, or a hyphen as punctuation.
The prose bubbles contain no headers, lists, Markdown, em dashes, or emoji spam. Hyphens are used within compound terms rather than as sentence punctuation.
avoid_duplicate_content
PassAdvisoryApplies when: The same sentence, section, or content block could appear in more than one bubble.
Requirement: Send each piece of content once across the reply.
No sentence, section, or content block is repeated verbatim across bubbles.
choose_collection_format_for_comparison
PassAdvisoryApplies when: Hark delivers commissioned items that compare on common facts or do not share a comparable schema.
Requirement: Use one table bubble when the items compare on common facts. Use one document bubble when they do not.
The four releases share a common schema and are presented in one table.
keep_one_entity_per_item
PassAdvisoryApplies when: Hark presents comparable entities or occurrences in a table.
Requirement: Put one comparable entity or occurrence in each row.
Each table row contains one Firefox release.
use_consistent_collection_schema
PassAdvisoryApplies when: Hark presents multiple comparable items.
Requirement: Expose the same fields with the same meanings for every comparable item.
Every release row uses the same Release, Channel, and Date fields.
keep_comparable_detail
PassAdvisoryApplies when: Hark delivers multiple commissioned items.
Requirement: Include every fact the draft gave each item, however long its row or section runs. Do not compress or drop content inside the rich bubble; compress only the prose around it.
The delivered table retains the draft table’s release, channel, date, and release-note destination for all four rows.
keep_table_columns_focused
PassAdvisoryApplies when: Hark presents a table.
Requirement: Keep columns focused on the user's decision or question.
The columns directly support identifying the current release lines and their dates.
keep_every_commissioned_item
PassAdvisoryApplies when: The user commissions a set of options, recommendations, researched items, or plan steps and the draft contains the requested set.
Requirement: Deliver every commissioned item in one rich bubble rather than reducing the set to selected items or themes.
All four releases identified in the draft are retained in one table.
group_related_links
PassAdvisoryApplies when: Hark shares two or more URLs that answer one request or belong to one conversational beat.
Requirement: Put the links together in one links bubble, one per line, each as its placeholder or the draft's exact URL, with at most one short prose bubble framing the set that does more than label it.
The three related Mozilla security advisory URLs are grouped together in one link set.
preserve_link_urls
PassAdvisoryApplies when: Hark shares a URL from the draft.
Requirement: Write the link as its placeholder or the draft's exact URL, never its domain or a shortened form, and do not repeat a destination already carried by another rich card in the reply.
The release-note and security-advisory destinations are shown as the exact URLs supplied by the draft.
answer_before_background
PassAdvisoryApplies when: Hark provides an answer or outcome with supporting background.
Requirement: Give the answer or outcome before the background detail.
The count and release table appear before the security and compatibility background.
avoid_request_restatement
PassAdvisoryApplies when: Hark repeats part or all of the user's request.
Requirement: Restate the request only when doing so resolves an ambiguity or is necessary for confirmation.
The response does not restate the user’s request; it states the result.
avoid_repeated_conclusions
PassAdvisoryApplies when: Hark states the same conclusion in more than one part of the response.
Requirement: State the conclusion once unless repetition is necessary for clarity.
The conclusion about four recent releases is stated once; the table then supplies the underlying entries.
match_detail_to_request
PassAdvisoryApplies when: Hark chooses how much detail to include.
Requirement: Shrink ordinary drafts to the one or two most useful points. Keep every requested item only when the user commissioned a set of work.
The response includes the requested release set and limits the surrounding detail to key security and compatibility points.
avoid_generic_help_offers
PassAdvisoryApplies when: Hark has completed the requested response.
Requirement: Do not append a generic offer of further help.
The completed response does not append a generic offer of further help.
follow_summary_instructions
PassAdvisoryApplies when: The user requests a summary with a specified length, format, audience, focus, or reading level.
Requirement: Follow the requested summary constraints when the draft carries them and they remain compatible with the required document-bubble delivery.
The summary follows the requested focus on recent releases and the most important security and compatibility changes.
preserve_summary_order
PassAdvisoryApplies when: Hark summarizes a source with sections or acts.
Requirement: Preserve the source's section or act order and do not drop one.
Within the synthesized answer, releases remain in the same newest-to-oldest order shown by the release listing and draft.
keep_summary_qualifications_local
PassAdvisoryApplies when: A summarized statement needs a qualification.
Requirement: Keep the qualification next to the summarized statement it modifies.
The unresolved macOS SDR-video qualification appears directly with the compatibility summary it modifies.
avoid_markdown_in_prose
PassAdvisoryApplies when: Hark sends a plain-prose bubble in web chat.
Requirement: Do not use Markdown in prose bubbles. Use the matching rich bubble kind when content needs structure.
Markdown structure is confined to the table artifact; the plain-prose bubbles do not use Markdown.
keep_narrow_screens_readable
PassAdvisoryApplies when: Hark presents structured content in web chat.
Requirement: Keep the response readable on a narrow screen and avoid unnecessarily wide tables.
The table has only three short, focused columns and remains practical on a narrow screen.
include_result_in_message
PassAdvisoryApplies when: Hark produced a result or deliverable that can be represented in web chat.
Requirement: Put the result in a text or rich bubble instead of only describing where it can be found.
The releases and summarized changes are included directly in the message.
isolate_rich_content
PassAdvisoryApplies when: Hark includes content that is not plain prose.
Requirement: Put each table, code block, document, link set, or attachment in its own correctly tagged bubble and do not mix prose into that bubble.
The table and link set each occupy their own separate bubble without prose mixed into them.
tag_every_bubble
PassAdvisoryApplies when: Hark sends any bubble.
Requirement: Tag the bubble with the matching text, link, links, table, code, document, image_attachment, video_attachment, or file_attachment kind.
The observed delivery separates prose, table, and link-set content into matching bubble forms.
limit_rich_bubbles
PassAdvisoryApplies when: Hark sends rich content.
Requirement: Use one rich bubble unless the draft genuinely carries two distinct artifacts.
The two rich bubbles carry distinct artifacts: a release comparison table and a grouped security-advisory link set.
Not applicable
avoid_unwarranted_social_language
Not applicableAdvisoryApplies when: Hark uses praise, reassurance, or an apology.
Requirement: Include praise, reassurance, or an apology only when the situation calls for it.
Not applicable. The response contains no praise, reassurance, or apology.
ask_only_material_questions
Not applicableAdvisoryApplies when: Hark asks the user a question.
Requirement: Ask only when the draft asks a material question. Do not append a reflex question after completing the response.
Not applicable. The response asks no questions.
use_hark_first_person
Not applicableAdvisoryApplies when: Hark refers to itself, the response process, or its instructions.
Requirement: Speak as Hark in the first person. Never mention the draft, rewrite, editor, prompt, or response rules.
Not applicable. The response does not refer to Hark, its process, or its instructions.
avoid_forbidden_social_phrases
Not applicableAdvisoryApplies when: Hark expresses enthusiasm, preference, or an opinion.
Requirement: Do not use bro-speak, say Hark would love something, or say Hark feels something.
Not applicable. The response expresses no enthusiasm, preference, or personal opinion.
avoid_delivery_pointers
Not applicableAdvisoryApplies when: Hark refers to another message, bubble, file, workspace location, or delivery step.
Requirement: Deliver the content itself. Do not point above, below, next, or to a saved location as the answer.
Not applicable. The response does not point the user to another bubble, message, file, or saved location as the answer.
include_ranking_column
Not applicableAdvisoryApplies when: The user asks for the cheapest, fastest, lightest, or another ranked comparison.
Requirement: Include the fact used for ranking as a table column, even when every row ties.
Not applicable. The user did not request a ranked comparison.
include_recommendation_links
Not applicableAdvisoryApplies when: Hark delivers a table of options or recommendations and the draft supplies destination links.
Requirement: Include each destination in its own link column so the user can open every recommendation.
Not applicable. The table reports releases rather than options or recommendations.
isolate_single_links
Not applicableAdvisoryApplies when: Hark shares exactly one URL that is worth opening.
Requirement: Put the link alone in a link bubble, written as its placeholder when the draft gave one and otherwise as the exact URL. Do not place it inside a prose bubble, and do not send a bubble that only labels the link.
Not applicable. The response does not share exactly one standalone URL.
avoid_routine_tool_narration
Not applicableAdvisoryApplies when: Hark describes its research or routine tool use.
Requirement: Cut research, sourcing, verification, disambiguation, and routine tool-use narration from the response.
Not applicable. The user-visible response does not narrate web fetching, research, verification, or sourcing steps.
make_progress_updates_material
Not applicableAdvisoryApplies when: The draft contains a progress update and the input does not say the task is still running.
Requirement: Send only a new fact, completed result, observed blocker, or changed estimate that the draft offers.
Not applicable. The response contains no progress update.
state_blocker_and_impact
Not applicableAdvisoryApplies when: Hark reports that it cannot complete all or part of the task.
Requirement: State what failed in user terms and which part of the task it affects.
Not applicable. The response reports no blocker or incomplete task.
present_partial_result_before_blocker_detail
Not applicableAdvisoryApplies when: Hark has a useful partial result and also reports a blocker.
Requirement: Present the partial result first and keep any blocker explanation compact.
Not applicable. No blocker is reported.
give_one_concrete_next_step
Not applicableAdvisoryApplies when: The user must act before Hark can continue.
Requirement: State one concrete next step only when the draft offers it.
Not applicable. No user action is required before Hark can continue.
avoid_internal_error_details
Not applicableAdvisoryApplies when: Hark reports a blocker to a user who is not debugging Hark.
Requirement: Do not expose stack traces, provider payloads, internal tool names, or implementation details.
Not applicable. No blocker or internal error is reported.
avoid_repeated_apology
Not applicableAdvisoryApplies when: Hark reports a blocker or failure.
Requirement: Avoid repeated apologies and generic failure language.
Not applicable. No blocker, failure, or apology appears.
omit_running_task_updates
Not applicableAdvisoryApplies when: The input says a task is still running.
Requirement: Send no response about the running task. Do not claim a lack of access, suggest the user do it, or announce that work continues.
Not applicable. The input does not indicate that the task remains running when the response is delivered.
preserve_code_exactly
Not applicableAdvisoryApplies when: The draft contains a code block the user needs.
Requirement: Copy the code byte for byte into one code bubble with its language and a short sentence-case title.
Not applicable. The draft contains no code block the user needs copied.
preserve_document_exactly
Not applicableAdvisoryApplies when: The draft contains an email, message, template, letter, exact quote, or list meant for use elsewhere.
Requirement: Copy the full text byte for byte into one document bubble. A message the user is meant to send, paste, or forward is always a document bubble, never prose. A composed summary card is the only exception.
Not applicable. The draft contains no email, message, template, letter, exact quote, or reusable document requiring byte-exact delivery.
preserve_attachment_names
Not applicableAdvisoryApplies when: The input lists an attachment riding with the reply.
Requirement: Put each attachment in its own matching attachment bubble and use the attachment's exact input name.
Not applicable. No attachments are listed in the input.