Cloud baseline
tencent/hy4-preview, single model via OpenRouter — 0.4796 on Forge 1.0
tencent/hy4-preview · scorer forge-1.0
- Overall
- 0.4796
- Excellent
- no
- Benchmark
- Forge 1.0
- Model build
- 37m 52s
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.8341 core + 0.12 × 0.82 gate × 0.67 excellence) × 0.6000 critical = 0.4796
Critical defects compound a multiplier on the whole score (pre-severity 0.7993):
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 (13 of 18 met here), then pays out at the excellence tier's own measured mean. Core 0.7340 + excellence 0.0653.
Earned score 0.480 · Cap 0.699 · Final score 0.480
The final score is the lower of the earned score and the cap. Meeting a cap's conditions adds no points.
- working ledger: maximum 0.699
t_event_rows - current platform, complete surfaces: maximum 0.799
u_ledger_tablev_theme_tokensv_dark_mode - production robustness: maximum 0.799
t_out_of_orderr_paginationb_comment_exactly_onceu_llm_explainu_widget_liveu_ledger_sortk_llm_model_current
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.006/6 functions bundle, load and export their handler
l lint warnings
1.000 distinct lint warning(s): []
l real packages
1.006/6 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: ['scope-change', 'sprint-member']
k rovo mcp
1.00rovo:mcp 4/4:
k llm model current
0.00vacuous — precondition unmet: >= 1 LLM call
k manifest semantics
1.00deploy readiness, manifest + permissions: 17 rules checked, none failing here
k runtime risks
1.00deploy readiness, predicted runtime failures: 10 rules checked, none failing here
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.0041/41 deliveries handed off correctly
t event rows
0.00event rows: 0/24 exact (precision 0.00, recall 0.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.25permuted deliveries: 0/9 rows exact, 3/3 sprints with oracle numbers
t multi sprint parse
0.75worst of 3 scoring sites (seed ffc774ae855ece46): 18/24 multi-id Sprint changes recorded exactly
t reestimate followed
1.003/3 re-estimated sprints show the oracle numbers
t retry after honoured
1.00waited 30.1 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.0074/74 historical changes recorded exactly after the first scheduled run
r removals found
1.0010/10 removed-to-backlog changes found
r heal dropped
1.004/4 dropped changes healed exactly once; 0 other row(s) added
r pagination
0.23worst of 3 scoring sites (seed 2dc104cb782f01d3): 10/43 reads the site served in two or more pages walked to their end, each page once, continuing where the site left off (/rest/agile/1.0/board 1/1, /rest/agile/1.0/board
r rate limit
1.00backfill request 2: waited 2.1 virtual s in-invocation; backfill continuation page: waited 2.1 virtual s in-invocation; heal request 2: waited 2.1 virtual s in-invocation
r as app
1.0030/30 scheduled-run Jira calls asApp
r completes in timeout
1.003/3 scheduled invocations inside the module timeout
r idempotent rerun
1.000 entity write(s) on a no-change run over 102 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
1.0029/29 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.0035/35 invokes returned a defined, structured result; a Jira 500 on getLedger's read: handled
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.33worst of 3 scoring sites (seed 2dc104cb782f01d3): 2/6 comments are ADF as the viewer naming key, sprint and creep; ['PAY-354 status 201 via user', 'PAY-354 status 201 via user', 'PAY-294 status 201 via user']
b comment exactly once
0.00not exactly once: ['post@930: 1 comment(s), 0 success flag(s)', 'doubleClick@930: 1 comment(s), 0 success flag(s)', 'post@1038: 1 comment(s), 0 success flag(s)', 'doubleClick@1038: 1 comment(s), 0 success flag(s)']
b realtime payload clean
1.0016/16 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.75worst of 3 scoring sites (seed 2dc104cb782f01d3): widget numbers: 3.00/4 views exact (sprints by startDate, four §1 numbers each)
u widget chart
0.753/4 charts on one linear scale within 1px; ['worst bar off its linear scale by 6.54px']
u widget edit config
1.00edit/config 6/6:
u ledger table
0.61worst of 3 scoring sites (seed ffc774ae855ece46): ledger tables: 1.82/3 exact (rows, cells, default order)
u ledger sort
0.676/9 at-toggle states ordered with aria-sort (3 after another sort was active)
u issue router
0.000/3 issue keys open /browse/<KEY> through the Forge router
u comment flow
0.505/10 comment-flow steps right (select, success flag, forbidden error flag, modal works)
u modal close
1.003/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.00explain 0/5 over 5 scripted answers: 0:clean:one_llm_call_answered_clean, 1:digits:one_llm_call_answered_digits, 2:refusal:one_llm_call_answered_refusal, 3:malformed:one_llm_call_answered_malformed, 4:error:one_llm_call_
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.5910/17 surfaces themed with --ds-text* at >= 4.5:1; failing ['sprint-action-930-light-800x600', 'sprint-action-930-dark-800x600', 'sprint-action-1038-light-800x600', 'sprint-action-1038-dark-800x600']
v dark mode
0.7112/17 surfaces paint a --ds-surface* background in their mode; ['widget-view-129-dark-380x480: dominant [18, 18, 18]', 'widget-edit-129-dark: dominant [18, 18, 18]', 'widget-view-263-dark-380x480: dominant [18, 18, 18]']
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, 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
1.003/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 5/5: result fields named ['sprintName', 'committed', 'added', 'removed', 'creepPercent', 'hiddenChanges', 'changes']
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.00mean over 3 scoring sites: backfill 15 Jira calls / optimum 15 (incl. 2 forced 429 repeat(s)) = 1.00x
e event economy
0.00mean over 3 scoring sites: event rows inexact — economy is not credited on unfinished work
e ui round trips
1.00mean over 3 scoring sites: round trips before first paint: {'widget-view': 0, 'widget-edit': 1, 'sprint-action': 1}
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: e5c9e891fb12174571c2128bf170b44a90b3923ea95d4c218c8a57503227970c
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
- tencent/hy4-preview
- Engine events
- 0
- Repair rounds
- 0
- Started
- Oct 6, 2026, 04:51 PM
- Finished
- Oct 6, 2026, 05:37 PM