M11-01: Supported MVP input profile

[DrunkOnJava]

Created from the roadmap audit in TODO.md.

Source: https://github.com/DrunkOnJava/rvt-rs/blob/main/TODO.md#L1166
Tracking commit: 1ec8105

Scope

Labels: priority:P0, type:feature, area:product

• Define a narrow support statement:
  • Revit versions: choose exact versions based on corpus, likely
    2023 and 2024 first.
  • File types: .rvt project files first; .rfa family support
    remains metadata/schema unless elements are validated.
  • Disciplines: architectural core first.
  • Classes: levels, walls, floors, doors, windows, rooms, materials.

Acceptance criteria:

• Support statement is in README and viewer.
• Unsupported files produce clear diagnostics.

Definition of done

• The TODO acceptance criteria for this section are implemented or explicitly superseded by a linked decision.
• Tests, fixtures, or documentation are added at the level appropriate to the change risk.
• User-facing behavior and limitations remain honest in README/docs/viewer messaging.
• Relevant CI checks pass before the issue is closed.

[DrunkOnJava]

Starting implementation now. I am pairing this with #43 because the support statement needs both README/docs coverage and in-viewer guidance.

[DrunkOnJava]

Implemented supported MVP profile documentation in e30b788.

Changes:

• Added docs/supported-profile.md with supported-today, experimental MVP target, and unsupported/partial boundaries.
• Linked the profile from README and docs/status.md.
• Kept the statement conservative: inspection workflows are supported today; real-project conversion remains limited to a narrow 2023/2024 architectural MVP target.

Validation:

• npm run typecheck (viewer)
• npm run build (viewer; existing >500 kB chunk warning only)
• git diff --check

I will close this after the main-branch checks for e30b788 finish green.