Module phases 

Ordered scan phases for the historical termivar legacy-scan pipeline.

Runtime scope

• Build: non-default legacy-scanner feature.
• Execution: Surface A — the mixed-authority ordered sequence composed for termivar legacy-scan. Phases 2–4 use a bounded passive discovery authority and phases 5–9 use a separate bounded active-verification authority. Phase 1 and custom extensions may retain direct I/O, so the complete run remains outside StandardWebDecisionRuntime and reports Unmetered accounting.
• Default termivar scan: no. Within legacy-scan, DirectoryFuzzer is conditional on --legacy-directory-fuzz.
• Support: legacy alpha.

See docs/internals/runtime-map.md.

Re-exports

pub use phase1_recon::ReconPhase;

pub use phase2_crawl::CrawlPhase;

pub use phase3_fuzzer::DirectoryFuzzer;

pub use phase4_param::ParameterDiscoverer;

pub use phase5_sqli::SqliScanner;

pub use phase6_xss::XssScanner;

pub use phase7_ssti::SstiScanner;

pub use phase8_lfi_xxe::LfiXxeScanner;

pub use phase9_ssrf::SsrfScanner;

Modules

phase1_recon

Phase 1: Reconnaissance & Port Scanning

phase2_crawl

Phase 2: bounded same-origin discovery

phase3_fuzzer

Phase 3: controlled directory discovery

phase4_param

Phase 4: bounded differential parameter discovery

phase5_sqli

Phase 5: bounded SQL-behavior observations

phase6_xss

Phase 6: bounded reflection observation

phase7_ssti

Phase 7: bounded template-arithmetic observations

phase8_lfi_xxe

Phase 8: opt-in local-file canary verification

phase9_ssrf

Phase 9: quarantined SSRF out-of-band probing