docs: a Command line page for sluiceway v0.45.0, its commands, their --json answers and exit codes

.gitmodules

@@ -1,4 +1,4 @@
 [submodule "vendor/sluiceway"]
 	path = vendor/sluiceway
 	url = https://github.com/sluiceway/sluiceway.git
-	branch = v0.42.2
+	branch = v0.45.0

src/content/docs/hosted-app/using-the-app.mdx

@@ -95,6 +95,10 @@ on GitHub.
 Ticking and Rescan from the app work in a repo whose `sluiceway.yaml` names `sluiceway[bot]` in
 `recordWriters`, and in any other repo they open the dashboard on GitHub.
 
+You can also tick and rescan from a terminal, or have a coding agent do it with a token you
+make: <a href={page("hosted-app/command-line")}>the command line</a> asks the app, which judges
+it by the same rules.
+
 ## Rescan
 
 **Rescan** in the top bar asks for a <a href={glossary("Full scan")}>full scan</a>: of the repo
@@ -132,6 +136,9 @@ who merged, the commit, and the result in the trail's words. A deploy outside th
 flagged in red, "outside the dashboard", and names nobody, because the tool's history never says
 who.
 
+A tick from <a href={page("hosted-app/command-line")}>the command line</a> counts as the person
+whose token it used, and its line says "via the command line".
+
 Filter by repo, by stack or to the flagged lines only. Each filter is a plain link, so a filtered
 log has an address you can paste into a ticket. **CSV** downloads what the page shows, with the
 same filters, the time in UTC and the whole commit.