Skip to content

POC: drop the extra lead flow from the work-project test - #3824

Closed
cursor[bot] wants to merge 2 commits into
mainfrom
poc/shorter-work-project-lead
Closed

cursor[bot] wants to merge 2 commits into
mainfrom
poc/shorter-work-project-lead

Conversation

@cursor

@cursor cursor Bot commented Oct 24, 2026

Copy link
Copy Markdown
Contributor

This PR does not merge.

Subtracted from #3821 (60bf7a086):

  • The goal test's own lead flow (filerFlow). The projects host already has a lead flow. The workstream-lead refusal only needs that flow to declare setWorkProject and the opened entry. Same nine cases.
  • setWorkProjectBlock from the package barrel. The action stays. The standing-rules block is not a package export either.
  • Two comments in board.ts that restated the filedInProject write.

Still passes: packages/workforce/test/work-project.test.ts, 9/9. ESLint is clean on the three files.

Fold fd6966bc7 onto the original and close this PR unmerged after that lands.

Open in Web View Automation 

claude and others added 2 commits October 24, 2026 00:09
…oject

Adds the server-owned session field workProjectId, written only by the
setWorkProject action every worker flow declares (agent, coordinator,
Error Reporter), and the client's setWorkProject(worker, project,
{ sessionId? }). The action admits the session's own user, on a project
they are a member of (or own, if private), and refuses the project
coordinator's, task, delegate and workstream-lead sessions.

filingProjectOf reads workProjectId between projectId and filingProjectId.
The board stamps the filer's project on each task row at filing
(filedInProject; in a delegate's ongoing session, the held row's stamp);
the hand-over copies filingProjectId from that stamp, and runProjectOf's
held-row step reads it, so a filed task keeps its project after a change.
Rows filed before the stamp existed fall back to the conversation's
project (BP-030).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Qsh48df8qzrorsfaCXn1X7
The projects host already has a lead flow. The workstream-lead refusal
only needs that flow to declare setWorkProject. Also drop the unused
setWorkProjectBlock package export and two comments that restated the stamp.

Co-authored-by: Jake Hoffner <jhoffner@users.noreply.github.com>
@vercel

vercel Bot commented Oct 24, 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 24, 2026 12:18am UTC
flow-state-dev-kitchen-sink Ignored Ignored Oct 24, 2026 12:18am UTC
flow-state-dev-ui Ignored Ignored Oct 24, 2026 12:18am UTC

Request Review

jhoffner pushed a commit that referenced this pull request Oct 24, 2026
…stream lead

Drops the test's own 24-line lead flow for the projects harness's `lead`
fixture flow with the action declared on it, the unused
`setWorkProjectBlock` export, and two comments restating the stamp write.
From the restraint review's POC (#3824).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Qsh48df8qzrorsfaCXn1X7
@jhoffner jhoffner closed this Oct 24, 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.

3 participants