Reorganize documentation

README.md

@@ -112,7 +112,7 @@ Frontend deploys to **Vercel**, backend (with managed Postgres) deploys to
 The repo includes a [`render.yaml`](./render.yaml) blueprint so Render
 provisions the backend and the database in one click.
 
-See [DEPLOYMENT.md](./DEPLOYMENT.md) for the step-by-step guide.
+See [docs/deployment.md](./docs/deployment.md) for the step-by-step guide.
 
 ## Notes
 

docs/README.md

@@ -0,0 +1,13 @@
+# Documentation
+
+Project documentation for the Forgeng monorepo. For setup and a high-level
+overview, start with the [root README](../README.md).
+
+## Contents
+
+- **[deployment.md](./deployment.md)** — How the frontend (Vercel) and backend
+  (Render + Postgres) deploy, environment variables, and free-tier caveats.
+- **[student-features.md](./student-features.md)** — Feature proposals for the
+  student portal, grounded in the current code and data model.
+- **[admin-completion-todo.md](./admin-completion-todo.md)** — Working TODO for
+  wiring up admin actions against the backend.

DEPLOYMENT.md → docs/deployment.md

@@ -47,7 +47,7 @@ URL automatically.
 
 ## 2. Backend → Render
 
-The repo ships with a [`render.yaml`](./render.yaml) blueprint that
+The repo ships with a [`render.yaml`](../render.yaml) blueprint that
 provisions the web service and the Postgres database in one click.
 
 ### One-time setup