For now I've simply set HALCYON_NO_AUTOUPDATE=1 to prevent this:
2014-11-05T12:25:52.660167+00:00 heroku[api]: Set HALCYON_NO_AUTOUPDATE config vars by ...
2014-11-05T12:25:52.660167+00:00 heroku[api]: Release v316 created by ...
2014-11-05T12:25:52.789571+00:00 heroku[web.1]: State changed from up to starting
2014-11-05T12:25:54.864142+00:00 heroku[web.1]: Starting process with command `/app/.halcyon/slug/bin/circuithub-api Staging -p 28601`
2014-11-05T12:25:55.036800+00:00 heroku[web.1]: Stopping all processes with SIGTERM
2014-11-05T12:25:56.265594+00:00 app[web.1]: -----> Setting buildpack paths
2014-11-05T12:25:56.265612+00:00 app[web.1]: *** DEBUG: .profile.d/buildpack.sh
2014-11-05T12:25:56.362218+00:00 heroku[web.1]: Process exited with status 143
2014-11-05T12:25:56.704846+00:00 app[web.1]: -----> Setting Halcyon paths
2014-11-05T12:25:56.704856+00:00 app[web.1]: *** DEBUG: halcyon/src/paths.sh
2014-11-05T12:25:56.739107+00:00 app[web.1]: -----> Setting Halcyon paths
2014-11-05T12:25:56.739115+00:00 app[web.1]: *** DEBUG: halcyon/src/paths.sh
2014-11-05T12:25:58.355622+00:00 heroku[web.1]: State changed from starting to up
It appears that halcyon goes through it auto-update cycle whenever a Heroku app is unidled (with a 1X app anyway)
For now I've simply set
HALCYON_NO_AUTOUPDATE=1
to prevent this: