String resource management UI

[einari]

Context

Depends on Screenplay's string resource construct (pending reconciliation
with the existing Internationalization language feature — see that
Screenplay issue). Studio needs a way to manage owned strings per
module/feature and let users promote literals to resources.

Proposal

• "Extract to resource" action on any literal label "text" (or other
  text-bearing property) — prompts for a resource name, creates the entry
  in the owning module/feature's strings, rewrites the reference in
  place. Mirrors IDE "extract to constant" UX.
• Per-locale editing surface once the locale model is settled — a table
  view per strings block, one column per active locale.
• Missing-translation indicators, consistent with how other gaps
  (unresolved names, incompatible themes) are surfaced elsewhere in
  Studio.

Open questions

• Blocked on the Screenplay-side reconciliation with the existing
  Internationalization construct — don't build the per-locale table UI
  until that's settled, to avoid building against a shape that changes.

---

Dependencies

Depends on

• Language construct: string resources for UI text (labels, nav, etc.) Screenplay#93 — the strings construct, itself blocked on Internationalization for strings Screenplay#7
• Screen editor: make the Scene designers editable and retire the legacy wireframe editor #156 — the surface "extract to resource" acts on

Blocked: don't build the per-locale table UI until the Internationalization reconciliation in Cratis/Screenplay#93 settles, to avoid building against a shape that changes. The "extract to resource" action can proceed ahead of it.

Part of the screen work — build order and full dependency map: Cratis/Scene#7

---

Scope update — Cratis/Screenplay#93 is decided, this is unblocked

The language side resolved to extending the existing $strings. mechanism, not adding an inline strings block. That settles the shape this UI edits against, so the "blocked" note above no longer applies. Concretely:

• "Extract to resource" takes a literal label "text", writes a <key.path> = "text" entry into the .play file's companion .strings file for the default locale, and rewrites the reference in place to the unquoted token $strings.<key.path>.
• Per-locale editing is a table over the companion .strings files (MySystem.en.strings, MySystem.nb.strings, …) — one column per discovered locale, rows keyed by dotted key. StringsFiles already discovers every .strings file under a root and exposes base name + locale, so Studio does not need its own discovery.
• Missing-translation indicators are keys present in one locale's file and absent from another — computable directly from the same discovery.
• Keys are dotted paths (invoices.actions.newInvoice); ownership is expressed by key naming, not by a language construct. The "extract" flow should propose a key prefix from the declaring module/feature.

Format details and the round-trip guarantee are in Documentation/screenplay/internationalization.md in the Screenplay repo.

[cratis-direct]

Thanks for opening this - it has been received and will be looked at.

---

Posted by Stagehand (AI) - an autonomous agent, not a person. Review accordingly.

[cratis-direct]

Thanks for opening this - it has been received and will be looked at.

---

Posted by Stagehand (AI) - an autonomous agent, not a person. Review accordingly.

[woksin]

Program kickoff and scoping have started locally as part of the coordinated end-to-end Screenplay/Stage/Studio/CLI delivery effort tracked in Cratis/Screenplay#174. This issue is in a later/nonblocking lane, not a prerequisite for the first deterministic backend delivery. @woksin is coordinating in dependency order with repository-specific AI corpus instructions and specifications. Existing work/PRs will be reconciled rather than duplicated. This is a kickoff, not a completion claim or a claim that a coding branch exists for this issue; focused progress, verification evidence and blockers will follow here.

[einari]

Consolidated into #156.

Every upstream dependency this issue waited on has shipped (Cratis/Scene #1–#6, Cratis/Screenplay #91–#96), and the read-only half of this designer is already on Cratis/Studio@main under Source/Editor/. What remains is the same remaining work as every other designer — making the surface editable and retiring the legacy PrototypeEditor, which is one job, not eight.

#156 now tracks that, and carries a table of exactly what this issue asked for, what landed, and what is left.