Verified against Semitexa Ultimate 2026.09.19.1020

Impact, Context, and Watch Mode

Project Graph is not only for inspection. It is also a practical safety layer for change planning.

Canonical flow

1. Analyze the impact radius before editing.
2. Package only the context needed for review or AI work.
3. Keep the graph current during active changes when the session is long.

Commands

bin/semitexa ai:review-graph:impact Semitexa\\Demo\\Application\\Service\\DemoCatalogService
bin/semitexa ai:review-graph:impact Semitexa\\Demo\\Application\\Service\\DemoCatalogService --context
bin/semitexa ai:review-graph:impact Semitexa\\Demo\\Application\\Service\\DemoCatalogService --context --prompt=review
bin/semitexa ai:review-graph:watch --full-on-start

When the answer is "nothing"

Zero impact is only proof when the graph read everything that could hide a dependent. The text output says "not proof" and names the gaps when it did not, and --json carries coverage.absence_is_proof. See What the Graph Could Not See.

Why this matters

This is where the graph becomes engineering safety: clearer blast-radius decisions, smaller prompts, fewer accidental side effects, and safer refactors.