feat(task-trackers): add custom HTTP provider#254
Merged
Conversation
Решения: - Добавлен встроенный provider key custom-http вместо vendor-specific адаптера для приватных систем. - Generic HTTP contract реализован поверх base_url + Bearer token и маппит upstream DTO в TaskTrackerCard, включая upstream web_url как неперсистентное поле browser response. - Kaiten остаётся зарегистрированным provider; registry/catalog теперь содержит оба provider-а. Отброшено: - Runtime plugin host и multi-instance generic providers не добавлялись, потому что текущая settings-модель keyed by tracker рассчитана на один endpoint. - Vendor-specific provider для Overtime не добавлялся, чтобы не делать приватный upstream публичной осью Throne. Ограничения: - Custom HTTP adapter read-only: не пишет в upstream, не зеркалит карточку в Intent.text и не меняет lifecycle Intent.
gently-whitesnow
force-pushed
the
feat/custom-http-task-tracker
branch
from
July 16, 2026 08:03
315af7d to
3a7bd59
Compare
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.
Цель
Добавить в Throne расширяемую интеграцию приватных task-tracker систем через встроенный generic/custom HTTP provider, не заводя vendor-specific provider для Overtime.
Изменения
custom-httpрядом с существующимkaiten.specs/contracts/task-trackers/generic-http.md.TaskTrackerCardполучил optional upstreamWebUrl; API browser DTO предпочитает его, но attachment snapshot остаётся read-only/non-authoritative.Решения
custom-httpостаётся обычным in-tree provider по ADR-0045/0046.Ограничения
custom-http, потому что текущая settings-модель keyed by tracker.Проверка
git diff --check origin/master...HEADdotnet test apps/api/tests/Throne.Application.Tests/Throne.Application.Tests.csproj --filter 'FullyQualifiedName~TaskTrackers'dotnet test apps/api/tests/Throne.Api.Tests/Throne.Api.Tests.csproj --filter 'FullyQualifiedName~TaskTracker'dotnet test apps/api/tests/Throne.Infrastructure.Tests/Throne.Infrastructure.Tests.csproj --filter 'FullyQualifiedName~TaskTrackers'