Skip to content

POC: inline the coordinator read's yours schema - #3453

Closed
cursor[bot] wants to merge 2 commits into
mainfrom
poc/shorter-read-yours
Closed

cursor[bot] wants to merge 2 commits into
mainfrom
poc/shorter-read-yours

Conversation

@cursor

@cursor cursor Bot commented Oct 15, 2026

Copy link
Copy Markdown
Contributor

This PR does not merge. It is a smaller cut of #3450 (49c66ba47). Fold 29c892ebe onto that branch and close this unmerged after 3450 lands. Do not reset 3450 onto this branch.

Subtracted. readLinkedProjectOutputSchema had one caller, and its comment repeated the handler. The same extend now sits on the handler's outputSchema. The handler comment names the mark once. The test comment that retold the incident is gone; the test title already says the model sees owners as user ids. The docs sentence no longer says readProject returns what readProject returns.

Still passes. packages/workforce/test/project-coordinator.test.ts: 30 passed. The mark is still workstream.owner === user, and the expect is still { checkout: true, billing: false }. Inverting the comparison failed: expected that object, received { checkout: false, billing: true }.

Net −9 against 49c66ba47 (6 insertions, 15 deletions).

Left on 3450: WORKER.md, the README section sentence and the catalog row, the changeset, and the harness test's expect.

Open in Web View Automation 

claude and others added 2 commits October 15, 2026 00:00
…on (FIX-2005)

A user's hand-off to their own workstream sometimes never reached it: the
project coordinator's turn made no dispatch. It read the project first,
couldn't tell its user's workstream from another member's (owners are bare
user ids), and then said it was someone else's, said "routed" without
routing, folded the ask into objectives, or asked what it meant.

- readProject, the project coordinator's tool, marks each workstream
  `yours` when the session's user owns it.
- The DevTeam project coordinator's file puts the hand-off rule first: a
  named workstream's ask goes on with dispatchTask in this turn, however
  short, with no project read before it; a hand-off is only a dispatch that
  answered ok; the readProject rule is for questions.

The closure goal's b3 failed 7 of 20 runs on main and 0 of 19 with this.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WGrSpvKPW4xoKddwpB3doh
The one-use schema and the notes that repeated the mark are gone. The docs sentence no longer says the tool returns itself.

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

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

Request Review

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