skynet push -c fails when the topic titles of existing topics in the Content Spec don't match the topic titles in the database.

If the user is presented with a list of the actual topic titles and the topic titles in the Content spec, (s)he may verify that in fact the topics specified are the ones (s)he wants, and they have simply been subjected to minor edits in skynet since the Content Spec was last constructed / updated.

In this case it would be useful for the user to be able to do this:

skynet push -c(n|e) --db-canonical filename.txt

When invoked with the --db-canonical option, when the processor encounters a mismatch between a specified topic title, rather than throwing an error the processor rewrites the title in the Content spec with the title from the database.