Lane 9 PR 5: J1 walks Admin's part; the first person to sign in owns the server (#735) #944
Loading…
Reference in a new issue
No description provided.
Delete branch "build/lane9-5-j1-admin"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #735 (lane 9 PR 5, J1's Admin leg).
Journey (
e2e/j1-first-campaign.spec.js):GET /api/setup/state'sskipped, with one "Set up X" link per skipped step (backups, what is kept, the models, Discord), and asserted absent when nothing is owed. The three projects share one DB, so this is conditional./admin, "Set up backups" is gone, andskippedno longer holdsbackups./admin, and the document doesn't scroll sideways./admin/*addresses, the?tab=backupredirect contract, full axe scans, IS-377's non-admin page and the Contents navigation.App bug found and fixed: nothing ever made the first administrator of a new server its owner (D68). Only the migration's backfill did, for servers that already existed.
routers/auth.pynow setsis_server_owner=(user_count == 0)besideis_admin.test_auth_callback.pyasserts the first user is the owner and a later one isn't. The column defaults to false, so the first-user assertion fails on main.Checks:
test_auth_callback.pyandtest_server_owner.py: 50 pass.changelog.d/735-j1-admin-leg.fixed.md.Coverage note: on a fresh CI database, desktop walks the setup wizard branch. The Admin leg's Save therefore runs in the keyboard project there (Enter), not as a mouse click. The page and assertions are the same.
🤖 Generated with Claude Code