superlab 0.1.62 → 0.1.64

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

@@ -33,9 +33,10 @@
 ## Rule Preflight
 
 - Read `.lab/.managed/rule-manifest.json` before drafting.
-- Record a `Rule Preflight` block in the write-iteration artifact before revising prose.
-- The `Rule Preflight` block must record the installed rule source file, rule source revision, project version, resolved stage, resolved mode, resolved target, and any override reason.
+- Write the `Rule Preflight` block with `.lab/.managed/scripts/render_rule_preflight.py` before revising prose; do not hand-fill it from memory.
+- The `Rule Preflight` block must record the installed rule source file, rule source revision, project version, resolved stage, resolved mode, resolved target, a machine-generated preflight stamp, and any override reason.
 - If the installed write rule and the current round behavior disagree, fix the targeting or record a valid override reason before further editing.
+- In draft mode, rule-preflight mismatches and paper-topology mismatches are blockers, not polish warnings.
 
 ## Context Write Set
 
@@ -75,8 +76,11 @@ Run these on every round:
 - Ordinary manuscript drafting rounds should follow `workflow_language`.
 - During ordinary rounds, ordinary `.tex` section drafts must stay in `workflow_language`; do not treat `paper_language` as the default draft language.
 - When `workflow_language` and `paper_language` differ, treat the workflow-language paper layer as active and use it as the default ordinary working layer.
+- Resolve the active paper topology from `.lab/config/workflow.json` before drafting: the active canonical layer is `<deliverables_root>/paper/`, and when `workflow_language` differs from `paper_language` the active workflow-language layer is `<deliverables_root>/paper/workflow-language/`.
 - Ordinary write rounds should still edit one target paper layer at a time, not both language layers at once.
 - 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. Active-layer targets (`active-canonical` / `active-workflow-language`) remain managed manuscript rounds; deprecated or legacy paper-layer targets are only acceptable as out-of-band file edits and must not silently replace the active paper topology.
+- Do not treat old layer names such as `review_zh`, `translation_zh`, `sections_zh`, or stale `deliverables/.../workflow-language/*.md` paths as active manuscript roots, even if older project files still reference them.
 - 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 instead of silently treating canonical as the default working layer.
 - 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.
 - 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.
@@ -153,6 +157,7 @@ Run these on every round:
   - record what each figure or analysis asset should show and why the reader needs it
   - record which citation anchors must appear in the section and why each anchor matters
 - Before drafting `introduction`, `method`, `experiments`, `related work`, or `conclusion`, run `.lab/.managed/scripts/validate_paper_plan.py --paper-plan .lab/writing/plan.md`.
+- 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.
 - 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.
@@ -198,6 +203,7 @@ Run these on every round:
 - Record the round target layer in the write-iteration artifact as `canonical manuscript`, `workflow-language paper layer`, or `both`.
 - If workflow-language was active and the round still targeted the canonical manuscript, record why canonical-only writing was acceptable in the write-iteration artifact.
 - If both layers were edited, record why the cross-language sync was required and whether it was explicitly requested by the user or required by final-draft/export finalization.
+- Record the active canonical paper root, the active workflow-language paper root when present, the resolved target path role, and any out-of-band reason in the write-iteration artifact before accepting the round.
 - Record the protocol/scope impact audit in the write-iteration artifact whenever a round replaces or rewrites a canonical experiment/evaluation protocol.
 - If the round is an export or remote-publication round, record the export target, whether the workflow-language paper layer was included in the exported or pushed bundle, and why any canonical-only export was acceptable.
 - When `workflow_language` and `paper_language` differ, record the final manuscript language choice in the write-iteration artifact with the workflow language, paper language, finalization decision, and why that decision was chosen.

package/package.json

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