Cloud baseline
xiaomi/mimo-v2.6-flash, single model via OpenRouter — 0.5016 on Forge 1.0
xiaomi/mimo-v2.6-flash · scorer forge-1.0
- Overall
- 0.5016
- Excellent
- no
- Benchmark
- Forge 1.0
- Model build
- 54m 46s
Tier breakdown
Scoring detail
How this score was built
Per-check scorer output, as posted by the app. Expand a section to inspect its checks.
Earned credit before admission
(0.88 × 0.8597 core + 0.12 × 0.88 gate × 0.75 excellence) × 0.6000 critical = 0.5016
Critical defects compound a multiplier on the whole score (pre-severity 0.8360):
The core (88% of the total) is the weighted mean of the nine measured tiers. The last 12% is the excellence slice: it unlocks in proportion to the perfection conditions below (14 of 18 met here), then pays out at the excellence tier's own measured mean. Core 0.7565 + excellence 0.0795.
Earned score 0.502 · Cap 0.799 · Final score 0.502
The final score is the lower of the earned score and the cap. Meeting a cap's conditions adds no points.
- current platform, complete surfaces: maximum 0.799
u_ledger_tablea_action_resultv_theme_tokens - production robustness: maximum 0.809
t_out_of_orderb_comment_exactly_onceu_llm_explainu_widget_live
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.005/5 functions bundle, load and export their handler
l lint warnings
1.000 distinct lint warning(s): []
l real packages
1.005/5 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.002/2 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: ['ledger-change', 'sprint-issue']
k rovo mcp
1.00rovo:mcp 4/4:
k llm model current
1.005 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
0.92deploy readiness, predicted runtime failures: 12 rules checked; failing (priced here): R7 no hard-coded custom field id [src/ledger.js]
Issue updates flow trigger to queue to consumer: one ledger row per change under duplicate, reordered and dropped deliveries, multi-sprint changelog values, re-estimates followed, Retry-After honoured, no user context in background work.
t trigger handoff
1.0045/45 deliveries handed off correctly
t event rows
1.00event rows: 33/33 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)
t out of order
0.67permuted deliveries: 4/4 rows exact, 0/2 sprints with oracle numbers
t multi sprint parse
1.0018/18 multi-id Sprint changes recorded exactly
t reestimate followed
0.000/2 re-estimated sprints show the oracle numbers
t retry after honoured
1.00waited 30.0 virtual s in-invocation
t no user in async
1.00background work is asApp only
The first scheduled run backfills every change since each active sprint started, removals included; later runs heal what the event stream missed, page through results in each endpoint's own style, wait out rate limits and finish inside the module timeout.
r backfill complete
1.0059/59 historical changes recorded exactly after the first scheduled run
r removals found
1.0015/15 removed-to-backlog changes found
r heal dropped
1.003/3 dropped changes healed exactly once; 0 other row(s) added
r pagination
1.0075/75 paginated reads walked to their end
r rate limit
1.00waited 2.0 virtual s in-invocation
r as app
1.0026/26 scheduled-run Jira calls asApp
r completes in timeout
1.003/3 scheduled invocations inside the module timeout
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
1.0020/20 ledger reads are entity queries on the sprint index
s index order
1.003/3 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.0031/31 invokes returned a defined, structured result
b no permission leak
1.00no hidden key, summary or change id reached a person
b hidden count
1.009/9 hidden counts equal the oracle
b comment adf as user
0.000/6 comments are ADF as the viewer naming key, sprint and creep; ['WEB-21 status 201 via user', 'WEB-21 status 201 via user', 'FIN-450 status 201 via user']
b comment exactly once
0.00not exactly once: ['post@958: 1 comment(s), 0 success flag(s)', 'doubleClick@958: 1 comment(s), 0 success flag(s)', 'post@1018: 1 comment(s), 0 success flag(s)', 'doubleClick@1018: 1 comment(s), 0 success flag(s)']
b realtime payload clean
1.0032/32 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 loads
1.004/4 configured widget views render a sprint with its numbers
u widget numbers
0.00widget numbers: 0.00/4 views exact (sprints by startDate, four §1 numbers each)
u widget chart
0.000/4 charts on one linear scale within 1px; ['worst bar off its linear scale by 24.63px', 'worst bar off its linear scale by 24.24px']
u widget edit config
1.00edit/config 6/6:
u ledger table
0.99ledger tables: 2.97/3 exact (rows, cells, default order)
u ledger sort
1.006/6 at-toggle states ordered with aria-sort
u issue router
1.003/3 issue keys open /browse/<KEY> through the Forge router
u comment flow
0.504/8 comment-flow steps right (select, success flag, forbidden error flag, modal works)
u modal close
0.672/3 close clicks reached bridge close
u not started
1.00future sprint shows not-started only
u widget live
0.75live widget 3/4: shows_new_numbers; 0 idle invoke(s), sprints right after the live changes 0/2
u llm explain
0.85explain 17/20 over 5 scripted answers: 2:refusal:error_flag, 3:malformed:error_flag, 4:error:error_flag
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
0.6511/17 surfaces themed with --ds-text* at >= 4.5:1; failing ['sprint-action-958-light-800x600', 'sprint-action-958-dark-800x600', 'sprint-action-1018-light-800x600', 'sprint-action-1018-dark-800x600']
v dark mode
1.0017/17 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.004/4 widget sizes without horizontal overflow, every sprint visible
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/3 active sprints answered exactly
a action errors
1.002/2 bad sprintId inputs return {error} without throwing
a action permissions
1.006/6 per-person answers list exactly what that person may browse
a skill instructions
1.00SKILL.md body 3/3
Few Jira requests in the backfill and per event, few round trips before each surface paints, and a scheduled run with nothing new writes nothing — paid only in proportion to the excellence gate.
e reconcile economy
1.00backfill 10 Jira calls / optimum 9 = 1.11x
e event economy
1.0077 Jira calls for 34 relevant changes = 2.26 per change (optimum 1)
e ui round trips
1.00round trips before first paint: {'widget-view': 0, 'widget-edit': 1, 'sprint-action': 1}
e idempotent rerun
0.0016 entity write(s) on a no-change run over 95 rows
Graded browser recording
Loading duration…Watch the full graded browser recording at its original speed: the payment field, structure inspection, committed updates and replay. The check results and screenshots on this page provide the wider evidence. Pause or scrub to inspect a view.
Each tower represents a payment: height encodes its amount, cap color its status, and the collar its currency. The selected detailed tower is expected to animate its collar after a committed backend update or replay. These are the task requirements; the check results show what this app actually achieved.
Drag the timeline to seek. Keyboard: arrow keys move 5 seconds; Home and End jump to the start and end.
Recording integrity
SHA-256: baed682667369e36f154f9b01efc231cf1243d099c365733b78f4d90a36b1140
Screenshots
Captured from the built application during browser grading. Captions identify the recorded views and checks; these images do not represent repair rounds.
Run details
- Model
- xiaomi/mimo-v2.6-flash
- Engine events
- 0
- Repair rounds
- 0
- Started
- Oct 3, 2026, 11:21 AM
- Finished
- Oct 3, 2026, 12:21 PM