This is all about the mapping between site-url/xxxx/yyyy/zzzz and Astro pages. Even though there are no files in the /src/pages tree, the magic files [slug].astro, [...path].astro perform the same sort of rôle as if there were.

Add these to /src/:

└── pages
    ├── author
    │   └── [slug].astro
    ├── category
    │   └── [slug].astro
    ├── index.astro
    ├── [...path].astro
    ├── [slug].astro
    ├── tag
    │   └── [slug].astro
    └── [year]
        └── [month].astro

All this would have been impossible without AI assistance.

Make static front end for ncvp.me/wp.

Make GitHub repo astro-wpress, link Cloudflare to it and deploy.

Move images and other media files which have to be loaded by URL to the cloud so the URLs don't have to be fiddled with as the site is copied around. Is it important that these external files come from SSL protected sites?

Here's one from wikimedia.org

Something basic with the master at localhost/wp/wp and distributed around to the various default cloud sites

Now it's clear that I don't need full site editing and only need the block editor for the Home and Blog pages, convert all other pages and posts to the classic editor.

The gallery shortcode is much more concise than raw HTML, but there's no control over thumb and slide captions beyond what's in the media library.
Moving sites around is more of a pain because the image ids are (usually) different in the different sites.

Raw HTML seems to be the way forward.
This one doesn't pop-out:

Hellebores

This one does. As usual, you have to enter the img url twice:

Hellebores

There's inevitably some fiddling required when sites are moved around, but it's probably less than the single-image gallery method.

You can't seem to do this from the normal edit page, but have to go to the quick edit page. Irritating. OK I've found it now. Check 'Discussion' in screen options.

I'm surprised this isn't part of WP core. There are a few plugins which address the problem, at least one of which admits to being susceptible to being bypassed by a knowledgeable hacker. It ought to be possible to see how strong a user's password is from the dashboard.