Skip to content

[Inline parity 5/6] Preserve separate reply-child context - #5

Closed
salmonumbrella wants to merge 13 commits into
inline-chat:mainfrom
salmonumbrella:feat/inline-parity-child-context
Closed

salmonumbrella wants to merge 13 commits into
inline-chat:mainfrom
salmonumbrella:feat/inline-parity-child-context

Conversation

@salmonumbrella

@salmonumbrella salmonumbrella commented Nov 8, 2026 •

Copy link
Copy Markdown

What changed

  • Retry pending topic updates on later room events, with a per-room limit.
  • Keep eligible child conversations in separate rooms with their own history and access.
  • Retain readable source parent context and an existing-only backlink scoped to the same login.
  • Reject unsupported Matrix threads and foreign portal/receiver reply targets before mutation.
  • Journal generated topic intent before writes and retract only owned context after an authoritative detach.
  • Preserve hidden-dialog exclusion and return an explicit error for unsupported thread-history requests.

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.

@salmonumbrella
salmonumbrella force-pushed the feat/inline-parity-child-context branch from 0d6838a to 5025621 Compare November 8, 2026 13:55
@morajabi morajabi closed this Nov 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants