docs: localization spec — explicit no-tier-gating decision

Translate for any user with lang='it' regardless of paid/free status.
Italian + UK are the first markets, so IT availability is part of the
public-facing experience — a free-tier visitor needs to see the AI in
Italian to convert. At ~$0.005/day total cost the gating isn't worth
the savings.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

docs/superpowers/specs/2026-05-27-localization-italian-design.md

@@ -373,3 +373,10 @@ End-to-end manual check after deploy:
 - We do not surface translation cost in any user-visible UI. Cost is
   recorded in `strategic_log_translations.llm_cost_usd` and the existing
   `ai_calls` ledger picks up per-user calls as today.
+- We do **not** gate strategic-log translation on user tier. Any user
+  with `lang='it'` triggers Italian translation for that hour's log,
+  regardless of whether they are paid, on credit, or free. Rationale:
+  Italian + UK are the first markets the operator is targeting, so
+  Italian availability is part of the public-facing experience — a
+  free-tier visitor needs to see the AI in Italian to convert. At
+  ~$0.005/day total cost the gating overhead is not worth the savings.