mirror of
https://github.com/azaion/annotations.git
synced 2026-06-21 16:21:07 +00:00
Oleksandr Bezdieniezhnykh
03f879206e
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>
1.5 KiB
1.5 KiB
Flow F3 — Real-time SSE Subscription
Cross-reference: system-flows.md → Flow F3.
Sequence
sequenceDiagram
autonumber
participant UI
participant Ctrl as AnnotationsController.Events (component 02 doc-ownership)
participant Evt as AnnotationEventService (02)
participant ProducerF1 as Flow F1 (annotation create)
participant ProducerF8 as Flow F8 (dataset bulk status)
UI->>Ctrl: GET /annotations/events (Accept: text/event-stream, JWT ANN)
Ctrl->>Ctrl: set Content-Type: text/event-stream, no-cache
Ctrl->>Evt: ReadAllAsync(cancellationToken)
par event sources
ProducerF1->>Evt: PublishAsync(eventDto)
ProducerF8->>Evt: PublishAsync(eventDto)
end
Evt-->>Ctrl: yield AnnotationEventDto
Ctrl-->>UI: data: {json}\n\n
UI--xCtrl: client disconnects
Ctrl->>Ctrl: cancellation token fires; loop exits
State
stateDiagram-v2
[*] --> Subscribing
Subscribing --> Streaming: header sent + reader attached
Streaming --> Streaming: PublishAsync -> data frame
Streaming --> Closed: client cancel / process restart
Closed --> [*]
Notes
- Channel is unbounded: a slow client cannot back-pressure the producer. If a client stalls indefinitely, memory growth is bounded by per-publisher cancellation tokens at the controller level. Step 4 verification candidate.
- Cross-pod fan-out is not provided — each pod has its own channel. Sticky sessions or a broker-backed bus required for horizontal scale.