OutputBuilderCommon
Inherits OutputBuilder < Reference < Object
Constants
Parameter kinds already covered by the dedicated render sections above (trees, named lists, query params baked into URL, or body payloads).
Fixed order so plain output is deterministic. The protocol drives the prefix and "path" comes from path params, so neither is repeated here. component_type/exported/explicit appear on explicit-intent (filter-less exported) and provider surfaces; the *_permission / grant_uri_permissions / path_permissions keys only on providers. Absent keys are skipped per endpoint.
Mobile entry points keep method = "GET" internally; the protocol carries the real semantics and drives the display prefix.
Parameter kinds drawn as one cyan comma-joined line of names, in emission
order: {param_type, label}.
Parameter kinds drawn as an indented tree under a ○ <label>: header,
in emission order: {param_type, label, name/value separator}. Both are
green and both mark params the analyzer could not resolve; the separator
follows the wire syntax of the thing being printed (Name: value for a
header, name=value for a cookie).
Protocols the rest of the line already tells the reader about, so a badge
would only repeat it: http is the default and says nothing, the mobile
protocols drive the SCHEME/INTENT/UNIVERSAL/PROVIDER prefix, and cli is
spelled out by the cli:// URL.
Instance methods
The plain report is the only format that frames itself — a heading over
the endpoint list, and the passive-scan findings appended below a second
one. Both used to sit in NoirRunner#report, which forced the runner to
special-case "is this the default format?" on either side of a dispatch
that otherwise treats every format alike.