Migrate the TAC operations views to Read API v2 - #3635
Draft
tom2drum wants to merge 1 commit into
Draft
Conversation
Adds the task spec and its six subtasks. Also adds two team first names to the cspell dictionary, since .agents/TEAM.md is in cspell's ignore list and spec headers name people. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Resolves #3627
The
tac-operation-lifecycleservice used to describe an operation's whole lifecycle through one overloadedtypefield that mixed the transfer route with the outcome, a rollback and a locally derived failure reason. Two consequences could not be worked around in the UI: the route was unknowable until an operation completed, so the direction could not be shown while it mattered most; and a finalized failure without a rollback was indistinguishable from a success. The service now exposes route, business outcome, rollback and failure reason as separate fields through a new Read API v2, and this branch moves the operations list, the operation details page and the by-transaction block onto it.The plan lives in
.agents/tasks/3627-tac-operations-api-v2/spec.md, split into six subtasks.This is a spec-first draft: nothing is implemented yet. The branch will receive the work subtask by subtask, and this description will be rewritten when the PR is marked ready for review.