Cloud baseline
qwen/qwen3.8-max-prime · Build 1
qwen/qwen3.8-max-prime · scorer forge-2.0
- Overall
- 0.6515
- Benchmark
- Forge 2.0
- Model build
- 73m 47s
Recorded inference cost
$35.98
From the saved OpenRouter generation billing summary (192 recorded requests). Includes auxiliary model calls made during the build. Scoring reuses the saved build; this amount describes the original inference spend.
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.9670 tests earned × 1.0000 critical defects × 0.6737 reliability = 0.6515 final score
tests earned = 0.15 × 0.9018 v1 + 0.8318 v2 (out of 0.85)
v1 = 0.88 × 0.9014 tiers L–A + 0.12 × 0.9146 gate × 0.9895 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.5 × 0.9500Already counted in this group: t_out_of_order, t_multi_sprint_parse
- R Reconcile: worst test
r_heal_dropped, score 0.25 × 0.9250 - B Resolvers and permissions: worst test
b_comment_adf_as_user, score 0.6667 × 0.9667Already counted in this group: b_hidden_count
- U UI function: worst test
u_widget_live, score 0 × 0.9000Already counted in this group: u_widget_numbers, u_widget_chart, u_ledger_table, u_ledger_sort, u_comment_flow, u_llm_explain
- A Rovo: worst test
a_action_result, score 0.4 × 0.9400Already counted in this group: a_action_permissions
- R4 Changing world: worst test
r4_field_switch, score 0.9839 × 0.9984 - R7 Custom field: worst test
r7_writes_accepted, score 0.63 × 0.9630Already counted in this group: r7_values_fresh
- R10 Native JQL: worst test
r10_precomputation_refresh, score 0.75 × 0.9750Already counted in this group: r10_shared_permissions
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.9146: 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.6515 · No cap applies · Final score 0.6515
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
Fixture 1: 1.0000
lint: 0 errors, every stage reached
Fixture 2: 1.0000
lint: 0 errors, every stage reached
Fixture 3: 1.0000
lint: 0 errors, every stage reached
l bundles load
1.009/9 functions bundle, load and export their handler
Fixture 1: 1.0000
9/9 functions bundle, load and export their handler
Fixture 2: 1.0000
9/9 functions bundle, load and export their handler
Fixture 3: 1.0000
9/9 functions bundle, load and export their handler
l lint warnings
1.000 distinct lint warning(s): []
Fixture 1: 1.0000
0 distinct lint warning(s): []
Fixture 2: 1.0000
0 distinct lint warning(s): []
Fixture 3: 1.0000
0 distinct lint warning(s): []
l real packages
1.009/9 bundles resolve @forge/* at the kit pins only
Fixture 1: 1.0000
9/9 bundles resolve @forge/* at the kit pins only
Fixture 2: 1.0000
9/9 bundles resolve @forge/* at the kit pins only
Fixture 3: 1.0000
9/9 bundles resolve @forge/* at the kit pins only
l manifest rules
1.006/6 manifest rules met:
Fixture 1: 1.0000
6/6 manifest rules met:
Fixture 2: 1.0000
6/6 manifest rules met:
Fixture 3: 1.0000
6/6 manifest rules met:
l scopes
1.00scopes: missing [], extra []
Fixture 1: 1.0000
scopes: missing [], extra []
Fixture 2: 1.0000
scopes: missing [], extra []
Fixture 3: 1.0000
scopes: 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}
Fixture 1: 1.0000
dashboards:widget 2/2: {'custom_ui_resource': True, 'edit_resource': True}
Fixture 2: 1.0000
dashboards:widget 2/2: {'custom_ui_resource': True, 'edit_resource': True}
Fixture 3: 1.0000
dashboards: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)
Fixture 1: 1.0000
4/4 board picks reached the dashboard through the widget edit API (updateConfig/onProductSave)
Fixture 2: 1.0000
4/4 board picks reached the dashboard through the widget edit API (updateConfig/onProductSave)
Fixture 3: 1.0000
4/4 board picks reached the dashboard through the widget edit API (updateConfig/onProductSave)
k rovo skill
1.00rovo:skill 7/7:
Fixture 1: 1.0000
rovo:skill 7/7:
Fixture 2: 1.0000
rovo:skill 7/7:
Fixture 3: 1.0000
rovo:skill 7/7:
k current apis
1.00current APIs 5/5:
Fixture 1: 1.0000
current APIs 5/5:
Fixture 2: 1.0000
current APIs 5/5:
Fixture 3: 1.0000
current APIs 5/5:
k consumer shape
1.00consumer shape 3/3
Fixture 1: 1.0000
consumer shape 3/3
Fixture 2: 1.0000
consumer shape 3/3
Fixture 3: 1.0000
consumer shape 3/3
k entity declared
1.00entities with a sprint-partitioned, ranged index: ['scope-change', 'scope-ledger', 'scope-member', 'sprint-issue']
Fixture 1: 1.0000
entities with a sprint-partitioned, ranged index: ['scope-change', 'scope-ledger', 'scope-member', 'sprint-issue']
Fixture 2: 1.0000
entities with a sprint-partitioned, ranged index: ['scope-change', 'scope-ledger', 'scope-member', 'sprint-issue']
Fixture 3: 1.0000
entities with a sprint-partitioned, ranged index: ['scope-change', 'scope-ledger', 'scope-member', 'sprint-issue']
k v2 surfacesdiagnostic, no weight
1.00v2 surfaces declared: ['jira:adminPage', 'webtrigger', 'scope-ledger']
Fixture 1: 1.0000
v2 surfaces declared: ['jira:adminPage', 'webtrigger', 'scope-ledger']
Fixture 2: 1.0000
v2 surfaces declared: ['jira:adminPage', 'webtrigger', 'scope-ledger']
Fixture 3: 1.0000
v2 surfaces declared: ['jira:adminPage', 'webtrigger', 'scope-ledger']
k rovo mcp
1.00rovo:mcp 4/4:
Fixture 1: 1.0000
rovo:mcp 4/4:
Fixture 2: 1.0000
rovo:mcp 4/4:
Fixture 3: 1.0000
rovo:mcp 4/4:
k llm model current
1.0013 LLM call(s); model ids list() does not return: []; llm module with claude: True
Fixture 1: 1.0000
13 LLM call(s); model ids list() does not return: []; llm module with claude: True
Fixture 2: 1.0000
13 LLM call(s); model ids list() does not return: []; llm module with claude: True
Fixture 3: 1.0000
13 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
Fixture 1: 1.0000
deploy readiness, manifest + permissions: 17 rules checked, none failing here
Fixture 2: 1.0000
deploy readiness, manifest + permissions: 17 rules checked, none failing here
Fixture 3: 1.0000
deploy readiness, manifest + permissions: 17 rules checked, none failing here
k runtime risks
1.00deploy readiness, predicted runtime failures: 12 rules checked, none failing here
Fixture 1: 1.0000
deploy readiness, predicted runtime failures: 12 rules checked, none failing here
Fixture 2: 1.0000
deploy readiness, predicted runtime failures: 12 rules checked, none failing here
Fixture 3: 1.0000
deploy 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
Fixture 1: 1.0000
1023/1023 deliveries handed off correctly
Fixture 2: 1.0000
996/996 deliveries handed off correctly
Fixture 3: 1.0000
1031/1031 deliveries handed off correctly
t event rows
1.00event rows: 170/170 exact (precision 1.00, recall 1.00)
Fixture 1: 1.0000
event rows: 170/170 exact (precision 1.00, recall 1.00)
Fixture 2: 1.0000
event rows: 172/172 exact (precision 1.00, recall 1.00)
Fixture 3: 1.0000
event rows: 174/174 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); 24 concurrent group(s) raced (independent 15, same-event 5, same-issue 4)
Fixture 1: 1.0000
every change holds at most one ledger row in every phase (duplicated deliveries included); 24 concurrent group(s) raced (independent 15, same-event 5, same-issue 4)
Fixture 2: 1.0000
every change holds at most one ledger row in every phase (duplicated deliveries included); 24 concurrent group(s) raced (independent 15, same-event 5, same-issue 4)
Fixture 3: 1.0000
every change holds at most one ledger row in every phase (duplicated deliveries included); 19 concurrent group(s) raced (independent 10, same-event 5, same-issue 4)
t out of order
0.8667worst of 3 scoring sites (seed 3c04f61f28a4a511): permuted deliveries: 11/11 rows exact, 2/4 sprints with oracle numbers
Fixture 1: 0.8667
permuted deliveries: 11/11 rows exact, 2/4 sprints with oracle numbers
Fixture 2: 1.0000
permuted deliveries: 10/10 rows exact, 3/3 sprints with oracle numbers
Fixture 3: 0.9286
permuted deliveries: 11/11 rows exact, 2/3 sprints with oracle numbers
t multi sprint parse
0.9917worst of 3 scoring sites (seed d031c3ee22136508): 120/121 multi-id Sprint changes recorded exactly
Fixture 1: 1.0000
123/123 multi-id Sprint changes recorded exactly
Fixture 2: 1.0000
131/131 multi-id Sprint changes recorded exactly
Fixture 3: 0.9917
120/121 multi-id Sprint changes recorded exactly
t reestimate followed
0.50worst of 3 scoring sites (seed d031c3ee22136508): 3/6 re-estimated sprints show the oracle numbers
Fixture 1: 0.6667
4/6 re-estimated sprints show the oracle numbers
Fixture 2: 0.8333
5/6 re-estimated sprints show the oracle numbers
Fixture 3: 0.5000
3/6 re-estimated sprints show the oracle numbers
t retry after honoured
1.00InvocationError retryAfter 30s >= 30s
Fixture 1: 1.0000
InvocationError retryAfter 30s >= 30s
Fixture 2: 1.0000
InvocationError retryAfter 30s >= 30s
Fixture 3: 1.0000
InvocationError retryAfter 30s >= 30s
t no user in async
1.00background work is asApp only
Fixture 1: 1.0000
background work is asApp only
Fixture 2: 1.0000
background work is asApp only
Fixture 3: 1.0000
background 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)
Fixture 1: 1.0000
130/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)
Fixture 2: 1.0000
103/103 historical changes v1 never recorded, recorded one virtual hour after the upgrade (the backfill is dosed; v1 rows are R1's, at 2 h)
Fixture 3: 1.0000
138/138 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
Fixture 1: 1.0000
24/24 removed-to-backlog changes found
Fixture 2: 1.0000
15/15 removed-to-backlog changes found
Fixture 3: 1.0000
20/20 removed-to-backlog changes found
r heal dropped
0.25worst of 3 scoring sites (seed 3c04f61f28a4a511): 1/4 dropped changes healed exactly once; 0 other row(s) added
Fixture 1: 0.2500
1/4 dropped changes healed exactly once; 0 other row(s) added
Fixture 2: 0.7500
3/4 dropped changes healed exactly once; 0 other row(s) added
Fixture 3: 0.2500
1/4 dropped changes healed exactly once; 0 other row(s) added
r pagination
1.0053/53 reads the site served in two or more pages walked to their end through the cursors the site offered (/rest/agile/1.0/board 16/16, /rest/agile/1.0/board/{id}/sprint 27/27, /rest/api/3/changelog/bulkfetch 5/5, /rest/
Fixture 1: 1.0000
53/53 reads the site served in two or more pages walked to their end through the cursors the site offered (/rest/agile/1.0/board 16/16, /rest/agile/1.0/board/{id}/sprint 27/27, /rest/api/3/changelog/bulkfetch 5/5, /rest/api/3/search/jql 5/5); 20 one-page read(s), nothing to walk, not graded
Fixture 2: 1.0000
347/347 reads the site served in two or more pages walked to their end through the cursors the site offered (/rest/agile/1.0/board 114/114, /rest/agile/1.0/board/{id}/sprint 223/223, /rest/api/3/changelog/bulkfetch 5/5, /rest/api/3/search/jql 5/5); 216 one-page read(s), nothing to walk, not graded; 1 persisted walk(s) resumed at the exact cursor in the same background lineage
Fixture 3: 1.0000
49/49 reads the site served in two or more pages walked to their end through the cursors the site offered (/rest/agile/1.0/board 16/16, /rest/agile/1.0/board/{id}/sprint 27/27, /rest/api/3/changelog/bulkfetch 3/3, /rest/api/3/search/jql 3/3); 20 one-page read(s), nothing to walk, not graded
r rate limit
1.00run 1 (backfill) request 2: waited 2.6 virtual s in-invocation; run 1 (backfill) continuation page: waited 2.6 virtual s in-invocation; run 2 (hour-1) request 2: waited 2.6 virtual s in-invocation
Fixture 1: 1.0000
run 1 (backfill) request 2: waited 2.6 virtual s in-invocation; run 1 (backfill) continuation page: waited 2.6 virtual s in-invocation; run 2 (hour-1) request 2: waited 2.6 virtual s in-invocation
Fixture 2: 1.0000
run 1 (backfill) request 2: waited 2.6 virtual s in-invocation; run 1 (backfill) continuation page: waited 2.6 virtual s in-invocation; run 2 (hour-1) request 2: waited 2.6 virtual s in-invocation
Fixture 3: 1.0000
run 1 (backfill) request 2: waited 2.6 virtual s in-invocation; run 1 (backfill) continuation page: waited 2.6 virtual s in-invocation; run 2 (hour-1) request 2: waited 2.6 virtual s in-invocation
r as app
1.00153/153 Jira calls of the scheduled runs and their queue continuations asApp (scheduled 153)
Fixture 1: 1.0000
153/153 Jira calls of the scheduled runs and their queue continuations asApp (scheduled 153)
Fixture 2: 1.0000
1327/1327 Jira calls of the scheduled runs and their queue continuations asApp (consumer 1203, scheduled 124)
Fixture 3: 1.0000
138/138 Jira calls of the scheduled runs and their queue continuations asApp (scheduled 138)
r completes in timeout
1.008/8 invocations of the scheduled runs and their queue continuations inside their module timeout (scheduled 8)
Fixture 1: 1.0000
8/8 invocations of the scheduled runs and their queue continuations inside their module timeout (scheduled 8)
Fixture 2: 1.0000
107/107 invocations of the scheduled runs and their queue continuations inside their module timeout (consumer 99, scheduled 8)
Fixture 3: 1.0000
8/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 360 rows
Fixture 1: 1.0000
0 ledger write(s) (scope-ledger) on a no-change run over 360 rows
Fixture 2: 1.0000
0 ledger write(s) (scope-ledger) on a no-change run over 378 rows
Fixture 3: 1.0000
0 ledger write(s) (scope-ledger) on a no-change run over 379 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
Fixture 1: 1.0000
KVS used, no 403 from the KVS proxy
Fixture 2: 1.0000
KVS used, no 403 from the KVS proxy
Fixture 3: 1.0000
KVS used, no 403 from the KVS proxy
s entity index used
1.00795/795 ledger reads are entity queries on a declared index
Fixture 1: 1.0000
795/795 ledger reads are entity queries on a declared index
Fixture 2: 1.0000
1405/1405 ledger reads are entity queries on a declared index
Fixture 3: 1.0000
784/784 ledger reads are entity queries on a declared index
s index order
1.006/6 tables list changes in change-time order
Fixture 1: 1.0000
6/6 tables list changes in change-time order
Fixture 2: 1.0000
6/6 tables list changes in change-time order
Fixture 3: 1.0000
6/6 tables list changes in change-time order
s limits
1.00no KVS limit errors
Fixture 1: 1.0000
no KVS limit errors
Fixture 2: 1.0000
no KVS limit errors
Fixture 3: 1.0000
no 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.0057/57 invokes returned a defined, structured result; a Jira 500 on sprintLedger's read: handled
Fixture 1: 1.0000
57/57 invokes returned a defined, structured result; a Jira 500 on sprintLedger's read: handled
Fixture 2: 1.0000
57/57 invokes returned a defined, structured result; a Jira 500 on sprintLedger's read: handled
Fixture 3: 1.0000
57/57 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
Fixture 1: 1.0000
no hidden key, summary or change id reached a person
Fixture 2: 1.0000
no hidden key, summary or change id reached a person
Fixture 3: 1.0000
no hidden key, summary or change id reached a person
b hidden count
0.9444worst of 3 scoring sites (seed 3c04f61f28a4a511): 17/18 hidden counts equal the oracle
Fixture 1: 0.9444
17/18 hidden counts equal the oracle
Fixture 2: 1.0000
18/18 hidden counts equal the oracle
Fixture 3: 0.9444
17/18 hidden counts equal the oracle
b comment adf as user
0.6667worst of 3 scoring sites (seed 3c04f61f28a4a511): 8/12 comments are ADF as the viewer naming key, sprint and creep; ['34183 status 201 via user', '37609 status 201 via user', '36424 status 201 via user']
Fixture 1: 0.6667
8/12 comments are ADF as the viewer naming key, sprint and creep; ['34183 status 201 via user', '37609 status 201 via user', '36424 status 201 via user']
Fixture 2: 0.8333
10/12 comments are ADF as the viewer naming key, sprint and creep; ['27265 status 201 via user', '26646 status 201 via user']
Fixture 3: 0.6667
8/12 comments are ADF as the viewer naming key, sprint and creep; ['25732 status 201 via user', '25037 status 201 via user', '27349 status 201 via user']
b comment exactly once
1.0012 click/double-click gesture(s), none posted more than one comment
Fixture 1: 1.0000
12 click/double-click gesture(s), none posted more than one comment
Fixture 2: 1.0000
12 click/double-click gesture(s), none posted more than one comment
Fixture 3: 1.0000
12 click/double-click gesture(s), none posted more than one comment
b realtime payload clean
1.00206/206 realtime payloads hold sprint ids only
Fixture 1: 1.0000
206/206 realtime payloads hold sprint ids only
Fixture 2: 1.0000
193/193 realtime payloads hold sprint ids only
Fixture 3: 1.0000
199/199 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
Fixture 1: 1.0000
6/8 configured widget views render a sprint with its numbers
Fixture 2: 1.0000
6/8 configured widget views render a sprint with its numbers
Fixture 3: 1.0000
6/8 configured widget views render a sprint with its numbers
u widget numbers
0.625worst of 3 scoring sites (seed d031c3ee22136508): widget numbers: 5.00/8 views exact (sprints by startDate, four §1 numbers each)
Fixture 1: 0.7500
widget numbers: 6.00/8 views exact (sprints by startDate, four §1 numbers each)
Fixture 2: 0.7500
widget numbers: 6.00/8 views exact (sprints by startDate, four §1 numbers each)
Fixture 3: 0.6250
widget numbers: 5.00/8 views exact (sprints by startDate, four §1 numbers each)
u widget chart
0.50worst of 3 scoring sites (seed d031c3ee22136508): 4/8 charts on one linear scale within 1px; ['worst bar off its linear scale by 3.42px', 'worst bar off its linear scale by 3.42px']
Fixture 1: 1.0000
8/8 charts on one linear scale within 1px
Fixture 2: 0.7500
6/8 charts on one linear scale within 1px; ['worst bar off its linear scale by 1.23px', 'worst bar off its linear scale by 1.23px']
Fixture 3: 0.5000
4/8 charts on one linear scale within 1px; ['worst bar off its linear scale by 3.42px', 'worst bar off its linear scale by 3.42px']
u widget edit config
1.00edit/config 10/10:
Fixture 1: 1.0000
edit/config 10/10:
Fixture 2: 1.0000
edit/config 10/10:
Fixture 3: 1.0000
edit/config 10/10:
u ledger table
0.9205worst of 3 scoring sites (seed d031c3ee22136508): ledger tables: 5.52/6 exact (rows, cells, default order)
Fixture 1: 0.9572
ledger tables: 5.74/6 exact (rows, cells, default order)
Fixture 2: 0.9593
ledger tables: 5.76/6 exact (rows, cells, default order)
Fixture 3: 0.9205
ledger tables: 5.52/6 exact (rows, cells, default order)
u ledger sort
0.1667worst of 3 scoring sites (seed 3c04f61f28a4a511): 3/18 at-toggle states ordered with aria-sort (6 after another sort was active)
Fixture 1: 0.1667
3/18 at-toggle states ordered with aria-sort (6 after another sort was active)
Fixture 2: 0.2778
5/18 at-toggle states ordered with aria-sort (6 after another sort was active)
Fixture 3: 0.1667
3/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
Fixture 1: 1.0000
6/6 issue keys open /browse/<KEY> through the Forge router
Fixture 2: 1.0000
6/6 issue keys open /browse/<KEY> through the Forge router
Fixture 3: 1.0000
6/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']
Fixture 1: 0.9688
31/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']
Fixture 2: 0.9688
31/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@984']
Fixture 3: 0.9688
31/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@1056']
u modal close
1.006/6 close clicks reached bridge close
Fixture 1: 1.0000
6/6 close clicks reached bridge close
Fixture 2: 1.0000
6/6 close clicks reached bridge close
Fixture 3: 1.0000
6/6 close clicks reached bridge close
u not started
1.00future sprint shows not-started only
Fixture 1: 1.0000
future sprint shows not-started only
Fixture 2: 1.0000
future sprint shows not-started only
Fixture 3: 1.0000
future sprint shows not-started only
u widget live
0.00worst of 3 scoring sites (seed 3c04f61f28a4a511): moved sprints showing the new numbers live 0/1; 0 idle invoke(s)
Fixture 1: 0.0000
moved sprints showing the new numbers live 0/1; 0 idle invoke(s)
Fixture 2: 1.0000
moved sprints showing the new numbers live 1/1; 0 idle invoke(s)
Fixture 3: 0.0000
moved sprints showing the new numbers live 0/1; 0 idle invoke(s)
u llm explain
0.8696explain 20/23 over 5 scripted answers: 2:refusal:modal_still_sorts, 3:malformed:modal_still_sorts, 4:error:modal_still_sorts
Fixture 1: 0.8696
explain 20/23 over 5 scripted answers: 2:refusal:modal_still_sorts, 3:malformed:modal_still_sorts, 4:error:modal_still_sorts
Fixture 2: 0.8696
explain 20/23 over 5 scripted answers: 2:refusal:modal_still_sorts, 3:malformed:modal_still_sorts, 4:error:modal_still_sorts
Fixture 3: 0.8696
explain 20/23 over 5 scripted answers: 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.0031/31 surfaces themed with --ds-text* at >= 4.5:1
Fixture 1: 1.0000
31/31 surfaces themed with --ds-text* at >= 4.5:1
Fixture 2: 1.0000
31/31 surfaces themed with --ds-text* at >= 4.5:1
Fixture 3: 1.0000
31/31 surfaces themed with --ds-text* at >= 4.5:1
v dark mode
1.0031/31 surfaces paint a --ds-surface* background in their mode
Fixture 1: 1.0000
31/31 surfaces paint a --ds-surface* background in their mode
Fixture 2: 1.0000
31/31 surfaces paint a --ds-surface* background in their mode
Fixture 3: 1.0000
31/31 surfaces paint a --ds-surface* background in their mode
v csp clean
1.000 CSP violation(s), 0 failed asset request(s)
Fixture 1: 1.0000
0 CSP violation(s), 0 failed asset request(s)
Fixture 2: 1.0000
0 CSP violation(s), 0 failed asset request(s)
Fixture 3: 1.0000
0 CSP violation(s), 0 failed asset request(s)
v console clean
1.000 console/page error(s) on nominal scenarios: []
Fixture 1: 1.0000
0 console/page error(s) on nominal scenarios: []
Fixture 2: 1.0000
0 console/page error(s) on nominal scenarios: []
Fixture 3: 1.0000
0 console/page error(s) on nominal scenarios: []
v widget sizes
1.006/6 widget sizes without horizontal overflow, every sprint visible, no number clipped
Fixture 1: 1.0000
6/6 widget sizes without horizontal overflow, every sprint visible, no number clipped
Fixture 2: 1.0000
6/6 widget sizes without horizontal overflow, every sprint visible, no number clipped
Fixture 3: 1.0000
6/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.40worst of 3 scoring sites (seed 3c04f61f28a4a511): 2/5 active sprints answered exactly
Fixture 1: 0.4000
2/5 active sprints answered exactly
Fixture 2: 0.8000
4/5 active sprints answered exactly
Fixture 3: 0.4000
2/5 active sprints answered exactly
a action errors
1.002/2 bad sprintId inputs return {error} without throwing
Fixture 1: 1.0000
2/2 bad sprintId inputs return {error} without throwing
Fixture 2: 1.0000
2/2 bad sprintId inputs return {error} without throwing
Fixture 3: 1.0000
2/2 bad sprintId inputs return {error} without throwing
a action permissions
0.50worst of 3 scoring sites (seed 3c04f61f28a4a511): 6/12 per-person answers list exactly what that person may browse
Fixture 1: 0.5000
6/12 per-person answers list exactly what that person may browse
Fixture 2: 0.8333
10/12 per-person answers list exactly what that person may browse
Fixture 3: 0.5000
6/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']
Fixture 1: 1.0000
SKILL.md body 5/5: result fields named ['sprintName', 'committed', 'added', 'removed', 'creepPercent', 'hiddenChanges', 'changes']
Fixture 2: 1.0000
SKILL.md body 5/5: result fields named ['sprintName', 'committed', 'added', 'removed', 'creepPercent', 'hiddenChanges', 'changes']
Fixture 3: 1.0000
SKILL.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: (1.0000 + 1.0000 + 1.0000) / 3 = 1.0000; each fixture's measurements are listed separately.
Fixture 1: 1.0000
backfill 34 background Jira calls (by lineage, every phase) / optimum 20 (incl. 2 forced 429 repeat(s)) = 1.70x; 1.0 at <= 2.45x; 2 2.0 call(s) not counted (field-value writes, person-facing, web trigger)
Fixture 2: 1.0000
backfill 34 background Jira calls (by lineage, every phase) / optimum 20 (incl. 2 forced 429 repeat(s)) = 1.70x; 1.0 at <= 2.45x; 2 2.0 call(s) not counted (field-value writes, person-facing, web trigger)
Fixture 3: 1.0000
backfill 34 background Jira calls (by lineage, every phase) / optimum 20 (incl. 2 forced 429 repeat(s)) = 1.70x; 1.0 at <= 2.45x; 2 2.0 call(s) not counted (field-value writes, person-facing, web trigger)
e event economy
0.9684mean over 3 scoring sites: (0.9936 + 0.9438 + 0.9677) / 3 = 0.9684; each fixture's measurements are listed separately.
Fixture 1: 0.9936
616 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) = 2.88x; 1.0 at <= 2.86x; 167 field-value write(s) not counted
Fixture 2: 0.9438
603 Jira calls (by lineage, every phase) / baseline 199 (198 delivered relevant change(s) x 1 read + 1 forced 429 repeat; a normalizer, not a reachable optimum) = 3.03x; 1.0 at <= 2.86x; 167 field-value write(s) not counted
Fixture 3: 0.9677
597 Jira calls (by lineage, every phase) / baseline 202 (201 delivered relevant change(s) x 1 read + 1 forced 429 repeat; a normalizer, not a reachable optimum) = 2.96x; 1.0 at <= 2.86x; 178 field-value write(s) not counted
e ui round trips
1.00mean over 3 scoring sites: (1.0000 + 1.0000 + 1.0000) / 3 = 1.0000; each fixture's measurements are listed separately.
Fixture 1: 1.0000
round trips before first paint: {'widget-view': 0, 'widget-edit': 1, 'sprint-action': 1}
Fixture 2: 1.0000
round trips before first paint: {'widget-view': 0, 'widget-edit': 1, 'sprint-action': 1}
Fixture 3: 1.0000
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
Fixture 1: 1.0000
h2: 59 of 59 v1 rows in scope-ledger with the source attributes recorded by the probe
Fixture 2: 1.0000
h2: 100 of 100 v1 rows in scope-ledger with the source attributes recorded by the probe
Fixture 3: 1.0000
h2: 66 of 66 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
Fixture 1: 1.0000
all 59 v1 source rows intact; 59 final copies preserve recorded v1 attributes at every observed checkpoint
Fixture 2: 1.0000
all 100 v1 source rows intact; 100 final copies preserve recorded v1 attributes at every observed checkpoint
Fixture 3: 1.0000
all 66 v1 source rows intact; 66 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
Fixture 1: 1.0000
48 of 48 changes made while the migration ran are in scope-ledger at the end
Fixture 2: 1.0000
47 of 47 changes made while the migration ran are in scope-ledger at the end
Fixture 3: 1.0000
64 of 64 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)
Fixture 1: 1.0000
6 of 6 panel reads show the migration right (total 59; complete after the h2 read)
Fixture 2: 1.0000
6 of 6 panel reads show the migration right (total 100; complete after the h2 read)
Fixture 3: 1.0000
6 of 6 panel reads show the migration right (total 66; 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.009 of 9 hours kept background within 70 % (1680 points; the contract default; the probe recorded no change); busiest hour 1498; mandatory field-write lower bound 7 (reads additional)
Fixture 1: 1.0000
9 of 9 hours kept background within 70 % (1680 points; the contract default; the probe recorded no change); busiest hour 1498; mandatory field-write lower bound 7 (reads additional)
Fixture 2: 1.0000
32 of 32 hours kept background within 70 % (1680 points; the contract default; the probe recorded no change); busiest hour 1676; mandatory field-write lower bound 7 (reads additional)
Fixture 3: 1.0000
9 of 9 hours kept background within 70 % (1680 points; the contract default; the probe recorded no change); busiest hour 1009; mandatory field-write lower bound 7 (reads additional)
r2 person never quota refused
1.000 of 1084 person-facing requests refused for quota
Fixture 1: 1.0000
0 of 1084 person-facing requests refused for quota
Fixture 2: 1.0000
0 of 1123 person-facing requests refused for quota
Fixture 3: 1.0000
0 of 1123 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)
Fixture 1: 1.0000
5 of 5 429s answered by their reason (quota: all background paused; burst: the endpoint; per-issue: the issue)
Fixture 2: 1.0000
5 of 5 429s answered by their reason (quota: all background paused; burst: the endpoint; per-issue: the issue)
Fixture 3: 1.0000
5 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
Fixture 1: 1.0000
130 of 130 pre-upgrade changes v1 never recorded are in scope-ledger, right
Fixture 2: 1.0000
103 of 103 pre-upgrade changes v1 never recorded are in scope-ledger, right
Fixture 3: 1.0000
138 of 138 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
Fixture 1: 1.0000
9 of 9 functions never exceeded their limit
Fixture 2: 1.0000
9 of 9 functions never exceeded their limit
Fixture 3: 1.0000
9 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)
Fixture 1: 1.0000
1 of 1 invocations handed a Retry-After longer than their limit stopped and resumed later (results: retry)
Fixture 2: 1.0000
1 of 1 invocations handed a Retry-After longer than their limit stopped and resumed later (results: retry)
Fixture 3: 1.0000
1 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; 24 concurrent group(s) raced (independent 15, same-event 5, same-issue 4)
Fixture 1: 1.0000
every (changeId, sprintId) appears once at each of 7 checkpoints; 24 concurrent group(s) raced (independent 15, same-event 5, same-issue 4)
Fixture 2: 1.0000
every (changeId, sprintId) appears once at each of 7 checkpoints; 24 concurrent group(s) raced (independent 15, same-event 5, same-issue 4)
Fixture 3: 1.0000
every (changeId, sprintId) appears once at each of 7 checkpoints; 19 concurrent group(s) raced (independent 10, 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
Fixture 1: 1.0000
1 of 1 closed sprints kept exactly their final ledger
Fixture 2: 1.0000
1 of 1 closed sprints kept exactly their final ledger
Fixture 3: 1.0000
1 of 1 closed sprints kept exactly their final ledger
r4 move new board
1.0017 of 17 cross-board moves recorded with the new board's estimate
Fixture 1: 1.0000
17 of 17 cross-board moves recorded with the new board's estimate
Fixture 2: 1.0000
11 of 11 cross-board moves recorded with the new board's estimate
Fixture 3: 1.0000
18 of 18 cross-board moves recorded with the new board's estimate
r4 field switch
0.9839worst of 3 scoring sites (seed 3c04f61f28a4a511): 41 of 42 rows after the switch use the new field; 20 of 20 earlier rows keep their estimate; wrong after: ('1464099', '1026')
Fixture 1: 0.9839
41 of 42 rows after the switch use the new field; 20 of 20 earlier rows keep their estimate; wrong after: ('1464099', '1026')
Fixture 2: 1.0000
41 of 41 rows after the switch use the new field; 11 of 11 earlier rows keep their estimate
Fixture 3: 0.9848
34 of 35 rows after the switch use the new field; 31 of 31 earlier rows keep their estimate; wrong after: ('1358087', '924')
r4 deleted history
1.002 of 2 rows of deleted issues kept as history with deleted: true
Fixture 1: 1.0000
2 of 2 rows of deleted issues kept as history with deleted: true
Fixture 2: 1.0000
3 of 3 rows of deleted issues kept as history with deleted: true
Fixture 3: 1.0000
2 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
Fixture 1: 1.0000
4 answer(s) after a browse revoke showed ledger data and none of the newly hidden issues
Fixture 2: 1.0000
5 answer(s) after a browse revoke showed ledger data and none of the newly hidden issues
Fixture 3: 1.0000
4 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
Fixture 1: 1.0000
8 of 8 §2.6 controls found by label; new secret shown once: yes; then masked ••••<last4>: yes
Fixture 2: 1.0000
8 of 8 §2.6 controls found by label; new secret shown once: yes; then masked ••••<last4>: yes
Fixture 3: 1.0000
8 of 8 §2.6 controls found by label; new secret shown once: yes; then masked ••••<last4>: yes
r5 admin actions apply
1.002 of 2 admin-page invokes of the admin's save and rotate applied
Fixture 1: 1.0000
2 of 2 admin-page invokes of the admin's save and rotate applied
Fixture 2: 1.0000
2 of 2 admin-page invokes of the admin's save and rotate applied
Fixture 3: 1.0000
2 of 2 admin-page invokes of the admin's save and rotate applied
r5 nonadmin refused
1.004 non-admin/forged admin actions landed no attempted effect in storage
Fixture 1: 1.0000
4 non-admin/forged admin actions landed no attempted effect in storage
Fixture 2: 1.0000
4 non-admin/forged admin actions landed no attempted effect in storage
Fixture 3: 1.0000
4 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
Fixture 1: 1.0000
5 invalid events (bad-signature, stale, stale-future, tampered, unsigned) had no effect
Fixture 2: 1.0000
5 invalid events (bad-signature, stale, stale-future, tampered, unsigned) had no effect
Fixture 3: 1.0000
5 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
Fixture 1: 1.0000
1 sequential replay(s) and one concurrent pair had one acceptance and no duplicate Jira/deployment effect at any checkpoint; bookkeeping writes 0
Fixture 2: 1.0000
1 sequential replay(s) and one concurrent pair had one acceptance and no duplicate Jira/deployment effect at any checkpoint; bookkeeping writes 0
Fixture 3: 1.0000
1 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
Fixture 1: 1.0000
10 of 10 cases answered with their status
Fixture 2: 1.0000
10 of 10 cases answered with their status
Fixture 3: 1.0000
10 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
Fixture 1: 1.0000
3 of 3 validly signed events accepted (202) and recorded as `Deployed to <env>` on every ledger row of the issues they name
Fixture 2: 1.0000
3 of 3 validly signed events accepted (202) and recorded as `Deployed to <env>` on every ledger row of the issues they name
Fixture 3: 1.0000
3 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
Fixture 1: 1.0000
the CI secret (panel) never appeared outside its one-time display
Fixture 2: 1.0000
the CI secret (panel) never appeared outside its one-time display
Fixture 3: 1.0000
the 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.9123worst of 3 scoring sites (seed d031c3ee22136508): mean over 7 checkpoints; worst h5: 282 of 354 issues right; CORE-407 'committed' (want removed); NOTIF-106 'committed' (want )
Fixture 1: 0.9973
mean over 7 checkpoints; worst final: 303 of 306 issues right; AUTH-214 'committed' (want added +5, removed); AUTH-338 None (want added +0.5)
Fixture 2: 0.9955
mean over 7 checkpoints; worst h6: 316 of 320 issues right; CRM-237 None (want added +2); CRM-412 'added +0' (want added +1)
Fixture 3: 0.9123
mean over 7 checkpoints; worst h5: 282 of 354 issues right; CORE-407 'committed' (want removed); NOTIF-106 'committed' (want )
r7 writes accepted
0.63worst of 3 scoring sites (seed 3aaa6d6b73d37669): 172 of 273 bulk field writes accepted; refused: 404
Fixture 1: 0.9774
173 of 177 bulk field writes accepted; refused: 404
Fixture 2: 0.6300
172 of 273 bulk field writes accepted; refused: 404
Fixture 3: 0.9681
182 of 188 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
Fixture 1: 1.0000
2 of 2 manipulated calls respected function and visible sprint scope
Fixture 2: 1.0000
2 of 2 manipulated calls respected function and visible sprint scope
Fixture 3: 1.0000
2 of 2 manipulated calls respected function and visible sprint scope
r8 failure handling
1.002 of 2 LLM failures handled
Fixture 1: 1.0000
2 of 2 LLM failures handled
Fixture 2: 1.0000
2 of 2 LLM failures handled
Fixture 3: 1.0000
2 of 2 LLM failures handled
r8 cost controls
1.003 of 3 cache/kill-switch/budget cases met their full outcome
Fixture 1: 1.0000
3 of 3 cache/kill-switch/budget cases met their full outcome
Fixture 2: 1.0000
3 of 3 cache/kill-switch/budget cases met their full outcome
Fixture 3: 1.0000
3 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), 102029 bytes of JS+CSS (<= 153600), 0 external request(s)
Fixture 1: 1.0000
widget-view: 1 invoke(s) before first paint (<= 1), 102029 bytes of JS+CSS (<= 153600), 0 external request(s)
Fixture 2: 1.0000
widget-view: 1 invoke(s) before first paint (<= 1), 102029 bytes of JS+CSS (<= 153600), 0 external request(s)
Fixture 3: 1.0000
widget-view: 1 invoke(s) before first paint (<= 1), 102029 bytes of JS+CSS (<= 153600), 0 external request(s)
r9 sprint boot
1.00sprint-modal: 1 invoke(s) before first paint (<= 1), 106135 bytes of JS+CSS (<= 153600), 0 external request(s)
Fixture 1: 1.0000
sprint-modal: 1 invoke(s) before first paint (<= 1), 106135 bytes of JS+CSS (<= 153600), 0 external request(s)
Fixture 2: 1.0000
sprint-modal: 1 invoke(s) before first paint (<= 1), 106135 bytes of JS+CSS (<= 153600), 0 external request(s)
Fixture 3: 1.0000
sprint-modal: 1 invoke(s) before first paint (<= 1), 106135 bytes of JS+CSS (<= 153600), 0 external request(s)
r9 admin boot
1.00admin-page: 1 invoke(s) before first paint (<= 1)
Fixture 1: 1.0000
admin-page: 1 invoke(s) before first paint (<= 1)
Fixture 2: 1.0000
admin-page: 1 invoke(s) before first paint (<= 1)
Fixture 3: 1.0000
admin-page: 1 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
Fixture 1: 1.0000
scopeChanged manifest declares issue IN/NOT IN, required sprintId, and bound function
Fixture 2: 1.0000
scopeChanged manifest declares issue IN/NOT IN, required sprintId, and bound function
Fixture 3: 1.0000
scopeChanged manifest declares issue IN/NOT IN, required sprintId, and bound function
r10 initial membership
1.0024/24 initial_membership cases correct
Fixture 1: 1.0000
24/24 initial_membership cases correct
Fixture 2: 1.0000
24/24 initial_membership cases correct
Fixture 3: 1.0000
24/24 initial_membership cases correct
r10 precomputation refresh
0.75worst of 3 scoring sites (seed d031c3ee22136508): 18/24 precomputation_refresh cases correct; refresh: missing=['23989'], extra=[], invoked=0; refresh: missing=[], extra=['23989'], invoked=0
Fixture 1: 0.9167
22/24 precomputation_refresh cases correct; refresh: missing=['37837'], extra=[], invoked=0; refresh: missing=[], extra=['37837'], invoked=0
Fixture 2: 0.9167
22/24 precomputation_refresh cases correct; refresh: missing=['24436'], extra=[], invoked=0; refresh: missing=[], extra=['24436'], invoked=0
Fixture 3: 0.7500
18/24 precomputation_refresh cases correct; refresh: missing=['23989'], extra=[], invoked=0; refresh: missing=[], extra=['23989'], invoked=0
r10 shared permissions
0.8611worst of 3 scoring sites (seed d031c3ee22136508): JQL disclosure not observed: 62/72 shared_permissions cases correct; shared-user: missing=['23989'], extra=[], invoked=0; shared-user: missing=[], extra=['23989'], invoke
Fixture 1: 0.9722
JQL disclosure not observed: 70/72 shared_permissions cases correct; shared-user: missing=['37837'], extra=[], invoked=0; shared-user: missing=[], extra=['37837'], invoked=0
Fixture 2: 0.9444
JQL disclosure not observed: 68/72 shared_permissions cases correct; shared-user: missing=['24436'], extra=[], invoked=0; shared-user: missing=['24436'], extra=[], invoked=0
Fixture 3: 0.8611
JQL disclosure not observed: 62/72 shared_permissions cases correct; shared-user: missing=['23989'], extra=[], invoked=0; shared-user: missing=[], extra=['23989'], invoked=0
r10 empty and closed
1.004/4 empty_and_closed cases correct
Fixture 1: 1.0000
4/4 empty_and_closed cases correct
Fixture 2: 1.0000
4/4 empty_and_closed cases correct
Fixture 3: 1.0000
4/4 empty_and_closed cases correct
r10 invalid arguments
1.004/4 invalid_arguments cases correct
Fixture 1: 1.0000
4/4 invalid_arguments cases correct
Fixture 2: 1.0000
4/4 invalid_arguments cases correct
Fixture 3: 1.0000
4/4 invalid_arguments cases correct
Run notes and corrections
Canonical native verdict summary reports $35.9783692, 192 billed generations and 62392147 prompt / 61848576 cached / 240515 completion tokens. Per-call request and invoice correspondence remains an observation; no independent raw invoice audit is claimed.
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: 0e78b51723c06bc21e0b05863876b6890d5a2f2e9146664801564f75d985e074
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
- qwen/qwen3.8-max-prime
- Engine events
- 0
- Repair rounds
- 0
- Started
- Oct 15, 2026, 05:50 AM
- Finished
- Oct 15, 2026, 07:24 AM