Well, I am not sure if there is a logic conclusion that no manual formatting is recommended. No manual formatting stands up on its own logic.
OK, you have sfsdf skhkshdf shfksjhf s shfsdhf s kshfd skhf, and it is using n-Para style. n-Para style defines the format of the paragraph. This you know. So if you manually format characters (note, NOT the paragraph, but a manual format of some characters), then yes, it DOES make sense that the paragraph style being used is now n-Para (appended with) CHAR (formatting).
Make a CHAR style, with Bold. Call it n-ParaBold. Now you can select any characters in a n-Para paragraph, make that selection n-ParaBold...and it will be.
The problem with manual format of styles is that they do show up in the style dropdown; and further, in my experience any manual formatting of styles tends to get carried away. People do all sorts of things and you can end up with dozens and dozens of those amended styles in the style dropdown. Yuck.
It is far better to use
explicit format, by the use of styles. If you need a bold characteristic within n-Para, fine...make one. That is what CHAR styles are for.
You can make it so it is not tied to n-Para. Just make an AllStylesBold CHAR style and use it whenever you need any characters bolded. Make the Based on property of the Style "underlying properties". Then the only thing that would change is Bold (or whatever).
I have (for example) AllStylesBold, AllStylesItalics CHAR styles that do italics and bold, and ONLY italics and bold. The font, size etc etc remains the same. There is one important aspect though. CHAR styles are toggles.
If the underlying style - say n-Para is italics, and you apply a CHAR style that is italics....the selected text will become UN-italics. This is of course important.
Gerry
My paintings and sculpture