Registry: verify service description metadata agreement #184

New issue

Closed

opened 2026-09-08 02:03:10 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-08 02:03:10 +00:00

Owner

Registry metadata-agreement follow-up. plugins.json requires a published description and current service entrypoints expose PluginMetadata.description, but validate_service_entrypoint() only reconciles name/version/api_version. A service can therefore advertise one description in the registry and instantiate with another while source validation stays green. TDD slice: reconcile effective service description (including Core's empty default), keep exact errors per plugin, then run the full compatibility/Nix/package gate.

Registry metadata-agreement follow-up. `plugins.json` requires a published description and current service entrypoints expose `PluginMetadata.description`, but `validate_service_entrypoint()` only reconciles name/version/api_version. A service can therefore advertise one description in the registry and instantiate with another while source validation stays green. TDD slice: reconcile effective service description (including Core's empty default), keep exact errors per plugin, then run the full compatibility/Nix/package gate.

nsaspy closed this issue

2026-09-08 02:03:10 +00:00

nsaspy referenced this issue

2026-09-08 02:19:40 +00:00

coding: fence branch creation to observed HEAD #388