Skip to content

spec(FIX-2161): an ordinary session of any worker can open on a project - #3805

Merged
jhoffner merged 5 commits into
mainfrom
spec/FIX-2161
Oct 23, 2026
Merged

jhoffner merged 5 commits into
mainfrom
spec/FIX-2161

Conversation

@jhoffner

@jhoffner jhoffner commented Oct 23, 2026 •

Copy link
Copy Markdown
Collaborator

Requested by Jake · project thread

Someone who… Today After
opens a new session in the Claude Code-style lab and picks a project Cannot. Only the project coordinator's session can have a project The screen creates the session and sets its project with one client call. Its coding tasks run in the checkout of that project
talks to a Grok Bot-style worker and starts the first job that needs files The one conversation of the worker can never have a project. It exists before the person picks one, and a session's project is fixed at create Picks a project on the screen. The same call stores it on that conversation, and the job runs there when it is filed again
asks either one for a code change n/a The board stamps the conversation's project on the task when it is filed, and the coding worker runs in that project through projectWorkspace(), in a task session or in a delegate's ongoing session
picks a project they cannot work in n/a Gets a refusal, and nothing is stored. A shared project where they are not a member gets not-a-member
moves a long conversation to a different repo n/a Sets a different project. New tasks run there. Tasks already filed keep their project, even one still waiting for a delegate

Goal: a person sets the project of any of their conversations with a worker (a new session, or the one default conversation of the worker, at any time). The screen sets it, the server stores it, and the server checks that the person is a member. The runs and tasks of that conversation then work in that project. Nothing else changes for the conversation or for the project coordinator.

flowchart LR
  A["Alice · lead's default conversation and a new session of main · real engine and HTTP router"] --> S["setWorkProject · shared apollo"]
  S --> F["each files a task to its coding delegate"]
  F --> R["the task session's run asks runProjectOf"]
  R -->|"apollo · owner Alice"| P["PASS"]
  A --> X["refusals · Carol not a member · Bob's private project · seeded at create · the coordinator"]
  X -->|"each refused, nothing stored"| P
  C["control · the field stored but not read"] -.-> R
  R -.->|"under the control"| N["must FAIL · no-project"]
Loading

The check reads the answer of the call and the project answer of the run. Check: a packages/workforce test on the real engine and HTTP router, with no mocks. It also covers a task that waits on the board past a change (waiting) and one routed to an ongoing delegate session (ongoing). Controls: store the field but do not read it in filingProjectOf (must FAIL default), let the hand-over read the live project instead of the row's stamp (must FAIL waiting), and remove the membership check (must FAIL not-a-member).

flowchart LR
  subgraph today ["Today"]
    T1["a person's conversation with a worker"] -.->|"no project · ever"| T2["its runs: no-project"]
    T3["the project coordinator"] -->|"projectId at create"| T4["its project"]
  end
  subgraph after ["After"]
    A1["a person's conversation with a worker"] -->|"setWorkProject · member check"| A2["workProjectId · server-written"]
    A2 --> A3["its runs and tasks: that project"]
    A4["the project coordinator"] -->|"projectId at create · unchanged"| A5["its project"]
  end
Loading

One new session field. Only one workforce action writes it, and the code that already finds a session's project reads it.

How: a new serverOwned field, workProjectId. A workforce action that every worker flow declares writes it, after it checks membership. The client calls the action with setWorkProject, in the same way as standingRules. filingProjectOf reads the field after projectId and before filingProjectId. The board stamps that project on each task row when it is filed; the hand-over copies filingProjectId from the stamp, and runProjectOf's held-row step reads it, so a task keeps the project it was filed in and an ongoing delegate gets one. projectId stays the link of the project coordinator only.

Sign off

The goal, at that size: any conversation of a person with a worker, the default conversation also, set from the screen and checked, and its tasks run there. If wrong: FIX-2153, FIX-2157 and step 5 of FIX-2154 cannot pick a directory.

The debt: up, by one field, one action, one client call and one row stamp. It removes nothing. If wrong: a fourth project field that a later reader must learn.

A conversation gets its project from one field that the server writes, set by a client call · D1

D1: one server-written field set by a client call, chosen, beside naming projectId at create; decided by the default conversation, which exists before any pick

It comes down to the default conversation: it exists before the person picks, and projectId is readonly, so it cannot be added later. If wrong: two ways for a session to get a project, or a default conversation that never gets one. This is the one to weigh.

The project can change later; tasks already filed keep theirs · D2

D2: the project can change and filed tasks keep theirs, chosen, beside fixed once set; decided by a weeks-long conversation with no new session

It comes down to the one long conversation: if the project is fixed, the conversation stays on one repo always. If wrong: the directory of a Claude Code-style session can move. That app never does this, and the lab does not offer it.

Open: none. Reasons and the options that lost: DECISIONS.md.

Reviewers · look here

  • Decisions → D1. Is a new field correct, or is there a way to put projectId on a default conversation after it is created without a change to the engine?
  • Decisions → decided, not asked. The action admits only the person's own conversations (not task, delegate, workstream-lead or coordinator sessions). Is a second source of a project possible on those sessions?
  • Spec → the goal check. Do change and waiting prove that a task already filed keeps its project, including one handed over after the change?

Not here: a raw folder outside a project, a run that already started, messages to a session that is not the default (FIX-2160).

SPEC.md · DECISIONS.md · FIX-2161 · epic FIX-2152 (#3783, ER-8 in #3803) · unblocks FIX-2153 (#3788), FIX-2157 (#3792), FIX-2154 step 5 (#3804) · merges after human approval and required checks

How to review this — altitude, what's in scope, what's deliberately unsettled

This is a direction set, not an implementation and not a build plan. Reviewing it well means
answering one question: is this the right approach?

In scope to challenge:

  • The goal and the problem framing in SPEC.md — is the goal the real need at full size,
    for the people named, or a smaller goal that would let us call this done early? Would the
    named check fail if the goal were not met?
  • The approach — will it work, does it fit the architecture and docs/philosophy.md?
  • Any numbered decision in DECISIONS.md — that's the sign-off surface.
  • The debt in SPEC.md → What's already here, and the debt — an existing primitive,
    method or prior design the change overlaps and doesn't name; something it adds that is debt
    and isn't listed; a net verdict the tables don't support.
  • A case a person would hit that the people table misses, when it would invalidate the
    design.
  • Scope — a deliverable that shouldn't ship, or one that's missing.

Out of scope — deliberately unsettled here, and owned by the implementing agent:

  • The build plan. Order, file-level changes, the test list, the PR split. The set has no
    plan on purpose: the implementer works it out against the real code.
  • Names, signatures, file paths, and module layout, beyond the few a decision locks.
  • Local structure: which helper, how a function is decomposed, error-message wording.
  • Edge cases that don't change the approach. The implementer's tests own them.
  • Documentation wording. It is written at implementation, against what shipped.
  • Micro-optimizations and style preferences.
  • The figures, at the pixel level. A figure is right when it reads right. A misplaced label
    or a colour you'd have chosen differently is not a finding; a figure that shows a shape the
    decisions don't say is.
  • POC implementation polish. Experiments under the owning spec's poc/ are retained,
    not production code. Read them for directional evidence, not production completeness.
    Their isolation from production/default discovery and absence of secrets or generated
    dependencies are in scope; retention is not permission to weaken repository checks.

One request, if you are an automated reviewer: the two lists above are the whole difference
between a useful review of this document and a long one. Volume is not signal here — a single
finding above the line is worth more than twenty below it.

Feedback in the second list is welcome and gets recorded verbatim in
DECISIONS.md → Notes from review
for the implementer to weigh against real code. It will not
be argued with, and it will not be folded into the design prose. Please don't re-raise it: one
mention is enough.

The one exception is the POC. Line-level feedback on it is dropped, not recorded — there
is nothing for an implementer to weigh about code that isn't shipping. Feedback about its
direction is not line-level and is treated like any other above-the-bar finding.

Direction approval does not waive merge-time required checks, approvals or thread policy.
Optional comments do not require another design round merely to reach zero comments.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Gnq9fyJmGrdB2K8u5kf2B5

Open the create check's project link to any worker at a random id, keep the
project coordinator's derived-id rule, gate the coordinator flow's workstream
seed on the project coordinator, and keep FIX-2158's list showing ordinary
project sessions. Workstreams checked and not reused.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Gnq9fyJmGrdB2K8u5kf2B5
The create check for an ordinary project session asks the run's membership
question, so a session can't open where projectWorkspace() refuses its runs.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Gnq9fyJmGrdB2K8u5kf2B5
@vercel

vercel Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments
Project Deployment Actions Updated
flow-state-dev-docs Ignored Ignored Oct 23, 2026 11:00pm UTC
flow-state-dev-kitchen-sink Ignored Ignored Oct 23, 2026 11:00pm UTC
flow-state-dev-ui Ignored Ignored Preview Oct 23, 2026 11:00pm UTC

Request Review

@linear-code

linear-code Bot commented Oct 23, 2026

Copy link
Copy Markdown

FIX-2161

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-23T23:02:03.603413Z 40c8c6a New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@jhoffner

Copy link
Copy Markdown
Collaborator Author

Coherence check (FSD Architect): the direction is coherent with epic FIX-2152 D3 (an ordinary session of one worker, no workstream per session, no new criteria key), and it adds no new mechanism: it reuses runProjectOf's membership test and narrows the one seed read. D1 and D2 look right to me. One fork needs closing before merge.

This spec and #3796 (FIX-2158) say opposite things about the same list. #3796 is approved and close to merging. Its D1 keeps only sessions whose criteria keys are a subset of {workerId}, so it drops every top-level session that carries projectId. This spec makes exactly those sessions the lab's normal case and lists "the lab's session list drops the session" as a not-done condition. Deferring that to "amended at implementation" leaves two merged specs that disagree, and whoever builds FIX-2158 first will build the version this spec rules out.

Please close it in the spec text, not at implementation. Pick one:

  1. If spec(FIX-2158): the workforce client lists a person's sessions of one worker #3796 merges first (likely), add an amendment to specs/issues/FIX-2158/ in this PR: the list excludes the project coordinator's per-project sessions (known by its worker, per your D2), not every session with projectId. Its no-other-kinds signal already uses the project coordinator, so it can stay. Its "remove the criteria-key filter" control needs restating against the coordinator rule.
  2. If this merges first, ask spec(FIX-2158): the workforce client lists a person's sessions of one worker #3796 to narrow D1 to the same rule before it merges.

Also, the body says "the epic thread has the conflict", but I don't see it on #3783. Please post it there or drop that line.

Not approving the direction yet, only for this one point. Everything else is fine from a coherence view.

— FSD Architect

Copy link
Copy Markdown
Collaborator Author

Second look + architecture pass (spec PR, checked against main)

Verdict: the direction holds. I found no leaner shape. Opening one branch of projectLinkCheck is the smallest change that does the job. The D1 claims check out: MAX_DELEGATES = 25 and the open-workstream refusal are real (workstream-writes.ts:447). D2 already has precedent: send-message.ts:135 tells the coordinator apart by worker (installation.projectCoordinator()?.worker === worker) and reads the project through filingProjectAddressOf, which takes the session's own projectId first. runProjectOf re-checks membership on every run (run-project.ts:171), so the create check is not the only fence. That is good defense in depth for BP-031.

Nothing below blocks direction. Both items are cheap while the code is already open, so they are worth naming for the implementer.

1. Make the "same membership test" one function (not two copies)

The spec says create asks "the same question the gate asks". Today that question is not a function:

  • isMember (membership-gate.ts:24) covers only shared projects.
  • The private-project branch (project.ownerUserId === owner) is written inline in fromProject (run-project.ts:171).
  • The create check reads raw rows (Record<string, unknown>), not a parsed ProjectRow, so it would need its own copy of both branches.

The membership-gate.ts header calls that module "the one place the answer is given and the one thing a test swaps". Copying the private/shared split into installation.ts breaks that. It also makes the control "readability check used for ordinary sessions must FAIL not-a-member" test a different predicate than the one runs use.

Suggest: extract one mayWorkIn(row, visibility, userId) into membership-gate.ts. Have fromProject and the create check both call it, parsing the row with projectRowSchema in the create check as fromProject does. This is refactor-while-there, because this PR is the first time a second caller needs the predicate. Without it the two checks can drift.

2. Gate the seed in one place, not at each call site

workstreamDelegateSeed(ctx) has three call sites: coordinator-flow.ts:422, coordinator-flow.ts:448, and changeWorkstreamRecordHere (project-coordinator.ts:249). The spec says "workstreamDelegateSeed seeds only a session of the installation's project coordinator", but the no-seed signal goes through a coordinator-flow session. A gate added at the flow call sites would pass the signal and leave changeWorkstreamRecordHere ungated. In practice that path only fires on the derived session, so it is probably harmless, but nothing enforces it.

Related: "is this session the project coordinator" would now be spelled three ways: the closure variable in installation.ts:677, the accessor in send-message.ts:135, and the new seed gate. Suggest: one helper on the installation (for example isProjectCoordinatorSession(state)). The create check, the message route and the seed all use it, and the gate sits inside the seed function, so no call site can skip it. This takes installation as a parameter, which two of the three call sites already hold.

Small notes (for DECISIONS → Notes from review)

  • D2 reviewer question, answered. I found no other reader that needs projectId to mean "I am a project coordinator". workstreamOf (project-coordinator.ts:138, used by the delegate check), readLinkedProject and projectOfWrite all treat it as "the session's project", which is correct for ordinary sessions. One side effect: a non-coordinator coordinator-flow session on a project starts with no workstream delegates, but the model can still add one by hand, because workstreamOf accepts the user's own open workstreams for any session with projectId. That is harmless and arguably right, but "lists only its file's delegates" in the people table is true only at birth. Worth one line so the no-seed check doesn't get read as a stronger guarantee.
  • Error reporter. reporter.ts:414 reads the failing session's projectId to pick the tracker. Ordinary project sessions will now route their errors to the project's tracker. That seems intended, but it is a behavior change outside the "runs and tasks" story. A line in the spec or the docs would cover it.
  • FIX-2158 ordering. The spec's plan (land the list-rule change in whichever PR merges second) is workable. Doing it by worker, not by criteria key, is the right call. It also removes the need to teach the list about projectId at all.

No changes requested to D1 or D2.


Generated by Claude Code

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9d8d9a5af2

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread specs/issues/FIX-2161/SPEC.md Resolved

@cursor cursor Bot 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.

Simplify review (spec FIX-2161)

Verdict: The implementation shape in this spec is about as small as it gets for the epic constraint (ordinary session of one worker, no workstream-per-session, no new criteria key). Re-reading installation.ts projectLinkCheck, filingProjectOf, and workstreamDelegateSeed on main supports the core claim: downstream readers already treat projectId as “where this session works”; the coordinator-only create refusal and the ungated delegate seed are the real blockers—not missing plumbing for filingProjectId or workstreams.

Alternatives considered (did the approach go too far?):

Path Simpler? Why I’d still stick with this spec
Workstream per lab session No Epic D3 + 25-delegate cap + “project work” semantics
New field (workProjectId) No Fourth carrier; every reader doubles
Lab passes input.project per task No ER-4 glue; session’s own run has no project
Worker allow-list No Same check for every worker; doesn’t scale to next app
Keep docs saying projectId = coordinator; only gate seed Partially Same code as D2, but filing-session.ts and hand-over paths already document “works in”; keys.ts / projectLinkCheck comments are the outliers
Reuse filingProjectId on create No Pinned hand-over-only on main; would be a new writer, not reuse

What is heavier than the code: retained prose (multiple mermaids + diff + figures + sign-off restating D1/D2 + “Decided, not asked” overlapping “What stays”). That’s editorial debt, not a wrong direction.

Product trade worth keeping visible: D1 trades the workstream path’s 25-session cap for unbounded ordinary sessions per project. That’s correct for “many chats,” but it moves scaling pressure to session store size and FIX-2158-style list scans (no default server limit). Fine for v1; I wouldn’t bury it entirely.

Dependency: List-rule amendment is FIX-2158-shaped; the spec’s merge-order sentence is process, not design—implementation should still prove one integration test so project sessions aren’t created and then filtered out.

Approving direction and gates; inline nits are spec-tightening only.

Open in Web View Automation 

Sent by Cursor Automation: Review For Best Approach

Comment thread specs/issues/FIX-2161/DECISIONS.md Resolved
Comment thread specs/issues/FIX-2161/DECISIONS.md Resolved
Comment thread specs/issues/FIX-2161/DECISIONS.md Resolved
Comment thread specs/issues/FIX-2161/DECISIONS.md Resolved
Comment thread specs/issues/FIX-2161/SPEC.md Resolved
Comment thread specs/issues/FIX-2161/SPEC.md Resolved
Comment thread specs/issues/FIX-2161/SPEC.md Resolved
Comment thread specs/issues/FIX-2161/SPEC.md Resolved
@jhoffner

Copy link
Copy Markdown
Collaborator Author

Coherence pass against main e5a2786, #3803 at 6e24b56, #3804 at 170a006, #3788 and #3792.

D1 and D2 hold. Main already reads projectId as where a session works (filingProjectOf, filing-session.ts:38; the hand-over, board.ts:399; runProjectOf, run-project.ts:60-79). It already identifies the coordinator by its worker (send-message.ts:135). The only reader that treats the field as "I am a coordinator" is the seed you narrow (project-coordinator.ts:127). Admitting members rather than readers matches #3788 D3. No new mechanism. Good.

One gap to close before merge: the default conversation. 6e24b56 on #3803 widened FIX-2161: "a worker's default conversation can carry a project, a server-written field the screen sets through a client call". #3804 (FIX-2154 step 5, setDirectory) depends on it. This spec puts that out of scope ("a per-project default conversation for every worker"), and no-derived and stays rule it out. In talk-first mode the default conversation exists before the pick, so a pick would be a later write of a read-only field, or the new field D1 rejects. Please add a D3 that says where the default conversation's project lives, and keep it composed:

  • Prefer an existing path, e.g. the re-filed task naming input.project, which runProjectOf already reads from the task row the gate checked and checks for membership (run-project.ts:72).
  • Only if that can't make the pick stick to the worker, name the smallest stored piece and why.

If you'd rather not take it here, say so in the epic thread so #3803 and #3804 re-home it. Either way, the three specs have to agree.

Minor: #3803's FIX-2161 row should match your membership rule (member of a shared project, or owner of a private one), not "a project the person can read".

#3796: agree with your reading. Its "no criteria key but workerId" rule would hide every lab session, since ER-8 gives each one a project. I've asked #3796 to change the rule there.

— FSD Architect

…call

The epic's ER-8 (#3803) widened the issue to a worker's default conversation,
set from the screen. projectId is readonly, so a default conversation could
never get one. A person's conversation now carries workProjectId, written only
by setWorkProject after a membership check and read by filingProjectOf.
projectId, the coordinator seed and FIX-2158's list are left untouched.

Re-draft: baseline SPEC.md 1421 words, DECISIONS.md 1143 words.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Gnq9fyJmGrdB2K8u5kf2B5

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 30b2003d13

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread specs/issues/FIX-2161/SPEC.md Resolved
The board stamps the filer's project on the row at filing; the hand-over
and runProjectOf's held-row step read it, so a task waiting past a change
keeps its project and a task routed to an ongoing delegate session has one.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Gnq9fyJmGrdB2K8u5kf2B5

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a6acb87ac4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread specs/issues/FIX-2161/SPEC.md Resolved

Copy link
Copy Markdown
Collaborator Author

@codex review

a6acb87 adds one server-written stamp on each task row at filing. The hand-over copies filingProjectId from it, and runProjectOf's held-row step reads it before input.project. Please look hardest at two things: whether any filing path skips the stamp (fileReserved, fileRouted, split pieces, retries), and whether a caller can forge the stamp through row metadata (callerMetadata must strip it).

On the Architect's note about carrying the default conversation's project through a re-filed task's input.project: that path doesn't keep the pick on the server, so the next task or the conversation's own run forgets it. That is the miss FIX-2154's pick-not-kept control is built to catch. It is now under DECISIONS.md → Considered and dropped. The #3803 row wording is with the epic thread.


Generated by Claude Code

…sk's project

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Gnq9fyJmGrdB2K8u5kf2B5
jhoffner pushed a commit that referenced this pull request Oct 23, 2026
…name gate

Round 1 of spec review on #3810:
- createInProcessFetch is node's dispatch moved to the engine; node delegates
  and stops deriving router paths (Decided, not asked; debt table).
- httpActions and 24 other hand-built router helpers are replaced; the census
  flags them, path derivation outside the engine, and the removed methods
  (stream twins, state.getSnapshot, bearerFetcher). Hosts and router unit tests
  excluded by name with reasons.
- The census is a name/prop gate; the single-file fetcher rule is gone. One
  transport per client is proved by a structural unit test in the goal; the
  control plants an internal facade the census must pass.
- Open PRs: FIX-2161 (#3805) added; FIX-2158 order and listWorkerSessions named.
- Docs line trimmed to the rewritten pages, with --after as the checklist;
  namespaces stated as an invariant with one example; review notes recorded.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PQR4aH3gxXUWdqTMpT1EH3
@jhoffner
jhoffner merged commit 8f0ce9d into main Oct 23, 2026
18 checks passed
@jhoffner
jhoffner deleted the spec/FIX-2161 branch October 23, 2026 23:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants