Skip to content

fix(jira): queue busy turns async + reliable inline parentId replies - #248

Merged
patroza merged 2 commits into
fork/identityfrom
fix/jira-queue-and-inline-reply
Jul 31, 2026
Merged

fix(jira): queue busy turns async + reliable inline parentId replies#248
patroza merged 2 commits into
fork/identityfrom
fix/jira-queue-and-inline-reply

Conversation

@omegent-app

@omegent-app omegent-app Bot commented Jul 31, 2026

Copy link
Copy Markdown

Summary

  • Busy threads: always thread.turn.start — orchestration queues when mid-turn; no more “already working” short-circuit. Reply stays async via existing forkDetach(bridgeTurn).
  • Inline replies: Jira only accepts children under root comments. Nested parentId → 400 → we used to fall flat. Before POST, GET the trigger comment and use its parentId when set.
  • Webhook parsing accepts REST-style comment.parentId and ignores empty Automation parent.id.

Live evidence (SA-421)

Exact delivery this time:

  • Inbound: jira-comment:SA-421:71413 — Patrick @omegent on nested comment 71413 (parentId on REST is 71399, not in Automation payload).
  • Outbound busy reply 71415 was flat (parent: None / empty Automation parent).
  • Probe: parentId: 71413 → 400 Parent comment not found, and no child comments exist; parentId: 71399 → 200 with parentId: 71399.

Test plan

  • vp test run apps/server/src/jira/JiraWebhook.test.ts (23)
  • vp check (0 errors)
  • Manual: @omegent while thread is busy → no busy text; turn queues; reply posts when done
  • Manual: @omegent as nested reply → bot reply has REST parentId = thread root

opened by Patrick Roza in chat thread Discord · Discord

@patroza
patroza force-pushed the fork/identity branch 5 times, most recently from e5e3872 to 180a4be Compare July 31, 2026 09:28
@patroza
patroza force-pushed the fix/jira-queue-and-inline-reply branch 5 times, most recently from 1823660 to 97f1ede Compare July 31, 2026 09:37
@patroza
patroza enabled auto-merge (squash) July 31, 2026 09:37
@omegent-app @patroza @github-actions
fix(jira): queue busy turns async; resolve thread root for inline rep…
86a1581 
…lies

Stop short-circuiting busy threads with "already working" — always
dispatch thread.turn.start so orchestration queues the message, and keep
bridgeTurn fork-detached (async reply when the turn finishes).

Make parentId threading reliable: Jira only accepts children under root
comments (nested parentId → 400, then we used to fall flat). GET the
trigger comment and use its parentId when set before posting. Accept
comment.parentId on webhooks; ignore empty Automation parent.id.

Live evidence SA-421: reply 71415 was flat because parent was nested
71413 (true root 71399); parentId=71399 succeeds.

Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
@patroza
patroza force-pushed the fix/jira-queue-and-inline-reply branch from 97f1ede to 86a1581 Compare July 31, 2026 09:40
@patroza
patroza disabled auto-merge July 31, 2026 09:43
@patroza
patroza merged commit 87f2ca5 into fork/identity Jul 31, 2026
3 checks passed
patroza added a commit that referenced this pull request Jul 31, 2026
@omegent-app @patroza @github-actions
fix(jira): queue busy turns async; resolve thread root for inline rep…
73b36dd 
…lies (#248)

Stop short-circuiting busy threads with "already working" — always
dispatch thread.turn.start so orchestration queues the message, and keep
bridgeTurn fork-detached (async reply when the turn finishes).

Make parentId threading reliable: Jira only accepts children under root
comments (nested parentId → 400, then we used to fall flat). GET the
trigger comment and use its parentId when set before posting. Accept
comment.parentId on webhooks; ignore empty Automation parent.id.

Live evidence SA-421: reply 71415 was flat because parent was nested
71413 (true root 71399); parentId=71399 succeeds.

Co-authored-by: omegent-app[bot] <306514130+omegent-app[bot]@users.noreply.github.com>
Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
patroza added a commit that referenced this pull request Jul 31, 2026
@omegent-app @patroza @github-actions
fix(jira): queue busy turns async; resolve thread root for inline rep…
22e799b 
…lies (#248)

Stop short-circuiting busy threads with "already working" — always
dispatch thread.turn.start so orchestration queues the message, and keep
bridgeTurn fork-detached (async reply when the turn finishes).

Make parentId threading reliable: Jira only accepts children under root
comments (nested parentId → 400, then we used to fall flat). GET the
trigger comment and use its parentId when set before posting. Accept
comment.parentId on webhooks; ignore empty Automation parent.id.

Live evidence SA-421: reply 71415 was flat because parent was nested
71413 (true root 71399); parentId=71399 succeeds.

Co-authored-by: omegent-app[bot] <306514130+omegent-app[bot]@users.noreply.github.com>
Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
patroza added a commit that referenced this pull request Jul 31, 2026
@omegent-app @patroza @github-actions
fix(jira): queue busy turns async; resolve thread root for inline rep…
2decba0 
…lies (#248)

Stop short-circuiting busy threads with "already working" — always
dispatch thread.turn.start so orchestration queues the message, and keep
bridgeTurn fork-detached (async reply when the turn finishes).

Make parentId threading reliable: Jira only accepts children under root
comments (nested parentId → 400, then we used to fall flat). GET the
trigger comment and use its parentId when set before posting. Accept
comment.parentId on webhooks; ignore empty Automation parent.id.

Live evidence SA-421: reply 71415 was flat because parent was nested
71413 (true root 71399); parentId=71399 succeeds.

Co-authored-by: omegent-app[bot] <306514130+omegent-app[bot]@users.noreply.github.com>
Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
patroza added a commit that referenced this pull request Jul 31, 2026
@omegent-app @patroza @github-actions
fix(jira): queue busy turns async; resolve thread root for inline rep…
871684c 
…lies (#248)

Stop short-circuiting busy threads with "already working" — always
dispatch thread.turn.start so orchestration queues the message, and keep
bridgeTurn fork-detached (async reply when the turn finishes).

Make parentId threading reliable: Jira only accepts children under root
comments (nested parentId → 400, then we used to fall flat). GET the
trigger comment and use its parentId when set before posting. Accept
comment.parentId on webhooks; ignore empty Automation parent.id.

Live evidence SA-421: reply 71415 was flat because parent was nested
71413 (true root 71399); parentId=71399 succeeds.

Co-authored-by: omegent-app[bot] <306514130+omegent-app[bot]@users.noreply.github.com>
Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
@patroza patroza mentioned this pull request Jul 31, 2026
Closed
patroza added a commit that referenced this pull request Jul 31, 2026
@omegent-app @patroza @github-actions
fix(jira): queue busy turns async; resolve thread root for inline rep…
21c6abf 
…lies (#248)

Stop short-circuiting busy threads with "already working" — always
dispatch thread.turn.start so orchestration queues the message, and keep
bridgeTurn fork-detached (async reply when the turn finishes).

Make parentId threading reliable: Jira only accepts children under root
comments (nested parentId → 400, then we used to fall flat). GET the
trigger comment and use its parentId when set before posting. Accept
comment.parentId on webhooks; ignore empty Automation parent.id.

Live evidence SA-421: reply 71415 was flat because parent was nested
71413 (true root 71399); parentId=71399 succeeds.

Co-authored-by: omegent-app[bot] <306514130+omegent-app[bot]@users.noreply.github.com>
Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
patroza added a commit that referenced this pull request Jul 31, 2026
@omegent-app @patroza @github-actions
fix(jira): queue busy turns async; resolve thread root for inline rep…
1c5d314 
…lies (#248)

Stop short-circuiting busy threads with "already working" — always
dispatch thread.turn.start so orchestration queues the message, and keep
bridgeTurn fork-detached (async reply when the turn finishes).

Make parentId threading reliable: Jira only accepts children under root
comments (nested parentId → 400, then we used to fall flat). GET the
trigger comment and use its parentId when set before posting. Accept
comment.parentId on webhooks; ignore empty Automation parent.id.

Live evidence SA-421: reply 71415 was flat because parent was nested
71413 (true root 71399); parentId=71399 succeeds.

Co-authored-by: omegent-app[bot] <306514130+omegent-app[bot]@users.noreply.github.com>
Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
patroza added a commit that referenced this pull request Jul 31, 2026
@omegent-app @patroza @github-actions
fix(jira): queue busy turns async; resolve thread root for inline rep…
c35abca 
…lies (#248)

Stop short-circuiting busy threads with "already working" — always
dispatch thread.turn.start so orchestration queues the message, and keep
bridgeTurn fork-detached (async reply when the turn finishes).

Make parentId threading reliable: Jira only accepts children under root
comments (nested parentId → 400, then we used to fall flat). GET the
trigger comment and use its parentId when set before posting. Accept
comment.parentId on webhooks; ignore empty Automation parent.id.

Live evidence SA-421: reply 71415 was flat because parent was nested
71413 (true root 71399); parentId=71399 succeeds.

Co-authored-by: omegent-app[bot] <306514130+omegent-app[bot]@users.noreply.github.com>
Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
patroza added a commit that referenced this pull request Jul 31, 2026
@omegent-app @patroza @github-actions
fix(jira): queue busy turns async; resolve thread root for inline rep…
18b3b3d 
…lies (#248)

Stop short-circuiting busy threads with "already working" — always
dispatch thread.turn.start so orchestration queues the message, and keep
bridgeTurn fork-detached (async reply when the turn finishes).

Make parentId threading reliable: Jira only accepts children under root
comments (nested parentId → 400, then we used to fall flat). GET the
trigger comment and use its parentId when set before posting. Accept
comment.parentId on webhooks; ignore empty Automation parent.id.

Live evidence SA-421: reply 71415 was flat because parent was nested
71413 (true root 71399); parentId=71399 succeeds.

Co-authored-by: omegent-app[bot] <306514130+omegent-app[bot]@users.noreply.github.com>
Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
patroza added a commit that referenced this pull request Jul 31, 2026
@omegent-app @patroza @github-actions
fix(jira): queue busy turns async; resolve thread root for inline rep…
cc20a43 
…lies (#248)

Stop short-circuiting busy threads with "already working" — always
dispatch thread.turn.start so orchestration queues the message, and keep
bridgeTurn fork-detached (async reply when the turn finishes).

Make parentId threading reliable: Jira only accepts children under root
comments (nested parentId → 400, then we used to fall flat). GET the
trigger comment and use its parentId when set before posting. Accept
comment.parentId on webhooks; ignore empty Automation parent.id.

Live evidence SA-421: reply 71415 was flat because parent was nested
71413 (true root 71399); parentId=71399 succeeds.

Co-authored-by: omegent-app[bot] <306514130+omegent-app[bot]@users.noreply.github.com>
Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
patroza added a commit that referenced this pull request Jul 31, 2026
@omegent-app @patroza @github-actions
fix(jira): queue busy turns async; resolve thread root for inline rep…
4a82923 
…lies (#248)

Stop short-circuiting busy threads with "already working" — always
dispatch thread.turn.start so orchestration queues the message, and keep
bridgeTurn fork-detached (async reply when the turn finishes).

Make parentId threading reliable: Jira only accepts children under root
comments (nested parentId → 400, then we used to fall flat). GET the
trigger comment and use its parentId when set before posting. Accept
comment.parentId on webhooks; ignore empty Automation parent.id.

Live evidence SA-421: reply 71415 was flat because parent was nested
71413 (true root 71399); parentId=71399 succeeds.

Co-authored-by: omegent-app[bot] <306514130+omegent-app[bot]@users.noreply.github.com>
Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
patroza added a commit that referenced this pull request Jul 31, 2026
@omegent-app @patroza @github-actions
fix(jira): queue busy turns async; resolve thread root for inline rep…
33ca07e 
…lies (#248)

Stop short-circuiting busy threads with "already working" — always
dispatch thread.turn.start so orchestration queues the message, and keep
bridgeTurn fork-detached (async reply when the turn finishes).

Make parentId threading reliable: Jira only accepts children under root
comments (nested parentId → 400, then we used to fall flat). GET the
trigger comment and use its parentId when set before posting. Accept
comment.parentId on webhooks; ignore empty Automation parent.id.

Live evidence SA-421: reply 71415 was flat because parent was nested
71413 (true root 71399); parentId=71399 succeeds.

Co-authored-by: omegent-app[bot] <306514130+omegent-app[bot]@users.noreply.github.com>
Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
patroza added a commit that referenced this pull request Jul 31, 2026
@omegent-app @patroza @github-actions
fix(jira): queue busy turns async; resolve thread root for inline rep…
f87f3a1 
…lies (#248)

Stop short-circuiting busy threads with "already working" — always
dispatch thread.turn.start so orchestration queues the message, and keep
bridgeTurn fork-detached (async reply when the turn finishes).

Make parentId threading reliable: Jira only accepts children under root
comments (nested parentId → 400, then we used to fall flat). GET the
trigger comment and use its parentId when set before posting. Accept
comment.parentId on webhooks; ignore empty Automation parent.id.

Live evidence SA-421: reply 71415 was flat because parent was nested
71413 (true root 71399); parentId=71399 succeeds.

Co-authored-by: omegent-app[bot] <306514130+omegent-app[bot]@users.noreply.github.com>
Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
patroza added a commit that referenced this pull request Jul 31, 2026
@omegent-app @patroza @github-actions
fix(jira): queue busy turns async; resolve thread root for inline rep…
612d353 
…lies (#248)

Stop short-circuiting busy threads with "already working" — always
dispatch thread.turn.start so orchestration queues the message, and keep
bridgeTurn fork-detached (async reply when the turn finishes).

Make parentId threading reliable: Jira only accepts children under root
comments (nested parentId → 400, then we used to fall flat). GET the
trigger comment and use its parentId when set before posting. Accept
comment.parentId on webhooks; ignore empty Automation parent.id.

Live evidence SA-421: reply 71415 was flat because parent was nested
71413 (true root 71399); parentId=71399 succeeds.

Co-authored-by: omegent-app[bot] <306514130+omegent-app[bot]@users.noreply.github.com>
Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
bcb98eb 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
edcc7f0 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
a030eae 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
ed35cd4 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
9fed9a0 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
06566c9 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
6e5230f 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
30908c7 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
bb76d7e 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
a6fc4fd 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
59ecd4b 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
a3d1305 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
9e3f4da 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
fef90d7 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
4369add 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
fda3935 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
b47b115 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
69d7e57 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
c9d5c04 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
1bea296 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
dee1641 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
14161cb 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
e088281 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
c10b85e 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
a81d76a 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
aa5ec4b 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
7d3bb4f 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
3dab323 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
76d1d32 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
patroza pushed a commit that referenced this pull request Jul 31, 2026
@github-actions
feat(identity): session identity overlay with participation and Jira …
b31e77e 
…fixes

Identity product layer based on current fork/changes: session claims,
source attribution, participant UI (#247), and Jira queue/inline replies
(#248), with mobile typecheck fixes for stage label and toolbar clearance.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@patroza