the problem is that there's no apostrophe in that.  autocomplete works from the actual name, not the key.  it would be awfully tricky to blend the two.

That reminds me, for a while I've been wanting to ticket something like make name of new plus card use exact name of constitutent cards, so that eg in this case it would be "Peter Kindfield's House+zip code" when it's created. That is, I've seen a number of times/places when a new card like +zip code is created and the trunk name has a "_" in it instead. Does that make sense?

That is supposed to be the default behavior unless you explicitly say to do something different. If we can find cases where some sort of name variant is being used unintentionally, then yes let's ticket and fix.  If we can't reproduce it, I don't think we're ready for a ticket.

On the other hand, Gerry feels strongly that it should be possible for descendants to use name variants, and in fact he thinks Wagn over-corrects. I don't feel strongly about this issue, but at a minimum I'd like there to be clear, easy-to-understand patterns.

(note: I would use "ancestor" rather than constituent)