[Bug]: @removed decorator for a property won't work directly, if a model is not added from the very begining

[qiaozha]

Describe the bug

enum Versions {
  v1,
  v2,
  v3
}

@added(Versions.v2)
model Foo {
  prop: string;

  // @add(Versions.v2) // if I comment it out, it won't work
  @removed(Versions.v3)
  prop2: int32;
}

this will report

error
@typespec/versioning/incompatible-versioned-reference
'DemoService.Foo' was added in version 'v2' but contains type 'DemoService.Foo.prop2' added in version 'v1'.
22:3

Does @removed mean being removed since some version ? If so, I don't see why we need to add the @add decorator to remove a property.

Reproduction

playground link

Checklist

• Follow our Code of Conduct
• Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.
• The provided reproduction is a minimal reproducible example of the bug.

[markcowl]

Note that, if you mark the property with @added(Versions.V2) then this issue can be worked around