Skip to content

Keep failed trace reads separate from compatibility verdicts #259

Closed

Description

@devantler

🤖 Generated by the Agentic Engineer

The reader accepts a missing or cross-namespace producer edge carrying a compatible contract verdict even though those paths never inspect the producer.

Audience: product authors and consumers using the portable browser hosts. This is a reproducible client behavior gap in the current released implementation; preserve public metadata, independent product ownership and existing access boundaries.

Reproduction: Supply a missing or rejected cross-namespace edge with compatibility marked compatible.

Acceptance: Failures that prevent producer inspection require not-evaluated compatibility; valid evaluated edges followed by traversal timeout, depth limits or explicit cycles remain supported. Preserve existing release gates and include failing-then-passing browser regressions, current-head review and release verification.

Part of #1. Rough size: S.

Activity

  1. self-assigned this
    on Oct 4, 2026
  2. added theissue type on Oct 4, 2026
  3. added a commit that references this issue on Oct 4, 2026
  4. devantler commented on Oct 4, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Delivered by merged PR #265 at merge commit 4b0fde323d4fe62f6b430488bd514155c772988b. Exact-head required CI, current-head review, and the recorded real-browser user-path evaluation passed. Closing because this issue's acceptance criteria are now part of main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Fields

Priority

None yet

Effort

None yet

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions