standuplisted

# /standup - state of the company Report only - do not dispatch agents, do not start work, do not fix things you notice (note them as worries instead). Read, in order: `company/state/RESUME.md`, `company/state/STATUS.md`, `company/state/WORRIES.md`, `company/state/DECISIONS.md`, `company/state/active-task.json` (if present - it lists every task entry in flight in this working tree), open CRs in `company/change-requests/`, `git log --oneline -10`, and the tail of `company/state/adherence.log`. Report every entry in flight, in the file's order, and check each one's worktree git log for progress that has not been reported. Read only: a standup never adds or removes an entry. Also run `bash company/run-gates.sh` if the last stamp in `company/state/gates.status` is missing or stale - the standup states gate truth, not gate memory. Also tail `company/state/costs.log` if present (one line per stop, pipe separated: `ts | session | kind | task | model | in=.. out=.. cache_r=.. cache_w=.. | est=$X.XX`). The task column can name several slugs joined with `+` (truncated to three plus `+more`), so match by CONTAINMENT, not equality: a line belongs to an entry when the task column CONTAINS that entry's `task` slug (OQ-MST-05 assumption). Sum the `est=$` column two ways for the Spend line: spend for TODAY (lines whose `ts` date matches today) and spend PER ENTRY (for each entry, sum every line whose task column contains its slug). Never split a shared line - it is attributed in full to