Changelog

What's New

• Road-aware routing: Where road network data is loaded for South Africa, routing can prefer real road geometry after the safest hex corridor is found—better paths when the data is present.
• Operations pipeline: Documented and scripted steps to load road data into the platform database on Linux-style hosts (with automation-friendly containers where needed).
• Consistent errors: API failures return a predictable JSON shape (human message, HTTP status, machine-readable code, and request correlation when available)—easier for partners to log and retry.
• Discovery: A small metadata response describes what the running instance supports (version, capabilities, documentation links) so integrations can self-check after deploy.

Improvements

• Wrong HTTP method: Clients using GET on routes that expect POST receive a clear 405 with guidance instead of a confusing 404.
• Rate limiting: Throttled responses use the same error format as the rest of the API.
• Documentation: Expanded public docs for integration, collections, and operations (including how road data is produced).

Note

There were no new commits on origin/main for wolf-safety-router (Go) on 2026-03-25. The active ship for this period is 2026-03-23 — Safety router (Go) — public hex auth, CORS, and enterprise rate limits.

Note

There were no new commits on origin/main for wolf-safety-router (Go) on 2026-03-24. The active ship for this period is 2026-03-23 — Safety router (Go) — public hex auth, CORS, and enterprise rate limits.

What's New

• Stack: These changes ship in wolf-safety-router, the Go service behind public hex/config traffic and related routing (not the Node wolf-server).

Improvements

• Public hex reads: GET /hexes/all and GET /hexes/config are exempt from auth where appropriate so the public map can load configuration and hex data without a session, while authenticated routes keep normal rules.
• CORS for public data: Public hex responses only allow trusted Community Wolf web origins (e.g. *.communitywolf.com) instead of wide-open browser origins.
• Enterprise vs anonymous: Rate limiting distinguishes enterprise clients from anonymous traffic so dashboards are less likely to be throttled under normal load.
• Refactors: Wildcard CORS handling and related auth paths were tightened with lint fixes in the Go handlers and middleware.

Bug Fixes

• Auth middleware: Public configuration and hex requests are no longer blocked incorrectly by authentication checks.
• Lint and quality: Small cleanups in routing and CORS code paths for maintainability.

Engineering reference

• Window: All main activity for this release landed on 2026-03-23 (no further merges on main on 2026-03-24 or 2026-03-25 in this audit).
• Commits (chronological): 95b7d9d — exempt public hex GETs from auth; 28c0f7b — restrict public hex CORS; 9dd60a3 — enterprise rate limits + CORS/auth follow-up.
• Full diff artifact (Go tree): internal/git-audits/2026-03-22-to-03-25/wolf-safety-router-full.diff (range 95b7d9d^..origin/main at time of export).

Improvements

• Community context: Incident reports can be loaded at startup and merged into the hex graph for richer analysis.
• Scoring weights: Report, POI, and area context weights are tunable and wired consistently across scoring modes.
• Configuration: External configuration can drive scoring behaviour without code changes where supported.
• Engine modes: Optional second-stage engine can be enabled selectively; startup is staged to reduce peak memory use on smaller instances.
• Cache layout: Memory-efficient cache structure for large hex datasets.

Bug Fixes

• Scoring: Corrected weight application and modifier sign handling in edge cases.
• Quality: Test and validation fixes for routing and scoring pipelines.

Improvements

• Browser access: CORS and HTTPS settings aligned so web apps can call the service reliably in production.
• Large payloads: Timeouts tuned for very large aggregate responses so clients don’t fail mid-request.
• Memory: Safer default limits on constrained hosts to reduce out-of-memory restarts during heavy workloads.
• Routing: Wider initial search corridor and clearer road-only behaviour; optional toggles documented for operators.
• Operations: Deploy pipeline improvements with health checks and rollback paths when a release misbehaves.

What's New

• Signed-in hosting: Deployment configuration aligned with standard platform authentication for protected environments.
• Cache bootstrap: Optional automatic download of hex cache data on startup for faster cold starts.
• Private artefacts: Support for authenticated download of cache packages from private release storage when configured.

Improvements

• Resilience: Service continues with sensible cache fallbacks when the primary data store is temporarily unavailable.
• Health checks: Single consolidated health registration for monitors and load balancers.

What's New

• Precinct support: Cached precinct boundaries and related endpoints for location-aware routing and scoring.
• Hex scoring detail: Finer-grained hex scores with points-of-interest and open-map context where available.
• Scoring v2: Clearer curve and risk presentation; proportional use of POI context; more consistent segment scoring.

Improvements

• Corridor limits: Returned limits now match the active route configuration.
• Risk display: Tier scaling aligned with the latest scoring model.

Bug Fixes

• Scoring display: Curve and velocity presentation improvements for analysis views.
• Documentation: Notes on how precinct-level crime distribution affects scores where relevant.

What's New

• Hex corridors: Routes can follow corridor geometry aligned to the hex grid for clearer analysis.
• Road snapping: Paths respect road geometry where configured.
• Validation: Stricter checks before routes are returned to callers.

Improvements

• Documentation refreshed for teams connecting routing, scoring, and validation workflows.

What's New

• Safety Router: New service repository for routing and safety analysis workflows used by the platform.