Repository navigation
fix(hub): tell agents why the hub refused their request - #51
Merged
TheGreatAxios merged 1 commit intoNov 2, 2026
Merged
TheGreatAxios merged 1 commit into
TheGreatAxios merged 1 commit into
Conversation
TheGreatAxios
force-pushed
the
cl-11925-show-agents-why-the-hub-rejected-a-document-write
branch
2 times, most recently
from
November 1, 2026 21:26
26fd890 to
a78ac24
Compare
TheGreatAxios
marked this pull request as ready for review
November 1, 2026 23:23
|
Triage: Pass No changes needed from you. A maintainer will review this pull request. Triage will approve, request review. |
Refs CL-11925, CL-11927
TheGreatAxios
force-pushed
the
cl-11925-show-agents-why-the-hub-rejected-a-document-write
branch
from
November 2, 2026 00:42
a78ac24 to
f9abd5b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
ProjectErrorturns an arktype errors object into the{path, message}list, the only form the workflow HTTP layer passes on to an agent's tool result. Before this, reasons were.summarystrings, so a model saw only{"code":"invalid_artifact_write","status":400}and repeated the same call.issues: x.summarynow sendsissues: x, a one-word change at each site. Strings no longer typecheck asissues.issue.expectedis used for narrow/type rules,is not allowed herefor undeclared keys, andis not one of the allowed valuesfor unions whose description embeds the value.approaches: "goes on the approaches document; write this problem_brief without it".Folds in #52.
How it was verified
apps/hub/src/projects/errors.test.tsrunswrite_artifactthrough the workflow HTTP layer against the hub routes and checkstypeIssuesacross.narrow(), unions and undeclared keys with no submitted value in any message.bun run test, lint, format and typecheck pass.Refs CL-11925, CL-11927