Skip to content

fix(project): require owner request for Worker reports - #64

Merged
mingtaojin merged 2 commits into
mainfrom
fix/explicit-worker-coordinator-report
Nov 20, 2026
Merged

mingtaojin merged 2 commits into
mainfrom
fix/explicit-worker-coordinator-report

Conversation

@mingtaojin

Copy link
Copy Markdown
Owner

Why

Worker discussions can still be open when the agent sends a final report to the coordinator. This change requires the project owner to request that report in the current Worker group.

What changed

  • Bind final and escalation reports to the exact owner message ID used as requestId.
  • Validate the owner, current Worker group, and explicit report wording before writing coordinator input.
  • Keep intermediate reports and ordinary replies local, and update prompts, docs, tests, and the live probe.

Scope

  • Covers Worker-initiated final and escalation reports.
  • Runtime-generated native questions, approvals, execution failures, and interruptions keep their existing coordinator path.
  • Ambiguous owner wording requires a clearer request in the Worker group.

Blast Radius

Worker reports that do not have a current explicit owner request now fail before coordinator delivery. Existing local discussion and native event handling remain covered by the project runtime tests.

Verification

  • npm test passed with 719 tests.
  • npm run check, npm run build, and git diff --check passed.
  • Independent verifier passed the focused report and native-event checks, 87 project-runtime tests, and the parent regression. The real Codex probe was blocked by the local daemon/model timing limit.

@mingtaojin
mingtaojin merged commit ac01238 into main Nov 20, 2026
@mingtaojin
mingtaojin deleted the fix/explicit-worker-coordinator-report branch November 20, 2026 07:41
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.

1 participant