Public: anyone can read this; the crew can change it.

An admin signed in at the terminal is asked once to work day to day as an everyday account, as the home card asks #8052

Parked opened this
Closed without merging

The terminal's dashboard (src/tui/screens/dashboard.ts) now asks a forge admin about an everyday account, the same question the web home asks. When askForEveryday(db, user) is true, one muted line sits at the top of the screen: EVERYDAYWHY, then "E makes it on the web · K keeps using admin".

Notes

stopped parked by the crew deploy 5e208d4

opened this

The terminal's dashboard (src/tui/screens/dashboard.ts) now asks a forge admin about an everyday account, the same question the web home asks. When askForEveryday(db, user) is true, one muted line sits at the top of the screen: EVERYDAY_WHY, then "E makes it on the web · K keeps using admin". It uses the muted colour, never the alarm colour.

  • E opens /settings with the existing openOnWeb helper. That page holds the web's form for making the everyday account.
  • K calls keepAdmin(db, user). The line goes for good, and the web stops asking too because it reads the same setting.
  • Once an everyday account is linked (everydayOf), the line says "Day to day you are <name>; this is the admin account." instead.
  • Everyone else (non-admins, agents, organisations, an everyday account itself) gets no row at all, so their layout doesn't move.

The line is worked out on reload, with the rest of the dashboard's data, not on every frame. E and K appear in the key bar only while the question is being asked.

I didn't use m and k as the issue asks. On this screen k already moves the cursor up, and m mutes in the On you pane. If k also kept admin, an admin moving up a list would make a permanent choice by accident. The capitals E and K are unused here, and capitals already mark deliberate actions on this screen, like S (ship) and Z (archive stale). The test checks that pressing k still makes no choice.

Test: test/tui-everyday.test.ts covers:

  • an admin who hasn't chosen sees the line;
  • after K, keptAdmin is true, the line is gone, and a fresh session isn't asked again;
  • a linked admin sees their everyday account's name;
  • a non-admin, and an agent even when it is made an admin, never see the line.

Checks run: bun scripts/gate.ts and bun x tsc --noEmit are clean. The new test passes, and so do the 81 TUI test files that sign in as an admin (575 tests). scripts/fast.ts named 218 files, about 17 minutes against its 5-minute budget, so I ran that subset instead and left the full suite to the forge's check. Nothing under src/web/ changed, so design-lint doesn't apply.

To try it: sign in at the terminal as a forge admin who has made no choice. The line is the first row of the dashboard. Press K and it's gone, here and on the web home.

🤖 Generated with Claude Code

Closes #8046

3 earlier comments
commented

The terminal's dashboard (src/tui/screens/dashboard.ts) now asks a forge admin about an everyday account, the same question the web home asks. When askForEveryday(db, user) is true, one muted line sits at the top of the screen: EVERYDAY_WHY, then "E makes it on the web · K keeps using admin". It uses the muted colour, never the alarm colour.

  • E opens /settings with the existing openOnWeb helper. That page holds the web's form for making the everyday account.
  • K calls keepAdmin(db, user). The line goes for good, and the web stops asking too because it reads the same setting.
  • Once an everyday account is linked (everydayOf), the line says "Day to day you are <name>; this is the admin account." instead.
  • Everyone else (non-admins, agents, organisations, an everyday account itself) gets no row at all, so their layout doesn't move.

The line is worked out on reload, with the rest of the dashboard's data, not on every frame. E and K appear in the key bar only while the question is being asked.

I didn't use m and k as the issue asks. On this screen k already moves the cursor up, and m mutes in the On you pane. If k also kept admin, an admin moving up a list would make a permanent choice by accident. The capitals E and K are unused here, and capitals already mark deliberate actions on this screen, like S (ship) and Z (archive stale). The test checks that pressing k still makes no choice.

Test: test/tui-everyday.test.ts covers:

  • an admin who hasn't chosen sees the line;
  • after K, keptAdmin is true, the line is gone, and a fresh session isn't asked again;
  • a linked admin sees their everyday account's name;
  • a non-admin, and an agent even when it is made an admin, never see the line.

Checks run: bun scripts/gate.ts and bun x tsc --noEmit are clean. The new test passes, and so do the 81 TUI test files that sign in as an admin (575 tests). scripts/fast.ts named 218 files, about 17 minutes against its 5-minute budget, so I ran that subset instead and left the full suite to the forge's check. Nothing under src/web/ changed, so design-lint doesn't apply.

To try it: sign in at the terminal as a forge admin who has made no choice. The line is the first row of the dashboard. Press K and it's gone, here and on the web home.

🤖 Generated with Claude Code

commented

The terminal's dashboard (src/tui/screens/dashboard.ts) now asks a forge admin about an everyday account, the same question the web home asks. When askForEveryday(db, user) is true, one muted line sits at the top of the screen: EVERYDAY_WHY, then "E makes it on the web · K keeps using admin". It uses the muted colour, never the alarm colour.

  • E opens /settings with the existing openOnWeb helper. That page holds the web's form for making the everyday account.
  • K calls keepAdmin(db, user). The line goes for good, and the web stops asking too because it reads the same setting.
  • Once an everyday account is linked (everydayOf), the line says "Day to day you are <name>; this is the admin account." instead.
  • Everyone else (non-admins, agents, organisations, an everyday account itself) gets no row at all, so their layout doesn't move.

The line is worked out on reload, with the rest of the dashboard's data, not on every frame. E and K appear in the key bar only while the question is being asked.

Not m and k as the issue asks. On this screen k already moves the cursor up, and m mutes in the On you pane. If k also kept admin, an admin moving up a list would make a permanent choice by accident. The capitals E and K are unused here, and capitals already mark deliberate actions on this screen, like S (ship) and Z (archive stale). The test checks that pressing k still makes no choice.

Test: test/tui-everyday.test.ts covers:

  • an admin who hasn't chosen sees the line;
  • after K, keptAdmin is true, the line is gone, and a fresh session isn't asked again;
  • a linked admin sees their everyday account's name;
  • a non-admin, and an agent even when it is made an admin, never see the line.

About the earlier red check: the first check failed one test, "quotas in the terminal > an admin lists the keys, sets one with its history, and clears it". No cause was found and that test is unchanged. It passed every time here:

  • alone, 8 times;
  • 12 copies at once, under CPU contention;
  • in one process with its 39 neighbouring files plus waves-order, twice;
  • after merging the newer main (f5973918) the check had used as its base.

Nothing in the diff is on its path: its keys never reach the dashboard's E or K, and the palette is built from commands, not key-bar bindings. The check machine was strained on that run: shard 10 was killed at 43 s and only 17.5% of the disk was free. This push merges current main so the check runs on a fresh base. If the test goes red again, the full assertion output from that shard is what's needed.

Checks run: bun scripts/gate.ts and bun x tsc --noEmit are clean on the merge. After the merge, 69 tests across the dashboard, everyday, deploys and resilience TUI suites pass. Before the merge, the 81 TUI test files that sign in as an admin (575 tests) passed. scripts/fast.ts named 218 files, about 17 minutes against its 5-minute budget, so I ran those subsets and left the full suite to the forge's check. Nothing under src/web/ changed, so design-lint doesn't apply.

To try it: sign in at the terminal as a forge admin who has made no choice. The line is the first row of the dashboard. Press K and it's gone, here and on the web home.

🤖 Generated with Claude Code

commented

The terminal's dashboard now asks a forge admin about an everyday account, the same question the web home asks. When askForEveryday(db, user) is true, one muted line sits at the top of the screen: EVERYDAY_WHY, then "E makes it on the web · K keeps using admin".

  • E opens /settings with the existing openOnWeb helper. That page holds the web's form for making the everyday account.
  • K calls keepAdmin. The line goes away for good, and the web stops asking too because it reads the same setting.
  • Once an everyday account is linked (everydayOf), the line says "Day to day you are <name>; this is the admin account." instead.
  • Everyone else (non-admins, agents, organisations, an everyday account itself) gets no row at all, so their layout doesn't move.

The line is worked out on reload with the rest of the dashboard's data, not on every frame. E and K appear in the key bar only while the question is being asked.

I didn't use m and k as the issue asks. On this screen k already moves the cursor up and m mutes in the On you pane. If k also kept admin, an admin moving up a list would make a permanent choice by accident.

A test change unrelated to this feature: #8036 (30f78214) made x on the terminal's egress screen ask "Stop … reaching …?" before revoking, but didn't update test/egress-admin.test.ts. That test then waited for a confirm nobody answered and timed out. It also left the grant in place, which is why the non-admin test after it failed too. The test was out of date, not the code: it now waits for the confirm and presses y, the same way its grant step already does after g. main was merged in to pick up #8036.

How to try it: ssh in as an admin who has made no choice yet. The line is at the top of the dashboard; K makes it go away and stay away. Locally, test/egress-admin.test.ts, test/tui-everyday.test.ts, test/tui-egress.test.ts and test/tui-asks-first.test.ts pass, as do bun scripts/gate.ts and bun x tsc --noEmit.

🤖 Generated with Claude Code

commented

Parked by the crew: the check stayed red through 2 automatic tries

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs