Invoice Lifecycle and Shared Term Browser Suite

Verification Boundary

The browser exercises invoice lifecycle screens with mock data, including shared payment-term selection and the initial working-unit context.

What This Suite Proves

The file contains assertions for editing terms and the resulting due date. Those consumer assertions have no complete Books acceptance binding; the remaining lifecycle examples belong to Transactions.

What It Does Not Prove

Mock invoice state does not prove live issuance, ledger writes or payment-term deletion protection. No execution result is claimed.

Real Dependencies and Test Doubles

The invoice components and browser interactions are real. Local response handlers supply configuration choices and invoice mutations.

Must Not Be Doubled

The invoice editor, term selector and displayed due-date calculations remain the production code exercised by these examples.