First readthe specific methods, parameters, and boundaries, then follow thestructured stepsto execute. The values, file names, and titles are examples and must be replaced according to the current input; do not treat the examples as actual business facts.
Input and execution
The user needs the preface to use a separate label while the body starts displaying reading page numbers from page 1. First verify the input file, the user-approved modification scope, and the target output. Here, add a visible footer; do not modify the PDF reader PageLabels, and this is not bookmark page numbers or Bates sequential numbering. Regenerate the mapping after the actual body page count changes; replace=false will not clear old footers, so do not blindly repeat execution on existing numbering.
Keep a single native CLI script or the same MCP session, and use the ID actually returned by the current doc_open. The CLI compiler's document slot only applies to the brand-new process script it generates, not to an already-running editor ID. When a tool is missing, report the gap; do not impersonate it with a similar command.
Verification and delivery
Reopen the output and check that preface i and body 1/3, 2/3, 3/3 appear only on the corresponding pages, and that the footer does not obscure the body; keep the four pages of original text and the source summary.
Deliver a new output that actually exists and a brief processing note, and preserve the input; if only a technical sample check was completed, state clearly that a real complex document or in-host synchronization was not verified. No other sibling skill resources are needed; this skill contains all necessary references and scripts.