Skip to content

Provider compatibility URL rules and bundled metadata still live in core #66

Closed

Description

@anycodes

Bug Description

After the provider isolation merge in PR #38, the core compatibility configuration helpers still format the native envd URL directly, and pure Express configuration/profile data is maintained in a core utility implementation. This leaves backend rules outside the adapter boundary and bypasses provider-owned compatibility rules.

Steps to Reproduce

Inspect the merged transport/config URL helper and the lower utils/bundled_config / utils/bundled_metadata implementation. Change the owned compatibility URL rule to an opaque provider path in a focused regression: the core helper still returns the hard-coded envd host.

Expected Behavior

The provider owns its backend data and URL convention. Core consumes a pure distribution schema and delegates compatibility formatting without loading authentication/runtime adapters. Native public behavior and historical export identities remain unchanged. Neutral profile types belong below the provider runtime.

Actual Behavior

Native URL formatting remains inline in core configuration, and provider-specific defaults/profile fields are maintained in lower utility implementations.

Environment

Linux, Node 22.22.2 / Python 3.11.15, merged isolation source 0.3.0. No real credentials or cloud resources are needed to reproduce this ownership regression.

Acceptance criteria

  • Provider-owned pure metadata and explicit compatibility URL delegation.
  • No runtime adapter imports or new registry discovery in neutral configuration.
  • Opaque URL-rule regression, existing API/config/import regressions and required CI pass.
  • Bilingual documentation, CHANGELOG context and per-owner engineering evidence; preserve the accepted wheel/auth/native-HTTP repairs.
  • Existing Express binary/client cloud acceptance and cleanup remain visible at their tested revisions; no native backend acceptance is invented.

This is a scoped completion follow-up to the user's complete-decoupling request. Optional native image factories remain separate from this contract repair.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions