Package impact in WU briefs
Before editing, wu:brief maps each declared code_paths entry to a known package owner when the path is
inside a discovered package directory. It also lists the known packages that depend on those owners,
including transitive dependents. The shared Markdown renderer adds the same volatile section for
every client, after the cache-stable prompt prefix.
What the map reads
Section titled “What the map reads”Discovery covers a fixed set of workspace package roots. Dependency links use only dependencies and
devDependencies that name another discovered workspace package. Reverse traversal is cycle-safe.
It reports downstream dependents, not packages that the changed package itself depends on.
Paths and package names are quoted as data. A path pattern under a known package directory is a conservative owner hint; patterns are not expanded. A path or pattern without a known package directory remains visible as unresolved.
Limits
Section titled “Limits”This is best-effort metadata-derived coverage. Missing, unreadable, invalid, or unnamed manifests may be silently omitted by the graph builder. The section explains that coverage can be partial and that the omitted-manifest count is unavailable; it does not estimate a count or claim the graph is complete.
The map does not analyze symbols, runtime imports, services, permissions, or release effects. It is not complete repository assurance. An unresolved path or an empty dependent list describes only what the available manifests establish.