Repository navigation
Expose task reporting defaults and advisory override warnings - #750
Merged
Merged
Conversation
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.
Merge decision: ready — task creation and retries expose the represented reporting default and explain deliberate overrides without changing reporting authority.
User outcome
Task creators can see both the effective reporting target and the actor-visible immediate supervisor default. An explicit target that differs from an accessible, unambiguous default returns an advisory warning with both targets and their provenance; the explicit choice is preserved.
Material changes
Evidence
115 targeted tests passed across reporting diagnostics, canonical task management, MCP direct-message/task tools, task continuation and controller supervision. The new tests exercise the actual MCP create handler and canonical services against an isolated mock database, including retries, private-default visibility and scope denial. Ruff on the reporting service/new tests and git diff --check passed.
Ship boundary
Minimum criteria: matching, differing, omitted and unavailable defaults behave consistently on create/read/retry; overrides remain intact. Incorrect warnings, disclosure of private default identities or changed reporting authority would block delivery.
Live ontology configuration and public runtime behaviour were not validated. Deployment and changing worker message routing are outside this assignment; no deployment is requested.