Skip to content

Ratchet weak public API types after the Agent Server contract rollout #300

Description

@neubig

Objective

Introduce a checked-in weak-type budget for public API declarations and incrementally tighten remaining domain boundaries after the MCP contract rollout.

Dependency

Follow-up after the generated Agent Server contract and canonical typed MCP settings API land.

Scope

Migrate in reviewable increments:

  1. conversation creation and workspace configuration;
  2. event/action/observation discriminated unions;
  3. agent-profile skills and condenser settings;
  4. remote state; and
  5. remaining public any declarations.

The budget records existing approved weak locations with reasons; new or widened weak locations fail CI; removing an entry permanently lowers the budget. Evaluate generic transport internals and deliberately opaque proxy payloads separately from public domain contracts.

Exit criteria

The budget acts as a ratchet rather than a target, preventing new public type regressions while allowing incremental cleanup.

Metadata

Metadata

Assignees

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