test(trails): promote semantic wayfinder dogfood smoke#799
Merged
graphite-app[bot] merged 1 commit intoJun 19, 2026
Merged
Conversation
Contributor
Author
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
There was a problem hiding this comment.
Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.
Merge activity
|
## Context Wayfinder dogfood was proving that the operator graph existed, but not enough of the new navigation layer semantics. This branch promotes the release smoke into a multi-app semantic fixture that catches graph-fact, relation, invalid grammar, and rejected-compile provenance drift. ## Changes - Compile demo and operator topo wrappers inside an isolated temp root. - Assert demo resources, signals, errors, deps, and impact facts from saved artifacts. - Assert invalid Wayfinder grammar fails visibly. - Assert rejected operator compile leaves prior demo artifacts fresh. - Preserve existing operator checks for overview, search, contract, outline, deps, impact, diff, and adapter facts. - Document the release gate in AGENTS.md and release docs, with a branch-local @ontrails/trails changeset. ## Verification - bun run wayfinder:dogfood - bun run --cwd apps/trails typecheck - bun run format:check - bun run docs:wrap-check - bun test apps/trails/src/__tests__/survey.test.ts packages/wayfinder/src/__tests__/loader.test.ts - bun run changeset:check - bun run check - bun run test - bun run build - bun run publish:check - git diff --check - gt submit --stack --draft --restack --no-edit --no-interactive --dry-run - Graphite pre-push hook passed during submit ## Local Review In-thread local review found no P0-P2 issues. One relevant P3 was fixed before submit: the signal impact assertion now requires the relation edge to originate from entity.updated, proving scoped relation output instead of merely matching any consumer edge.
c6fd0d0 to
a528239
Compare
bb8cbe8 to
de79459
Compare
Base automatically changed from
trl-1053-keep-wayfinder-artifact-drift-scoped-to-the-compiled-topo
to
main
June 19, 2026 22:31
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.

Context
Wayfinder dogfood was proving that the operator graph existed, but not enough of the new navigation layer semantics. This branch promotes the release smoke into a multi-app semantic fixture that catches graph-fact, relation, invalid grammar, and rejected-compile provenance drift.
Changes
Verification
Local Review
In-thread local review found no P0-P2 issues. One relevant P3 was fixed before submit: the signal impact assertion now requires the relation edge to originate from entity.updated, proving scoped relation output instead of merely matching any consumer edge.