Skip to content

feat(workforce): workers run only on registered worker flows (FIX-1789) - #2847

Merged
jhoffner merged 4 commits into
mainfrom
fix/FIX-1789
Oct 7, 2026
Merged

jhoffner merged 4 commits into
mainfrom
fix/FIX-1789

Conversation

@jhoffner

@jhoffner jhoffner commented Oct 7, 2026 •

Copy link
Copy Markdown
Collaborator

The problem

Today any flow passed to the hire can run any worker. A worker flow with no door can still be hired, but it can't take a message. A flow that refuses a hire's configuration fails only at the moment someone hires a worker onto it. The built-in agent keeps each worker's skills drawer at org scope, and nothing on a shared entry says who wrote it.

What this does

The app passes its worker flows to the hire as workerFlows. Before any worker is hired, each flow, the built-in agent included, is checked for three things:

  • it takes the configuration a hire supplies;
  • it has exactly one door;
  • any of its resources that declares writtenBy was built with sharedResource().

One error names every problem with every flow. A flow passed as { flow, standardOnly: true } refuses hired workers, which are runtime hires and reloaded roster rows. sharedResource and writeShared stamp the writer from the session. The agent drawer moves to user scope.

Today and after, in five cases: the doorless and wrong-typed flows are refused at boot by name, the agent's drawer is in its user's scope, a shared entry names the user and the worker, and a user's own worker on a kept flow is refused

What's asked of you

This implements the approved direction. One call is yours:

DevForce's EM now takes a person's line, and files the feature it names

  • The spec said to give the EM a real door. Its door reads <issue-slug>: <what> and files that feature; any other line files nothing, and the EM says so. Inbox's reply under the EM's ask is now on. FIX-1690 had it off.
  • If this is wrong: a person's reply can file a feature without the ask's Approve. The fallback is a door that only answers.

Parts worth reviewing closely

For the code reviewer:

  1. worker-flow-contract.ts checks the configuration by minting the flow with a full probe bag. It reads the structured issues that core now attaches to a config refusal (FlowConfigRefusalError), not the message text. An issue on the whole bag always refuses the flow, and so does any refusal it can't read.
  2. Check 3 judges a resource by where it came from: sharedResource() marks its output with a non-enumerable brand, bound to the schema it built. Spreading the resource or swapping its schema loses the brand.
  3. A hired worker is a record with an ownerPin (hire.ts). No new field was added.

Fixes FIX-1789 · spec specs/issues/FIX-1789/ on main (review #2811, amendments #2841, #2843) · epic FIX-1786 · goal goals/worker-contract/runs-workers-only-on-registered-flows PASS, three source-revert controls FAIL their leg only.

How to review this

How to review this. This implements an approved spec — the approach and the numbered
decisions in its DECISIONS.md are already signed off by a human, so please review the
code against that direction, not the direction itself. The canonical set is retained
at specs/issues/<ISSUE-ID>/ on main; Linear links to it and the original merged spec
PR, which keeps review history. Follow-up amendment PRs explain later direction changes.
Current architecture docs remain the authority for shipped behavior (BP-037).

Most valuable here: correctness on the second path (the legacy shape, the null
boundary, the concurrent case, the cancel path), anything deriving an auth or routing
decision from caller-controllable input, and a behaviour the tests assert around
rather than on.

Already settled upstream: the approach and every decision in the spec's DECISIONS.md
(human-approved — if one is wrong, say so as a spec finding and it gets folded back; don't
re-argue it inline), and the conventions in docs/contributing/best-practices.md.

Engineering calls
  • Attribution is judged by provenance, not by what the schema accepts. A resource that declares writtenBy must be built with sharedResource(), which owns the field. This narrows the spec's check 3 from "judged by what it accepts" to "built by the helper". Sampling values can't prove that an arbitrary Zod schema stores { userId, workerId? }: review found a union with an unsigned branch, a transform of the whole entry, a broader field and .or("system"), and all four passed the probes. The repo has no hand-rolled writtenBy resource except the goal's deliberately broken one. If wrong: a hand-rolled resource with a correct full shape is refused. Switch it to sharedResource.
  • core: config-refusal errors carry structured issues; additive. A mint's config refusal now throws FlowConfigRefusalError with issues: { path, code, message }[]. The message and the error's name are unchanged. unrecognized_keys gives one issue per key, at that key's own path. Two codes are the framework's own: no_config_schema, and block_contributes, where an empty path means the whole bag. The contract reads these instead of parsing text. As a result, a block that transforms the whole bag is refused, and a custom message containing ; stays one issue. If wrong: none on the message side; a caller that checks instanceof Error still matches. @flow-state-dev/core gets a patch changeset.
  • The configuration probe mints the flow. That way it also catches a block's flowConfigSchema.
  • admissionHint is removed. After registration it could never fire. If wrong: none.
  • Registration also refuses a flow passed under a key that is not its kind (BR-8). The refusal now names the flow, not a worker. A misnamed flow still has its other problems reported in the same run.
  • Results are cached per flow object and name (WeakMap). The check runs once per flow across hires, reloads and runtime hires.
  • writeShared creates or replaces the entry. The entry names whoever wrote last. FIX-1793 decides who may write.
  • The two-door warning on a runtime hire's result is gone. No hired flow can have two doors now.
  • The DevTeam host refuses a tree with no EM before the hire when an ask is requested. It names raiseAsk, as goal leg AR-6 expects.
  • The generated module's export stays kinds, and KindRefusedHireError keeps its name. Only the generated export's type is now HireOptions["workerFlows"]. Both renames are FIX-1796's. The refusal text now says "worker flows".
  • Docs were edited by hand, then put through a docs-editor pass. That pass's findings are folded in.
Everything else: verification, V0, files

Goal, as the spec drew it

flowchart LR
  I["fixture app · eight worker flows · two users of one org"] --> R["register and boot on the real path"]
  R --> A["leg a · three flows refused at boot by name · nothing hired"]
  R --> B["leg b · alice's agent worker keeps its own state off org scope · her shared note names her"]
  R --> C["leg c · bob's hired worker on a standard-only flow refused"]
  A --> P["PASS · the goal is met"]
  B --> P
  C --> P
  X["control · today's main"] -.-> A
  X -.-> B
  X -.-> C
  B -.->|"on main"| F["must FAIL · alice's drawer is in the org's cells"]
Loading

pnpm tsx goals/worker-contract/runs-workers-only-on-registered-flows/run.mts (model-free), on the current head:

  • PASS. One boot error named doorless, numbered and loose-attribution, and nothing was hired.
  • 5 workers booted on 5 flows.
  • Alice's 2 drawer writes landed in user scope, and bob's run touched neither.
  • The shared note named alice and support.scout.
  • Bob's hired worker on "coordinator" was refused at reload and left as stored, and support.coord ran on it.

The runner can't load on main, because workerFlows, sharedResource and writeShared don't exist there. So each leg's control reverts that leg's mechanism to main's behaviour, and each fails only its own leg:

  • registration check off → FAIL [a] … hired 5 worker(s).
  • scope: "user" off → FAIL [b] alice's drawer rows are in the org's cells and [b] bob's run touched alice's drawer.
  • standard-only off → FAIL [c] bob's own worker runs on the kept flow "coordinator".

Unit tests, red then green

  • worker-flow-contract.test.ts:
    • Each review repro was red on the head before its fix: the union with an unsigned branch, the whole-entry transform, the broader field, .or("system"), a schema swapped onto a spread or built resource, a block transforming the whole bag, a ; inside a custom message, a misnamed doorless flow, and the wrapped loose schemas.
    • The parser has its own tests over structured issues.
    • Green: 41.
  • flow-config.test.ts (core): 5 tests on structured issues. Each is a real mint refusal, with the message unchanged. Green: 46.
  • worker-flow-registration.test.ts (V2–V4, V7, runtime hire), shared-resource.test.ts (V5, real engine), agent-worker-own-state.test.ts (V6, real engine): red on main's behaviour, green now.

Suites (current head): workforce 90 files / 1415 tests · core 143 / 2302 · shift-manager 33 / 374 (1 skipped) · pnpm typecheck passes, boundary and control-shape guards included. The goals touched by the fixture-door refactor pass, apart from the two that fail the same way on main: a-mailbox-holds-the-work-a-seat-drains (V14) and manager-queue-lab/it-stands-the-team… (its diff gate depends on the branch).

V0: every worker-flow map in the repo went through registration, on the real hosts, test suites and model-free goals. Each flow that failed was fixed here. Flows with no door now use one shared door: goals/lib/worker-door.mts for goals and packages/shift-manager/test/fixtures/hearing-door.mts for the labs (folded in from #2849). Flows missing seatPackages: pentest probe and the workforce-seats control pairs. DevForce's EM got a real door (block 3).

What the spec missed (DOCS.md): moving the drawer made four doc claims false. They were fixed in built-in-worker.md (two sentences and the SVG), overview.md, the workforce README and docs/architecture/workforce-default-worker-kind.md.

Changesets: minor for @flow-state-dev/workforce (epic D9), patch for @flow-state-dev/core (structured config-refusal issues).

Files:

  • New: packages/workforce/src/{worker-flow-contract,shared-resource}.ts.
  • Changed in workforce: hire.ts, seat-hire-blocks.ts, roster/{check,reload}.ts, agent-worker-flow.ts, codegen/render.ts, loader/read-workforce-directory.ts, index.ts.
  • Changed in core: packages/core/src/helpers/flow-config.ts and flow/defineFlow.ts.
  • Callers renamed from kinds to workerFlows.
  • New goal: goals/worker-contract/runs-workers-only-on-registered-flows/.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XMg2dz8sMEdyzCQTRsaMTV


Note

High Risk
Changes the single admission gate for hiring, user-scoped agent skills (data isolation), and durable roster reload rules for standard-only flows—areas that affect multi-tenant behavior and boot-time failures.

Overview
FIX-1789 tightens workforce hiring: apps register worker flows via workerFlows (renamed from kinds), and hireWorkforce / reloadHiredSeats validate every registered flow—including built-in agent—before any seat is minted.

A flow must compose workerConfigSchema(), expose exactly one public “door” action (userMessage + { message }), and declare any resource with writtenBy only through sharedResource() / writeShared(). Failures aggregate in one boot error via workerFlowProblems. Entries can be { flow, standardOnly: true } so runtime hires and reloaded roster rows cannot run on flows reserved for WORKER.md workers.

@flow-state-dev/core now throws FlowConfigRefusalError with structured { path, code, message } issues when a config bag is refused, which the contract reads instead of parsing error text.

The built-in agent moves per-seat skills storage from org to user scope so two people do not share one worker’s drawer. Docs, kitchen-sink, and goal harnesses are updated (workerDoor helper, Shift Manager EM inbox behavior).

Reviewed by Cursor Bugbot for commit a657979. Configure here.

hireWorkforce takes the installation's worker flows as `workerFlows`
(renamed from `kinds`, with SeatHireCapabilityOptions and
reloadHiredSeats) and checks every one, the built-in `agent` included,
against the worker contract before any worker is hired: it takes the
configuration a real hire supplies, by key and by value; it has exactly
one door; and any `writtenBy` it declares is the shared-resource field.
One problem refuses the whole call, once per flow. The check is exported
as `workerFlowProblems` for a library's own tests.

An entry `{ flow, standardOnly: true }` keeps a flow for the workers the
installation's files define. A record carrying an owner pin (a runtime
hire, a stored roster row) is refused on it, after the `agent` default;
a stored row refused this way is reported and left as stored.

`sharedResource` declares an org-scoped collection whose entries carry a
required `writtenBy: { userId, workerId? }`, and `writeShared` stamps it
from the session, never from input.

The built-in agent keeps its skills drawer at user scope, off org scope.
The two-door warning is gone: none or two doors now refuse.

Every worker-flow map in the repo was run through the check (V0). Test
and goal fixtures without a door got one; DevForce's EM gets a real door
that files a feature from `<issue-slug>: <what>`. New goal:
goals/worker-contract/runs-workers-only-on-registered-flows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XMg2dz8sMEdyzCQTRsaMTV
@vercel

vercel Bot commented Oct 7, 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 7, 2026 4:20pm UTC
flow-state-dev-kitchen-sink Ignored Ignored Oct 7, 2026 4:20pm UTC
flow-state-dev-ui Ignored Ignored Preview Oct 7, 2026 4:20pm UTC

Request Review

@linear-code

linear-code Bot commented Oct 7, 2026

Copy link
Copy Markdown

FIX-1789

@cursor

cursor Bot commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: a948c856-ec33-4600-b502-1de5ce26b1b0)

@jhoffner
jhoffner marked this pull request as ready for review October 7, 2026 15:23
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 7, 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-07T16:12:39.271626Z 49d6397 Manual request
ℹ️ 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.

@cursor

cursor Bot commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: f58d5e06-9fca-4b43-af4b-65269f6dd8d4)

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

Problem

Workers could run on flows the installation never registered (or on the built-in agent when the app meant to reserve it for file-defined seats). FIX-1789 needs a single, loud gate before mint: only registered worker flows, plus standardOnly for user-owned workers.

Verdict

Approve. The split — resolveWorkerFlows + registration-time workerFlowProblems + sharedResource/writeShared — matches the locked contract (structural admission at hire, door via seatDoorOf, attribution on declared writtenBy). I don’t see a materially simpler design that still covers hand-built hireWorkforce({ workerFlows }) and library flows tested without codegen.

A wrapper-only path (defineWorkerFlow / Shape B) would shrink call sites but was correctly rejected: it wouldn’t catch flows registered as plain defineFlow results. Renaming kinds → workerFlows without the contract would be smaller diff but wouldn’t deliver the epic.

Where complexity crept in (non-blocking)

  1. Check 1 couples to error-string shape — configurationProblem mint-probes then contractKeysRefused parses describeFlowConfigIssues wording. If core rephrases or the throw isn’t a config refusal, you can get a silent pass on configuration. Higher-confidence simplification (when you’re willing to touch it): read the flow’s closed configSchema and safeParse(CONTRACT_PROBE_BAG) (or export/reuse describeFlowConfigIssues from core) instead of parsing messages; keep the mint probe only if block flowConfigSchema must be part of “hire bag admissible.”
  2. Doc drift — worker-flow-contract.ts says contractKeysRefused is what hire uses for mint refusals; hire.ts only does refuse(messageOf(error)). Either wire a shared reader for worker-facing mint errors (old admissionHint intent) or trim the comment.
  3. Duplicated attribution rules — WRITTEN_BY_ACCEPTS / WRITTEN_BY_REFUSES parallel writtenBySchema in shared-resource.ts. One helper next to writtenBySchema would keep check 3 and the helper in sync.
  4. Naming debt — public API is workerFlows, but user-visible strings still say “kind” (missingKindReason, KindRefusedHireError) and codegen still exports kinds. Fine for this PR; FIX-1796-style sweep would reduce cognitive load.
  5. POC mirror — specs/issues/FIX-1789/poc/.../contract.ts largely copies production; pointing the POC at @flow-state-dev/workforce exports would avoid two implementations (process hygiene, not runtime).

What’s working

  • CONTRACT_KEYS derived from workerConfigSchema().shape + probe-bag sync test.
  • WeakMap cache on flow identity — right tradeoff for reload.
  • standardOnly as a small WorkerFlowEntry shape.
  • Goal runs-workers-only-on-registered-flows exercises the real hire path.
  • Built-in skills scope: "user" aligns with the architecture doc.

Skipped (larger than this PR)

  • Reload doing N× hireWorkforce([one row]) — pre-existing; contract adds only once-per-flow cost.
  • Replacing the whole contract with a third-party package — nothing fits this FSD-specific door + hire-bag model.

No changeset concern from me; workforce surface change is appropriately covered.

Open in Web View Automation 

Sent by Cursor Automation: Review For Best Approach

Comment thread packages/workforce/src/hire.ts Resolved

@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: ae72c9d583

ℹ️ 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 packages/workforce/src/hire.ts Resolved
Comment thread packages/workforce/README.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.

Code Snob

The contract is the size it has to be (worker-flow-contract.ts, shared-resource.ts, the hire check). What can go is the door pasted into the fixtures.

Eighteen goal flows repeat the same message door that answers Heard: …, and the two shift-manager labs each carry a copy of hearing-door.mts. One helper covers the identical copies: #2849

That draft does not merge. Fold goals/lib/worker-door.mts and the single packages/shift-manager/test/fixtures/hearing-door.mts into this branch, then close the POC unmerged after this lands.

Left alone on purpose: the host door that returns {}, and the worker-contract goal's doors, whose replies name the flow. Also drop the sentence in worker-flow-contract.ts that says hire words mint refusals with contractKeysRefused. Hire no longer calls it.

View PR

Open in Web View Automation 

Sent by Cursor Automation: Code Snob

- Check 1 fails closed: a mint refusal in no shape the reader knows is a
  problem, not a pass. Parser tests cover each shape on their own.
- Check 3 finds writtenBy through refine, transform, pipe, intersection and
  union, and compares parsed output, so a field that drops workerId fails.
  The rule lives beside writtenBySchema (isSharedWrittenBy).
- workerFlowProblems reports a name mismatch along with every other problem.
- Refusals and the missing-WORKER.md diagnostic say worker flows and
  workerFlows; README signatures and the architecture quick reference
  updated (skills drawer at user scope).
- Docs: declared vs hired workers defined once; standardOnly behaviour on
  hire and reload stated; writtenBy guarantee stated plainly.
- Fixture doors: one goals/lib worker door and one shift-manager
  hearing-door, replacing the per-goal copies.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XMg2dz8sMEdyzCQTRsaMTV
@cursor

cursor Bot commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 9b2305dd-d836-417a-b821-cad8afd32f87)

jhoffner commented Oct 7, 2026

Copy link
Copy Markdown
Collaborator Author

@codex review

a5672b3 rewrites the attribution check (declaredWrittenByFields and isSharedWrittenBy in shared-resource.ts) and makes the configuration reader fail closed. Please look closely at both.


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: a5672b3195

ℹ️ 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".

…ues (FIX-1789)

- Check 3: a resource that declares writtenBy must be built by
  sharedResource(), which marks its output with a non-enumerable brand
  bound to the schema it built. A hand-rolled resource is refused even
  with the right shape; a spread or schema-swapped copy loses the brand.
  Value probing and output comparison are gone.
- Check 1: core's config refusals now throw FlowConfigRefusalError with
  structured issues ({ path, code, message }), message unchanged. The
  contract reads those, not the text: a whole-bag issue is always a
  problem, and a `; ` inside a custom message is one issue.
- core: config-refusal errors carry structured issues; additive. Patch
  changeset.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XMg2dz8sMEdyzCQTRsaMTV
@cursor

cursor Bot commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: af6f6ff1-81be-4eed-af97-fa9f11fb6adf)

jhoffner commented Oct 7, 2026

Copy link
Copy Markdown
Collaborator Author

@codex review

49d6397 replaces both checks at the root. Attribution is judged by which helper built the resource (sharedResource()'s brand in shared-resource.ts), not by inspecting the schema. The configuration check reads core's new structured FlowConfigRefusalError.issues (packages/core/src/helpers/flow-config.ts, defineFlow.ts) instead of message text. Please look closely at the core change and at whether any path still passes a flow it should refuse.


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: 49d6397c22

ℹ️ 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 on lines +174 to +175
const writtenBy: WrittenBy =
typeof seatId === "string" && seatId.length > 0 ? { userId, workerId: seatId } : { userId };

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Derive worker attribution from worker provenance

When an ordinary, non-worker flow has an unrelated nonempty configuration setting named seatId, this branch treats that key as proof that a worker is running and stamps the human write with a false workerId. Core does not reserve seatId, and SharedWriteContext accepts arbitrary flow configuration, so writeShared needs a workforce-specific provenance signal rather than the presence of this generic key.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Declined in this PR. You're right that seatId is not a reserved key in core. But FIX-1788's approved plan replaces this exact source with the server-only session link: "If its singleton cutover hasn't landed, the helper reads seatId, and FIX-1788 switches it". A different provenance signal added here would be code FIX-1788 then deletes. Today writeShared's documented use is in worker flows, where seatId is stamped by the hire. I'm leaving this thread unresolved so the owner can decide, since it's about whether attribution is correct.


Generated by Claude Code

…FIX-1789)

- Check 1 compares the probe mint's contract keys with the bag it was
  given; a transform over `seatId` (or any contract key) is a problem
  that quotes the key and both values.
- A block requirement hidden behind a flow's own required setting is
  left to the hire, which refuses with core's own error; a test pins it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XMg2dz8sMEdyzCQTRsaMTV
@cursor

cursor Bot commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 14f06044-96ed-475b-b0d0-be4ca181fd70)

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