On InvoiceKit, I separated four scope lines that often get collapsed into “Firebase setup”: sign-in, session persistence, owner-scoped data access, and live transition checks. Each line needs a different acceptance test. In a client brief, name the user action and the proof for each one—for example, reopening an authenticated session or confirming an invoice status against the live service. That turns a vague backend estimate into reviewable delivery criteria.