Skip to content

[Review] Restrict type-transition preview text to supported card operations #2950

Description

@Chris0Jeky

MEDIUM found in the independent authority/proposal review of #2949 at c9fccd4. Source-traced, not runtime-reproduced.

A valid card/move proposal with an extra workItemType: "Epic" parameter passes the move validator. AutomationProposalService.BuildReadableDiff appends Task -> Epic for generic card actions, but the move handler ignores that parameter. The actual move remains authorized and atomic; the preview incorrectly claims an additional type change. Ordinary MCP create/update paths construct supported payloads.

Residual acceptance: render a type transition only for operations that actually support it, or reject unsupported workItemType parameters consistently before preview. Regress move plus an extra type field and preserve valid create/update preview/apply behavior. No broad operation-vocabulary redesign.

Tracked separately under the bounded review rule; not an authorization bypass. Requested Project Pending, Priority III, v0.4.

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

    Priority IIIValuable but unscheduled: residuals, tech-debt, performance, depth work.backendPrimary implementation impact in .NET API/domain/application/infrastructure.bugSomething isn't working

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions