05 — MSP vs storage

MSP is settings, not storage. In this workflow, Museport is the settings connector. It belongs to the configuration track.

The refresh problem belongs to the storage and hosting track: which host serves the page, and where the text is stored. For Meta Sites, the edited text belongs in the published HTML file served by GitHub Pages.

Changing a settings connector cannot, by itself, move Muse text into the page, publish a new HTML file, or make Google Sites reload a different host's copy. Those steps still require the edit-and-upload chain.

Keep the questions separate:

• Settings: Are the intended Museport settings connected?
• Storage and publishing: Is the text in the correct HTML file, has Git-FED uploaded it, and has Pages published it?

A successful settings connection is not proof that new page text has been saved. A successful Pages deployment is not proof that settings changed.