os-done-or-not

# os-done-or-not One question, one screen: **did the agent finish, and what actually happened** - in words a reader who does not code will understand. Nothing happened (pure questions, no files touched) → one line saying so, no report. ## Language The language the user speaks in this session, detected from the conversation - translate every template label. Code, files, commands stay English. ## Step 1 - gather proof that takes seconds Fast checks only; never re-run the test suite - use results this session already produced. Not confirmable in seconds, or still running → **"not checked"**, never "yes". ```bash git status --porcelain # uncommitted? git log --oneline -10 # what landed git log origin/HEAD..HEAD --oneline 2>/dev/null # unpushed? gh pr view --json state,mergeStateStatus && gh pr checks # if a PR exists ``` ## Step 2 - name the outcome Sessions end one of eight ways; pick the match **before** writing, or the report says "fully done: yes" and "safe to close: no" in the same breath. | # | Outcome | Verdict shape | |---|---|---| | 1 | Shipped and verified | done Yes · nothing needed · close Yes | | 2 | Done - one action is yours | done Yes · needed = that action · close Yes | | 3 | Stalled on your decision | done No · needed = the decision · close No | | 4 | Partly done, rest deferred | core Yes, rest recorded as debt · close Yes | | 5 | Didn't work - rolled back | done No · lead = what was learned · close Yes | | 6 | Something broke...