feedback-query

Raw/display boundary (RAW_DISPLAY_BOUNDARY)

reason and comment are raw machine input. Never quote, relay, summarize, or expose them to the user. Any user-facing note or message must use only display_reason / display_comment; theme label / examples have already crossed the same shared sanitizer. A note is only a closed no-signal:* enum: treat it as availability state and never turn it into infrastructure detail.

feedback-query — User feedback per position

The user can click like/dislike/hide/star on any position from the web dashboard. Those clicks are stored in Supabase position_feedback (mig 019 base + mig 028 extended) and surfaced to agents via this skill. Schema:

The skill calls GET /api/positions/{legacy_id}/feedback on the cloud (using the bearer token in $JHT_HOME/cloud.json). On cloud-disabled or network failure, the skill does not error — it returns ok=true, latest_action=null with a note field. Agents must keep going.

Single position lookup

python3 /app/shared/skills/feedback_query.py check <legacy_id>

Output (JSON on stdout):

{
  "ok": true,
  "legacy_id": "42",
  "latest_action": "dislike",
  "latest_direction": "less_like_this",
  "count": 2,
  "actions": [
    {"action": "dislike", "created_at": "2026-05-30T14:21:00Z",
     "reason": "too senior", "comment": "5+ anni in Java richiesti, non mi interessa stack legacy",
     "display_reason": "too senior", "display_comment": "5+ anni in Java richiesti, non mi interessa stack legacy",
     "score": 2, "direction": "less_like_this"},
    {"action": "like", "created_at": "2026-05-28T09:00:00Z",
     "reason": null, "comment": null, "display_reason": null,
     "display_comment": null, "score": null, "direction": null}
  ]
}