chore(release): 1.2.1

[refeed]

Closes #371

Everything under ## [Unreleased] has been on main since 1.2.0 (2026-08-03) and is unreachable from a pinned install — tirith lint, tirith fmt, the pre-commit hooks, tirith ui, the result context on messages, and the error_tolerance verdict fix (#293). This cuts the tag that makes them installable.

What changed

File	Change
CHANGELOG.md	## [Unreleased] → ## [1.2.1] - 2026-09-08. Content untouched.
setup.py, src/tirith/__init__.py	1.2.0 → 1.2.1
README.md	install-verification output; tests/test_readme_is_current.py pins it to __version__
documentation/docs/tirith-usage/*	install pins @1.2.0 → @1.2.1; "1.2.0 is the newest tag"
documentation/docs/tirith-usage/editor-and-local.md	dropped the ":::note Not in 1.2.0" admonition — the release contains what it was about
both pre-commit blocks	rev: main → rev: 1.2.1, which is the point of publishing .pre-commit-hooks.yaml
docs/platform-check.md	the generator.version in the sample result document
documentation/static/**	regenerated by documentation/scripts/generate-llms-full.py, as its docstring asks

After merge

Tag and push, or the install pins in this PR resolve to nothing:

git tag -a 1.2.1 -m 'Release 1.2.1' && git push origin 1.2.1

Note the tags in this repo are unprefixed (1.2.0, 1.0.6) — bump_version.py prints a v-prefixed suggestion that does not match what is actually published.

On the version number

Semver would make this 1.3.0: tirith lint, tirith fmt and tirith ui are new commands, and the changelog's Added section is the longest part of it. Cut as 1.2.1 as asked; say the word and I will move it.

Deliberately not in this PR

The landing page and the agent-facing packs still describe tirith lint as unshipped, and still pin @1.2.0:

• documentation/src/pages/index.js — the "Any CI" tab keeps tirith lint commented out, and the anywhere section carries an IN DEV badge
• documentation/src/data/demoPhases.js — five commented # in dev, not in 1.2.0 lines, and inDev: true on the pre-commit integration
• documentation/static/llms.txt → src/data/agentBrief.js — "tirith lint is not in the released package"
• .cursor/rules/tirith-policies.mdc, .claude/skills/tirith-policies/ — the same claim, plus "do not put it in a pipeline"

Uncommenting those, flipping the IN DEV badge to BETA, and moving the tense out of the conditional is copy and badge work with its own review surface, and half-doing it here would leave a pin that says 1.2.1 next to a caveat that says not in 1.2.0. Each file group is internally consistent as it stands. Follow-up.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

Files with missing lines	Coverage Δ
src/tirith/__init__.py	100.00% <100.00%> (ø)
src/tirith/platform/report.py	89.09% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[sonarqubecloud]

❌ The last analysis has failed.

See analysis details on SonarQube Cloud