Skip to content

fix(dashboard): nest a member-driven crew under its creator in the conductor lane - #14462

Merged
bolichen97 merged 2 commits into
mainfrom
fix/conductor-lane-member-creator-anchor
Sep 27, 2026
Merged

bolichen97 merged 2 commits into
mainfrom
fix/conductor-lane-member-creator-anchor

Conversation

@chenmingwei23

@chenmingwei23 chenmingwei23 commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: In the sidebar's conductor lane, a crew whose conductor is a crew member reads as ONE unit of work: its workers nest under the member's thread instead of scattering across the top level - and every crew arrives collapsed, so a lane with three crews reads as three rows, not thirty.

Open the conductor lane while a crew member (for example kirocrew-pipeline-conductor) is dispatching workers through session_create. Every one of its workers sits at the top level, each wearing the bent-arrow glyph whose tooltip says opened by a closed session - while the member is open, running, and visible on the System page's Sessions table with those same workers nested under it. The screenshot pair below is the actual state of one such sidebar: a dozen issue-fix: rows scattered through the list, none of them attached to anything.

Why it matters

The lane exists so that a conductor and its workers can be read together. Member-driven crews are the ones with the most workers (the pipeline conductor alone runs ten to thirty at a time), so this is the case where the nesting matters most and it is exactly the case that did not nest. The glyph also states a falsehood about a live session - "closed" - which sends a reader to look for a creator that is running.

Not a goal

  • Listing folded state per user in the backend: the fold set stays in localStorage, as before.
  • Listing crew members' own DM threads in the Sessions sidebar as ordinary rows. They stay on the Members page; the lane draws one only as a dimmed anchor, only while a worker of it is on screen.
  • Changing how the backend resolves parent.key. The wire was correct: the backend already resolved the citation to the member's live slot.
  • Anything about the folder or flat lanes, or the System page's Sessions tab, which keeps showing every row open. The conductor lane's collapsed default is the sidebar's own: it is the surface where a member crew's ten to thirty workers otherwise fill the whole rail.

What changed (motivation -> approach -> change)

Symptom -> root cause: ChatPage filters dashboard.slots by isChatPageSurface(surface ?? mode) before the list reaches ChatSidebar (ChatPage.tsx:535), and a member's DM slot is mode: 'member' / surface: 'member'. So the sidebar's population never contained the member's row. nestsUnder requires the cited key to name a row in the population it is given; it did not, so each worker became a root, and citedCreatorExists (built over the same population) could not find the creator either, so the row took the orphan glyph rather than the cites-parent one. The System page reads /api/sessions/memory, which carries every session, so it nested fine - the two views diverged on exactly one kind of creator.

Change, in website/src/pages/ChatSidebar.tsx:

  • creatorAnchors: for the conductor lane only, walk from every listed local row to the creator its parent.key names; when that creator is a live local slot in dashboard.slots but not in the listed rows, admit it. The walk is transitive (member -> lead -> worker) and bounded by the live population. Peer rows are excluded: their parent.key is in another gateway's key space and is resolved against the peer listing already.
  • lanePopulation = allRows + creatorAnchors feeds citedCreatorExists, conductorRows and the adoption-move tracker. conductorMatching is unchanged (built from flatSlots), so a borrowed creator can never be a match: it renders as the existing dimmed anchor with its chevron, only while a descendant is on screen.
  • SessionRow gains onOpenElsewhere. renderSessionRow sets it for any local row whose surface the chat page does not render, navigating to /members?member=<agent>. With it set, click and Enter go there instead of switchSlot; rename, close, fork, drag and the row menu are withheld exactly as they are for a peer row (foreignRow = !!peerId || onOpenElsewhere != null); the hover title says where the row opens.
  • One new string, pages.chatSidebar.opens_on_members_page, in en.manual.json and every shipped locale (en-XA regenerated).
  • website/capture/session-tree-member-anchor.{html,tsx} + scripts/capture-session-tree-member-anchor.mjs: an isolated capture entry that reproduces the product's store-vs-prop split through the real ChatSidebar, plus a behaviour check (worker depths before and after, the orphan glyph, the anchor's depth and dimming, its hover title, and an unrelated chat-conductor control pair).

Second commit - collapsed by default (maintainer decision, 2026-09-27). With the workers attached to their creator, a fully expanded lane still did not read as N crews: the maintainer opened it on a live box and asked for every crew to arrive shut. This supersedes the expanded default #13676 recorded one day earlier; that decision was made before a member-driven crew had ever nested here, and the shut row keeps everything #13676 wanted visible (chevron, child count, the subtree's needs-you / running badges).

  • Every crew in the conductor lane arrives collapsed, at every level. The row carries its child count plus the subtree's aggregate badges; one press on the chevron opens it.
  • The persisted fold set flips sense: mc-sidebar-conductor-expanded holds the rows the user has OPENED. A row absent from it is shut. The superseded mc-sidebar-conductor-collapsed key is deleted on first read (a user's old "folded away" set is the new default, so nothing they hid comes back open).
  • Reveal, adoption, search and session_create behave as before around the new default: a revealed or newly adopted row opens its ancestors so the row is on screen.
  • The anchor row wears a small Members page chip with the leave-this-page glyph (pages.chatSidebar.members_page_chip) so the page jump is visible text naming the DESTINATION, not hover-only and not the bare noun "Members", which in this product also means the crew's participants; the child count carries N sessions this one opened as its accessible name and tooltip (pages.chatSidebar.opened_sessions_count, plural, registered in pluralKeys.json), so the bare number has a unit.
  • docs/feature-map/README.md, Sessions row: records the collapsed default, the new key, and the member-anchor behaviour.
  • The adoption bookkeeping skips a provisional row (lineage_pending): the cold-start frame ships every row parent: null while the gateway's projection seeds, and recording those nulls would read the settling frame's citations as one move per row and persist every crew open on every reload. Skipped, the settling frame is each row's first sighting - a creation - so the collapsed default holds; a row seen settled before keeps the baseline it had.

Backwards compatibility

Compatible on the wire and in the backend. The only new rows are creators that were previously absent, and they carry no local-only affordance. Client-side, the fold set changes name and sense: mc-sidebar-conductor-collapsed (what the user closed) is removed on first read and mc-sidebar-conductor-expanded (what the user opened) starts empty. A user who had folded a conductor away still finds it folded, because folded is now the default; what they lose is any crew they had left open, which reopens with one press.

Tests

website/src/test/ChatSidebar.conductorLane.test.tsx, new block a creator this page does not list, run with npx vitest run src/test/ChatSidebar.conductorLane.test.tsx - 55 passed (46 existing + 6 anchor pins + 2 UX pins: the Members page chip on the anchor and not on a worker; the child count's accessible name + 1 cold-start pin: a lineage_pending frame followed by the settled one leaves every crew shut and the opened set empty; reverting the one-line guard reddens exactly that pin). The harness gained an optional storeSlots argument so the store can hold more than the prop, which is the split under test.

  • draws the member as a top-level anchor and nests its workers at depth 1 with neither citation glyph
  • the anchor is drawn only while a worker of it is on screen (an unrelated crew borrows nothing)
  • follows a chain of unlisted creators (member -> lead -> worker nests at depth 2)
  • clicking or pressing Enter on the anchor navigates to /members?member=kirocrew-pipeline-conductor and leaves chat.activeSlot untouched
  • the anchor is not draggable, has no close/fork controls, and its title names the Members page; a listed worker beside it keeps everything
  • a creator that is genuinely gone (parent.key: null, no such slot in the store) still reads as an orphan

Mutation check: with website/src/pages/ChatSidebar.tsx alone replaced by its origin/main version and the same file re-run, the result is 4 failed | 48 passed (52) - four of the six new anchor pins redden and the two guard pins (the "borrows nothing" and "still reads as an orphan" cases) stay green, which is what those two are for. The file was restored and verified byte-identical by sha256 afterwards.

Collapsed default, same file: the pin is EXPANDED by default is rewritten to is COLLAPSED by default, plus pins for the shut row's count and aggregate, the opened-set persistence, the migration that deletes the old key, and reveal / adopt / search opening ancestors. Mutation check: inverting the default (!conductorExpanded.has(key)) reddens exactly the 3 default pins and leaves the other 51 green.

website/src/test/ChatSidebar.laneFolderHideParity.test.tsx - 32 passed. Its beforeEach now opens the one crew the fixture nests, because a shut crew would hide the nested child for a reason unrelated to folder hiding, which is what that file tests.

Also run: tsc -p tsconfig.app.json clean; eslint on the changed files clean; node scripts/i18n-check.mjs exit 0 (19 checks); node scripts/check-i18n-keys.mjs exit 0; node scripts/gen-pseudolocale.mjs regenerated en-XA.

Manual verification

node scripts/capture-session-tree-member-anchor.mjs against a dev server on the final head: every check ok, RESULT: ok - before: three workers at depth 0, each with data-orphan-of="member-kirocrew-pipeline-conductor", and no member row present; after: member at depth 0 with data-conductor-anchor="true" and opacity=0.55, workers at depth 1, zero orphan glyphs, the anchor's title naming the Members page, control pair (chat conductor + worker) unchanged.

Screenshots / video

Before - the state Raymond's sidebar was in: the pipeline conductor's workers float at the top level with the "closed creator" glyph.

before

After, shut by default (final head) - the member-driven crew is one dimmed anchor row: the Members page chip with the leave-this-page glyph, the child count (3) and the subtree's needs-you / running badges; no worker on screen.

shut by default

After, opened (final head) - one press on the chevron nests the three workers one level under it; the aggregate leaves with the fold, the count stays. The unrelated chat conductor beside it is unchanged.

opened

Related Issues

Part of #12757 (conductor lane / session tree). Supersedes the expanded-by-default decision of #13676 for the conductor lane (maintainer decision 2026-09-27, recorded above and in the feature map).

Pattern harvest

Rule candidate: review-prompt
Pattern: a view derives a relation over a FILTERED population and then labels the unresolved side with a fact ("closed", "gone", "missing") that is only true of the UNFILTERED one. When a component receives a pre-filtered list and joins on identities that can point outside it, the join and any "does X exist" glyph must read the full population, or the glyph must be phrased as "not shown here".

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated - docs/feature-map/README.md Sessions row now states the collapsed default, the mc-sidebar-conductor-expanded key, and the member-anchor row
  • No secrets, credentials, or internal references in the diff

before-member-driven-crew-orphaned

…nductor lane

ChatPage filters dashboard.slots by surface before the sidebar sees them, so a
crew member's own DM thread (surface 'member') never reached the conductor lane.
Every worker it opened cited it with a live parent.key, found no row for that
key, and rendered at the top level wearing the "opened by a closed session"
glyph while the System page nested the same rows.

The lane now borrows an unlisted live local creator from the full slot list,
transitively, as a dimmed anchor row. The anchor opens on the Members page and
withholds rename/close/fork/drag like a peer row.
@chenmingwei23
chenmingwei23 requested a review from a team September 27, 2026 11:22
@chenmingwei23
chenmingwei23 requested a review from a team as a code owner September 27, 2026 11:22
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Sep 27, 2026
@github-actions

github-actions Bot commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor

GPT 5.6 Review — ✅ no blocking findings

GPT 5.6 completed its review of 6e87a9d0b897373a0bb2bb65e77d7b7a6dcf50f3 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 6e87a9d

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 6e87a9d0b897373a0bb2bb65e77d7b7a6dcf50f3: <one-sentence reason>

@github-actions

github-actions Bot commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Fable 5) — ✅ PASS

Design-level review of 6e87a9d0b897373a0bb2bb65e77d7b7a6dcf50f3 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: PASS

Confirm the 2026-09-27 maintainer ask to collapse by default — it reverses #13676 from one day earlier and exists only as this PR's assertion.

[DESIGN-REVIEWED] 6e87a9d

@github-actions

github-actions Bot commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Fable 5) — ✅ human override accepted

@chenmingwei23 overrode this lane for 6e87a9d0b897373a0bb2bb65e77d7b7a6dcf50f3 via /ai-review override (this commit only).

@github-actions

github-actions Bot commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Fable 5) — 🟡 CONCERNS

UX-level review of 6e87a9d0b897373a0bb2bb65e77d7b7a6dcf50f3 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

UX-Verdict: CONCERNS

Clicking the anchor row leaves the chat page, but the blind reader expected it to open the conversation in place — only the small chip hints at the jump.

Watch

  • Anchor-row click is a surprise navigation. The reader read the row as "a conversation… clicking the row probably opens the conversation itself" and only the tag as "a link that takes me somewhere else entirely"; the diff routes the whole row's click/Enter to /members?member=…. Hit on every member-driven crew until learned; disorienting but one back-press to recover. Smallest fix: change pages.chatSidebar.members_page_chip from the noun "Members page" to the behavior "Opens on Members page", so the chip describes the row's click, not a separate link.
  • Collapsed-by-default makes the aggregate badges the crew's entire status, and the reader could not decode the running one: "1 thing repeating or retrying… I genuinely don't know" (needs-you was guessed right). The glyphs and their hover-only tooltips predate this PR, but this PR promotes them to every crew's default face — worth a human look at whether the running glyph reads at that exposure.

[UX-REVIEWED] 6e87a9d

@github-actions

github-actions Bot commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5 Review — ✅ no blocking findings

Reviewed 6e87a9d0b897373a0bb2bb65e77d7b7a6dcf50f3 — this comment is updated in place on each push.

Review details

Keyboard jump order publishes rows the chat page cannot open, so a digit chord lands on a different session than the badge it reads.

FINDING — website/src/pages/ChatSidebar.tsx:6076 — creatorAnchors borrows a surface: 'member' row from allLiveSlots, and renderSessionRow stamps it data-session-row (not inert), so it enters shortcutOrderKeys → dispatch(setSidebarOrder(...)); shortcutDigitByKey then continues past it without advancing idx because live = new Set(localSlots.map(s => s.key)) is the surface-filtered prop, while useKeyboardShortcuts.ts:798 builds orderSlotsBySidebar(slots, sidebarOrder) from the unfiltered dashboard.slots and keeps it at that index — so with the modifier held the row badged 1 is the first worker but Alt/Ctrl+1 kbSwitches to the member's DM thread, every later digit/letter and the ⌘[/⌘] cycle is shifted by the anchor count, and activeSlot lands on a slot ChatPage's filteredSlots cannot render → Fix: drop keys failing isChatPageSurface from the DOM read at ChatSidebar.tsx:6431 before setShortcutOrderKeys, so both consumers see the same population.

FINDING — website/src/pages/ChatSidebar.tsx:9959 — const expanded = conductorExpanded.has(key) with readConductorExpanded() returning an empty set (the superseded mc-sidebar-conductor-collapsed key is deleted, so every existing conductor-lane user starts empty) makes emit hit if (!expanded) return before recursing, and the only two callers of expandConductorAncestors are the citation-change effect (6349) and an explicit requestSlotReveal menu item (6915) — so a user whose active session is a nested worker reloads or cycles into the conductor lane and their current session has no row and no aria-current highlight anywhere, unlike the stale-collapse fold which exempts s.key === activeSlot at 4631 → Fix: in emit, treat a row on activeSlot's ancestor chain as expanded without persisting it.

[OPUS-REVIEWED] 6e87a9d

Verdict parsed from the review's SHA-scoped output markers for commit 6e87a9d0b897373a0bb2bb65e77d7b7a6dcf50f3.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 6e87a9d0b897373a0bb2bb65e77d7b7a6dcf50f3: <one-sentence reason>

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision labels Sep 27, 2026
@chenmingwei23
chenmingwei23 force-pushed the fix/conductor-lane-member-creator-anchor branch from e60e1bc to 31b6b24 Compare September 27, 2026 13:09
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Sep 27, 2026
@chenmingwei23

Copy link
Copy Markdown
Contributor Author

Capture frames on head 219d757678 - capture-session-tree-member-anchor.mjs, RESULT: ok, 24/24 checks.

Shut by default - the member-driven crew is one dimmed anchor row: the Members chip, the child count (3, accessible name "3 sessions this one opened") and the subtree's needs-you / running badges. No worker on screen.

shut by default

Opened - one press on the chevron nests the three workers one level under it. The aggregate leaves with the fold; the count stays.

opened

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Sep 27, 2026
@chenmingwei23

Copy link
Copy Markdown
Contributor Author

/ai-review override first-principles 219d757: Maintainer decision 2026-09-27: the conductor lane arrives collapsed by default, superseding #13676's expanded default for this lane; recorded in the PR description and docs/feature-map/README.md Sessions row.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@chenmingwei23 marked the first-principles AI finding as false positive, not applicable, or explicitly accepted for 219d7576783c4658b9a32b18f5fcd5ce8b20749e.

Maintainer decision 2026-09-27: the conductor lane arrives collapsed by default, superseding #13676's expanded default for this lane; recorded in the PR description and docs/feature-map/README.md Sessions row.

This decision applies only to this commit. A new push requires a new judgment.

@chenmingwei23
chenmingwei23 force-pushed the fix/conductor-lane-member-creator-anchor branch from 219d757 to 8b751d7 Compare September 27, 2026 14:10
@github-actions github-actions Bot removed the readiness: action required A blocking check or review needs attention label Sep 27, 2026
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Sep 27, 2026
@chenmingwei23

Copy link
Copy Markdown
Contributor Author

/ai-review override first-principles 8b751d7: Maintainer decision 2026-09-27: the conductor lane arrives collapsed by default, superseding #13676's expanded default for this lane; recorded in the PR description and docs/feature-map/README.md Sessions row. Re-posted after a dead-catalog-key fix moved the head.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@chenmingwei23 marked the first-principles AI finding as false positive, not applicable, or explicitly accepted for 8b751d7de54b0cc571c12004d25c0ae8c49bfc34.

Maintainer decision 2026-09-27: the conductor lane arrives collapsed by default, superseding #13676's expanded default for this lane; recorded in the PR description and docs/feature-map/README.md Sessions row. Re-posted after a dead-catalog-key fix moved the head.

This decision applies only to this commit. A new push requires a new judgment.

@chenmingwei23
chenmingwei23 force-pushed the fix/conductor-lane-member-creator-anchor branch from 8b751d7 to 87ea60c Compare September 27, 2026 14:22
@chenmingwei23

Copy link
Copy Markdown
Contributor Author

/ai-review override first-principles 87ea60c: Maintainer decision 2026-09-27: the conductor lane arrives collapsed by default, superseding #13676's expanded default for this lane; recorded in the PR description and docs/feature-map/README.md Sessions row. Re-posted after a feature-map wording fix moved the head.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@chenmingwei23 marked the first-principles AI finding as false positive, not applicable, or explicitly accepted for 87ea60c8dcd1b5d73f9d778051a2be01d552065c.

Maintainer decision 2026-09-27: the conductor lane arrives collapsed by default, superseding #13676's expanded default for this lane; recorded in the PR description and docs/feature-map/README.md Sessions row. Re-posted after a feature-map wording fix moved the head.

This decision applies only to this commit. A new push requires a new judgment.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Sep 27, 2026
@chenmingwei23
chenmingwei23 force-pushed the fix/conductor-lane-member-creator-anchor branch from 87ea60c to 666e32c Compare September 27, 2026 14:51
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Sep 27, 2026
@chenmingwei23

Copy link
Copy Markdown
Contributor Author

/ai-review override first-principles 666e32c: Maintainer decision 2026-09-27: the conductor lane arrives collapsed by default, superseding #13676's expanded default for this lane; recorded in the PR description and docs/feature-map/README.md Sessions row. Re-posted after the anchor chip was reworded for the UX lane.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@chenmingwei23 marked the first-principles AI finding as false positive, not applicable, or explicitly accepted for 666e32c2db056bceeaca777f312f3ac062d17789.

Maintainer decision 2026-09-27: the conductor lane arrives collapsed by default, superseding #13676's expanded default for this lane; recorded in the PR description and docs/feature-map/README.md Sessions row. Re-posted after the anchor chip was reworded for the UX lane.

This decision applies only to this commit. A new push requires a new judgment.

Requested by the maintainer on 2026-09-27 after seeing the lane with every
member-driven crew open: even once the workers were attached to their creator,
a fully expanded lane still did not read as N crews. Every crew now arrives
collapsed at every level, as one row carrying its child count and the
subtree's needs-you / running badges, and the person opens the crews they care
about.

The persisted fold set flips sense: mc-sidebar-conductor-expanded holds the
rows the user has opened, and a row absent from it is shut. The superseded
mc-sidebar-conductor-collapsed key is removed on first read. Reveal, adoption,
search and session_create behave as before around the new default.

Alongside, for the two reviewer notes on the anchor row: the row wears a small
"Members" chip so the page jump is visible text and not hover-only, and the
child count carries "N sessions this one opened" as its accessible name and
tooltip so the bare number has a unit. The feature-map Sessions row records
the collapsed default, the new key and the member-anchor behaviour.
@chenmingwei23
chenmingwei23 force-pushed the fix/conductor-lane-member-creator-anchor branch from 666e32c to 6e87a9d Compare September 27, 2026 15:06
@chenmingwei23

Copy link
Copy Markdown
Contributor Author

/ai-review override first-principles 6e87a9d: Maintainer decision 2026-09-27: the conductor lane arrives collapsed by default, superseding #13676's expanded default for this lane; recorded in the PR description and docs/feature-map/README.md Sessions row. Re-posted after the cold-start lineage_pending guard moved the head.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@chenmingwei23 marked the first-principles AI finding as false positive, not applicable, or explicitly accepted for 6e87a9d0b897373a0bb2bb65e77d7b7a6dcf50f3.

Maintainer decision 2026-09-27: the conductor lane arrives collapsed by default, superseding #13676's expanded default for this lane; recorded in the PR description and docs/feature-map/README.md Sessions row. Re-posted after the cold-start lineage_pending guard moved the head.

This decision applies only to this commit. A new push requires a new judgment.

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Sep 27, 2026

@bolichen97 bolichen97 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed on behalf of the maintainers (sweep 2026-09-27): readiness passed, required checks green on 6e87a9d, no blocking review threads, security posture unchanged. Approving and merging.

@bolichen97
bolichen97 merged commit 45803ef into main Sep 27, 2026
97 of 98 checks passed
@bolichen97
bolichen97 deleted the fix/conductor-lane-member-creator-anchor branch September 27, 2026 17:06
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Sep 27, 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