Recent trail + People on a task: user pages and developer guides
Four pages for #1450 (GH #124) and #1451-#1453 (GH #89):
- Recent-Trail — the Recent tab in the waffle menu, what the outline means,
why coming back to a module opens a second heading, and the access rules.
- Recent-Trail-Developer-Guide — the table and why it has no unique key, the
refresh-collapse rule, the prune's derived-table trick, filter-before-group,
batching labels while reusing each module's own gate, why the client-side
ping exists at all, and the media-query specificity bug that hid the search
box 53px off-screen where the body could not report it.
- People-on-a-Task — owner plus Involved, the notification switches, the
optional per-person tick, and why subtasks are excluded.
- People-on-a-Task-Developer-Guide — opens with the naming rule (screen says
Involved, code says collaborator, and why), then the table that deliberately
omits the owner, the four filters that can hide a task, EXISTS-not-JOIN, the
router learning a multi-person audience, and the trap where keeping the owner
in assignee_id sends the notification to the wrong person.
Both dev guides carry the colour-keyed file table and are written to be
followed by somebody who has not worked on the codebase before.
Sidebar: Recent trail under Getting Started beside the command palette;
People on a task nested under Tasks. Link and file-path checks both clean.