feat(managed)!: state member comparison item limitations as tagged reason objects (#11177)

* feat(managed): give each member comparison limitation a structured reason

* feat(managed)!: state member comparison item limitations as tagged objects

Each method and field comparison item limitation is now {code, side?, message}
instead of a prefixed sentence beside a parallel limitation_reasons list.

BREAKING CHANGE: compare_managed_members item limitations are objects, not
strings, and limitation_reasons is removed. Read limitations[].code (and side)
instead of matching message prefixes such as "signature-not-resolved:".
Comparison Evidence written by earlier builds is refused; recreate it.

* test(managed): assert limitation codes instead of banning a message prefix
This commit is contained in:
morluto authored and GitHub committed 2026-11-16 05:53:44 +08:00
1 parent f270a5cac1
commit 21adb649ac
7 files changed
+227 -71

No files matched your search

@@ -677,6 +677,11 @@ signature has the other member kind is malformed and cannot establish an
unchanged signature. Comparison retains exact byte-based pairs for malformed
signatures, including empty, truncated, or invalid headers, but reports them as
unknown with a `signature-malformed` limitation when no change is observed.
Each method and field comparison item states its limitations as
`{code, side?, message}` objects: `code` names the reason, `side` names the
other inventory when the reason concerns it (for example
`unknown-within-incomplete-metadata` with `side: "right"`), and `message`
explains it. Read the code rather than the message text.
Runtime-provided methods have the Runtime code type or the InternalCall
implementation flag, as core library FCalls do. They are counted separately in
`native_implementations.runtime_provided`; they have no file-backed native body