ci: безопасно интегрировать принятый Crank и отделить production deploy #105
Merged
bsodfather
merged 17 commits from 2026-10-26 21:36:10 +00:00
ops/separate-production-deploy into main
17
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
4e7440f25e |
ci: separate protected source integration from explicit production deployment
CI / UI Checks (pull_request) Successful in 8s
CI / Rust Checks (pull_request) Successful in 12m54s
CI / Rust Feature Validation (pull_request) Skipped
CI / Frontend E2E (pull_request) Skipped
CI / Community Image Smoke (pull_request) Skipped
CI / Required Checks (pull_request) Successful in 3s
CI / Deploy (pull_request) Skipped
|
||
|
|
44774883a0 |
fix(epic3): выводить Tools-сигнал из клиентской проекции tools/list (Story 3.5, FR-14)
CI / UI Checks (pull_request) Successful in 8s
CI / Rust Checks (pull_request) Successful in 10m49s
CI / Rust Feature Validation (pull_request) Skipped
CI / Frontend E2E (pull_request) Skipped
CI / Community Image Smoke (pull_request) Skipped
CI / Required Checks (pull_request) Successful in 1s
CI / Deploy (pull_request) Skipped
Community Release / release (push) Successful in 25m35s
QA F1: CatalogFingerprint сравнивал только Tool-bindings, а tools/list строится из catalog_tool_definitions, которая ещё зависит от tool_selection_policy (mode, groups, search.max_results); в Search-режиме отдаваемый список вообще не зависит от bindings. Из-за этого commit, меняющий только политику, не порождал notifications/tools/list_changed (клиент оставался со stale-каталогом), а binding-only commit в Search порождал ложный сигнал. Теперь Tools-часть отпечатка — канонизированные определения, которые реально отдаёт tools/list (отсортированы, чтобы порядок чтения не был ложным изменением): сигнал есть ровно тогда, когда меняется видимая клиенту проекция. ATDD: новый сценарий на обеих ревизиях — policy-only commit (Direct -> Search) даёт ровно один Tools-кадр и авторитетный tools/list с search_tools/call_tool, а последующий binding-only commit в Search-режиме не сигналит. Юнит-оракулы переведены на реальную проекцию: policy-only change, невидимое поле политики, version bump с идентичным определением и binding change в Search-режиме — silent. |
||
|
|
a0365bb80b |
feat(epic3): отправлять Tools catalog change signals после commit (Story 3.5, FR-14)
Клиент, согласовавший tools list-changed, получает bounded `notifications/tools/list_changed` после коммита видимой Tool-проекции опубликованного Agent snapshot; `tools/list` остаётся авторитетным для клиента без notification и после reconnect. - signals.rs: третий тип сигнала в существующем stream-local watcher (один tick = максимум один кадр на тип, fixed-capacity queue, без cross-process bus и без post-commit hook); fingerprint сравнивает tool_name/operation.version/title/description, поэтому Tool-only commit не даёт Resource/Prompt сигналов и наоборот. - registry.rs: tools.listChanged=true (реально отправляется в обеих revision); modern filter toolsListChanged теперь подтверждается acknowledge и не шлётся вне согласованного набора. - legacy GET-стрим несёт Tools-сигнал вместе с Resource/Prompt. - ATDD: RED на baseline (ack пуст, Tools-кадра нет, capability false), GREEN — 8 integration-сценариев × обе revision, unit-оракулы wire, representatives official MCP SDK 1.32.2 smoke со штатными headers. - capability inventory/baseline manifest и frozen projection обновлены под tools.listChanged=true; ci-story-checks.sh дополнен AC 3.5. |
||
|
|
2499016dc7 |
fix(epic3): принимать поток progress при JSON-first Accept официального SDK (Story 3.4, FR-14)
CI / Rust Checks (pull_request) Successful in 9m12s
CI / Rust Feature Validation (pull_request) Skipped
CI / Frontend E2E (pull_request) Skipped
CI / Community Image Smoke (pull_request) Skipped
CI / Required Checks (pull_request) Successful in 1s
CI / Deploy (pull_request) Skipped
CI / UI Checks (pull_request) Successful in 10s
Community Release / release (push) Successful in 24m39s
Официальный MCP SDK перечисляет медиатипы в `Accept` JSON-first (`application/json, text/event-stream`). Прежняя реализация выбирала negotiated JSON-тело, и клиент, которому нужен progress, не получал ни одного кадра. Коррекция переиспользует уже провалидированные шаги: для `tools/call` с допустимым progress token и предложенным event-stream режим ответа переключается на SSE. Admission/авторизация не двигались; другой метод, отсутствующий или непригодный token и JSON-only `Accept` сохраняют negotiated режим. ATDD: тот же JSON-first `Accept` даёт строго монотонные progress 1/2/3 и прежний result в обеих supported revisions, а негативные контроли (без token и с непригодным token) остаются на JSON-теле. |
||
|
|
f613250fd3 |
fix(epic3): сделать ATDD отмены чувствительным к регрессии и покрыть bounds токена в обеих revision (Story 3.4, FR-14)
- CANCEL_GRACE_MS 1200 -> 2500 (> LONG_HOLD_MS) и const-assert на этот порядок: при незавершённой отмене вызов успевает завершиться и записать исход внутри окна проверки, поэтому тест доказывает остановку, а не только «ещё не готово». - malformed/oversized/empty/object/array token теперь проверяются и в modern revision, не только в legacy (обе читают одно поле RequestMetaObject). - комментарий cancelled_response приведён к фактическому поведению: у остановленного вызова строки Invocation History нет вообще. |
||
|
|
862cde8559 |
feat(epic3): progress и безопасная отмена Tool calls (Story 3.4, FR-14)
- request-scoped lifecycle одного tools/call: валидированный `_meta.progressToken` (строковый/числовой, 1..=128 байт) и bounded очередь реальных этапов (tool_resolved → authorization_resolved → execution_dispatched) в собственный SSE-stream запроса; без token или без stream-carrier результат не меняется; - сериализация `notifications/progress` по pinned схеме обеих revisions (progressToken/progress/message, total не изобретается); - отмена по revision: 2025-11-25 — `notifications/cancelled` через bounded in-flight таблицу (владение = session + platform credential, не progress token); 2026-07-28 — закрытие response stream; в обоих случаях drop будущего вызова = кооперативная остановка, terminal-сообщение не отправляется; - streamed ответ сохраняет проекцию Story 3.18: closed `notifications/message` перед финальным кадром (перенос logging-scope в тело стрима); - ATDD: 12 end-to-end тестов на реальном endpoint/каталоге/counted upstream (обе revisions, malformed/oversized/reused token, owner/foreign/late cancel, disconnect, ambiguous outbound, representative client smoke) + 7 unit-тестов границ lifecycle; entry в scripts/ci-story-checks.sh. |
||
|
|
49c8af24ed |
fix(epic3): обновить checksum inventory в capability baseline (Story 3.19)
CI / Rust Checks (pull_request) Successful in 8m5s
CI / Rust Feature Validation (pull_request) Skipped
CI / UI Checks (pull_request) Successful in 31m50s
CI / Frontend E2E (pull_request) Skipped
CI / Community Image Smoke (pull_request) Skipped
CI / Required Checks (pull_request) Successful in 1s
CI / Deploy (pull_request) Skipped
Community Release / release (push) Successful in 22m34s
Story 3.19 меняет `docs/capability-inventory.json` (статусы `listChanged`, `subscriptions/listen`, `notifications/*/list_changed`), поэтому `docs/capability-baseline/manifest.json` должен ссылаться на новый SHA-256 того же артефакта: `85970569…` → `10ca3538aa1b6b25868f80e19932c7ef918398c4817c52bc1aae52f18c31522b`, ровно как в `tests/fixtures/mcp-revisions/*.provenance.json` этого же delta. Поймано Required CI на `a965bc4` (run 887, job 2491): шаг `Check Capability Baseline` падал с `CHECKSUM_MISMATCH pointer=/artifacts/0/sha256`; остальные шаги того же job'а (tooling unit tests 305 OK, capability inventory `status=valid protocol_items=50`, community scope) были зелёными. Локально после правки: `validate-capability-baseline.py` → `baseline_version=2026.08.24.1 flows=35`, `validate-capability-inventory.py` → `status=valid`, community scope (1263 файла), runtime-config/config/metrics/rust boundaries и code health — 0. Содержательных изменений продукта здесь нет: только checksum-указатель на уже изменённый в предыдущем коммите артефакт. |
||
|
|
a965bc4137 |
feat(epic3): уведомления об изменении Resource/Prompt каталога MCP (Story 3.19)
CI / UI Checks (pull_request) Successful in 9s
CI / Rust Checks (pull_request) Failing after 4m10s
CI / Rust Feature Validation (pull_request) Skipped
CI / Frontend E2E (pull_request) Skipped
CI / Community Image Smoke (pull_request) Skipped
CI / Required Checks (pull_request) Failing after 1s
CI / Deploy (pull_request) Skipped
Story 3.19 / FR-19 на принятой базе Story 3.18 (`47a6e54`, PR #99): после commit опубликованного каталога Agent клиент получает `notifications/resources/list_changed` и/или `notifications/prompts/list_changed`, обе pinned revisions, а обычное чтение каталога остаётся авторитетным при потере сигнала. Scope ограничен list-change: `resources/subscribe`/`unsubscribe` остаются `-32601`, значение `resources.subscribe` остаётся `false` (одобренный владельцем вариант A). Публикация переносит только semantic delta Story 3.19 из `/home/codex/code/crank-worktrees/story31-worktree` (`1b6db09` + cumulative overlay) на принятый head 3.18, а не копирует worktree: - новый `protocol/signals.rs` (watcher, отпечаток каталога, bounded filter, revision-correct encoders, bounded legacy stream registry) и `protocol/signals_tests.rs` (17 unit oracles); - `subscriptions/listen` (modern-only dispatch registration) + честные `listChanged: true` объявления; `app/endpoint.rs` получает legacy GET producer/DELETE retire, `app/dispatch.rs` — modern listen stream; - ATDD `mcp_signals` 5 сценариев на реальном endpoint/PostgreSQL/artifact store; capability inventory и frozen/provenance проекции обновлены (`b90b59f3…`, inventory `10ca3538…`); - `scripts/ci-story-checks.sh`: добавлены 3.19-проверки, записи Story 3.18 сохранены (гейт не ослаблен). Принятая правка code-health `206ca78` сохранена: `app/endpoint.rs` 402 строки (было 381), `app/legacy_dispatch.rs` 731 без изменений, т.е. split не переписан. Новый ATDD-файл `mcp_signals.rs` до 1138 строк превышал лимит `scripts/check-rust-code-health.sh`, поэтому его сценарии механически вынесены в `mcp_signals/scenarios.rs` без изменения проверок. Наследованный дефект tooling-гейта: `tests/unit/test_validate_capability_inventory.py` требует, чтобы `Run tooling unit tests` шёл раньше `scripts/validate-capability-inventory.py`; в принятом `ci.yml` (3.18) шаг оказался в условном feature-job. Шаг перенесён в обязательный `rust` job перед проверкой inventory — исполняемый tooling-гейт теперь проверяется там же, где применяется; ни одна проверка не отключена и не ослаблена. Проверки на этом коммите: `ci-story-checks.sh` exit 0 — 4/9/1/12/10/3/5(+1 manual ignored)/17 passed; `crank-community-mcp --lib` 102/0; transport 20/0, mcp_prompts 15/0, revision_matrix::negotiation 23/0, era_isolation 5/0; `cargo fmt --check` и `cargo clippy -p crank-community-mcp -p mcp-server --all-targets -D warnings` — 0; `check-rust-code-health.sh` — pass; capability inventory `status=valid protocol_items=50 revisions=2`; `python3 -m unittest discover -s tests/unit` — 305 OK. NOT_RUN (честно, не PASS): полный `just verify`, межкомпонентная интеграция, нагрузка и квалификация ≥3 реальных клиентов — остаются на собранной фиче 3.20 по validation-policy.md. |
||
|
|
47a6e54660 |
fix(ui): bump nginx runtime base to 1.30.6 for the image scan gate
CI / Rust Checks (pull_request) Successful in 6m33s
CI / Rust Feature Validation (pull_request) Skipped
CI / UI Checks (pull_request) Successful in 16m36s
CI / Frontend E2E (pull_request) Skipped
CI / Community Image Smoke (pull_request) Skipped
CI / Required Checks (pull_request) Successful in 1s
CI / Deploy (pull_request) Skipped
Community Release / release (push) Failing after 16m35s
|
||
|
|
206ca784f7 |
fix(epic3): уложить endpoint.rs Story 3.18 в лимит 1000 строк
CI / UI Checks (pull_request) Successful in 11s
CI / Rust Checks (pull_request) Successful in 9m2s
CI / Rust Feature Validation (pull_request) Skipped
CI / Frontend E2E (pull_request) Skipped
CI / Community Image Smoke (pull_request) Skipped
CI / Required Checks (pull_request) Successful in 1s
CI / Deploy (pull_request) Skipped
The Story 3.18 logging arm pushed `crates/crank-community-mcp/src/app/endpoint.rs` to 1058 lines, so `scripts/check-rust-code-health.sh` failed the Required CI (Rust Checks, run 870 / job 2408) at the pinned 1000-line default. Move the whole legacy-era dispatch of `mcp_post_response` verbatim into `app/legacy_dispatch.rs` (`handle_legacy_request`), leaving the endpoint as the transport/admission layer it documents itself to be. endpoint.rs is now 381 lines and the new module 731, both inside the limit; no baseline pin and no check was touched. Behaviour is unchanged: the moved match keeps every arm, envelope, status code and safe detail as-is (legacy-only logging/setLevel, -32602 INVALID_LEVEL, EVENT_LEVEL_APPLIED Notice acknowledgment, per-session level isolation), the pre-dispatch legacy level read stays in `mcp_post_response`, and the only edits to the moved text are the mechanical `&credential` -> `credential` (the credential now arrives as a reference) and `protocol_version` already being `Option<&str>`. |
||
|
|
a438c1df42 |
feat(epic3): безопасное structured logging MCP (Story 3.18)
CI / UI Checks (pull_request) Successful in 11s
CI / Rust Checks (pull_request) Failing after 4m11s
CI / Rust Feature Validation (pull_request) Skipped
CI / Frontend E2E (pull_request) Skipped
CI / Community Image Smoke (pull_request) Skipped
CI / Required Checks (pull_request) Failing after 1s
CI / Deploy (pull_request) Skipped
Story 3.18 (#25) surface: клиент получает только закрытые structured `notifications/message` выбранного уровня, без запросов, секретов и internal causes. - `logging` capability advertising в обеих поддерживаемых revisions; `logging/setLevel` — legacy-only dispatch (modern — `_meta` per request); - закрытый словарь LoggingLevel (RFC 5424), malformed → -32602 с одним safe detail; закрытый набор safe events, task-local request scope; bounded in-memory opt-in, без миграций; - `notifications/message` идут перед ответом в SSE; JSON-режим их не несёт; - ATDD в `scripts/ci-story-checks.sh`: mcp_logging (10), inventory projection (3), protocol::logging unit (12); - проекция capability inventory/frozen oracle переведена на `logging`. Story ATDD и affected проверки пройдены на этом дереве (fmt, clippy, python oracle 56 OK, capability inventory valid). Полный `just verify` — NOT_RUN на story по validation-policy, остаётся на собранной фиче. |
||
|
|
aed83268a0 |
fix(release): publish assets to the public HTTPS Gitea origin
CI / UI Checks (pull_request) Successful in 8s
CI / Rust Checks (pull_request) Successful in 6m53s
CI / Rust Feature Validation (pull_request) Skipped
CI / Frontend E2E (pull_request) Skipped
CI / Community Image Smoke (pull_request) Skipped
CI / Required Checks (pull_request) Successful in 1s
CI / Deploy (pull_request) Skipped
Community Release / release (push) Failing after 38m13s
The release job container sees gitea.server_url as the internal http://gitea:3000 origin, so scripts/ci-release-assets.py refused to forward its token (run 865 failed at the publish step after packaging). Point the publisher at https://git.itexp.me, the origin the repository already uses for the public URL. |
||
|
|
12d8a3d490 |
fix(test): isolate Valkey in the CI job network and bound readiness
CI / UI Checks (pull_request) Successful in 8s
CI / Rust Checks (pull_request) Successful in 6m1s
CI / Rust Feature Validation (pull_request) Skipped
CI / Frontend E2E (pull_request) Skipped
CI / Community Image Smoke (pull_request) Skipped
CI / Required Checks (pull_request) Successful in 1s
CI / Deploy (pull_request) Skipped
Community Release / release (push) Failing after 18m56s
|
||
|
|
e57ab47c05 |
ci: run the Story 3.16 composite-prompt ATDD in the story gate
CI / UI Checks (pull_request) Successful in 8s
CI / Rust Checks (pull_request) Canceled after 19m49s
CI / Rust Feature Validation (pull_request) Canceled after 0s
CI / Frontend E2E (pull_request) Canceled after 0s
CI / Community Image Smoke (pull_request) Canceled after 0s
CI / Deploy (pull_request) Canceled after 0s
CI / Required Checks (pull_request) Failing after 1s
The recovery branch publishes Story 3.16 together with Story 3.17, so the targeted story gate must exercise both accepted user outcomes: composite Prompts with published Resources and the bounded completion/resources-list admission of 3.17. |
||
|
|
1baeefe889 |
ci: validate accepted stories with targeted ATDD and gate feature checks
CI / UI Checks (pull_request) Successful in 10s
CI / Rust Checks (pull_request) Failing after 25m35s
CI / Rust Feature Validation (pull_request) Skipped
CI / Frontend E2E (pull_request) Skipped
CI / Community Image Smoke (pull_request) Skipped
CI / Required Checks (pull_request) Failing after 1s
CI / Deploy (pull_request) Skipped
|
||
|
|
9567bbf3aa |
fix(ci): pass the community scope guard and publish release artifacts before registry steps
CI / Rust Checks (pull_request) Canceled after 38m52s
CI / UI Checks (pull_request) Canceled after 0s
Community Release / release (push) Canceled after 38m39s
CI / Frontend E2E (pull_request) Canceled after 0s
CI / Community Image Smoke (pull_request) Canceled after 0s
CI / Deploy (pull_request) Canceled after 0s
- the community scope guard rejected the innocuous English comment 'One timed resources/list' in the Story 3.8 discovery diagnostic (its 'one-time-token' marker matches any 'one time' phrase). Reword the comment; no behaviour change. - move the release artifact publication ahead of the registry/OpenBao steps, so a credential problem cannot leave the archives, checksums and SBOM unpublished. |
||
|
|
54ce770682 |
feat(epic3): deliver the accepted Epic 3 scope through Story 3.17
CI / Rust Checks (pull_request) Failing after 13m41s
CI / UI Checks (pull_request) Skipped
CI / Frontend E2E (pull_request) Skipped
CI / Community Image Smoke (pull_request) Skipped
CI / Deploy (pull_request) Skipped
Community Release / release (push) Failing after 13m33s
Recovery delivery of the accumulated, TL-accepted Epic 3 work that had never been
committed to Git (stories 3.6-3.17, see the crank board). Story 3.18 is not accepted
yet and is deliberately excluded: its logging surface, its capability registration,
its oracle projections and its tests are not part of this tree.
Accepted scope
- 3.6 typed static Resource Drafts; 3.7 publication and exact binding of static
Resource Versions; 3.8 MCP discovery/read and revocation of static Resources;
- 3.9 Resource import/export in API and UI plus TLS dependency maintenance;
3.10 REST-backed Resource templates; 3.11 shared REST read runtime and the MCP
revision/capability foundation;
- 3.12 parameterised Prompt Drafts with preview; 3.13 Prompt publication and exact
version binding to Agents; 3.14 MCP prompts; 3.15 Prompt import/export;
- 3.16 composite Prompts with published Resources (dependency content scan plus
dynamic read through the accepted 3.11 runtime, admin preview and MCP prompts/get);
- 3.17 bounded MCP completion suggestions from typed published schemas and the
resources/list admission fix for bound template publications.
Accepted evidence being reused (unchanged code paths)
- 3.16 candidate: core 7, admin-api 22, registry 4, mcp-server 4, UI 6; one final
`just verify` run 1651 passed / 0 failed / 2 ignored.
- 3.17 candidate: full run 1672 passed / 0 failed / 2 ignored, QA targeted reruns and
a real MCP Inspector 2.12.0 client smoke.
Delivery engineering in this commit
- CI: one event per change (feature branches are gated by their pull request, push
runs only on main), story events run the changed packages, the full workspace suite
stays the feature/release gate; no cache/sharding without a measured runner check.
- Release: the packaged archives, checksums and SBOM are now uploaded to the Gitea
release entry of the tag instead of dying with the runner workspace.
Not included on purpose: Story 3.18 work, build caches, runtime databases, local
credentials and scratch evidence.
Refs: crank kanban t_e39d7263; baseline
|