docs(lore-0051): descope step 3 (remote mTLS apply), apply over loopback admin

[karczuRF]

What

Reframes task 0051 around applying the prices.* schema over loopback as the box default admin (BE's docker-compose sidecar model) and descopes Step 3's remote mTLS DDL apply path.

Why

Studying BE's infra-hetzner + crates/db-clickhouse:

• BE's db-clickhouse-init applies schema as a sidecar on the box over the plaintext Docker bridge as default — there is no mTLS in the apply path.
• BE removed its remote-DDL users (migration_admin/partition_admin, BE task 0241).
• mTLS in BE is solely the runtime read/write transport for the remote api/indexer Lambdas (mtls::client_from_lambda_env).
• Task 0063 grants prices-api the same posture — box admin via loopback (clickhouse-client --user=default on the box, 0063 Steps 1+3).

So a remote mTLS DDL connection is unnecessary and re-introduces exactly what BE retired.

Changes (task doc only)

• Step 3 marked descoped; no mTLS code — the existing plaintext prices-clickhouse-init is the apply tool.
• Step 4 reframed: run the plaintext init against the box loopback (on box / SSH tunnel) as default admin.
• Acceptance criteria: dropped the mTLS criterion; live-apply criteria reframed + marked gated on 0063 handover.
• 0052 dependency dropped from Blocked-on; rationale recorded under Design Decisions → Emerged docs(lore-0003): amm-trades-schema §7 + §11 — four-decoder reality #5.

No code changes. mTLS (0052) remains the runtime transport for 0038/0039/0040.