Ursa 4.0.13

Ursa 4.0.13

Production support release for OWY run-directory analysis triggers.

• Documents the explicit ursa_run_directory_analysis_* production policy required by /api/v1/dewey/run-directory-analysis-triggers.
• Adds coverage for OWY's current ILMN command, illumina_run_qc_bclconvert, as a run_analysis command.
• Keeps missing policy config as a loud 503; no fallback/default inference is added.
• Runtime rollout notes: production lsmcok1 is configured with goodole3, us-west-2, johnm@lsmc.com, and the approved DayOA reference/result S3 roots. Secrets are not included in this release note.

daylily-ursa 4.0.0

Breaking DayEC bucket-contract release. Ursa now uses explicit reference/control/stage S3 URI fields, pins daylily-ephemeral-cluster 5.0.0 and DayOA 2.0.0, and rejects retired /fsx/data staging paths.

3.0.6

Split Ursa observability, write, and TapDB admin service credentials.

3.0.5

Ursa GUI cache warmup and shell hydration refresh.

3.0.2

Release Ursa explicit allowed host filtering and explicit TapDB domain runtime configuration.

2.0.11.35

Release 2.0.11.35

2.0.11.21

Pin daylily-ephemeral-cluster 2.3.3 and disable S3 acceleration for Ursa daylily-ec subprocesses.

2.0.11.20

Pin Zebra Day 6.0.11 to keep TapDB 6.0.13 dependency graph consistent.

2.0.11.19

Pin daylily-tapdb 6.0.13 while preserving daylily-ephemeral-cluster 2.3.2.

2.0.11.18

Align TapDB schema init args with TapDB 6.0.12 and update Zebra Day dependency to 6.0.10.