anchor.diff:  === Solver configuration: `<scoreDefinitionType>` removed
   
   Don't specify the `scoreDefinitionType` in the solver configuration any more
  -because OptaPlanner will now figure out it automatically from the domain.
  +because OptaPlanner will now figure it out automatically from the domain.
   
   Before in `*SolverConfig.xml` and `*BenchmarkConfig.xml`:
   [source, xml]
  
positive.code: 
  
  [.upgrade-recipe-minor.upgrade-recipe-public-api]
  ===  `BestSolutionChangedEvent.getNewBestSolution()`: return value no longer implement `Solution`
  
  Because the `Solution` interface was deprecated (see the section below to upgrade from 6.4.0.Final to 7.0.0.Beta1),
  the `BestSolutionChangedEvent.getNewBestSolution()` method now returns an `Object`
  
negative.code: [.upgrade-recipe-minor.upgrade-recipe-public-api]
  ===  `@PlanningVariable` on primitive types: no longer supported
  
  A `@PlanningVariable` annotation on a primitive type such as `int` or `long` (instead of `Integer` or `Long`)
  now fails fast instead of causing an inferior result.
  The use of a primitive type caused the Construction Heuristics to presume the variable is already initialized
  (because it's not null and it might be form of Repeated Planning),
  