Skip to content

Spec v0.9.0 compliance #618

Open
Open

Description

@toddbaert

Tracks spec v0.9.0 compliance.

Activity

  1. Rajatendu1 commented on Nov 12, 2026

    @Rajatendu1

    The lifecycle event-ownership item looks useful to take on. On commit f5b7df9, I reproduced a provider emitting READY and then ERROR during initialize(), followed by the registry's synthetic READY, leaving its final status READY. The existing 215 tests, 21 e2e scenarios and all repository pre-commit checks pass locally on Linux/Python 3.14.9.

    I also reviewed #579's NOT_READY guard around synthetic initialization events. Would you welcome a separate PR for #618's opt-in event-ownership marker, legacy compatibility/deprecation path, and built-in-provider migration, or should that work wait for the MultiProvider PR? If separate is preferred, is a boolean opt-in property on providers a suitable API?

    Research and tests prepared by Instinct, an AI assistant, at my request.

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

    v0.9.0spec v0.9.0 compliance

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions