c143. Loose Ends

Mark's prompts, 2026-11-12, verbatim, in the merge-sweep session:

We've had many many threads in motion. I'd like to make sure they're all merged (PRs) and pulled locally

The reason I'm trying to merge, in theory, much of a cycle's work is confined to the cycle folder and unique history and supporting pages spawned by the cycles and not step on each other's toes. In practice they often edit the same files and despite best intentions, conflicts arise. So, we may overwrite one cycles work in the rare occasion we can't untangle the PR's I'd say this is to be expected–avoided if at all possible. though. But let's prioritize getting all the new work merged into the main branch with recommendation for cleanup post merge, re-doing of any lost or damaged work. conflict resolution if needed.

Yes, clean up

Do we have the next steps outlined above recorded in a location that will be easy to pick up to tie up the longer running loose ends?