Update ontology registry and S3 deployment metadata

[cmungall]

Summary

• register the SSBD ontology and its two prefix mappings
• update the FMA and GARD download URLs to their maintained locations
• set explicit gzip content type and cache-control metadata for S3 deployments
• remove the obsolete database directory placeholder

Why

The previous FMA and GARD sources have moved, SSBD needs to be available through the non-OBO ontology registry, and deployed .db.gz artifacts should carry stable HTTP metadata for clients and caches.

Impact

Ontology builds can download FMA, GARD, and SSBD from their current sources. S3-hosted database archives will be served as gzip content with a one-day public cache lifetime.

Root cause

The registry and generated Makefile still referenced superseded download locations, SSBD had not yet been registered, and the S3 deployment commands did not set object metadata explicitly.

Validation

• uv run pytest tests/test_builder/ (7 passed, 2 skipped)
• focused YAML, prefix CSV, and generated Makefile consistency assertions
• git diff --check origin/main...HEAD

[claude]

Claude encountered an error —— View job

---

I'll analyze this and get back to you.