editaplot

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

EditaPlot

Turn a scientific question and a read-only table into an auditable, editable Origin figure. Keep the beginner experience conversational; use the deterministic engine for inspection, planning, rendering, exporting, and readback.

将科学问题和只读数据表转化为可审计、可编辑的Origin图形。保持面向初学者的对话式体验；使用确定性引擎完成检查、规划、渲染、导出和回读。

Request only scoped Windows permissions

仅请求范围明确的Windows权限

Read the complete repository, selected table, and optional local reference image.
Write only to the EditaPlot repository, the current user's Codex Skill directory, and the selected source file's parent folder for source-adjacent deliverables.
Run the local launcher, PowerShell/Python subprocesses, and an EditaPlot-owned Origin instance in the same active interactive Windows user session.
A normal Codex command may first run under an isolated account. If the Origin worker returns
```
origin_codex_sandbox_context
```
, submit a formal, narrowly scoped local-execution request for that exact
```
origin-smoke
```
or
```
render
```
command. Rerun it only if that exact request is approved, either by the user when prompted or by the configured Codex auto-reviewer. Approval is not guaranteed, and this handoff is not a sandbox bypass. Never ask the user to copy the command into a separate PowerShell window or broaden the request to administrator or system-configuration access.
Use network access only for repository download/update and locked dependency retrieval. Treat a user-scope winget Python installation as a separate system change that still requires explicit consent.
Do not request administrator rights, mouse control, whole-drive write access, cloud upload of private inputs, or DCOM, registry, firewall, user-group, or Origin-installation changes. When Controlled Folder Access, an organization policy, cloud sync, or a read-only location blocks writes, request access only to the affected folder or ask for an explicit alternate output folder.

读取完整仓库、选中的数据表，以及可选的本地参考图片。
仅向EditaPlot仓库、当前用户的Codex Skill目录，以及选中的源文件父文件夹写入与源文件相邻的交付物。
在同一个活动的交互式Windows用户会话中运行本地启动器、PowerShell/Python子进程，以及由EditaPlot管理的Origin实例。
普通的Codex命令可能首先在隔离账户下运行。如果Origin工作器返回
```
origin_codex_sandbox_context
```
，请针对确切的
```
origin-smoke
```
或
```
render
```
命令提交正式的、范围严格受限的本地执行请求。仅当该确切请求获得批准（用户在提示时确认，或配置的Codex自动审核器批准）后，才能重新运行。不保证一定能获得批准，且此交接并非绕过沙箱。切勿要求用户将命令复制到单独的PowerShell窗口中，也不要将请求范围扩大到管理员或系统配置访问权限。
仅在下载/更新仓库和获取锁定版本的依赖项时使用网络访问。将用户范围的winget Python安装视为独立的系统变更，仍需获得用户明确同意。
请勿请求管理员权限、鼠标控制、整盘写入权限、私有输入的云上传，或修改DCOM、注册表、防火墙、用户组、Origin安装。当受控文件夹访问、组织策略、云同步或只读位置阻止写入时，仅请求受影响文件夹的访问权限，或要求用户明确指定备用输出文件夹。

Start with the beginner path

从初学者路径开始

Reject unsupported platforms before installing anything. Support the CLI/dependency layer only on physical Windows 10/11 x64 with 64-bit CPython 3.10–3.12. Target Origin/OriginPro 2021 and later through external
```
originpro
```
; Origin 2020b and earlier are unsupported by this route. The fully verified live baseline is CPython 3.10 + Origin 2024b / 10.15. Treat another 2021+ version as capability-gated, not automatically verified, until its smoke and complete artifacts pass. State plainly that macOS (Intel/Apple Silicon), Linux, WSL, Wine/CrossOver, Parallels, and other VMs are unsupported in V1.
```
doctor
```
cannot reliably detect every VM, so ask the user to confirm a physical Windows host when that fact is unknown.
Locate
```
editaplot.cmd
```
in the installed Skill directory; when working from a cloned repository, use the repository-root
```
editaplot.cmd
```
. Use an absolute launcher path in commands. Do not make beginners select a Python executable or invoke
```
scripts/editaplot.py
```
directly.
Require the complete repository for first installation. Run repository-root
```
editaplot.cmd setup
```
; never instruct users to copy only
```
skill/editaplot
```
, because that omits the runtime. Read
```
references/runtime.md
```
for setup, discovery, and command details.
Reuse an existing compatible Python. If none exists, explain in Chinese that installing Python is a system-level change. Run
```
winget show
```
first and explain the exact publisher, source, and agreements. Only explicit user confirmation permits a later non-interactive installation of
```
Python.Python.3.12
```
with user scope and x64 architecture. If winget is unavailable, provide the official python.org Windows installation instructions and wait for the user; never use an untrusted mirror or silently install Python.
Run
```
editaplot.cmd doctor
```
for each new workflow. Allow
```
doctor --repair
```
only for the reported project-local Python dependency repair. Keep all Python packages in
```
.editaplot-venv
```
. Treat Origin as a locally installed user-managed application; never install or modify it during repair.
Run
```
editaplot.cmd start <data-file>
```
for a new table. Add
```
--intent "<user intent>"
```
when the user states a goal. Treat its inspection and recommendation payload as internal working state. Use the original local source path exposed by the attachment. If the host provides only a temporary copied attachment and the original folder cannot be recovered, ask once for the intended local source/output folder before rendering; never guess an unrelated workspace destination.
After selecting a candidate template, run
```
editaplot.cmd understand <data-file> --template-id <id>
```
with the same confirmed mapping that will be used for planning. Group its result into a short checklist: data type; columns to draw; columns used only for support or validation; columns retained but not drawn; proposed figure elements; and calculations that will not be performed. Every source column must appear exactly once. If any item is
```
uncertain
```
, ask for a corrected mapping and run
```
understand
```
again; do not confirm or plan it.
Tell a beginner only: what was recognized, the best one to three chart choices, why they fit, and the smallest scientific decision still required. Do not dump an
```
inspect → recommend → understand → plan
```
pipeline or raw JSON unless they ask for technical detail.
Ask the user to confirm both a one-sentence scientific purpose and the concise element checklist. Freeze the exact
```
proposal_hash
```
, approved derived-item IDs, and resolved ambiguity choices in
```
--semantic-confirmation-json
```
. Never reuse a confirmation after the source, mapping, purpose, or proposal hash changes. When confidence is low, candidate margins are small, roles or units are ambiguous, or a display transformation is proposed, ask only the additional focused questions needed.
If the user supplies a reference figure, first run
```
reference-inspect
```
. Codex may then describe only its panel/mark/encoding/layout/style grammar in the strict ReferenceFigureSpec JSON and run
```
reference-review
```
; the runtime performs no OCR or model inference. Show the adopted and rejected features, bind every essential mark to confirmed renderable user data, and obtain a separate hash-bound confirmation. Never copy reference values, labels, fits, phase assignments, author text, logos, watermarks, or the bitmap into the Origin project. Prefer verified
```
template_adaptation
```
; keep
```
controlled_composition
```
blocked until that exact composition has passed the full Origin evidence gate. A reference cannot add missing evidence or change the confirmed scientific element list. Treat style inferred from the reference as a suggestion, not as the user's instruction. Ask the user to choose one of three modes: keep the verified template default; use a confirmed, allow-listed approximation suggested by the reference; or provide exact custom values. For the exact mode, ask separately for colors, physical line width, fill transparency, page size, and legend visibility, frame, or position. An explicit user choice has precedence over a conflicting reference token. Freeze each reference suggestion as
```
applied
```
,
```
retained_template_default
```
, or
```
rejected
```
; never claim a request was applied unless the selected template has the same verified preview/Origin route and the required Origin object readback.
When color is user-selectable, run
```
editaplot.cmd palettes
```
, show
```
assets/palettes/palette-selector-public.zh-CN.png
```
, and recommend no more than two compatible
```
palette_id
```
values. Read
```
references/palettes.md
```
before freezing one.
Internally freeze the confirmed choice with
```
editaplot.cmd plan
```
; never hand-edit a plan or write a decision back to the source file. For an exact XPS request, write the confirmed values to a separate JSON object and pass its path with
```
--visual-style-json
```
. The supported exact fields are
```
series_colors
```
,
```
line_width_pt
```
,
```
fill_transparency_percent
```
,
```
page_size_cm
```
,
```
legend_visible
```
,
```
legend_position
```
, and
```
legend_frame
```
. Invalid explicit fields or values must fail fast and be corrected with the user; never silently discard them or fall back to a reference/default style. The render command copies this approved plan into the final output folder as
```
render-plan.json
```
.
Treat Origin readiness as technical state only. Doctor performs read-only discovery of
```
Origin.Application
```
,
```
Origin.ApplicationSI
```
, installed candidates, Python,
```
originpro
```
, and
```
OriginExt
```
; it never launches Origin and
```
ready_for_render
```
never means a live connection succeeded. If the default launch registration is present, proceed to the real pre-render smoke without asking the user to open Origin or confirm it again. Keep beginner output to one to three plain-language sentences; leave CLSIDs, registry views, candidates, and stages in JSON. Read the redacted
```
origin_execution_context
```
separately from
```
ready_for_render
```
. A
```
codex_sandbox
```
status requires the exact-command approval handoff above before COM is called; only an approved request may be rerun. Auto-review evaluates that individual request and does not pre-grant Origin access. An
```
unknown
```
Windows execution context is fail-closed and is not an approval request: stop before COM and report that the current Windows identity could not be verified.
Run
```
editaplot.cmd origin-smoke --output-dir <unique-smoke-directory>
```
with
```
launch_isolated
```
: start and own a dedicated Origin instance, perform the live smoke and version handshake, then apply the template capability decision. This command is mandatory after planning and before formal rendering.
```
attach_existing
```
is an explicit advanced mode only; never reset, overwrite, or close a user-owned project, and detach instead of exiting. Report failures by technical stage and next step without speculation. Never use mouse automation or provide application patches or bypass instructions. The runtime must attempt to clean a partial EditaPlot-owned activation and may try one fresh isolated instance for a retryable startup code only if cleanup succeeds. Cleanup failure returns
```
origin_activation_cleanup_failed
```
and stops. It must then wait with
```
sec -poc 30
```
and confirm
```
run.isOCready()
```
before reading the version or creating a project. Never loop, switch to
```
ApplicationSI
```
, edit DCOM/registry permissions, or tell a beginner to run the whole workflow as administrator. After the automatic attempt is exhausted, request approval for at most one retry in the same active Windows-user context and use a fresh empty sibling smoke directory so the first report remains intact.
```
origin_com_class_not_registered
```
and
```
origin_com_activation_access_denied
```
stop without automatic retry. Do not force-terminate a Python worker merely because it has run for a long time: it may own a hidden Origin instance. Preserve diagnostics and report the last progress stage before proposing any user-controlled cancellation. Keep the sandbox approval handoff distinct from an activation retry: the former happens before COM, while the latter is available only after the bounded activation/cleanup policy has run. When primary activation and cleanup both fail, expose only
```
primary_activation_code
```
,
```
primary_activation_stage
```
,
```
cleanup_error_code
```
, and
```
cleanup_error_stage
```
. Never include a Windows account name, local path, raw HRESULT, or raw COM text in that structured diagnostic payload, and never retry because both pairs are present. Current EditaPlot workers serialize only their active
```
origin-smoke
```
/
```
render
```
Origin section within one signed-in Windows session; data inspection, recommendation, and planning may remain concurrent. Respect
```
origin_job_queue
```
progress, which is emitted immediately when waiting and then about every 30 seconds. Ordering is not guaranteed to be strict FIFO. The 30-minute limit applies only to the waiting job: it stops that waiter without killing or interrupting the active holder. Do not submit a duplicate while a queue message is visible. Manual scripts, older EditaPlot releases, and unrelated programs are outside this coordination boundary.
Only after that smoke passes, render an allowed template route with
```
editaplot.cmd render <plan>
```
. Keep an EditaPlot-owned Origin instance open after success unless the user requests otherwise. By default, let the runtime create a direct sibling of the source file named
```
<source_stem>_EditaPlot_YYYYMMDD_HHMMSS
```
; keep all formal artifacts in that folder. Do not redirect ordinary runs to the repository, Skill directory, current working directory, or a shared global output folder. Use
```
--output-dir
```
only when the user explicitly requests another location.
Run
```
editaplot.cmd verify <output-directory>
```
against that source-adjacent folder and perform human visual QA. If smoke or render fails, a Python preview or standalone PNG/PDF/SVG is only a preview and must not be presented as completed Origin work. Formal success requires the editable OPJU, PNG, PDF, TIF, object readback, and human visual QA together.

Before any render, read

references/origin-safety.md

references/figure-contract.md

, and

references/verification.md

. For a new table or chart decision, read

references/data-contracts.md

references/chart-selection.md

, and

references/semantic-understanding.md

. When a reference image is supplied, also read

references/reference-figures.md

安装任何内容前先拒绝不支持的平台。仅在搭载64位CPython 3.10–3.12的物理机Windows 10/11 x64上支持CLI/依赖层。通过外部
```
originpro
```
库支持Origin/OriginPro 2021及更高版本；Origin 2020b及更早版本不支持此调用方式。完全验证的实时基准环境是CPython 3.10 + Origin 2024b / 10.15。其他2021+版本需通过能力门禁，不会自动视为已验证，直到其冒烟测试和完整产物通过验证。明确说明V1版本不支持macOS（Intel/Apple Silicon）、Linux、WSL、Wine/CrossOver、Parallels及其他虚拟机。
```
doctor
```
命令无法可靠检测所有虚拟机，因此当不确定主机类型时，需请用户确认是物理Windows主机。
在已安装的Skill目录中找到
```
editaplot.cmd
```
；如果是从克隆的仓库运行，使用仓库根目录的
```
editaplot.cmd
```
。命令中使用启动器的绝对路径。不要让初学者选择Python可执行文件或直接调用
```
scripts/editaplot.py
```
。
首次安装需要完整的仓库。运行仓库根目录的
```
editaplot.cmd setup
```
；切勿指导用户仅复制
```
skill/editaplot
```
，因为这样会遗漏运行时。有关设置、发现和命令的详细信息，请阅读
```
references/runtime.md
```
。
优先复用已有的兼容Python环境。如果没有，用中文说明安装Python属于系统级变更。先运行
```
winget show
```
，并说明确切的发布者、来源和协议。仅在用户明确确认后，才能后续以用户范围、x64架构非交互式安装
```
Python.Python.3.12
```
。如果winget不可用，提供python.org官方的Windows安装说明并等待用户操作；切勿使用不受信任的镜像或静默安装Python。
每个新工作流都要运行
```
editaplot.cmd doctor
```
。仅允许使用
```
doctor --repair
```
修复报告的项目本地Python依赖问题。所有Python包都保存在
```
.editaplot-venv
```
中。将Origin视为用户自行管理的本地安装应用；修复过程中切勿安装或修改Origin。
处理新数据表时运行
```
editaplot.cmd start <数据文件>
```
。如果用户说明了目标，添加
```
--intent "<用户意图>"
```
。将其检查和推荐的负载视为内部工作状态。使用附件暴露的原始本地源路径。如果主机仅提供临时复制的附件且无法恢复原始文件夹，在渲染前询问一次用户期望的本地源/输出文件夹；切勿猜测不相关的工作区目标路径。
选好候选模板后，使用与规划阶段相同的已确认映射运行
```
editaplot.cmd understand <数据文件> --template-id <id>
```
。将结果整理为简短的检查清单：数据类型；要绘制的列；仅用于支持或验证的列；保留但不绘制的列；拟议的图形元素；以及不会执行的计算。每个源列必须恰好出现一次。如果任何项为
```
uncertain
```
（不确定），请用户提供修正后的映射并重新运行
```
understand
```
；不要确认或规划该内容。
对初学者仅说明：识别到的内容、1-3个最佳图表选择、选择原因，以及仍需用户做出的最小范围科学决策。除非用户要求技术细节，否则不要抛出
```
inspect → recommend → understand → plan
```
的流水线或原始JSON。
请用户同时确认一句话的科学目的和简洁的元素检查清单。将确切的
```
proposal_hash
```
、已批准的派生项ID和已解决的歧义选择固化到
```
--semantic-confirmation-json
```
中。源数据、映射、目的或提案哈希发生变化后，切勿复用之前的确认。当置信度低、候选方案差异小、角色或单位不明确，或拟议进行显示变换时，仅询问必要的额外针对性问题。
如果用户提供了参考图，首先运行
```
reference-inspect
```
。之后Codex只能用严格的ReferenceFigureSpec JSON描述其面板/标记/编码/布局/样式语法，并运行
```
reference-review
```
；运行时不执行OCR或模型推理。展示已采纳和已拒绝的特性，将每个核心标记绑定到已确认的可渲染用户数据，并获得单独的哈希绑定确认。切勿将参考值、标签、拟合结果、相归属、作者文本、logo、水印或位图复制到Origin项目中。优先使用经过验证的
```
template_adaptation
```
；在确切的合成方案通过完整的Origin证据门禁之前，保持
```
controlled_composition
```
为禁用状态。参考图不能补充缺失的证据，也不能更改已确认的科学元素列表。将从参考图推断出的样式视为建议，而非用户指令。请用户从三种模式中选择一种：保留已验证模板的默认样式；使用参考图建议的、已确认的白名单近似样式；或提供确切的自定义值。对于精确模式，分别询问颜色、物理线宽、填充透明度、页面大小，以及图例的可见性、边框或位置。用户的明确选择优先于冲突的参考标记。将每个参考建议固化为
```
applied
```
（已应用）、
```
retained_template_default
```
（保留模板默认）或
```
rejected
```
（已拒绝）；切勿声称请求已应用，除非所选模板具有相同的已验证预览/Origin路径，并且完成了所需的Origin对象回读。
当颜色可由用户选择时，运行
```
editaplot.cmd palettes
```
，展示
```
assets/palettes/palette-selector-public.zh-CN.png
```
，并推荐不超过两个兼容的
```
palette_id
```
。固化配色方案前请阅读
```
references/palettes.md
```
。
使用
```
editaplot.cmd plan
```
在内部固化已确认的选择；切勿手动编辑方案，也不要将决策写回源文件。对于精确的XPS请求，将确认的值写入单独的JSON对象，并通过
```
--visual-style-json
```
传递其路径。支持的精确字段包括
```
series_colors
```
、
```
line_width_pt
```
、
```
fill_transparency_percent
```
、
```
page_size_cm
```
、
```
legend_visible
```
、
```
legend_position
```
和
```
legend_frame
```
。无效的显式字段或值必须快速失败，并与用户一起修正；切勿静默丢弃它们或回退到参考/默认样式。render命令会将此已批准的方案作为
```
render-plan.json
```
复制到最终输出文件夹中。
Origin就绪状态仅视为技术状态。Doctor命令对
```
Origin.Application
```
、
```
Origin.ApplicationSI
```
、已安装的候选版本、Python、
```
originpro
```
和
```
OriginExt
```
执行只读发现；它永远不会启动Origin，
```
ready_for_render
```
也绝不意味着实时连接成功。如果存在默认启动注册，直接进行真正的渲染前冒烟测试，无需要求用户打开Origin或再次确认。面向初学者的输出保持1-3句通俗易懂的话；将CLSID、注册表视图、候选版本和阶段信息保留在JSON中。单独读取经过脱敏的
```
origin_execution_context
```
和
```
ready_for_render
```
。状态为
```
codex_sandbox
```
时，需要先完成上述的确切命令批准交接，才能调用COM；仅已批准的请求可以重新运行。自动审核仅评估单个请求，不会预先授予Origin访问权限。Windows执行上下文为
```
unknown
```
时属于失败关闭状态，不属于批准请求：在调用COM前停止，并报告当前Windows身份无法验证。
使用
```
launch_isolated
```
模式运行
```
editaplot.cmd origin-smoke --output-dir <唯一冒烟测试目录>
```
：启动并管理一个专用的Origin实例，执行实时冒烟测试和版本握手，然后应用模板能力决策。此命令在规划之后、正式渲染之前是必须执行的。
```
attach_existing
```
仅为显式的高级模式；切勿重置、覆盖或关闭用户所有的项目，应采用分离而非退出的方式。按技术阶段和下一步措施报告失败原因，不要猜测。切勿使用鼠标自动化，也不要提供应用补丁或绕过说明。运行时必须尝试清理部分由EditaPlot管理的激活实例，且仅在清理成功后，才可针对可重试的启动代码尝试一个全新的隔离实例。清理失败会返回
```
origin_activation_cleanup_failed
```
并停止。之后必须使用
```
sec -poc 30
```
等待，并确认
```
run.isOCready()
```
，然后才能读取版本或创建项目。切勿循环、切换到
```
ApplicationSI
```
、编辑DCOM/注册表权限，或告诉初学者以管理员身份运行整个工作流。自动尝试用尽后，请求批准在同一个活动Windows用户上下文中最多重试一次，并使用全新的空同级冒烟测试目录，以保留第一次报告的完整性。
```
origin_com_class_not_registered
```
和
```
origin_com_activation_access_denied
```
错误会直接停止，不会自动重试。不要仅仅因为Python工作器运行时间长就强制终止它：它可能管理着一个隐藏的Origin实例。在建议用户主动取消之前，应保留诊断信息并报告最新的进度阶段。将沙箱批准交接与激活重试区分开：前者发生在COM调用之前，而后者仅在受限的激活/清理策略运行后才可用。当主激活和清理都失败时，仅暴露
```
primary_activation_code
```
、
```
primary_activation_stage
```
、
```
cleanup_error_code
```
和
```
cleanup_error_stage
```
。切勿在结构化诊断负载中包含Windows账户名、本地路径、原始HRESULT或原始COM文本，且由于两组错误都存在，切勿重试。当前的EditaPlot工作器在一个已登录的Windows会话中，仅对其活动的
```
origin-smoke
```
/
```
render
```
Origin部分进行串行化；数据检查、推荐和规划可以保持并发。遵守
```
origin_job_queue
```
进度，该进度在等待时立即发出，之后约每30秒发出一次。顺序不保证严格的FIFO。30分钟限制仅适用于等待的作业：它会停止等待者，但不会杀死或中断活动的持有者。在队列消息可见时，不要提交重复请求。手动脚本、旧版本的EditaPlot和不相关的程序不在此协调范围内。
仅当冒烟测试通过后，使用
```
editaplot.cmd render <方案>
```
渲染允许的模板路径。成功后保持EditaPlot管理的Origin实例处于打开状态，除非用户另有要求。默认情况下，运行时会在源文件的同级目录创建名为
```
<源文件主名>_EditaPlot_YYYYMMDD_HHMMSS
```
的文件夹；所有正式产物都保存在该文件夹中。不要将普通运行重定向到仓库、Skill目录、当前工作目录或共享的全局输出文件夹。仅当用户明确要求其他位置时，才使用
```
--output-dir
```
。
对该源文件同级文件夹运行
```
editaplot.cmd verify <输出目录>
```
，并执行人工视觉质量检查。如果冒烟测试或渲染失败，Python预览或独立的PNG/PDF/SVG仅为预览，绝不能作为已完成的Origin作品展示。正式成功需要同时具备可编辑的OPJU、PNG、PDF、TIF、对象回读和人工视觉质量检查。

在任何渲染之前，请阅读

references/origin-safety.md

、

references/figure-contract.md

和

references/verification.md

。对于新的数据表或图表决策，请阅读

references/data-contracts.md

、

references/chart-selection.md

和

references/semantic-understanding.md

。如果提供了参考图片，还需阅读

references/reference-figures.md

。

Keep scientific decisions with the user

科学决策由用户把控

Treat the original data file as immutable. Never overwrite it, fill missing source columns, or invent measurements. Permit helper columns only in memory or the editable Origin project.
Classify every source column before planning as primary render, secondary render, support-only, retain-not-render, or uncertain. Support-only and retained columns cannot become visible through a reference image. An unknown numeric column is a question, not another automatic curve.
Distinguish scientific analysis from display transformation. Never silently normalize, smooth, fit, remove outliers, calculate error bars, identify phases, or infer material peaks.
For GSAS/GSAS-II Rietveld data, distinguish Observed, Calculated, optional Background, supplied Difference, explicit Phase positions, and non-rendering control/diagnostic columns. Preserve an upstream Publication
```
Diff
```
exactly; never apply a second display offset.
For XPS, keep cosmetic preferences separate from the scientific contract. A user may explicitly request exact series colors, physical line widths, fill transparency, a safe page/aspect ratio, and legend show/hide, borderless, or position choices. Apply only fields supported and read back by the selected verified XPS renderer; otherwise retain the default or reject the field visibly. Neither a user style request nor a reference image may change source values or column roles, the high-to-low binding-energy axis contract, component identity, residual disposition, or the verified single-region
```
set_fill_area(..., type=9)
```
/
```
-pfm 3
```
fill implementation.
For SHAP, accept only externally precomputed per-sample contributions. Never train a model or invoke SHAP. Mean |SHAP| and optional group percentages may only summarize those supplied rows with the allow-listed formulas recorded in the semantic proposal and explicitly approved; never invent contributions or silently reorder features.
Confirm unknown units, error semantics, percentage denominators, meaningful order, dual axes, and any other choice that can change the claim.
Recommend from the scientific question and data structure, not aesthetics alone. Refuse a misleading chart even when technically renderable.
Keep template route status (
```
verified
```
,
```
experimental
```
, or
```
unsupported
```
) separate from current host compatibility (
```
verified
```
,
```
compatible_unverified
```
, or
```
blocked
```
). Never relabel a
```
compatible_unverified
```
Origin version as verified; continue only when its smoke succeeds and the selected template's required capabilities are available.
Reject decorative 3D. Require a scientifically meaningful third axis; keep a new 3D route experimental until Z-axis, camera, OpenGL type, source mapping, four exports, editable OPJU, readback, and visual QA pass.
对于已验证的
```
density_ridgeline3d
```
，我只接受 2–6 个真实带单位条件的 mixed-wide 六角色表：上游提供同语义同单位的实线/虚线预计算密度，并为每组提供恰好一个
```
Focal X
```
。焦点固定为 Z=0 基线 locator；不要计算 KDE、峰值、阈值、交点或焦点。当前主机还必须先通过实时 smoke 与
```
OPEN_GL_3D
```
能力检查，不能只凭模板已验证就跳过主机门禁。
Do not send selected files to any additional network service or include them in public artifacts. A file explicitly provided through Codex remains subject to the user's Codex account, organization, and retention policies; do not claim the Skill can override those policies.
Before inspecting medical data or reference images, require the user to confirm that the material follows their institution's rules, is deidentified, and has been checked for burned-in text.
Treat
```
panel-plan
```
as a deidentification-aware layout and evidence gate, not an OCR, PHI detector, medical image editor, or merged editable Origin project. Preserve every verified subproject.

原始数据文件视为不可变。切勿覆盖它、填充缺失的源列或编造测量值。仅允许在内存中或可编辑的Origin项目中使用辅助列。
规划前将每个源列分类为：主渲染列、次渲染列、仅支持列、保留不渲染列或不确定列。仅支持列和保留列不能通过参考图变为可见。未知的数值列是一个待确认的问题，而非另一条自动曲线。
区分科学分析与显示变换。切勿静默执行归一化、平滑、拟合、离群值移除、误差棒计算、相识别或材料峰推断。
对于GSAS/GSAS-II Rietveld数据，区分观测值、计算值、可选背景、提供的差值、明确的相位置，以及不渲染的控制/诊断列。严格保留上游Publication的
```
Diff
```
；切勿应用二次显示偏移。
对于XPS，将外观偏好与科学约定分开。用户可以明确请求精确的系列颜色、物理线宽、填充透明度、安全的页面/宽高比，以及图例的显示/隐藏、无边框或位置选择。仅应用所选已验证XPS渲染器支持并可回读的字段；否则保留默认值或明确拒绝该字段。用户的样式请求或参考图都不能更改源值或列角色、结合能轴从高到低的约定、组分身份、残差处理，或已验证的单区域
```
set_fill_area(..., type=9)
```
/
```
-pfm 3
```
填充实现。
对于SHAP，仅接受外部预先计算的每个样本的贡献值。切勿训练模型或调用SHAP。平均|SHAP|和可选的组百分比只能使用语义提案中记录的、已明确批准的白名单公式来汇总提供的行；切勿编造贡献值或静默重排特征。
确认未知的单位、误差语义、百分比分母、有意义的顺序、双轴，以及任何其他可能改变结论的选择。
基于科学问题和数据结构进行推荐，而非仅考虑美观。即使技术上可以渲染，也要拒绝具有误导性的图表。
将模板路径状态（
```
verified
```
（已验证）、
```
experimental
```
（实验性）或
```
unsupported
```
（不支持））与当前主机兼容性（
```
verified
```
（已验证）、
```
compatible_unverified
```
（兼容但未验证）或
```
blocked
```
（受阻））分开。切勿将
```
compatible_unverified
```
的Origin版本重新标记为已验证；仅当其冒烟测试通过且所选模板的所需能力可用时，才能继续。
拒绝装饰性3D。要求具有科学意义的第三轴；新的3D路径保持实验性，直到Z轴、相机、OpenGL类型、源映射、四种导出格式、可编辑OPJU、回读和视觉质量检查全部通过。
对于已验证的
```
density_ridgeline3d
```
，我只接受 2–6 个真实带单位条件的 mixed-wide 六角色表：上游提供同语义同单位的实线/虚线预计算密度，并为每组提供恰好一个
```
Focal X
```
。焦点固定为 Z=0 基线 locator；不要计算 KDE、峰值、阈值、交点或焦点。当前主机还必须先通过实时 smoke 与
```
OPEN_GL_3D
```
能力检查，不能只凭模板已验证就跳过主机门禁。
不要将选中的文件发送到任何额外的网络服务，也不要将其包含在公共产物中。通过Codex明确提供的文件仍受用户的Codex账户、组织和保留政策约束；不要声称该Skill可以覆盖这些政策。
在检查医学数据或参考图片之前，要求用户确认材料符合其所在机构的规定、已去标识化，并且已检查是否有嵌入文本。
将
```
panel-plan
```
视为支持去标识化的布局和证据门禁，而非OCR、PHI检测器、医学图像编辑器或合并的可编辑Origin项目。保留每个已验证的子项目。

Apply the publication-informed contract

遵循符合发表规范的约定

Make every chart defend one explicit conclusion or evidence role.
Use a white background, Arial, restrained color families, clear hierarchy, and no rainbow palette, decorative 3D, or unjustified grid.
Derive physical Origin dimensions from chart type, data density, series count, and label length. Keep fixed size only for a profile that explicitly requires it, such as legacy fixed C 1s.
Convert documented point, line-width, and page-size units correctly. Never copy small journal-page font values directly into Origin API fields; read back the resulting axis and text objects.
Keep each condition's color consistent across related panels. Freeze palette IDs and exact HEX values, allowed modes, safe category count, and accessibility constraints into the plan.
Let an explicit user style request outrank a style token inferred from a reference image. Color, line-width, transparency, page/aspect, and legend requests are still capability-gated and must be classified as applied, retained default, or rejected before rendering.
Do not let a reference image or unverified cosmetic preference silently redefine semantic color mappings for XPS components, signed effects, heatmaps, diagnostic lines, confusion matrices, or similar evidence. An explicit replacement is allowed only through that route's independently verified override with exact series mapping and readback.
Give every medical panel one distinct evidence role. Freeze a shared condition-to-color map before composing quantitative panels; require explicit semantic confirmation for a shared legend.
Prefer editable labels and Origin objects. A Python preview or embedded bitmap is not an Origin deliverable.
Call the result “publication-informed,” never “Nature compliant” or journal-approved.

每张图表都应支撑一个明确的结论或证据角色。
使用白色背景、Arial字体、克制的配色系列、清晰的层级，不使用彩虹配色、装饰性3D或无依据的网格。
根据图表类型、数据密度、系列数量和标签长度推导Origin的物理尺寸。仅对明确要求固定尺寸的配置文件（如传统的固定C 1s）使用固定尺寸。
正确转换文档中的磅、线宽和页面大小单位。切勿将期刊页面的小字体值直接复制到Origin API字段中；应回读生成的轴和文本对象。
在相关面板中保持每个条件的颜色一致。将配色ID和确切的HEX值、允许的模式、安全的类别数量和可访问性约束固化到方案中。
用户明确的样式请求优先于从参考图推断出的样式标记。颜色、线宽、透明度、页面/宽高比和图例请求仍需通过能力门禁，并且必须在渲染前分类为已应用、保留默认或已拒绝。
不要让参考图或未经验证的外观偏好静默重新定义XPS组分、带符号效应、热图、诊断线、混淆矩阵或类似证据的语义颜色映射。仅通过该路径独立验证的、具有确切系列映射和回读的覆盖机制，才允许显式替换。
为每个医学面板分配一个明确的证据角色。在组合定量面板之前固化共享的条件-颜色映射；共享图例需要明确的语义确认。
优先使用可编辑的标签和Origin对象。Python预览或嵌入的位图不属于Origin交付物。
将结果称为“符合发表规范的”，绝不要称为“符合Nature标准”或“期刊认可的”。

Report the result in plain language

用通俗易懂的语言报告结果

Return the recognized data shape and roles, selected chart and alternatives, confidence and confirmed transformations, source-adjacent output folder, copied plan, OPJU/PNG/PDF/TIF paths, validation/readback paths, and any remaining human check. For a beginner, translate internal identifiers into natural language, summarize environment state in one to three sentences, and put technical paths after the concise outcome.

返回识别到的数据形状和角色、所选图表和备选方案、置信度和已确认的变换、源文件同级输出文件夹、复制的方案、OPJU/PNG/PDF/TIF路径、验证/回读路径，以及任何剩余的人工检查项。对于初学者，将内部标识符转换为自然语言，用1-3句话总结环境状态，并将技术路径放在简洁的结果之后。

Load detailed references only as needed

仅按需加载详细参考文档

```
references/runtime.md
```
: launcher, setup, Python discovery, CLI commands, and artifacts.
```
references/chart-selection.md
```
: chart families, ranking rules, and support levels.
```
references/data-contracts.md
```
: accepted layouts, column semantics, and repair guidance.
```
references/semantic-understanding.md
```
: per-column use, element checklist, derived-data lineage, and the hash-bound confirmation gate.
```
references/reference-figures.md
```
: safe reference grammar, bindings, adaptation limits, and separate confirmation.
```
references/figure-contract.md
```
: evidence logic, visual hierarchy, typography, and color rules.
```
references/origin-safety.md
```
: local Automation and verified-API guardrails.
```
references/verification.md
```
: mandatory artifacts, readback, and visual QA.
```
references/showcase.md
```
: neutral demonstration data and gallery policy.
```
references/palettes.md
```
: Chinese palette selector, compatibility, and accessibility limits.

```
references/runtime.md
```
：启动器、设置、Python发现、CLI命令和产物。
```
references/chart-selection.md
```
：图表系列、排名规则和支持级别。
```
references/data-contracts.md
```
：支持的布局、列语义和修复指南。
```
references/semantic-understanding.md
```
：逐列用途、元素检查清单、派生数据血缘，以及哈希绑定确认门禁。
```
references/reference-figures.md
```
：安全参考语法、绑定、适配限制和单独确认。
```
references/figure-contract.md
```
：证据逻辑、视觉层级、排版和颜色规则。
```
references/origin-safety.md
```
：本地自动化和已验证API的防护措施。
```
references/verification.md
```
：必选产物、回读和视觉质量检查。
```
references/showcase.md
```
：中性演示数据和图库政策。
```
references/palettes.md
```
：中文配色选择器、兼容性和可访问性限制。