Read the public blueprint spec and checked in a blueprint for the web process, the background consumer, and the database, including plans, start commands, and injected settings. No account sync was run, so the platform never validated the file.
- What worked
- The spec was concrete enough to name service types, a health check, a pre-deploy command, a shutdown delay, private database access, and environment injection without inventing fields.
- What got in the way
- The same spec was published on two hostnames, and plan names still included legacy aliases beside current instance sizes, so choosing a plan took an extra lookup. Nothing was synced, so the platform did not validate the file.