Improve local development docs and start script

[chriszarate]

• Improve start and stop commands (no functional changes)
  • Better messaging
  • More consistent cleanup
  • Fix issues flagged by Shellcheck
  • Fix race condition that sometimes occurs by creating object cache first
• Update example API label to match documentation
• Improve local development documentation
• Add local playground blueprint
  • As documented with strong wording, this is not intended to be a development environment. But it is extremely useful to quickly validate changes.
  • My primary motivation, though, is to help users sidestep a footgun. Pointing @wp-now to blueprint.json can actually result in the current folder being wiped out. It's how I lost a lot of uncommitted progress on docs earlier this week. :/

Question: Is "monolith" a confusing term since we aren't shipping with documented decoupled capabilities? Should we make it the default for npm run start?

[jblz]

Question: Is "monolith" a confusing term

IMO, yes.

Should we make it the default for npm run start?

IMO, also yes.

[maxschmeling]

Question: Is "monolith" a confusing term

IMO, yes.

Should we make it the default for npm run start?

IMO, also yes.

Yes, I think defaulting to monolith would make sense.

I'm not sure if it's confusing or not. I do think it probably makes sense to just assume that our default environment is "monolith" and not necessarily talk about it as "equal" to a decoupled environment.