datatug / datatug-core / 38430769269

100%

push

github

fix(detective): preserve typed proposals and bind Case inputs (#363)

AI Check and Validator proposals were rejected because the recursive security-field filter treated the legitimate Validator.scope assertion field as authority. Accept that typed field while strict decoding rejects authority on the tool envelope and Draft, including unknown or duplicate fields inside range values.

Add shared BindCaseInputs and MatchCaseCohort contracts so local and hosted adapters bind declared Case inputs consistently, reject scalar and cohort replacement, and retain exact set/range semantics. Unrelated scalar Case context remains available without changing the Check schema.

Validation: every proposal kind exercised through Assistant.Run; row/set Validators and authority injection regressions; Case scalar/set/range conflict and malformed input tests; full Core tests at 100% statement coverage, vet, and compatible golangci-lint with zero findings. Independent review is bound to the final head before landing.

Source commits:

- 12ce8c7bf03c fix(detectiveai): accept typed Validator scope in proposals
- 926aabb79086 fix(detective): bind Case cohorts consistently and decode ranges strictly
- 248f185e6b14 fix(detective): detach accepted Case input values

Pull request: datatug/datatug-core#363
Review: /private/tmp/detective-root-01a1348b/core-scope-review-r3.md

58 of 0 new or added lines in 0 files covered. (NaN%)

14550 of 14550 relevant lines covered (100.0%)

1.0 hits per line