Retire or intentionally restore the standard-journeys documentation pipeline

## Problem

The repository retains standard-journey data, generation code, and generated outputs from an earlier documentation structure, but the adopter-facing site no longer has an intentional consumer for them. This increases maintenance and review cost and makes it easy to accidentally republish maintainer-oriented assurance pages.

## Decision required

Choose one outcome:

1. Remove the unused generator, data, checks, and generated outputs, preserving only evidence that has an active release or audit consumer; or
2. Define a deliberate machine-readable consumer and restore the pipeline with clear ownership and publication boundaries.

Do not restore the old Journeys navigation tree as the default adopter experience.

## Acceptance criteria

- [ ] Every retained generated artifact has a named consumer and owner.
- [ ] Dead generation steps and CI checks are removed if no consumer exists.
- [ ] Adopter navigation remains task-oriented and excludes internal assurance terminology.
- [ ] Any retained evidence pages are clearly separated from released beginner documentation.
- [ ] Release and docs checks fail if an unowned generated surface is reintroduced.

Inizia inventariando i dati di standard-journey, il codice di generazione, gli output generati e i controlli correlati di release o documentazione indicati nell’issue. Identifica ogni consumer e owner attivo, quindi determina se sia giustificata la rimozione o il ripristino intenzionale di una pipeline leggibile dalle macchine. Il lavoro è completato quando gli artefatti mantenuti hanno degli owner, i passaggi inutilizzati sono rimossi, la navigazione per gli adopter rimane orientata alle attività e i controlli impediscono il ritorno di superfici senza owner.

Scritto dal modello di indicizzazione a partire dal testo della issue.