~bigbes/agents-dev · parade

main · last commit 13 days ago · 7g0stsfu

← Back to the parade

ah-ziq yonote: comments.resolve 400s — live API requires isResolved boolean in body Past Stand

status: closed P2 bug @Eugene Blikh
bd reopen ah-ziq
Created byEugene Blikh
Ownerbigbes@gmail.com
Created2026-07-19T18:11:32Z
Started2026-07-19T18:11:47Z
Updated2026-07-19T18:21:38Z
Closed2026-07-19T18:21:38Z
Description
Live re-smoke of the Q&A loop (ah-eje, task 5) proved comments.resolve is broken: the daemon's POST /api/comments.resolve got HTTP 400 invalid_type 'Invalid input: expected boolean, received undefined (isResolved)'. Yonote 1.47.1 requires an isResolved:true field in the resolve payload; our client sends only {id}. Deterministic — every resolve fails, answer delivery is unaffected (non-fatal WARN path worked as designed). Fix: add IsResolved to the resolve wire payload in internal/yonote/comments.go, adjust tests, re-verify live that a fresh qa question ends isResolved:true.

Depends on

No outgoing dependencies.

Depended on by

Nothing depends on this issue.

No comments.

Close reason

Fixed in 2720611: resolve payload now {id, isResolved:true}. Live-verified (task 6 / comment 732b89b2): resolve succeeded, no WARN, comment isResolved:true.
  • Eugene Blikh created the issue · 2026-07-19T21:11:32Z
  • Eugene Blikh claimed · 2026-07-19T21:11:47Z
  • Eugene Blikh closed the issue · 2026-07-19T21:21:37Z
    Fixed in 2720611: resolve payload now {id, isResolved:true}. Live-verified (task 6 / comment 732b89b2): resolve succeeded, no WARN, comment isResolved:true.
  • Eugene Blikh added label milestone:yonote · 2026-07-20T03:08:53Z
  • Eugene Blikh removed label milestone:yonote · 2026-07-20T03:10:31Z
Stored rows — what this pane was built from, as read
issues 1 row
id ah-ziq
content_hash f6ed15a8569893a586511b86daf9a0cfc59c0fd794875182892371c1c8323d80
title yonote: comments.resolve 400s — live API requires isResolved boolean in body
description Live re-smoke of the Q&A loop (ah-eje, task 5) proved comments.resolve is broken: the daemon's POST /api/comments.resolve got HTTP 400 invalid_type 'Invalid input: expected boolean, received undefined (isResolved)'. Yonote 1.47.1 requires an isResolved:true field in the resolve payload; our client sends only {id}. Deterministic — every resolve fails, answer delivery is unaffected (non-fatal WARN path worked as designed). Fix: add IsResolved to the resolve wire payload in internal/yonote/comments.go, adjust tests, re-verify live that a fresh qa question ends isResolved:true.
design
acceptance_criteria
notes
status closed
priority 2
issue_type bug
assignee Eugene Blikh
estimated_minutes NULL
created_at 2026-07-19T18:11:32Z
created_by Eugene Blikh
owner bigbes@gmail.com
updated_at 2026-07-19T18:21:38Z
closed_at 2026-07-19T18:21:38Z
closed_by_session
external_ref NULL
spec_id
compaction_level 0
compacted_at NULL
compacted_at_commit NULL
original_size NULL
sender
ephemeral 0
wisp_type
pinned 0
is_template 0
mol_type
work_type
source_system
metadata �{}
source_repo
close_reason Fixed in 2720611: resolve payload now {id, isResolved:true}. Live-verified (task 6 / comment 732b89b2): resolve succeeded, no WARN, comment isResolved:true.
event_kind
actor
target
payload
await_type
await_id
timeout_ns 0
waiters
hook_bead
role_bead
agent_state
last_activity NULL
role_type
rig
due_at NULL
defer_until NULL
no_history 0
started_at 2026-07-19T18:11:47Z
is_blocked 0
events 5 rows
id 019f7b93-813d-797d-863e-ed930143a6a8
issue_id ah-ziq
event_type created
actor Eugene Blikh
old_value
new_value
comment NULL
created_at 2026-07-19T21:11:32Z
id 019f7b93-bc19-7693-b893-6f5a94880cba
issue_id ah-ziq
event_type claimed
actor Eugene Blikh
old_value {"id":"ah-ziq","title":"yonote: comments.resolve 400s — live API requires isResolved boolean in body","description":"Live re-smoke of the Q\u0026A loop (ah-eje, task 5) proved comments.resolve is broken: the daemon's POST /api/comments.resolve got HTTP 400 invalid_type 'Invalid input: expected boolean, received undefined (isResolved)'. Yonote 1.47.1 requires an isResolved:true field in the resolve payload; our client sends only {id}. Deterministic — every resolve fails, answer delivery is unaffected (non-fatal WARN path worked as designed). Fix: add IsResolved to the resolve wire payload in internal/yonote/comments.go, adjust tests, re-verify live that a fresh qa question ends isResolved:true.","status":"open","priority":2,"issue_type":"bug","owner":"bigbes@gmail.com","created_at":"2026-07-19T18:11:32Z","created_by":"Eugene Blikh","updated_at":"2026-07-19T18:11:32Z"}
new_value {"assignee":"Eugene Blikh","status":"in_progress"}
comment NULL
created_at 2026-07-19T21:11:47Z
id 019f7b9c-bd80-789b-a127-b51b189577a8
issue_id ah-ziq
event_type closed
actor Eugene Blikh
old_value
new_value Fixed in 2720611: resolve payload now {id, isResolved:true}. Live-verified (task 6 / comment 732b89b2): resolve succeeded, no WARN, comment isResolved:true.
comment NULL
created_at 2026-07-19T21:21:37Z
id 019f7cda-aa8e-73dc-b464-e23396e778fc
issue_id ah-ziq
event_type label_added
actor Eugene Blikh
old_value NULL
new_value NULL
comment Added label: milestone:yonote
created_at 2026-07-20T03:08:53Z
id 019f7cdc-2ad0-767c-91ff-4506788b1824
issue_id ah-ziq
event_type label_removed
actor Eugene Blikh
old_value NULL
new_value NULL
comment Removed label: milestone:yonote
created_at 2026-07-20T03:10:31Z