Skip to content

conformance: map signal step to public TrackSignal API (DEV-1201) - #8

Merged
pavel-y-ivanov merged 1 commit into
mainfrom
feat/dev-1201-signal-driver
Jul 14, 2026
Merged

conformance: map signal step to public TrackSignal API (DEV-1201)#8
pavel-y-ivanov merged 1 commit into
mainfrom
feat/dev-1201-signal-driver

Conversation

@pavel-y-ivanov

@pavel-y-ivanov pavel-y-ivanov commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Completes DEV-1201 part 3 for go (last core SDK): the conformance driver maps the harness signal step onto the public Client.TrackSignal surface — event_id/name required, signal_type/sentiment/timestamp(RFC3339)/properties/attachment_id optional, comment/after refused loudly (no public field, fleet no-silent-drops rule). signal added to advertised capabilities; unsupportedSteps now empty. HARNESS_REF bumped to cf744e9 (signal scenarios pin, matching js/python/java/rust). Signal scenarios are experimental (report-only) so no ratchet changes.

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>
@pavel-y-ivanov
pavel-y-ivanov merged commit 09a58f4 into main Jul 14, 2026
5 checks passed
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.

2 participants