Where the running build's source lives.
Branch rather than commit, deliberately. A pinned /tree/<sha> answers "the source of
which version" most precisely, which is what §13 is about — but it rots: a fork with a
private repository, a rewritten history or a squashed merge leaves the player holding an
address that 404s, which is a worse answer than a branch that resolves. The exact commit
is not lost by choosing the branch: About prints it one row above this as
v<calver> (<branch>@<commit>), so a reader has both the precise version and a URL that
works.
base is the operator's own repository once mica_source_url reaches this (still to
come); until then every phone points at upstream, which is the honest answer for a server
running an unmodified copy and the wrong one for a fork. That gap is why the offer above
says "where this build says its source lives" rather than asserting it.
MICA-70's one privacy-disclosure string, read by both the first-run notice (
shell/PrivacyNotice.svelte) and the permanent copy in Settings > About — plain text with nothing reactive about it, so there is no facet or permission to gate it behind (the same reasoningMICA_BUILD_INFOabove already rests on).