Add resume and iteration-log blog posts

[JiangruiKang]

Summary

• add self-contained Quarto posts for Iteration Log and Resume Feature
• preserve the May 4, 2026 authorship, mathematical content, code, empirical outputs, and links to the executable QMCPy notebooks
• add the two notebook-produced comparison figures for the iteration-log article
• integrate the latest main with an ordinary merge commit and place both posts under the current blogs/ source tree
• reconcile PLAN.md, STATUS.md, and notes/NEXT.md while retaining the community software directory and multi-machine workflow added on main

Why

The original website migration covered the 18-post historic QMCPy archive. Two newer articles were subsequently added to the QMCPy MkDocs Blogs navigation through QMCSoftware/QMCSoftware#508, so they were absent from this repository.

The first PR revision also predated the repository-wide blog/ → blogs/ rename. Merging the latest main exposed direct conflicts in PLAN.md and STATUS.md; leaving the new posts under the obsolete singular directory would additionally have excluded them from Quarto's current render inputs.

Migration notes

• technical notebooks remain in QMCSoftware/QMCSoftware; these posts link back to those authoritative executable sources
• timing results are explicitly described as empirical rather than theoretical guarantees
• the Resume Feature source prose says 524,288 new samples in one stale sentence, while its code and stage summary give 1,048,576 - 131,072 = 917,504; the migrated article uses the internally consistent 917,504 value without changing the source notebook
• conflict repair used a normal merge commit; no rebase, history rewrite, or force-push was used

Validation

• Quarto 1.9.38: quarto render — 33/33 pages rendered
• 20 blog source pages present under blogs/
• rendered CNAME matches the source CNAME
• site-wide local-target check — 1,038 targets checked, 0 missing links/assets
• desktop and 390×844 mobile browser checks for the Blog listing and both posts
• both Iteration Log figures loaded with nonzero natural dimensions
• no page-console warnings or errors
• git diff --check and git diff --cached --check

[Copilot]

Pull request overview

Migrates two newer QMCPy documentation blog articles (May 4, 2026) into this Quarto website under the current blogs/ tree, including the notebook-produced figures, and reconciles project handoff/planning docs to reflect the expanded blog archive.

Changes:

• Add two new self-contained Quarto blog posts: “Stop Re-running…” and “How Much Accuracy Do You Need?”
• Add iteration-log comparison figures under blogs/iteration-log/figures/.
• Update PLAN.md, STATUS.md, and notes/NEXT.md to reflect the 20-post archive and migration status.

Reviewed changes

Copilot reviewed 5 out of 7 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
STATUS.md	Updates milestone/status bullets to reflect expanding the QMCPy blog archive from 18 to 20 posts.
PLAN.md	Marks the two-post expansion work as completed and updates Phase 11 checklist items accordingly.
notes/NEXT.md	Updates operational handoff/current focus and next steps related to reviewing/publishing the two-post expansion.
blogs/resume-feature/index.qmd	Adds the “How Much Accuracy Do You Need?” Quarto post content and examples for QMCPy resume/checkpointing.
blogs/iteration-log/index.qmd	Adds the “Stop Re-running…” Quarto post content and embeds iteration-log/resume comparison figures.

Suppressed comments (1)

notes/NEXT.md:30

• The “Immediate next task” list still instructs the reader to review and merge draft PR #4, which is already merged. Adjust the list to start with verifying deployment, then continue with the normal AUTHOR_WORKFLOW process for the next change.

1. Review the two new posts and the completed checks in draft pull request #4.
2. Merge the pull request after approval and verify the production deployment.
3. For the next substantive Website change, follow the start, validation,
   synchronization, and publication steps in `AUTHOR_WORKFLOW.md`.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.