chat: space space home tip; a conversation's tip covers the project after 15 quiet seconds

[ZeroPoint95]

Tips, cleaned up. Three things:

1. A missing tip

New tip: space space takes you back to home

• Shows in a conversation after the first message, and never on home.
• It's the first tip a conversation shows.
• Goes away for good once you press space space.

2. Conversation tips moved out of the footer

A tip used to replace the whole bottom row, so space space home and the other controls disappeared.

Now the controls always stay, and the tip sits at the bottom right, covering project: while it's up:

─ glm-5.3-flash:auto · ◇ asks ──────────────────────────────────────────  $0.00   idle ─
 ›
 opt+e effort · opt+a approvals · / commands · space space home   💡 space space takes you back to home ✕

• Waits 15 seconds. It appears only after 15s with no key, click, scroll or paste, counting from when the last answer finished or codeaf opened, whichever is later. This applies to conversations only; home is unchanged.
• Counted only when you can see it. A tip is used up after 6 sessions shown; a session counts only once the tip has actually been drawn, not just queued behind the 15s wait.
• ✕ closes it until you leave the conversation and come back. project: comes back as soon as the tip goes.
• Same 💡 bulb as home.
• It sits where the project sits, so it follows the task sidebar with no special handling.

3. Clearer settings line

Settings › Workspace › disable hints now reads: disable💡 tips everywhere (requires restart)

It still turns off every tip, on home and in conversations.

Review fixes

• Home's tips rotate again after space space. The gesture used to fire before home opened, so the /project tip jumped the queue on every trip home by two spaces. It now fires after home opens, from a conversation or a place. A new test drives two spaces from a conversation and checks that home's tip moves on; it fails without the fix.
• Tips are counted when drawn and wait from launch (above).
• The manual and change entry no longer mention codeaf config, which isn't a command.

Checked

• New tests cover the 15s wait, the ✕, and the settings line. The existing tip and footer tests pass, and the manual pages are updated.
• Tried it in the real app:
  • There was no tip right after an answer, and it appeared by itself after 15s.
  • A key hid it and brought project: back; it reappeared after 15s.
  • ✕ closed it, project: came back, and it stayed closed.
  • With disable hints on, no tip appeared.
• make test-touched passes.

🤖 Generated with Claude Code

[AbirAbbas]

I checked this on top of current dev. It's one commit behind (#1410), but it merges cleanly, and make pr-ready passes with #1496 merged in too. I also drove it in tmux on a real model, and the main flow holds:

• nothing for 15 s after an answer, then the 💡 tip over project: with the controls still on the left
• a key, click, scroll or paste hides it
• ✕ keeps it away until you leave the conversation
• space space retires the new tip, and /home and the Home tab don't

One regression to fix before merge: going home by two spaces stops Home's tips rotating.
noticeEvent(eventHomeGesture) runs before openHome() (input.go ~1316, placekeys.go ~449/459). So Home's tip is decided while the conversation is still in front, and there pick-a-project (armed only on Home) reads as unarmed. When Home opens it counts as "fresh" again and jumps the queue. Result: every trip home by two spaces shows /project sets the project folder for a new conversation, while the tab still rotates normally.

Repro with a throwaway test on chatTipLab:

• four trips of noticeEvent(eventHomeGesture) + showPage(pageHome) gave pick-a-project ×4
• four trips of showPage(pageHome) alone gave task-in-chat, standing-by-chord, manual-answers, reopen-tab

Firing the event after showPage(pageHome) restores the rotation and still retires home-by-two-spaces. A test that drives two spaces from a conversation and checks that Home's tip moves on would pin it.

Smaller things, none blocking:

• A conversation's tip counts as shown when it arrives (noticeBoard.take, once per session), not when it's drawn. With the 15 s wait, someone who never pauses can use up its 6 showings without ever seeing it.
• tipQuietFrom is zero at launch, so a conversation reopened right after a relaunch shows its tip at once, with no wait. The comment says that's on purpose; just noting the PR body describes it differently.
• (requires restart): settle() re-reads HintsAt, so the change actually takes effect at the end of the next turn.
• codeaf config (in hints-and-tips.md and the change entry) isn't a command. That was already wrong on dev, but it's worth dropping while you're in there.