internal/httpd/builds.go builds both pages from the store and from git
rather than dispatching commands:
builds(line 12) callss.st.ListBuilds, and parses.gitbay/ci.ymlfrom the default branch inline to populate the trigger picker.build(line 40) callss.st.BuildByNumberands.st.BuildLog.
build list, build show and build log all exist, so nothing is
stranded there — but the page can drift from them, which is the reason
the registry exists.
The job list is the real gap: no command returns the jobs a trigger can
name, so only the browser can offer them. iOS prefills the most recent
build's job and makes the user type the rest. Needs a build jobs <owner/name> command reading the same config the scheduler reads, then
both pages dispatching it.
Found auditing the route table against the iOS argv set. The Parity page carries "build list, log" and "build trigger" as grouped rows, which read as covered.