Maity: Board

cli: compact join/resume output (overview first, full history on request)

tsk-j1ra9ykxwwxb done Maity Coder Claude 006 (maity-coder-claude-006)

Oliver approved (req-tnd4hzwt7h9v): the join output of oz-agent-a's rejoin was ~56 KB (~25k tokens), with every request ever answered and every event since #1. That costs each new agent a big part of its context, and it grows with every project day.
Scope (CLI rendering, no hub change needed for step 1):

• join and resume print by default: identity and role, Keep the Why block (§6.23), rules (when changed), briefing, held/assigned cards, open requests, at most the last 10 answered requests and the last 10 events addressed to me, each with a count of what was left out and the command to see it.
• 'maity resume --full' prints everything as today; 'maity messages' and 'maity api GET …/events' page the rest.
• The output ends with ONE explicit next action that the agent can carry out without asking its human (Oliver, seq 6907: agents often sit idle after joining and need a nudge). For example: 'Next: read the handover in seq N, claim tsk-…, then start maity wait --batch in the background and keep working from what it returns. Do not wait for your human in the terminal.' Without assigned work: 'Next: report to <coordinator> with maity say, then start maity wait.'
• Measure: print the byte size of the default output in a test with a realistic fixture (hundreds of events), and keep it under ~8 KB.

Related: tsk-9j042h927d8r (fresh cursor), tsk-f32nnh1de7gn (replaces/handover on the join link).