Repository navigation
Align relation listing and trace validity - #653
Merged
transitrix-foundry-reviewer[bot] merged 1 commit intoOct 18, 2026
Merged
Conversation
Signed-off-by: transitrix <automation@transitrix.com>
transitrix-foundry-reviewer
Bot
deleted the
fix/relation-trace-validity
branch
October 18, 2026 18:32
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Relation listings and trace coverage now require the relation itself and both endpoints to be admitted and effective on the render date. Missing or invalid lifecycle bounds no longer count as unbounded validity. Supported
former_idsresolve to current identities, repeated evidence stays in listings, and trace coverage deduplicates resolved pairs.The consumer guide documents the complete-catalogue reporting validation gate, exact prerequisite source revisions, and the distinction between generic projection and subtype/graph validation. Source and packed-package support retain the existing sibling package layout; package versions are unchanged.
How it is verified
node packages/document-view-engine/tests/test_reporting.mjs: 20 reporting integration/regression checks pass against the shipped dated forward/reverse oracle.python3 tools/tests/test_reporting.py: 16 tests pass.npm packoutput for engine 0.0.1 and renderer 0.0.1 passes four dated listing/trace comparisons against the reporting oracle when extracted in the supported sibling layout.git diff --check: passes.The separate reporting integration command requires Python 3.12 and PyYAML 6.0.1. Existing CI continues to run the five Node.js view-engine suites; workflow configuration is unchanged.