anchor.diff:  
   * Action invocations: +
   
  -If an action returns a collection that includes the object, then the object will be excluded from the list when rendered. If it returns a single object and the user does not have access to that object, then the action will seemingly return `null`
  +If an action returns a collection that includes the object, then the object will be excluded from the list when rendered.
  +If it returns a single object and the user does not have access to that object, then the action will seemingly return `null`
   
   * Collections: +
   
  
positive.code: (`false`)
  |Whether deprecated facets should be ignored or honoured.  +
  +
  By default all deprecated facets are honoured; they remain part of the metamodel.  If instead this property is set to
  `true` then the facets are simply not loaded into the metamodel and their semantics will be excluded.  +
  +
  In most cases this should reduce the start-up times for the application.  However, be aware that this could also
  substantially alter the semantics of your application.  To be safe, we recommend that you first run your application
  using `isis.reflector.validator.allowDeprecated` set to `false`; if any deprecated annotations etc. are in use, then
  the app will fail-fast and refuse to start.
  
  
  |`isis.reflector.facets.` +
  
negative.code: (`false`)
  |whether to disable the default recognizers registered by `ExceptionRecognizerCompositeForJdoObjectStore`. +
  
  This implementation provides a default set of recognizers to convert RDBMS constraints into user-friendly messages.
  In the (probably remote) chance that this functionality isn't required, they can be disabled through this flag.
  
  
  |`isis.services.` +
  