verify-concurrent-session-changeslisted

# Verify Concurrent Session Changes (Shared, Non-Git Folder) Built from two dated occurrences of the same gap (2026-08-11 self-initiated concurrency check; 2026-08-12, different context — user pointed at a specific already-finished session's output to reconcile against). Clears `process-vs-work-doctrine` rule 1. Per rule 3, kept in this single-file form — no spec directory, no install script, no CONTEXT.md — until a third real use. ## Procedure ### 1. Find candidates by timestamp List files/folders in the shared tree by modification time, relative to your own last-known-good state (when you last read or wrote into that folder). This gives you the candidate set of what changed and roughly when — not proof of what changed, just where to look. ### 2. Find stale references If anything in the candidate set was renamed or moved, grep the **entire** shared tree (not just the changed files) for the old name/path. A hit means a pointer wasn't updated — something is now broken, not just "different." Do this step regardless of how thorough step 1's timestamp scan looked; renames are exactly the kind of change that looks clean by timestamp alone and broken everywhere else. ### 3. Read full content, not just confirm change For each genuinely changed or new item, read it completely. A changed timestamp only tells you *that* something changed, never *how*. Judge whether the change is additive/consistent with your own work or contradictory — and say which, explicitly, rather than rep