[pyjeebz]

Prepares 1.2.0: Journeys 1 (#7–#14) and the MCP fix (#6).

• Version: 1.2.0 in pyproject.toml, cli/pyproject.toml and cli/src/prescale_cli/__init__.py.
• Changelog: ## Unreleased becomes ## 1.2.0 — 2026-11-08. The release workflow checks for this heading, and the section becomes the GitHub release notes.
• Notes corrected:
  • three example journeys, not two
  • the dashboard caveat replaced: pyjeebz/prescale-web#2 shipped, so journey runs are compared only with journey baselines
• New "Changed" entry: with prescale/journeys/ present, run, investigate and ci replay journeys. --urls restores the old behaviour.

Why 1.2.0 and not 1.1.4: Journeys is new capability, so semver makes it a minor release, not a patch. The roadmap's old "1.2 database branches" label moves to a later version.

How it was verified

• prescale --version → prescale, version 1.2.0 after reinstalling
• ruff check cli/src cli/tests clean · pytest cli/tests -q 368 passed
• The release workflow's own awk extraction, run locally, produces the 1.2.0 section as the notes.

Risk

Tier: risky, because it's a release. Merging this PR publishes nothing. Pushing the tag v1.2.0 after merging publishes to PyPI and creates the GitHub release.

After the release:

• move the Action's v1 tag to v1.2.0, so @v1 users get journeys
• prescale-web#2 is already deployed, so the release order holds

Rollback: nothing to roll back before the tag. After it, a public version can only be superseded by a patch release.

---

Generated by Claude Code