Uh oh!
There was an error while loading. Please reload this page.
feat(twister,linear): structured-container taxonomy signals on links - #384
Merged
Conversation
LinkSignals gains taxonomy — namespaced keys for the structured containers an item belongs to (project, repository, board, folder), matched exactly against priority bindings so items route to the user's priorities without a model call. The Linear connector emits the issue's project (a container within the team; the team itself is already the sync channel). Claude-Session: https://claude.ai/code/session_01FHoQc2TdA62Wp4BwUxvR6P Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
Summary
LinkSignalsgainstaxonomy?: string[]— namespaced keys ("<connector>:<kind>:<id>") for the structured containers an item belongs to: its project, repository, board or folder. The platform matches these exactly against priority bindings so items route to the user's priorities without a model call. Immutable ids only (same rule aslink.source); omit when the source has no structured container.linear:project:<uuid>(the project is a container within a team; the team itself is already the sync channel, so it needs no key). The batch query now fetchesproject { id }.Test plan
signals.taxonomyentirely.tsc --noEmitclean,plot lintclean, changeset validated.🤖 Generated with Claude Code
https://claude.ai/code/session_01FHoQc2TdA62Wp4BwUxvR6P