Update documentation to OasisLMF/OasisPlatform 2.5.4

[benhayes21]

Summary

• Bumps PLAT_VER in update-redoc.py from 2.5.0 → 2.5.4 and regenerates all four OpenAPI/settings JSON schemas
• Replaces stale 1.4.x OasisLMF changelog and broken OasisPlatform include directive with full 2.5.0–2.5.4 changelogs
• Updates Python minimum requirement 3.8 → 3.10 across all relevant pages
• Documents new oasislmf CLI subcommands (generate-pre-loss, generate-post-file-gen, generate-losses-chunk, generate-losses-output, run-postanalysis, generate-doc, warmup, API client commands)
• Adds macOS Apple Silicon installation section and JIT cache warmup guide
• Updates ods_tools compatibility table (adds 3.2.x, 4.0.x, 5.0.x entries); rewrites ODS-tools page with combine and generate commands
• Fixes broken/stale OED links (repo moved from OpenDataStandards → ODS_OpenExposureData, docs reorganised under Docs/); updates spec format reference xlsx → CSV (OEDInputFields.csv, v4.0.0+); adds Marine Cargo section
• Updates container_configuration.rst: psycopg2 → psycopg driver string, API_AUTH_TYPE=disabled, server-internal RUN_MODE, Celery SSL/TLS env vars (v2.5.2+)
• Updates distributed_execution.rst: renames ktools_* → kernel_* params (v2.5.3), removes raw_output_locations (removed in v2.5.4)
• Adds four new model entries to Oasis-models page: Dynamic Footprint, PiWind Vulnerability Adjustments, PiWind S3, PiWind Azure

Test plan

• Run make html in GenerateDocs/ to verify Sphinx build passes without errors
• Check all new changelog links resolve to valid GitHub PRs
• Verify regenerated JSON schemas in src/schema/ match OasisPlatform 2.5.4 release

🤖 Generated with Claude Code

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-06-17 09:34 UTC

[sambles]

Thanks for fixing, i made a note to do this. (but forgot)

Comments:

• Do we use the files releases/oasis_platform.rst releases/oasislmf.rst? might be better to ditch these and link to the release note pages, seems a pain to keep inline

• I don't think the schema/< json file> data is needed. The schema viewers pulls then info from a url (but dosen't hurt to have a copy)

[benhayes21]

The schema files are actually load-bearing for the build — conf.py references them by local filesystem path ('spec': 'schema/platform-1.json' etc.), so Sphinx reads them from disk at build time. Without them committed, every build environment would need to run update-redoc.py first to generate them.

That said, you're right that sphinxcontrib-redoc can also accept URLs as the spec value, so it would be possible to switch to pointing directly at the GitHub release asset URLs and then gitignore src/schema/. Happy to do that as a follow-up if you'd prefer it — just out of scope for this PR.

[benhayes21]

Changelogs have been replaced with links to the GH release page though @sambles