Repository navigation
refactor(api,mcp,auth)!: align thread history, panel routes, tool names and user fields with shared conventions - #292
Merged
Merged
Conversation
Bring the remaining API and MCP names in line with the shared LabStack
conventions now recorded in AGENTS.md.
- Agent thread history returns items and next_cursor (null at the end),
accepts page_size, and summarises threads as {id, title, updated_at}.
A thread reads as {id, messages, updated_at}; AG-UI messages, run
inputs and events keep their protocol names. The route parameter is :id.
- POST /api/variables/resolve moves to POST /api/panels/variables/resolve,
next to the other panel routes and matching resolve_panel_variables.
- The MCP app helper get_panel_exemplars becomes list_panel_exemplars: it
returns a bounded set of traces, not one known resource.
- replace_dashboard no longer claims to be idempotent. base_version is
optional and every save appends a version.
- The auth middleware no longer reserves the retired /-/ prefix.
- AGENTS.md states the conventions without pointing at private projects,
adds id, pagination and annotation rules, and records the single-provider
OIDC routes as an exception.
BREAKING CHANGE: thread history JSON, the variable resolution route and the
exemplar tool name change with no aliases.
User accounts follow the shared user conventions: role and status
changes are separate operations from profile edits, and the fields use
the shared names.
- Migration 20261009000000 renames users.name to display_name and
replaces the active flag with status ('active' or 'suspended').
- PATCH /api/users/{id} changes only email and display_name.
PATCH /api/users/{id}/role and PATCH /api/users/{id}/status are new,
admin-only routes. All three reject unknown fields and bound the body.
- User JSON, including /api/auth/me and setup, uses display_name and
status.
- Suspension blocks every sign-in path, sessions and OAuth tokens as
inactive accounts did. Role and status changes still revoke sessions,
and the last active administrator is still protected.
- The suspension audit event is user.suspended.
BREAKING CHANGE: user JSON fields and the user update routes change with
no aliases.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Align Fanout's remaining API and MCP names with the shared LabStack naming conventions, which AGENTS.md now states directly.
itemsandnext_cursor(nullat the end) and acceptspage_size. A thread summary is{id, title, updated_at}and a thread reads as{id, messages, updated_at}. The route parameter is:id. AG-UI messages, run inputs and events keep their protocol names.POST /api/panels/variables/resolve, next to the other panel routes and matching theresolve_panel_variablestool.get_panel_exemplarsbecomeslist_panel_exemplars, because it returns a bounded set of traces rather than one known resource.replace_dashboardno longer claims to be idempotent:base_versionis optional and every save appends a version.PATCH /api/users/{id}changes onlyemailanddisplay_name.PATCH /api/users/{id}/roleandPATCH /api/users/{id}/statuschange role and status. All three reject unknown fields and bound the request body./api/auth/meand setup, usesdisplay_nameandstatus(activeorsuspended).user.suspended./-/prefix.Contract changes. None of these have aliases.
items,next_cursor,page_size,idandupdated_at.POST /api/variables/resolveis nowPOST /api/panels/variables/resolve.get_panel_exemplarsis nowlist_panel_exemplars.nameis nowdisplay_name, andactiveis replaced bystatus.PATCH /api/users/{id}no longer changes role or status. The two new routes above do that.20261009000000_user_profile_status.sql(Goose) renamesusers.nametodisplay_nameand replaces theactiveflag withstatus.Verification
just checkjust test-racewhen auth, API, ingest, query, MCP, or agent paths changedjust e2e(28/28)