Minor but breaking changes

This is, for the most part, cleanup and standards-compliance stuff—prefixing category method names, properly naming the files containing categories, whitespace, etc.—but also fixes assumptions about how core data model classes are named.  ***NOTE: The method name changes BREAK API compatibility.***  I suggest labeling and tagging this as version 1.0.0, with earlier incompatible versions being considered 0.x.  I've also included a podspec file that assumes that this will be labeled and tagged 1.0.0.
You are correct—this doesn't work.  I've now added a test for this (which required adding a second entity) to the sample project.
[...]
Got a quick fix?  If not, got a few minutes to talk about how to fix it?