feat: list every viva-catalog wrapper in the registry at level listed - #185
Merged
Merged
Conversation
Completes strategy decision 5, phase A. compose_api/registry/catalog.py reads the vivarium-collective catalog, pins each repository to the commit its branch points at, and writes catalog.yaml (50 entries). load_manifest merges it under manifest.yaml, which wins on id. Nothing is written to vivarium-collective; the script only reads. Listed entries are visible but refused on the service until raised to tested, so this changes no runtime behaviour for current submissions. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This was referenced Oct 6, 2026
jcschaff
changed the base branch from
feat/registry-manifest-enforcement
to
main
October 6, 2026 13:48
…log ingest Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jcschaff
added a commit
that referenced
this pull request
Oct 6, 2026
….6.0 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #184. Merge that first; GitHub retargets this PR to
mainwhen #184's branch is deleted. This completes strategy decision 5, phase A: every wrapper appears at listed.What this adds
compose_api/registry/catalog.py, run withuv run python -m compose_api.registry.catalog:viva_marketplace/modules.jsonfrom thevivarium-collective/viva-catalogrepository;GITHUB_TOKENto avoid the rate limit);compose_api/registry/catalog.yaml, and prints what was added, re-pinned or removed.catalog.yaml(generated, marked as such) has 50 entries, all at listed, each pinned to a commit. There are no module-root collisions with each other or with the curated manifest.load_manifestmerges the catalog undermanifest.yaml; an id in the curated manifest wins. Raising a wrapper therefore means adding it tomanifest.yamlwith its evidence, and the generated file never needs hand edits.Behaviour
No change for current submissions. A listed entry is visible in the registry but refused on HPC, with the reason "registry entry
viva-telluriumis at levellisted; the service runstestedor higher". That is the ladder working as designed, and it replaces "not provided by any registered simulator", which was the less accurate message for these modules.Nothing is written to
vivarium-collective.Not included
A scheduled workflow that re-runs the ingest and opens a PR. A pull request opened with the workflow's
GITHUB_TOKENdoes not trigger CI, so doing it properly needs a GitHub App or a PAT secret. That is a separate decision; for now, re-running the ingest is a one-line manual step.Tests
tests/registry/test_catalog.py(5), without the network:Registry and API rejection tests: 37 passed.
make checkclean.🤖 Generated with Claude Code