pub fn hosted_signup_intents(
did: &str,
username: &str,
transaction_id: Option<&str>,
provision_epoch: u64,
) -> Vec<EnrollmentIntent>Expand description
The enrollment intents one hosted signup journals (#698 Phase 2): the hosted DID and the account’s local username, both at the default label.
A hosted signup creates ONE account whose stable subject differs by
token profile: the atproto profile mints sub=<did> (PAR is
DPoP-mandatory there), while native Bearer-only clients (e.g. OpenCode)
take the non-atproto profile and mint sub=<username>. The clearance
resolver matches the enrollment table by exact subject, so enrolling
only the DID leaves every native-profile credential unlabeled (denied
NoClearance at the dispatch PEPs). Journaling both subjects keeps the
username an authority-owned enrollment key exactly like the JIT path
already does (append_jit_enrollment_intent journals the local
username), and both keys stay replay-idempotent per transaction.