A capability lands over SSH first. If it belongs to the triage/review/respond loop, it lands on the web in the same merge request. Anything whose input is a credential — secrets, mirror tokens, API tokens, session minting — stays SSH-only by design: the web dispatcher refuses SSHOnly commands outright.

Rows are one page or one action each. Grouped rows hide gaps, twice now: "browse, log, blame, search" read as covered while blame had no command at all, and "build list, log" read as covered while the job list a trigger can name had none (krz/gitbay#50), leaving the picker browser-only and the iOS build screen unable to say more than the log.

Creating from a fork works anywhere the source can be typed as owner/name:branch; only the web lacks it. Retargeting moves an open merge request onto another branch of the same repository and stales the reviews, since an approval was of the diff against the old branch.

Issue, MR and release bodies, and their comments, carry the markup they were written in — --format md|org on create, comment and edit, stored alongside the text so changing a preference later cannot reinterpret prose that already exists. Every surface renders the stored format; the no above is the absence of a picker on the web form and in the iOS composer, both of which write markdown. Diff-line comments have no format column and are always markdown.

No row is web-only any more. Blame, file editing, log at a ref, archive, the public listing and the wiki were all in that state — a handler reading git or the store directly instead of dispatching a command — until krz/gitbay!99, !101 and !102 gave them commands.

The wiki row covers reading. Editing a wiki is a push to <repo>.wiki.git on every surface, including the web, so there is no edit row to have parity on.

n/a marks a capability deliberately absent from a surface rather than missing from it. Archive download is n/a on iOS: the read API carries a command's stdout as a JSON string, so a gzip stream cannot survive it, and the app has nowhere useful to put a tarball — the brief rules out local git, so there is no clone, checkout or build to feed. The web's route stays the way to get one.

A README or wiki page's org renders per surface: the web through go-org, the iOS client through the shared OrgSwift package (krz/org-swift). OrgSwift is held to orgo's output by the krz/org-conformance corpus — golden renderings from orgo, itself diffed against Emacs ox-html — so constructs the iOS client used to approximate (tables, footnotes, timestamps, heading tags, nested lists) now render the way the reference does. go-org is not yet on the corpus.

explore is the listing without a query; repo search is the one with.

About text renders as markdown or org-mode per the about_format it was stored with. The iOS Profile decoder lists its keys explicitly, so it ignores about and links rather than breaking on them.

profile set carries description, website, about and links. It is not SSHOnly — nothing about a bio is a credential, and the JSON API runs it — but no surface has ever offered a form, so the no above is missing UI rather than a rule.

issue list, mr list, repo list, and feed take --limit <n> and --cursor <c>. Cursors are opaque; each page carries the next one. Without the flags a list stays complete, so existing scripts are unchanged. The web renders server-side and does not paginate; iOS pages with the cursors.

Build secrets, mirror configuration and tokens, custom domain claims, API token minting, web session minting, deploy keys, account and instance administration. Deleting or transferring a repository is also CLI-only: both want a typed confirmation, not a button.

These are the only rows where a no is intended. Everywhere else a no is work outstanding, and n/a means a surface cannot usefully carry the capability at all — see the archive note above.