superlab 0.1.77 → 0.1.79

package/lib/lab_write_contract.json

@@ -1,5 +1,5 @@
 {
-  "chinese_terminology_rule": "Chinese workflow-language terminology: when `workflow_language=zh`, concept terms should use a Chinese paper-facing name and a Chinese short form by default. English full form plus acronym may appear at first mention only as `中文全称（English full form, ACRONYM）`, then prose should reuse the Chinese short form. Prefer natural compact Chinese short forms; two-character, three-character, four-character, or longer short phrases are all acceptable when they read naturally. Do not force a fixed-length abbreviation. Avoid repeating English concept fragments throughout Chinese prose. Run `validate_workflow_language_text.py` on touched Chinese workflow-language sections, tables, figures, and analysis assets before completing the write round.",
+  "chinese_terminology_rule": "Chinese workflow-language terminology: when `workflow_language=zh`, concept terms should use a Chinese paper-facing name and a Chinese short form by default. English full form plus acronym may appear at first mention only as `中文全称（English full form, ACRONYM）`, then prose should reuse the Chinese short form. Prefer natural compact Chinese short forms; two-character, three-character, four-character, or longer short phrases are all acceptable when they read naturally. Do not force a fixed-length abbreviation. Avoid repeating English concept fragments throughout Chinese prose. Before completing the write round, run `validate_paper_layer.py` on the resolved active Chinese paper layer so the whole layer is checked rather than only the touched file. Use `validate_workflow_language_text.py` as a local repair helper when narrowing down specific offending files.",
   "stage_prompt": {
     "codex_en": "This command runs the `/lab:write` stage. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Carry the same core insight anchor through the paper: Introduction creates the cognitive contrast, Method turns the insight into design motivation, Experiments diagnose it with evidence, and Conclusion states the broader principle and boundary. Do not create a standalone `Our Insights` section just to satisfy this; weave the insight into motivation, mechanism, evidence, and limitations. Read the matching paper-writing reference, the current section block in `section-style-policies.md`, and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. When `workflow_language` and `paper_language` differ, treat the workflow-language paper layer as the default ordinary working layer. Resolve the active paper topology from `.lab/config/workflow.json` before drafting: the active canonical root is `<deliverables_root>/paper/`, and when workflow-language is active its root is `<deliverables_root>/paper/workflow-language/`. Ordinary write rounds should still edit one target paper layer at a time rather than silently refreshing both language layers. If the user names a concrete file or layer, treat that as the only target for the round unless they also explicitly request synchronization. Classify the named target path before editing it. Only active-layer targets count as managed manuscript rounds; legacy side layers such as `review_zh`, `translation_zh`, `sections_zh`, or stale `deliverables/.../workflow-language/*.md` paths are out-of-band/legacy edits and must not silently replace the active paper topology. If a workflow-language paper layer is active and the round still targets the canonical manuscript, record why canonical-only writing was acceptable in the write iteration artifact. If `paper_language_finalization_decision=convert-to-paper-language`, explicit canonical-manuscript work may target the canonical `paper_language` manuscript, but that does not make canonical the default ordinary working layer while workflow-language remains active. Treat the workflow-language paper layer as a real persisted artifact rather than a review layer, and preserve it as a full LaTeX mirror with `workflow-language/main.tex`, `workflow-language/references.bib`, `workflow-language/sections/*.tex`, `workflow-language/tables/*.tex`, `workflow-language/figures/*.tex`, and `workflow-language/analysis/analysis-asset.tex`. Do not write new workflow-language output to deprecated review-layer paths such as `docs/lab/paper/review_zh/`. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, do not use labels containing `_` or `-` in reader-facing prose, apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels, do not assume a fixed drafting order such as Method before Experiments, add a local naming bridge when a section uses canonical short names before their defining section has been drafted, and reuse the canonical label instead of replacing it with a narrative alias. Follow the current section's encouraged, discouraged, and banned expression lists from `section-style-policies.md`; section-specific banned expressions take priority over prose-polish goals. Before any additional tighten, compress, or polish pass on the same section, run a section-level acceptance gate first. That gate must explicitly confirm naming consistency, adjacent-section consistency, claim, metric, and ranking consistency with the current evidence, local clarity, local concision, and section-style compliance. If the round changes the paper's canonical experiment or evaluation protocol, treat that change as a canonical replacement unless the user explicitly scoped it as supplementary or appendix-only, run a paper-wide impact audit before more polishing, update the highest-impact stale sections and assets first, and do not default to translation/workflow-layer sync work unless the user explicitly asked for it or the language-finalization workflow requires it. Only edit both the canonical manuscript and the workflow-language paper layer in the same round when the user explicitly asks for cross-language synchronization or when a final-draft/export language-finalization step requires both layers to be refreshed together. Do not treat a routine tighten/compress/polish request as an instruction to sync the workflow-language companion. For export or remote-publication rounds, if `paper_language_finalization_decision=convert-to-paper-language`, include the workflow-language paper layer in the exported or pushed bundle by default. Allow canonical-only export or remote publication only when the user explicitly asked for it or when the remote target forbids extra files. If any gate item is unresolved, or if a banned expression or move from the current section policy remains, spend the round fixing that blocker instead of polishing sentences further, and do not default the next-step recommendation to another polish pass. Main tables must be locally self-contained: the title, header, note, and adjacent prose should tell the reader what each row and column means, the metric direction, and any relevant unit, denominator, or event condition. Short headers remain allowed, but abbreviations in paper-facing tables must be expanded locally in the same table. If Method or Experiments prose promises a metric family, the main table set must either expose those metrics directly or explicitly mark the missing ones as appendix-only and explain why. If a metric is measured but omitted because it is zero everywhere, redundant, or appendix-only, state that disposition explicitly in the table note instead of silently dropping it. Do not treat `\\resizebox{\\linewidth}{!}{...}` as the default way to fit a main table. Fit main tables by redesign first: shorten headers, move secondary metrics out of the main table, reduce or split columns, then adjust `\\tabcolsep` conservatively; only use `\\resizebox` as a last resort, keep width changes readable, and explain the width-control rationale locally in the same table note. Do not use `\\scriptsize` or `\\tiny` as the default main-table fit strategy. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check, the section-level acceptance gate, section-style policy compliance, the protocol/scope impact audit, the export or remote bundle audit, the round target layer, any canonical-only justification while workflow-language was active, any cross-language sync justification, the active canonical/workflow-language roots, the resolved target path role, any out-of-band justification, the insight integration audit, and the table-semantics audit in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language paper-layer path in the latest write iteration, and only then edit the final manuscript in the chosen language.",
     "claude_en": "This command runs the `write` stage of the lab workflow. Use `.claude/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference, the current section block in `section-style-policies.md`, and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. When `workflow_language` and `paper_language` differ, treat the workflow-language paper layer as the default ordinary working layer. Ordinary write rounds should still edit one target paper layer at a time rather than silently refreshing both language layers. If the user names a concrete file or layer, treat that as the only target for the round unless they also explicitly request synchronization. If a workflow-language paper layer is active and the round still targets the canonical manuscript, record why canonical-only writing was acceptable in the write iteration artifact. If `paper_language_finalization_decision=convert-to-paper-language`, explicit canonical-manuscript work may target the canonical `paper_language` manuscript, but that does not make canonical the default ordinary working layer while workflow-language remains active. Treat the workflow-language paper layer as a real persisted artifact rather than a review layer, and preserve it as a full LaTeX mirror with `workflow-language/main.tex`, `workflow-language/references.bib`, `workflow-language/sections/*.tex`, `workflow-language/tables/*.tex`, `workflow-language/figures/*.tex`, and `workflow-language/analysis/analysis-asset.tex`. Do not write new workflow-language output to deprecated review-layer paths such as `docs/lab/paper/review_zh/`. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, do not use labels containing `_` or `-` in reader-facing prose, apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels, do not assume a fixed drafting order such as Method before Experiments, add a local naming bridge when a section uses canonical short names before their defining section has been drafted, and reuse the canonical label instead of replacing it with a narrative alias. Follow the current section's encouraged, discouraged, and banned expression lists from `section-style-policies.md`; section-specific banned expressions take priority over prose-polish goals. Before any additional tighten, compress, or polish pass on the same section, run a section-level acceptance gate first. That gate must explicitly confirm naming consistency, adjacent-section consistency, claim, metric, and ranking consistency with the current evidence, local clarity, local concision, and section-style compliance. If the round changes the paper's canonical experiment or evaluation protocol, treat that change as a canonical replacement unless the user explicitly scoped it as supplementary or appendix-only, run a paper-wide impact audit before more polishing, update the highest-impact stale sections and assets first, and do not default to translation/workflow-layer sync work unless the user explicitly asked for it or the language-finalization workflow requires it. Only edit both the canonical manuscript and the workflow-language paper layer in the same round when the user explicitly asks for cross-language synchronization or when a final-draft/export language-finalization step requires both layers to be refreshed together. Do not treat a routine tighten/compress/polish request as an instruction to sync the workflow-language companion. For export or remote-publication rounds, if `paper_language_finalization_decision=convert-to-paper-language`, include the workflow-language paper layer in the exported or pushed bundle by default. Allow canonical-only export or remote publication only when the user explicitly asked for it or when the remote target forbids extra files. If any gate item is unresolved, or if a banned expression or move from the current section policy remains, spend the round fixing that blocker instead of polishing sentences further, and do not default the next-step recommendation to another polish pass. Main tables must be locally self-contained: the title, header, note, and adjacent prose should tell the reader what each row and column means, the metric direction, and any relevant unit, denominator, or event condition. Short headers remain allowed, but abbreviations in paper-facing tables must be expanded locally in the same table. If Method or Experiments prose promises a metric family, the main table set must either expose those metrics directly or explicitly mark the missing ones as appendix-only and explain why. If a metric is measured but omitted because it is zero everywhere, redundant, or appendix-only, state that disposition explicitly in the table note instead of silently dropping it. Do not treat `\\resizebox{\\linewidth}{!}{...}` as the default way to fit a main table. Fit main tables by redesign first: shorten headers, move secondary metrics out of the main table, reduce or split columns, then adjust `\\tabcolsep` conservatively; only use `\\resizebox` as a last resort, keep width changes readable, and explain the width-control rationale locally in the same table note. Do not use `\\scriptsize` or `\\tiny` as the default main-table fit strategy. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check, the section-level acceptance gate, section-style policy compliance, the protocol/scope impact audit, the export or remote bundle audit, the round target layer, any canonical-only justification while workflow-language was active, any cross-language sync justification, and the table-semantics audit in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language paper-layer path in the latest write iteration, and only then edit the final manuscript in the chosen language.",

package/package-assets/claude/commands/lab/write.md

@@ -10,6 +10,6 @@ Execute the requested `/lab-write` command against the user's argument now. Do n
 When the user provides reference PDFs, paper URLs, local reference-paper paths, or asks to write by reference, stay within the write stage and switch to reference-guided deep-write. Extract structure, map section/subsection slots, paragraph roles, table/figure roles, and bridge logic to the current paper, record the consumption plan, and only then draft prose. The current section must visibly realize the mapped slots; do not treat a consumption plan as enough. Reuse structure only; do not copy wording, claims, metrics, captions, or conclusions. Keep service-style or AI-assistant meta language and workflow-only placeholder language out of paper-facing prose.
 When Method, Experiments, captions, tables, or analysis assets introduce or revise reported metrics, create or update `.lab/writing/metric-glossary.md` before prose polish. Each metric must define its paper-facing name, approved short name, table/header label, plain-language definition, calculation, unit or denominator, direction, scope or conditions, allowed aliases, forbidden aliases, and first-use location. Use the same metric names across prose, captions, table notes, table headers, and result summaries. Run `validate_metric_glossary.py` and remove forbidden aliases from reader-facing LaTeX before finalizing the round.
 Carry the same core insight anchor through the paper: Introduction creates the cognitive contrast, Method turns the insight into design motivation, Experiments diagnose it with evidence, and Conclusion states the broader principle and boundary. Do not create a standalone `Our Insights` section just to satisfy this; weave the insight into motivation, mechanism, evidence, and limitations.
-Chinese workflow-language terminology: when `workflow_language=zh`, concept terms should use a Chinese paper-facing name and a Chinese short form by default. English full form plus acronym may appear at first mention only as `中文全称（English full form, ACRONYM）`, then prose should reuse the Chinese short form. Prefer natural compact Chinese short forms; two-character, three-character, four-character, or longer short phrases are all acceptable when they read naturally. Do not force a fixed-length abbreviation. Avoid repeating English concept fragments throughout Chinese prose. Run `validate_workflow_language_text.py` on touched Chinese workflow-language sections, tables, figures, and analysis assets before completing the write round.
-For Chinese workflow-language output, run `validate_workflow_language_text.py` over the touched workflow-language sections, tables, figures, and analysis assets before completing the write round. If it reports English concept fragments, translate them or define a justified glossary exception before prose polish.
+Chinese workflow-language terminology: when `workflow_language=zh`, concept terms should use a Chinese paper-facing name and a Chinese short form by default. English full form plus acronym may appear at first mention only as `中文全称（English full form, ACRONYM）`, then prose should reuse the Chinese short form. Prefer natural compact Chinese short forms; two-character, three-character, four-character, or longer short phrases are all acceptable when they read naturally. Do not force a fixed-length abbreviation. Avoid repeating English concept fragments throughout Chinese prose. Before completing the write round, run `validate_paper_layer.py` on the resolved active Chinese paper layer so the whole layer is checked rather than only the touched file. Use `validate_workflow_language_text.py` as a local repair helper when narrowing down specific offending files.
+For Chinese workflow-language output, run `validate_paper_layer.py` on the resolved active paper layer before completing the write round so the whole layer is checked instead of only the touched file. Use `validate_workflow_language_text.py` as a local repair helper when narrowing down specific offending files. If the layer validator reports English concept fragments or English paper-facing headings/captions, translate them or define a justified glossary exception before prose polish.
 This command runs the `write` stage of the lab workflow. Use `.claude/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference, the current section block in `section-style-policies.md`, and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. When `workflow_language` and `paper_language` differ, treat the workflow-language paper layer as the default ordinary working layer. Ordinary write rounds should still edit one target paper layer at a time rather than silently refreshing both language layers. If the user names a concrete file or layer, treat that as the only target for the round unless they also explicitly request synchronization. If a workflow-language paper layer is active and the round still targets the canonical manuscript, record why canonical-only writing was acceptable in the write iteration artifact. If `paper_language_finalization_decision=convert-to-paper-language`, explicit canonical-manuscript work may target the canonical `paper_language` manuscript, but that does not make canonical the default ordinary working layer while workflow-language remains active. Treat the workflow-language paper layer as a real persisted artifact rather than a review layer, and preserve it as a full LaTeX mirror with `workflow-language/main.tex`, `workflow-language/references.bib`, `workflow-language/sections/*.tex`, `workflow-language/tables/*.tex`, `workflow-language/figures/*.tex`, and `workflow-language/analysis/analysis-asset.tex`. Do not write new workflow-language output to deprecated review-layer paths such as `docs/lab/paper/review_zh/`. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, do not use labels containing `_` or `-` in reader-facing prose, apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels, do not assume a fixed drafting order such as Method before Experiments, add a local naming bridge when a section uses canonical short names before their defining section has been drafted, and reuse the canonical label instead of replacing it with a narrative alias. Follow the current section's encouraged, discouraged, and banned expression lists from `section-style-policies.md`; section-specific banned expressions take priority over prose-polish goals. Before any additional tighten, compress, or polish pass on the same section, run a section-level acceptance gate first. That gate must explicitly confirm naming consistency, adjacent-section consistency, claim, metric, and ranking consistency with the current evidence, local clarity, local concision, and section-style compliance. If the round changes the paper's canonical experiment or evaluation protocol, treat that change as a canonical replacement unless the user explicitly scoped it as supplementary or appendix-only, run a paper-wide impact audit before more polishing, update the highest-impact stale sections and assets first, and do not default to translation/workflow-layer sync work unless the user explicitly asked for it or the language-finalization workflow requires it. Only edit both the canonical manuscript and the workflow-language paper layer in the same round when the user explicitly asks for cross-language synchronization or when a final-draft/export language-finalization step requires both layers to be refreshed together. Do not treat a routine tighten/compress/polish request as an instruction to sync the workflow-language companion. For export or remote-publication rounds, if `paper_language_finalization_decision=convert-to-paper-language`, include the workflow-language paper layer in the exported or pushed bundle by default. Allow canonical-only export or remote publication only when the user explicitly asked for it or when the remote target forbids extra files. If any gate item is unresolved, or if a banned expression or move from the current section policy remains, spend the round fixing that blocker instead of polishing sentences further, and do not default the next-step recommendation to another polish pass. Main tables must be locally self-contained: the title, header, note, and adjacent prose should tell the reader what each row and column means, the metric direction, and any relevant unit, denominator, or event condition. Short headers remain allowed, but abbreviations in paper-facing tables must be expanded locally in the same table. If Method or Experiments prose promises a metric family, the main table set must either expose those metrics directly or explicitly mark the missing ones as appendix-only and explain why. If a metric is measured but omitted because it is zero everywhere, redundant, or appendix-only, state that disposition explicitly in the table note instead of silently dropping it. Do not treat `\resizebox{\linewidth}{!}{...}` as the default way to fit a main table. Fit main tables by redesign first: shorten headers, move secondary metrics out of the main table, reduce or split columns, then adjust `\tabcolsep` conservatively; only use `\resizebox` as a last resort, keep width changes readable, and explain the width-control rationale locally in the same table note. Do not use `\scriptsize` or `\tiny` as the default main-table fit strategy. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check, the section-level acceptance gate, section-style policy compliance, the protocol/scope impact audit, the export or remote bundle audit, the round target layer, any canonical-only justification while workflow-language was active, any cross-language sync justification, and the table-semantics audit in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language paper-layer path in the latest write iteration, and only then edit the final manuscript in the chosen language.

package/package-assets/claude/commands/lab-write.md

@@ -10,6 +10,6 @@ Execute the requested `/lab-write` command against the user's argument now. Do n
 When the user provides reference PDFs, paper URLs, local reference-paper paths, or asks to write by reference, stay within the write stage and switch to reference-guided deep-write. Extract structure, map section/subsection slots, paragraph roles, table/figure roles, and bridge logic to the current paper, record the consumption plan, and only then draft prose. The current section must visibly realize the mapped slots; do not treat a consumption plan as enough. Reuse structure only; do not copy wording, claims, metrics, captions, or conclusions. Keep service-style or AI-assistant meta language and workflow-only placeholder language out of paper-facing prose.
 When Method, Experiments, captions, tables, or analysis assets introduce or revise reported metrics, create or update `.lab/writing/metric-glossary.md` before prose polish. Each metric must define its paper-facing name, approved short name, table/header label, plain-language definition, calculation, unit or denominator, direction, scope or conditions, allowed aliases, forbidden aliases, and first-use location. Use the same metric names across prose, captions, table notes, table headers, and result summaries. Run `validate_metric_glossary.py` and remove forbidden aliases from reader-facing LaTeX before finalizing the round.
 Carry the same core insight anchor through the paper: Introduction creates the cognitive contrast, Method turns the insight into design motivation, Experiments diagnose it with evidence, and Conclusion states the broader principle and boundary. Do not create a standalone `Our Insights` section just to satisfy this; weave the insight into motivation, mechanism, evidence, and limitations.
-Chinese workflow-language terminology: when `workflow_language=zh`, concept terms should use a Chinese paper-facing name and a Chinese short form by default. English full form plus acronym may appear at first mention only as `中文全称（English full form, ACRONYM）`, then prose should reuse the Chinese short form. Prefer natural compact Chinese short forms; two-character, three-character, four-character, or longer short phrases are all acceptable when they read naturally. Do not force a fixed-length abbreviation. Avoid repeating English concept fragments throughout Chinese prose. Run `validate_workflow_language_text.py` on touched Chinese workflow-language sections, tables, figures, and analysis assets before completing the write round.
-For Chinese workflow-language output, run `validate_workflow_language_text.py` over the touched workflow-language sections, tables, figures, and analysis assets before completing the write round. If it reports English concept fragments, translate them or define a justified glossary exception before prose polish.
+Chinese workflow-language terminology: when `workflow_language=zh`, concept terms should use a Chinese paper-facing name and a Chinese short form by default. English full form plus acronym may appear at first mention only as `中文全称（English full form, ACRONYM）`, then prose should reuse the Chinese short form. Prefer natural compact Chinese short forms; two-character, three-character, four-character, or longer short phrases are all acceptable when they read naturally. Do not force a fixed-length abbreviation. Avoid repeating English concept fragments throughout Chinese prose. Before completing the write round, run `validate_paper_layer.py` on the resolved active Chinese paper layer so the whole layer is checked rather than only the touched file. Use `validate_workflow_language_text.py` as a local repair helper when narrowing down specific offending files.
+For Chinese workflow-language output, run `validate_paper_layer.py` on the resolved active paper layer before completing the write round so the whole layer is checked instead of only the touched file. Use `validate_workflow_language_text.py` as a local repair helper when narrowing down specific offending files. If the layer validator reports English concept fragments or English paper-facing headings/captions, translate them or define a justified glossary exception before prose polish.
 This command runs the `write` stage of the lab workflow. Use `.claude/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference, the current section block in `section-style-policies.md`, and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. When `workflow_language` and `paper_language` differ, treat the workflow-language paper layer as the default ordinary working layer. Ordinary write rounds should still edit one target paper layer at a time rather than silently refreshing both language layers. If the user names a concrete file or layer, treat that as the only target for the round unless they also explicitly request synchronization. If a workflow-language paper layer is active and the round still targets the canonical manuscript, record why canonical-only writing was acceptable in the write iteration artifact. If `paper_language_finalization_decision=convert-to-paper-language`, explicit canonical-manuscript work may target the canonical `paper_language` manuscript, but that does not make canonical the default ordinary working layer while workflow-language remains active. Treat the workflow-language paper layer as a real persisted artifact rather than a review layer, and preserve it as a full LaTeX mirror with `workflow-language/main.tex`, `workflow-language/references.bib`, `workflow-language/sections/*.tex`, `workflow-language/tables/*.tex`, `workflow-language/figures/*.tex`, and `workflow-language/analysis/analysis-asset.tex`. Do not write new workflow-language output to deprecated review-layer paths such as `docs/lab/paper/review_zh/`. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, do not use labels containing `_` or `-` in reader-facing prose, apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels, do not assume a fixed drafting order such as Method before Experiments, add a local naming bridge when a section uses canonical short names before their defining section has been drafted, and reuse the canonical label instead of replacing it with a narrative alias. Follow the current section's encouraged, discouraged, and banned expression lists from `section-style-policies.md`; section-specific banned expressions take priority over prose-polish goals. Before any additional tighten, compress, or polish pass on the same section, run a section-level acceptance gate first. That gate must explicitly confirm naming consistency, adjacent-section consistency, claim, metric, and ranking consistency with the current evidence, local clarity, local concision, and section-style compliance. If the round changes the paper's canonical experiment or evaluation protocol, treat that change as a canonical replacement unless the user explicitly scoped it as supplementary or appendix-only, run a paper-wide impact audit before more polishing, update the highest-impact stale sections and assets first, and do not default to translation/workflow-layer sync work unless the user explicitly asked for it or the language-finalization workflow requires it. Only edit both the canonical manuscript and the workflow-language paper layer in the same round when the user explicitly asks for cross-language synchronization or when a final-draft/export language-finalization step requires both layers to be refreshed together. Do not treat a routine tighten/compress/polish request as an instruction to sync the workflow-language companion. For export or remote-publication rounds, if `paper_language_finalization_decision=convert-to-paper-language`, include the workflow-language paper layer in the exported or pushed bundle by default. Allow canonical-only export or remote publication only when the user explicitly asked for it or when the remote target forbids extra files. If any gate item is unresolved, or if a banned expression or move from the current section policy remains, spend the round fixing that blocker instead of polishing sentences further, and do not default the next-step recommendation to another polish pass. Main tables must be locally self-contained: the title, header, note, and adjacent prose should tell the reader what each row and column means, the metric direction, and any relevant unit, denominator, or event condition. Short headers remain allowed, but abbreviations in paper-facing tables must be expanded locally in the same table. If Method or Experiments prose promises a metric family, the main table set must either expose those metrics directly or explicitly mark the missing ones as appendix-only and explain why. If a metric is measured but omitted because it is zero everywhere, redundant, or appendix-only, state that disposition explicitly in the table note instead of silently dropping it. Do not treat `\resizebox{\linewidth}{!}{...}` as the default way to fit a main table. Fit main tables by redesign first: shorten headers, move secondary metrics out of the main table, reduce or split columns, then adjust `\tabcolsep` conservatively; only use `\resizebox` as a last resort, keep width changes readable, and explain the width-control rationale locally in the same table note. Do not use `\scriptsize` or `\tiny` as the default main-table fit strategy. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check, the section-level acceptance gate, section-style policy compliance, the protocol/scope impact audit, the export or remote bundle audit, the round target layer, any canonical-only justification while workflow-language was active, any cross-language sync justification, and the table-semantics audit in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language paper-layer path in the latest write iteration, and only then edit the final manuscript in the chosen language.

package/package-assets/claude/commands/lab:write.md

@@ -10,6 +10,6 @@ Execute the requested `/lab-write` command against the user's argument now. Do n
 When the user provides reference PDFs, paper URLs, local reference-paper paths, or asks to write by reference, stay within the write stage and switch to reference-guided deep-write. Extract structure, map section/subsection slots, paragraph roles, table/figure roles, and bridge logic to the current paper, record the consumption plan, and only then draft prose. The current section must visibly realize the mapped slots; do not treat a consumption plan as enough. Reuse structure only; do not copy wording, claims, metrics, captions, or conclusions. Keep service-style or AI-assistant meta language and workflow-only placeholder language out of paper-facing prose.
 When Method, Experiments, captions, tables, or analysis assets introduce or revise reported metrics, create or update `.lab/writing/metric-glossary.md` before prose polish. Each metric must define its paper-facing name, approved short name, table/header label, plain-language definition, calculation, unit or denominator, direction, scope or conditions, allowed aliases, forbidden aliases, and first-use location. Use the same metric names across prose, captions, table notes, table headers, and result summaries. Run `validate_metric_glossary.py` and remove forbidden aliases from reader-facing LaTeX before finalizing the round.
 Carry the same core insight anchor through the paper: Introduction creates the cognitive contrast, Method turns the insight into design motivation, Experiments diagnose it with evidence, and Conclusion states the broader principle and boundary. Do not create a standalone `Our Insights` section just to satisfy this; weave the insight into motivation, mechanism, evidence, and limitations.
-Chinese workflow-language terminology: when `workflow_language=zh`, concept terms should use a Chinese paper-facing name and a Chinese short form by default. English full form plus acronym may appear at first mention only as `中文全称（English full form, ACRONYM）`, then prose should reuse the Chinese short form. Prefer natural compact Chinese short forms; two-character, three-character, four-character, or longer short phrases are all acceptable when they read naturally. Do not force a fixed-length abbreviation. Avoid repeating English concept fragments throughout Chinese prose. Run `validate_workflow_language_text.py` on touched Chinese workflow-language sections, tables, figures, and analysis assets before completing the write round.
-For Chinese workflow-language output, run `validate_workflow_language_text.py` over the touched workflow-language sections, tables, figures, and analysis assets before completing the write round. If it reports English concept fragments, translate them or define a justified glossary exception before prose polish.
+Chinese workflow-language terminology: when `workflow_language=zh`, concept terms should use a Chinese paper-facing name and a Chinese short form by default. English full form plus acronym may appear at first mention only as `中文全称（English full form, ACRONYM）`, then prose should reuse the Chinese short form. Prefer natural compact Chinese short forms; two-character, three-character, four-character, or longer short phrases are all acceptable when they read naturally. Do not force a fixed-length abbreviation. Avoid repeating English concept fragments throughout Chinese prose. Before completing the write round, run `validate_paper_layer.py` on the resolved active Chinese paper layer so the whole layer is checked rather than only the touched file. Use `validate_workflow_language_text.py` as a local repair helper when narrowing down specific offending files.
+For Chinese workflow-language output, run `validate_paper_layer.py` on the resolved active paper layer before completing the write round so the whole layer is checked instead of only the touched file. Use `validate_workflow_language_text.py` as a local repair helper when narrowing down specific offending files. If the layer validator reports English concept fragments or English paper-facing headings/captions, translate them or define a justified glossary exception before prose polish.
 This command runs the `write` stage of the lab workflow. Use `.claude/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference, the current section block in `section-style-policies.md`, and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. When `workflow_language` and `paper_language` differ, treat the workflow-language paper layer as the default ordinary working layer. Ordinary write rounds should still edit one target paper layer at a time rather than silently refreshing both language layers. If the user names a concrete file or layer, treat that as the only target for the round unless they also explicitly request synchronization. If a workflow-language paper layer is active and the round still targets the canonical manuscript, record why canonical-only writing was acceptable in the write iteration artifact. If `paper_language_finalization_decision=convert-to-paper-language`, explicit canonical-manuscript work may target the canonical `paper_language` manuscript, but that does not make canonical the default ordinary working layer while workflow-language remains active. Treat the workflow-language paper layer as a real persisted artifact rather than a review layer, and preserve it as a full LaTeX mirror with `workflow-language/main.tex`, `workflow-language/references.bib`, `workflow-language/sections/*.tex`, `workflow-language/tables/*.tex`, `workflow-language/figures/*.tex`, and `workflow-language/analysis/analysis-asset.tex`. Do not write new workflow-language output to deprecated review-layer paths such as `docs/lab/paper/review_zh/`. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, do not use labels containing `_` or `-` in reader-facing prose, apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels, do not assume a fixed drafting order such as Method before Experiments, add a local naming bridge when a section uses canonical short names before their defining section has been drafted, and reuse the canonical label instead of replacing it with a narrative alias. Follow the current section's encouraged, discouraged, and banned expression lists from `section-style-policies.md`; section-specific banned expressions take priority over prose-polish goals. Before any additional tighten, compress, or polish pass on the same section, run a section-level acceptance gate first. That gate must explicitly confirm naming consistency, adjacent-section consistency, claim, metric, and ranking consistency with the current evidence, local clarity, local concision, and section-style compliance. If the round changes the paper's canonical experiment or evaluation protocol, treat that change as a canonical replacement unless the user explicitly scoped it as supplementary or appendix-only, run a paper-wide impact audit before more polishing, update the highest-impact stale sections and assets first, and do not default to translation/workflow-layer sync work unless the user explicitly asked for it or the language-finalization workflow requires it. Only edit both the canonical manuscript and the workflow-language paper layer in the same round when the user explicitly asks for cross-language synchronization or when a final-draft/export language-finalization step requires both layers to be refreshed together. Do not treat a routine tighten/compress/polish request as an instruction to sync the workflow-language companion. For export or remote-publication rounds, if `paper_language_finalization_decision=convert-to-paper-language`, include the workflow-language paper layer in the exported or pushed bundle by default. Allow canonical-only export or remote publication only when the user explicitly asked for it or when the remote target forbids extra files. If any gate item is unresolved, or if a banned expression or move from the current section policy remains, spend the round fixing that blocker instead of polishing sentences further, and do not default the next-step recommendation to another polish pass. Main tables must be locally self-contained: the title, header, note, and adjacent prose should tell the reader what each row and column means, the metric direction, and any relevant unit, denominator, or event condition. Short headers remain allowed, but abbreviations in paper-facing tables must be expanded locally in the same table. If Method or Experiments prose promises a metric family, the main table set must either expose those metrics directly or explicitly mark the missing ones as appendix-only and explain why. If a metric is measured but omitted because it is zero everywhere, redundant, or appendix-only, state that disposition explicitly in the table note instead of silently dropping it. Do not treat `\resizebox{\linewidth}{!}{...}` as the default way to fit a main table. Fit main tables by redesign first: shorten headers, move secondary metrics out of the main table, reduce or split columns, then adjust `\tabcolsep` conservatively; only use `\resizebox` as a last resort, keep width changes readable, and explain the width-control rationale locally in the same table note. Do not use `\scriptsize` or `\tiny` as the default main-table fit strategy. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check, the section-level acceptance gate, section-style policy compliance, the protocol/scope impact audit, the export or remote bundle audit, the round target layer, any canonical-only justification while workflow-language was active, any cross-language sync justification, and the table-semantics audit in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language paper-layer path in the latest write iteration, and only then edit the final manuscript in the chosen language.

package/package-assets/claude/commands/lab/357/274/232write.md

@@ -10,6 +10,6 @@ Execute the requested `/lab-write` command against the user's argument now. Do n
 When the user provides reference PDFs, paper URLs, local reference-paper paths, or asks to write by reference, stay within the write stage and switch to reference-guided deep-write. Extract structure, map section/subsection slots, paragraph roles, table/figure roles, and bridge logic to the current paper, record the consumption plan, and only then draft prose. The current section must visibly realize the mapped slots; do not treat a consumption plan as enough. Reuse structure only; do not copy wording, claims, metrics, captions, or conclusions. Keep service-style or AI-assistant meta language and workflow-only placeholder language out of paper-facing prose.
 When Method, Experiments, captions, tables, or analysis assets introduce or revise reported metrics, create or update `.lab/writing/metric-glossary.md` before prose polish. Each metric must define its paper-facing name, approved short name, table/header label, plain-language definition, calculation, unit or denominator, direction, scope or conditions, allowed aliases, forbidden aliases, and first-use location. Use the same metric names across prose, captions, table notes, table headers, and result summaries. Run `validate_metric_glossary.py` and remove forbidden aliases from reader-facing LaTeX before finalizing the round.
 Carry the same core insight anchor through the paper: Introduction creates the cognitive contrast, Method turns the insight into design motivation, Experiments diagnose it with evidence, and Conclusion states the broader principle and boundary. Do not create a standalone `Our Insights` section just to satisfy this; weave the insight into motivation, mechanism, evidence, and limitations.
-Chinese workflow-language terminology: when `workflow_language=zh`, concept terms should use a Chinese paper-facing name and a Chinese short form by default. English full form plus acronym may appear at first mention only as `中文全称（English full form, ACRONYM）`, then prose should reuse the Chinese short form. Prefer natural compact Chinese short forms; two-character, three-character, four-character, or longer short phrases are all acceptable when they read naturally. Do not force a fixed-length abbreviation. Avoid repeating English concept fragments throughout Chinese prose. Run `validate_workflow_language_text.py` on touched Chinese workflow-language sections, tables, figures, and analysis assets before completing the write round.
-For Chinese workflow-language output, run `validate_workflow_language_text.py` over the touched workflow-language sections, tables, figures, and analysis assets before completing the write round. If it reports English concept fragments, translate them or define a justified glossary exception before prose polish.
+Chinese workflow-language terminology: when `workflow_language=zh`, concept terms should use a Chinese paper-facing name and a Chinese short form by default. English full form plus acronym may appear at first mention only as `中文全称（English full form, ACRONYM）`, then prose should reuse the Chinese short form. Prefer natural compact Chinese short forms; two-character, three-character, four-character, or longer short phrases are all acceptable when they read naturally. Do not force a fixed-length abbreviation. Avoid repeating English concept fragments throughout Chinese prose. Before completing the write round, run `validate_paper_layer.py` on the resolved active Chinese paper layer so the whole layer is checked rather than only the touched file. Use `validate_workflow_language_text.py` as a local repair helper when narrowing down specific offending files.
+For Chinese workflow-language output, run `validate_paper_layer.py` on the resolved active paper layer before completing the write round so the whole layer is checked instead of only the touched file. Use `validate_workflow_language_text.py` as a local repair helper when narrowing down specific offending files. If the layer validator reports English concept fragments or English paper-facing headings/captions, translate them or define a justified glossary exception before prose polish.
 This command runs the `write` stage of the lab workflow. Use `.claude/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference, the current section block in `section-style-policies.md`, and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. When `workflow_language` and `paper_language` differ, treat the workflow-language paper layer as the default ordinary working layer. Ordinary write rounds should still edit one target paper layer at a time rather than silently refreshing both language layers. If the user names a concrete file or layer, treat that as the only target for the round unless they also explicitly request synchronization. If a workflow-language paper layer is active and the round still targets the canonical manuscript, record why canonical-only writing was acceptable in the write iteration artifact. If `paper_language_finalization_decision=convert-to-paper-language`, explicit canonical-manuscript work may target the canonical `paper_language` manuscript, but that does not make canonical the default ordinary working layer while workflow-language remains active. Treat the workflow-language paper layer as a real persisted artifact rather than a review layer, and preserve it as a full LaTeX mirror with `workflow-language/main.tex`, `workflow-language/references.bib`, `workflow-language/sections/*.tex`, `workflow-language/tables/*.tex`, `workflow-language/figures/*.tex`, and `workflow-language/analysis/analysis-asset.tex`. Do not write new workflow-language output to deprecated review-layer paths such as `docs/lab/paper/review_zh/`. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, do not use labels containing `_` or `-` in reader-facing prose, apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels, do not assume a fixed drafting order such as Method before Experiments, add a local naming bridge when a section uses canonical short names before their defining section has been drafted, and reuse the canonical label instead of replacing it with a narrative alias. Follow the current section's encouraged, discouraged, and banned expression lists from `section-style-policies.md`; section-specific banned expressions take priority over prose-polish goals. Before any additional tighten, compress, or polish pass on the same section, run a section-level acceptance gate first. That gate must explicitly confirm naming consistency, adjacent-section consistency, claim, metric, and ranking consistency with the current evidence, local clarity, local concision, and section-style compliance. If the round changes the paper's canonical experiment or evaluation protocol, treat that change as a canonical replacement unless the user explicitly scoped it as supplementary or appendix-only, run a paper-wide impact audit before more polishing, update the highest-impact stale sections and assets first, and do not default to translation/workflow-layer sync work unless the user explicitly asked for it or the language-finalization workflow requires it. Only edit both the canonical manuscript and the workflow-language paper layer in the same round when the user explicitly asks for cross-language synchronization or when a final-draft/export language-finalization step requires both layers to be refreshed together. Do not treat a routine tighten/compress/polish request as an instruction to sync the workflow-language companion. For export or remote-publication rounds, if `paper_language_finalization_decision=convert-to-paper-language`, include the workflow-language paper layer in the exported or pushed bundle by default. Allow canonical-only export or remote publication only when the user explicitly asked for it or when the remote target forbids extra files. If any gate item is unresolved, or if a banned expression or move from the current section policy remains, spend the round fixing that blocker instead of polishing sentences further, and do not default the next-step recommendation to another polish pass. Main tables must be locally self-contained: the title, header, note, and adjacent prose should tell the reader what each row and column means, the metric direction, and any relevant unit, denominator, or event condition. Short headers remain allowed, but abbreviations in paper-facing tables must be expanded locally in the same table. If Method or Experiments prose promises a metric family, the main table set must either expose those metrics directly or explicitly mark the missing ones as appendix-only and explain why. If a metric is measured but omitted because it is zero everywhere, redundant, or appendix-only, state that disposition explicitly in the table note instead of silently dropping it. Do not treat `\resizebox{\linewidth}{!}{...}` as the default way to fit a main table. Fit main tables by redesign first: shorten headers, move secondary metrics out of the main table, reduce or split columns, then adjust `\tabcolsep` conservatively; only use `\resizebox` as a last resort, keep width changes readable, and explain the width-control rationale locally in the same table note. Do not use `\scriptsize` or `\tiny` as the default main-table fit strategy. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check, the section-level acceptance gate, section-style policy compliance, the protocol/scope impact audit, the export or remote bundle audit, the round target layer, any canonical-only justification while workflow-language was active, any cross-language sync justification, and the table-semantics audit in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language paper-layer path in the latest write iteration, and only then edit the final manuscript in the chosen language.

package/package-assets/codex/prompts/lab/write.md

@@ -8,6 +8,6 @@ Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
 Execute the requested `/lab:write` stage against the user's argument now. Do not only recommend another lab stage. If a blocking prerequisite is missing, say exactly what is missing and ask at most one clarifying question.
 When the user provides reference PDFs, paper URLs, local reference-paper paths, or asks to write by reference, stay within the write stage and switch to reference-guided deep-write. Extract structure, map section/subsection slots, paragraph roles, table/figure roles, and bridge logic to the current paper, record the consumption plan, and only then draft prose. The current section must visibly realize the mapped slots; do not treat a consumption plan as enough. Reuse structure only; do not copy wording, claims, metrics, captions, or conclusions. Keep service-style or AI-assistant meta language and workflow-only placeholder language out of paper-facing prose.
 When Method, Experiments, captions, tables, or analysis assets introduce or revise reported metrics, create or update `.lab/writing/metric-glossary.md` before prose polish. Each metric must define its paper-facing name, approved short name, table/header label, plain-language definition, calculation, unit or denominator, direction, scope or conditions, allowed aliases, forbidden aliases, and first-use location. Use the same metric names across prose, captions, table notes, table headers, and result summaries. Run `validate_metric_glossary.py` and remove forbidden aliases from reader-facing LaTeX before finalizing the round.
-Chinese workflow-language terminology: when `workflow_language=zh`, concept terms should use a Chinese paper-facing name and a Chinese short form by default. English full form plus acronym may appear at first mention only as `中文全称（English full form, ACRONYM）`, then prose should reuse the Chinese short form. Prefer natural compact Chinese short forms; two-character, three-character, four-character, or longer short phrases are all acceptable when they read naturally. Do not force a fixed-length abbreviation. Avoid repeating English concept fragments throughout Chinese prose. Run `validate_workflow_language_text.py` on touched Chinese workflow-language sections, tables, figures, and analysis assets before completing the write round.
-For Chinese workflow-language output, run `validate_workflow_language_text.py` over the touched workflow-language sections, tables, figures, and analysis assets before completing the write round. If it reports English concept fragments, translate them or define a justified glossary exception before prose polish.
+Chinese workflow-language terminology: when `workflow_language=zh`, concept terms should use a Chinese paper-facing name and a Chinese short form by default. English full form plus acronym may appear at first mention only as `中文全称（English full form, ACRONYM）`, then prose should reuse the Chinese short form. Prefer natural compact Chinese short forms; two-character, three-character, four-character, or longer short phrases are all acceptable when they read naturally. Do not force a fixed-length abbreviation. Avoid repeating English concept fragments throughout Chinese prose. Before completing the write round, run `validate_paper_layer.py` on the resolved active Chinese paper layer so the whole layer is checked rather than only the touched file. Use `validate_workflow_language_text.py` as a local repair helper when narrowing down specific offending files.
+For Chinese workflow-language output, run `validate_paper_layer.py` on the resolved active paper layer before completing the write round so the whole layer is checked instead of only the touched file. Use `validate_workflow_language_text.py` as a local repair helper when narrowing down specific offending files. If the layer validator reports English concept fragments or English paper-facing headings/captions, translate them or define a justified glossary exception before prose polish.
 This command runs the `/lab:write` stage. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Carry the same core insight anchor through the paper: Introduction creates the cognitive contrast, Method turns the insight into design motivation, Experiments diagnose it with evidence, and Conclusion states the broader principle and boundary. Do not create a standalone `Our Insights` section just to satisfy this; weave the insight into motivation, mechanism, evidence, and limitations. Read the matching paper-writing reference, the current section block in `section-style-policies.md`, and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. When `workflow_language` and `paper_language` differ, treat the workflow-language paper layer as the default ordinary working layer. Resolve the active paper topology from `.lab/config/workflow.json` before drafting: the active canonical root is `<deliverables_root>/paper/`, and when workflow-language is active its root is `<deliverables_root>/paper/workflow-language/`. Ordinary write rounds should still edit one target paper layer at a time rather than silently refreshing both language layers. If the user names a concrete file or layer, treat that as the only target for the round unless they also explicitly request synchronization. Classify the named target path before editing it. Only active-layer targets count as managed manuscript rounds; legacy side layers such as `review_zh`, `translation_zh`, `sections_zh`, or stale `deliverables/.../workflow-language/*.md` paths are out-of-band/legacy edits and must not silently replace the active paper topology. If a workflow-language paper layer is active and the round still targets the canonical manuscript, record why canonical-only writing was acceptable in the write iteration artifact. If `paper_language_finalization_decision=convert-to-paper-language`, explicit canonical-manuscript work may target the canonical `paper_language` manuscript, but that does not make canonical the default ordinary working layer while workflow-language remains active. Treat the workflow-language paper layer as a real persisted artifact rather than a review layer, and preserve it as a full LaTeX mirror with `workflow-language/main.tex`, `workflow-language/references.bib`, `workflow-language/sections/*.tex`, `workflow-language/tables/*.tex`, `workflow-language/figures/*.tex`, and `workflow-language/analysis/analysis-asset.tex`. Do not write new workflow-language output to deprecated review-layer paths such as `docs/lab/paper/review_zh/`. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, do not use labels containing `_` or `-` in reader-facing prose, apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels, do not assume a fixed drafting order such as Method before Experiments, add a local naming bridge when a section uses canonical short names before their defining section has been drafted, and reuse the canonical label instead of replacing it with a narrative alias. Follow the current section's encouraged, discouraged, and banned expression lists from `section-style-policies.md`; section-specific banned expressions take priority over prose-polish goals. Before any additional tighten, compress, or polish pass on the same section, run a section-level acceptance gate first. That gate must explicitly confirm naming consistency, adjacent-section consistency, claim, metric, and ranking consistency with the current evidence, local clarity, local concision, and section-style compliance. If the round changes the paper's canonical experiment or evaluation protocol, treat that change as a canonical replacement unless the user explicitly scoped it as supplementary or appendix-only, run a paper-wide impact audit before more polishing, update the highest-impact stale sections and assets first, and do not default to translation/workflow-layer sync work unless the user explicitly asked for it or the language-finalization workflow requires it. Only edit both the canonical manuscript and the workflow-language paper layer in the same round when the user explicitly asks for cross-language synchronization or when a final-draft/export language-finalization step requires both layers to be refreshed together. Do not treat a routine tighten/compress/polish request as an instruction to sync the workflow-language companion. For export or remote-publication rounds, if `paper_language_finalization_decision=convert-to-paper-language`, include the workflow-language paper layer in the exported or pushed bundle by default. Allow canonical-only export or remote publication only when the user explicitly asked for it or when the remote target forbids extra files. If any gate item is unresolved, or if a banned expression or move from the current section policy remains, spend the round fixing that blocker instead of polishing sentences further, and do not default the next-step recommendation to another polish pass. Main tables must be locally self-contained: the title, header, note, and adjacent prose should tell the reader what each row and column means, the metric direction, and any relevant unit, denominator, or event condition. Short headers remain allowed, but abbreviations in paper-facing tables must be expanded locally in the same table. If Method or Experiments prose promises a metric family, the main table set must either expose those metrics directly or explicitly mark the missing ones as appendix-only and explain why. If a metric is measured but omitted because it is zero everywhere, redundant, or appendix-only, state that disposition explicitly in the table note instead of silently dropping it. Do not treat `\resizebox{\linewidth}{!}{...}` as the default way to fit a main table. Fit main tables by redesign first: shorten headers, move secondary metrics out of the main table, reduce or split columns, then adjust `\tabcolsep` conservatively; only use `\resizebox` as a last resort, keep width changes readable, and explain the width-control rationale locally in the same table note. Do not use `\scriptsize` or `\tiny` as the default main-table fit strategy. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check, the section-level acceptance gate, section-style policy compliance, the protocol/scope impact audit, the export or remote bundle audit, the round target layer, any canonical-only justification while workflow-language was active, any cross-language sync justification, the active canonical/workflow-language roots, the resolved target path role, any out-of-band justification, the insight integration audit, and the table-semantics audit in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language paper-layer path in the latest write iteration, and only then edit the final manuscript in the chosen language.

package/package-assets/codex/prompts/lab-write.md

@@ -8,6 +8,6 @@ Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
 Execute the requested `/lab:write` stage against the user's argument now. Do not only recommend another lab stage. If a blocking prerequisite is missing, say exactly what is missing and ask at most one clarifying question.
 When the user provides reference PDFs, paper URLs, local reference-paper paths, or asks to write by reference, stay within the write stage and switch to reference-guided deep-write. Extract structure, map section/subsection slots, paragraph roles, table/figure roles, and bridge logic to the current paper, record the consumption plan, and only then draft prose. The current section must visibly realize the mapped slots; do not treat a consumption plan as enough. Reuse structure only; do not copy wording, claims, metrics, captions, or conclusions. Keep service-style or AI-assistant meta language and workflow-only placeholder language out of paper-facing prose.
 When Method, Experiments, captions, tables, or analysis assets introduce or revise reported metrics, create or update `.lab/writing/metric-glossary.md` before prose polish. Each metric must define its paper-facing name, approved short name, table/header label, plain-language definition, calculation, unit or denominator, direction, scope or conditions, allowed aliases, forbidden aliases, and first-use location. Use the same metric names across prose, captions, table notes, table headers, and result summaries. Run `validate_metric_glossary.py` and remove forbidden aliases from reader-facing LaTeX before finalizing the round.
-Chinese workflow-language terminology: when `workflow_language=zh`, concept terms should use a Chinese paper-facing name and a Chinese short form by default. English full form plus acronym may appear at first mention only as `中文全称（English full form, ACRONYM）`, then prose should reuse the Chinese short form. Prefer natural compact Chinese short forms; two-character, three-character, four-character, or longer short phrases are all acceptable when they read naturally. Do not force a fixed-length abbreviation. Avoid repeating English concept fragments throughout Chinese prose. Run `validate_workflow_language_text.py` on touched Chinese workflow-language sections, tables, figures, and analysis assets before completing the write round.
-For Chinese workflow-language output, run `validate_workflow_language_text.py` over the touched workflow-language sections, tables, figures, and analysis assets before completing the write round. If it reports English concept fragments, translate them or define a justified glossary exception before prose polish.
+Chinese workflow-language terminology: when `workflow_language=zh`, concept terms should use a Chinese paper-facing name and a Chinese short form by default. English full form plus acronym may appear at first mention only as `中文全称（English full form, ACRONYM）`, then prose should reuse the Chinese short form. Prefer natural compact Chinese short forms; two-character, three-character, four-character, or longer short phrases are all acceptable when they read naturally. Do not force a fixed-length abbreviation. Avoid repeating English concept fragments throughout Chinese prose. Before completing the write round, run `validate_paper_layer.py` on the resolved active Chinese paper layer so the whole layer is checked rather than only the touched file. Use `validate_workflow_language_text.py` as a local repair helper when narrowing down specific offending files.
+For Chinese workflow-language output, run `validate_paper_layer.py` on the resolved active paper layer before completing the write round so the whole layer is checked instead of only the touched file. Use `validate_workflow_language_text.py` as a local repair helper when narrowing down specific offending files. If the layer validator reports English concept fragments or English paper-facing headings/captions, translate them or define a justified glossary exception before prose polish.
 This command runs the `/lab:write` stage. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Carry the same core insight anchor through the paper: Introduction creates the cognitive contrast, Method turns the insight into design motivation, Experiments diagnose it with evidence, and Conclusion states the broader principle and boundary. Do not create a standalone `Our Insights` section just to satisfy this; weave the insight into motivation, mechanism, evidence, and limitations. Read the matching paper-writing reference, the current section block in `section-style-policies.md`, and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. When `workflow_language` and `paper_language` differ, treat the workflow-language paper layer as the default ordinary working layer. Resolve the active paper topology from `.lab/config/workflow.json` before drafting: the active canonical root is `<deliverables_root>/paper/`, and when workflow-language is active its root is `<deliverables_root>/paper/workflow-language/`. Ordinary write rounds should still edit one target paper layer at a time rather than silently refreshing both language layers. If the user names a concrete file or layer, treat that as the only target for the round unless they also explicitly request synchronization. Classify the named target path before editing it. Only active-layer targets count as managed manuscript rounds; legacy side layers such as `review_zh`, `translation_zh`, `sections_zh`, or stale `deliverables/.../workflow-language/*.md` paths are out-of-band/legacy edits and must not silently replace the active paper topology. If a workflow-language paper layer is active and the round still targets the canonical manuscript, record why canonical-only writing was acceptable in the write iteration artifact. If `paper_language_finalization_decision=convert-to-paper-language`, explicit canonical-manuscript work may target the canonical `paper_language` manuscript, but that does not make canonical the default ordinary working layer while workflow-language remains active. Treat the workflow-language paper layer as a real persisted artifact rather than a review layer, and preserve it as a full LaTeX mirror with `workflow-language/main.tex`, `workflow-language/references.bib`, `workflow-language/sections/*.tex`, `workflow-language/tables/*.tex`, `workflow-language/figures/*.tex`, and `workflow-language/analysis/analysis-asset.tex`. Do not write new workflow-language output to deprecated review-layer paths such as `docs/lab/paper/review_zh/`. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, do not use labels containing `_` or `-` in reader-facing prose, apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels, do not assume a fixed drafting order such as Method before Experiments, add a local naming bridge when a section uses canonical short names before their defining section has been drafted, and reuse the canonical label instead of replacing it with a narrative alias. Follow the current section's encouraged, discouraged, and banned expression lists from `section-style-policies.md`; section-specific banned expressions take priority over prose-polish goals. Before any additional tighten, compress, or polish pass on the same section, run a section-level acceptance gate first. That gate must explicitly confirm naming consistency, adjacent-section consistency, claim, metric, and ranking consistency with the current evidence, local clarity, local concision, and section-style compliance. If the round changes the paper's canonical experiment or evaluation protocol, treat that change as a canonical replacement unless the user explicitly scoped it as supplementary or appendix-only, run a paper-wide impact audit before more polishing, update the highest-impact stale sections and assets first, and do not default to translation/workflow-layer sync work unless the user explicitly asked for it or the language-finalization workflow requires it. Only edit both the canonical manuscript and the workflow-language paper layer in the same round when the user explicitly asks for cross-language synchronization or when a final-draft/export language-finalization step requires both layers to be refreshed together. Do not treat a routine tighten/compress/polish request as an instruction to sync the workflow-language companion. For export or remote-publication rounds, if `paper_language_finalization_decision=convert-to-paper-language`, include the workflow-language paper layer in the exported or pushed bundle by default. Allow canonical-only export or remote publication only when the user explicitly asked for it or when the remote target forbids extra files. If any gate item is unresolved, or if a banned expression or move from the current section policy remains, spend the round fixing that blocker instead of polishing sentences further, and do not default the next-step recommendation to another polish pass. Main tables must be locally self-contained: the title, header, note, and adjacent prose should tell the reader what each row and column means, the metric direction, and any relevant unit, denominator, or event condition. Short headers remain allowed, but abbreviations in paper-facing tables must be expanded locally in the same table. If Method or Experiments prose promises a metric family, the main table set must either expose those metrics directly or explicitly mark the missing ones as appendix-only and explain why. If a metric is measured but omitted because it is zero everywhere, redundant, or appendix-only, state that disposition explicitly in the table note instead of silently dropping it. Do not treat `\resizebox{\linewidth}{!}{...}` as the default way to fit a main table. Fit main tables by redesign first: shorten headers, move secondary metrics out of the main table, reduce or split columns, then adjust `\tabcolsep` conservatively; only use `\resizebox` as a last resort, keep width changes readable, and explain the width-control rationale locally in the same table note. Do not use `\scriptsize` or `\tiny` as the default main-table fit strategy. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check, the section-level acceptance gate, section-style policy compliance, the protocol/scope impact audit, the export or remote bundle audit, the round target layer, any canonical-only justification while workflow-language was active, any cross-language sync justification, the active canonical/workflow-language roots, the resolved target path role, any out-of-band justification, the insight integration audit, and the table-semantics audit in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language paper-layer path in the latest write iteration, and only then edit the final manuscript in the chosen language.

package/package-assets/codex/prompts/lab:write.md

@@ -8,6 +8,6 @@ Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
 Execute the requested `/lab:write` stage against the user's argument now. Do not only recommend another lab stage. If a blocking prerequisite is missing, say exactly what is missing and ask at most one clarifying question.
 When the user provides reference PDFs, paper URLs, local reference-paper paths, or asks to write by reference, stay within the write stage and switch to reference-guided deep-write. Extract structure, map section/subsection slots, paragraph roles, table/figure roles, and bridge logic to the current paper, record the consumption plan, and only then draft prose. The current section must visibly realize the mapped slots; do not treat a consumption plan as enough. Reuse structure only; do not copy wording, claims, metrics, captions, or conclusions. Keep service-style or AI-assistant meta language and workflow-only placeholder language out of paper-facing prose.
 When Method, Experiments, captions, tables, or analysis assets introduce or revise reported metrics, create or update `.lab/writing/metric-glossary.md` before prose polish. Each metric must define its paper-facing name, approved short name, table/header label, plain-language definition, calculation, unit or denominator, direction, scope or conditions, allowed aliases, forbidden aliases, and first-use location. Use the same metric names across prose, captions, table notes, table headers, and result summaries. Run `validate_metric_glossary.py` and remove forbidden aliases from reader-facing LaTeX before finalizing the round.
-Chinese workflow-language terminology: when `workflow_language=zh`, concept terms should use a Chinese paper-facing name and a Chinese short form by default. English full form plus acronym may appear at first mention only as `中文全称（English full form, ACRONYM）`, then prose should reuse the Chinese short form. Prefer natural compact Chinese short forms; two-character, three-character, four-character, or longer short phrases are all acceptable when they read naturally. Do not force a fixed-length abbreviation. Avoid repeating English concept fragments throughout Chinese prose. Run `validate_workflow_language_text.py` on touched Chinese workflow-language sections, tables, figures, and analysis assets before completing the write round.
-For Chinese workflow-language output, run `validate_workflow_language_text.py` over the touched workflow-language sections, tables, figures, and analysis assets before completing the write round. If it reports English concept fragments, translate them or define a justified glossary exception before prose polish.
+Chinese workflow-language terminology: when `workflow_language=zh`, concept terms should use a Chinese paper-facing name and a Chinese short form by default. English full form plus acronym may appear at first mention only as `中文全称（English full form, ACRONYM）`, then prose should reuse the Chinese short form. Prefer natural compact Chinese short forms; two-character, three-character, four-character, or longer short phrases are all acceptable when they read naturally. Do not force a fixed-length abbreviation. Avoid repeating English concept fragments throughout Chinese prose. Before completing the write round, run `validate_paper_layer.py` on the resolved active Chinese paper layer so the whole layer is checked rather than only the touched file. Use `validate_workflow_language_text.py` as a local repair helper when narrowing down specific offending files.
+For Chinese workflow-language output, run `validate_paper_layer.py` on the resolved active paper layer before completing the write round so the whole layer is checked instead of only the touched file. Use `validate_workflow_language_text.py` as a local repair helper when narrowing down specific offending files. If the layer validator reports English concept fragments or English paper-facing headings/captions, translate them or define a justified glossary exception before prose polish.
 This command runs the `/lab:write` stage. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Carry the same core insight anchor through the paper: Introduction creates the cognitive contrast, Method turns the insight into design motivation, Experiments diagnose it with evidence, and Conclusion states the broader principle and boundary. Do not create a standalone `Our Insights` section just to satisfy this; weave the insight into motivation, mechanism, evidence, and limitations. Read the matching paper-writing reference, the current section block in `section-style-policies.md`, and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. When `workflow_language` and `paper_language` differ, treat the workflow-language paper layer as the default ordinary working layer. Resolve the active paper topology from `.lab/config/workflow.json` before drafting: the active canonical root is `<deliverables_root>/paper/`, and when workflow-language is active its root is `<deliverables_root>/paper/workflow-language/`. Ordinary write rounds should still edit one target paper layer at a time rather than silently refreshing both language layers. If the user names a concrete file or layer, treat that as the only target for the round unless they also explicitly request synchronization. Classify the named target path before editing it. Only active-layer targets count as managed manuscript rounds; legacy side layers such as `review_zh`, `translation_zh`, `sections_zh`, or stale `deliverables/.../workflow-language/*.md` paths are out-of-band/legacy edits and must not silently replace the active paper topology. If a workflow-language paper layer is active and the round still targets the canonical manuscript, record why canonical-only writing was acceptable in the write iteration artifact. If `paper_language_finalization_decision=convert-to-paper-language`, explicit canonical-manuscript work may target the canonical `paper_language` manuscript, but that does not make canonical the default ordinary working layer while workflow-language remains active. Treat the workflow-language paper layer as a real persisted artifact rather than a review layer, and preserve it as a full LaTeX mirror with `workflow-language/main.tex`, `workflow-language/references.bib`, `workflow-language/sections/*.tex`, `workflow-language/tables/*.tex`, `workflow-language/figures/*.tex`, and `workflow-language/analysis/analysis-asset.tex`. Do not write new workflow-language output to deprecated review-layer paths such as `docs/lab/paper/review_zh/`. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, do not use labels containing `_` or `-` in reader-facing prose, apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels, do not assume a fixed drafting order such as Method before Experiments, add a local naming bridge when a section uses canonical short names before their defining section has been drafted, and reuse the canonical label instead of replacing it with a narrative alias. Follow the current section's encouraged, discouraged, and banned expression lists from `section-style-policies.md`; section-specific banned expressions take priority over prose-polish goals. Before any additional tighten, compress, or polish pass on the same section, run a section-level acceptance gate first. That gate must explicitly confirm naming consistency, adjacent-section consistency, claim, metric, and ranking consistency with the current evidence, local clarity, local concision, and section-style compliance. If the round changes the paper's canonical experiment or evaluation protocol, treat that change as a canonical replacement unless the user explicitly scoped it as supplementary or appendix-only, run a paper-wide impact audit before more polishing, update the highest-impact stale sections and assets first, and do not default to translation/workflow-layer sync work unless the user explicitly asked for it or the language-finalization workflow requires it. Only edit both the canonical manuscript and the workflow-language paper layer in the same round when the user explicitly asks for cross-language synchronization or when a final-draft/export language-finalization step requires both layers to be refreshed together. Do not treat a routine tighten/compress/polish request as an instruction to sync the workflow-language companion. For export or remote-publication rounds, if `paper_language_finalization_decision=convert-to-paper-language`, include the workflow-language paper layer in the exported or pushed bundle by default. Allow canonical-only export or remote publication only when the user explicitly asked for it or when the remote target forbids extra files. If any gate item is unresolved, or if a banned expression or move from the current section policy remains, spend the round fixing that blocker instead of polishing sentences further, and do not default the next-step recommendation to another polish pass. Main tables must be locally self-contained: the title, header, note, and adjacent prose should tell the reader what each row and column means, the metric direction, and any relevant unit, denominator, or event condition. Short headers remain allowed, but abbreviations in paper-facing tables must be expanded locally in the same table. If Method or Experiments prose promises a metric family, the main table set must either expose those metrics directly or explicitly mark the missing ones as appendix-only and explain why. If a metric is measured but omitted because it is zero everywhere, redundant, or appendix-only, state that disposition explicitly in the table note instead of silently dropping it. Do not treat `\resizebox{\linewidth}{!}{...}` as the default way to fit a main table. Fit main tables by redesign first: shorten headers, move secondary metrics out of the main table, reduce or split columns, then adjust `\tabcolsep` conservatively; only use `\resizebox` as a last resort, keep width changes readable, and explain the width-control rationale locally in the same table note. Do not use `\scriptsize` or `\tiny` as the default main-table fit strategy. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check, the section-level acceptance gate, section-style policy compliance, the protocol/scope impact audit, the export or remote bundle audit, the round target layer, any canonical-only justification while workflow-language was active, any cross-language sync justification, the active canonical/workflow-language roots, the resolved target path role, any out-of-band justification, the insight integration audit, and the table-semantics audit in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language paper-layer path in the latest write iteration, and only then edit the final manuscript in the chosen language.

package/package-assets/codex/prompts/lab/357/274/232write.md

@@ -8,6 +8,6 @@ Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
 Execute the requested `/lab:write` stage against the user's argument now. Do not only recommend another lab stage. If a blocking prerequisite is missing, say exactly what is missing and ask at most one clarifying question.
 When the user provides reference PDFs, paper URLs, local reference-paper paths, or asks to write by reference, stay within the write stage and switch to reference-guided deep-write. Extract structure, map section/subsection slots, paragraph roles, table/figure roles, and bridge logic to the current paper, record the consumption plan, and only then draft prose. The current section must visibly realize the mapped slots; do not treat a consumption plan as enough. Reuse structure only; do not copy wording, claims, metrics, captions, or conclusions. Keep service-style or AI-assistant meta language and workflow-only placeholder language out of paper-facing prose.
 When Method, Experiments, captions, tables, or analysis assets introduce or revise reported metrics, create or update `.lab/writing/metric-glossary.md` before prose polish. Each metric must define its paper-facing name, approved short name, table/header label, plain-language definition, calculation, unit or denominator, direction, scope or conditions, allowed aliases, forbidden aliases, and first-use location. Use the same metric names across prose, captions, table notes, table headers, and result summaries. Run `validate_metric_glossary.py` and remove forbidden aliases from reader-facing LaTeX before finalizing the round.
-Chinese workflow-language terminology: when `workflow_language=zh`, concept terms should use a Chinese paper-facing name and a Chinese short form by default. English full form plus acronym may appear at first mention only as `中文全称（English full form, ACRONYM）`, then prose should reuse the Chinese short form. Prefer natural compact Chinese short forms; two-character, three-character, four-character, or longer short phrases are all acceptable when they read naturally. Do not force a fixed-length abbreviation. Avoid repeating English concept fragments throughout Chinese prose. Run `validate_workflow_language_text.py` on touched Chinese workflow-language sections, tables, figures, and analysis assets before completing the write round.
-For Chinese workflow-language output, run `validate_workflow_language_text.py` over the touched workflow-language sections, tables, figures, and analysis assets before completing the write round. If it reports English concept fragments, translate them or define a justified glossary exception before prose polish.
+Chinese workflow-language terminology: when `workflow_language=zh`, concept terms should use a Chinese paper-facing name and a Chinese short form by default. English full form plus acronym may appear at first mention only as `中文全称（English full form, ACRONYM）`, then prose should reuse the Chinese short form. Prefer natural compact Chinese short forms; two-character, three-character, four-character, or longer short phrases are all acceptable when they read naturally. Do not force a fixed-length abbreviation. Avoid repeating English concept fragments throughout Chinese prose. Before completing the write round, run `validate_paper_layer.py` on the resolved active Chinese paper layer so the whole layer is checked rather than only the touched file. Use `validate_workflow_language_text.py` as a local repair helper when narrowing down specific offending files.
+For Chinese workflow-language output, run `validate_paper_layer.py` on the resolved active paper layer before completing the write round so the whole layer is checked instead of only the touched file. Use `validate_workflow_language_text.py` as a local repair helper when narrowing down specific offending files. If the layer validator reports English concept fragments or English paper-facing headings/captions, translate them or define a justified glossary exception before prose polish.
 This command runs the `/lab:write` stage. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Carry the same core insight anchor through the paper: Introduction creates the cognitive contrast, Method turns the insight into design motivation, Experiments diagnose it with evidence, and Conclusion states the broader principle and boundary. Do not create a standalone `Our Insights` section just to satisfy this; weave the insight into motivation, mechanism, evidence, and limitations. Read the matching paper-writing reference, the current section block in `section-style-policies.md`, and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. When `workflow_language` and `paper_language` differ, treat the workflow-language paper layer as the default ordinary working layer. Resolve the active paper topology from `.lab/config/workflow.json` before drafting: the active canonical root is `<deliverables_root>/paper/`, and when workflow-language is active its root is `<deliverables_root>/paper/workflow-language/`. Ordinary write rounds should still edit one target paper layer at a time rather than silently refreshing both language layers. If the user names a concrete file or layer, treat that as the only target for the round unless they also explicitly request synchronization. Classify the named target path before editing it. Only active-layer targets count as managed manuscript rounds; legacy side layers such as `review_zh`, `translation_zh`, `sections_zh`, or stale `deliverables/.../workflow-language/*.md` paths are out-of-band/legacy edits and must not silently replace the active paper topology. If a workflow-language paper layer is active and the round still targets the canonical manuscript, record why canonical-only writing was acceptable in the write iteration artifact. If `paper_language_finalization_decision=convert-to-paper-language`, explicit canonical-manuscript work may target the canonical `paper_language` manuscript, but that does not make canonical the default ordinary working layer while workflow-language remains active. Treat the workflow-language paper layer as a real persisted artifact rather than a review layer, and preserve it as a full LaTeX mirror with `workflow-language/main.tex`, `workflow-language/references.bib`, `workflow-language/sections/*.tex`, `workflow-language/tables/*.tex`, `workflow-language/figures/*.tex`, and `workflow-language/analysis/analysis-asset.tex`. Do not write new workflow-language output to deprecated review-layer paths such as `docs/lab/paper/review_zh/`. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, do not use labels containing `_` or `-` in reader-facing prose, apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels, do not assume a fixed drafting order such as Method before Experiments, add a local naming bridge when a section uses canonical short names before their defining section has been drafted, and reuse the canonical label instead of replacing it with a narrative alias. Follow the current section's encouraged, discouraged, and banned expression lists from `section-style-policies.md`; section-specific banned expressions take priority over prose-polish goals. Before any additional tighten, compress, or polish pass on the same section, run a section-level acceptance gate first. That gate must explicitly confirm naming consistency, adjacent-section consistency, claim, metric, and ranking consistency with the current evidence, local clarity, local concision, and section-style compliance. If the round changes the paper's canonical experiment or evaluation protocol, treat that change as a canonical replacement unless the user explicitly scoped it as supplementary or appendix-only, run a paper-wide impact audit before more polishing, update the highest-impact stale sections and assets first, and do not default to translation/workflow-layer sync work unless the user explicitly asked for it or the language-finalization workflow requires it. Only edit both the canonical manuscript and the workflow-language paper layer in the same round when the user explicitly asks for cross-language synchronization or when a final-draft/export language-finalization step requires both layers to be refreshed together. Do not treat a routine tighten/compress/polish request as an instruction to sync the workflow-language companion. For export or remote-publication rounds, if `paper_language_finalization_decision=convert-to-paper-language`, include the workflow-language paper layer in the exported or pushed bundle by default. Allow canonical-only export or remote publication only when the user explicitly asked for it or when the remote target forbids extra files. If any gate item is unresolved, or if a banned expression or move from the current section policy remains, spend the round fixing that blocker instead of polishing sentences further, and do not default the next-step recommendation to another polish pass. Main tables must be locally self-contained: the title, header, note, and adjacent prose should tell the reader what each row and column means, the metric direction, and any relevant unit, denominator, or event condition. Short headers remain allowed, but abbreviations in paper-facing tables must be expanded locally in the same table. If Method or Experiments prose promises a metric family, the main table set must either expose those metrics directly or explicitly mark the missing ones as appendix-only and explain why. If a metric is measured but omitted because it is zero everywhere, redundant, or appendix-only, state that disposition explicitly in the table note instead of silently dropping it. Do not treat `\resizebox{\linewidth}{!}{...}` as the default way to fit a main table. Fit main tables by redesign first: shorten headers, move secondary metrics out of the main table, reduce or split columns, then adjust `\tabcolsep` conservatively; only use `\resizebox` as a last resort, keep width changes readable, and explain the width-control rationale locally in the same table note. Do not use `\scriptsize` or `\tiny` as the default main-table fit strategy. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check, the section-level acceptance gate, section-style policy compliance, the protocol/scope impact audit, the export or remote bundle audit, the round target layer, any canonical-only justification while workflow-language was active, any cross-language sync justification, the active canonical/workflow-language roots, the resolved target path role, any out-of-band justification, the insight integration audit, and the table-semantics audit in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language paper-layer path in the latest write iteration, and only then edit the final manuscript in the chosen language.

package/package-assets/shared/lab/.managed/scripts/validate_paper_layer.py

@@ -0,0 +1,237 @@
+#!/usr/bin/env python3
+from __future__ import annotations
+
+import argparse
+import re
+import sys
+from pathlib import Path
+
+from paper_topology import find_project_root, resolve_paper_topology
+from validate_manuscript_delivery import (
+    REQUIRED_FIGURE_FILES,
+    REQUIRED_TABLE_FILES,
+    check_analysis_asset,
+    check_asset_consumption,
+    check_bibliography,
+    check_experiments_section,
+    check_figure_file,
+    check_global_tex,
+    check_introduction_section,
+    check_language_layers,
+    check_latest_write_iteration_preflight,
+    check_main_tex,
+    check_method_section,
+    check_table_file,
+)
+from validate_paper_topology import validate_topology_artifacts
+from validate_workflow_language_text import load_allowed_fragments, validate_files
+
+
+INPUT_RE = re.compile(r"\\(?:input|include|wlpath)\{([^}]+)\}")
+REF_RE = re.compile(r"\\(?:auto|c|C)?ref\{([^}]+)\}|\\(?:eqref|pageref)\{([^}]+)\}")
+CITE_RE = re.compile(r"\\(?:cite|citep|citet)\*?(?:\[[^\]]*\])?\{([^}]+)\}")
+LABEL_RE = re.compile(r"\\label\{([^}]+)\}")
+BIB_KEY_RE = re.compile(r"@\w+\{([^,\s]+),")
+
+
+def parse_args() -> argparse.Namespace:
+    parser = argparse.ArgumentParser(
+        description="Validate the active paper layer as a whole instead of checking only one section file."
+    )
+    parser.add_argument("--project-root", required=True, help="Project root containing .lab/config/workflow.json")
+    parser.add_argument(
+        "--layer",
+        default="active",
+        choices=("active", "canonical", "workflow-language"),
+        help="Which paper layer to validate",
+    )
+    parser.add_argument("--mode", required=True, choices=("draft", "final", "export"))
+    return parser.parse_args()
+
+
+def read_text(path: Path) -> str:
+    return path.read_text(encoding="utf-8")
+
+
+def strip_comments(text: str) -> str:
+    return re.sub(r"(?<!\\)%.*", "", text)
+
+
+def resolve_target_layer(project_root: Path, layer: str) -> tuple[str, Path | None, str | None]:
+    topology = resolve_paper_topology(project_root)
+    workflow_config_path = project_root / ".lab" / "config" / "workflow.json"
+    workflow_config = {}
+    if workflow_config_path.exists():
+        import json
+
+        workflow_config = json.loads(workflow_config_path.read_text(encoding="utf-8"))
+
+    if layer == "workflow-language":
+        return "workflow-language", topology["workflow_root"], workflow_config.get("workflow_language")
+    if layer == "canonical":
+        return "canonical", topology["canonical_root"], workflow_config.get("paper_language") or workflow_config.get("workflow_language")
+    if topology["workflow_language_active"] and topology["workflow_root"] is not None:
+        return "workflow-language", topology["workflow_root"], workflow_config.get("workflow_language")
+    return "canonical", topology["canonical_root"], workflow_config.get("paper_language") or workflow_config.get("workflow_language")
+
+
+def collect_tex_files(layer_root: Path) -> list[Path]:
+    return sorted(path for path in layer_root.rglob("*.tex") if path.is_file())
+
+
+def resolve_input_target(source_file: Path, layer_root: Path, raw_target: str) -> Path | None:
+    target = raw_target.strip()
+    if not target:
+        return None
+    candidates: list[Path] = []
+    target_path = Path(target)
+    if target_path.is_absolute():
+        candidates.append(target_path)
+    else:
+        paths_to_try = [target_path]
+        if target_path.suffix == "":
+            paths_to_try.append(target_path.with_suffix(".tex"))
+        for candidate in paths_to_try:
+            candidates.append((source_file.parent / candidate).resolve())
+            candidates.append((layer_root / candidate).resolve())
+    for candidate in candidates:
+        if candidate.exists():
+            return candidate
+    return candidates[0] if candidates else None
+
+
+def parse_bibliography_keys(layer_root: Path) -> set[str]:
+    keys: set[str] = set()
+    for bib_path in sorted(layer_root.glob("*.bib")):
+        text = read_text(bib_path)
+        for match in BIB_KEY_RE.finditer(text):
+            keys.add(match.group(1).strip())
+    return keys
+
+
+def validate_latex_graph(layer_root: Path, tex_files: list[Path]) -> list[str]:
+    issues: list[str] = []
+    main_tex = layer_root / "main.tex"
+    if not main_tex.exists():
+        issues.append(f"{layer_root}: missing main.tex for paper-layer validation")
+    if not tex_files:
+        issues.append(f"{layer_root}: no .tex files found in the target paper layer")
+        return issues
+
+    labels: dict[str, Path] = {}
+    refs: list[tuple[Path, str]] = []
+    cites: list[tuple[Path, str]] = []
+
+    for tex_path in tex_files:
+        text = strip_comments(read_text(tex_path))
+        for match in INPUT_RE.finditer(text):
+            target = resolve_input_target(tex_path, layer_root, match.group(1))
+            if target is None or not target.exists():
+                issues.append(
+                    f"{tex_path}: missing LaTeX include target `{match.group(1)}` inside the active paper layer"
+                )
+        for match in LABEL_RE.finditer(text):
+            label = match.group(1).strip()
+            if not label:
+                continue
+            if label in labels and labels[label] != tex_path:
+                issues.append(
+                    f"duplicate LaTeX label `{label}` appears in both {labels[label]} and {tex_path}"
+                )
+            labels[label] = tex_path
+        for match in REF_RE.finditer(text):
+            label = next(group for group in match.groups() if group)
+            refs.append((tex_path, label.strip()))
+        for match in CITE_RE.finditer(text):
+            for key in match.group(1).split(","):
+                normalized = key.strip()
+                if normalized:
+                    cites.append((tex_path, normalized))
+
+    for tex_path, label in refs:
+        if label not in labels:
+            issues.append(f"{tex_path}: unresolved LaTeX reference `{label}` in the active paper layer")
+
+    bibliography_keys = parse_bibliography_keys(layer_root)
+    if cites and not bibliography_keys:
+        issues.append(f"{layer_root}: citations are present but no bibliography keys were found in the paper layer")
+    for tex_path, key in cites:
+        if bibliography_keys and key not in bibliography_keys:
+            issues.append(f"{tex_path}: unresolved bibliography key `{key}` in the active paper layer")
+
+    return issues
+
+
+def validate_manuscript_delivery_layer(layer_root: Path) -> list[str]:
+    issues: list[str] = []
+    check_main_tex(layer_root, issues)
+    check_bibliography(layer_root, issues)
+    check_global_tex(layer_root, issues)
+    check_introduction_section(layer_root, issues)
+    check_method_section(layer_root, issues)
+    check_experiments_section(layer_root, issues)
+    check_asset_consumption(layer_root, issues)
+    check_language_layers(layer_root, issues)
+    check_latest_write_iteration_preflight(layer_root, issues)
+
+    tables_dir = layer_root / "tables"
+    check_table_file(tables_dir / REQUIRED_TABLE_FILES[0], issues, "tables/main-results.tex")
+    check_table_file(tables_dir / REQUIRED_TABLE_FILES[1], issues, "tables/ablations.tex")
+
+    figures_dir = layer_root / "figures"
+    check_figure_file(figures_dir / REQUIRED_FIGURE_FILES[0], issues, "figures/problem-setting.tex")
+    check_figure_file(figures_dir / REQUIRED_FIGURE_FILES[1], issues, "figures/method-overview.tex")
+    check_figure_file(figures_dir / REQUIRED_FIGURE_FILES[2], issues, "figures/results-overview.tex")
+
+    analysis_dir = layer_root / "analysis"
+    check_analysis_asset(analysis_dir / "analysis-asset.tex", issues)
+    return issues
+
+
+def validate_layer(project_root: Path, layer: str, mode: str) -> tuple[list[str], str, Path | None]:
+    issues: list[str] = []
+    resolved_layer, layer_root, layer_language = resolve_target_layer(project_root, layer)
+    if layer_root is None:
+        issues.append("workflow-language paper layer is not active for this project")
+        return issues, resolved_layer, layer_root
+    if not layer_root.exists():
+        issues.append(f"paper layer does not exist: {layer_root}")
+        return issues, resolved_layer, layer_root
+
+    issues.extend(validate_topology_artifacts(project_root))
+
+    tex_files = collect_tex_files(layer_root)
+    issues.extend(validate_latex_graph(layer_root, tex_files))
+
+    if layer_language == "zh":
+        glossary_path = project_root / ".lab" / "writing" / "terminology-glossary.md"
+        allowed = load_allowed_fragments(str(glossary_path) if glossary_path.exists() else None, [])
+        issues.extend(validate_files([str(path) for path in tex_files], allowed))
+
+    if mode in {"final", "export"}:
+        issues.extend(validate_manuscript_delivery_layer(layer_root))
+
+    return issues, resolved_layer, layer_root
+
+
+def main() -> int:
+    args = parse_args()
+    project_root = find_project_root(Path(args.project_root).resolve())
+    if project_root is None:
+        print("could not find .lab/config/workflow.json for project root", file=sys.stderr)
+        return 1
+
+    issues, resolved_layer, layer_root = validate_layer(project_root, args.layer, args.mode)
+    if issues:
+        for issue in issues:
+            print(issue, file=sys.stderr)
+        return 1
+
+    print(
+        f"paper layer is valid: {resolved_layer} -> {layer_root}"
+    )
+    return 0
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())

package/package-assets/shared/lab/.managed/scripts/validate_workflow_language_text.py

@@ -17,6 +17,9 @@ ENGLISH_FRAGMENT_RE = re.compile(
     r"(?:[ \t]+[A-Za-z][A-Za-z0-9+]*(?:-[A-Za-z][A-Za-z0-9+]*)*)*)(?![A-Za-z0-9_])"
 )
 FIELD_RE = re.compile(r"^[ \t]*-[ \t]*([^:：]+)[:：][ \t]*([^\n]*)[ \t]*$", flags=re.MULTILINE)
+PAPER_FACING_COMMAND_RE = re.compile(
+    r"\\(?:section|subsection|subsubsection|paragraph|subparagraph|caption)\*?\{([^}]*)\}"
+)
 
 
 DEFAULT_ALLOWED_FRAGMENTS = {
@@ -146,6 +149,22 @@ def should_ignore_candidate(candidate: str, allowed: set[str]) -> bool:
     return False
 
 
+def should_ignore_heading_candidate(candidate: str, allowed: set[str]) -> bool:
+    normalized = normalize_fragment(candidate)
+    if not normalized:
+        return True
+    if normalized in allowed or normalized.replace(" ", "") in allowed:
+        return True
+    tokens = re.findall(r"[A-Za-z][A-Za-z0-9+]*", candidate)
+    if not tokens:
+        return True
+    if all(token.lower() in allowed for token in tokens):
+        return True
+    if len(tokens) == 1 and re.fullmatch(r"[A-Z0-9+\-]{2,}", tokens[0]):
+        return True
+    return False
+
+
 def find_mixed_fragments(text: str, allowed: set[str]) -> list[tuple[int, str]]:
     issues: list[tuple[int, str]] = []
     stripped = strip_latex_noise(remove_first_mention_parentheticals(text))
@@ -167,6 +186,30 @@ def find_mixed_fragments(text: str, allowed: set[str]) -> list[tuple[int, str]]:
     return issues
 
 
+def strip_inline_latex_markup(text: str) -> str:
+    text = re.sub(r"\\[A-Za-z@*]+(?:\[[^\]]*\])?", " ", text)
+    text = text.replace("{", " ").replace("}", " ")
+    return re.sub(r"\s+", " ", text).strip()
+
+
+def find_heading_english_fragments(text: str, allowed: set[str]) -> list[tuple[int, str]]:
+    issues: list[tuple[int, str]] = []
+    for line_no, line in enumerate(text.splitlines(), start=1):
+        seen_on_line: set[str] = set()
+        for match in PAPER_FACING_COMMAND_RE.finditer(line):
+            candidate = strip_inline_latex_markup(match.group(1))
+            if not candidate or CJK_RE.search(candidate) or not re.search(r"[A-Za-z]", candidate):
+                continue
+            normalized = normalize_fragment(candidate)
+            if normalized in seen_on_line:
+                continue
+            seen_on_line.add(normalized)
+            if should_ignore_heading_candidate(candidate, allowed):
+                continue
+            issues.append((line_no, candidate))
+    return issues
+
+
 def validate_files(files: list[str], allowed: set[str]) -> list[str]:
     issues: list[str] = []
     for file_name in files:
@@ -185,6 +228,10 @@ def validate_files(files: list[str], allowed: set[str]) -> list[str]:
             issues.append(
                 f"{path}:{line_no}: English concept fragment '{fragment}' appears in Chinese workflow-language prose; translate it, define it once as a first mention, or add a justified glossary exception"
             )
+        for line_no, fragment in find_heading_english_fragments(text, allowed):
+            issues.append(
+                f"{path}:{line_no}: English paper-facing heading or caption '{fragment}' appears in Chinese workflow-language LaTeX; translate it, define it once locally, or add a justified glossary exception"
+            )
     return issues
 
 

package/package-assets/shared/lab/.managed/templates/rebuttal-panel.md

@@ -22,9 +22,15 @@
 
 ## External Rebuttal Intake
 
-| Source | Raw criticism summary | Affected unit | Reviewer axis | Severity | Route | Acceptance check |
-| --- | --- | --- | --- | --- | --- | --- |
-|  |  |  |  |  |  |  |
+| Source | Raw criticism summary | Affected unit | Reviewer axis | Severity | Why it matters | Route | Acceptance check |
+| --- | --- | --- | --- | --- | --- | --- | --- |
+|  |  |  |  |  |  |  |  |
+
+## Revision Traceability
+
+| Author claim or revised statement | Claimed artifact location | Independently verified | Remaining gap |
+| --- | --- | --- | --- |
+|  |  |  |  |
 
 ## Reviewer Panel Findings
 
@@ -70,9 +76,15 @@
 
 ## Actionable Issue Register
 
-| ID | Axis | Severity | Affected artifact | Finding | Required fix | Route | Acceptance check | Core mutation required |
-| --- | --- | --- | --- | --- | --- | --- | --- | --- |
-|  |  |  |  |  |  |  |  |  |
+| ID | Axis | Severity | Affected artifact | Finding | Why it matters | Required fix | Route | Acceptance check | Core mutation required |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
+|  |  |  |  |  |  |  |  |  |  |
+
+## Consensus / Disagreement / Resolution
+
+- Consensus:
+- Disagreement:
+- Resolution:
 
 ## Core Mutation Check
 

package/package-assets/shared/skills/lab/SKILL.md

@@ -314,7 +314,7 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 - Keep terminology stable across rounds and sections.
 - Maintain `.lab/writing/terminology-glossary.md` as the write-stage source for full forms, approved short forms, reader-facing explanations, allowed aliases, and terms that should stay out of prose.
 - When `workflow_language=zh`, use Chinese workflow-language terminology: concept terms need a Chinese paper-facing name and Chinese short form by default; English full form plus acronym may appear only at first mention, then prose should reuse the Chinese short form. Prefer natural compact Chinese short forms; two-character, three-character, four-character, or longer short phrases are all acceptable when they read naturally.
-- When completing Chinese workflow-language output, run `validate_workflow_language_text.py` on touched sections, tables, figures, and analysis assets before claiming the round is accepted; unresolved English concept fragments are blockers for final/export write rounds.
+- When completing Chinese workflow-language output, run `validate_paper_layer.py` on the resolved active paper layer before claiming the round is accepted; use `validate_workflow_language_text.py` only as a local repair helper when the layer validator identifies specific offending files.
 - Maintain `.lab/writing/metric-glossary.md` as the write-stage source for reported metric names, definitions, calculations, denominators, directions, scopes, and aliases.
 - When a round introduces or revises key terms, include a compact terminology note in the user-facing write summary and record the terminology-clarity self-check in the latest write iteration artifact.
 - When a round introduces or revises metrics, include a compact metric-glossary note in the user-facing write summary and record the metric-glossary validation in the latest write iteration artifact.

package/package-assets/shared/skills/lab/references/paper-writing/argument-stress-test.md

@@ -0,0 +1,34 @@
+# Argument Stress Test
+
+Run this after the logic pass and before language polish. The goal is to break weak argument chains early.
+
+## Required Checks
+
+1. **Weakest-link test**  
+   Which paragraph carries the most unsupported inference? Rewrite or narrow it first.
+
+2. **Reverse-claim test**  
+   If the main claim were false, which sentence in this section would fail first? That sentence usually reveals the overclaim.
+
+3. **Alternative-explanation test**  
+   What simpler explanation could produce the same pattern? State it explicitly and check whether the section already weakens it.
+
+4. **Boundary test**  
+   What does the current evidence still not justify? Add that limit before polishing.
+
+5. **Evidence-trace test**  
+   Can every major claim be traced to a figure, table, protocol statement, citation, or definition already present?
+
+## Section-Specific Triggers
+
+- **Introduction**: would the paper still look necessary if the claimed challenge were softened?
+- **Method**: could a reviewer say the module is an arbitrary stack choice?
+- **Experiments**: does the prose explain what the result teaches, not only what number is larger?
+- **Conclusion**: does any sentence exceed what the experiments actually support?
+
+## Repair Moves
+
+1. Replace vague claims with a narrower mechanism claim.
+2. Add one explicit bridge sentence from evidence to interpretation.
+3. Move unsupported motivation out of results and back into hypothesis language.
+4. State the remaining alternative explanation if it is not fully ruled out.

package/package-assets/shared/skills/lab/references/paper-writing/section-question-bank.md

@@ -0,0 +1,59 @@
+# Section Question Bank
+
+Use this file before drafting or revising a paper section. The goal is to force one pass on section purpose before wording.
+
+## Global Questions
+
+1. What single job must this section do for the paper?
+2. What must the reader understand after this section that they did not understand before?
+3. Which claim, protocol, metric, or boundary does this section depend on?
+4. Which paragraph is most likely to confuse a skeptical reviewer?
+5. Which sentence would become false if one supporting result disappeared?
+
+## Abstract
+
+1. Is the task clear in one pass?
+2. Is the gap tied to prior work rather than hype?
+3. Is the mechanism-level insight visible?
+4. Is the main result bounded by scope?
+5. Is the main boundary stated?
+
+## Introduction
+
+1. What common assumption or prior explanation is being challenged?
+2. What failure, anomaly, or unmet need forces the paper to exist?
+3. What is the core insight anchor?
+4. Why does the proposed direction follow from that insight?
+5. Which contribution is truly central, and which are supporting?
+
+## Related Work
+
+1. What are the 2-4 actual research clusters readers need?
+2. Which paper is the closest prior work?
+3. What exact capability remains unresolved in each cluster?
+4. Does each cluster end with a gap statement?
+5. Did any paragraph become a citation list instead of a comparison?
+
+## Method
+
+1. Which design choice would a reviewer call arbitrary?
+2. What problem forces each module, loss, or representation?
+3. Is the information flow described in executable order?
+4. What technical effect is expected from each major design?
+5. Which term or label still lacks a first-mention explanation?
+
+## Experiments
+
+1. Are dataset scope, split protocol, and baseline setup separately visible?
+2. Is each metric defined once in reader-facing language?
+3. Which table answers the main effectiveness question?
+4. Which ablation rules out the strongest simpler explanation?
+5. What boundary or failure mode remains after the main result?
+
+## Conclusion
+
+1. What is the strongest supported takeaway?
+2. What broader principle follows from that takeaway?
+3. What boundary prevents overclaiming?
+4. What next step follows from the boundary instead of from habit?
+5. Did the section introduce any new evidence or claim?

package/package-assets/shared/skills/lab/references/paper-writing/writing-anti-patterns.md

@@ -0,0 +1,33 @@
+# Writing Anti-Patterns
+
+Run this only after logic and theory blockers are cleared. The goal is to remove common low-quality prose habits without inventing new content.
+
+## Common Anti-Patterns
+
+1. **Throat-clearing openings**  
+   Paragraphs that spend one or two sentences warming up before making the point. Move the point to the first sentence.
+
+2. **Uniform paragraph length**  
+   Every paragraph having the same size often signals template writing rather than argument structure. Split or merge by idea, not by rhythm.
+
+3. **Synonym cycling**  
+   Switching among multiple names for the same concept creates false variety and weakens terminology control. Keep one canonical paper-facing name.
+
+4. **Generic evaluative vocabulary**  
+   Words such as `important`, `significant`, `effective`, `clear`, or `promising` without concrete content. Replace with the specific consequence, metric, or boundary.
+
+5. **List-shaped filler**  
+   Sentences that pile up three or more loosely related claims to sound complete. Split them into one claim per sentence when the logic differs.
+
+6. **Overconnected transitions**  
+   Repeated `therefore`, `moreover`, `furthermore`, or similar connectors can hide weak logic. Keep the connective only when the relation is explicit.
+
+7. **Meta-writer commentary**  
+   Phrases about what the paper is doing rather than the research itself, unless the sentence is a legitimate roadmap or scope statement.
+
+## Quick Repair Questions
+
+1. Can the first sentence of each paragraph state the paragraph's job directly?
+2. Did any concept get renamed just to avoid repetition?
+3. Can a vague adjective be replaced by a metric, mechanism, or constraint?
+4. Did any sentence become longer because two different ideas were forced together?

package/package-assets/shared/skills/lab/references/rebuttal-mode.md

@@ -56,11 +56,23 @@ For each external comment, record:
 - affected paper unit: claim, section, table, figure, protocol, metric, threat model, experiment, or wording
 - reviewer axis: R1, R2, R3, R4, or R5
 - severity: fatal, major, minor, or clarification
+- why it matters: what acceptance risk or scientific risk it creates
 - route: `write`, `iterate`, `report`, `framing`, `data`, `spec`, or `ask-user`
 - acceptance check: concrete evidence or manuscript condition that resolves the issue
 
 Do not answer external criticism with prose-only reassurance. If the issue is valid, it must become a repair task. If it is invalid, state the evidence that rules it out.
 
+## Revision Traceability
+
+When the paper already contains a claimed repair, rebuttal response, or revised section, record:
+
+- author claim: what the current draft or response says was fixed
+- claimed artifact location: where the claimed fix lives
+- independently verified: yes / no / partial
+- remaining gap: what still fails the acceptance check
+
+Do not mark an issue resolved only because the manuscript says it was resolved. The pass must independently verify the fix or keep the remaining gap open.
+
 ## Reviewer Panel
 
 Run five independent review lenses. Each lens must produce actionable issues, not vague advice.
@@ -112,6 +124,16 @@ Every issue must include:
 
 Prioritize fatal and major issues before language polish. Minor presentation fixes may be batched.
 
+## Consensus / Disagreement / Resolution
+
+At the end of the panel, summarize:
+
+- consensus: what multiple review lenses agree is the main blocking problem
+- disagreement: what remains contested across lenses or between criticism and evidence
+- resolution: what concrete route, evidence, or rewrite will settle the disagreement
+
+Use this summary to keep rebuttal mode actionable instead of devolving into parallel opinions.
+
 ## Core Mutation Policy
 
 Core mutation means changing any of:

package/package-assets/shared/skills/lab/stages/review.md

@@ -5,9 +5,11 @@
 1. Give a concise summary of the artifact or result under review.
 2. State the top review question or risk focus.
 3. Audit in reviewer mode.
-4. Output fatal flaws first when present.
-5. Rank the fix priority.
-6. End with residual risks and a clear next action.
+4. Convert findings into structured issues: problem, why it matters, required fix, severity, route, and acceptance check.
+5. When the target already has claimed fixes or rebuttal responses, add revision traceability: author claim, claimed artifact location, independently verified or not, and remaining gap.
+6. Output fatal flaws first when present.
+7. Rank the fix priority.
+8. End with consensus, disagreement, resolution, residual risks, and a clear next action.
 
 ## Context Read Set
 
@@ -48,7 +50,8 @@
 - For quick prompts such as "rebuttal一下看有什么缺点", start with the rebuttal Light Read Set only: active LaTeX, result summaries, managed indices, and supplied criticism. Do not run a whole-repository scan unless the panel records a specific escalation reason.
 - External rebuttal, AC, meta-review, colleague, or user criticism must be converted into internal actionable issues before any rewrite or response draft.
 - The Reviewer Panel must classify issues across R1 Significance / Originality / Insight, R2 Soundness / Technical Quality, R3 Evaluation / Analysis, R4 Results / Tables / Numeric Evidence, and R5 Presentation / Clarity.
-- Each issue must include severity, affected artifact, required fix, route, acceptance check, and whether core mutation is required.
+- Each issue must include problem, why it matters, severity, affected artifact, required fix, route, acceptance check, and whether core mutation is required.
+- For re-review or rebuttal-repair passes, record author claim, claimed location, independently verified status, and remaining gap before marking an issue resolved.
 - In L1/L2, core mutation remains an approval boundary unless explicitly authorized. In L3, route core mutation through the shared ledger policy instead of treating it as a reviewer-stage blocker.
 
 ## Output Style
@@ -57,6 +60,7 @@
 - findings first
 - fatal flaws called out explicitly
 - fix priority stated clearly
+- consensus / disagreement / resolution stated clearly
 - evidence-linked critique
 - explicit residual risks
 - explicit alternative explanations and boundary risks

package/package-assets/shared/skills/lab/stages/write.md

@@ -70,6 +70,9 @@ Run these on every round:
 - section flow check -> `skills/lab/references/paper-writing/does-my-writing-flow-source.md`
 - reviewer pass -> `skills/lab/references/paper-writing/paper-review.md`
 - section-specific style policy -> `skills/lab/references/paper-writing/section-style-policies.md` (load the block matching the current section)
+- section question bank -> `skills/lab/references/paper-writing/section-question-bank.md`
+- argument stress test -> `skills/lab/references/paper-writing/argument-stress-test.md`
+- language anti-pattern sweep -> `skills/lab/references/paper-writing/writing-anti-patterns.md`
 
 ## Rebuttal Mode
 
@@ -167,9 +170,9 @@ Do not enter prose polish until the current section has passed the reference-con
 - In Conclusion, state the broader principle or action implication implied by the evidence, then state the boundary. Do not introduce a new insight there.
 - Avoid paper-facing headings such as `Our Insights` or `核心洞见`; if a heading is needed, use normal section roles such as motivation, analysis, ablation, or discussion and let the insight appear in the prose.
 - Nontrivial section work must use three separated revision passes instead of one all-purpose rewrite:
-  - Logic pass: check the paragraph role, claim chain, premise-to-conclusion transition, evidence dependency, and whether the section naturally follows from adjacent sections. Do not polish wording in this pass.
-  - Theory / field pass: after the logic pass is clean, check concept use, field terminology, metric definitions, citation anchors, and whether the chosen framework actually fits the claim. Do not treat fluent language as proof that the theory is right.
-  - Language pass: only after logic and theory blockers are resolved, revise academic tone, sentence rhythm, transitions, concision, and local readability.
+  - Logic pass: check the paragraph role, claim chain, premise-to-conclusion transition, evidence dependency, and whether the section naturally follows from adjacent sections. Use `section-question-bank.md` to force explicit answers about section purpose. Do not polish wording in this pass.
+  - Theory / field pass: after the logic pass is clean, check concept use, field terminology, metric definitions, citation anchors, and whether the chosen framework actually fits the claim. Run `argument-stress-test.md` here, including the weakest-link test, reverse-claim test, and strongest alternative explanation check. Do not treat fluent language as proof that the theory is right.
+  - Language pass: only after logic and theory blockers are resolved, revise academic tone, sentence rhythm, transitions, concision, and local readability. Run `writing-anti-patterns.md` here and remove throat-clearing openings, uniform paragraph patterns, synonym cycling, and generic evaluative filler before accepting the pass.
 - Do not continue into language polish when the logic pass or theory / field pass still has an unresolved blocker; repair the blocker first or route back to `review`, `iterate`, or `report` if the blocker is evidentiary.
 - Default automation should not require the user to approve every pass. Record the three pass outcomes in the write-iteration artifact and stop for one user question only when a failed pass would change paper-level framing, claims, protocol, or downstream section structure.
 - If the user explicitly asks for interactive or human-in-the-loop rewriting, show the result of each pass and wait before moving from logic -> theory -> language.
@@ -188,7 +191,8 @@ Do not enter prose polish until the current section has passed the reference-con
 - Do not default the next-step recommendation to another polish pass. Recommend the first unresolved section-level blocker, or stop if the section is already accepted for the round.
 - Use natural-language full names in prose. If an approved short form is needed later, define it once and reuse it consistently.
 - Chinese workflow-language terminology must be stricter than generic first-mention rules. When `workflow_language=zh`, concept terms should use a Chinese paper-facing name and a Chinese short form by default. English full form plus acronym may appear at first mention only as `中文全称（English full form, ACRONYM）`, then prose should reuse the Chinese short form. Prefer natural compact Chinese short forms; two-character, three-character, four-character, or longer short phrases are all acceptable when they read naturally. Do not force a fixed-length abbreviation. Avoid repeating English concept fragments such as `residual-fitting pathology`, `treated-group noise`, `gain-head function class`, `input-matched`, or `refinement` throughout Chinese prose.
-- For `workflow_language=zh`, run `validate_workflow_language_text.py` over touched workflow-language sections, tables, figures, and analysis assets before completing the round. If it reports English concept fragments, translate them, define them once as `中文全称（English full form, ACRONYM）`, or add a justified glossary exception before prose polish.
+- For `workflow_language=zh`, run `validate_paper_layer.py` on the resolved active paper layer before completing the round. This is a whole-layer gate, not a touched-file spot check. If it reports English concept fragments or English paper-facing headings/captions, translate them, define them once as `中文全称（English full form, ACRONYM）`, or add a justified glossary exception before prose polish.
+- Use `validate_workflow_language_text.py` as a local repair helper when you need to narrow the issue to one specific workflow-language file after the whole-layer validator fails.
 - Do not use labels containing `_` or `-` in reader-facing prose.
 - Keep internal identifiers, config keys, and experiment package labels out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose.
 - Keep run provenance such as tuning-run labels, probe names, internal config strings, rerun ids, and package labels out of reader-facing prose. If the evidence is useful, rewrite it as a bounded paper-facing diagnostic or move the raw provenance to workflow notes or appendix metadata.
@@ -225,10 +229,12 @@ Do not enter prose polish until the current section has passed the reference-con
 - Before drafting `introduction`, `method`, `experiments`, `related work`, or `conclusion`, also run `.lab/.managed/scripts/validate_paper_topology.py --project-root .` so plan/context files cannot keep presenting legacy layers as the active paper topology. If that validator fails, do not mark the topology as repaired and do not continue section polish.
 - When the repository workflow config is available, the paper-plan validator also checks that `.lab/writing/plan.md` stays in `workflow_language` instead of silently drifting into another language.
 - If the paper-plan validator fails, stop and fill `.lab/writing/plan.md` first instead of drafting prose.
+- After revising the active section, run `.lab/.managed/scripts/validate_paper_layer.py --project-root . --layer <resolved-layer> --mode draft` so layer-wide language drift and LaTeX graph breakage are caught even when the current section itself looks clean.
 - During ordinary draft rounds, run `.lab/.managed/scripts/validate_section_draft.py --section <section> --section-file <section-file> --mode draft` and `.lab/.managed/scripts/validate_paper_claims.py --section-file <section-file> --mode draft` after revising the active section.
 - During ordinary draft rounds that introduce or revise metrics, also run `.lab/.managed/scripts/validate_metric_glossary.py --metric-glossary .lab/writing/metric-glossary.md --tex-file <section-or-table-file> --mode draft`.
 - If reference-guided deep-write was triggered, also run `.lab/.managed/scripts/validate_reference_consumption.py --section <section> --section-file <section-file> --mode draft` after revising the active section.
 - Treat draft-round output from the section and claim validators as warnings that must be recorded and addressed in the write-iteration artifact, not as immediate stop conditions.
+- Treat paper-layer validator failures as blockers. They indicate active-layer breakage that section-local validators cannot safely waive.
 - If the active section already lives under a paper-layer `sections/` directory, the draft section validator should also warn when the neighboring required figure or analysis placeholder files are still missing from that same paper layer.
 - For each subsection, explicitly include motivation, design, and technical advantage when applicable.
 - Avoid a writing style that reads like incremental patching of a naive baseline.
@@ -257,6 +263,7 @@ Do not enter prose polish until the current section has passed the reference-con
 - Core asset coverage for a paper-facing final draft should include a problem-setting or teaser figure, a method overview figure, a results overview figure, a main-results table, an ablation table, and one additional analysis asset.
 - Keep `.lab/writing/plan.md` synchronized with the current table plan, figure plan, citation plan, and section-to-asset map whenever manuscript assets change.
 - For final-draft or export rounds, run `.lab/.managed/scripts/validate_section_draft.py --section <section> --section-file <section-file> --mode final` and `.lab/.managed/scripts/validate_paper_claims.py --section-file <section-file> --mode final` before accepting the round.
+- For final-draft or export rounds, run `.lab/.managed/scripts/validate_paper_layer.py --project-root . --layer <resolved-layer> --mode final` before accepting the round; use `--mode export` for export/publish rounds.
 - For final-draft or export rounds with reported metrics, run `.lab/.managed/scripts/validate_metric_glossary.py --metric-glossary .lab/writing/metric-glossary.md --tex-file <section-file> --mode final` before accepting the round. Add relevant table, figure, or analysis `.tex` files with repeated `--tex-file` when they contain metric names.
 - If reference-guided deep-write was triggered, run `.lab/.managed/scripts/validate_reference_consumption.py --section <section> --section-file <section-file> --mode final` before accepting the final-draft or export round.
 - If the final-round section or claim validators fail, keep editing the affected section until it passes; do not stop at asset-complete but rhetorically weak or unsafe prose.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "superlab",
-  "version": "0.1.77",
+  "version": "0.1.79",
   "description": "Strict /lab research workflow installer for Codex and Claude",
   "keywords": [
     "codex",