fix: make delete CLI path a --path option, clarify FTS guard comment

Reviewer feedback:
- path as a second positional arg was unreachable (Click assigns
  left-to-right, so a path string would land in repo_id). Now --path/-p.
- Added comment explaining fts is always initialized in lifespan, so
  the None guard is purely defensive.

Author: Selene29

packages/cli/src/repowise/cli/commands/delete_cmd.py

@@ -17,7 +17,7 @@
 @click.command("delete")
 @click.argument("repo_id", required=False, default=None)
 @click.option("--force", "-f", is_flag=True, default=False, help="Skip confirmation prompt.")
-@click.argument("path", required=False, default=None)
+@click.option("--path", "-p", default=None, help="Path to the repository directory.")
 def delete_command(repo_id: str | None, force: bool, path: str | None) -> None:
     """Delete a repository and all its generated data."""
     repo_path = resolve_repo_path(path)

packages/server/src/repowise/server/routers/repos.py

@@ -138,7 +138,9 @@ async def delete_repo(
     # Collect page IDs before CASCADE deletes the Page rows
     page_ids = await crud.list_page_ids(session, repo_id)
 
-    # Clean up FTS index (FTS5 virtual table has no FK cascade)
+    # Clean up FTS index (FTS5 virtual table has no FK cascade).
+    # fts is always initialized in the lifespan before the server accepts
+    # requests, so this guard is purely defensive.
     if fts is not None:
         await fts.delete_many(page_ids)