scrutiniselisted

# Scrutinise Review the scope supplied with the user's invocation. If none is supplied, use today's commits on the current branch plus all uncommitted changes. Determine the current date and local timezone, inspect the Git log, staged and unstaged diffs, and relevant untracked files, and state the resolved scope explicitly. Do not broaden an explicit scope. If the directory is not a Git repository, explain which default cannot be resolved and use a clearly identified file scope or obtain the missing target. Read [the scrutiniser procedure](../../references/scrutiniser.md) in full. The bundled reference is the specialist's operating procedure; it does not register an agent type in Codex. Use an actual available delegation tool for the independent forensic review. Give the reviewer a self-contained brief containing: - The exact scope, including the date boundary where relevant. - The absolute working directory and verified Git branch or detached state. - The path to the bundled scrutiniser procedure and an instruction to read it in full. - A critical, no-skim mandate: inspect source, call sites and tests; verify claims rather than trusting commit messages, plans or descriptions. - A read-only mandate: report findings, do not edit files, fix code, commit, or publish anything. - The applicable repository instructions, known access limits, and the requirement to report unverified areas instead of assuming that files, dependencies, submodules or test facilities are availabl