anchor.diff:  ###health-check
   File location: `<plan>/hooks/health-check`
   
  -This hook is run when the Chef Habitat HTTP API receives a request at `/health`.
  +This hook is run periodically on a configurable interval.
   
   The `health-check` script must return a valid exit code from the list below.
   
  
positive.code: * [health-check](#health-check)
  * [init](#init)
  * [install](#install)
  * [reload](#reload)
  * [reconfigure](#reconfigure)
  * [suitability](#suitability)
  * [run](#run)
  
negative.code: 
  An `install` hook, unlike other hooks, will not have access to any census data exposed via binds or the `svc` namespace. Also, configuration in `svc_config_path` is not accesible to an `install` hook. If an `install` hook needs to utilize templated configuration files, templates located in the `svc_config_install_path` may be referenced. This location will contain rendered templates in a package's `config_install` folder. Finally, any configuration updates made during a service's runtime that would alter an `install` hook or any configuration template in `svc_config_install_path` will not cause a service to reload.
  
  ###reconfigure
  File location: `<plan>/hooks/reconfigure`
  
  A `reconfigure` hook can be written for processes that can respond to changes in `<plan>/config` without requiring a restart. This hook will execute **instead** of the default behaviour of restarting the process. `{{pkg.svc_pid_file}}` can be used to get a handle on the `PID` of the service.
  
  The `reconfigure` hook is not necessarily run on every change to `<plan>/config`. The `reconfigure` hook will not be run if the service restarts before the `reconfigure` hook has run. The restart is considered sufficient for reconfiguring the service. For example, when applying a configuration that changes both the `run` hook and `<plan>/config`, the change to the `run` hook will trigger a restart and therefore the `reconfigure` hook will not be run. 
  
  Habitat does not support changing the `PID` of the underlying process in any lifecycle hook. If part of a service's reconfiguration relies on changing the `PID`, you should not provide a `reconfigure` hook and rely on the default behaviour of restarting the service.
  
  ###suitability
  File location: `<plan>/hooks/suitability`
  