Story 3.4 — progress и кооперативная отмена Tool call (FR-14) #102
Closed
bsodfather
wants to merge 0 commits from
delivery/epic3-story-3.4 into main
pull from: delivery/epic3-story-3.4
merge into: bsodfather:main
bsodfather:main
bsodfather:delivery/rmcp107-progress-peer
bsodfather:delivery/rmcp107-subscriptions
bsodfather:delivery/rmcp107-logging-handler
bsodfather:delivery/rmcp107-notification-handlers
bsodfather:delivery/rmcp107-negotiation-handlers
bsodfather:delivery/rmcp107-tools
bsodfather:delivery/rmcp107-completion-handler
bsodfather:delivery/rmcp107-prompts-handlers
bsodfather:delivery/rmcp107-resource-handlers
bsodfather:delivery/rmcp107-responses
bsodfather:delivery/rmcp107-dispatch
bsodfather:delivery/rmcp107-initialized
bsodfather:delivery/rmcp107-ping
bsodfather:delivery/rmcp107-initialize-input
bsodfather:delivery/rmcp107-negotiation
bsodfather:delivery/rmcp107-envelopes
bsodfather:work/rmcp107-signals
bsodfather:delivery/rmcp107-progress-cancel
bsodfather:work/rmcp107-logging
bsodfather:fix/rustix-rustsec-2026-0486
bsodfather:delivery/rmcp107-completion
bsodfather:fix/rmcp-security-0462
bsodfather:delivery/rmcp107-prompts
bsodfather:delivery/rmcp107-resources
bsodfather:delivery/rmcp107-tools-responses
bsodfather:feat/rmcp107-tools-runtime
bsodfather:fix/trivy-runner-cache-20261108
bsodfather:fix/trivy-asset-api-20261108
bsodfather:fix/release-db-source-20261107
bsodfather:fix/release-resume-20261107
bsodfather:feat/rmcp106-tools-adapter
bsodfather:feat/story-4.5-input-continuation
bsodfather:delivery/epic4-story-4.4
bsodfather:delivery/ui-npm-tls12-cap
bsodfather:delivery/epic4-story-4.3
bsodfather:delivery/epic4-story-4.2
bsodfather:ops/separate-production-deploy
bsodfather:delivery/epic4-story-4.1
bsodfather:delivery/epic3-story-3.5
bsodfather:delivery/epic3-story-3.19
bsodfather:delivery/epic3-story-3.18
bsodfather:delivery/ui-image-security-fix
bsodfather:delivery/epic3-through-3.17
bsodfather:ops/ui-scope-20261025
bsodfather:ci/delivery-20261025
bsodfather:wip/hermes-checkpoint-20261025t100022z
bsodfather:wip/hermes-checkpoint-20261025t080537z
bsodfather:fix/epic2-external-uri-parity
bsodfather:maintenance/reconcile-20261003
bsodfather:master
bsodfather:fix/review-story-1-2
bsodfather:fix-review-story-1-2
No Reviewers
Labels
Clear labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
feature-ready
Breaking change that won't be backward compatible
Something is not working
Documentation changes
Improve existing functionality
New functionality
This is security issue
Issue or pull request related to testing
Фича/эпик собраны: выполнить необходимые полные интеграционные/E2E проверки CI.
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Medium
3
The priority is medium
Priority
Low
4
The priority is low
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
Status
Abandoned
3
Somebody has started to work on this but abandoned work
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
bsodfather
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: bsodfather/crank#102
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Кандидат поставки: принятая TL Story 3.4 (#11) поверх принятого объёма Эпика 3 (3.6–3.17), Story 3.18 и Story 3.19.
delivery/epic3-story-3.4, head2499016dc7a691f240b51f180cea06a87930b6bef613250fd3c7e63796c679b1f7b9cd5cbdf5b8fd(принятый candidate Story 3.4, treed95d598c43ed511449f7dc6165c25243bc6e4b73), correction накатан отдельным коммитом2499016из durable patchstory34-accepted-correction.patch(sha256265b13baad6fd656dd2d070b689485341baf616279b16daa7178de3bade8a28a).main/1b6db09:aed8326(3.6–3.17, rc.4) →a438c1d(3.18) →206ca78(code-health) →47a6e54(UI nginx 1.30.6, rc.6) →a965bc4(3.19) →49c8af2(rc.7) →862cde8/f613250(Story 3.4) →2499016(принятая коррекция).Что меняется
tools/call, который несёт валидный progress token и предлагаетtext/event-streamвAccept, получает поток даже если медиатипы перечислены JSON-first — именно так их отправляет официальный MCP SDK. Раньше такой клиент не видел ни одного progress-кадра.Acceptостаются на negotiated JSON-теле.apps/mcp-server/tests/integration/tools_lifecycle.rs(обе supported revisions + негативные контроли);scripts/ci-story-checks.shуже содержит записи Story 3.4 (app::lifecycle,tools_lifecycle) и соответствует AC3.4 — правка entry не потребовалась.Проверки
t_3d6f1354: RED endpoint-only revert / GREEN на обеих revisions, lifecycle 14, transport 20, revision matrix 99, fmt/clippy PASS; официальный SDK 1.32.2 со штатнымAccept— progress 1/2/3 и прежний resultlead_123.t_2e40d1a1на exactf613250+ этот correction diff.t_ffc22d76.Честные границы
mainне вливается: merge запускает protected productionDeploy, для него нужен отдельно одобренный target/runbook с backup и rollback.just verifyна этой волне не перезапускался: исторический full наf613250переиспользуется только как фон, коррекция подтверждена точечными affected-проверками по validation-policy.Результат обязательных проверок на этом head (
2499016dc7a691f240b51f180cea06a87930b6be):CI / Required Checks (pull_request)= success (run 921, 16:13:27Z)CI / Rust Checks (pull_request)= success, 9m12s — включая story ATDD:app::lifecycle7,tools_lifecycle14, плюс предыдущие entry 4/9/1/12/10/3/5(+1 ignored)/17CI / UI Checks (pull_request)= successfeature-ready)Prerelease
v0.4.0-rc.8опубликован: https://git.itexp.me/bsodfather/crank/releases/tag/v0.4.0-rc.8 (release id 388, prerelease=true, annotated tag → этот же SHA). Release pipeline run 922 — success: story ATDD, сборка бинарников и UI, package/checksums/SBOM, публикация вложений, composeup --wait(postgres, migrate, admin-api, mcp-server, ui — все healthy, миграцииfrom_version 0 → 23 applied), неизменённый image scanpassдля всех трёх образов, push в registry.Вложения релиза проверены скачиванием: 3 архива + checksums + SBOM, все три архива покрыты
crank-community-v0.4.0-rc.8-checksums.txtи совпадают по SHA-256; SBOM в manifest не входит.PR остаётся открытым: merge в
mainзапускает protected productionDeployи в эту поставку не входит. Production/стенды/Seerr/VPN/DNS не затрагивались; Story 3.20/auth и AC09 в поставку не входят.Интеграция выполнена объединяющим PR #105, main
599dc1867b. Head этого PR полностью входит в main. Закрываю заменённую заявку; исходные ветки и теги сохраняются. Production deploy отделён от merge и не запускался.Pull request closed