situate-whatlisted

# What The reader is disoriented. End that in five lines. Read `references/brief.md` first — it defines the five-line budget, what earns a line, the option lines, and the evidence tiers that keep this cheap enough to ask casually. User arguments: $ARGUMENTS ## Context Current branch — run this command and read the output: ```bash git branch --show-current 2>/dev/null || echo "(detached HEAD)" ``` Ahead / behind trunk — run this command and read the output: ```bash git rev-list --left-right --count "$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null || echo origin/main)"...HEAD 2>/dev/null || echo "(no comparison available)" ``` Working tree — run this command and read the output: ```bash git status --short 2>/dev/null | head -20 || echo "(unavailable)" ``` Commits since trunk — run this command and read the output: ```bash TRUNK=$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null || echo origin/main); BASE=$(git merge-base HEAD "$TRUNK" 2>/dev/null); if [ -n "$BASE" ]; then git log --no-merges --format='%h %s' "$BASE..HEAD" | head -15; elif git rev-parse --verify --quiet "$TRUNK" >/dev/null; then echo "(no merge-base with $TRUNK)"; else echo "(trunk $TRUNK not found)"; fi ``` ## Procedure ### 1. Read what was actually asked Empty `$ARGUMENTS` means the whole situation: what this session has been doing, and where the repository stands. An argument narrows it to that subject, and narrowing is the point — `this skill the test failure` ans