mirror of https://github.com/azaion/annotations.git synced 2026-06-21 18:51:06 +00:00

Files

T

Oleksandr Bezdieniezhnykh 03f879206e docs+src: complete Steps 1-3 outcomes + auth re-sync baseline

This commit captures everything produced during autodev existing-code
Steps 1 (Document), 2 (Architecture Baseline Scan), and 3 (Test Spec),
together with the targeted auth + CORS re-sync triggered on 2026-05-14
when codebase drift was detected at Step 4 entry. None of this work was
previously committed.

Step 1 (Document) — 50+ _docs/02_document/ files: problem, solution,
architecture, system flows, glossary, module-layout, per-component
specs (01..06), modules, deployment, diagrams, data model, FINAL
report, verification log, discovery.

Step 2 (Architecture Baseline) — architecture_compliance_baseline.md.
Verdict PASS_WITH_WARNINGS (0 Critical, 0 High, 1 Medium, 2 Low). No
High/Critical findings; auto-chained to Step 3 per existing-code flow.

Step 3 (Test Spec) — _docs/02_document/tests/* (67 scenarios across
blackbox, security, resilience, resource-limit, performance), plus
e2e/docker-compose.test.yml, e2e/seed/run.sh, scripts/run-tests.sh,
scripts/run-performance-tests.sh. Coverage 88% over the active scope
(40 of 45 items covered, 6 RB-deferred, 5 documented-as-uncovered).

Targeted auth + CORS re-sync — replaces the deleted in-house token
issuer with a JWKS-verifier model. AuthController and TokenService
removed; JwtExtensions switched from HS256 symmetric to ES256 over
admin's JWKS. ConfigurationResolver and CorsConfigurationValidator
added under src/Infrastructure/. ADR-002 and ADR-006 retired; SEC-01,
SEC-02, SEC-03 marked Closed. One new testability risk recorded in
architecture.md Open Risks Section 6 (JWKS HTTPS gating).

Source changes:
- src/Auth/JwtExtensions.cs (modified) — ES256, JWKS, alg pinning
- src/Program.cs (modified) — DI wiring for ConfigurationResolver
  and CorsConfigurationValidator
- src/Controllers/AuthController.cs (deleted) — no in-service issuance
- src/Services/TokenService.cs (deleted) — same
- src/Infrastructure/ConfigurationResolver.cs (new)
- src/Infrastructure/CorsConfigurationValidator.cs (new)
- .env.example (new) — required env var documentation
- .gitignore (updated)

Cross-repo coordination: _docs/cross-repo/flights_h1_h2_h3_change_spec
captures the change-spec for downstream services that consumed the now
deleted /auth endpoints.

Co-authored-by: Cursor <cursoragent@cursor.com>

2026-05-14 20:19:05 +03:00

1.6 KiB

Raw Blame History

Annotations (realtime & stream sync)

1. High-Level Overview

Purpose: SSE push for annotation changes and RabbitMQ Stream failsafe export — 01_annotations.md sections SSE Communication and Annotation Sync / Failsafe / RabbitMQ Stream.

Architectural pattern: Event channel + background outbox producer.

Upstream dependencies: Platform (DB, config, paths), Annotations REST (domain mutations enqueue/publish).

Downstream consumers: Browser UI (SSE); Admin sync worker; AI Training consumer (external).

2. Internal interfaces

AnnotationEventService — in-process Channel<AnnotationEventDto>; PublishAsync / Reader.
FailsafeProducer + RabbitMqConfig — stream client, MessagePack payloads, drains annotations_queue_records.
HTTP: AnnotationsController.Events — text/event-stream subscription (same controller file as REST component; doc ownership here for SSE).

3. External API / integration

Surface	Notes
`GET /annotations/events`	SSE; see suite SSE section
RabbitMQ stream `azaion-annotations`	Env `RABBITMQ_*` from `Program`

4. Data access patterns

Queue table buffering; stream send on connectivity; image bytes in create messages per suite.

5. Caveats

MessagePack key stability; stream consumer offsets independent per consumer type.

6. Dependency graph

Imports from: Platform, annotations domain (via service calls / shared types). Consumed by: External infrastructure.

7. Modules included

sse-realtime, rabbitmq-stream-sync.

1.6 KiB Raw Blame History