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.

Empieza por inventariar los datos de standard-journey, el código de generación, las salidas generadas y las comprobaciones relacionadas de release o documentación mencionadas en el issue. Identifica cada consumidor y propietario activo, y determina después si está justificada la eliminación o una pipeline legible por máquinas restaurada intencionadamente. Se considera terminado cuando los artefactos conservados tienen propietarios, se eliminan los pasos muertos, la navegación para los adoptantes sigue orientada a tareas y las comprobaciones impiden que vuelvan a aparecer superficies sin propietario.

Escrito por el modelo de indexación a partir del texto del issue.