For what it's worth, there was a recent discussion on the developers' email list about nomenclature, as in "what is a part vs what is a component?" And it turns out that the answer isn't as simple as one might hope. Part of the problem is that (as noted) Kicad's developers (and users) speak many languages, and as such interpretation of those words differs. For example, I'm guilty of considering "part" and "component" synonymously, and one of the others on the developers' list suggested that they are not. To wit, a "part" can be a generic thing, like a resistor, a capacitor, an IC chip. And a "component" is more fully specified, such as a 10k0 1% 0805 resistor and an SN74LVC17PW Schmitt Trigger buffer.
A corollary to that discussion was, "the EESchema libraries, what do they hold, anyway, and when we edit something, what are we editing?" From a purely operational standpoint, the "library editor" in EESchema allows users to edit symbols and whether those symbols are parts (resistor, cap, etc, as defined above) or components (that 74LVC17) or "just a symbol" (like your power symbols VCC et all, and symbols which call out things that need to be on a BOM, etc etc). That kinda muddied the waters.
A second corollary follows from the history @Joan_Sparky discussed. Originally EESchema and pcbnew were separate programs. (Aside: there has been discussion about renaming these programs and the other Kicad utilities to basically unify them under the Kicad banner.) The original idea was that symbols and footprints should be separate. After all, why have a hundred op-amps in your symbol library when only one is sufficient? And why not have the ability to choose which footprint you want to use for your op-amp when you go to do the layout, as it doesn't matter what footprint you want when drawing the schematic? Hence, separate libraries and a utility (CvPCB) that lets the user do the footprint assignment after drawing the schematic.
Except: professional users (who design electronics for a living in a typical business environment) utterly abhor this whole CvPCB flow. I could list a whole bunch of reasons, but it comes down to this: these users (myself included) work from a vetted parts list (where the criteria includes non-design things like "can we buy this part?"). So anything in a component library must be complete. That is, an "atomic part." This requires that, for starters, there is no such thing as a generic op-amp. Instead, the library has a part OPA1652AID. And since we are familiar with the vendors' part naming, we include the suffix which indicates package. This requires that the library symbol include the correct footprint. The final required bit of information needed to make the symbol a complete component is a Part Number. Whether that is a manufacturer part number or a company/house part number is driven by your company's ERP requirements. At my day job, we have such an ERP system and everything that goes into a product is assigned a company part number. So that part number is in every library component symbol, so when a BOM is generated, the purchasing person can import it into her system and order parts as required.
And for the hobby/DIY/Maker users who do not have an ERP system and aren't building anything in production quantities, the original CvPCB flow works for them.
The good news is that Kicad support both use cases.
Sorry for the length.
The end result of the listserv naming discussion was that they were going to pick a nomenclature and document it so every user will be clear on what is meant. And again, that is especially important because of the multiple languages spoken by users. And if you choose to not RTFM, then I can't help you