Repository navigation
[Inline parity 5/6] Preserve separate reply-child context - #5
Closed
salmonumbrella wants to merge 13 commits into
Closed
salmonumbrella wants to merge 13 commits into
salmonumbrella wants to merge 13 commits into
Conversation
salmonumbrella
force-pushed
the
feat/inline-parity-child-context
branch
from
November 8, 2026 13:55
0d6838a to
5025621
Compare
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
Why
Inline reply children can have different audiences from their parents. Flattening them into Matrix threads would widen access; separate rooms still need enough context to remain understandable.
Usage
Pending topic retries require a later room event; idle rooms and failures before intent is saved need a later reconciliation.
No configuration change. Eligible separate children show parent context in their topic. Channel descriptions may populate empty or connector-owned topics; later user text is preserved. Temporary parent lookup failures retain existing context and suppress stale creation text. Hidden children remain excluded by default. Native child creation and Matrix thread routing remain unsupported.
Stacks on #4 (and its preceding dependencies).
Refs #1.