Skip to content

[Tracker] File the 6 upstream StatusPro server feature requests #57

@dougborg

Description

@dougborg

Why

Six items in the tool-surface-redesign epic (#31) are blocked on capabilities the StatusPro server doesn't yet expose. The probes in #30 confirmed each unsupported parameter is silently ignored — there's no client-side workaround that doesn't 10x the round-trip count.

Today the issues exist locally but nothing tracks whether we've actually filed them upstream with the StatusPro team. This issue closes that loop.

Items to file with StatusPro

Each links to the local issue (which has the full motivation + probe results) — the upstream filing should reference these so context isn't duplicated.

Acceptance

  • Each checkbox above ticked when filed upstream, with a link to the upstream ticket/email/Slack thread in a comment here
  • Local issue (feat(client): list_orders id[] batch fetch #32 etc.) updated with cross-reference to the upstream filing so future readers can trace status

Notes

  • Out-of-repo work — closes once filed, not when upstream ships
  • Watch the weekly OpenAPI sync workflow (chore(ci): add weekly upstream OpenAPI spec sync workflow #48) for spec movement that would unblock any of these
  • If the channel for filing is unclear, that's itself worth surfacing — recommend asking the StatusPro team for their preferred feedback channel

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions