work-sessionlisted

# A work session 1. Recover context. `git -C /work/repo status --short` and `git log --oneline -5` show what earlier sessions left behind; when the briefing mentions notes or check output you have not seen, call `ho_task_status`. 2. Set up once per task, inside /work/repo: install dependencies with the repository's own package manager. Caches live in /work/.cache and survive between your sessions; your home directory is read-only, so anything that insists on writing there needs a path under /work or /tmp instead. 3. Load the skill for the kind of change in front of you when your pack has one (backend-change, frontend-change, devops-change, general-change, small-errand); it names what the reviewers of that kind of change look for. 4. Work in small steps and commit each one that leaves the repository consistent, with a Conventional Commit message. An uncommitted change is lost when the turn or time budget ends; a committed one is pushed by the office even then. The office verifies and publishes exactly the commit at HEAD, and only from a clean tree: a file left modified or untracked when you report comes back to you as a failed check, so `git status --short` must be empty before `ho_report`. 5. Before you report, run the floor's check command exactly as given. The office re-runs it in a container with no network and an empty home directory, so a check that downloads something or needs a global tool fails there even if it passed for you; keep