#5: Docs consistency pass

[miroslavpojer]

Overview

One consistency pass over every file in living-doc — README.md, CONTRIBUTING.md, and
everything under docs/ (introduction, guides, tutorials, projects, specs). The pages were written
across several incremental rounds and had drifted; this PR reconciles them. No behaviour changes —
documentation only.

Fixed, in order:

1. Naming drift — generator-ready.json is the final name for the toolkit's canonical dataset.
   All 5 tutorials, quickstart.md, getting-started.md, and the spec prose/diagrams/task lists
   still used the old pdf_ready.json / pdf_ready_json / PDFREADY. Every occurrence now reads
   generator-ready.json; the pre-rename names survive only inside a labelled "Superseded name"
   callout in docs/specs/data-flows.md §5.
2. Python floor — example actions/setup-python snippets pinned python-version: '3.11' in 7
   files; all moved to '3.10' to match the agreed ecosystem floor.
3. Tutorial-capture scope — docs/specs/architecture.md §4.1 and docs/specs/roadmap.md Post-v1
   are now word-for-word identical on the narrow "run the flagged scenarios and collect
   screenshots + step commentary" scope. No text anywhere implies a video-generation skill exists in
   this ecosystem or in agentic-toolkit.
4. Links & anchors — full relative-link + heading-anchor check over docs/** + root *.md is
   clean (0 missing files, 0 missing anchors). No §/anchor cross-reference points at a section
   absent from its target. No [[wiki-link]] syntax anywhere.
5. Decision-driven cross-spec corrections — confirmed applied in the target specs and that no
   doc still references the superseded text: 3.10 (not 3.14) Python floor, no additive
   v1.x/v2.0.0 schema gate, datasets_pdf rename in-scope for Phase 1 (not "deferred").
6. Self-referential tokens — roadmap.md Step 1 and phase-0-tasklist.md P0-A1 literally
   contained the strings their own acceptance greps search for (pdf_ready, [[…]],
   python-version: '3.11'); reworded to preserve meaning without the literal tokens.

Files touched

Tracked (in this diff):

File	Change
docs/guides/getting-started.md	python-version → '3.10'; pdf_ready.json → generator-ready.json (×3); rewrote the file-names note
docs/introduction/quickstart.md	python-version → '3.10'; pdf_ready.json → generator-ready.json (×2)
docs/tutorials/gh-issues-to-markdown.md	python-version → '3.10'; pdf_ready.json → generator-ready.json (×2)
docs/tutorials/gh-source-to-markdown.md	same
docs/tutorials/gh-source-to-pdf.md	same
docs/tutorials/user-stories-to-pdf.md	same
docs/tutorials/ado-workitems-to-markdown.md	same

Acceptance criteria

• Link check over docs/** + root *.md is clean — every relative link resolves; every anchor
  matches an existing heading.
• grep -riE 'pdf[_-]ready|doc[_-]ready' returns hits only inside the labelled "superseded name"
  callout in docs/specs/data-flows.md §5.
• grep -rE '\[\[|\]\]' over docs/** returns nothing.
• No cross-reference names a §/anchor absent from its target document.
• Tutorial-capture scope wording is identical in docs/specs/architecture.md §4.1 and
  docs/specs/roadmap.md Post-v1, and consistent in the glossary.
• No python-version: '3.1[1-4]' literal remains in docs/**.
• This PR body carries the change report.

Release Notes

• Documentation examples now use the final artifact name generator-ready.json for the toolkit's
  canonical dataset (previously shown as pdf_ready.json).
• Example workflow snippets in the quickstart, Getting Started guide, and tutorials pin
  python-version: '3.10', matching the ecosystem's Python 3.10 floor.
• Cross-references, tutorial-capture scope wording, and stray wiki-link syntax across the docs set
  were reconciled after several incremental drafting rounds.

Related

Closes #5