update PoC in DevPlan to reflect what was actually achieved

Doc/DevelopmentPlan/DevelopmentPlan.tex

@@ -81,11 +81,13 @@ To create a semantic history of the development process, labels will be used ext
 To demonstrate the feasibility of the project, a proof of concept (PoC) will be developed. The PoC will demonstrate the following features:
 
 \begin{itemize}
-	\item Basic dungeon generation, including rooms, corridors, and placement of gold, items, monsters, and traps
-	\item Line of sight and pathfinding implementation
-	\item Non-functional items and traps
-	\item Minimum viable monster AI
-	\item Basic movement and very simple environmental interaction (acquiring items, basic combat)
+	\item Basic dungeon generation, including a connected graph of rooms and corridors.
+	\item Rendering the level and any produced menus.
+	\item The start screen and high-score screen.
+	\item Read and written high score file.
+	\item Line of sight and pathfinding implementation.
+	\item Basic movement.
+	\item Implemented but not integrated traps, items, and monsters.
 \end{itemize}
 
 If there are no issues implementing the features above, it shall be assumed that there are no fundamental flaws with the requirements or architectural design of the project.  Several major features of the project have been excluded from this demonstration (advanced item manipulation and traps, hidden passageways, complex monster AI, etc.) because the PoC is otherwise too ambitious.  As long as the underlying code is well-architectured, the more sophisticated features of the application should be able to flow out of the PoC foundation.\\