Decide whether ts audit generate should crawl beyond the supplied page #1065

Description

ts audit generate <url> drafts configuration and asset findings from the supplied page. ts audit ad-templates generate <url> already has a separate same-origin section crawl. This issue asks for a product decision on whether the generic generator should inspect more than its entry page; it is not yet an approved crawl implementation.

Decision to make

Evaluate the benefit of additional pages against crawl time, duplicate findings, consent/session behavior and the risk of changing generated config unexpectedly. If a crawl is chosen, define same-origin boundaries, page and time budgets, selection of sections, failure handling, deterministic output, and how findings from several pages are merged. If the single-page behavior is retained, document it clearly and give operators a way to use the existing ad-template crawl where relevant.

Done when

• A maintainer records the chosen behavior and the evidence or use case behind it.
• The decision specifies limits, output and failure behavior if crawling is approved.
• CLI help and documentation describe the chosen behavior.
• Any implementation follows the recorded decision and has tests for the selected boundaries.

Affected area

CLI audit generation.