azaion/satellite-provider

Fork 0

mirror of https://github.com/azaion/satellite-provider.git synced 2026-06-21 07:01:15 +00:00

Files

T

Oleksandr Bezdieniezhnykh 51b572108a

ci/woodpecker/push/01-test Pipeline was successful

Details

ci/woodpecker/push/02-build-push Pipeline was successful

Details

[AZ-484] Cycle 1 Steps 12-16: docs, security, perf, deploy report

Captures the post-implementation autodev gates for AZ-484 multi-source
tile storage:

- Step 12 (Test-Spec Sync): added 7 AC rows (AZ-484 AC-1..AC-7) and a
  PT-07 NFR row to traceability-matrix.md; added PT-07 scenario to
  performance-tests.md.
- Step 13 (Update Docs): refreshed data_model.md (tiles columns +
  indexes + selection rule + UPSERT contract + migrations 012/013),
  module-layout.md (Common/Enums section with L-001 guidance,
  DataAccess imports-from now lists 6 sites), 6 module / component
  docs to reflect the new repo signatures, source/captured_at fields,
  and Dapper enum bypass workaround. ripple_log_cycle1.md records
  zero out-of-scope ripple.
- Step 14 (Security Audit): PASS_WITH_WARNINGS - 0 Critical, 0 High,
  5 Medium, 5 Low. AZ-484 itself added zero new findings. Hardening
  items (Postgres default creds, .env in build context, GMaps key
  rotation, ASP.NET Core 8.0.21 -> 8.0.25, rate limiter) recorded
  for separate tickets.
- Step 15 (Performance Test): all PT-01..PT-07 scenarios Unverified
  (non-blocking); PT-07 baseline-comparison harness deferred to a
  leftover for next cycle.
- Step 16 (Deploy): cycle deploy report covering migration safety,
  rollback path, post-deploy verification, security caveats.

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

2026-05-11 10:03:05 +03:00

2.7 KiB

Raw Blame History

Leftover — PT-07 perf harness + cycle 1 perf run

Timestamp: 2026-05-11T07:05:00Z
Origin: autodev cycle 1, Step 15 (Performance Test)
Blocker class: non-user-input — work was deferred at the Step 15 user gate; no missing user decision blocks completion.

What was deferred

PT-07 implementation in scripts/run-performance-tests.sh: capture pre-change baseline for GetTilesByRegionAsync p95 latency, run post-change measurement, compute the ratio, and assert ratio ≤ 1.10. PT-07 was recorded as a documentation entry during Step 12 (_docs/02_document/tests/performance-tests.md + traceability-matrix.md "NFRs → Test Mapping" section) but the runner script does not yet have the corresponding scenario.
Active perf run of PT-01..PT-06 against the post-AZ-484 build. The runner exists; it requires docker-compose up on the dev host. Not executed this cycle (per the meta-rule "ask before kicking off Docker / long-running perf operations").

Why it is safe to defer

AZ-484 functional correctness validated by 5 dedicated AZ-484 integration tests (Step 11). The DB read paths exercised by PT-07 are the same ones exercised by MostRecentAcrossSourcesSelection_AZ484_AC2 etc.
The post-AZ-484 SQL uses the same idx_tiles_unique_location_source index as the contract specifies; structurally there is no new full scan, join, or lock added vs. pre-AZ-484.
Cycle 1 perf run is recorded as Unverified (not Fail) per the test-run perf-mode rules — gate does not block deploy.

Replay actions for next /autodev invocation

When the next cycle's autodev runs, before any new tracker write or before re-entering Step 15 in cycle 2:

Add PT-07 to scripts/run-performance-tests.sh:
- Capture a pre-change baseline by checking out the parent of the AZ-484 commit (git rev-parse HEAD~N where N points at the AZ-484 batch), running the existing PT-03/PT-04 region scenarios, and recording the GetTilesByRegionAsync timings (the repository already logs slow query warnings at >500 ms — extend that log line to include median/p95 captured per call window).
- Run the post-change measurement against the current HEAD.
- Compute the p95 ratio and fail when > 1.10.
Bring up the docker stack (docker-compose up --build -d) and run the full perf script with the user's explicit go-ahead.
Capture results into _docs/06_metrics/perf_<YYYY-MM-DD>_cycle<N>.md.
Once results are recorded, delete this leftover file.

Tracker action (none required this cycle)

This leftover does NOT require a Jira ticket on its own — it tracks deferred process work, not user-visible scope. If the perf comparison reveals a regression next cycle, that finding will create a Jira bug; until then there is nothing to file.

2.7 KiB Raw Blame History