Cloud baseline
z-ai/glm-5.3-prime, single model via OpenRouter — 0.4736 on Forge 1.0
z-ai/glm-5.3-prime · scorer forge-1.0
- Overall
- 0.4736
- Excellent
- no
- Benchmark
- Forge 1.0
- Model build
- 23m 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.8457 core + 0.12 × 0.86 gate × 0.73 excellence) × 0.6000 critical = 0.4921
Critical defects compound a multiplier on the whole score (pre-severity 0.8201):
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.7442 + excellence 0.0759.
Earned score 0.492 · Cap 0.499 · Final score 0.474
The final score is the lower of the earned score and the cap. Meeting a cap's conditions adds no points.
- deployable: maximum 0.499
l_deployable - current platform, complete surfaces: maximum 0.799
k_rovo_skillu_ledger_tablea_action_resultv_theme_tokens - production robustness: maximum 0.799
t_out_of_orderu_llm_explainu_widget_liveu_ledger_sortb_hidden_count
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
0.00lint: 19 error(s), stage SchemaValidator/26: ["app storage entities attributes property sprintId 'string' must be object", "app storage entities attributes property changeId 'string' must be object", "app storage entitie
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
0.29rovo:skill 2/7: source_dir_has_skill_md, name_equals_dir, description_50_1024, allowed_tools_has_action, allowed_tools_cover_dependencies
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']
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
0.93deploy readiness, manifest + permissions: 15 rules checked; failing (priced here): M7 KVS entity indexes name declared attributes within the documented limits [ledger-change.sprintId: 'string' is not a {type: …} mapping;
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.0047/47 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.75worst of 3 scoring sites (seed 84ad952355868f82): permuted deliveries: 9/9 rows exact, 0/3 sprints with oracle numbers
t multi sprint parse
1.0029/29 multi-id Sprint changes recorded exactly
t reestimate followed
0.00worst of 3 scoring sites (seed f36cee1a99ed4cce): 0/3 re-estimated sprints show the oracle numbers
t retry after honoured
1.00waited 30.3 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.0071/71 historical changes recorded exactly after the first scheduled run
r removals found
1.0011/11 removed-to-backlog changes found
r heal dropped
1.004/4 dropped changes healed exactly once; 0 other row(s) added
r pagination
1.00100/100 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/{id}/sprint 44/44, /rest/api/3/changelog/bulkfe
r rate limit
1.00backfill request 2: waited 2.3 virtual s in-invocation; backfill continuation page: waited 2.3 virtual s in-invocation; heal request 2: waited 2.3 virtual s in-invocation
r as app
1.0032/32 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 108 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.0028/28 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 ledger's read: handled
b no permission leak
1.00no hidden key, summary or change id reached a person
b hidden count
0.676/9 hidden counts equal the oracle
b comment adf as user
0.33worst of 3 scoring sites (seed f36cee1a99ed4cce): 2/6 comments are ADF as the viewer naming key, sprint and creep; ['API-218 status 201 via user', 'API-218 status 201 via user', 'OPS-413 status 201 via user']
b comment exactly once
1.006 click/double-click posts each ended with exactly one comment and one success flag (the 429-once fault included)
b realtime payload clean
1.0042/42 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.00worst of 3 scoring sites (seed f36cee1a99ed4cce): 0/4 charts on one linear scale within 1px; ['worst bar off its linear scale by 8.06px', 'worst bar off its linear scale by 6.56px']
u widget edit config
1.00edit/config 6/6:
u ledger table
0.94worst of 3 scoring sites (seed f36cee1a99ed4cce): ledger tables: 2.83/3 exact (rows, cells, default order)
u ledger sort
0.503/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.80worst of 3 scoring sites (seed f36cee1a99ed4cce): 8/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.83worst of 3 scoring sites (seed f36cee1a99ed4cce): explain 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
0.8815/17 surfaces themed with --ds-text* at >= 4.5:1; failing ['sprint-action-1247-light-800x600', 'sprint-action-1247-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, 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.00worst of 3 scoring sites (seed f36cee1a99ed4cce): 0/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
0.00vacuous — precondition unmet: SKILL.md exists
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.20mean over 3 scoring sites: 224 Jira calls / optimum 32 (31 delivered relevant change(s) x 1 read + 1 forced 429 repeat) = 7.00x; 1.0 at <= 1.46x
e ui round trips
1.00mean over 3 scoring sites: round trips before first paint: {'widget-view': 1, '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: a4ba382227955818339a76a13e5e7c1520a6b6e052118290804dd4aebe633651
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
- z-ai/glm-5.3-prime
- Engine events
- 0
- Repair rounds
- 0
- Started
- Oct 7, 2026, 02:43 AM
- Finished
- Oct 7, 2026, 04:28 AM