conformance: map signal step to public TrackSignal API (DEV-1201) - #8
Merged
Conversation
Mirrors the merged js/python/java/rust driver changes: signal capability advertised, step maps event_id/name/signal_type/sentiment/timestamp/ properties/attachment_id onto Client.TrackSignal; comment/after refused loudly (no public field). HARNESS_REF bumped to the signal-scenarios pin. Authored locally by the coordinator (Devin has no write access to this repo); implementation follows the DEV-1201 part-3 session's pattern. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
rsd-raindrop
approved these changes
Jul 14, 2026
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.
Completes DEV-1201 part 3 for go (last core SDK): the conformance driver maps the harness
signalstep onto the publicClient.TrackSignalsurface — event_id/name required, signal_type/sentiment/timestamp(RFC3339)/properties/attachment_id optional,comment/afterrefused loudly (no public field, fleet no-silent-drops rule).signaladded to advertised capabilities; unsupportedSteps now empty. HARNESS_REF bumped tocf744e9(signal scenarios pin, matching js/python/java/rust). Signal scenarios are experimental (report-only) so no ratchet changes.