v0.8.1 — smoke test: look at the data, then ask how to seed and who to log in as

Smoke test: look at the data, then ask how to seed and who to log in as.
/pspt:smoke now checks the local database before it visits any page.

Added

• Data and accounts step — before any visit, /pspt:smoke confirms the
  database is local (otherwise it stops), counts the rows in the tables the
  chosen pages read and the users per role, finds the project's own seed and
  reads whether it deletes data first, and works out which roles the pages
  need. Then it asks two questions:
  • Data: use what is already there · run the project's seed (saying what
    it deletes first) · generate a smoke seed — the fewest rows the pages need,
    built from data-spec.md, every row marked and removed again in clean-up
    · or "I'll seed it myself".
  • Accounts: one throwaway test user per role · the seed's accounts · or
    the user's own account, for this run only and never printed.
• Named logins in smoke.mjs — "logins": { "customer": …, "admin": … }
  opens one browser session per account; each target's auth names the
  account it visits as.

Changed

• Clean-up also removes generated seed rows (children first, by recorded id)
  and deletes a run plan that holds a password the user typed. Rows from the
  project's own seed stay, and the report says so.
• A role the API cannot grant is created through the app's own user service,
  or inserted with a password hashed by the app's own function — never plain
  text.

---

Full history: CHANGELOG.md