docs: revise REQ-010/163 for archive upload, add REQ-178/179

docs/requirements.md

@@ -62,8 +62,9 @@ changes.
 
 ## B. Video archive
 
-- **REQ-010** — The video archive lives at a local path (disk or mount); videos are **not
-  uploaded** through the browser.
+- **REQ-010** — The video archive lives at a local path (disk or mount). Videos may be
+  copied in from disk **or uploaded through the browser** into an existing date folder
+  (REQ-178).
 - **REQ-011** — Archive structure: `<video_root>/<date>/<batch>.<ext>`. The system lists the
   dates, and within each date the videos with their batch labels parsed from the filename.
 - **REQ-012** — Each video shows its duration, resolution, and whether it has already been
@@ -71,6 +72,13 @@ changes.
 - **REQ-013** — Videos play in the browser with seeking (HTTP Range), without copying the
   file first.
 
+- **REQ-178** — The Video Archive page can create a `YYYY-MM-DD` folder and upload videos
+  into it. Uploads are streamed to disk, never overwrite an existing file, and only accept
+  `video.VIDEO_EXTS`.
+- **REQ-179** — The Video Archive page shows a button that copies the archive's host path
+  to the clipboard, as a Linux path and as a Windows (`\\wsl.localhost\<distro>\...`) path
+  when known.
+
 ## C. Trim & frame extraction
 
 - **REQ-020** — The user sets the in/out range with a timeline slider on the player, and can
@@ -316,8 +324,9 @@ changes.
   Each clip carries a sidecar with the server's start time, which the app trusts over reading
   the burned-in overlay. Archive folder names remain calendar dates; the app derives cycles
   from the real start time, so the folder name is never read as a date.
-- **REQ-163** — Nothing in the archive is moved, renamed or written to; it is mounted
-  read-only. The grouping lives in an index beside it. Timestamps that could not be read, or
+- **REQ-163** — Nothing existing in the archive is moved, renamed or deleted; only
+  user-initiated uploads and folder creation append to it. The grouping lives in an index
+  beside it. Timestamps that could not be read, or
   were read with low confidence, are flagged and can be hand-entered; a hand-entered time
   outranks any reading and is never overwritten by a rescan.