docs: Document dependency-tree goal in quick-start and multi-module guides

quick-start-guide.adoc:
- Add dependency-tree to the Multi-Module Projects basic usage examples
- Add a full 'dependency-tree' section to the Available Goals reference,
  covering both multi-module and single-module usage with sample output
  and a list of typical use cases

multi-module-tutorial.adoc:
- Replace the 'Verbose Dependency Graph Display' subsection with a
  dedicated 'Dependency Tree' subsection documenting the new goal,
  including filtered (-m) usage and representative output samples
- Retain a short note on the compile -v flag for in-build verbose output
- Add an 'Inspect Dependencies Before Building' step before the
  'Build Specific Module' section to introduce dependency-tree early
  in the workflow narrative

Author: graemeg

docs/multi-module-tutorial.adoc

@@ -183,6 +183,17 @@ Output shows build progress:
 [INFO] Reactor build complete: 3/3 modules built
 ----
 
+=== Inspect Dependencies Before Building
+
+Before building, use `dependency-tree` to verify module relationships without
+invoking the compiler:
+
+[source,bash]
+----
+pasbuild dependency-tree          # Show all modules and their dependencies
+pasbuild dependency-tree -m demo  # Show only demo's dependencies
+----
+
 === Build Specific Module
 
 Build only a specific module (and its dependencies):
@@ -340,39 +351,70 @@ pasbuild test -m demo                 # Test demo module
 pasbuild package -m ui                # Package UI library
 ----
 
-=== Verbose Dependency Graph Display
+=== Dependency Tree
 
-Display the module dependency graph with the `-v` (verbose) flag:
+Display the full dependency graph without compiling anything:
 
 [source,bash]
 ----
-pasbuild compile -v
+pasbuild dependency-tree
 ----
 
-Output shows each module and its dependencies:
+Output lists every module in topological order (dependencies first), with each
+dependency labelled by kind:
 
 [source]
 ----
-[INFO] Building 3 modules in dependency order
-[INFO] Dependency Graph:
+[INFO] ------------------------------------------------------------------------
+[INFO] Dependency Tree
+[INFO] ------------------------------------------------------------------------
 [INFO]
-[INFO] core (no dependencies)
-[INFO] ui (depends on: core)
-[INFO]   └─ core
-[INFO] demo (depends on: ui)
-[INFO]   └─ ui
+[INFO] core 1.0.0 [library]
+[INFO]   (no dependencies)
 [INFO]
-[INFO] Building module 1/3: core
-[INFO] Building module 2/3: ui
-[INFO] Building module 3/3: demo
+[INFO] ui 1.0.0 [library]
+[INFO]   └─ core [module]
+[INFO]
+[INFO] demo 1.0.0 [application]
+[INFO]   ├─ ui [module]
+[INFO]   └─ some-ext:2.0.0 [external]
 ----
 
-The verbose flag helps you:
+Restrict the output to a single named module with `-m`:
+
+[source,bash]
+----
+pasbuild dependency-tree -m demo
+----
+
+[source]
+----
+[INFO] ------------------------------------------------------------------------
+[INFO] Dependency Tree for module: demo
+[INFO] ------------------------------------------------------------------------
+[INFO]
+[INFO] demo 1.0.0 [application]
+[INFO]   ├─ ui [module]
+[INFO]   └─ some-ext:2.0.0 [external]
+----
+
+`dependency-tree` is particularly useful for large multi-module projects where
+running `compile -v` buries the dependency graph under screens of compiler
+output.  The goal exits immediately after printing the tree — no compilation
+occurs.
+
+=== Verbose Dependency Graph During Build
+
+The `-v` (verbose) flag still shows a compact dependency summary at the start
+of a `compile` run, but the output is interleaved with FPC compiler lines:
+
+[source,bash]
+----
+pasbuild compile -v
+----
 
-- Visualize module relationships
-- Verify correct dependency setup
-- Understand the build order
-- Debug complex dependency chains
+Use `dependency-tree` when you want to inspect dependencies in isolation;
+use `-v` when you want extra detail alongside the full build output.
 
 === Combined with Other Flags
 

docs/quick-start-guide.adoc

@@ -652,7 +652,8 @@ my-framework/                      # Aggregator (packaging=pom)
 cd my-framework
 pasbuild compile              # Build all modules in dependency order
 pasbuild compile -m demo      # Build only demo (and its dependencies)
-pasbuild compile -v           # Show dependency graph
+pasbuild dependency-tree      # Show dependency graph without compiling
+pasbuild dependency-tree -m demo  # Show only demo's dependencies
 ----
 
 **For detailed multi-module documentation**, see link:multi-module-tutorial.adoc[Multi-Module Tutorial].
@@ -1267,6 +1268,65 @@ pasbuild install
 
 **Note:** For multi-module aggregator projects, `install` runs on each non-aggregator module in dependency order.
 
+=== dependency-tree
+
+Displays the dependency graph of a project without invoking the compiler.
+
+[source,shell]
+----
+pasbuild dependency-tree           # All modules (or external deps for single-module)
+pasbuild dependency-tree -m demo   # Dependencies for the named module only
+----
+
+**What it does:**
+
+For multi-module (aggregator) projects, modules are listed in topological order — dependencies before dependents. Each module entry shows:
+
+* Local module dependencies (`[module]`)
+* External repository dependencies (`[external]`)
+* The module's packaging type (`[library]`, `[application]`, `[aggregator]`)
+
+For single-module projects, only the declared `<dependencies>` (external) are shown.
+
+**Example output — multi-module project:**
+
+[source]
+----
+[INFO] ------------------------------------------------------------------------
+[INFO] Dependency Tree
+[INFO] ------------------------------------------------------------------------
+[INFO]
+[INFO] math-core 1.0.0 [library]
+[INFO]   (no dependencies)
+[INFO]
+[INFO] math-utils 1.0.0 [library]
+[INFO]   └─ math-core [module]
+[INFO]
+[INFO] calculator 1.0.0 [application]
+[INFO]   ├─ math-utils [module]
+[INFO]   └─ some-lib:2.0.0 [external]
+----
+
+**Example output — single-module project with external dependencies:**
+
+[source]
+----
+[INFO] ------------------------------------------------------------------------
+[INFO] Dependency Tree
+[INFO] ------------------------------------------------------------------------
+[INFO]
+[INFO] my-app 1.0.0
+[INFO]   ├─ lib-alpha:1.0.0 [external]
+[INFO]   └─ lib-beta:3.2.1 [external]
+----
+
+**Use cases:**
+
+* Inspect the dependency graph before a build, without compiler output interfering
+* Verify that module dependency declarations are correct
+* Quickly audit which external libraries a module relies on
+* Diagnose unexpected transitive dependency relationships
+
 === init
 
 Bootstraps a new project.