Skip to content

Bring RBS signatures and Steep checks back in sync #36

@nficano

Description

@nficano

The repository has a Steepfile and sig/ tree, but the signatures are not synchronized with the implementation. Running asdf exec bundle exec steep check currently exits non-zero and reports 307 problems from 7 files, including undeclared public methods in lib/arcp/serializer.rb, missing constants in lib/arcp/errors.rb, Data-defined classes such as Arcp::Envelope and lease value objects being treated as incompatible with their RBS declarations, and runtime methods such as JobManager#register_agent and SessionActor#run missing from signatures. This makes the type surface misleading as documentation and prevents Steep from serving as a quality gate.

Fix prompt: Update the RBS files so they model the current Ruby 3.4 implementation, especially the Data.define value objects, module functions, constants, keyword initializers, and runtime manager APIs. Add missing declarations for serializer accessors, error constants, feature constants such as MODEL_USE and PROVISIONED_CREDENTIALS, and public runtime methods checked by the Steepfile. Once the signatures are accurate, wire bundle exec steep check into CI or the default verification path so future public API changes keep the signatures current.

Metadata

Metadata

Assignees

No one assigned

    Labels

    code-qualityCode quality, maintainability, or type-signature hygieneseverity:mediumMedium severity

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions