Files
crank/apps/admin-api/tests/integration/resources/metrics_capture.rs
bsodfather 54ce770682
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
feat(epic3): deliver the accepted Epic 3 scope through Story 3.17
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 1b6db09bd1.
2026-10-25 09:08:22 +00:00

48 lines
2.4 KiB
Rust
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
//! Test-only поддержка изолированного захвата метрик для AT-3.6-06.
//!
//! Файл лежит в тестовом пути (`apps/<app>/tests/**`), поэтому объявление
//! прямого рекордера метрик здесь разрешено правилом
//! `scripts/check-metrics-boundaries.py` (`is_test_path`), а сам checker,
//! пороги и production-метрики не меняются.
//!
//! Подключение: приватный `#[cfg(test)]`-harness
//! `service::resources::tests::guard_telemetry` включает файл через `#[path]`.
//! Никакого production-экспорта, никаких новых публичных API и никакого обхода
//! проверки «через alias»: тот же самый `DebuggingRecorder`, что был раньше,
//! просто объявлен в тестовом размещении.
use metrics::{SharedString, Unit};
use metrics_util::{
CompositeKey,
debugging::{DebugValue, DebuggingRecorder, Snapshotter},
};
/// Один наблюдаемый образец метрики: ключ, единица, описание и значение.
pub(crate) type Sample = (CompositeKey, Option<Unit>, Option<SharedString>, DebugValue);
/// Установленный в процессе изолированный рекордер метрик.
pub(crate) struct MetricsCapture {
snapshotter: Snapshotter,
}
impl MetricsCapture {
/// Ставит изолированный рекордер и возвращает ручку для снятия образцов.
///
/// Рекордер и его захват — те же, что раньше жили в `guard_telemetry.rs`:
/// положительные образцы `crank_http_requests_total` по-прежнему обязательны
/// и проверяются тем же тестом.
pub(crate) fn install() -> Self {
let recorder = DebuggingRecorder::new();
let snapshotter = recorder.snapshotter();
recorder
.install()
.expect("isolated Resource guard metrics recorder");
Self { snapshotter }
}
/// Образцы, накопленные рекордером к этому моменту.
pub(crate) fn samples(&self) -> Vec<Sample> {
self.snapshotter.snapshot().into_vec()
}
}