Sentinel change map

A run can touch 100+ files across several repos, and a plain diff does not show what each file does or how the pieces connect. This turns the run's changes into one self-contained HTML page opened locally. The page contains source code: keep it on the requester's machine and never publish it.

• Columns come from each repo's stack profile (its lanes rules). Repos with different stacks get their own columns side by side.
• Links connect files that use each other: imports, class references, HTTP calls from a client repo to a server endpoint, entity to migration table. Unchanged files a changed file connects to are shown dashed.
• Clicking a file shows its role, what changed, its links, and key diff blocks. Flows walk a feature as numbered steps.

Workflow

Run commands from the workspace root. Replace <slug> with the run slug; files live in .sentinel/runs/<slug>/.

1. Scope

Base revisions default to HEAD, which covers all uncommitted work. If part of the run was already committed, pass the baseline SHAs from state.json (baseline) with --base <repo_id>=<sha>. Files that were uncommitted before the run started must be marked as pre-existing in their notes.

2. Collect