Split refactoring problems into init, options and final.

pkg/analysis_server/tool/spec/spec_input.html

Index: pkg/analysis_server/tool/spec/spec_input.html
diff --git a/pkg/analysis_server/tool/spec/spec_input.html b/pkg/analysis_server/tool/spec/spec_input.html
index 54c0a58782ad9429eebb25d5e70e594fe7518407..dccffeb366ea62a7a24bab1907f68c146036535d 100644
--- a/pkg/analysis_server/tool/spec/spec_input.html
+++ b/pkg/analysis_server/tool/spec/spec_input.html
@@ -1223,11 +1223,30 @@
           </field>
         </params>
         <result>
-          <field name="problems">
+          <field name="initialProblems">
             <list><ref>RefactoringProblem</ref></list>
             <p>
-              The status of the refactoring. The array will be empty
-              if there are no known problems.
+              The initial status of the refactoring, i.e. problems related to
+              the context in which the refactoring is requested.
+              The array will be empty if there are no known problems.
+            </p>
+          </field>
+          <field name="optionsProblems">
+            <list><ref>RefactoringProblem</ref></list>
+            <p>
+              The options validation status, i.e. problems in the given options,
+              such as light-weight validation of a new name, flags
+              compatibility, etc.
+              The array will be empty if there are no known problems.
+            </p>
+          </field>
+          <field name="finalProblems">
+            <list><ref>RefactoringProblem</ref></list>
+            <p>
+              The final status of the refactoring, i.e. problems identified in
+              the result of a full, potentially expensive validation and / or
+              change creation.
+              The array will be empty if there are no known problems.
             </p>
           </field>
           <field name="feedback" optional="true">