[Ticket]: Re-scope the store/query epics after the ADR-0014 boundary decision

Tracked by lightbridge-authz epic: ADORSYS-GIS/lightbridge-authz#581

### Type

Chore / follow-up

### Summary

ADR-0014 (mirror of lightbridge-authz ADR-0027) resolves the store boundary as consolidation: the telemetry store moves to `lightbridge-authz-usage`; this repo keeps the collectors. Several open epics/tickets here were scoped against "this repo keeps the store" and must be re-scoped, re-labeled, or closed with a pointer — explicitly, per issue, so the backlog stops asserting the rejected architecture.

### Intent

Two ADRs that agree are only useful if the backlog agrees with them. #161's own assumption said "if the boundary resolves the other way, this epic moves repositories" — it now does; this ticket is the bookkeeping that makes that true everywhere.

### Source of truth (links)

ADR-0014 (this repo) · lightbridge-authz ADR-0027 · lightbridge-authz#535 · #182

### Current Behavior

#159 (Timescale foundation here), #163–#166 (image/hypertables/retention/aggregates here), #167 (generalise day tables here), #161 + #183–#188 (query API here) all target the governance Postgres.

### Expected Behavior

Per-issue disposition recorded on each issue:

- **#159, #163, #164, #165, #166** — close or re-point: the Timescale foundation work happens once, in the authz usage store (lightbridge-authz#489 + the new epic there). Anything governance-specific in their text (e.g. #163's CNPG image findings) is copied across before closing, not lost.
- **#167** — superseded in place by the authz day/seat-grain story: the generalised schema is built in the consolidated store; this repo's vendor-named tables are migrated then dropped (authz cutover story), not generalised in situ. Close with pointers.
- **#161, #183, #184, #185, #186, #187, #188** — move repositories: their requirements are carried by the authz per-grain query API story (and are cited there). Close here with pointers, or transfer if history matters.
- **#160, #168, #169, #170, #171, #84, #144, #189, #191** — stay here, retargeted at the usage ingest endpoints where they name `/internal/v1/ingest`.
- **#95, #96–#105, #30, #158** — stay here as collector/normalizer/schema-definition work; storage target updated to the consolidated store in each body.
- **RFC-0003 §6** — corrected by the ADR-0014 PR itself.

### Acceptance Criteria

1. Every issue above carries a disposition comment linking ADR-0014 and (where applicable) the successor authz issue.
2. No open issue in this repo still asserts that telemetry storage or its query API lives in the governance Postgres.
3. Epic rollup points (#159's 24, #161's) are re-planned, not silently deleted.

### Out of Scope

Doing any of the moved work; the data migration itself (authz cutover story + the governance-ctl re-sink story).

### Technical Context

The `executions`/`model_calls`/`tool_calls` schema and the normalizer designs here are the *donor* artifacts — the authz stories cite them as the shapes to port, so keep them readable until the port lands.

### Risks

Closing issues before their requirements are demonstrably carried by the successor issues loses hard-won constraints (e.g. #185's provider-user-id join rule, #188's no-`unwrap_or(0)` rule). Mitigation: the authz stories were written citing these issues explicitly; verify each citation before closing.

### Test Plan

N/A (backlog bookkeeping); AC 2 is checkable by search.

### Verification evidence

Links to the disposition comments, added as this ticket is worked.

### Human accountable owner

Stephane Segning Lambou

### AI Usage
AI-assisted (Claude): research and drafting. Reviewed and owned by Stephane Segning Lambou.