mcp-data-platform-v1.84.0

The human feedback and review loop lands end to end: reviewers leave structured feedback on portal artifacts, agents resolve it by capturing knowledge, and the chain stays visible through validation and sign-off. This release also fixes two API-catalog panel issues and expands portal screenshot coverage.

Highlights

Feedback threads on portal artifacts (#604, #605, #606)

Reviewers can now leave structured feedback directly on a saved artifact and work it to resolution.

• Open a correction, question, or suggestion thread anchored to an artifact (or to a text quote within it), reply, and moderate it through an open/answered/resolved lifecycle. Each thread carries a typed timeline (comments, status changes, ratings, approvals), and the asset and collection list pages show per-object open-thread counts scoped to the viewer.
• A reviewer who arrives through a public share link is signed in and promoted to a durable viewer share, so they can participate without a separately granted account.

Resolve feedback into catalog knowledge (#609)

An agent can resolve a feedback thread by capturing the knowledge it represents, with no new MCP tools.

• capture_insight gains an optional thread_ids. Capturing an insight links the named threads to it, records the link on each thread's timeline, and resolves them. Linking is gated by the same owns-or-edit access check as the thread actions, so it is not a back door around access control; unauthorized or unmatched ids are reported back as unlinked.
• manage_artifact gains thread actions (list_threads, get_thread, reply_thread, resolve_thread, request_validation), scoped to artifacts the caller owns or can edit. The net MCP tool count is unchanged.
• The resolved chain from a thread to its insight to the applied changeset and target dataset is available at GET /api/v1/portal/threads/{id}/chain and rendered as a "Knowledge chain" panel on a resolved thread.

Validation, sign-off, and worklists (#610)

The feedback author confirms or disputes how their feedback was resolved, and worklists keep open items visible so nothing is dropped.

• The author marks a thread validated or disputed (with a reason) via manage_artifact action=respond_validation or POST /api/v1/portal/threads/{id}/validation. Disputing re-opens the thread, and a response is only accepted against an outstanding validation request.
• Worklists: GET /api/v1/portal/worklist/practitioner returns open, resolution-required threads across every artifact the caller owns or can edit, and GET /api/v1/portal/worklist/sme returns threads awaiting the caller's validation.
• Sign-off aggregation: GET /api/v1/portal/assets/{id}/signoff and .../collections/{id}/signoff return "signed off by N of M", where N is the distinct users who approved and M is the owner plus active share grantees.
• The portal adds a validate and dispute control, an inbox with practitioner and reviewer tabs, and a sign-off badge.

API catalog panel reliability (#607, #608)

• The API catalogs panel no longer crashes when a spec uses the embedded source kind (the platform's own self-connection seeds one). An unrecognized source kind now degrades to a plain badge, and embedded specs are read-only in the panel since they are re-seeded from their toolkit at startup. (#607)
• The spec re-embed and URL-refresh buttons now show in-flight state (per-spec disable, spinner, and an inline status banner) and debounce rapid clicks, so an operator no longer queues duplicate embedding jobs against the same spec. (#608)

Portal screenshot coverage (#599)

• Expanded automated portal screenshot coverage, including editor and drawer states, with light and dark theming fixes, for documentation and review.

Upgrade notes

• Three database migrations apply automatically on startup: 000064_portal_threads, 000065_portal_thread_events, and 000066_portal_shares_origin (the feedback thread substrate and a share-origin column). No manual step.
• No configuration changes and no breaking changes. The feedback, validation, and sign-off features are available wherever the portal is enabled with a database.

Installation

Homebrew (macOS)

brew install txn2/tap/mcp-data-platform

Claude Code CLI

claude mcp add mcp-data-platform -- mcp-data-platform

Docker

docker pull ghcr.io/txn2/mcp-data-platform:v1.84.0

Verification

All release artifacts are signed with Cosign. Verify with:

cosign verify-blob --bundle mcp-data-platform_1.84.0_linux_amd64.tar.gz.sigstore.json \
  mcp-data-platform_1.84.0_linux_amd64.tar.gz

Changelog

Features

• feat(feedback): generic thread substrate + human feedback authoring (#601) (#604) (@cjimti)
• feat(feedback): portal feedback panel UI + owner-scoped thread counts (#601) (#605) (@cjimti)
• feat(screenshots): comprehensive portal coverage, editor/drawer states, theming fixes (#599) (@cjimti)
• feat(threads): agent review bridge into the knowledge loop (#602) (#609) (@cjimti)
• feat(threads): validation/signoff lifecycle + worklists (#603) (#610) (@cjimti)

Bug Fixes

• fix(catalogs): handle embedded source kind without crashing the panel (#607) (@cjimti)
• fix(catalogs): debounce + visual feedback for spec retry/refresh (#608) (@cjimti)
• fix(feedback): address adversarial review of the feedback UI (#601) (#606) (@cjimti)

Full diff: v1.83.0...v1.84.0