Cloud baseline
Hy4 preview, single model via OpenRouter
tencent/hy4-preview · scorer forge-2.0
- Overall
- 0.5165
- Benchmark
- Forge 2.0
- Model build
- 58m 21s
Recorded inference cost
$2.06
From the saved OpenRouter generation billing summary (218 recorded requests). Whether auxiliary model calls were included was not retained. Scoring reuses the saved build; this amount describes the original inference spend.
Token usage
Tokens: 35.1M in · 158k out · 34.5M cached (exact, OpenRouter records)
35,210,403 tokens over 218 model calls: every call of the run, the model's own and the harness's helper calls, counted from OpenRouter records. Reasoning tokens as the provider reports them: 89,176 (not added to the total).
tencent/hy4-preview
In 35.1M · Out 158k · Cached 34.5M · Reasoning 89.2k · 217 calls
google/gemini-2.5-flash
In 1.4k · Out 3 · Cached 0 · Reasoning 0 · 1 call
Tier breakdown
Each bar is the tier's mean, from 0 to 1 (for E, its mean × the excellence gate). The percentage is the tier's share of the score. Mean × share, added over all tiers, is the tests earned figure below.
Scoring detail
How this score was built
Per-test scorer output, as posted by the app. Expand a section to inspect its tests.
Correctness combines the lowest score for each test across the scoring fixtures; economy measurements use their mean. The combined result can therefore be lower than every individual fixture’s final score. Critical defects reduce the weighted result, followed by the reliability multiplier, before any score cap applies.
The rules behind these numbers: Forge 2.0 requirements, weights and score caps.
The score, step by step
0.9244 tests earned × 1.0000 critical defects × 0.5588 reliability = 0.5165 final score
tests earned = 0.15 × 0.8764 v1 + 0.7929 v2 (out of 0.85)
v1 = 0.88 × 0.8724 tiers L–A + 0.12 × 0.9055 gate × 1.0000 excellence
Reliability: every tier in the breakdown above, except Excellence, is a group of tests. Each group of tests multiplies the score by 1 − 0.10 × the shortfall of its worst test: by 0.90 when that test fails completely, by 0.95 when it scores 0.5.
- T Event pipeline: worst test
t_reestimate_followed, score 0 × 0.9000Already counted in this group: t_out_of_order
- R Reconcile: worst test
r_pagination, score 0.9857 × 0.9986 - S Storage: worst test
s_entity_index_used, score 0.9991 × 0.9999 - B Resolvers and permissions: worst test
b_comment_adf_as_user, score 0.1667 × 0.9167 - U UI function: worst test
u_not_started, score 0 × 0.9000Already counted in this group: u_widget_numbers, u_widget_chart, u_ledger_table, u_ledger_sort, u_comment_flow, u_widget_live, u_llm_explain
- A Rovo: worst test
a_action_result, score 0 × 0.9000 - R4 Changing world: worst test
r4_field_switch, score 0.6154 × 0.9615Already counted in this group: r4_move_new_board
- R7 Custom field: worst test
r7_writes_accepted, score 0.3312 × 0.9331Already counted in this group: r7_values_fresh
- R10 Native JQL: worst test
r10_precomputation_refresh, score 0.3333 × 0.9333Already counted in this group: r10_shared_permissions, r10_empty_and_closed, r10_invalid_arguments
v1 is this run's score on the tests carried over from Forge 1.0: 15% of the total. v2 is the requirements R1–R10, each at its share of the score: the other 85%. Critical defects multiply the whole score, and so does each group of tests, by 1 − 0.10 × the shortfall of its worst test.
Excellence gate 0.9055: the average of the 18 conditions below, each counted at the value shown. Green is met in full; red is not, and lowers the gate. The 3 excellence tests are paid in proportion to the gate; together they are 1.8% of the total.
Earned score 0.5165 · No cap applies · Final score 0.5165
Under a cap the final score is min(earned, cap − 0.05 × (1 − earned)): always below the cap, and closer to it the more the run earned. With no cap it is the earned score. Avoiding a cap adds no points.
Forge's own linter reports no errors (warnings cost points), every manifest function bundles and loads, packages resolve at the kit's pins, the manifest rules the linter misses, and only the scopes the app's calls need.
l deployable
1.00lint: 0 errors, every stage reached
l bundles load
1.009/9 functions bundle, load and export their handler
l lint warnings
1.000 distinct lint warning(s): []
l real packages
1.009/9 bundles resolve @forge/* at the kit pins only
l manifest rules
1.006/6 manifest rules met:
l scopes
1.00scopes: missing [], extra []
Current modules and APIs: dashboards:widget with its edit API, the rovo:skill and rovo:mcp wiring, a Forge LLM model the platform lists as active, no /rest/api/3/search, no @forge/api storage, a nodejs22.x or nodejs24.x runtime, the consumer shape, the declared KVS entity, and deploy readiness: a manifest and permissions real Forge would accept and no code predicted to fail there.
k dashboard widget
1.00dashboards:widget 2/2: {'custom_ui_resource': True, 'edit_resource': True}
k widget edit bridge
1.004/4 board picks reached the dashboard through the widget edit API (updateConfig/onProductSave)
k rovo skill
1.00rovo:skill 7/7:
k current apis
1.00current APIs 5/5:
k consumer shape
1.00consumer shape 3/3
k entity declared
1.00entities with a sprint-partitioned, ranged index: ['scope-change', 'scope-ledger', 'sprint-issue']
k v2 surfacesdiagnostic, no weight
1.00v2 surfaces declared: ['jira:adminPage', 'webtrigger', 'scope-ledger']
k rovo mcp
1.00rovo:mcp 4/4:
k llm model current
1.0013 LLM call(s); model ids list() does not return: []; llm module with claude: True
k manifest semantics
1.00deploy readiness, manifest + permissions: 17 rules checked, none failing here
k runtime risks
1.00deploy readiness, predicted runtime failures: 12 rules checked, none failing here
Issue updates flow trigger to queue to consumer: one ledger row per change under duplicate, reordered, dropped and concurrent deliveries, multi-sprint changelog values, re-estimates followed, Retry-After honoured, no user context in background work.
t trigger handoff
1.001023/1023 deliveries handed off correctly
t event rows
1.00event rows: 170/170 exact (precision 1.00, recall 1.00)
t no double count
1.00every change holds at most one ledger row in every phase (duplicated deliveries included); 25 concurrent group(s) raced (independent 16, same-event 5, same-issue 4)
t out of order
0.7333worst of 3 scoring sites (seed 3c04f61f28a4a511): permuted deliveries: 11/11 rows exact, 0/4 sprints with oracle numbers
t multi sprint parse
1.00123/123 multi-id Sprint changes recorded exactly
t reestimate followed
0.000/6 re-estimated sprints show the oracle numbers
t retry after honoured
1.00InvocationError retryAfter 30s >= 30s
t no user in async
1.00background work is asApp only
The first scheduled run starts the backfill of every change since each active sprint started, removals included; later runs heal what the event stream missed and a run with nothing new writes nothing; they page through results in each endpoint's own style, never retry before Retry-After and finish inside the module timeout, queue continuations included.
r backfill complete
1.00130/130 historical changes v1 never recorded, recorded one virtual hour after the upgrade (the backfill is dosed; v1 rows are R1's, at 2 h)
r removals found
1.0024/24 removed-to-backlog changes found
r heal dropped
1.004/4 dropped changes healed exactly once; 0 other row(s) added
r pagination
0.9857worst of 3 scoring sites (seed 3aaa6d6b73d37669): 69/70 reads the site served in two or more pages walked to their end through the cursors the site offered (/rest/agile/1.0/board 15/15, /rest/agile/1.0/board/{id}/sprint
r rate limit
1.00run 1 (backfill) request 2: waited 2.2 virtual s in-invocation; run 1 (backfill) continuation page: waited 2.2 virtual s in-invocation; run 2 (hour-1) request 2: waited 2.2 virtual s in-invocation
r as app
1.00216/216 Jira calls of the scheduled runs and their queue continuations asApp (scheduled 216)
r completes in timeout
1.008/8 invocations of the scheduled runs and their queue continuations inside their module timeout (scheduled 8)
r idempotent rerun
1.000 ledger write(s) (scope-ledger) on a no-change run over 363 rows
Forge KVS with the storage scope, ledger reads through the declared entity index in change-time order, no KVS limit errors.
s storage scope
1.00KVS used, no 403 from the KVS proxy
s entity index used
0.99911131/1132 ledger reads are entity queries on a declared index
s index order
1.006/6 tables list changes in change-time order
s limits
1.00no KVS limit errors
Every invoked resolver exists and answers structured errors, nobody sees changes to issues they cannot browse (not on screen, not in an LLM prompt, not in a Realtime payload), the hidden-change count is right, and each click posts exactly one ADF comment as the viewer.
b invoke contract
1.0066/66 invokes returned a defined, structured result; a Jira 500 on sprintLedger's read: handled
b no permission leak
1.00no hidden key, summary or change id reached a person
b hidden count
1.0018/18 hidden counts equal the oracle
b comment adf as user
0.1667worst of 3 scoring sites (seed 3c04f61f28a4a511): 2/12 comments are ADF as the viewer naming key, sprint and creep; ['36351 status 201 via user', '37206 status 201 via user', '34183 status 201 via user']
b comment exactly once
1.0012 click/double-click gesture(s), none posted more than one comment
b realtime payload clean
1.00188/188 realtime payloads hold sprint ids only
The dashboard widget's numbers and chart, its board choice saved through the host, live updates through Forge Realtime, the sprint action's ledger table, sorting, issue links, comment flow, the Forge LLM explanation, close and not-started states.
u widget loadsdiagnostic, no weight
1.006/8 configured widget views render a sprint with its numbers
u widget numbers
0.25widget numbers: 2.00/8 views exact (sprints by startDate, four §1 numbers each)
u widget chart
0.252/8 charts on one linear scale within 1px; ['worst bar off its linear scale by 41.56px', 'worst bar off its linear scale by 40.90px']
u widget edit config
1.00edit/config 10/10:
u ledger table
0.8822worst of 3 scoring sites (seed d031c3ee22136508): ledger tables: 5.29/6 exact (rows, cells, default order)
u ledger sort
0.33336/18 at-toggle states ordered with aria-sort (6 after another sort was active)
u issue router
1.006/6 issue keys open /browse/<KEY> through the Forge router
u comment flow
0.968831/32 comment-flow steps right (select, one comment and a success flag per click and double click, forbidden error flag, modal works); failed: ['modal_works_after@916']
u modal close
1.006/6 close clicks reached bridge close
u not started
0.00future sprint context: not-started not shown alone
u widget live
0.00moved sprints showing the new numbers live 0/1; 0 idle invoke(s)
u llm explain
0.8261explain 19/23 over 5 scripted answers: 1:digits:every_number_is_a_ledger_number, 2:refusal:modal_still_sorts, 3:malformed:modal_still_sorts, 4:error:modal_still_sorts
Atlassian design tokens with 4.5:1 contrast in light and dark, a painted surface, no Content Security Policy violations or console errors, and the widget readable at 380 px wide.
v theme tokens
1.0030/30 surfaces themed with --ds-text* at >= 4.5:1
v dark mode
1.0030/30 surfaces paint a --ds-surface* background in their mode
v csp clean
1.000 CSP violation(s), 0 failed asset request(s)
v console clean
1.000 console/page error(s) on nominal scenarios: []
v widget sizes
1.006/6 widget sizes without horizontal overflow, every sprint visible, no number clipped
The get-sprint-scope action returns exact numbers and the visible changes for the invoking person, returns errors instead of throwing, and the skill's SKILL.md tells the agent how to use it.
a action result
0.000/5 active sprints answered exactly
a action errors
1.002/2 bad sprintId inputs return {error} without throwing
a action permissions
1.0012/12 per-person answers list exactly what that person may browse
a skill instructions
1.00SKILL.md body 5/5: result fields named ['sprintName', 'committed', 'added', 'removed', 'creepPercent', 'hiddenChanges', 'changes']
Few Jira requests in the first scheduled run and per relevant change in triggers and consumers, and surfaces that paint after one round trip — paid only in proportion to the excellence gate.
e reconcile economy
1.00mean over 3 scoring sites: backfill 36 background Jira calls (by lineage, every phase) / optimum 20 (incl. 2 forced 429 repeat(s)) = 1.80x; 1.0 at <= 2.45x; 10 2.0 call(s) not counted (field-value writes, person-facing,
e event economy
1.00mean over 3 scoring sites: 382 Jira calls (by lineage, every phase) / baseline 214 (213 delivered relevant change(s) x 1 read + 1 forced 429 repeat; a normalizer, not a reachable optimum) = 1.79x; 1.0 at <= 2.86x; 28 fie
e ui round trips
1.00mean over 3 scoring sites: round trips before first paint: {'widget-view': 0, 'widget-edit': 1, 'sprint-action': 1}
Every v1 row moves to the new scope-ledger entity exactly once, with its change id and time, while events keep flowing and across invocation limits, within 2 virtual hours of the upgrade, with its progress in the admin panel; v1's entity stays intact.
r1 v1 rows migrated
1.00h2: 59 of 59 v1 rows in scope-ledger with the source attributes recorded by the probe
r1 v1 rows intact
1.00all 59 v1 source rows intact; 59 final copies preserve recorded v1 attributes at every observed checkpoint
r1 events during migration
1.0048 of 48 changes made while the migration ran are in scope-ledger at the end
r1 progress visible
1.006 of 6 panel reads show the migration right (total 59; complete after the h2 read)
On a site of about 1,000 issues, background work stays inside its share of the 2,400-point hour, no person-facing request meets a quota 429, and Retry-After and RateLimit-Reason (quota, burst, per-issue write) decide every retry; the backfill still completes.
r2 background share
1.0030 of 30 hours kept background within 70 % (1680 points; the contract default; the probe recorded no change); busiest hour 1472; mandatory field-write lower bound 7 (reads additional)
r2 person never quota refused
1.000 of 993 person-facing requests refused for quota
r2 rate limit reaction
1.005 of 5 429s answered by their reason (quota: all background paused; burst: the endpoint; per-issue: the issue)
r2 backfill complete
1.00130 of 130 pre-upgrade changes v1 never recorded are in scope-ledger, right
Work longer than one invocation continues in the next, no function waits past its limit (a long Retry-After is handed back, not waited out), and a killed invocation leaves no duplicate.
r3 never killed
1.009 of 9 functions never exceeded their limit
r3 long retry after deferred
1.001 of 1 invocations handed a Retry-After longer than their limit stopped and resumed later (results: retry)
r3 no duplicate rows
1.00every (changeId, sprintId) appears once at each of 7 checkpoints; 25 concurrent group(s) raced (independent 16, same-event 5, same-issue 4)
Sprints close, issues move to another board's sprint, a board's estimation field changes, issues are deleted and a person loses browse permission while the app runs; the ledger and every view come out right.
r4 sprint close final
1.001 of 1 closed sprints kept exactly their final ledger
r4 move new board
0.9091worst of 3 scoring sites (seed 3aaa6d6b73d37669): 10 of 11 cross-board moves recorded with the new board's estimate; CRM-224 (1494454): removed row ok, added row wrong/missing (estimate 8, want 1)
r4 field switch
0.6154worst of 3 scoring sites (seed 3aaa6d6b73d37669): 21 of 41 rows after the switch use the new field; 11 of 11 earlier rows keep their estimate; wrong after: ('1492218', '955'), ('1493225', '955'), ('1493708', '955') (+17)
r4 deleted history
1.002 of 2 rows of deleted issues kept as history with deleted: true
r4 permission revoked
1.004 answer(s) after a browse revoke showed ledger data and none of the newly hidden issues
A jira:adminPage built in UI Kit with the contract's controls, and every admin resolver checking Jira's ADMINISTER permission on the server, never trusting the payload.
r5 panel labels
1.008 of 8 §2.6 controls found by label; new secret shown once: yes; then masked ••••<last4>: yes
r5 admin actions apply
1.004 of 4 admin-page invokes of the admin's save and rotate applied
r5 nonadmin refused
1.008 non-admin/forged admin actions landed no attempted effect in storage
Signed deployment events: a missing or wrong signature, a tampered body or a stale timestamp is refused with no effect, a replay applies once, a valid event records the deployment, and the secret is never disclosed.
r6 unsigned no effect
1.005 invalid events (bad-signature, stale, stale-future, tampered, unsigned) had no effect
r6 replay once
1.001 sequential replay(s) and one concurrent pair had one acceptance and no duplicate Jira/deployment effect at any checkpoint; bookkeeping writes 0
r6 status codes
1.0010 of 10 cases answered with their status
r6 valid applies
1.003 of 3 validly signed events accepted (202) and recorded as `Deployed to <env>` on every ledger row of the issues they name
r6 secret never disclosed
1.00the CI secret (panel) never appeared outside its one-time display
The read-only scope-status field holds committed or added +points for an issue in an active sprint, removed for one that has left an active sprint since that sprint started, and nothing for any other issue, written in bulk through Jira's app field-value API and fresh within the virtual hour.
r7 values fresh
0.765worst of 3 scoring sites (seed 3c04f61f28a4a511): mean over 7 checkpoints; worst final: 227 of 375 issues right; AUTH-116 'committed' (want added +5, removed); AUTH-142 None (want added +0)
r7 writes accepted
0.3312worst of 3 scoring sites (seed 3c04f61f28a4a511): 51 of 154 bulk field writes accepted; refused: 404
Tool calls validated against the viewer's sprint scope, back-off on a 429 without Retry-After, answers with no finish reason refused, a 10-minute cache, and the admin's kill switch and daily token budget enforced on the server.
r8 tool call scope
1.002 of 2 manipulated calls respected function and visible sprint scope
r8 failure handling
1.002 of 2 LLM failures handled
r8 cost controls
1.003 of 3 cache/kill-switch/budget cases met their full outcome
The widget and the sprint action each make at most one invoke and load at most 150 KB before their first data paint, with no external origin; the admin page renders after one invoke.
r9 widget boot
1.00widget-view: 1 invoke(s) before first paint (<= 1), 102375 bytes of JS+CSS (<= 153600), 0 external request(s)
r9 sprint boot
1.00sprint-modal: 1 invoke(s) before first paint (<= 1), 106674 bytes of JS+CSS (<= 153600), 0 external request(s)
r9 admin boot
1.00admin-page: 0 invoke(s) before first paint (<= 1)
scopeChanged(sprintId) is a jira:jqlFunction returning native issue predicates from the ledger. Jira shares its precomputed expansion across users, applies each viewer's browse permissions, and keeps the same cached mapping fresh through the documented precomputation update API after changes and reconciliation. Empty, future and closed sprints, IN and NOT IN, and invalid arguments are checked by running actual native JQL.
r10 manifest
1.00scopeChanged manifest declares issue IN/NOT IN, required sprintId, and bound function
r10 initial membership
1.0024/24 initial_membership cases correct
r10 precomputation refresh
0.3333worst of 3 scoring sites (seed 3c04f61f28a4a511): 8/24 precomputation_refresh cases correct; refresh: missing=['35130'], extra=[], invoked=0; refresh: missing=[], extra=['35130'], invoked=0
r10 shared permissions
0.6667worst of 3 scoring sites (seed 3c04f61f28a4a511): JQL disclosure not observed: 48/72 shared_permissions cases correct; shared-user: missing=['35130'], extra=[], invoked=0; shared-user: missing=['35130'], extra=[], invoke
r10 empty and closed
0.75worst of 3 scoring sites (seed 3c04f61f28a4a511): 3/4 empty_and_closed cases correct; closed: missing=['37696'], extra=[], invoked=0
r10 invalid arguments
0.753/4 invalid_arguments cases correct; invalid: no explicit refusal or query returned issues
Graded browser recording
Loading duration…Watch the full graded browser recording at its original speed: the dashboard widget, the sprint action, the not-started sprint and the Forge LLM cases, as the scorer drove them on the run's own seed, the first of the three scoring sites. The test results and screenshots on this page provide the wider evidence. Pause or scrub to inspect a view.
The UI Kit admin panel is not in the recording: it is graded from its component tree.
Drag the timeline to seek. Keyboard: arrow keys move 5 seconds; Home and End jump to the start and end.
SHA-256: 4a2a417298cdb7e28ec94145f235afe3a92d0e782fc4550ff1d457d8ee7a8a2c
Screenshots
Pictures from one of the three scoring sites, the one on the run's own seed. The dashboard widget and the sprint action are captured from the built app in a browser during grading. The admin panel picture is drawn by the benchmark from the app's component tree, not by Jira, and nothing is graded from that picture. A test keeps the score of its worst site (the excellence measurements keep their mean), so a test can fail on a site these pictures do not show. A detail that opens "worst of …" names the seed of the site the test scored worst on, which can be the pictured one.
Run details
- Model
- tencent/hy4-preview
- Engine events
- 0
- Repair rounds
- 0
- Started
- Oct 20, 2026, 06:55 PM
- Finished
- Oct 20, 2026, 08:14 PM