docs: verify rendered release identity

[stefan-jansen]

Summary

• expose ml4t-library, ml4t-version, and ml4t-commit in every rendered documentation page
• make ordinary CI and a dedicated read-only Docs workflow reject missing or mismatched identity metadata after a real strict build
• verify both stable and versioned HTML after release deployment, while retaining the existing release.json check
• add canonical documentation, issue, release, and license links plus the exact contributor quality gates
• prepare version 0.1.4 so the corrected deployment can identify its exact release commit

Verification

• uv run ruff check src/ tests/ examples/ scripts/
• uv run ruff format --check src/ tests/ examples/ scripts/
• uv run ty check
• uv run pytest tests/ -q --cov-report=json:coverage.json - 421 passed
• uv run python scripts/ci/check_coverage.py coverage.json - lines 95.49%, branches 85.36%
• revision-identified uv run mkdocs build --strict plus local identity verification
• uv build
• pre-commit run --all-files
• actionlint .github/workflows/docs.yml .github/workflows/ci.yml .github/workflows/release.yml

The dedicated Docs workflow and ordinary CI build the real site with the docs extra, then validate every rendered page. Core pytest verifies exact matching and mismatch rejection without adding optional docs dependencies to core qualification.

Closes #48

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.