Work overhaul: plan, track and ship like Linear, with Basecamp's project home

Work is g1t's Basecamp/Jira: where a team plans, tracks and ships. Today it is a plan (Now, Next, Later), a board, triage, lists, labels and milestones. It needs a significant overhaul, so planning and tracking work are a strength rather than a list of items.

Agents' sessions moved to Chat in #309. Work can still take you to them, and to Chat, from any work item.

The bar

• Linear: fast, keyboard-first, opinionated views and cycles.
• Jira: depth, custom fields, workflows.
• Basecamp: projects with their message board, docs, to-dos and schedule in one place.

Work should feel like Linear, with Basecamp's sense of a project as a home.

What to look at (discovery first)

1. Projects or initiatives: a home for a body of work, with its items, its docs in the Library, its chat, its milestones and its people. Open question: how this relates to g1t's repositories, which Code calls projects.
2. Cycles: time-boxed work beside the Now/Next/Later plan, with progress and carry-over.
3. The work item page: a redesign. Description, sub-items, linked pull requests and sessions, decisions, activity, and agents who can pick it up (dispatch to a Chat session).
4. Views: saved and shared filters, grouping, list, board and timeline.
5. Triage and intake: from chat, from email, from agents, and from GitHub issues already imported.
6. Speed: every view instant and every action keyboard-first.
7. Mobile: it already has Work; keep it in step.

First step

A short design doc in the Library covering the information architecture, the core objects and a few screens, reviewed with the owner before any rebuild. Then slices, each its own pull request.

Done when

The owner signs off on the design. The first slices that ship are the project home, the new work item page and cycles.