@open-press/cli 0.6.0 → 0.7.1

package/template/core/src/openpress/workbench.tsx

@@ -33,18 +33,14 @@ import {
   ProjectEntryPanel,
   type ProjectMentionItem,
 } from "./projectWorkspace";
-import { paginateSourcePages, type PaginatedPage } from "./pagination";
+import { createAnchorPageMap, resolveAnchorPageIndex } from "./anchorMap";
 import { scheduleBrowserFrame } from "./frameScheduler";
 import {
-  createAnchorPageMap,
-  numberSourceHeadings,
   PUBLIC_DRAWER_BREAKPOINT,
   PublicPage,
-  resolveAnchorPageIndex,
   useViewMode,
 } from "./publicPage";
 import { getProjectIdentity } from "./projectIdentity";
-import { hasBuildTimePagination } from "./reactDocumentMetadata";
 import { buildPublicPreviewHref, isLocalWorkspaceHost } from "./runtimeMode";
 import { useReaderRuntime } from "./readerRuntime";
 import type { DeploymentInfo, ReaderDocument, HtmlPageBlock, SourceBlock } from "./types";
@@ -123,14 +119,9 @@ export function HtmlWorkbench({
   deploymentInfo: DeploymentInfo;
 }) {
   const sourceContainerRef = useRef<HTMLDivElement | null>(null);
-  const numberedPages = useMemo(() => numberSourceHeadings(pages), [pages]);
+  const displayPages = pages;
   const viewModeState = useViewMode();
   const { viewMode } = viewModeState;
-  const buildTimePaginated = hasBuildTimePagination(document);
-  const [paginatedPages, setPaginatedPages] = useState<PaginatedPage[] | null>(null);
-  const displayPages: DisplayPage[] = viewMode === "paged" && !buildTimePaginated
-    ? (paginatedPages ?? numberedPages)
-    : numberedPages;
   const mediaAssets = useMemo(() => collectMediaAssetIndex(displayPages), [displayPages]);
   const anchorPageMap = useMemo(() => createAnchorPageMap(displayPages), [displayPages]);
   const projectComponentUsages = useMemo(() => createProjectComponentUsages(displayPages), [displayPages]);
@@ -163,7 +154,6 @@ export function HtmlWorkbench({
   const pdfButtonText = workbenchPdfButtonText(localDeployEnabled, pdfActionStatus, staticPdfHref);
   const pdfStatusMessage = workbenchPdfStatusMessage(localDeployEnabled, pdfActionStatus);
   const pdfButtonDisabled = localDeployEnabled ? pdfActionStatus === "generating" || pdfActionStatus === "opening" : !staticPdfHref;
-  const activePaginatedReady = viewMode === "reading" || buildTimePaginated || Boolean(paginatedPages);
   const inspectorSelectionLabel = formatInspectorSelection(inspector.selectedBlock);
   const activeInlineSavedComment = getInlineSavedCommentForTarget(inlineSavedComment, inspector.selectedTarget);
   const inspectorCommentDisabled = !inspector.selectedBlock || !inspectorCommentText.trim() || inspectorCommentStatus === "submitting";
@@ -392,10 +382,6 @@ export function HtmlWorkbench({
     scheduleBrowserFrame(() => reader.setPage(reader.currentPageIndex, { behavior: "auto" }));
   };
 
-  useLayoutEffect(() => {
-    setPaginatedPages(null);
-  }, [numberedPages]);
-
   useEffect(() => {
     setInspectorCommentStatus("idle");
     setInspectorCommentError("");
@@ -407,24 +393,6 @@ export function HtmlWorkbench({
     void refreshPendingComments();
   }, [devMode, refreshPendingComments, workspaceView]);
 
-  useLayoutEffect(() => {
-    if (buildTimePaginated) return undefined;
-    if (viewMode !== "paged" || paginatedPages) return undefined;
-    const sourceContainer = sourceContainerRef.current;
-    if (!sourceContainer) return undefined;
-
-    let cancelled = false;
-    const cancelFrame = scheduleBrowserFrame(() => {
-      const nextPages = paginateSourcePages(sourceContainer, numberedPages);
-      if (!cancelled) setPaginatedPages(nextPages);
-    });
-
-    return () => {
-      cancelled = true;
-      cancelFrame();
-    };
-  }, [buildTimePaginated, numberedPages, paginatedPages, viewMode]);
-
   const actionSection = (
     <section className="openpress-public-action-section" aria-label="輸出">
       <span className="openpress-public-action-heading">輸出</span>
@@ -512,7 +480,6 @@ export function HtmlWorkbench({
         className={`reader-app openpress-reader-app openpress-public-viewer openpress-dev-public-viewer is-ready${reader.rightPanelOpen ? "" : " is-closed-right"}`}
         data-openpress-react-runtime="true"
         data-openpress-view-mode={viewMode}
-        data-openpress-pagination={activePaginatedReady ? "ready" : "pending"}
         data-openpress-inspector-mode={inspector.inspectorMode ? "on" : "off"}
         data-active-workspace={workspaceView}
       >
@@ -533,7 +500,6 @@ export function HtmlWorkbench({
               pages={displayPages}
               currentPageIndex={reader.currentPageIndex}
               devMode={devMode}
-              paginatedReady={activePaginatedReady}
               sourceContainerRef={sourceContainerRef}
               registerPage={reader.registerPage}
               exposeSourceData={devMode}

package/template/core/src/styles/openpress/responsive.css

@@ -269,12 +269,6 @@
     box-shadow: none;
   }
 
-  .openpress-public-viewer.openpress-reader-app[data-openpress-pagination="pending"] .openpress-public-navigation {
-    transform: translateX(-110%);
-    pointer-events: none;
-    box-shadow: none;
-  }
-
   .openpress-public-viewer.openpress-reader-app .openpress-public-scrim {
     position: fixed;
     inset: 0;
@@ -309,14 +303,6 @@
     display: block;
   }
 
-  .openpress-public-viewer.openpress-reader-app[data-openpress-pagination="pending"] .openpress-public-scrim {
-    display: none;
-  }
-
-  .openpress-public-viewer.openpress-reader-app[data-openpress-pagination="pending"] .openpress-public-fab {
-    display: flex;
-  }
-
   .openpress-public-viewer[data-openpress-view-mode="paged"] .reader-pages {
     --openpress-public-page-width: min(
       var(--openpress-page-width),

package/template/core/tsconfig.json

@@ -17,7 +17,10 @@
     "noEmit": true,
     "jsx": "react-jsx",
     "paths": {
-      "@openpress/core": ["./src/openpress/core/index.tsx"],
+      "@open-press/core": ["./src/openpress/core/index.tsx"],
+      "@open-press/core/mdx": ["./src/openpress/mdx/index.ts"],
+      "@open-press/core/manuscript": ["./src/openpress/manuscript/index.tsx"],
+      "@open-press/core/numbering": ["./src/openpress/numbering/index.ts"],
       "@/components": ["./document/components/index.ts", "./document/components/index.tsx"],
       "@/components/*": ["./document/components/*"],
       "@/*": ["./src/*"]

package/template/core/vite.config.ts

@@ -5,7 +5,7 @@ import path from "node:path";
 import type { IncomingMessage, ServerResponse } from "node:http";
 import { defineConfig } from "vite";
 import react from "@vitejs/plugin-react";
-import { loadConfig, publicPdfHref } from "./engine/config.mjs";
+import { loadConfig, publicPdfHref } from "./engine/runtime/config.mjs";
 import { handleCommentRequest } from "./engine/react/comment-endpoint.mjs";
 import { handleProjectAssetRequest } from "./engine/react/project-asset-endpoint.mjs";
 
@@ -15,8 +15,11 @@ const workspaceRoot = process.env.OPENPRESS_WORKSPACE_ROOT
   : frameworkRoot;
 const sourceRoot = path.join(frameworkRoot, "src");
 const openpressCliPath = path.join(frameworkRoot, "engine", "cli.mjs");
-const staticServerPath = path.join(frameworkRoot, "engine", "static-server.mjs");
+const staticServerPath = path.join(frameworkRoot, "engine", "output", "static-server.mjs");
 const openpressCoreEntry = path.join(frameworkRoot, "src", "openpress", "core", "index.tsx");
+const openpressMdxEntry = path.join(frameworkRoot, "src", "openpress", "mdx", "index.ts");
+const openpressManuscriptEntry = path.join(frameworkRoot, "src", "openpress", "manuscript", "index.tsx");
+const openpressNumberingEntry = path.join(frameworkRoot, "src", "openpress", "numbering", "index.ts");
 const openpressConfig = await loadConfig(workspaceRoot);
 const outputDir = openpressConfig.paths.outputDir;
 const reactDocumentRoot = openpressConfig.paths.documentRoot;
@@ -55,7 +58,11 @@ export default defineConfig({
   resolve: {
     dedupe: ["react", "react-dom", "@mdx-js/react"],
     alias: {
-      "@openpress/core": openpressCoreEntry,
+      // Subpaths must come before the base path so resolution matches longest first.
+      "@open-press/core/mdx": openpressMdxEntry,
+      "@open-press/core/manuscript": openpressManuscriptEntry,
+      "@open-press/core/numbering": openpressNumberingEntry,
+      "@open-press/core": openpressCoreEntry,
       "@/components": reactDocumentComponentsRoot,
       "@": sourceRoot,
       ...workspaceAliases,

package/template/packs/academic-paper/document/chapters/01-introduction/content/01-introduction.mdx

@@ -1,21 +1,35 @@
 ## Introduction
 
-This document is a model and starting point for an academic paper drafted in open-press. The structure follows the IEEE conference template conventions where they make sense for screen-first reading: numbered sections, italic sub-sections, an abstract block, and a numbered references list. The two-column body of IEEEtran is not yet supported — single-column will land as the v0.8 paged.js migration arrives.
+The purpose of this paper template is to provide a compact, readable structure for a
+machine-learning research manuscript written in a formal journal style.
 
-Use this pack for **drafting, iteration, and preprint distribution**. When the paper is ready for venue submission, export the prose into the publisher's required LaTeX class (`IEEEtran`, `acmart`, etc.). The pack does not replace LaTeX for camera-ready submission; it replaces the awkward iteration loop *before* submission.
+### Background and Motivation
 
-### Where to start
+Recent studies have shown that modern experiments produce larger datasets and richer
+artifact pipelines, but the writing process is often bottlenecked by repeated formatting
+adjustments. A lightweight drafting layer can decouple scientific reasoning from
+typesetting concerns and let the author focus on experimental validity first.
 
-Each chapter directory under `document/chapters/` is one paper section:
+### Problem Statement
 
-- `01-introduction/` — motivate the work, state the contribution, summarise the structure.
-- `02-methods/` — describe what you did, with enough detail to reproduce.
-- `03-results-and-discussion/` — present results with figures and tables; interpret what they mean.
-- `04-acknowledgment/` — acknowledge funding, collaborators, reviewers.
-- `05-references/` — numbered `[1]`, `[2]` references.
+The key challenge addressed in this draft is to keep the manuscript internally
+consistent while moving from scratch notes to a submission-ready narrative. The
+workflow should preserve section hierarchy, citation order, and figure/table integrity
+without requiring manual renumbering.
 
-Replace each chapter's MDX content with your own. The skeleton text below each `##` heading is illustrative — overwrite it.
+### Contribution
 
-### Abstract and Index Terms
+This demo paper includes the following contributions:
 
-Edit the abstract and index terms inside `document/index.tsx` (the `cover` JSX export). They render on the title page above the body. Keep the abstract under 250 words and avoid abbreviations, symbols, or math in it.
+- A reproducible chapter flow (`Introduction → Methods → Results and Discussion →
+  Conclusion`),
+- Consistent heading levels for major and minor sections,
+- Placeholder media and tables that can be swapped with real results,
+- A reference block and placeholder metadata for a clean handoff to final publication
+  tooling.
+
+### Paper Organization
+
+The paper is organized as follows: Section 2 details the methodology,
+Section 3 reports results and discusses representative scenarios,
+Section 4 summarizes conclusions and practical recommendations.

package/template/packs/academic-paper/document/chapters/02-methods/content/01-methods.mdx

@@ -1,30 +1,50 @@
 ## Methods
 
-Describe the materials, instruments, datasets, models, or procedures you used. Anyone familiar with the field should be able to reproduce your work from this section.
+This section describes a hypothetical experimental design suitable for an applied
+machine-learning paper.
 
-### Apparatus and Materials
+### Data and Problem Setup
 
-Specify hardware, software versions, datasets, and any pre-processing. Cite reused work using `[N]` numeric references (e.g. "we trained the encoder following the procedure of [3]").
+We assume a synthetic dataset with 3,200 anonymized samples collected under three
+operational conditions. Each sample includes paired feature vectors, timestamped
+metadata, and a binary outcome label. The baseline split is 70/15/15 for training,
+validation, and held-out test sets.
 
-### Procedure
+### Core Pipeline
 
-Describe the experimental procedure as steps a reader could follow:
+The pipeline has three stages:
 
-1. State the input data and pre-processing.
-2. State the model / algorithm / instrument settings.
-3. State the evaluation metric(s) and any held-out splits.
-4. State randomness control (seeds, repeats, confidence reporting).
+1. **Preprocessing**: normalization, missing-value handling, and feature screening.
+2. **Modeling**: training a compact baseline model and a comparison ablation set.
+3. **Evaluation**: calibration-aware scoring and bootstrapped confidence intervals.
 
-### Notation
+For this draft, preprocessing includes clipping extreme values and aligning all
+continuous fields to SI-style unit notation.
 
-Define notation early. Italicise Roman symbols for quantities and variables, but not Greek symbols. Use a long dash rather than a hyphen for a minus sign. Number equations consecutively:
+### Equations
 
-$$a + b = \gamma \tag{1}$$
+The main objective is written as:
 
-Refer to equations by `(1)`, not `Eq. (1)` or `equation (1)`, except at the start of a sentence: "Equation (1) shows ...".
+$$
+\mathcal{L}(\theta) = \sum_{i=1}^{N}\left(\hat{y}_{i}(\theta)-y_{i}\right)^2
+$$
 
-### Reporting Units
+where $\theta$ are trainable parameters and the objective is minimized on the
+training subset.
 
-- Use SI (MKS) as primary units; English units only as secondary (in parentheses).
-- Don't mix complete spellings and abbreviations: "Wb/m²" or "webers per square meter", not "webers/m²".
-- Use a zero before decimal points: `0.25`, not `.25`.
+### Evaluation Protocol
+
+Model quality is measured by macro-averaged F1, AUROC, and an uncertainty-aware
+calibration score. Reproducibility is ensured by fixing the random seed and logging
+all preprocessing parameters.
+
+### Implementation Notes
+
+- All runs were executed on a dual-socket compute node with two GPUs.
+- Checkpoints were stored every 5 epochs.
+- Logging followed a single JSON schema shared across all experiments.
+
+### Validation and Quality Control
+
+Validation is automated through a script that checks missing captions, file path
+consistency, and reference formatting before final export.

package/template/packs/academic-paper/document/chapters/03-results-and-discussion/content/01-results.mdx

@@ -1,29 +1,47 @@
 ## Results and Discussion
 
-Present the findings of your study, then interpret what they mean for the research question stated in the introduction.
+### Benchmark Results
 
-### Quantitative Results
+The synthetic experiment yields a consistent improvement trend across three datasets.
+Performance gains are modest but stable after hyperparameter tuning.
 
-Use a table to summarise results across conditions. Caption above the table.
+| Metric | Baseline | Proposed | Improvement |
+| --- | --- | --- | --- |
+| Macro-F1 | 0.61 | 0.67 | +9.8% |
+| AUROC | 0.74 | 0.81 | +9.5% |
+| Calibration Error | 0.082 | 0.043 | -47.6% |
 
-<TableCaption>Sample comparison of conditions.</TableCaption>
+The proposed model retains a similar variance profile while improving score
+stability in low-sample conditions.
 
-| Condition | Metric A | Metric B | Notes |
-| --- | --- | --- | --- |
-| Baseline | 0.71 | 0.65 | Prior work [3] |
-| Ours (v1) | 0.78 | 0.69 | This work |
-| Ours (v2) | **0.83** | **0.72** | Best |
+### Representative Visualization
+
+<img
+  src="media/figure-placeholder.svg"
+  alt="Example of a figure placeholder"
+  style={{ maxWidth: "420px", width: "100%", height: "auto" }}
+/>
+
+Figure 1. Example of a result trend visualization (placeholder image).
+
+### Error Analysis
 
-Cite figures and tables in the text the first time they appear: "Fig. 1 shows the architecture", "Table I summarises the conditions". Use `Fig.` even at the start of a sentence; spell out `Figure` only when it is the subject.
+Some error cases cluster around edge classes with incomplete metadata. These cases
+benefit from better augmentation and a revised class-balanced loss.
 
-### Qualitative Discussion
+### Sensitivity Study
 
-Discuss what the results mean. State the limitations honestly — if the experiment doesn't cover a case you'd like to claim, say so. Avoid the word "essentially" when you mean "approximately" or "effectively".
+- Training set size below 40% causes a steeper drop in recall.
+- Early stopping thresholds above 3 epochs reduce overfitting in our setting.
+- Calibrated post-processing improves confidence robustness.
 
-### Threats to Validity
+### Discussion
 
-Briefly list what could invalidate the results: small sample size, single dataset, environmental drift, evaluator bias, etc. Reviewers will look for this section; pre-empt it.
+The most practical takeaway is that small engineering changes in preprocessing and
+evaluation discipline can produce measurable gains even when architecture changes are
+minimal.
 
-### Future Work
+### Limitations
 
-Indicate where the work goes next. Keep this to one short paragraph — over-claiming future scope hurts more than it helps in review.
+This section reports synthetic results only; real-world deployment would require
+cross-domain validation, privacy checks, and a stronger external benchmark suite.

package/template/packs/academic-paper/document/chapters/04-acknowledgment/content/01-acknowledgment.mdx

@@ -1,12 +1,26 @@
-## Acknowledgment
+## Conclusions
 
-The preferred American spelling is *acknowledgment* without an "e" after the "g". Avoid stilted constructions like "one of us (R. B. G.) thanks ...". Prefer "R. B. G. thanks ...".
+This template run shows that a simple methodology with consistent evaluation
+accounting can achieve reliable gains without dramatic architectural complexity.
 
-Acknowledge:
+### Key Takeaways
 
-- Funding sources (with grant numbers if applicable).
-- Collaborators who contributed materially but are not listed as authors.
-- Anonymous reviewers whose comments improved the paper.
-- Institutional or computational resources.
+- Keep preprocessing and metric reporting deterministic.
+- Use a calibrated validation protocol before reporting final headline scores.
+- Reserve model complexity for problems that cannot be solved with better data
+  discipline.
 
-Place sponsor acknowledgments in the unnumbered footnote on the first page of the published version. In this draft pack, keep them here until you migrate to a publisher's class file at submission time.
+### Practical Recommendations
+
+Authors are encouraged to replace each placeholder paragraph with real study details,
+including hardware, code provenance, and full reproducibility statements.
+
+### Limitations and Future Work
+
+The current draft is synthetic; external generalization remains to be demonstrated.
+Future work should add domain transfer tests and a public benchmark release.
+
+### Acknowledgments
+
+We thank the hypothetical reviewers and platform contributors who would have reviewed
+this draft in a real submission round.

package/template/packs/academic-paper/document/chapters/05-references/content/01-references.mdx

@@ -1,27 +1,32 @@
 ## References
 
-Number citations consecutively within square brackets `[1]`. Sentence punctuation follows the bracket. Refer simply to the reference number, as in `[3]` — do not use `Ref. [3]` or `reference [3]` except at the start of a sentence: "Reference [3] was the first ...".
-
-Unless there are six authors or more, give all authors' names; do not use `et al.`. Papers not yet published should be cited as *unpublished*; accepted but not yet published as *in press*. Capitalize only the first word in a paper title, except for proper nouns and element symbols.
-
-For papers published in translation journals, give the English citation first, followed by the original foreign-language citation.
+Please number references consecutively within brackets `[1]`.
+Sentence punctuation follows the bracketed number.
 
 ---
 
-[1] G. Eason, B. Noble, and I. N. Sneddon, "On certain integrals of Lipschitz–Hankel type involving products of Bessel functions," *Phil. Trans. Roy. Soc. London*, vol. A247, pp. 529–551, April 1955.
+[1] G. Eason, B. Noble, and I. N. Sneddon, “On certain integrals of
+Lipschitz-Hankel type involving products of Bessel functions,” *Phil. Trans. Roy.
+Soc. London*, vol. A247, pp. 529–551, April 1955.
 
-[2] J. Clerk Maxwell, *A Treatise on Electricity and Magnetism*, 3rd ed., vol. 2. Oxford: Clarendon, 1892, pp. 68–73.
+[2] J. Clerk Maxwell, *A Treatise on Electricity and Magnetism*, 3rd ed., vol. 2.
+Oxford: Clarendon, 1892, pp. 68–73.
 
-[3] I. S. Jacobs and C. P. Bean, "Fine particles, thin films and exchange anisotropy," in *Magnetism*, vol. III, G. T. Rado and H. Suhl, Eds. New York: Academic, 1963, pp. 271–350.
+[3] I. S. Jacobs and C. P. Bean, “Fine particles, thin films and exchange anisotropy,”
+in *Magnetism*, vol. III, G. T. Rado and H. Suhl, Eds. New York: Academic,
+1963, pp. 271–350.
 
-[4] K. Elissa, "Title of paper if known," unpublished.
+[4] K. Elissa, “Title of paper if known,” unpublished.
 
-[5] R. Nicole, "Title of paper with only first word capitalized," *J. Name Stand. Abbrev.*, in press.
+[5] R. Nicole, “Title of paper with only first word capitalized,” *J. Name Stand.
+Abbrev.*, in press.
 
-[6] Y. Yorozu, M. Hirano, K. Oka, and Y. Tagawa, "Electron spectroscopy studies on magneto-optical media and plastic substrate interface," *IEEE Transl. J. Magn. Japan*, vol. 2, pp. 740–741, August 1987.
+[6] Y. Yorozu, M. Hirano, K. Oka, and Y. Tagawa, “Electron spectroscopy studies
+on magneto-optical media and plastic substrate interface,” *IEEE Trans. J. Magn.
+Japan*, vol. 2, pp. 740–741, August 1987.
 
-[7] M. Young, *The Technical Writer's Handbook*. Mill Valley, CA: University Science, 1989.
-
----
+[7] M. Young, *The Technical Writer's Handbook*. Mill Valley, CA: University
+Science, 1989.
 
-> **Reminder**: replace the seven placeholder references above with your own bibliography before circulating the draft. They are the IEEE conference template's example citations and have nothing to do with your paper.
+> Open-press is used for iteration. Remove all template placeholder text and replace
+> references before submission.

package/template/packs/academic-paper/document/components/Page.tsx

@@ -1,27 +1,60 @@
-import type { PageProps } from "@openpress/core";
+import { Frame, MdxArea } from "@open-press/core";
+import type { SectionsPageProps } from "@open-press/core/manuscript";
+import { useEffect, useRef } from "react";
 
 export default function Page({
+  frameKey,
+  chainId,
   pageIndex,
   totalPages,
-  chapterSlug,
-  chapterTone,
-  children,
-}: PageProps) {
+  sectionSlug,
+  sectionTitle,
+  sectionTone,
+}: SectionsPageProps) {
+  const pageBodyRef = useRef<HTMLElement | null>(null);
+
+  const runningHeader =
+    "This is a non-peer reviewed Express letter submitted to J SEDI";
+  const runningRight = "Your short title goes here";
+
+  useEffect(() => {
+    const area = pageBodyRef.current?.querySelector(".openpress-mdx-area");
+    if (!area) return;
+
+    area.querySelectorAll<HTMLElement>("h2[data-chapter]").forEach((heading) => {
+      const chapterValue = heading.getAttribute("data-chapter");
+      if (!chapterValue) return;
+      if (!/^\d+$/.test(chapterValue)) return;
+      const normalized = String(Number.parseInt(chapterValue, 10));
+      heading.setAttribute("data-chapter", normalized);
+    });
+  }, [chainId]);
+
   return (
-    <section
-      className="reader-page reader-page--content"
-      data-page-kind="content"
-      data-page-footer="true"
+    <Frame
+      frameKey={frameKey}
+      role="manuscript.content"
+      className="reader-page--content"
       data-page-index={pageIndex}
       data-total-pages={totalPages}
-      data-chapter-slug={chapterSlug}
-      data-chapter-tone={chapterTone}
+      data-section-id={sectionSlug}
+      data-chapter-tone={sectionTone}
     >
       <div className="page-frame">
-        <header className="page-header" aria-hidden="true" />
-        <main className="page-body">{children}</main>
-        <footer className="page-footer" aria-hidden="true" />
+        <header className="page-header" aria-hidden="true">
+          <span className="running-head-left">{runningHeader}</span>
+          <span className="running-head-right">{runningRight}</span>
+        </header>
+        <main className="page-body" ref={pageBodyRef}>
+          <MdxArea chainId={chainId} overflow="extend" />
+        </main>
+        <footer className="page-footer" aria-hidden="true">
+          <span className="footer-left">{sectionTitle}</span>
+          <span className="footer-right">
+            {totalPages > 1 ? `${pageIndex + 1}/${totalPages}` : pageIndex + 1}
+          </span>
+        </footer>
       </div>
-    </section>
+    </Frame>
   );
 }

package/template/packs/academic-paper/document/design.md

@@ -112,7 +112,7 @@ Block-level 強調(callout / warning / note)目前不在 design system 範圍;
 
 ### Chapter & Section Numbering
 
-Engine 不在 h2/h3 內容前注入任何編號或前綴;pagination runtime 計數後寫入 `data-chapter` / `data-section` attribute(值是 `01`、`1.1` 這種兩位數阿拉伯格式)。實際顯示樣式由 theme 的 `::before content` 決定,這讓不同文件能挑不同 numbering vocabulary 而不動 engine。
+Engine 不在 h2/h3 內容前注入任何編號或前綴;export pipeline 會在 build-time 寫入 `data-chapter` / `data-section` attribute(值是 `01`、`1.1` 這種兩位數阿拉伯格式)。實際顯示樣式由 theme 的 `::before content` 決定,這讓不同文件能挑不同 numbering vocabulary 而不動 reader runtime。
 
 預設(editorial-monograph 起手樣式):
 
@@ -258,7 +258,7 @@ body 內容區的 page padding(content margin)由 `.reader-page` 內的 `--page-
 | 資料歸資料 | chart data 透過 React props 或鄰近的 typed data module 傳入,不寫死在 CSS |
 | 樣式歸樣式 | chart frame 等通用規則放在 `document/theme/patterns/`;變體 CSS 放在元件自己的 `style.css` |
 | 元件歸元件 | 一個視覺 = 一個 `document/components/ComponentName/` 包;MDX 只保留 `<ComponentName />` 呼叫 |
-| Caption 必填 | caption 只寫說明文字,不手寫圖號或表號;runtime 會替 content pages 的 figure/table 自動編號 |
+| Caption 必填 | caption 只寫說明文字,不手寫圖號或表號;export pipeline 會替 content pages 的 figure/table 自動編號 |
 | PDF-safe | 圖表需 `break-inside: avoid`,高度不可壓到 footer |
 
 如果使用者要求新的視覺元件,Agent 應先更新本檔說明,再改對應的 `document/components/<name>/style.css` 或 `document/theme/` CSS,最後用 reader 預覽檢查 PDF 輸出。