Skip to content

fix(ui): shorten native measurement precision - #7273

Merged
huangruiteng merged 1 commit into
mainfrom
codex/native-score-precision-20261025
Oct 24, 2026
Merged

huangruiteng merged 1 commit into
mainfrom
codex/native-score-precision-20261025

Conversation

@loopx-agent

@loopx-agent loopx-agent commented Oct 24, 2026 •

Copy link
Copy Markdown
Collaborator

Goal And Delivered Outcome

Native measurements displayed complete floating-point strings in the primary result, making scores difficult to scan. Format headline values to at most four decimal places, with up to four significant digits in scientific notation below 0.0001 or from 1,000,000. Existing measurement details retain the exact original values.

  • Outcome basis: reported excessive decimal precision in the Research view.
  • Before → after: a synthetic 0.8765432109876543 becomes 0.8765 in the headline; full precision stays in the existing source disclosure and evidence action. Tiny nonzero values remain nonzero, missing measurements remain unknown, and score selection/calculation uses the original native projection.
  • Intended base: main; baseline 984691c6ac54686d6747f4325564e68d81397f85.

Author Declaration

  • Written by: model_agent — OpenAI Codex.
  • Specification and revision: no separate written specification; the reported display defect and this PR's request are the basis. Presentation follows docs/development/design.md at the baseline above.
Criterion Disposition Path / symbol Validation
Short, readable native results and retained-improvement summaries implemented goal-research-progress.tsx, local formatNativeMeasurement Packaged decimal/tiny/large/signed/zero cases
Exact native values remain accessible without changing the owner data implemented Existing measurement sources and evidence actions Exact-value details/action assertions; source bytes unchanged and zero mutations
Preserve missing/invalid/partial results and narrow reading implemented Existing native-reading scenario Chinese/English, 1280px/390px and 200% text coverage
  • Self-check: inspected the complete two-file diff and the actual packaged default/expanded views. One local formatter serves the existing native result and retained-improvement readers; no new module, setting or scoring owner.

Scope And Continuation

Complete within this display scope. Changes are limited to the Research native-measurement reader and its existing browser regression. Backend projection, ranking, stored values and citation permissions remain unchanged. Merge and installation into a running App remain separate; this PR does not claim installed adoption.

Validation

  • Tested revision: 21e7c4b8378146f04e4e8f73288f9fceec828055 (same source bytes as the local build and browser checks).
  • Run state: finished.
  • Input classes: synthetic.
Check kind Result Evidence / limitation
static passed git diff --check; node --check examples/personal-workspace-browser/research-native-reading.mjs
integration passed npm run build:chat and npm run build:desktop in apps/presentation/dashboard; TypeScript checks and packaged builds pass
real_entrypoint passed LOOPX_PERSONAL_WORKSPACE_PACKAGED=1 LOOPX_PERSONAL_WORKSPACE_SCENARIO=research-native-reading node examples/personal-workspace-browser-smoke.mjs with the checkout's Python and Playwright dependencies
real_backend passed Existing disposable SQLite/HTTP research owner, native projection and source verifier; ten cases cover decimal/tiny/large values plus existing signed/zero/invalid/missing/partial roles
manual passed Ego Lite inspection of packaged UI with the real isolated HTTP owner at 1280px and 390px, before/after and expanded original-value details

Coverage: the browser regression verifies exact original values in details/actions, correct signed changes, unchanged source bytes, zero mutation attempts, both languages, keyboard evidence return and 200% text. Public images use independent synthetic values; the reported screenshot and live Goal data were not uploaded. Builds retain the existing non-blocking large-chunk warning. No model was dispatched; installed desktop activation is unverified.

Frontend / Visual Evidence

  • UI impact: changed.
  • Boundary: actual packaged Chat UI against a disposable real research backend with synthetic records. Before 984691c6; after 21e7c4b8. This is not an installed-App screenshot.
  • Journey: read the compact result immediately; optionally expand the existing measurement-source disclosure for exact precision. No new configuration or mandatory interaction.
  • Viewports/states: 1280px desktop and 390px narrow, default and expanded; unknown initial/retained values remain visible. The automated scenario also covers negative, zero, invalid, partial and empty results.
  • Source data: synthetic.
  • Attention/craft review: the native score now fits beside its unit; final/initial/retained readings remain together on narrow screens. Original precision moves into existing detail. Typography, hierarchy, help, source access and the main layout remain unchanged; no new cards, colors or motion.

Before — desktop

Before — desktop

After — desktop

After — desktop

Before — narrow

Before — narrow

After — narrow

After — narrow

After — original precision in expanded detail

After — original precision in expanded detail

Type of Change

  • Bug fix

LoopX Area

  • Public docs or presentation surface (Research UI)

Technical Direction

Research result readability; no change to benchmark evaluation or native measurement authority.

Shared-authority RFC fixture impact

N/A — no control-plane migration or shared-authority change.

Boundary Checklist

  • Diff, description and attachments contain public-safe synthetic content only; no private state, credentials, raw traces, internal links or local paths.
  • No maintainer-owned benchmark work duplicated.
  • Scope remains the reported precision defect.
  • No paired RFC changed.
  • Visual evidence included above.
  • Commit includes a DCO Signed-off-by trailer.

Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>

@loopx-agent loopx-agent left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewer: model_agent; model=gpt-6.1-sol; provider=OpenAI; reasoning_effort=max; declaration_source=runtime_reported; observation_id=23a04ec78b16bbedc99165a64bbd64958da29757ab4b99198bfb1ce25350843f

Approval conclusion (author-owned PR; GitHub blocks formal self-approval)

动机

研究者阅读固定窗口的原生测量时,会被长小数挤占主要结果区。 同一测量原来直接显示 0.8765432109876543;现在主读数为 0.8765,原始值仍在证据按钮与展开来源中。 已用真实 HTTP/SQLite owner 的打包页面验证 12 组数据、桌面与窄屏默认/展开视图,以及原文与焦点返回。 不改变测量、排序、采用或评分;不把可读性检查当作模型质量、已安装采用或因果收益证明。

改动思路

格式化属于已有显示投影;原生数值、角色与引用仍由同一个 typed owner 提供,当前局部 helper 足够,无需新设置或计算分支。 本PR只统一原生结果及增量的显示精度,并在现有来源详情补足原数值;不改原生投影、执行或持久状态。 原生结果的计算与采用仍由原owner判断;页面只缩短主读数,按需详情和证据按钮继续保留完整信息。把数值改写进存储或用隐藏精度换密度都会破坏任务,因此本次都没有这样做。

具体改动

完整审查2路径 +34/-6,准确提交 21e7c4b8378146f04e4e8f73288f9fceec828055,基线 984691c6ac54686d6747f4325564e68d81397f85。规格 docs/reference/trajectory-assessment.md 固定版本 984691c6ac54686d6747f4325564e68d81397f85;同时读取同版本设计系统的整页层级、按需来源与可读字号要求。映射标签是本次审查标签。NR-Roles implemented:Initial, best, final and provider-retained results remain distinct; missing or invalid is unknown, never zero. 验证:12-case actual packaged reading and citation tests。 NR-Precision implemented:Display is a read-only projection of source-bound native measurements and original evidence remains accessible. 验证:base/head decimal contrast; exact aria values; expanded values; source readback。 NR-NoAuthority implemented:Reading a captured result does not dispatch an experiment, replace native evaluation or establish causal attribution. 验证:real owner source_unchanged=true; mutation_attempts=0。

关键代码讲解

  • formatNativeMeasurement:统一显示精度。原始字符串/10位有效数改为4位小数或4位有效数科学记数;关键边界是 Tiny nonzero stays nonzero; negative zero normalizes to0; no input mutation。调用 Intl.NumberFormat 后交给 NativeResults and RetainedImprovement,失败/恢复由 Existing typed owner refuses invalid measurements 负责。

  • RetainedImprovement:显示原owner的已保留成果差值。增量、基线及最后候选差值统一格式,详情继续String原值;关键边界是 Unknown remains em dash/unknown; no invented baseline or retention。调用 formatNativeMeasurement and existing onCitation 后交给 adopted gain section and source details,失败/恢复由 No comparison -> no gain section; original unknown/historical warning 负责。

  • NativeResults:保留四类原生测量及证据。主读数格式化;展开来源补充完整值;原aria String不改;关键边界是 Best/final/retained roles and raw source binding unchanged。调用 same formatter and existing citation callback 后交给 Research reading and source panel,失败/恢复由 Absent/invalid points remain unknown, not clickable zero 负责。

原生计算、单位、排序、完整/部分窗口及证据事件没有改变。扩展已有真实后端浏览器用例覆盖十进制、小/大数;本次再检查负零和最小非零浮点值。12组读取全部通过,原文键盘打开、Escape返回原按钮、英文增量与帮助均通过。聊天与桌面构建通过;quick premerge 的4项直接检查、3项catalog与1项公开边界检查通过。

对主干的风险

主要反例是极小非零结果被显示为零,或者主读数缩短后原始精度无处可查。当前小于阈值的绝对值使用科学记数,5e-324仍显示5E-324;负零统一显示0,原生值本身未写回。原有未知、无效、空窗口与部分窗口没有被补零,最佳值也未冒充原生保留。桌面和390px展开来源的下部逐项检查,完整值、候选和时间仍可读;长单位在200%字号下换行,未出现横向溢出。

本次初次浏览器脚本把增量查在错误的区域,并用显式role CSS查隐式region及第一个隐藏tooltip,导致测试脚本失败;检查实际DOM后纠正了独立脚本,保留原失败记录,当前完整交互检查通过。这是reviewer选择器错误,未改产品代码或放宽产品断言。两个真实fixture owner最终均 source_unchanged=true、mutation_attempts=0。公开描述已有同提交桌面/窄屏前后和展开截图;没有将私有原始证据上传。

我的整体评价

APPROVE,本次限定的可读性结果已达成。long_horizon 为 preserved:没有据格式化宣称求解收益;user_experience 为 improved。桌面主读数和三个并列结果可同时阅读;窄屏展开仍显示完整数值、来源和限制,长单位在200%字号下换行且无横向溢出。 只验证当前源码打包页面与合成只读后端;正常已安装 App、真实研究者理解、模型采用与因果收益未验证。 原先长小数挤开并列结果,当前首屏可同时读主结果与首次/最后/保留;展开后仍能检查完整来源。一个局部formatter与现有详情即可闭合任务,额外设置或新组件没有必要,兼容评估为无协议/持久格式变化。

严格质量回执 cqr_e4465e74e02125307dc5 为 PASS;风险验证与公开边界检查通过。没有发现需阻断的当前变更问题。未查询或等待CI、未执行合并、安装或发布;评审结论不授予这些权限。后续若数字规则、原生投影、组件层级或提交改变,需要按新头重新检查。

English verdict: APPROVE — 21e7c4b8378146f04e4e8f73288f9fceec828055. The packaged reader shortens headline values while preserving exact source values, unknowns, roles and citation access. Twelve real HTTP-backed numeric cases, desktop/narrow visual checks, both builds and risk-based premerge passed. Installed adoption and model/causal benefits are unverified; no merge performed.

@huangruiteng
huangruiteng merged commit fac15a7 into main Oct 24, 2026
25 of 31 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants