Update dependencies

Author: chriscarrollsmith

.gitignore

@@ -11,4 +11,6 @@ package-lock.json
 package.json
 .specstory
 .cursorrules
-.cursor
+.cursor
+repomix-output.txt
+artifacts/

docs/customization.qmd

@@ -71,9 +71,9 @@ We also create POST endpoints, which accept form submissions so the user can cre
 
 #### Customizable folders and files
 
-- FastAPI application entry point: `main.py`
-- FastAPI routes: `routers/`
-    - User authentication endpoints: `account.py`
+- FastAPI application entry point and homepage GET route: `main.py`
+- FastAPI POST routes: `routers/`
+    - User authentication endpoints: `authentication.py`
     - User profile management endpoints: `user.py`
     - Organization management endpoints: `organization.py`
     - Role management endpoints: `role.py`
@@ -106,6 +106,8 @@ Most everything else is auto-generated and should not be manually modified.
 
 ### Code conventions
 
+The GET route for the homepage is defined in the main entry point for the application, `main.py`. The entrypoint imports router modules from the `routers/` directory, which contain the other GET and POST routes for the application. In CRUD style, the router modules are named after the resource they manage, e.g., `account.py` for account management.
+
 We name our GET routes using the convention `read_<name>`, where `<name>` is the name of the page, to indicate that they are read-only endpoints that do not modify the database. In POST routes that modify the database, you can use the `get_session` dependency as an argument to get a database session.
 
 Routes that require authentication generally take the `get_authenticated_account` dependency as an argument. Unauthenticated GET routes generally take the `get_optional_user` dependency as an argument. If a route should *only* be seen by authenticated users (i.e., a login page), you can redirect to the dashboard if `get_optional_user` returns a `User` object.