Brings every cross-cutting doc surface in line with the 21 PRs that
landed on `main` on 2026-05-14, anchored by the v8.0 architectural
foundation (PR #125) and the security + correctness wave that
followed it.

- `CHANGELOG.md` — new `[Unreleased]` block covering the v8.0
  architectural foundation (graph at ingest, four-agent rebrand,
  `/hunt`, sixteen connectors, automation maturity, public
  scoreboard), the eight-PR security hardening wave (PRs #116-#128),
  the three-PR CodeQL alert sweep to zero (#133, #136, #137), the
  UEBA env-var alignment (PR #135, first community contribution,
  closes #134), the security-smoke + UX cleanup pair (PR #132,
  closes #131 + #130), and the playbook engine correctness pass
  (PR #129).
- `README.md` — new `v8.0 wave-1 (on main, not yet tagged)` entry
  in the version-history section; `Next` block rewritten as
  `v8.0 wave-2` with the still-`[~]` items from
  `AISOC_V8_PROGRESS.md`. Version badge intentionally not bumped
  (still 7.3.1) because wave-1 is on `main` but not tagged.
- `AGENTS.md` — new `v8.0 wave-1` block under "Learned Workspace
  Facts" documenting the four-agent topology, `/hunt` surface,
  connector inventory, automation maturity ladder, security wave
  outcomes, CodeQL hygiene patterns (inline `replace`-chain
  sanitisation for `py/log-injection`, single import style for
  `py/import-and-import-from`), and the UEBA env-var dual-alias
  convention.
- `AISOC_V8_PROGRESS.md` — `Status` block refreshed to record that
  PR #125 shipped at `b854010e` on 2026-05-14, list the 12
  post-merge PRs that landed on `main` after it, and clarify that
  wave-2 is the still-tracked `[~]` work.
- `apps/docs/docs/deployment/env-vars.md` — UEBA section rewritten
  around the dual-alias rule (unprefixed wins over `UEBA_`-prefixed,
  matches every other Python service and the `docker-compose.yml`
  exports); table now lists canonical + legacy names side by side.
- `apps/docs/docs/operations/security.md` — new `Static analysis
  (CodeQL)` section: zero alerts on `main` as a CI gate, plus the
  two patterns that came up repeatedly during the sweep
  (inline-at-call-site sanitisation for `py/log-injection`, single
  import style for `py/import-and-import-from`).

No code changes; pure documentation sync.

Co-authored-by: Beenu Arora <[email protected]>

Addresses the security review item on PR #139: the GET handler did a
flat dict lookup with no tenant filter, so any caller who learned (or
guessed) a run_id could read another tenant's findings, MITRE techniques,
and proposed actions. This diverges from the project convention
("tenant isolation is enforced at the query layer", see PRs #116–#128
that hardened /hunts and /cases).

Changes
- `get_triage` now accepts an optional `tenant_id` query parameter and
  returns 404 (not 403) on mismatch — same response shape as the
  unknown-run-id branch so a probing caller can't distinguish "wrong
  tenant" from "no such run".
- An absent `tenant_id` falls back to "default" and still 404s when the
  run was launched under a real tenant: fail closed.
- `_poll_until_done` helper updated to thread the tenant_id (defaults
  to "acme" because that's what _multi_signal_payload posts; per-test
  override available).
- Adds `test_get_with_mismatched_tenant_returns_404` covering owner-200,
  other-tenant-404, and absent-tenant-404. 9/9 triage tests pass.
- Picks up ruff format normalisation on triage.py (cosmetic: collapses
  two manually-wrapped expressions to fit `line-length = 140`; needed
  for the `ruff format --check` CI gate).

The two related review items (`_coerce_uuid("default")` cross-tenant
collision in the in-process store, and adding `Depends(get_current_user)`
for end-to-end auth) are deferred:
- The `_coerce_uuid` aliasing is cosmetic today (the store is
  single-replica in-process) and the PR body already notes that.
  It becomes load-bearing when this moves to Redis/DB and should land
  with the storage swap, salted with the resolved tenant UUID.
- Auth/Depends is intentionally upstream (gateway) for the agents
  service across all v8.0 endpoints; adding it here in isolation would
  diverge from the existing /investigate pattern.

Addresses the security review item on PR #139: the GET handler did a
flat dict lookup with no tenant filter, so any caller who learned (or
guessed) a run_id could read another tenant's findings, MITRE techniques,
and proposed actions. This diverges from the project convention
("tenant isolation is enforced at the query layer", see PRs #116–#128
that hardened /hunts and /cases).

Changes
- `get_triage` now accepts an optional `tenant_id` query parameter and
  returns 404 (not 403) on mismatch — same response shape as the
  unknown-run-id branch so a probing caller can't distinguish "wrong
  tenant" from "no such run".
- An absent `tenant_id` falls back to "default" and still 404s when the
  run was launched under a real tenant: fail closed.
- `_poll_until_done` helper updated to thread the tenant_id (defaults
  to "acme" because that's what _multi_signal_payload posts; per-test
  override available).
- Adds `test_get_with_mismatched_tenant_returns_404` covering owner-200,
  other-tenant-404, and absent-tenant-404. 9/9 triage tests pass.
- Picks up ruff format normalisation on triage.py (cosmetic: collapses
  two manually-wrapped expressions to fit `line-length = 140`; needed
  for the `ruff format --check` CI gate).

The two related review items (`_coerce_uuid("default")` cross-tenant
collision in the in-process store, and adding `Depends(get_current_user)`
for end-to-end auth) are deferred:
- The `_coerce_uuid` aliasing is cosmetic today (the store is
  single-replica in-process) and the PR body already notes that.
  It becomes load-bearing when this moves to Redis/DB and should land
  with the storage swap, salted with the resolved tenant UUID.
- Auth/Depends is intentionally upstream (gateway) for the agents
  service across all v8.0 endpoints; adding it here in isolation would
  diverge from the existing /investigate pattern.

* feat(agents): expose RouterOrchestrator over HTTP (T2.2, v8.0)

The parallel LangGraph topology (RouterOrchestrator) has been on `main`
with 17 passing unit tests since the v8.0 wave-1 push, but it had no
caller: nothing in `services/agents` actually dispatched a real triage
run through it. This wires it in via a new, additive HTTP surface
without touching the existing linear `/investigate` flow.

New endpoints in `services/agents/app/api/triage.py`:

  POST /api/v1/cases/{case_id}/triage    → launch run, returns run_id
  GET  /api/v1/triage/{run_id}           → poll status + telemetry

Topology resolution priority:
  1. explicit `topology` in the request body  (per-run override)
  2. AISOC_AGENT_PARALLEL_TOPOLOGY env flag    (deployment default)
  3. sequential                                 (safe fallback)

So existing deployments keep the safe default and individual callers
(eval harness, ops console, demo seed) can opt one specific run into
the parallel topology without flipping the env-wide flag.

Run state lives in an in-process `_triage_runs` dict (same pattern as
the existing investigate `_runs`). String tenant_id / incident_id are
coerced to deterministic UUIDs via `uuid.uuid5` against a project-
scoped namespace so the same string always maps to the same
InvestigationState — safe for tests + replay.

Tests (`services/agents/tests/test_triage_endpoint.py`, 8 cases):
  - POST returns run_id + status=running, topology resolved correctly
  - env flag flip (parallel ↔ sequential) honoured
  - explicit body override beats env flag
  - end-to-end fan-out: phishing/identity/cloud/insider sub-agents
    invoked in parallel, GET returns merged signals + wall_clock_ms
  - auto-close short-circuit when classifier yields zero signals
  - GET on unknown run_id → 404
  - minimal-body POST (no tenant_id / incident_id) coerces cleanly

Sub-agent runners + `_emit_event` are shimmed via `monkeypatch` so the
suite is hermetic — no Kafka, no LLM, no Neo4j. Patterns mirror
`test_orchestrator_parallel.py`, which is unchanged and still green
(17/17).

The legacy `/api/v1/cases/{id}/investigate` linear streaming path on
InvestigatorOrchestrator is untouched — zero blast radius on existing
demos or the Investigation Rail.

Marks T2.2 done in AISOC_V8_PROGRESS.md and adds an [Unreleased] entry
to CHANGELOG.md.

Signed-off-by: Beenu Arora <[email protected]>

* fix(agents): enforce tenant isolation on GET /triage/{run_id}

Addresses the security review item on PR #139: the GET handler did a
flat dict lookup with no tenant filter, so any caller who learned (or
guessed) a run_id could read another tenant's findings, MITRE techniques,
and proposed actions. This diverges from the project convention
("tenant isolation is enforced at the query layer", see PRs #116–#128
that hardened /hunts and /cases).

Changes
- `get_triage` now accepts an optional `tenant_id` query parameter and
  returns 404 (not 403) on mismatch — same response shape as the
  unknown-run-id branch so a probing caller can't distinguish "wrong
  tenant" from "no such run".
- An absent `tenant_id` falls back to "default" and still 404s when the
  run was launched under a real tenant: fail closed.
- `_poll_until_done` helper updated to thread the tenant_id (defaults
  to "acme" because that's what _multi_signal_payload posts; per-test
  override available).
- Adds `test_get_with_mismatched_tenant_returns_404` covering owner-200,
  other-tenant-404, and absent-tenant-404. 9/9 triage tests pass.
- Picks up ruff format normalisation on triage.py (cosmetic: collapses
  two manually-wrapped expressions to fit `line-length = 140`; needed
  for the `ruff format --check` CI gate).

The two related review items (`_coerce_uuid("default")` cross-tenant
collision in the in-process store, and adding `Depends(get_current_user)`
for end-to-end auth) are deferred:
- The `_coerce_uuid` aliasing is cosmetic today (the store is
  single-replica in-process) and the PR body already notes that.
  It becomes load-bearing when this moves to Redis/DB and should land
  with the storage swap, salted with the resolved tenant UUID.
- Auth/Depends is intentionally upstream (gateway) for the agents
  service across all v8.0 endpoints; adding it here in isolation would
  diverge from the existing /investigate pattern.

* fix(lint): UP038 in test_triage_endpoint — use X | Y in isinstance

main pinned ruff to 0.4.x in PR #191 and enforces UP038 (PEP 604 union
syntax in isinstance) without `--unsafe-fixes`. The new wall_clock_ms
assertion in this branch used the old `(int, float)` tuple form, which
trips the gate.

---------

Signed-off-by: Beenu Arora <[email protected]>
Co-authored-by: Beenu Arora <[email protected]>
Co-authored-by: Prince Sinha <[email protected]>
Co-authored-by: cursor-agent <[email protected]>
Co-authored-by: beenuar <[email protected]>