Skip to content

docs/contracts drift: descriptor-ir stale claims; §7 dtor wording; upstream candidate (SharedFutureImpl.drop assert) #98

Description

@lann

Severity: low — documentation debt from the review (orchestrator-owned).

  1. descriptor-ir.md:80 claims s64/u64 are "range-checked at lower"; the
    interpreter passes bigints through (cabi/lower.ts:43-44, wrap
    semantics). The table is marked interim, but the stale claim is a trap
    for readers — amend.
  2. descriptor-ir.md "Open items" says map is "not emitted by current
    translators"; the shim enables CM_MAP and emits it (lib.rs:83,
    plan.rs:1425-1431), loader consumes it. Amend.
  3. docs/architecture.md §7's dtor claims get aligned with reality as the
    dtor-gating issue lands (gate + promising entry), including the §5
    known-limitation note for guest-initiated suspending dtors.
  4. Upstream finding candidate for
    upstream-component-model-repo-findings.md: definitions.py:1150's
    assert(isinstance(self.pending_buffer, WritableBuffer)) in
    SharedFutureImpl.drop appears internally inconsistent with :2614 +
    :1183 (the only guest-reachable pending side at drop time is a writer,
    whose buffer is a ReadableBuffer). deltic's omission of the assert is
    defensible; record as a tracker entry (filing upstream is the
    operator's call).

Found in the 2026-08-10 adversarial conformance review (runtime + translator vs component-model @ 73b7ad5 definitions.py; wasmtime-environ 47.0.3 treated as trusted).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions