Skip to content

Plan, apply and roll back changes to a production ontology, with a blast radius report and a proof an auditor can re-check.

docs(contributors): credit Nicolas Geysse for the serve-http hardening

FABIOTESS829e18f1945b
diff --git a/CONTRIBUTORS.md b/CONTRIBUTORS.md
index 27c6cb02..e23d3c68 100644
--- a/CONTRIBUTORS.md
+++ b/CONTRIBUTORS.md
@@ -19,6 +19,10 @@ Open Ontologies exists thanks to everyone who has built, used, broken, and impro
- Identified that anonymous restriction classes (and any blank-node IRIs returned by SPARQL) get freshly minted IDs on every parse, producing ~40 phantom add/remove pairs plus a Cartesian product of confidence-scored "renames" on `detect(x, x)` for typical OWL ontologies (Pizza tutorial repro). Shipped a surgical filter on the `_:` prefix in `extract_vocabulary` that bought time for the proper successor (RDFC 1.0 canonicalisation via Oxigraph 0.5.8 — landed in [2e329ee](https://github.com/fabio-rovai/open-ontologies/commit/2e329ee)).
- PR description quality (clear repro, minimal diff, full checklist of build/test/clippy/audit, CHANGELOG entry) is the model contributor experience.
+- **Nicolas Geysse** ([@nicolas-geysse](https://github.com/nicolas-geysse)) — operational hardening of the HTTP transport, and the most rigorous issue reports this project has had ([PR #78](https://github.com/fabio-rovai/open-ontologies/pull/78), [PR #79](https://github.com/fabio-rovai/open-ontologies/pull/79)):
+ - `serve-http` had a graceful-shutdown `CancellationToken` that nothing ever cancelled, so the shutdown future pended forever, the process could only be killed, and the unix socket was left on disk afterwards. Fixed with ctrl-c and `SIGTERM` handling, a second-signal escape hatch for a stalled shutdown, and socket unlink on both paths.
+ - An unauthenticated `/health` liveness route, correctly registered after the bearer layer so orchestrators can probe without credentials while `/api` and `/mcp` stay behind auth, plus a README table documenting that the HTTP surface is **not** read-only.
+ - Seven issues filed against named commits, each citing file and line and stating the failure mode rather than the code smell. Several found silent-corruption paths rather than crashes, which is the harder class to see.
- **Ladislav Gazo** ([@lgazo](https://github.com/lgazo)) — opt-in persistent triple store ([PR #81](https://github.com/fabio-rovai/open-ontologies/pull/81)):
- A `[storage]` backend selector for the main graph: `memory` (default, unchanged) or `persistent`, opening a RocksDB-backed Oxigraph store at `<data_dir>/triplestore` so triples survive a restart. CLI flag, env override and config, with correct precedence, plus a drop-and-reopen round-trip test.
- Handled the case that would otherwise have quietly not worked: the one-shot CLI subcommands read the same setting, so `load` then `query` share state. Kept sandbox stores in-memory so only the main graph is ever persistent, and documented Oxigraph's single-writer-per-directory constraint rather than leaving it to be discovered.