* feat(mcp): make agent feedback a read loop, advertise the tool, and stop over-promising
gnubok_feedback had collected 40 reports since May with no read surface
(no page, digest, or script), while replying "We aggregate signal
weekly". Triaged in full on 2026-08-17 (16 fixed / 12 open / 8 gaps /
4 partial; P0/P1 fixes in #1644-#1649).
- New local loop skill /loop-feedback-triage: reads agent.feedback rows
past a sequence watermark (seeded at 213147), verifies each against
main, appends a dated digest to dev_docs/mcp_feedback_digest.md
(local-only, dev_docs is gitignored), opens small fix PRs through the
loop-verify gate. Never merges, never files issues. Closes the
feedback-digest backlog item blocked since 2026-07-09 on a channel
decision.
- The tool is now advertised in the server instructions block and as
feedback_channel in gnubok_get_agent_briefing (it was discoverable only
by scanning tools/list). Reply copy is honest about what happens.
- SIE duplicate-block errors name the blocking import id and point at
undo-then-retry (gnubok_undo_sie_import / Angra import): agents were
stuck behind a completed zero-entry import without knowing the way out.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* fix(mcp): trim feedback_channel schema description to stay under the tools/list size guard
The added briefing field crossed the 59.7K projected-token ceiling by 6
once #1411's tool landed on main. Trimmed the description prose rather
than bumping the ceiling, per the guard's own instruction.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---------
Co-authored-by: Jakob Wennberg <311770904+jakobwennberg-oss@users.noreply.github.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
