Add side panels, task selection, graph animation, and project docs

- Foldable left panel (user profile) and right panel (task details)
- Clicking a task in the list or graph node selects it and shows details
- Both views (task list + graph) always mounted via absolute inset-0 for
  correct canvas dimensions; tabs toggle visibility with opacity
- Graph node selection animation: other nodes repel outward (charge -600),
  then selected node smoothly slides to center (500ms cubic ease-out),
  then charge restores to -120 and graph stabilizes
- Graph re-fits on tab switch and panel resize via ResizeObserver
- Fix UUID string IDs throughout (backend returns UUIDs, not integers)
- Add TaskDetailPanel, UserPanel components
- Add CLAUDE.md project documentation

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

frontend/node_modules/next/dist/esm/build/build-context.js

@@ -0,0 +1,35 @@
+// A layer for storing data that is used by plugins to communicate with each
+// other between different steps of the build process. This is only internal
+// to Next.js and will not be a part of the final build output.
+// These states don't need to be deeply merged.
+let pluginState = {};
+export function resumePluginState(resumedState) {
+    Object.assign(pluginState, resumedState);
+}
+// This method gives you the plugin state with typed and mutable value fields
+// behind a proxy so we can lazily initialize the values **after** resuming the
+// plugin state.
+export function getProxiedPluginState(initialState) {
+    return new Proxy(pluginState, {
+        get (target, key) {
+            if (typeof target[key] === "undefined") {
+                return target[key] = initialState[key];
+            }
+            return target[key];
+        },
+        set (target, key, value) {
+            target[key] = value;
+            return true;
+        }
+    });
+}
+export function getPluginState() {
+    return pluginState;
+}
+// a global object to store context for the current build
+// this is used to pass data between different steps of the build without having
+// to pass it through function arguments.
+// Not exhaustive, but should be extended to as needed whilst refactoring
+export const NextBuildContext = {};
+
+//# sourceMappingURL=build-context.js.map